Just recently I've been having problems with two things: Navigation and bluetooth voice dialer. Google maps works fine until I try to use navigation. After that, it force closes then has to be force stopped by the system, otherwise the force close message keeps popping up. Bluetooth commands just won't work. The dialer screen comes up, but won't "start." It just makes a loud noise in the headset, vibrates a few times, then closes. Anyone experiencing the same problems?
T-Mobile G2, Stock Froyo 2.2
Related
I was just wondering if anyone else has come across this issue or heard about it...
I am running CyanogenMod 2.2 Nightly (7-31-2010) with SnapV3 Kernel. I was just out driving while listening to Pandora through bluetooth. I happened to try out google navigation whilst doing this and I noticed that I couldn't get a GPS lock. The navigation app just kept saying that it was looking for GPS.
After some playing around I realized that if I turn off Pandora the navigation app works perfectly, but every time I turn on Pandora I either get the looking for GPS message or my position will not update.
Thanks for any input!
Intensentropy said:
I was just wondering if anyone else has come across this issue or heard about it...
I am running CyanogenMod 2.2 Nightly (7-31-2010) with SnapV3 Kernel. I was just out driving while listening to Pandora through bluetooth. I happened to try out google navigation whilst doing this and I noticed that I couldn't get a GPS lock. The navigation app just kept saying that it was looking for GPS.
After some playing around I realized that if I turn off Pandora the navigation app works perfectly, but every time I turn on Pandora I either get the looking for GPS message or my position will not update.
Thanks for any input!
Click to expand...
Click to collapse
It's been known for a while that you can't listen to music (over speakerphone speaker using any app) and use GPS perhaps bluetooth suffers the same flaw?
If you download GPSTest then start it and open pandora, last.fm, local music player, etc and then hop into GPSTest really fast you'll see the phones unable to find GPS satellites.
Ok, I'll give that a try. Thanks for the info!
I've been working in other cities where I need the gps to get there and want to listen to pandora, so after I ran into this problem, I started keeping a nandroid of a 2.1 rom....
Intensentropy said:
I was just wondering if anyone else has come across this issue or heard about it...
I am running CyanogenMod 2.2 Nightly (7-31-2010) with SnapV3 Kernel. I was just out driving while listening to Pandora through bluetooth. I happened to try out google navigation whilst doing this and I noticed that I couldn't get a GPS lock. The navigation app just kept saying that it was looking for GPS.
After some playing around I realized that if I turn off Pandora the navigation app works perfectly, but every time I turn on Pandora I either get the looking for GPS message or my position will not update.
Thanks for any input!
Click to expand...
Click to collapse
Just came back from jog and yours was the 1st post I came across, strange because this is EXACTLY what happened. Listening to pandora in the back ground Endomond gps tracker kept pausing, this is the 1st time that program has ever had an issue so there is conflict somewhere.
Well, I have played around with it a bit more and found that playing pandora through bluetooth does not cause a problem. I only run into the issue when using the phones speaker. I'm not sure about headphones though, I havn't tried that yet as I dont really have the need for them.
Of course there is still a problem with the navigation app turning off pandora every time it gives you audible directions. To stop this I just mute the navigation app and everything works well together.
I just run into a similar problem this morning
I'm running the leaked 2.2 build from last weekend.... before froyo, I could listen to pandora and use google nav all while plugged into my car stereo via aux jack.
now, when navigation gives a direction, it pauses pandora and you manually have to go back to it and press play
sooo annoying... anyone else run into this?
Order of Operations Counts, I think
I ran into this issue both with 2.1 and now 2.2 on my Evo. I'm not sure who the culprit is, but I've found that starting navigation, letting it acquire the GPS signal, and then launching Pandora works fine. If I do it the other way around my GPS signal basically dies.
Another interesting quirk I've noted is that if I start GPS first, but then Pandora.. my Nav voice will play through the speakerphone while Pandora plays through the headphone jack. If I start Pandora first, then Nav, they both play through the speakers.
I think what it may be is if Pandora starts/is caching while the phone is trying to startup GPS and acquire a position. I'll test it more during my drive home tonight. This has to be a software bug on side or the other. (Maybe it's google's ad software in Pandora trying to grab GPS for location specific advertising lol)
thefudd said:
I just run into a similar problem this morning
I'm running the leaked 2.2 build from last weekend.... before froyo, I could listen to pandora and use google nav all while plugged into my car stereo via aux jack.
now, when navigation gives a direction, it pauses pandora and you manually have to go back to it and press play
sooo annoying... anyone else run into this?
Click to expand...
Click to collapse
I was directed here http://code.google.com/p/android/issues/detail?id=9569 yesterday when I brought up the same issue on a different thread. It's an issue with android itslef. Looks like it kicked in at the 1.47 ota, prior to that, the audio would go right back to playing pandora or whatever after nav told you to take a left.
Is anyone having problems with their bluetooth locking up? I am getting various issues that all seem to be related to the bluetooth. I routinely connect to a Jabra Cruiser Bluetooth speakerphone in my car and stream music, mostly Pandora but sometimes google music or other players.
This morning I turned on the speakerphone and immediately watchdog told me that bluetoothd and pandora services were both stuck at 40% each. I hadn't even launched pandora since the last reboot. Had to restart the phone.
Other times I will go to turn on the speakerphone and it will not connect. I try to turn bluetooth on and off. It shuts off fine but hangs turning on. Usually about 30 seconds later the entire phone becomes unresponsive and I have to restart it by holding power. Putting it in and out of flight mode does the same thing.
Still other times I will shut the speakerphone off or walk out of range and the bluetooth icon on the phone continues to show connected. Sound may or may not come out of the phone and the volume control says bluetooth audio. Again restarting bluetooth locks up the phone and requires a restart.
Lastly sometimes bluetoothd and/or pandora will randomly go haywire and hang with high CPU utilization.
Anybody else seeing any or all of these symptoms or have any ideas. I am rooted and have the 2.3.6 update. Pretty sure the problems were occuring before the update, not sure about before the root.
Thanks...
Yes I am having similar problems when using bluetooth to connect to my home based panasonic DECT phone system. A reboot of the phone does repair the issue. It seems to occur every 24-72 hours, if the phone is not rebooted. My blackberry connects via bluetooth to the same panasonic phone system without issue. I suppose it could be a problem between multiple bluetooth devices. I suspect it is a SW bug though, because a simple reboot has always resolved the problem for me.
Do you have pandora installed? I uninstalled it yesterday and haven't had the problem yet. Did plenty of streaming with Google Music.
One thing I forgot to add. When the device says that is connected and sending out audio over the bluetooth, such as music, but it is really not, I get a moment of audio out of the built in speakers before it turns off.
eddiert said:
Do you have pandora installed? I uninstalled it yesterday and haven't had the problem yet. Did plenty of streaming with Google Music.
One thing I forgot to add. When the device says that is connected and sending out audio over the bluetooth, such as music, but it is really not, I get a moment of audio out of the built in speakers before it turns off.
Click to expand...
Click to collapse
Yes....we do have pandora installed...and now that you mention it; I believe it is quite possible that we only have the problem when we run pandora after a reboot. Because for the past few days there has been no issue. And I believe during this time I have not been using pandora. If it is Pandora...hopefully a future pandora bug fix will repair the issue.
Since I uninstalled Pandora I have not had a single lockup in almost two weeks. I guess I'll message Pandora and see if they'll fix it.
Edit - Looks like they may have fixed it. Crossing fingers.
What's New
What's in this version:
The Search hard key now takes you to the Pandora station search screen
"Now Playing": next track information is shown much sooner
"Now Playing": album art is now always scaled correctly
Fix crash when toggling Bluetooth on/off
Fix display of genre station lists on Android 2.3.4 and above
Many low level bug fixes and stability enhancements fixing crashes and application hangs
Whenever I enable listen-for-wakeup-command in Vlingo's InCar mode, Vlingo crashes within a few seconds. Has anyone else tried Vlingo on their Note 2, and does the same thing happen?
I used to have tons of problems with Vlingo back when Froyo was released do I haven't used it since. They had major Bluetooth issues for a while.
Yeah I said it!
Hi Everyone
I'm having issues with Google Voice Recognition. If I have headphones plugged in and I toggle voice recognition from the soft keyboard (the little mic icon) the media player I have running in the background cuts out. It stays out even after voice recognition has finished listening.
If I toggle voice recognition into listening mode again, the media audio cuts back in until voice recognition stops listening, then it cuts back out. Even apps like Utter! cause this same exact behavior. It seems to be when one of these apps forces the audio to focus on something else. This issue doesn't happen at all if I *don't* have anything plugged into the headphone jack. It works like normal in those cases.
Restarting the media player doesn't fix it. The only ways to fix it are to totally restart the phone, or unplug the headphones, toggle voice recognition, wait for it to stop listening, then plug the headphones back in. Then it all works correctly until the next time voice recognition is toggled. Then the problem happens all over again.
I'm running Beanstalk 4.3 RC1.1 + W03Tweaks v1.6.1 with uneak kernel 2.22. I've tried switching to a different kernel (devil) but I get the same results. I've noticed this problem on both 4.2 and 4.3 rom's for me (Both Beanstalk, haven't tested other roms).
It's driving me crazy since I can't use voice recognition when I'm driving without causing my music to stop. I made a video of what it's doing, http://www.youtube.com/watch?v=eFm-Hk0TADw.
Hi All,
I've noticed that when I'm listening to music or podcasts (via Rocket Player, Pocket Casts, etc. ) over bluetooth in my car, I cannot hear any notifications. The music/audio pauses briefly to play the notification sound, but no sound is heard. The same happens with turn by turn directions via Here Maps (haven't tried Google Maps yet, but I suspect the same issue would occur). Has anyone else run in to this issue?
Try the latest update released today: "Force output to be primary output when using BT_SCO."
Still the same issue even after the update, unfortunately.
https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=en
Just thought I'd follow up on this in case anyone else is having this problem. For whatever reason bluetooth notification randomly started working for me a few days ago. No rhyme or reason, but I'm glad it's working now.