Here's the deal. I have an iBolt car dock (that specific really shouldn't matter) and Tasker profiles to turn on GPS, Bluetooth, etc while my phone is plugged in. Been like that for months. Up until about a week and half to two weeks ago, my phone app would crash when trying to receive a call while in said dock. The message I got was "unfortunately, the process com.android.phone has stopped". When I noticed, I was running Carbon. I clean flashed the nightly I was on and same result. I then tried Deviant, Slim, JellyBeer, PAC-man, etc. All of them gave the same result. Same wipe procedure for all of them. Same apps as I've always had. I then flashed AOKP M1 and everything worked. Then I tried Task's AOKP. Same thing. Everything worked. I don't get it. I posted the issue without a logcat (as pulling one of those while driving is a no no) in those respective dev's threads but it seems they don't know what's going on with everyone else. Hence, this thread. If you are running any of the ROMs I mention and experienced the same problem, post here. If you have logcats (ballsy), even better. I figure this would be the best way for all the devs of those ROMs to see what is happening and so the problem can be nailed down.
I'm also using an iBolt dock. Posted this in Xone Deviant thread: http://forum.xda-developers.com/showthread.php?t=2215840&page=55
itsmikeramsay said:
Not 100% sure bro, haven't been able to test it...
Click to expand...
Click to collapse
CrackerTeg said:
@ itsmikeramsay. Did you see this a few pages back? Thoughts?
Click to expand...
Click to collapse
Same here. Phone ui crashes when call is initiated but call goes through. Catlog attached.
Glad to see someone else feels my frustration with this. I battle this issue all the time. I have 2 iBolt docks(the regular one & the pro dock) & have had this issue with both. If not the not the incoming calls freezing the phone, its the phone rebooting when pluging it in, or the dev will update the rom and the usb audio doesn't work at all. I'll give task's AOKP a try to see how things with it. I was a huge fan his roms in the past up untill an update and the usb audio stopped working. In that situation, I usual just try a couple different roms untill one works. But then, the incoming issue happens or it reboots when docked and I feel like throwing my phone out the window
btw, i got an email today about the prodock cables being shipped. I've been using the one that came with the first iBolt
If my wallet would allow it, I would buy a headunit with bluetooth and use a NFC chip to put the phone in dock mode and not have this issue regardless of what rom i'm running. but my wallet stays empty
---------- Post added at 01:16 PM ---------- Previous post was at 12:41 PM ----------
I'm pretty sure the usb audio out working on some roms/updates vs. not working others is due to something in the kernel. Ex. I flashed the latest deviant xone update(2.0) and the didn't work. So I reflashed the previous version (1.0 stableish) and the audio works.
I hope this gets resolved 'cause I enjoy listening to podcasts & playing ingress during my commute only to have it ruined by a phone call that freezes my phone, rebooting booting and listening to my wife "quit ignoring my phone calls"
Sent from my SGH-I747 using xda premium
Interesting. My complaint has nothing to do with the audio out portion of it as I use my phone for browsing and as a phone. I have my tablet or iPod for the music in my car. So the complaint has nothing really to do with the iBolt but the phone being docked and not being able to use the actual phone function. If the usb audio gets fixed, bonus but I'm much more concerned with the primary function of this device.
After doing a bit of research, it seems that samsung didn't implement call audio through the dock connector. I know this is not your direct complaint BUT if you are using the ibolt cable that has the dock resistor( that tells the phone to go in dock mode) and the Rom/kernel is trying to route the audio via the usb than the phone may be getting confused. I think the solution to your issue, since your not concerned about audio out, is to replace the supplied cable with a standard data/charging cable. I haven't tested this theory, but i'm pretty sure taking the dock resistor out of the equation will fix the phone freezing when receiving a call.
I did have a rom installed at one point that had audio out working AND didn't freeze on incoming BUT had an unrelated bug that drove me nuts, so flashed another rom. It's too bad I can recall which rom and which release it was
Thing is, I have a Parrot bluetooth adapter that my calls go through. They don't go through the dock at all. I have a tasker profile that triggers the phone to go into car mode with Google's no longer supported Car dock app when the device is plugged in. It also turns on bluetooth, GPS, blah blah. Like I said in the OP, everything was just peachy up until two weeks ago where something in those ROMs got borked. Either way, I'm now running Carbon's latest and the issue is gone. Whatever got messed up is now fixed. I wish I knew what it was tbh but I can't read git.
I would like to add my two cents.
I too have an iBolt dock for SGS3, and an after-market radio with bluetooth.
I have tried several ROMs (CM stable, LiquidSmooth, ParanoidAndroid), and all of them exhibit the same behavior:
Going into the docked mode is flakey at best. 90% of the time the phone doesn't recognize it has been docked.
Now comes the "best" part: on disconnect from the dock the phone's bluetooth stack apparently crashes. The bluetooth connection gets immediately lost, and the phone's bluetooth status is stuck in 'ON' position. After that there is no way to turn the phone's bluetooth 'OFF' and back 'ON'. The only way to restore is to reboot the phone.
I haven't tried to pull the logs from the phone yet, but it may be possible if I take the dock home and try to repro the condition.
Not asking for answers, just voicing my frustration hoping to draw dev's attention to the problem.
Related
Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
I have the same thing. silly thing keeps poping up. trying somethings if i get it to stop ill let you know. let me know if you get it to stop
Go into a roms zip file, find carhome apk, delete it and wipe and flash. I'm not sure if this will work since I don't know if you have to change the code too
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
Or use Root Explorer and go to /system/app and delete it there. I never used it anyway.
I had that same problem on that rom
I found 2 carhome apk's in my system apps. I deleted both but then had fc's.
So I'm curious off you find a solution
Swyped from a galaxy far far away......
thanks i tried that did not work. just done got a older nan backup and put it ok it seems ok for now.
thanks m8
car home is a virus
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
robenever said:
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
Click to expand...
Click to collapse
gapps.hdpi.zip? WTF? Quit running your own GApps. Wipe everything, get RC2, flash 20110307 GApps and go from there. Solves all problems.
Not sure if this will help you much but I had this same problem once and ended up unrooting my phone and even then it did it so I went into a sprint store and they replaced it free of charge.
crakerjaks said:
Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
Click to expand...
Click to collapse
i flashed to Sense then updated PRL, then Profile. Then i flashed back to CM6 its bn working eversince
i rather make my own gapps n take my chances than just sit here n do nothing. however, i am working unrooting my phone and rerooting it again. if that doesnt work.. then its back to the sprint store
I did a full wipe and reflashed CM7 RC2 along with the gapps that came with it, and so far no problems *knocks on wood*.
I had this problem and found that the culprit was pocket lint lodged in the phone's usb port--grounding out one or more pins.
I read a post about a guy who made his own car dock cable by grounding pin4, auto-triggering car home, like the real evo car dock, whenever he connected his cable.
I got thinking and grabbed out my jewlers loupe and saw some crud at the base of the usb jack. With the battery removed I got a slender sewing needle and bent the tip slightly with a plires to make an "r" shaped hook.
I gently scraped around the bottom and edges of the usb jack on the phone with the needle and pulled out a years worth of greazy lint crud that literally wedged against the pins, no doubt grounding out one or more of them, thus kicking up the car dock shenanigans. Seriously, a lot of lint.
Once the dock issue showed up, prior to cleaning the jack, the car home app showed up EVery time i plugged in usb.
I havent seen car home nonsense at all since cleaning out the jack.
prior to cleaning i called sprint having read about others doing the same. Without much hassle they sent me a warranty refurb (with 2.3.3 installed) to replace mine,
With a clean jack, i can send them back the refurb and keep mine as is.
hope this helps
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
slackard said:
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1107759
A story of how I fixed this problem over a month ago. Refer to post 5.
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
tnerb123 said:
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My circuit board fried, then fixed itself?
I would be interested in where you got this information from.
Sprint does acknowledge this. I have the same issue and thought i solved it by cleaning the USB jack--not so.
I was just in the sprint store the other day with my faulty phone and after some digging the tech found a bug report titiled something like "speaker phone always on" in their bug database. Recommendations in that bug report were to clean usb leads and if that doesnt solve, replace the phone.
Sprint offered to replace mine without too much hassle and shipped a refurb overnight, but the new phone came with gingnerbread and is therefore unrootable (at the time of this post), so i started looking for another solution--to disalbe the dock features entirely.
I came across the app NoDock, which loads a kernel module that interupts communication between the dock sensor and the OS, preventing the dock & speakerphone shenanigans.
I dug around in adb shell a bit and found the kernel module being loaded by the NoDock app.
Its located in /data/data/com.nothize.free.nodock/files/ and titled "nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko"
I was able to load this module by hand as SU in adb shell with the following:
#su
#insmod /data/data/com.nothize.free.nodock/files/nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko
I will work on moving this module out of the NoDock app directory and see if i can get it to load on-boot without needing the timelimited APK. No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
I already sent the gingerbread phone back to sprint and will stick with this solution for the time being.
Hope this helps anyone with similar problems.
Well you're not offending me, you're just thinking in a different way than I'm and (if) you haven't leave any destructive comments about it.
What the app worth is really the kernel module.......the app interface however, provides settings that may serve other use cases.
I wrote the kernel module myself, but not ripped off from anything else, so you cannot say that you are not willing to pay for just the "app" that loads the kernel module. In fact, you're paying the novel ideas and the novel kernel module too that took most of the time for the research to make it works for various phones including S2. You can read more if you have visited my website. So if you got the knowledge and skills, as I've already documented how I am doing this, you should be able to write your own kernel module.
The free trial app was a free app a long time ago......until I felt offending by some "free version users". They emailed me for support, they left silly comments, complains and complains out of a reason. I lost my hope to them while the paid users have so much better quality.
And you're lucky to extract the old free trial version....IIRC, the expire has been introduced to the kernel module too since some version.
slackard said:
No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
Click to expand...
Click to collapse
I had the same issue. Turned out that my issue wasn't a piece of pocket lint in the USB jack (which DOES cause the same issue)....instead it was a bent pin in my charger. I bought a new charger for $3 on Ebay and I have never had the issue since then. Common sense tells you that if you've gone through all avenues of software issues and the problem is still recurring then you need to start looking at physical aspects of the phone. In this case, the device that triggers car home automatically......aka the USB port and anything connected to it.
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Had a similar experience
Headset being detected even when not connected seems to be a common bug on Gnex, have seen several posts and I myself had to go through this. It usually gets fixed by itself in a day or two.. but till then use the "toggleheadset2" from the play store, which would allow you to manually say when the headphone is connected or not.
--Vj
PhreeqQitsikk said:
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Click to expand...
Click to collapse
---------- Post added at 10:27 AM ---------- Previous post was at 10:17 AM ----------
Only permanent solution is to change the socket. Its the switch inside which usually gets jammed.
Same exact problem
I am having this same exact problem. Its fine on stock, once I flash CM10 calls say connected and the time starts ticking but I can't hear a thing and no one on the other end can hear me.
Sometimes when I do connect, the person will hear me for a couple seconds and then it'll drop then connect again then drop...over and over again.
Google now doesn't pick up any voice searches either.
HELP, this is a relatively new issue. (2-3 months old) I've had the nexus since January and had it rooted and rom'd shortly after. Only recently has this issue cropped up.
toggleheadset2 seems to work but it sucks that I even have to use it. Any devs out there have suggestions/input? I've looked all over for a resolution.
Please don't make me go back to stock....Please!
Just bought a nexus from Verizon, on my second device now. First device was exchanged after 1 day, battery ran out in 6 hours, never held signal for more than 2 min. Second device is a refurb, phone worked great and had ZERO issues until updating to 4.0.4. Came with 4.0.2 on it, put off the update for several days to see if it worked ok. Everything ran smooth and fast, great battery life and signal. Immediately after the update, phone now hangs and freeze when unlocking, switching home screens, open app menu etc. Phone also seems to randomly think a headset is plugged in and will not make any sounds except ring, and in a call, neither ear speaker or mic work. Speakerphone works, and if a headset is plugged in, sounds works normally through headset. Found this app:Wired Headset Routing Fix which sometimes fixes mic issue. Sounds and mic work normally after a reboot, but will then randomly stop. Found several pages of threads all over about the mic issue, but with no fixes.
Tried flashing Bugless Beast rom to adress some of these issues, all problems remain. Mic/sound issue seems tom be related to something with the software that controls the headphone jack. Should I continue trying different roms? Try a different kernel? Possible to complete reset phone back to stock 4.0.2? It worked FANTASTICALLY before the update, how could I get it back to the way it was when I unboxed it? My 14 day warranty runs out on the 22nd, so I could exchange the phone again, but my Verizon store has been hounding me to switch to another device.
Any help would be greatly appreciated!
After your first device they gave you a refurb? Only After a day? That's strange.
Sent from my Galaxy Nexus using xda app-developers app
They initially gave me a brand new one, case was cracked completely through when they opened the box to activate it. The only other phone they had on hand was a refurb.
Yet another ROM comparison. I've been using CM since I got this phone in May 2013. I love CM. It is clean, fast has a ton of nice features and is NOT TouchWiz. I've been loyal to it since I got this phone. I had it on my previous Atrig 4G, too. The problem is that not everything works in CM on the d2att. I blame Samsung for this, but do not really know where the blame lays. I read reports that Samsung withheld the source which made it tough to get everything working correctly. The Bugs list on CM for this phone is not complete mainly with regards to Dock and Bluetooth, IMO. I have not tried any other AOSP ROMs, but some of these bugs may be there as well.
I recently decided to try the latest 4.4.2 stock rom and it seemed to work OK, but I had to freeze and uninstall so much stuff. I discovered S3Rx and am now very happy with my phone. I still have TouchWiz showing its ugly head (most prevalently in the pull down and dialer/incallUI), but now everything works!!!! The new modem NJ1 has better sensitivity (I can get calls in places when I had no signal previously). Bluetooth works correctly. I can have multiple BT streams and not lock up the phone (Audio and serial or serial and phone). Previously, it would drag down and both would eventually fail. BT connects more reliably and readily. I have not tried dock audio, but there is a selection for it and I am guessing it works. (I did try dock USB audio and not only does it work, but it is not noisy like it was in CM10/early CM11 when it was functional) The only niggle is car dock identification. When you place it in the dock, the car mode icon illuminates, but no app is launched. I had to create a Tasker profile to get it to launch the old Android Car Home app. To get the home button to resume to the Car Home app (known issue with car home), you need to enable the car home button through an exposed framework module. It all seems to just work. Also, no random reboots.
Hope this helps someone who is still trying to get life out of this great piece of hardware. If you are struggling to get the phone to do all it should do and are frustrated with CM, I recommend this rom
keithspg said:
Yet another ROM comparison. I've been using CM since I got this phone in May 2013. I love CM. It is clean, fast has a ton of nice features and is NOT TouchWiz. I've been loyal to it since I got this phone. I had it on my previous Atrig 4G, too. The problem is that not everything works in CM on the d2att. I blame Samsung for this, but do not really know where the blame lays. I read reports that Samsung withheld the source which made it tough to get everything working correctly. The Bugs list on CM for this phone is not complete mainly with regards to Dock and Bluetooth, IMO. I have not tried any other AOSP ROMs, but some of these bugs may be there as well.
I recently decided to try the latest 4.4.2 stock rom and it seemed to work OK, but I had to freeze and uninstall so much stuff. I discovered S3Rx and am now very happy with my phone. I still have TouchWiz showing its ugly head (most prevalently in the pull down and dialer/incallUI), but now everything works!!!! The new modem NJ1 has better sensitivity (I can get calls in places when I had no signal previously). Bluetooth works correctly. I can have multiple BT streams and not lock up the phone (Audio and serial or serial and phone). Previously, it would drag down and both would eventually fail. BT connects more reliably and readily. I have not tried dock audio, but there is a selection for it and I am guessing it works. (I did try dock USB audio and not only does it work, but it is not noisy like it was in CM10/early CM11 when it was functional) The only niggle is car dock identification. When you place it in the dock, the car mode icon illuminates, but no app is launched. I had to create a Tasker profile to get it to launch the old Android Car Home app. To get the home button to resume to the Car Home app (known issue with car home), you need to enable the car home button through an exposed framework module. It all seems to just work. Also, no random reboots.
Hope this helps someone who is still trying to get life out of this great piece of hardware. If you are struggling to get the phone to do all it should do and are frustrated with CM, I recommend this rom
Click to expand...
Click to collapse
Be careful with this type of post as it encourages competition between devs.
Just an option, but how about just "reviewing" Roms,
I created a thread on " whats your favorite Rom and why" and a day later it was pulled by the moderator.
CM has come along very well recently
So I've just switched back from IOS to Android and picked up a Pixel 3 XL with the 1-day sale. I tried setting up Android Auto though but I can't get it to work properly. I can connect and add my car (2017 Kia Niro), but after I try to select the Android Auto icon on the head unit it crashed and keeps flashing "Phone is not responding" and "Reading USB" over and over. On the phone, it still says connected to the car and shows the green notification bar suggesting Google Maps is in use.
I've tried using an older version of AA, but it gives an error unless I update. If I try to connect, not press the icon on the head unit and start playing Spotify, I get 1-2 seconds of audio through the car but then it crashes again. One time I got as far as launching and selecting the navigation tab until it crashed. I've briefly talked to Google support and they requested a bug report which I've sent. I also tried updating to the Q beta to see if that made any changes. I've used 5 different USB cables with no luck.
I didn't have any issues with Apple Carplay, and I also tried a very old Samsung phone (micro-USB) successfully so it shouldn't be the car causing the issue. Does anyone have any tips on what I should look at? I've done a factory reset, cleared all cars, toggled the AA setting on the head unit but nothing makes any difference. I'm pretty reliant on this functionality, so if it doesn't work I probably will be switching back to my iPhone.
Odd behavior. I've had a few issues with AA on my 3XL on Q beta 2 (patched), but none like that. I have a 2016 Chevy Malibu and most of the time when I plug it in I get video but no audio. Pressing play on Spotify does play, but no sound comes out. Disconnecting and reconnecting USB a few times fixes it. There are intermittent skips in the music where it cuts out for a second and comes back. The screen flashes black at times when a notification peeks on the screen like when the song changes. Overall it works, but Q beta brought some bugs. It was mostly OK on P. I believe the no audio started on beta 2.
Have you looked at the developer settings in AA to see if any toggles might help? I think you can go to About and tap the version 7 times, similar to enabling Dev Options by tapping build number in Android system settings.
fury683 said:
Odd behavior. I've had a few issues with AA on my 3XL on Q beta 2 (patched), but none like that. I have a 2016 Chevy Malibu and most of the time when I plug it in I get video but no audio. Pressing play on Spotify does play, but no sound comes out. Disconnecting and reconnecting USB a few times fixes it. There are intermittent skips in the music where it cuts out for a second and comes back. The screen flashes black at times when a notification peeks on the screen like when the song changes. Overall it works, but Q beta brought some bugs. It was mostly OK on P. I believe the no audio started on beta 2.
Have you looked at the developer settings in AA to see if any toggles might help? I think you can go to About and tap the version 7 times, similar to enabling Dev Options by tapping build number in Android system settings.
Click to expand...
Click to collapse
Thanks! I'll give that a shot when I go to my car later. I forgot about the AA dev options, it's been so long since I've used Android. Hopefully, if I do get it working I don't have the audio issues you mention by switching to Q else I guess I'll need to revert back to P.
I just received a new Subaru, and I couldn't get AA to open at all. After searching, a common denominator was the cable used to connect the phone (my car requires a usb connection). I tried 4 different cables before I got it to work.
The one that worked was an OTG cable, no longer available on Amazon.
Sent from my Pixel 3 XL using Tapatalk
princeplanet said:
I just received a new Subaru, and I couldn't get AA to open at all. After searching, a common denominator was the cable used to connect the phone (my car requires a usb connection). I tried 4 different cables before I got it to work.
The one that worked was an OTG cable, no longer available on Amazon.
Click to expand...
Click to collapse
I have 2 Subarus and had issues with AA until I figured out that I needed the head unit to come up, have the I agree screen dissappear, and then connect the phone. Works every time. Plugging the phone in before booting the head unit is hit or miss.
---------- Post added at 08:03 AM ---------- Previous post was at 08:01 AM ----------
wafflenator said:
Thanks! I'll give that a shot when I go to my car later. I forgot about the AA dev options, it's been so long since I've used Android. Hopefully, if I do get it working I don't have the audio issues you mention by switching to Q else I guess I'll need to revert back to P.
Click to expand...
Click to collapse
Try waiting for your cars head unit to come up before connecting the phone. Ideally bluetooth wilm be connected before you connect USB.
Well, turns out it was the cable. This was 4 old supposedly good cables from a few years ago, along with a new one from Best Buy. Picked up a new Insignia USB C cable where the reviews mentioned success with AA and it is working. Bit of a headache but good news.