Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

30 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So I did some googling on microg and signature spoofing and found some useful bits on the lineage page of the microg project: https://lineage.microg.org/ "Can you add support for my device? It is officially supported by LineageOS We already build LineageOS for microG for every device supported by LineageOS. Find your device in our Downloads page!" So @tdm just forget about my request and focus on getting the build to the official stage...and an official unofficial microg build should magically appear πŸ˜ƒ For anyone interested in why lineageos doesn't officially support the signature spoofing I'd say the microg FAQ is interesting to read, as well as this reddit post and the comments on the codereview it links to:
  2. @tdm: Thanks for all the hard work :). As I've said before somewhere I want to try and go googlefree, with microg. From what I gather signature-spoofing is required for some things and I know @Loader009 did a one-off build with support for this. I have no idea how much work this would be and if it's something you're up for, but would it be possible to get a micro-g ready build together with the regular build? I've been thinking about setting up a build and release pipeline myself, but all of my experience with this is limited to azure resources and database stuff as I'm a bi-developer by trade. I think I should be able to figure it out for myself based on the comments by @Loader009 and others earlier in this thread, but I'm a bit short on time for at least the rest of this month :(. If I get it to work, I'll share a link. If I'm not mistaken the key to getting nanoDroid (and anything else) to flash to /system from the recovery is waiting for you to get TWRP up and running with decryption. So I'll patiently wait for you to get to that and buy you a few beers (just not corona :D).
  3. @Loader009: Looking at your discussion with @tdm about enabling shell in recovery I gather that you've also not yet been able to get Nanodroid working. I've been wondering whether things would be easier with the TWRP-build in the SailfishOS thread, but haven't quite gotten around to trying that - probably next weekend. If you did manage to pull it off I'd be very happy to hear how you did it :).
  4. So I flashed test-build 3 and everything was fine. Made sure to flash recovery to a and then flash the zip to b. The only problem I'm running into is that I am having trouble sideloading nanodroid over adb :(. At first I just tried to sideload from recovery, but then realized that if I was in recovery with b active it would probably try to install it to partition a which is not where I flashed the .zip. -- rereading the instructions on the page about flashing gapps and they point this out as well. Anyhow...then proceeded to set partition a to active before flashing, but still no dice. In all instances the nanodroid wizard works perfectly...but when I reboot after installation f-droid and the aurora store are nowhere to be found - nor any of the other nanodroid changes. Is this a known issue or am I doing something wrong? Starting to get why the multi-partition thing can be annoying :P.
  5. Is there any trade-off or downside to enabling the VoLTE switch? (If not then why is it disaled by default? @tdm: thanks for all your hard work, loving the speed with which you're fixing LOS. Once testbuild 3 is out i think I'm ready to take the plunge. When I'm on build 3 I'll test the cheapo usb lan adapter I have lying around like somebody asked earlier in this thread.
  6. You should try calling yourself from your new phone to ask yourself to come in for a stern talking toπŸ˜†πŸ˜‹. I am unsure at the moment what to do. My current phone has never been de-googled, but I have a few lying around with google-free custom roms (native and GSI). I was actually considering to give it a go but I still have to investigate which rom to choose for this (Google free stock/Lineage/Sailfish/ ...)
  7. Just took delivery of my clack πŸ˜„ My cats (one of them at least) were also happy with the delivery
  8. So No IGG, in the Netherlands Pre-ordered 2019-06-13 Ordernr. 173## Received payment link on 2019-07-31 Paid by CC on 2019-08-02 Received stock assigned yesterday (2020-01-20 at 12:43 local time) Received tracking e-mail and txt today (2020-01-21 at 10:44 local time) Expected delivery here in NL, sometime this friday 2020-01-24. EDIT: Ordered me a qwerty keyboard
  9. Pretty sure I wouldn't have much trouble to convince my wife that we should do little city trip to London (from the Netherlands)....πŸ˜ƒ
  10. Thanks Erik, looks like things might be stabilizing and slowly ramping up. Looking at the margins you mention in relation to the number of weeks before Christmas, hitting general availability before Christmas may or may not happen. I hope that pans out in a way that works for FxTec, in terms of not missing (too much) of the holiday sales season.
  11. Then you could maybe even go crazy with the Frankenstein solution suggested by @Swond and @EskeRahn in the speculation thread and have esim + dual sim + microsd πŸ˜„. Really have no idea what you would use it all for or why you would want it, ... because you can? πŸ˜‹
  12. So I'm posting this in General because this is purely a matter of curiosity on my part, and I'm still (im)patiently πŸ˜‰ waiting for all the logistics and production issues to pass so I can receive my device, so wouldn't really call it a support item. Does the Pro1 have esim support? And if not, is this something that could be enabled at a later stage with a software update? Some phones with the Snapdragon 835 SoC support esim, but not all of them: https://www.gsmarena.com/compare.php3?idPhone1=8733&idPhone2=8647&idPhone3=8523#*,*,g955u https://www.manninfotech.net/lenovo-launched-miix-630-with-a-qualcomm-snapdragon-835/ - Would this be because They are variations on top of the same base SoC? i.e. SD835 is compatible with eSim it but its not part of the SD835 SoC as such. The Soc is capable of it but not all vendors/oems choose to implement it on the software side? (Possible motivations below) Development costs outweigh the perceived benefit or value of the extra feature. Staying friendly with Telco's, who as I gather are not too keen on eSim - because it will effectively lower the transaction cost of changing providers for consumers. Effectively contributing to reduction of perceived value or benefit as mentioned in the above point. The following code snippet shows part of the software implementation, I think, but I don't know to what extent this is dependent on the underlying hardware (see the first possible explanation above) <!-- Number of physical SIM slots on the device. This includes both eSIM and pSIM slots, and is not necessarily the same as the number of phones/logical modems supported by the device. For example, a multi-sim device can have 2 phones/logical modems, but 3 physical slots, or a single SIM device can have 1 phones/logical modems, but 2 physical slots (one eSIM and one pSIM) --> <integer name="config_num_physical_slots">2</integer> Source: https://review.lineageos.org/c/LineageOS/android_device_oneplus_msm8998-common/+/237480/1/overlay/frameworks/base/core/res/res/values/config.xml I'm completely fine with regular sim so at this point in time the issue is purely academic to me, but I'm curious anyway 😁.
  • Create New...

Important Information