S10 /Lineage os 18.1/AA Issues connecting to Car - Android Auto General

Hi All,
Im have a S10 running Linux4's unofficial Lineage os 18.1 and I cannot seem to get the AA to connect to the car (Mazda 2021) .
The app runs on the phone, but when plugged in the infotainment system says it cannot connect to android auto.
Ive tried a bunch of different roms, all have the same outcome, i've tried the downgrade to 6.3 (Android Auto 6.3.611314) but that still produces the same error.
Ive installed magisk to run AA AIO toolbox, but that crashes once you click the I understand button (it gets SU) .
Is there anything im missing? Where can I see the error log?
If I go back to stock AA starts working again, but I lose lineage which would suck.

Related

Bluetooth crashes OP3T on newest LineageOS builds

Hi,
with the newest builds of LineageOS for the OnePlus 3T im facing similar problems like in this post here ...
https://forum.xda-developers.com/oneplus-3t/help/lineage-os-bluetooth-crashing-op3t-t3561225
This applies both for the 20/03 and the 24/03 build. When I enter the settings and go to the Bluetooth section and there enable BT, the phone becomes unresponsive for some time and then reboots. What I found out is that if I enable BT via the status bar shortcut, everything is fine and my previously connected device (gear s2) reconnects stable. But if I then enter the settings and just click on the BT section entry, same story again, phone becomes unresponsive and then reboots. I flashed the ROM and then the OOS Firmware 4.1.0. Phone is rooted with SuperSU.
Have you tried a clean flash?
not yet. just dirty flashing with wipe cache and dalvik so far. i guess I'll give it a try then.
greg1977 said:
not yet. just dirty flashing with wipe cache and dalvik so far. i guess I'll give it a try then.
Click to expand...
Click to collapse
Report back with results plz
sakumaxp said:
Report back with results plz
Click to expand...
Click to collapse
I don't know what did the trick now but this is what I was trying...
I cleaned the cache + data of the Bluetooth system app and reinstalled BusyBox, then rebooted. The problem seems to be gone, no more crashes and freezing OS. Will leave it like this for me now. Just wanted to let you know as I don't seem to be the only one with this issue.
greg1977 said:
I don't know what did the trick now but this is what I was trying...
I cleaned the cache + data of the Bluetooth system app and reinstalled BusyBox, then rebooted. The problem seems to be gone, no more crashes and freezing OS. Will leave it like this for me now. Just wanted to let you know as I don't seem to be the only one with this issue.
Click to expand...
Click to collapse
All,
just wanted to give an update on this topic and hope for a solution
As the problem was coming back I decided to go for a full wipe and clean flash of the latest LineageOS version for the OnePlus 3T from this thread here: https://forum.xda-developers.com/oneplus-3t/development/rom-lineageos-14-1-t3547024
After I restored my apps I activated Bluetooth on the device and flawlessly connected my Smartwatch, a Gear S2. All good, all fine, all working.
AFTER that, when entering Settings => Bluetooth on the OP3T, there are 2 possible scenarios:
1) No other Bluetooth devices are around and emitting, the search stops after a few seconds saying that "no other BT devices are detected" ... makes sense.
2) There are other Bluetooth devices around and emitting, and based on my experience only one device is sufficient. The search goes on and on and on, after a while the screen freezes, and then the phone warm resets.
I was able to reproduce this inside my car when I tried to connect to the car audio system and also with my Bluetooth headset. Devices turned off => scenario 1, devices turned on and ready to connect => scenario 2.
Any idea here?

Honor 7 lite [honor 5c] stuck on Emui 4.1.2 NEM-L21

Wassup, I have a small problem, rather a big one.
I'm still stuck at NEM-L21C43B131 update, Emui 4.2.1, which is from 1 december 2016 I've read that I should have gotten nougat but I cannot recieve any updates, I've tried using HiSuite, Firmware finder on both PC and on the Phone, Proxy, DNS, and regular dload method. NONE HAVE WORKED.
I even contacted the huawei support and they said there are tons of firmware updates and I should have gotten them and they will maybe send out an firmware to me. (Not gotten it so dead end there)
I tried unlocking the bootloader, installed twrp to get a custom ROM, LineageOS 14.1 doesn't want to install due to Error 7, I tried to install Elite TWRP but the phone don't want to boot into it, so I tried using regular TWRP to install Elite ROM, it does install but doesn't exist which makes no sense whatsoever.
TWRP 3.1.1.0 is the only one that works, the rest just doesn't work.
I have even tried using Meticulus LineageOS for EMUI 4.X, but either I get encrypted password on it or error 7.
So I don't know what to do at this point, I heard android 7 fixes alot of bugs like RAM usage for honor 5C, and thats all I care about since the phone keeps crashing due to an app or freezing all togheter for 15-20 minutes and then reboots. (OR REALLY SUPER SLOW)
Factory resetted the phone about 30 times at this point.
If anyone got an idea I'm open to ears and eyes :good:
Thanks!

[HELP] My phone won't find my bluetooth headset

i had my galaxy j7 prime on android 8.1 and i decided to flash it, first i installed LineageOS and the problem started there, my phone stopped finding my headset, i thought that the problem was the rom so i ended up installing revolutionOS but the problem persisted, then i gave up and decided to get back to a stock firmware so i downloaded a rom for 7.0 wich i found on this forum and... nothing it still don't work
My bluetooth can find others phones and my headset is still found by other devices
what can i do?
soly23 said:
i had my galaxy j7 prime on android 8.1 and i decided to flash it, first i installed LineageOS and the problem started there, my phone stopped finding my headset, i thought that the problem was the rom so i ended up installing revolutionOS but the problem persisted, then i gave up and decided to get back to a stock firmware so i downloaded a rom for 7.0 wich i found on this forum and... nothing it still don't work
My bluetooth can find others phones and my headset is still found by other devices
what can i do?
Click to expand...
Click to collapse
Try install oxygen kernel first
Or
Your bluetooth device have a problem
Or
Missing some libaries on /system/lib
soly23 said:
i had my galaxy j7 prime on android 8.1 and i decided to flash it, first i installed LineageOS and the problem started there, my phone stopped finding my headset, i thought that the problem was the rom so i ended up installing revolutionOS but the problem persisted, then i gave up and decided to get back to a stock firmware so i downloaded a rom for 7.0 wich i found on this forum and... nothing it still don't work
My bluetooth can find others phones and my headset is still found by other devices
what can i do?
Click to expand...
Click to collapse
If your bluetooth device doesnt have any problem,flash correctly latest oreo firmware for your model through odin and check

[Help] AA mirror works but without Touch

Google play service 15.0.90
Android auto 3.6 all the way to 4.0 nothing worked.
Phone Samsung j6+
Magisk superuser is checked and I tried deactivating it and activating it again' rebooted, but does not support touch on my head unit.
Thanks in Advance !
Same problem!
Did you solve?
Same here!
Having the same issue with AA Stream, Stream2Auto, and AA Mirror. It was previously working fine.
Just tried putting AAMirror and Screen2Auto on my old phone (Le Max2) and it works just fine.
Android 9 - RevengeOS
AAuto: 5.1.500664-release
On my newer phone (Pixel 3a XL) it still does not work running the following:
Android 10
AAuto: 5.3.501644-release
Both phones are fresh installs of Android OS

Question Android Auto -- MIUI 12.5.4

Has any got the AA to work successfully?
Phone : Note 10 Pro Indian Variant (M2101k6P)
OS : MIUI 12.5.4.0 (RKFINXM)
Cable is connected to the phone but android auto does not detect it. Below are the steps i have taken
New phone, Setup afresh ( No old Data was copied)
Have tried 3 different cables.
Uninstalled AA updates, restart and reinstalled them.
Default USB configuration ( tried with all the options PTP,No Data Transfer,MIDI,File Transfer)
None of the apps are setup for Dual app.
Have AA Screen for phone installed.
Unknown Sources is checked in the Developer options of AA
Initially when i connected the phone for the first time, i saw a message "Unsupported device" , default USB was set to file transfer at this time.
After that neither the message pops up nor AA works.
Any other steps that will resolve the issue?
Thanks
letscheckitout said:
Has any got the AA to work successfully?
Phone : Note 10 Pro Indian Variant (M2101k6P)
OS : MIUI 12.5.4.0 (RKFINXM)
Cable is connected to the phone but android auto does not detect it. Below are the steps i have taken
New phone, Setup afresh ( No old Data was copied)
Have tried 3 different cables.
Uninstalled AA updates, restart and reinstalled them.
Default USB configuration ( tried with all the options PTP,No Data Transfer,MIDI,File Transfer)
None of the apps are setup for Dual app.
Have AA Screen for phone installed.
Unknown Sources is checked in the Developer options of AA
Initially when i connected the phone for the first time, i saw a message "Unsupported device" , default USB was set to file transfer at this time.
After that neither the message pops up nor AA works.
Any other steps that will resolve the issue?
Thanks
Click to expand...
Click to collapse
Any one ? Thanks
No problem to me with the EU global 12.5.4
[email protected] said:
No problem to me with the EU global 12.5.4
Click to expand...
Click to collapse
Thank you @[email protected] .
I did update to 12.5.8 Stable beta, issue stills exists.
Would I be able to flash the global one on to indian variant. I am new to the MIUI space.
Thanks
[email protected] said:
No problem to me with the EU global 12.5.4
Click to expand...
Click to collapse
Can you provide the model number of your device? RKFEUXM or RKFMIXM .
Which model rom should I download?
Also, can I download it and flash this rom through fastboot , with out the bootloader being unlocked? Or do i need to get the boot loader unlocked first ?
thank you
Using the 12.5.4.0 RKFEUXM in my VW Touran Discover Media Unit from 2018.
Mobile is the Redmi Note 10 pro
Important: Not rootetd & closed bootloader!
More problems to me as original.
[email protected] said:
Using the 12.5.4.0 RKFEUXM in my VW Touran Discover Media Unit from 2018.
Mobile is the Redmi Note 10 pro
Important: Not rootetd & closed bootloader!
More problems to me as original.
Click to expand...
Click to collapse
Thanks.
Do i need the Bootloader to be unocked to flash a diff region ROM ?
letscheckitout said:
Thanks.
Do i need the Bootloader to be unocked to flash a diff region ROM ?
Click to expand...
Click to collapse
I think so
[email protected] said:
I think so
Click to expand...
Click to collapse
Thanks , so i need to wait for 168 hours to get this thing unlocked
After the boot loader got unlocked i have installed tried the below ROM's but still cant get Android auto to work.
Eu ,Indonesian ,Global and Pixel ROM.
on All these roms none of the apps were setup for Dual apps.
Its driving me nuts , Any other steps that i can perform?
Lock bootloader and flash stock rom.
All my last mobiles where unlocked and rooted. None without any problem.
So i decided never to do this again. And all works as it should.
Sorry, not very helpful i guess ;-)
[email protected] said:
Lock bootloader and flash stock rom.
All my last mobiles where unlocked and rooted. None without any problem.
So i decided never to do this again. And all works as it should.
Sorry, not very helpful i guess ;-)
Click to expand...
Click to collapse
Did that , installed the Stock firmware but boot loader is unlocked, Still same issue. Kind of at a Dead End with this
letscheckitout said:
Has any got the AA to work successfully?
Phone : Note 10 Pro Indian Variant (M2101k6P)
OS : MIUI 12.5.4.0 (RKFINXM)
Cable is connected to the phone but android auto does not detect it. Below are the steps i have taken
New phone, Setup afresh ( No old Data was copied)
Have tried 3 different cables. onevanilla
Uninstalled AA updates, restart and reinstalled them.
Default USB configuration ( tried with all the options PTP,No Data Transfer,MIDI,File Transfer)
None of the apps are setup for Dual app.
Have AA Screen for phone installed.
Unknown Sources is checked in the Developer options of AA
Initially when i connected the phone for the first time, i saw a message "Unsupported device" , default USB was set to file transfer at this time.
After that neither the message pops up nor AA works.
Any other steps that will resolve the issue?
Thanks
Click to expand...
Click to collapse
Did you ever find a solution for this? I'm in the same situation.
Johnny5799 said:
Did you ever find a solution for this? I'm in the same situation.
Click to expand...
Click to collapse
Nope. A little bit of digging into the logs show that this is a permission issue but can't figure out , how to resolve it.
letscheckitout said:
Has any got the AA to work successfully?
Phone : Note 10 Pro Indian Variant (M2101k6P)
OS : MIUI 12.5.4.0 (RKFINXM)
Cable is connected to the phone but android auto does not detect it. Below are the steps i have taken
New phone, Setup afresh ( No old Data was copied)
Have tried 3 different cables. official site
Uninstalled AA updates, restart and reinstalled them.
Default USB configuration ( tried with all the options PTP,No Data Transfer,MIDI,File Transfer)
None of the apps are setup for Dual app.
Have AA Screen for phone installed.
Unknown Sources is checked in the Developer options of AA
Initially when i connected the phone for the first time, i saw a message "Unsupported device" , default USB was set to file transfer at this time.
After that neither the message pops up nor AA works.
Any other steps that will resolve the issue?
Thanks
Click to expand...
Click to collapse
Did you ever find a solution for this? I'm in the same situation.
letscheckitout said:
Nope. A little bit of digging into the logs show that this is a permission issue but can't figure out , how to resolve it.
Click to expand...
Click to collapse
I'm having a similar problem, what did you find in the logs?
Hey everyone, I've come across the same problem on my Peugeot 208 (2020 model) with a brand new Xiaomi 11T, MIUI Global 12.5.4.0 Stable (RKWEUXM) and Android 11 RP1A.200720.011.
Tried the following:
- updated the phone but it was in vain as it was already on the latest available version
- turned on "Receive updates early" but no luck getting anything new
- sideloaded Android Auto 7.0+ (both stable and daily releases) as phone came with version 6.9.
- tried different cable (can only use AA via cable)
- checked for dual apps but none are active
- deleted Android Auto cache
- deleted updates on Android Auto & reinstalled
This upcoming Friday I'm visiting the car shop to see if I can get the infotainment updated, fingers crossed.
After this, I guess I can only do some log dumping and dive into those with hopes of finding anything.
pantacruel said:
Hey everyone, I've come across the same problem on my Peugeot 208 (2020 model) with a brand new Xiaomi 11T, MIUI Global 12.5.4.0 Stable (RKWEUXM) and Android 11 RP1A.200720.011.
Tried the following:
- updated the phone but it was in vain as it was already on the latest available version
- turned on "Receive updates early" but no luck getting anything new
- sideloaded Android Auto 7.0+ (both stable and daily releases) as phone came with version 6.9.
- tried different cable (can only use AA via cable)
- checked for dual apps but none are active
- deleted Android Auto cache
- deleted updates on Android Auto & reinstalled
This upcoming Friday I'm visiting the car shop to see if I can get the infotainment updated, fingers crossed.
After this, I guess I can only do some log dumping and dive into those with hopes of finding anything.
Click to expand...
Click to collapse
Hi, i'm using AA on a peugeot 5008, which should be the same build.
It's working smoothly with ArrowOs, only diff is i'm still on AA 6.9
On dev settings : USB debug ON. Also check if AA has all authorisation needed.
TobyM95 said:
I'm having a similar problem, what did you find in the logs?
Click to expand...
Click to collapse
Nope, Even with the new 12.5 Enhanced Edition issue still exists
I resolved mine by trying quite a few different cables, I didn't think it would be the cable as the cable that came with the phone didn't work, but this cable has been working perfectly: USB C charging Cable TecMad USB Type-C
I'm not sure why this cable works but the stock cable doesn't, in theory they both meet the USB-C standard...

Categories

Resources