Jump to content

Benni

Members
  • Content Count

    179
  • Joined

  • Last visited

  • Days Won

    2

Benni last won the day on January 12

Benni had the most liked content!

Community Reputation

191 Excellent

About Benni

  • Rank
    Pro¹ (Android), Pro¹ X (Android (reserve, rooted))

Recent Profile Visitors

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

  1. Android Auto worked two out of two times for me with todays update.
  2. It stopped working again. Let's hope for a Lineage, or app update. Other phones seem to have the same issue: https://www.reddit.com/r/LineageOS/comments/1i2hi9y/android_auto_broken_after_update_from_los_21_to/
  3. I found this thread. They recommend a specific cable, or an AA Wireless dongle. Maybe worth to try.
  4. Update: I got it working again (for now) by re-installing the Android Auto app using the playstore. Warning I lost all my settings this way, so maybe try clearing cache first. @CornholioGSM
  5. Somewhat off topic, but I can confirm that Android Auto via cable is broken for me on official lineage 22.1 Pro1X and a Mercedes Car. Was working before the upgrade.
  6. I needed to switch back to the old slot because bluetooth audio was broken for me. Both media and calls.
  7. Yes, it makes the app believe that the phone is not rooted
  8. You can try the following commands (from telegram) to get the camera working: Just executed two commands and voila: camera works again $ adb shell setprop vendor.debug.camera.eisv3enable 1 $ adb shell killall -9 [email protected]_64 I had even transport apps simply crash (on opening the account/tickets view) when the safety net check failed.
  9. No idea how it works with microG, sorry. Also not my mod, I'm just a user.
  10. I'm pretty sure you need to pass safetynet/play integrity for banking apps. I do that using: * MagiskHide Props Config - with the stock fingerprint (config in attachment) * Univarsal SafetyNet Fix * Blacklist in Magisk printslist
  11. It's simply applying a device policy, I don't think there's anything to maintain 🙂
  12. With this tool, it is possible to disable the fingerprint reader for unlocking the phone. https://f-droid.org/de/packages/com.davidshewitt.admincontrol/ But that probably won't help your case. Maybe you can remap the "fingerprint" button e.g. using https://f-droid.org/de/packages/io.github.sds100.keymapper/?
  13. I can't reproduce this in firefox, lineage-20.0-20230504, with stored fingerprints.
  14. I would also recommend to verify the sha265 checksum of the downloaded lineage zip. You can find it next to the download button.
  15. I can confirm the "broken" offline charging on Pro1 and Pro1x with the most recent Lineage.
×
×
  • Create New...

Important Information

Terms