Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/18/2021 in Posts

  1. I haven't tried AICP yet because LOS 18.1 has been working nicely, including OTA updates wich leave both GApps and Magisk intact. Also, according to the settings page, my phone is encrypyted, too.
    2 points
  2. When I still had an official LineageOS, I was applying every weekly OTA and "su" would be preserved reliably. I never disabled encryption. Those were the days of AddonSU though, which was officially supported by LOS. Always remember that Magisk is a third-party tool before blaming the OS for it to stop working for some reason. Today I run my own builds which I install via sideload. This requires "su" to be reinstalled at every update ... one gets used to it. At this point, I would not prefer one ROM over another just for its ability to maintain root across updates. Let's face it: us roote
    1 point
  3. Related to this, in not such an easy way, the key thing that i gathered from a lengthy call with At&t when trying to add the Xperia 10 ii (returned it cause At&t insisted it will not work) is that and impacts my current Xperia 10 (which they said it likely won't but were less insistent). The key thing is they are doing a full court press (basketball) whenever a new device hits a 3G tower, which was the case with the Xperia 10 ii, for some reason on data it would not go 4G, so they immediately disabled it. However when calling them and getting to the advance tech support, they will ok
    1 point
  4. (lineage-18.1-20211018-nightly-pro1-signed.zip on October 1 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.
    1 point
  5. A big problem you would have is that AT&T has also been kicking off Pro1s and I don't expect it to be any different with the Pro1x. AT&T, after for years being willing to accept any phone and let you deal with whether or not it worked, has decided to only allow whitelisted phones that they have approved in their database. This is disappointing. I used AT&T pre-paid for years, starting when they were Cingular Prepaid. I left AT&T before they started pulling this and am on T-Mobile now, but it is disappointing.
    1 point
  6. Uploaded my LOS 16.0 build dated 20211017. AOSP patchlevel of October 2021. Contains a version of @Slion's experimental "Fn-Tab-as-Alt-Tab" mod as discussed above.
    1 point
  7. I agree that Fxtec's keyboard design is better for most purposes, even though some people complain about it being too wide for comfortable thumb typing. I cannot confirm this; I have rather small hands and I got used to its dimensions very quickly. That Pinephone slider keyboard prototype looks a lot like what the Fxtec people (then named Livermorium) tried to do for the Moto Z series of Motorola phones with their Keyboard Mod!
    1 point
  8. I feel similar to Hook. The lineage is a cleaned up Android, where you can infest it with the Gapps you need or none at all to your liking. The Aicp is (in my layman terms) like a Lineage with added options to tweak as you please. I like the AICP better, as it somehow feels cleaner. But I must admit that I barely use all the options, as none of the OS's are on my daily driver (a normal retail unit) that runs plain Android. I have a suspicion (though I have not yet tested!) that some of my apps will not work if I upgrade from stock Android to AICP. One app that I find crucial with a fli
    1 point
  9. That is pure hindsight bias. It is useless to look behind. Of course you would have made money if you knew back then what courses are today. If you would have bought XTZBEAR Coins for that money you would have like 0.02 $ right now...
    1 point
  10. Yes, this is a 2-in-1 problem. The first one is the different keymap of shifted (QWERTY) and normal (QWERTZ) variants of keyboards we have. It is a bit strange that F(x)tec itself has generated this issue as otherwise these layouts would work exactly the same way deep inside. So the problem is the shifting itself which made default layout of Pro1 to be unusual while QWERTZ variant is a perfectly usual layout. So @tdm's keyboard driver solved this issue by allowing to map appropriate keycodes to shifted keys respective to its written functions while also maps appropriate keycod
    1 point
×
×
  • Create New...

Important Information

Terms