Android Auto issues on Poco F1 Custom Roms

[Largamelion]

Installed LineageOS yesterday and on my drive home I experienced the flickering screen when disconnecting the phone. I have since disabled hardware overlays in developer settings and on the next two drives I had no more issues.

 

[mf76130]

At the moment i am testing the developer setting simulate secondary displays (its in the section drawing). When i enable it, whatever resolution, i get the menu visible, but it creates other problems, like after a radio restart not connecting AA back or phone stays black until a reboot.
Trying to fix this with Tasker, very nice app by the way
Which car radios do you use? i have the pioneer SPH-DAB230AB (7" WVGA-Touchscreen - so something around 8**x480)

 

[lukesan]

Hi,

I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.

Anyone else had this issue?

I'm using xiaomi.eu rom 9.1.17 beta

No issues on mine but you might try the following.. ---> App settings : 'Battery Saver' - set to 'no restrictions'... That's what kills the GPS reception on Waze after a couple of minutes. Normally if you have a car with a GPS module it should on keep working with Google maps since that one is able to use the car's hardware GPS so no need to set the battery saver on that one. (if you have a manufacturers navigation)

 

[krilok]

At the moment i am testing the developer setting simulate secondary displays (its in the section drawing). When i enable it, whatever resolution, i get the menu visible, but it creates other problems, like after a radio restart not connecting AA back or phone stays black until a reboot.
Trying to fix this with Tasker, very nice app by the way
Which car radios do you use? i have the pioneer SPH-DAB230AB (7" WVGA-Touchscreen - so something around 8**x480)

In my case, I'm using the built-in head-unit on a Kia Sportage, although not sure what it's resolution could be.

I'm no dev and my knowledge of how a custom rom is built is limited, but I've a hunch the problem is related to some 'driver' issue or incompatibility because of the phone's notched display. The fact that on MIUI stock Pie this has been fixed leads me to believe the problem points to the 'drivers' initially used when AOSP based roms started emerging, and if someone could revise and upgrade those drivers (or replace them with the ones used on current MIUI stock Pie), the issue could probably be fixed...

 

[mf76130]

In my case, I'm using the built-in head-unit on a Kia Sportage, although not sure what it's resolution could be.

I'm no dev and my knowledge of how a custom rom is built is limited, but I've a hunch the problem is related to some 'driver' issue or incompatibility because of the phone's notched display. The fact that on MIUI stock Pie this has been fixed leads me to believe the problem points to the 'drivers' initially used when AOSP based roms started emerging, and if someone could revise and upgrade those drivers (or replace them with the ones used on current MIUI stock Pie), the issue could probably be fixed...

On the stock rom i had also issues, AA was working, but i use the app "Podcast Addicted" and this sometimes struggles to play, on Custom Firmware and Original Firmware.
I am waiting for a new vendor firmware file

 

[krilok]

On the stock rom i had also issues, AA was working, but i use the app "Podcast Addicted" and this sometimes struggles to play, on Custom Firmware and Original Firmware.
I am waiting for a new vendor firmware file

My phone came with MIUI Oreo, and had the issues constantly. When it upgraded to MIUI Pie, I still had the issues, but a couple of minor updates later (some version dating to the end of December, if I remember correctly), the issue was not present anymore. Since then, I've switched to CRDroid, and although I've tried most custom AOSP roms and flashed latest vendor files on all, issue is still there, so I'm still thinking the fix is not in the vendor files at all and needs to be addressed at Rom base level...

 

[rn74]

No issues on mine but you might try the following.. ---> App settings : 'Battery Saver' - set to 'no restrictions'... That's what kills the GPS reception on Waze after a couple of minutes. Normally if you have a car with a GPS module it should on keep working with Google maps since that one is able to use the car's hardware GPS so no need to set the battery saver on that one. (if you have a manufacturers navigation)

thanks a lot, lukesan
this setting has solved my problem!

 

[JustinTrouble]

On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.

This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.

I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?

Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.

Hi! Mi 8 owner here.
I have exactly this on my Mi 8, so it's not just the F1. I'm running LineageOS and Syberia Project.
And I've seen a couple of other people mention it in the Mi 8 forums.
You're right about there being a lack of acknowledgment. I put this down to the popularity of Android Auto.

 

[krilok]

Hi! Mi 8 owner here.
I have exactly this on my Mi 8, so it's not just the F1. I'm running LineageOS and Syberia Project.
And I've seen a couple of other people mention it in the Mi 8 forums.
You're right about there being a lack of acknowledgment. I put this down to the popularity of Android Auto.

Yes, had read somewhere it happens on Mi8, too. Pity it seems there's no real interest in having it fixed definitely...

Have you tried disabling hardware overlays? Does it work for you?

 

[JustinTrouble]

Yes, had read somewhere it happens on Mi8, too. Pity it seems there's no real interest in having it fixed definitely...

Have you tried disabling hardware overlays? Does it work for you?

Yes, that fixes it for me.
Executing "service call SurfaceFlinger 1008 i32 1" in a shell as root also enables that setting. I've just setup Tasker to do it on boot.

 

[bartoloandre98]

New test build is awesome, works on fts too

 

[krilok]

New test build is awesome, works on fts too

???

 

[JustinTrouble]

I'm seeing the following errors in logcat on my Mi 8 when the screen is flickering:

01-29 17:13:37.164   704 12646 E SDM     : DRMAtomicReq::Commit: drmModeAtomicCommit failed with error 22
01-29 17:13:37.164   704 12646 E SDM     : HWDeviceDRM::AtomicCommit: AtomicCommit failed with error -22 crtc 111
01-29 17:13:37.164   704 12646 E SDM     : HWCDisplay::CommitLayerStack: Commit failed. Error = 11

 

[erindetti]

with rom citrus 5 CAF and CAF reloaded any android auto problem with my poco f1. all works fine .

 

[Tizio.Qualunque]

Thanks for your quick reply.
Happy to hear that it is generally working.
Not using dual Apps. Will try to flash a custom Rom in the next days

Did you disable the "miui optimizations" options in developer settings? If yes, re-enable them and reinstall android auto and Whatsapp will work

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------

with rom citrus 5 CAF and CAF reloaded any android auto problem with my poco f1. all works fine .

Using the phone or your car's headunit?

 

[erindetti]

Did you disable the "miui optimizations" options in developer settings? If yes, re-enable them and reinstall android auto and Whatsapp will work

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------



Using the phone or your car's headunit?

android auto car opel /mokka . with aamirror, aa_phenotype_patcher, and setting android auto.

 

[Tizio.Qualunque]

android auto car opel /mokka . with aamirror, aa_phenotype_patcher, and setting android auto.

Ok, so maybe the caf-based rom doesn't have this problem

 

[erindetti]

Ok, so maybe the caf-based rom doesn't have this problem

I speak about flickering problem , for what's app i don't know

 

[Tizio.Qualunque]

I speak about flickering problem , for what's app i don't know

Yes I know, i was talking about flickering problem too. The whatsapp issue was referred to @gella1992

 

[NeronLux]

Ok will try the caf version of Pixel experience and confirm