daniel.schaaaf

I am sure people tried their luck on the Pro1X. I just wanted to say that the app warns about having been built for an older Android version on LOS 17.1 (Android 10) too, and still works as intended.

Sorry to disappoint you, I own the older Pro1 model. I edited my posting accordingly. Maybe I misunderstood what I read in this thread. I got the impression that even for the Pro1 we would have to re-flash Android, and I was excited to see that the app was able to flash the display directly on a running LOS.

It's 2025, and I am going to necro the sh1t out of this thread because it confused me a lot ... but helped me getting the touchscreen on my replacement display for my Pro1 to work properly 😁 Essentially, Kaali said it all and provided the correct files. I uploaded translated and modified instructions as a PDF. I don't know why the instructions say to start the GTP Tools directly after installing it, because it just crashed since it can't access the hardware yet. The "fix" are the adb commands, which can also be performed in Termux (as SU) on the phone itself. Set SELinux permissive (

My Pro1 has problems with the "a" and "d" buttons. It doesn't feel quite like a hardware issue. More like the software sometimes swallow a character. Whenever I see an "a" or "d" missing, pressing either of these two buttons very lightly works the second time. I don't see anything suspicious in the logcat either. This might be the last straw for me and I am thinking about retiring my Pro1 ... with a sledge hammer. Yes, I am that disappointed! With the hardware keyboard having become unreliable, the phone is a nuisance to use. I hate the narrow screen with its curved edges.

You might want to get acquainted with XPrivacyLUA, which can restrict what information an app gets. E.g. my banking apps are not allowed to execute shell commands. When they ask "which su", XPL intercepts and replies "[empty]". This way the app does not know that it can't execute shell commands because it gets a valid reply from XPL, but the app won't see su either. The "only" problem is that you need ... Magisk with Riru and EdExposed or LSPosed. Down the rabbit hole, never to see the light of day again. Magisk reached its EOL, Riru is a mess, and Android (including LOS!) is getting more

Can sticky-shift be enabled/disabled somewhere in the settings? I never had sticky-shift on LOS 16 or 17, but would love to have this feature .

Just a small update: I had to make a new build because the first build of 17.1-20220303 was erroneously signed with test keys. If anyone installed a build with the test key instead of my own key, make sure to check "/data/system/packages.xml" and change test keys to my (JeBB) keys before you update (see instructions in the first posting). In case anyone is interested to learn a new language, here are some LOS build basics: http://www.trcompu.com/MySmartPhone/AndroidKitchen/Breakfast-Brunch-Lunch.html Don't brunch after mka ... otherwise you'll get a tummy ache ... I learned my lesson

Time for a new build. My old mirror raid needed some action. This time, I included some patches that @claude0001 backported to LOS16. I also made the touch screen margin control more granular, so you might want to check if the settings are to your liking. And, this build got rid of the Bluetooth file transfer MIME type restriction.

In case you have root, you can take a look at /sys/class/power_supply/... Just open any of the files inside the sub-directories of power_supply as text file to get an idea what it does. Some files can be read to get information about the hardware, like the battery voltage. Other files can be written to, to control the hardware. After some trial & error, you should have an idea which files are important to control the charging process. I guess this is also how ACC works. With apps like Automate or Tasker, you can run different scripts/commands to control the charge process i

I encountered similar difficulties previously, not only with banking apps but also others like Sygic. These apps store a fingerprint of your system in their settings. Installing a new system is likely to change the Android ID or other information. One way to avoid trouble is to block sensitive information with XPrivacyLua. But not by letting XPL return random information back to an app. Some hook definitions, built in or downloaded, allow the user to store custom fixed values. Be warned though, figuring out what information an app uses to identify users can be a lengthy and cumbersome pro

No, I didn't find a workaround ... but I also stopped looking after a while Disabling the signature check in Windows did work, the driver installed correctly, but fastboot still refused to do more than list my device. I have no idea what else could be wrong and just hope that I never have to use fastboot ...

Long time no see 😁 I uploaded a new build 💩 Is there a way to "bump" this thread when I edit the first posting? Or do I have to reply to the thread each time I want to make people aware of a new build?

Will changes to 18.1 automatically integrate into the 17.1 code? I still have to figure out how to use Gerrit and apply patches and all that ... if I ever find the time to do so ...

SD-cards are still working in Android 11. The difference is that apps are forced to use Scoped Storage exclusively. From November 2021, targeting Android 10 to circumvent the Scoped Storage API will be forbidden. This means that direct file access is impossible. Every file access has to be routed through Scoped Storage. The point is to prevent apps from accessing data on the SD-card they are not supposed to access. And it is supposed to reduce clutter. So, instead of using an appropriate file system for SD-cards (like F2FS or ext4 without journaling), Google introduced a high level "file

Sure, its their choice. And I fully understand that Lineage is not in the position to lead Android development and force Google to adapt. Still, I feel like this is the end of the road for me. (Edit: And I am very thankful for the work everyone has done with LineageOS! Lineage is clearly the better Android, and they rescued countless devices from an early obsolescence.) (Warning: Old-man-rant approaching!) Google's choice to develop Android the way they did made sense, back in the olden days. But they quickly gained marked shares, followed by absolute power. Despite that, they contin