Leaderboard

lineage-20.0-20230213-nightly-pro1-signed installed smoothly over OTA. Still January 5th security patch. I discovered after that I no longer had root, but since I don't actually use root very often, I don't know if it was this OTA that undid it. I reflashed Magisk V25 as a zip and all went well. V25 does make you jump through a few more hoops than older versions did when you use this depreciated method. It does make you download and update the app, during which it does the whatever with the boot stuff. But it's easy and painless. I only use it to give superuser permissions-- it use

Thanks for all the Lineage work that is being done. Is this work, in the end, going towards the indiegogo 'pro1x with lineage' phone? I am still patiently waiting for one since my pledge there, quite a few moons ago. Thanks again for all the work.

S/N fxtec007110 on the sticker. Qwerty. Queue jumper off Expansys, received November. Sunny Tauranga NZ, now that the cyclone has passed through.

I don't expect to see the money this year. I will be surprised if I get it next year. Don't get me wrong, love my Pro1, but at this point other than their good intentions, I have doubts that they have the capability to living up to expectations or promises. I mean, these are good guys. I truly believe that. But they are so far over their heads.

Yeah, I had seen that one. And I've already picked it up in my lineage-16.0 ROM for Pro1. 🙂 Thanks for coming up with this simple but effective solution! Those two lines of code may have their place with a HW keyboard that has no caps-lock. But with the Pro1/Pro1X, omitting them certainly improves intuitive use! For me this "compromise" is perfect as, apart from the "double-shift = caps lock"-behaviour, I actually like the features of an ALPHA keyboard.

The general idea is for Settings to set a global value, and and a modified KeyCharacterMap.java to check that value instead of depending on the .kcm files. The negative reviews are about the various possible ways to do this: a setting, a system property, etc. An instance variable isn't usable for this as each app gets a different instance of the KeyCharacterMap object, so there's no way to use a method in the class itself and have the change take effect in all instances. The normal way to do this is to add a new setting in LineageOS' SDK, but unfortunately the SDK can't be linked against the c

Not sure if I will include it in the end, but as the option of switching between "full" and "alpha" has been requested several times, I would be quite interested in how you would have implemented that. Otherwise, disabling the "double shift = caps" function seems like a very good idea and a good compromise between both worlds. First time I accidentally triggered that mode, it drove me nuts, and I was pretty harsh toward that poor, innocent caps key ... 😳

OK I think I've calmed down enough to finish this story First off they managed to lose the jpegs I sent them, so I resent them Then they said I needed to return the phone, which I did & they confirmed receipt a week after the post office said it had been delivered Several emails & nearly 3 months later I received an update on Pro1-X shipping & was assured the USB module would be included in that shipment Eventually, my partner managed to track down one of the directors on LinkedIn & we told them the tale of woe so far & threatened them with legal action