Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


daniel.schaaaf last won the day on October 26 2021

daniel.schaaaf had the most liked content!

Community Reputation

172 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. 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
  3. 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 ...
  4. 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?
  5. 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 ...
  6. 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
  7. 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
  8. 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 🤰👴 😁
  9. Changelog 20211025: New build with Android security patch level 05.10.2021. No other changes.
  10. 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) an unmodified 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 exchanged
  11. 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 :-(
  12. 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.
  13. 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).
  14. 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
  15. 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 ...
  • Create New...

Important Information