Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Hook

  1. 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
  2. oh, quick question before I go to bed. Is there an R boot image/recovery?
  3. Thanks so much, @tdm Can't wait to try this out in the morning! 😎
  4. 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.
  5. That looks correct. Here is a current link onAlieExpress: https://www.aliexpress.com/item/32956500815.html
  6. Yes, that is how I have installed Magisk.
  7. My results are the same as @Rob. S. No need to reflash either Magisk (used for SU only) or Gapps after OTA.
  8. 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?
  9. 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. 😄
  10. 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.
  11. All the Pro1 labeled fixes seem to be the keyboard stuff. https://download.lineageos.org/pro1/changes/
  12. 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
  13. 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.
  14. 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.
  15. 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).
  16. 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.
  17. 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.
  18. 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
  19. I don't play Mario Kart, but I'm not seeing any sort of delay on my touchscreen. Responsive and snappy as always.
  20. 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).
  21. 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.
  22. 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!
  23. 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
  24. 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.
  • Create New...

Important Information