Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/10/2021 in all areas

  1. Not sure what you mean by "special care," Updating via sideload is: 1. Boot to recovery 2. Adb sideload (name of nightly update zip) 3. Reboot to recovery (this changes the slot to the slot where the new update was installed) 4. adb sideload current Magisk zip (no need to reboot to recovery after this step) 5. adb sideload Gapps package zip. 6. System reboot. I have no idea if steps 4 and 5 are necessary if you are just updating, but they take little time and they can;t hurt, so I do them. None of this disturbs your user data pr anything you already h
    2 points
  2. It doesn't stop at "potentially disruptive", Google makes Android safer and more secure with every new version. Unfortunately they also make Android more restrictive for power-users and they gradually "encourage" users to stay away from SD-cards. At the same time, Android 11 doesn't look or feel much different from Android 4. At least not when you are used to tweaking the OS with GravityBox and custom launchers. I f-ing hate that everything is being developed in a haste. There is no time to settle on anything stable and work out the kinks. There has to be a brand new product on the marked
    2 points
  3. Attached fx_tec_pro_1_case_bottom v3 v3 -mod.stl fx_tec_pro_1_case_top.stl
    2 points
  4. I would prefer if it was settings the user could select/deselect (without the need of rooting and messing with system files)
    2 points
  5. So I get the setting improved things on your phone too? I now somehow regret not to have stressed the follwing from the beginning: Fully enabling AGPS (which I believe these settings do) enhances the functionality of GPS at the cost of privacy! There are valid arguments for having AGPS disabled by default in LineageOS and leaving it to the individual user to opt-in. See e.g. https://forum.xda-developers.com/t/keep-a-gps-supl-disabled-upon-rom-install.3612024/ However, I am not in charge. Go ahead with submitting a patch if you feel you must. 🙂
    2 points
  6. 1 point
  7. Tru dat, ive dropped mine several times with the 3d case and its unfazed, its almost like it doesnt matter if it droips anymore hehe
    1 point
  8. I would but am in Tanzania so far off, but ask @belletrist i gave him the schematics and he printed them well. He might be able to do it for you
    1 point
  9. When you're using the LOS updater, at some point it prompts you to reboot to finish the upgrade. At this point you can enter Magisk > Install > Install to inactive slot (after OTA). after this finishes, you can reboot and finish the upgrade.
    1 point
  10. Thanks for keeping us updated. This is interesting. I had ordered a spare display during the latest indiegogo campaign to be able to react without delay to such a situation (I guess I will face the same situation as the others from the batch soon...). I ordered display with frame because I do not feel able to play with a heat gun. Now I see that the delivery date for the display has also been postponed to August 2021. What is the reason for the postponement? I understand the delay for the Pro 1 X due to the Chip issue, but why a delay for the display?? The reason for this post
    1 point
  11. LineageOS devs seem to be disinterested too, they treat gapps-free users as weirdos.
    1 point
  12. Agreed. Unfortunately, it's not that straightforward to implement.
    1 point
  13. That's something I would be interested in, too. LOS 17.1 was painless for me so far with OTA updates – but then again it was non-rooted, no Magisk, just LOS + Gapps. Now that today one of my mandatory banking apps (mandatory even for entering internet banking on the PC) has stopped working, complaining about a modified software/firmware, I'll need root plus the stuff that hides both root and the fact that it's an alternative ROM rather sooner than later. I guess changing the update procedure to sideloading the updates like @Hook has been doing would be ok for me, although I'd be even
    1 point
  14. Again, I've only ever adb sideloaded the updates, as well as reflashing Magisk and Gapps. It has always gone smoothly for me with both Lineage and AICP.
    1 point
  15. Tried to extend the opengapps table with MindTheGapps: The last two I THINK could be included as obligatory in say "Google System Base" for OpenGapps. (I got them on AICP Q + OpenGapps 10 Pico also)
    1 point
  16. Went from, lineage-17.1-20210329-nightly-pro1-signed.zip on March 5 security patch installed using adb sideload and opengapps pico 20210327 to lineage-18.1-20210405-nightly-pro1-signed.zip on March 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210328_143848 Note that it went (almost) smooth DESPITE the change from opengapps to mindthegapps 👍 (note there is a new 0405 18.1 build already) (Edited below) I have issues selecting anything but US hardware some build in layout for the keyboard though. So currently the keyboard on 18.1
    1 point
  17. So the ghosting got worse again, I decided to do another re-seat. One thing I noticed this time was that the screw holding down the LCD cable assembly next to the earpiece basically fell out. I've screwed it back in now and tightened it down, wonder if that was a contributing factor as well. Let's see how long this fix will last, FXtec quoted me 1 month for the replacement display to be shipped. EDIT: Nope, didn't help at all.
    0 points
×
×
  • Create New...

Important Information

Terms