Hi All, I just had a question about bluetooth gps receivers.
I read awhile back that the Android OS's bluetooth stack was not equipped to handle serial port protocol connections over bluetooth which is what you need for a external bluetooth gps receiver. Just wondering if any of the new ROMs (2.1 or 2.2) have looked into implementing this? or if there's already an app out there.
i've looked and seems all the apps i found on market seem to be just data logging and doesn't allow you to replace the internal gps functionality.
this is a pretty good question. I have not seen anything about this mentioned on any rom. I would lean towards no but since i dont know for sure i figured i would help bump the thread hoping someone who knows for sure can shed some light
Seems to be working now -- my Samsung Galaxy S (running 2.1) can use my external Bluetooth GPS receiver now (not natively, but using a app called 'Bluetooth GPS Mouse')
okay, the app 'bluetooth gps mouse' doesn't seem to work. keeps saying i'm in china somewhere.
i actually found another program called 'Bluetooth gps provider' that works pretty good, except for google nav...
I informed them about the bug and today they released an update, so Bluetooth GPS Mouse should work now as well
Was wondering if Coredroid 7.0 supports sharing phone contacts via bluetooth? I have a Motorola Roadster Bluetooth device in my car and hoped my phone contact list could be shared so I could voice dial using it.
I'm having the following issues:
1) Takes a long time to connect..phone shows paired but not connected (after several minutes it may or may not connect)
2) Doesn't allow me to voicedial (Get an FC if I hit the voicedial button on Roadster)
3) Doesn't support accessing phonebook via bluetooth?
Love the Rom....just wish I could use bluetooth device in my car. Anyone else having issues?
I too am seeing the voice dialer FC when activated from BT but it seems to work fine when initiated from the phone. Would be nice to be able to initiate voice dial from my BT headset. Have done some reading on this issue and appears to be occurring with many roms so it might not be a coredroid issue or even an issue coredroid can fix??
longdongsilver said:
I too am seeing the voice dialer FC when activated from BT but it seems to work fine when initiated from the phone. Would be nice to be able to initiate voice dial from my BT headset. Have done some reading on this issue and appears to be occurring with many roms so it might not be a coredroid issue or even an issue coredroid can fix??
Click to expand...
Click to collapse
I ended up downloading Vlingo from the market. Voice dialing now works fine with my bluetooth Motorola roadster.
Sent from my Desire HD using Tapatalk
Are you able to use the bluetooth button, with the screen off, to initiate a dial?
I can't seem to find anything that works well to leave the phone in my bag in the back seat, and make a call.
so... I think I've narrowed down my issues with newer ROMs coming out and my bluetooth not working in the car anymore. just a little background information,
- 2011 Toyota Camry SE w/ JBL Audio
- Verizon Galaxy Nexus using various ROMs
prior to any newer releases, I would use voice/audio over bluetooth, ran great without a problem. I didn't get metadata on screen but was ok. pandora, spotify, notification sounds, google music, etc... worked like a charm.
well... now I noticed that only voice calls & google music work over bluetooth connection in the car. I thought this was first an issue with pairing the device to the car, so I deleted all the profiles in the car and redid connection on phone. I still couldn't get sound out of any other media application i.e.; pandora, youtube, notifcations, spotify, etc... I could only get google music to work correctly. the apps not working look like they are playing, I turn off bluetooth on phone and it continues playing, but when bluetooth is on I hear nothing.
so after researching, I see that majority of new releases include AVRCP 1.3 which pushes metadata to the displays. I noticed this now works with google music, but I can't for the life of me figure out how to get other media services working properly. I've researched on RW, Google, other Android forums and can see some have similar issues, but the thread soon dies. [/background]
can anyone tell me if I can use an updated ROM with AVRCP 1.0 instead of AVRCP 1.3 to test? does anyone have suggestions I could try to get other media services working? thanks!
RBalber said:
so... I think I've narrowed down my issues with newer ROMs coming out and my bluetooth not working in the car anymore. just a little background information,
- 2011 Toyota Camry SE w/ JBL Audio
- Verizon Galaxy Nexus using various ROMs
prior to any newer releases, I would use voice/audio over bluetooth, ran great without a problem. I didn't get metadata on screen but was ok. pandora, spotify, notification sounds, google music, etc... worked like a charm.
well... now I noticed that only voice calls & google music work over bluetooth connection in the car. I thought this was first an issue with pairing the device to the car, so I deleted all the profiles in the car and redid connection on phone. I still couldn't get sound out of any other media application i.e.; pandora, youtube, notifcations, spotify, etc... I could only get google music to work correctly. the apps not working look like they are playing, I turn off bluetooth on phone and it continues playing, but when bluetooth is on I hear nothing.
so after researching, I see that majority of new releases include AVRCP 1.3 which pushes metadata to the displays. I noticed this now works with google music, but I can't for the life of me figure out how to get other media services working properly. I've researched on RW, Google, other Android forums and can see some have similar issues, but the thread soon dies. [/background]
can anyone tell me if I can use an updated ROM with AVRCP 1.0 instead of AVRCP 1.3 to test? does anyone have suggestions I could try to get other media services working? thanks!
Click to expand...
Click to collapse
I think it's AVRCP 1.3 in CM 10 based roms that breaks this. I just switched to jelly belly 9 (4.1.2) which rolled back bluetooth profiles back to AVRCP 1.0 and pandora etc. works but without media info obviously. I also saw a AVRCP 1.3 patch for Pandora somewhere that may make it work. It's possible that the problem isn't that the ROM is not compatible, but that the Apps aren't.
osurferx said:
I think it's AVRCP 1.3 in CM 10 based roms that breaks this. I just switched to jelly belly 9 (4.1.2) which rolled back bluetooth profiles back to AVRCP 1.0 and pandora etc. works but without media info obviously. I also saw a AVRCP 1.3 patch for Pandora somewhere that may make it work. It's possible that the problem isn't that the ROM is not compatible, but that the Apps aren't.
Click to expand...
Click to collapse
Ok... I've confirmed it has to be AVRCP 1.3
Last night I took advice. I installed Jelly Belly 9 "4.1.2" w/ reverted AVRCP 1.0 because of BT issues, and this morning I went to work, tested connection with BT and everything worked! So... Looks like the issue lies with AVRCP 1.3. I don't see metadata on screen anymore but it doesn't bother me, I'd rather have all other media players working.
To touch on what others are saying, statements Google Music works perfectly fine with AVRCP 1.3 based ROM's as well as voice through BT. It's just the other media players i.e; pandora, slacker, youtube, notifications, etc.... that don't work. I'm guessing from what I read, is that the applications do not support AVRCP 1.3 and will not push to Toyota head units properly. Not sure if this is going to get fixed or not, but sucks because this limits what I can/can't use for ROMs at least a solution was found and reason why. Thanks bud!
You could also try https://github.com/loganakamatsu/PandoraAVRCP for the Pandora patch. Maybe patches exist for other apps as well...
I read on another thread that any app that supports the Scrobble Droid API hxxp://code.google.com/p/scrobbledroid/wiki/DeveloperAPI will pass the meta info to AVRCP. So I assume if you install ScrobbleDroid app hxxps://play.google.com/store/apps/details?id=net.jjc1138.android.scrobbler&hl=en from the play store any app that it is compatible with will also pass the meta info to the display.
As noted, Pandora is not supported as it does not broadcast its intents. I personally had issues getting the PandoraAVRCP github to patch. If anyone has a patched pandora.apk, I would certainly appreciate a PM.
Good luck.
I have a Nexus and am running the most recent Paradigm (though I am reading the ROM doesn't make a difference). When I am in my truck, which has bluetooth for the phone, my google voice typing (in SMS and anything else) does not work. As soon as I turn off bluetooth it works fine.
This thread explains the same thing:
code.google.com/p/android/issues/detail?id=35737
Is there a ROM that has this fixed?
Bluetooth router of A2DP to mono 'Hands Free' protocol used by older phone bluetooth adapters.
All similiar apps on Google Play either froze, crash or just did not work on Samsung Galaxy Express I8730,
so i developed one myself specifically targeting Jelly Bean 4.1.2 requiring minimum ver 4.0.
Still Beta and under improvements but seems to work fine on Samsung Galaxy Express GT-I8730 XXAMH1.
I can now hear WAZE navigation instructions loudly enough, while playing music on the car stereo
Share your experiences, Thank you
Bluetooth Router 4+ minor update
After testing on many devices here is a minor update.
Application is now Zipaligned for lower memory footprint and Activity is now "single instance".
If notification fails to appear the "routing" failed - try to disable and enable again - if still no notification then
this app is not compatible with your device.