zurvan2

Any root-using software could do it. I hit it using AdAway before I found the Magisk and AdAway option to configure "systemless" mode for both. Some apps or plugins/whatever might have a "systemless" option that prevents modifying the system partition. Check docs, but the best way to know is to test. 😉 The way it works is that an incoming OTA update checks the signature of the filesystem before proceeding, and if it's different at *all*, it can't be applied. OTA updates are basically a binary diff of the whole disk, so any difference from what it expects could result in a completely bric

There are several links to various stock rom packages in this thread: That thread also has instructions for rooting the stock rom. It will require wiping data. This thread Has yet-more images, and also instructions to roll back to older releases. Personally, I recommend rooting, installing all the magisk stuff you want to use, and then testing the ability to upgrade without losing root before you add any other data. You have to be very careful to not modify the system partition to preserve the ability to upgrade.

That link does work, thanks, I'll try it out. Any experience using this for video?

Anyone have links for these apps that work? I've tried searching, but I've found tons of results, and none seem to work. 😞

I've had mine for a bit over a year, since December of 2019, with a several-month gap this past summer while it was repaired/replaced in London. Covid-19 has meant that I'm at home most of the time, so there aren't as many reasons to use the phone keyboard, since I'm not "out and about." I always have quick access to my own real computer instead. The phone is still excellent in most ways. It really does "just work" for almost everything. The keyboard is still great when I use it, battery life is great, etc. No complaints about power or the screen or most of the software. Update

I'm using this https://www.amazon.com/dp/B07Y6F74F1/ref=cm_sw_r_cp_apa_fabc_VmSZFbVN4KMV9 and it works great. I'm really happy that FX Tec is supporting this kind of standard thing.

@netman This review was really great! I'm particularly fascinated by the lxc container support... that was really impressive. If anyone else is, there's a reddit post with some more information here:

My pro1 took a little vacation to London to be repaired, and it's now back, so I'm setting it up again. In the stock camera app, if I select "SD Card" for storage, it's writing the files to Android/data/org.codeaurora.snapcam/files rather than to DCIM/Camera. I thought this wasn't the case the last time I had a pro1 set up... Is there a way to get the stock camera to store photos in the standard place (I.E. DCIM/Camera) on the SD card? (and the card is set up as external, not adopted storage. I want it to be usable as a way to move files on and off the device)

Interesting. I'm also using a silicone case like that from a P20 Pro, but not the flip case, and it I don't find that it helps much with screen edges. I really wish we had something similar for the top part of the phone. *That* might help with screen edges, and would protect the phone more.

What case are you using that helps with the screen edge?

You can also order a replacement screen assembly directly from support, but it's more expensive. It is a simple process to replace, though.

I have always required root on my phones. I will not buy a phone that can't be rooted. I've even bought phones without a keyboard, but that were rootable. Root is non-negotiable. OTA Updates are affected, not directly by root, but by other things using root to modify the partitions that the OTA updates would affect. The OTA mechanism is a simple binary diff, so if a single byte is out of place, it would fail. This is done to minimize download size. I totally agree that android would be better off for all users if they adopted a finer-grained permission model for apps. In particular,

I've attempted to get Dolphin up and running, but no luck so far. If anyone has a game that's free on the play store that demonstrates the issue, that would be simplest to test.

How would you recommend doing so? I haven't noticed any performance problems so far, so I don't think I have any use cases that would stress it.

Governor: interactive Scheduler: cfq

I'm on rooted stock. What do I need to do?

Each partition has an image that can be applied to reset that partition to what it "should" be. Most of the partitions then cannot be modified and have OTA updates work... any modifications would make the OTA fail checks that ensure that the update is safe to apply. This is actually valuable, because the updates are not complete images, they are like a recipe to take the existing data on the partition and write new bits in specific locations. If the existing partition doesn't match the expected image, that could write complete garbage over whatever is actually there. There are a couple pa

Do Lineage and/or Sailfish have OTA updates that work while rooted? I've always been under the assumption that stock + rooted is the simplest to maintain, but perhaps I've drawn incorrect conclusions.

Same here. I mostly notice it in Termux, and didn't know if it was specifically an issue with Termux. Now confirmed in other apps. This happens every time the screen turns on and off, not just at boot time.

Roguelikes! The keyboard lets us play "real" roguelikes, not just the ones that have been simplified for mobile. Cataclysm: Dark Days Ahead Dungeon Crawl Stone Soup Nethack Brogue

There's an app called KeyMapper (and many other options as well) that will let you redefine the behavior of keys. You could use that to make shift-3 produce that symbol.

I would rather have to enter my password manually than have my phone subject to arbitrary inputs when it was unlocked without my knowing. This is the original purpose of a "keyguard".

I don't think most people are complaining that it's hard to reach the fingerprint reader... most complaints are that it's too easy to *unintentionally* activate the fingerprint reader. The failure cases are that the phone is already unlocked when you go to use it or that the screen shows "too many attempts". Both are because the fingerprint reader is, in essence *too* convenient.

I also had this. My theory was that despite my best efforts, something had actually modified the system partition, making the checksums not match. I restored the stock system.img as well as boot.img, and that let the update proceed. I was lucky that the version I was updating from was the original stock rom that I had system.img for. Since then I have been *much* more careful about things modifying the system, and have not had the same problem.

Compare lists of LTE bands on the two phones and t-mobile. You could also try an app like LTE Discovery on each device to show you which bands are in use.