I think I had something similar. For me, it had something to do with Android Auto permissions. I reinstalled that app, gave all permisions and then it worked.I haven't seen this posted anywhere on here, so I don't know if anyone else is having this issue, but I am unable to get Android Auto to output audio when connected via USB (my vehicle doesn't support wireless). Oddly enough, when I plug in my phone, it firsts starts playing through phone speakers, then stops all together. The radio shows that it's playing (song's time progresses), but nothing.
Model: HD1907 (Internationally modified TMo variant)
GApps: MindTheGapps (MindTheGapps-11.0.0-arm64-20210412_124247)
I was going to try and re-flash using OpenGApps, but wanted to see if anyone had any experience, or I'm just out of luck.
EDIT: I've tried OpenGApps, both Pico and Nano, and neither would even launch Android Auto when plugged in, and I am unable to get FlameGApps to load, gives an error "failed to mount/detect system"
You don't understand how it works, even if you went back to the latest OOS *you* wouldn't get L1. Only some flagged devices will get it (and only if they pass one more requirement) :^)
so the only way is msm tool to restore drm keys right? update to oos11 after try go to los again i thought maybe we have a way we didnt need to wipe.
Your DRM keys are still there, you just can't use them on anything but locked stock...unless you're lucky enough to have /unlocked/ keybox programmed with L1 keys just like lucky individuals who claim that OOS update magically restored their L1 ^^
i was one of these lucky guys in oos10 after upgraded to oos11 and stay on l3 i need try again when i need netflix or others things you need l1 kkkkk
Same here, survived reflashing back to 7/18 release and now fingerprint sensor works to unlock again.
I'm experiencing the same problem. I've attached a log file, and will be happy to help gather further info if needed.
Hmm. I very vaguely remember running into something similar a few years back. I believe what ended up being the fix for me was to go back to 100% stock (use the MSM tool to flash stock everything), then start the process fresh. If memory serves, it ended up being a nonstandard partition that was being missed by all the other install methods. This got everything back to where it needed to be, and I had no issues after.
IT WORKED! THANK YOU SO MUCH!!!!!!!!Hmm. I very vaguely remember running into something similar a few years back. I believe what ended up being the fix for me was to go back to 100% stock (use the MSM tool to flash stock everything), then start the process fresh. If memory serves, it ended up being a nonstandard partition that was being missed by all the other install methods. This got everything back to where it needed to be, and I had no issues after.
I'm having an issue after flashing. Everything works awesome until I try to call someone. I can hear them but all they hear is a high pitch tone. Plus it seems like i can hear what I say echoed back at me from the speaker. Any assistance you can provide would be appreciated.
Flash retail firmware and mic will work fine. See: https://gitlab.com/LineageOS/issues/android/-/issues/3933
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
for installing magisk, I always follow the following:Magisk canary