Hook

Updated to the 29 SEP weekly via OTA. All went smoothly and root was maintained, September security patch.

Not surprising. Try passing on these two videos to a shop and see if those, the specs and that fact that, other than the keyboard, it is a bog-standard Andriod phone gets someone willing to look at it.

Maybe, but I suspect your case was made much easier because they were Sony phones-- phones from a major known manufacturer. I'm not confident that will work as well for an FxTec phone, but one can hope (Though I have moved to T-Mobile now). Agree about the honey...

@tdm This is from the AICP-Q thread, but I'm wondering if any progress has been made on this?

Updated to the 22 SEP weekly via OTA. All went smoothly and root was maintained, Basically, looks like the same updater Lineage uses and has the same result.

Yeah, not in my spam box. I'll chalk it up for now to some blip in the internet, like dryers eating socks. 😉

This is the first time I didn't get an email of the update. 😕

Just a final note. Have most everything set up again and I am loving being back on AICP-- my favorite tweak being that it uses Slim Recents. Still tweaking, but everything is running smoothly.

I seem to have successfully flashed AICP 16, but I'll update once I have the phone fully set up again which will take me a while with other things I have to do. It booted up and is running very smoothly. I used the Lineage 18 recovery and started by wiping data/factory resetting, assuming a dirty flash wasn't a good idea. I did adb sideload and then, as always, rebooted to recovery. When I did that, I got a few mounting errors (which I didn't write down, sorry) which I chose to ignore. Lol. I flashed Magisk and open gapps nano and booted the system. Usual longer bootup for first time. E

oh, quick question before I go to bed. Is there an R boot image/recovery?

Thanks so much, @tdm Can't wait to try this out in the morning! 😎

Okay, virtually everything in this thread is over my head. Can someone direct me to good sources to figure out how to create or modify a keymap and what to do with it. I'd really like to understand how to make this modification on my Pro1 and I'm willing to do my own homework, but would appreciate being pointed in the right direction. 🙂 TIA.

That looks correct. Here is a current link onAlieExpress: https://www.aliexpress.com/item/32956500815.html

Yes, that is how I have installed Magisk.

My results are the same as @Rob. S. No need to reflash either Magisk (used for SU only) or Gapps after OTA.

I checked the updater and the OTA package is slightly larger (749 MB) than the sideloaded one (707 MB), whatever that means. Maybe just the sideload plus the install executable?

Yeah, the semantics is off. What is switched is what recovery indicates is the running slot. I chose to make it a step that I always ended the install with a reboot to recovery so I wouldn't forget where I was. 😄

I don't know since I always just went ahead and reflahed Gapps and Magisk when I was sideloading because it was easy. But tdm indicated that you shouldn't need to in his instructions for LOS 16 (though he noted some said it didn't work). And why does both Gapps and Magisk persist after OTAs? Just asking questions because I'd like to learn.

All the Pro1 labeled fixes seem to be the keyboard stuff. https://download.lineageos.org/pro1/changes/

I'm guessing from your question that the answer to my previous question is that you are on the stock Android 9 the pro1 came with and not Lineage OS. In which case, you don't need to care what flashing is (in this context, sideloading an alternative version of the OS). It may be that all you have to do is hook up the new screen and it will be fine. If not, try a factory reset after you have installed the screen, Assuming you have the latest update to the Pro1 (dated Aug 2020, I believe), i would expect it to apply what is needed for the screen edges. The factory reset will, of course, era

I didn't notice it before, but I just checked my Moto G8 Power on Android 11 and it's there too. I suspect it's an Android 11 thing.

The first one looks like a weird variation of the phantom touch phenomenon. I can't reproduce either on my Pro1 with a screen that was replaced in January by FxTec (not a Alieexpress Elephone U Pro LCD) using that latest nightly of LOS. I tested the second video y swiping rapidly up and down on the settings menu. Different speeds, different amounts of pressure. Always rolled, never froze, no lag.

If you are using the same MindTheGapps and you have previously flashed it to both slots, it doesn't matter if you flash it or not as long as data hasn't been wiped. At least, that's what I think is going on (I'm not an expert).

Good point. I don't know, just ass-u-and-me-ed it was enough to have the update installed in stock. But I bet you are right, has to be actively flashed with a factory reset after the new lcd is installed.

Depends. Are you running stock or Lineage? If you are on stock and you have all the updates, there shouldn't be any problem. If you are on Lineage, your vest bet will be to go back to stock for the update and then return to Lineage.