Cheap Chinese Radio and Android 10 - Android Q&A, Help & Troubleshooting

I have a Chinese radio specifically the 7023b model and with android 9 in google pixel 2, everything worked perfect. I connected android car through a usb cable, and enjoyed google maps and spotify. When I have updated to Android 10, everything works until the moment of connecting, it asks me for authorization usd debug, but it remains black screen and although I hear the voice, I can not see the image. It has a solution?

I'm experiencing the exact same problem with a Galaxy S9 and 7023B unit. Worked great with Android 9, no longer with 10. Even received a security update a few days ago, but didn't solve the problem. I contacted the radio vendor and said they are working on a patch for the radio and will send the new firmware when done, but I'm not hopeful. Think it is new security protocols for Android. Hope someone finds a fix!

Related

[Q] Bluetooth carkit problem

I have a Galaxy S3 I9300 for a couple of weeks now and I love it, other than the fact that I keep having a strange issue with the Bluetooth connection with my carkit. I've been searching forums for similar issues and I found a variety of carkit related problems, but none of the ones I found describe the same problem as what I'm having:
- Initially the Bluetooth connection works fine and I can play music or make a call through the carkit just fine
- When I switch off the car's systems and don't use any apps on the phone in the meanwhile, and then start the car's systems again, it establishes the Bluetooth connection just fine again
- When I switch off the car's systems and I use other apps for a while and then start the car again, it won't work. Bluetooth does appear to connect, but after that it just doesn't play ball. When I try to play a song at this point, the phone shows the song is playing, but neither the phone nor the car audio produces any sound
So anyway, every morning before leaving to work and every evening before going home, I reboot my phone first. Then I step into the car and it establishes the Bluetooth connection just fine. But if I don't reboot the phone first, it just won't work. Now I guess I could setup a tasker profile to automatically reboot the phone, but I'd rather just get the problem fixed.
I run a Galaxy S3 I9300 with stock Android 4.1.1, rooted. I have already tried to run the "Bluetooth Fix Repair" app and afterwards had to pair the phone with the carkit again, but that made no difference.
Any help would be greatly appreciated!
*bump*
Some additional info:
This issue has now also happened a few times while driving. While music (through Spotify) was playing over the bluetooth carkit, it would sometimes just stop working when I opened a different app (like for example opening an SMS). Spotify was still running (and the song was still ongoing) and also the bluetooth connection still showed as being connected, but it just wouldn't produce any sound anymore.
Anyway, it seems clear to me that this is a bluetooth issue, but I have no idea how I can troubleshoot this beyond what I've already done.
I would be happy to pay whoever can fix this problem..
With an issue like you are describing it may be helpful to list the headunit model too. I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
ItzCrooK2UxD said:
With an issue like you are describing it may be helpful to list the headunit model too.
Click to expand...
Click to collapse
My car is a Renault Megane RS, the carkit was built in. I believe it's called Renault Carminat TomTom.
ItzCrooK2UxD said:
I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Click to expand...
Click to collapse
I've covered everything like that in about 100 different ways, none of which made any difference.
ItzCrooK2UxD said:
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
Click to expand...
Click to collapse
Good point. It does have an SD card slot, but as far as I know that's only to update the maps of the navigation system. I'll see if I can figure that out.
Thanks for the tips!
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Apoc_ said:
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is in fact very possible that it is your phone, but wanted to throw it out there that bluetooth headunits can be troublesome on their own. Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me. Also do you have other bluetooth devices in the car, such as the 3GS you mentioned?
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
ItzCrooK2UxD said:
Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me.
Click to expand...
Click to collapse
Yeah I had read that too in some other thread (I went through just about every bluetooth related thread I could find, before I posted this topic). Mine saves up to 5. It didn't have anything in there except for my previous phone, which I had cleared. I also tried re-pairing the S3 several times, that didn't make any difference either.
Now, I just read somewhere that some people are having disconnection issues on the same carkit. In their case, in the end the problem turned out to be that their carkit will import all of their contacts from their phone (so you can call people even while your phone is in your pocket), and this would cause trouble when there are contacts without a phone number associated with it (just like my thousands of Exchange contacts). The people in question are talking about random disconnects though, whereas in my case it happens after doing some stuff on my phone. So it's probably unrelated, but I'll give that a try anyway just to rule it out. I just need to figure out a way to stop the carkit from importing contacts, because removing thousands of email contacts is obviously not an option.
I'll keep this topic updated with any progress. If anyone has any other ideas, please keep em coming. Thanks for the help so far!
ItzCrooK2UxD said:
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
Click to expand...
Click to collapse
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Apoc_ said:
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Click to expand...
Click to collapse
It reads a file that is being constantly updated (which happens to be the logcat file). Typically I will clear it right before doing what it took to cause the failure, like in your case in your car with the bluetooth on.
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
YoghurtPL said:
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
Click to expand...
Click to collapse
Yep - I have that too. The weird thing is that in that situation the phone does seem to think it is connected, while it really isn't. Just to be clear: this is not the only way to cause this issue (because it also happens when trying to reconnect the Bluetooth while on the phone it hasn't been disabled in the meanwhile).
So far I haven't been able to pull anything related from the logcat.
Also, while reading up on common bluetooth issues, I came across some posts of people who were saying that some phone/carkit combinations are having trouble with 2-way communication (because I can stream music from the phone to the carkit, but I can also change a song using the carkit or initiate a phonecall from the carkit). I'm going to try to only use communication initiated from the phone, and see whether that makes any difference. In the meanwhile: does anyone happen to know anything about 2-way communication issues with bluetooth, and how to overcome such issues?
Update:
- Updated carkit to latest firmware. No change, still same problem
- Have not been able to capture anything unusual in the logs
- I have a Bose Soundlink now, which is a wireless speaker. Whenever my S3 is connected to the Soundlink (with bluetooth), wifi doesn't work. Upon turning off bluetooth, wifi instantly works fine again. So this definitely confirms this is a problem with bluetooth on the phone, not on the carkit.
- Wanted to upgrade to Android 4.1.2 but Samsung won't let me, as it says the device is modified (rooted). Triangle away isn't helping. Damn you, Samsung. This is *the* reason I moved away from Apple, as I don't like companies who don't let you use your stuff any way you like. And now Samsung is moving down the same route. Idiots. Anyway, I guess the only option left, is to start using a custom ROM.
Does anyone happen to have experience in terms of solving bluetooth problems by using a custom ROM? I'm thinking of using Cyanogenmod 10.1
In the meanwhile I have upgraded to Android 4.1.2: still the same problem.
I have also discussed this matter with quite a few other Samsung smartphone owners, and all of them appear to be having the same issue. Most of them just don't seem to be bothered to spend time on looking for a fix.
Also, I have figured out that this problem is specific to media streaming. I'm able to use my phone on the carkit for calls at any time, without having to reboot first. Only when I try to listen to music, the problem occurs.
Anyway, I have ruled out that this problem is specific to me or my devices - this appears to be a global issue. So I'm completely puzzled as to why there's not a lot more fuss going on about this.
If anyone has any more suggestions for a resolution of this problem, please share.
S3 bluetooth connection problem
Had the same problem with my S3 and renault megane III handsfree bluetooth system.(Arkamsys software version 2.2.0.19 auditorium)
I downgraded to 4.0.4 baseband I9300CELH1 (stock) and problem seems fixed
hope this helps.
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Carkit bluetooth issue
Apoc_ said:
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Click to expand...
Click to collapse
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Bennes18 said:
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Click to expand...
Click to collapse
BB only, try this :
http://forum.xda-developers.com/showthread.php?t=2106424
Confirmed the update thing, i have updated the S3 to version 4.1.2 BB I9300CEELL1 and have no bluetooth issue whatsoever, car audio still on 2.2.0.19 byt the way
Pretty strange ... , but glad its working !
I have the same issue with a Ford Focus =/
also, while using CM or Omega, the music title never changes.

Android 5 Lollipop Bluetooth Connections

My Samsung Galaxy 5S automatically updated as opposed to update settings
Regardless there is no easy way back
Carrier is Telus
The bluetooth on the phone will not "pair" with the radio of a 2014 Nissan Altima
Before a reset it communicated audio yet no audio on phone although dialed
Samsung offers no help - blames 3rd party apps , no bug report link
Developer of Tune-in Radio advises its the bluetooth driver
Nissan now says "not a compatible phone on the list" although it worked fine on OS 4
Followed Samsungs standard advice , soft boot , clear cache , hard boot , restore all to no avail
Anyone have any ideas or links ?
Interestingly the dealer's 2015 ( which is supposed to be same radio model although may have software / firmware upgrades )

My amazfit bip can not reject a phone call!!!

Does anyone have a same problem with me? I don't know why? I can't hang up or Ignore a phone call, when i pressed both, my phone still rang! I have just reset factory my Bip and re-install Mifit but it still doesn't work! My Bip Firmware version is: V0.1.1.36 and Mifit App version is at 3.4.0! Can anyone tell me what the problem?
What OS on phone? Many people complained about the same issue for other watches on Android 8.0+ (not sure if 8.1 only, or from 8.0 and up). Check other threads. No solution so far unless you want to downgrade phone.
I had the same problem with 7.0 (samsung) I have changed my phone and runs on 8.0 ( huawei) I still have the problem, It worked fine on my samsung 7.0, suddenly it stopped working one day, changed my phone but still the same problem,so I guess its the watch.
take another phone dialer.z.B. google.
same issue for my bip on android 8.1
Amazfit pace.
same issue with Oneplus 3 running android 9 HAVOC OS

Question Bluetooth audio issue

When on calls and using Bluetooth (Lg FP8) if i get a notification the audio on the call becomes robotic and I can't make out the words of who I am speaking with. I have to toggle speaker on and back to BT to get it to stop. Doesn't happen with every notification, and isn't isolated to just one app afaik. Anyone else have this issue?
You're not the only one, Bluetooth on Androids seem really buggy.
Supposedly a December update is supposed to fix it, but that's what I hear about every issue with Pixel 6.
Try a network reset.
If that doesn't work try a hard reboot (soft reset).
ah0y said:
You're not the only one, Bluetooth on Androids seem really buggy.
Supposedly a December update is supposed to fix it, but that's what I hear about every issue with Pixel 6.
Click to expand...
Click to collapse
Here's a list of bugs as of Nov. 27 and their status:
Google Pixel 6, 6 Pro, & 6a new updates, bugs, issues, problems tracker
A detailed & continuously updated round-up of everything related to Google Pixel 6, 6 Pro, & 6a updates, bugs, issues, & problems.
piunikaweb.com

Question Android auto crashing

Hi guys
i have the XQ-CQ54 model with android 12 and i'm experiencing a lot of crashes with Android Auto. Tried everything including factory reset. Problem appears both on USB connection and wireless and appears on all cars i've tried it on (about 4 this far of different brands and models).
Anyone else with this?
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
viper. said:
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
Click to expand...
Click to collapse
i've tried various versions of android auto, they all crash... but they don't on my Samsung S20FE with same Android OS version (12)
Latest thing i tried was making sure power management is off for both AA and Spotify. We'll see if that makes a difference...
Yet again s20fe is not new on the market ,i know what you are saying but i still feel bugs might need some time to be polished on 5 iv as they dont have same hardware .
You can try to test it in safe mode...tho i am not sure if android auto is disabled or not in safe mode
tried changing battery management settings for apps, i'll see if that makes a difference.
andost said:
tried changing battery management settings for apps, i'll see if that makes a difference.
Click to expand...
Click to collapse
nope, didn't... still crashes...
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
dhj1949er said:
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
Click to expand...
Click to collapse
yeah, it's just that the behaviour is the same both on wireless android auto and with USB-c connected...
tonysunshine said:
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
Click to expand...
Click to collapse
just updated to android 13 (64.1.x) from 64.0.x firmware - same problem except on the way home it was worse than it has ever been before, crashed / disconnected every 5 minutes and reconnected... extremely annoying.
i have 1 IV and don't have crashes. But generally, not as reliable as it was with my XZ2.
Car is Peugeot 3008 mk2 from 2017. Wireless does not work at all but don't really care about that because it just drains battery instead of charging. Now, charging........sometimes it does not charge despite having AA active and using sat nav. Cable that I used with XZ2 (ugreen) does not work at all for AA. And most of the time not even for data on laptop. Cable from XZ2 works with AA every time, did a 5000km trip a few months back, no issues. Except it does not charge sometimes, LED is on, sign for charging is on but battery charge goes down.
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
TodNex said:
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
Click to expand...
Click to collapse
Yeah, I've tried that including completely removing / reinstalling app etc.
Now trying on another phone (yes, another 5 IV) which is set up from scratch without restoring from backup.
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
somm15 said:
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
Click to expand...
Click to collapse
Hep, another one here!
i'm trying to remove apps one by one now...
Well, I had 1 hours without any crash... after enabling the debug layer for android auto. I didn't notice any difference or additional info but no crash.
Hey Guys; I am facing the same issue. Just, that it's not related to Android Auto.
Many apps were crashing just randomly.
For example, like Tidal, sometimes it was playing music for hours and sometimes just for a few minutes until it crashed.
So I enabled a feature in developer mode which allows to show a crashing dialog. And just a few moments later the nextcloud app crashed and the error message was something like "out of memory".
Looking in to it => Yep, there it was => the OS is holding almost all of the available memory.
So, you might want to check your memory in Settings => Developer Options => Memory.
And since I almost bricked my device last night, I just flashed the latest 64.1.A.0.857 via newflasher and at the moment (fresh OS) it seems to be better - but I will surley find out these days.
Merry Christmas everyone ...
Hi guys, I had similar problems with Android auto. I did a software repair with Xperia Companion, since then AA works fine.

Categories

Resources