Ok now flashed CAF version of pixel experience on my Poco F1 and no longer get issues with Android Auto with my Kia
Yes, indeed CAF roms seem to have no issue with AA, but unfortunately, at the moment they have limited personalisation options compared to the rest of roms... Personally, I've stuck to CRdroid since after trying all the rest it's the one that fits all my needs. In the meantime, I'm running AA fine by disabling hardware overlays, although still hoping a permanent fix can be implemented at some point...
Since it had been months with this issue not being resolved, I decided to switch to a CAF based rom and have had no problems with AA so far. Although they may lack the customisation AOSP roms provide, they seem more stable, and definitely worth the sacrifice if AA is important for your daily driving routine... Still, it's a real pity no Dev seems to care much about solving the problem on AOSP roms...
I had this issues also on my redmi note 4. Pixel experience and am older kernel solved it for me. So most of the AA problems are kernel related. I tried this also on my Poco. No problems with stock MIUI and stock kernel. I switched kernel and the problems begun. So I'm back to MIUI stock, because I use AA every day a much.
Awesome. i flashed the Citrus CAF and that works fine as well, just the notch is a little bit ****ty, need to look for other CAF images, on the first search in only found citrus
Whats CAF stand for?
thanks for the hint
michael
Stands for 'Code Aurora Forum'
Here's some more information: https://customroms.net/faq/caf-vs-aosp-los-roms/
There are only three CAF roms for the F1 at present, afaik. Citrus, Pixel Experience and Reloaded. Personally, I'm using Reloaded, since its got a few extras the other two lack. So far, running quite well and no issues. As mentioned previously, CAF roms aren't that customisable compared to Aosp roms, but Edxposed and GravityBox can give you some more options...
I want to configure macrdroid.to disable the hw overlays on developer settings but I need to know shall I disable the hw overlay on boot and leave it disabled always and it won't do any harm or won't make a battery drain ? or shall I disable it only on AA launching app and then enable the HW overlay oncr AA closes
I have it switched off all the time and have no issues. It's annoying though when I reboot my phone and forget to switch it off. It there no way to make it stick after a reboot by editing a certain file?
Don't know if it may be related, but if I had hw overlays off all the time, AA would not flicker but would get stuck in night mode permanently (or day mode, depending on your phones theme). On CAF, this doesn't happen, so again, don't know how far it's related... In any case, I'm guessing hw overlays are there for a reason, so having them off permanently may not influence daily usage, but sooner or later I guess somethings bound to crash or fail...
@shouk_1987 - Didn't want to clutter the CrDroid thread since the AA issue happens on all AOSP / LOS roms, not only that particular one...
To create a routine in Macrodroid, you have to purchase and install 'Secure Settings Pro' app from the Play Store and grant it root privileges. Once done, go to Macrodroid and create a new macro, and on trigger chose whatever you feel is convenient for you (in my case, I chose to have it triggered when my phone connected to my car's Bluetooth). Then, on 'Actions', chose 'Applications' and then 'Locale/Tasker Plugin'. On the popup that appears, select 'Secure Settings Pro', and then 'Root Actions'. Find 'Hardware Overlays', click it, and the set it to 'OFF'. Click the 3 dots at the top right and save. It will then take you back to Macrodroid; just save the macro and you should be done.
To automate enabling HW overlays again, you can follow the same process above by creating another macro, but in Secure Settings Pro / Root Actions / Hardware Overlays, set it to 'ON' instead.
Thanks bro I found the shell command back in 3rd page and it works both ways but I was thinking of the trigger
Is it on reboot or car connection so I believe it would be on car's bluetooth connex and to revert back to enable hw overlays again after BT disconnex by say 3 mnts
I have another fatal issue on aosp for dual sim data connex
I will try CAF as well and I am guessing reloaded is the best one
FYI, after a few days using Reloaded CAF rom, I noticed AA kept crashing once I unplugged the phone from the car. I had to open AA on the phone again and exit manually to get it to stop crashing. This worked sometimes, but others it wouldn't stop crashing until a full phone reboot was performed. I got fed up, and switched to PE rom CAF, even though it had less customisation. Haven't had the AA crash since, and as mentioned earlier, at least there's Edxposed and GravityBox to give you some options to customise the rom.
I am on crdroid aosp and using hw overlays option enabled on boot and all is fine
Is it OK like this ? and if it is theb why are you insisting on CAF with less customizations than AOSP ?
It's not exactly insistance. I don't want to sound disrespectful to any of the devs and I'm really thankful for all their hard work, but afaik none of them has tried to fix the problem, or even acknowledge it for that matter, and its been quite a few months now. I understand they have better things to do and maybe AA is not a priority, but in my particular case, I'm on the road close to 4 hours a day, thus a working AA is a must for me. Sure, there's the workaround to make it work on AOSP roms by disabling HW overlays, and it indeed can be automated, but I'm not sure if by doing this other functionality may be affected, although I must say I never experienced any wierd stuff going on while having them disabled. In any case, this solution is still just a temporary workaround and not a permanent fix, thus my quest to find a rom that has AA running out of the box, without having to take several more steps to either patch, tinker or modify system settings I'm unfamiliar with.
TBH, if it weren't for the release of Edxposed, I would have surely stuck with CRdroid, which was also the rom I was using for quite a while for its stability and customisation. Nevertheless, since I've now managed to tune PE CAF to my liking using GravityBox, and so far have had no issues, I guess I'll stick to it for now and see how things evolve...
@shouk_1987: I sent you a PM but can't seem to find it on my message list. Let me know if you got it, please... Thanks.
Since last unofficial update of lineage os I experience troubles with Android Auto again (no, deactivating HW-overlays doesn't fix this )
After a while the app seems to crash and restart just to crash again including media and navigation. Phone stays black for a while after that but goes back to normal eventually I think (usually I do I restart). It happens after just a couple of minutes of usage.
Currently using
lineage-16.0-20190509-UNOFFICIAL-beryllium
And
beryllium-9.5.9-9.0-vendor-firmware
I read here that another kernel might do the fix, any suggestions? Can I just flash an older one without using my data?
Any ideas?
Thank you
After a while the app seems to crash and restart just to crash again including media and navigation. Phone stays black for a while after that but goes back to normal eventually I think (usually I do I restart). It happens after just a couple of minutes of usage.
Currently using
lineage-16.0-20190509-UNOFFICIAL-beryllium
And
beryllium-9.5.9-9.0-vendor-firmware
I read here that another kernel might do the fix, any suggestions? Can I just flash an older one without using my data?
Any ideas?
Thank you
In my own personal experience, changing kernels on any LOS/AOSP roms didn't fix anything and the issue was still there no matter what. I finally gave up and started using a CAF based rom instead.
Also, AFAIK flashing a different kernel doesn't delete any of your data, unless you mean flashing a different vendor. If that's the case, doing so will indeed encrypt your data unless you flash DFE right afterwards...
I am currently on AOSP and using a magisk module that disable hw overlays on every boot and AA is working good
I used to do this via macrdroid but I gave up on macrodroid
I used to do this via macrdroid but I gave up on macrodroid
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone