Hook

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.

Elephone U pro is correct.

Here is a guide I made for myself, edited from @tdm's original instructions. It is a little simpler because it assumes you have USB working and all the fastboot/adb stuff installed, and that you know where to get everything. It focuses more on just the actual flashing, showing both first time and updates. Since I made these instructions for me, they don't include what to do with Magisk other than flashing the zip, since that is all that is needed for SU. It may be useful for some in combination with @Slion's wonderfully detailed instructions of all the steps with all those many helpful lin

I don't play Mario Kart, but I'm not seeing any sort of delay on my touchscreen. Responsive and snappy as always.

Just curious. I'm not able to completely follow all of this, but is there anything being proposed here that would allow the / and ? to be remapped off of the P and L keys, maybe to right_fn and shift-right_fn? (because that is a more normal qwerty keyboard position for those symbols).

I know that isn't your only reason, but for others, if you sideload Magisk as a zip, it pretty much works as AddonSU did. Gives you root, doesn't require Magisk Manager (although it does install it—I ignore it), doesn't require any bootloader dance. It just gives root to the apps you grant root access to. Acts just like AddonSU for me. With Magisk 23.0, you have toe rename the apk to zip to flash it. And this install method is allegedly depreciated, but it works fine.

Wow, I hadn't even noticed that the F-logo key was now indeed working as the search key with the Android keyboard short-cuts. Thanks. I also (though I may not be interpreting correctly) would hate to see any keyboard feature be exclusive to the launcher as I always use different launchers. As long as I'm interrupting. thanks to all of you working on this. Most of the current keyboard conversations going on are way over my head, but I'm sure I'll benefit in the long run from what you folks accomplish @Sean McCreary, @Slion, @VaZso, @Rob. S., @EskeRahn Thanks!

This is just weird. I tested it just before I posted before I a swear it was working. But closer examination seems to show a highly varied response of different apps in terms of a) whether they autocapitalize, b) whether they follow the soft keyboarsd setting and c) whether they offer a control of their own for Autocapitalization. This is all in terms of what the hardware keyboard does in the case of having the AOSP soft keyboard with the Autocapitalization setting. Aquamail, based on K-9 , ignores the setting and always Autocapitalizes, as does Google messages. The Browser Fulguris ignor

Again, as far as I can tell, this is controlled by the the soft keyboard. AOSP keyboard has sticky shift (but no setting for it) but it does have an autocapitilization toggle. If you turn it off in the soft keyboard, the hardware keyboard no longer does it.

Sadly, this is the problem with jerry-rigged solutions and putting the Pro1 on Verizon is jerry-rigging (the mule SIM which fools the network into thinking the Pro1 is a different phone). Jerry-rigged solutions break. I had my Pro1 working on Verizon on stock for three months and it broke. Later, on LOS 18.1 I got it working again, but I didn't like the anxiety of knowing it could (and probably would) break again. This led me to a solution most people don't like but I have come to love. I have a (relatively) cheap Moto G8 Power as my phone, car phone (Android Auto) and out in the world com

I think we are saying the same thing. Maybe I wasn't clear-- I do not always have the terminology right. All I was saying is that, if recovery is showing you are on partition a: and you adb sideload the update, it still shows partition a: You then have to reboot to recovery and it shows you are now on partition b: Wnat actually accomplishes the change in partition is magic to a noob like me. 😄 And yes, reboot to recovery is not needed after Magisk and Gapps.

I obviously don't build LOS, but I've never had a problem with Gapps showing up when sideloading LOS via ADB. I have always used @tdm instructions, as mentioned by @EskeRahn. I adb sideload the latest LOS nightly, then reboot to recovery, which changes you from the a/b partition you were on to the other a/b partion where the update was installed. Then I adb sideload Magisk and Gapps (in that order, if it makes a difference-- I don't think it does).

Sticky shift (and super-sticky-shift) work fine here on 18.1, using AOSP as soft keyboard as @claude0001 indicated.

I switched my keyboard to US International and it seems to work for me.

See this thread:

Using English(US) layout, it does (except with software that takes over the keyboard like Softmaker Office).

I hope you are half pulling our leg about the swelled battery for years and the external cooling fan. Lol I'm not sure how Verizon will handle you if you are grandfathered in on an old plan. The Pro1 will work on Verizon following the instructions in this thread. https://community.fxtec.com/topic/2133-fxtec-on-verizon/page/5/?tab=comments#comment-41839 But this method requires that you have a Verizon SIM that has been activated in an approved phone with VoLTE. If you have that, you should be fine. But there is no way to know for sure in advance. I chose to have a sepa

Again, if it makes a difference, I never have used Trebuchet. I use Nova sometimes and Launch Time sometimes (can't make up my mind which I like better because, since I rarely use my Pro1 in portrait, it really doesn't make much difference)

For what it's worth, I never have auto-rotate turned on. That allows me to occasionally use rotate lock (the little weird icon that mysteriously pops up in the nav bar-- though it may pop up without the nav bar) to get specific rotation effects. I use it to lock Kindle in portrait while I have keyboard out as a handle for easier holding while reading... Kindle in landscape sucks! 😉 I never have trouble with apps not going into landscape when keyboard is out unless the app just doesn't do landscape at all and the auto rotate doesn't help. I've always kept autorotate off on all my phone