daniel.schaaaf

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

Google and Lineage are going the wrong way, making things too "secure" and "fool proof". Root and SD-cards are a good example of the things the future won't hold. I feel that power-users have to bend over backwards to use their devices the way they want. So that's what I did. I bent over backwards ... and gave birth to an old-timer 🤰👴 😁

Changelog 20211025: New build with Android security patch level 05.10.2021. No other changes.

Beloved community, here it is: Another up-to-date outdated ROM to satisfy your custom ROM fetish. LineageOS 17.1 JeBB "A noble spirit embiggens the smallest man!" is (so far) a slightly modified build that will be updated in irregular intervals. Future builds may contain additional fixes, or I may attempt to fix things with a Magisk module ... "may" is the important word here 😉 This build can be installed from scratch like any LineageOS build (LineageOS Wiki). Dirty-flashing from the last official LineageOS 17.1 is possible, but the official signature keys have to be exch

Sounds like there may be something blocking the microphone opening, like adhesive tape to hold the microphone or loudspeaker in place? I am afraid we have to live with a smartphone that fails in ... being a phone. Anything sound related is "not satisfactory". I am also afraid nothing, like audio circuit configuration files, will be fixed by fxtec themselves :-(

I did, and I appreciate(d) your instructions :-). Although I don't quite get why fxtec doesn't provide a signed driver ... Anyways, I only got fastboot to detect my phone. Any other command besides "fastboot devices" failed on Windows and Ubuntu, and all USB ports (four ports provided by four different controllers on my mainboard). Flashing boot.img (to boot, boot_a or boot_b) failed either because fastboot claimed the boot partition was too small, or because the phone stopped responding or rebooted. ADB worked without any problems.

My custom 17.1 installed just fine (from the official LOS17.1 recovery) ... to my own surprise. Flashing my boot.img failed because I can't get fastboot to cooperate on my PC (Windows 10 and Ubuntu).

I removed the camera protector with a thin steel prying tool like this one: There's no need to disassemble the phone. It did not quite fix my problem, but it got better. Now that the sun is out, I am unsure whether removing the adhesive tape made it better, or whether it was moving the camera a little with a tooth pick. I attached a picture that I resized slightly. The focus was on the birch tree. The background is still out of focus. But it is better than it was before, when anything further away than 50 cm would be blurry. I tried the manual focus in Open Camera. T

I think I managed to fix mine ... or make it less crappy ... 🙂 When I removed the protective cover, I noticed that the double sided adhesive tape overlapped with the camera cut-out. We are talking 0.5 mm here, but it might have been enough to restrict the lens from moving. On the picture, I already moved the lower part out of the way. I ended up removing the adhesive completely ...

In case you have root, you can take a look at /sys/class/power_supply/... For my Moto Z Play, I made an Automate Flow (script) to read and write to certain files (e.g. in /sys/class/power_supply/usb/) to control charging speed, stop charging at 85%, and even prevent apps like the Play Store to detect that the phone was charging. I did not have the time yet to make a script for the Pro1, so I can't tell which subdirectory in /sys/class/power_supply/ controls charging... /sys is a virtual file system connected to the kernel. You can open files under /sys (as text files) to get informat

I intend to stick with LOS 17.1. Building wasn't difficult, but I am afraid to install my build and mess up due to signature issues. I hate not having TWRP :-( Anyways, I plan to try my luck within a few weeks. If the update from the official LOS 17.1 to my own build works out alright, I will publish this new build here and on XDA.

It also matters which USB port you use. I guess that some USB controllers ICs are more finicky than others. My current mainboard has 19 USB ports provided by three different controllers, and I had to try different ports for various phones/tablets to work with fastboot. Apparently, USB is not as universal as the name implies :-)

The author of "Folder Music Player (Pro)" was/is struggling with the storage access framework of Android 11 as well. Apparently, it offers "horrible file access performance". As I said before, Google is going the Apple way ... slowly but surely :-(

It doesn't stop at "potentially disruptive", Google makes Android safer and more secure with every new version. Unfortunately they also make Android more restrictive for power-users and they gradually "encourage" users to stay away from SD-cards. At the same time, Android 11 doesn't look or feel much different from Android 4. At least not when you are used to tweaking the OS with GravityBox and custom launchers. I f-ing hate that everything is being developed in a haste. There is no time to settle on anything stable and work out the kinks. There has to be a brand new product on the marked