Latest update of Pixel Experience broke Android Auto. I'm a curse I believe as any rom I try, AA doesn't work. Now, I'll try NOS as recommended by fellow xda member. If it doesn't work in NOS too, I'm going back to crappy MIUI. Wish me luck ?
I was in the same situation you are, trying all roms and having to go back to Pie all the time. I installed NOS just to test it when it was released, and AA didn't work at first, but I made a comment on the roms thread, the friendly Dev there looked it up, and on his following update AA was finally fixed... ?Latest update of Pixel Experience broke Android Auto. I'm a curse I believe as any rom I try, AA doesn't work. Now, I'll try NOS as recommended by fellow xda member. If it doesn't work in NOS too, I'm going back to crappy MIUI. Wish me luck ?
Yes, you're right. Finally AA is working with NOS. Performance isn't that great as compared to PE and Havoc but I'll manage. Installed Ben's thermals to improve performance. Thank you again for this suggestion. I was on urge to go back to MIUI which I hate to the core.I was in the same situation you are, trying all roms and having to go back to Pie all the time. I installed NOS just to test it when it was released, and AA didn't work at first, but I made a comment on the roms thread, the friendly Dev there looked it up, and on his following update AA was finally fixed...
At present, AFAIK the only Q rom that has a fully working and stable AA is Nitrogen OS...In my case, Everytime when I connect, stop working and reboot the phone...I'm using evolution x custom rom
New update of Evo X today, in changelog it says AA has been fixed. I've not tried yet. I'm using NOS.In my case, Everytime when I connect, stop working and reboot the phone...I'm using evolution x custom rom
New update of Evo X today, in changelog it says AA has been fixed. I've not tried yet. I'm using NOS.
// Changelogs //
Device:-
- Updated blobs from miui v11.0.6
- Fixed Android Auto
- Fixed issues with type-c headphones
- Removed inbuilt firmware (Have to flash seperately from now on)
- Built with clang 11
- Fixed 5ghz hotspot
- Misc changes
Give NOS a shot... You won't be disappointed... ?Havoc-OS-v3.3-20200317-beryllium-Official-GApps also doesn't work. Oh well, back to LOS 16.0, where AA works great.
Thanks, I've noticed you like itGive NOS a shot... You won't be disappointed...
It's the only Q rom on which AA works without hiccups, and this is essential for my daily routine. On any of the other roms I've tried on which AA fails, I've made sure to comment and point out the issue on its respective thread, but either have been totally ignored, replied with "I don't have a car to test on", or have had no real interest from the devs to implement a fix. Also, this is a problem that still persists on Pie roms too, so we're talking over a year now and seems nobody really cares (although on Pie you could disable hardware overlays as a temporary fix)...Thanks, I've noticed you like it
BTW, NOS has a new test build up today.
https://drive.google.com/uc?id=1U2BRVVkGMUDsbXA7wQjRRQVU0XRukihf&export=download
Just tried this in my car, all seems to work as advertised.
So if I understand correctly, LOS 17.1 does not support AA, even with HW-overlays disabled? That would be a real bummer as I'm planning to upgrade to it as soon as it becomes official (which should happen soon). AA not working would be a definite showstopper though, I use it every day ('cept now because our country is in lockdown).It's the only Q rom on which AA works without hiccups, and this is essential for my daily routine. On any of the other roms I've tried on which AA fails, I've made sure to comment and point out the issue on its respective thread, but either have been totally ignored, replied with "I don't have a car to test on", or have had no real interest from the devs to implement a fix. Also, this is a problem that still persists on Pie roms too, so we're talking over a year now and seems nobody really cares (although on Pie you could disable hardware overlays as a temporary fix)...
Don't get me wrong, I mean no disrespect to any other dev who I know puts in countless hours and great efforts to build any of these roms, but so far the NOS dev is the only one who's bothered to figure out the problem and fix it for us. If AA gets fixed on other roms sometime, I'll certainly try them out, but so far this doesn't seem like something that's going to happen anytime soon...
AA on LOS 17.1 didn't work for me last time I tried, about 2 months ago. Besides LOS, I've also tried the following Q roms:So if I understand correctly, LOS 17.1 does not support AA, even with HW-overlays disabled? That would be a real bummer as I'm planning to upgrade to it as soon as it becomes official (which should happen soon). AA not working would be a definite showstopper though, I use it every day ('cept now because our country is in lockdown).
UPDATE - Nitrogen OS worked like a breeze. Also just decided to try the Pixel Rom. Current changelog states that a fix has been applied, but my screen still flickers away.Alright so thought I would share what I got to work so far. just note, I haven' t disabled hardware overlays in any of these roms, they were all used without any tinkering. My head unit is the JVC KWM740BT
What I have conducted ~
LOS 16 (9.0), back around its initial release (screen flickering issues)..
Pixel Experience (9.0), ran like a dream,
LOS 16 (9.0), tried again, worked okay, got bored of the rom.
Evolution X (9.0), ran okay, but the rom was unstable for me (bootloop)
LOS 17 (10) didn't work, had screen flickering issues.
Pixel Experience (10), ran just like 9.0
Havoc OS (10), currently on this rom, and am having issues with the device connecting, and when it does the phone freezes, aswell as the headunit resulting in a force reboot of the phone
Am about to try Nitrogen OS (as recommended), see how stable that is for me.
Just use tasker with a script on boot to disable hw overlay. Working fine.Just tried AA on LOS 17.1 for the Poco F1 and it works fine as long as you disable HW-overlays. The flickering of my phone's screen even stopped immediately after I disabled it and remained fine.
Unfortunately the Magisk module to automatically disable HW-overlays after a reboot does not seem to work on Android 10. I hope a V3 will be released with support for Android 10.