Is there any way to tell what version bluetooth is on a rom? I use a fitbit flex which needs blutooth 4.0. Any roms ive tried that are android 4.2 or 4.3 doesn't work with the flex. I would love to figure this out so I could use the newer software and still be able to sync my fitbit. Thanks
eeyore6802 said:
Is there any way to tell what version bluetooth is on a rom? I use a fitbit flex which needs blutooth 4.0. Any roms ive tried that are android 4.2 or 4.3 doesn't work with the flex. I would love to figure this out so I could use the newer software and still be able to sync my fitbit. Thanks
Click to expand...
Click to collapse
Which 4.3 roms haven't worked for you? Technically speaking they should all work, but I know Vanir didn't. CM10.2, PAC, Slimbean and others worked for me with my devices. I just remember Vanir not working even though it was 4.3.
Anything thats been 4.2 or 4.3. I know the cm I tried, a pacman one too. Fitbits website said with custom roms there have been some issues implying they didnt have the correct drivers. I have a jedi thats working but that goes back to 4.1. On the other roms when I go into the fitbit app to sync, the button to the right up top you would click to sync, never shows up on the 4.2 and 4.3 roms.
To clarify, my bluetooth to talk on the phone works but the software to sync up with the fitbit itself on the app does not work.
Probably use the application manager in settings and see the BT apk version.
You have to edit your build.prop to reflect one of the white-listed product models...
See: http://forum.xda-developers.com/showthread.php?t=2436260&highlight=fitbit+sync
Related
I have a d2tmo GS3 and been running CM10 nightlys. It is alright but I sometimes have BT trouble between the phone and the car and so I am looking to see if there is another ROM that will work better for me.
I am mainly looking for a relatively vanilla JB ROM. Don't need or care to much about fancy stuff. Its ok if it has extra features as long as they don't cause problems. More than anything else, I want a stable ROM that works correctly.
There are two problems I am having with BT.
The first is that the phone does not always auto connect for music with my car. It used to also have trouble connecting for phone, but a recent nightly build seems to have fixed that.
The second is that when it does connect, it automatically starts playing a random file (it did this with the stock ROM as well). For some reason my Nexus S didn't do this with either ICS or JB vanilla Android. My understanding is that this is cause the phone is getting an autoplay signal from the car. I am hoping there is an Android version that can be set to ignore this request.
Frosty.
aviphysics said:
I have a d2tmo GS3 and been running CM10 nightlys. It is alright but I sometimes have BT trouble between the phone and the car and so I am looking to see if there is another ROM that will work better for me.
I am mainly looking for a relatively vanilla JB ROM. Don't need or care to much about fancy stuff. Its ok if it has extra features as long as they don't cause problems. More than anything else, I want a stable ROM that works correctly.
There are two problems I am having with BT.
The first is that the phone does not always auto connect for music with my car. It used to also have trouble connecting for phone, but a recent nightly build seems to have fixed that.
The second is that when it does connect, it automatically starts playing a random file (it did this with the stock ROM as well). For some reason my Nexus S didn't do this with either ICS or JB vanilla Android. My understanding is that this is cause the phone is getting an autoplay signal from the car. I am hoping there is an Android version that can be set to ignore this request.
Click to expand...
Click to collapse
I'm actually having the same problem with auto-connect I have a thread going as well. I am running wicked JB which is TW based so close to stok and thats my only problem so far
Just to be clear, when I say "vanilla JB" I mean JB like google intended, not neccesarilty GS3 stock rom.
psykhotic said:
Frosty.
Click to expand...
Click to collapse
Does Frosty allow your phone to ignore BT autoplay requests?
Wicked
Sent from my SGH-T999 using xda premium
Frosty or Wicked. Both have been very stable for me.
Frosty is incredible give it a shot.
Does anyone know if the Bluetooth SMS MAP protocol is supposed to work in 4.2.2 AOKP (I'm running milestone 1)? My Honda Civic doesn't think the phone supports it, so I'm guessing it's not working, but wanted to make sure there wasn't something I was missing. Also, I'd love to know if anyone is working on it or knows what the status is. I moved from an old hacked-up CM10.1 over to AOKP hoping maybe this had been fixed/was working, but alas, it looks like I'm still out of luck.
If I had more time, I'd offer to fix it up myself (and may still) if someone could point me in the right direction to get started. From what I saw in old posts back during the CM9 days this was working, so it seems that it'd be possible to revive without too much deep knowledge of the protocol itself (some already did the hard work)...
-Daniel
Okay, does anyone know if any of the 4.2.x ROMs support bluetooth sms map?
dath1974 said:
Okay, does anyone know if any of the 4.2.x ROMs support bluetooth sms map?
Click to expand...
Click to collapse
well there are known bluetooth issues with 4.2.2 roms
I have a bluetooth headset which seems to work fine...
however I have a bluetooth mouse which recognizes but doesn't work in 4.2.2 roms
All 4.1.2 roms built off official stock seem to have bluetooth working fine...
hope this helped m8
In JB, a new Bluetooth stack was implemented. The MAP profile code, which was added to AOKP in ICS, is no longer valid. From what I have read, the new BT stack is not open source, so devs will not be able to reimplement MAP, at least for now.
Sent from my SGH-T959 using Tapatalk 2
So I've tried every custom ROM for my E973 and I've noticed something odd. The ROMs built using the team LGOG tree seem to have an issue initializing bluetooth. It takes about 6-7 sec for bluetooth to come on, and android beam file transfer doesn't work. On the other hand, with Paulicat's AOKP and dvhexer's CM 10.1, bluetooth initializes within a second or two and android beam works fine. Is this down to drivers or some other difference in the bluetooth implementation? Would it be possible to create a flashable zip to apply to the ROMs with slow bluetooth to make it faster/more stable?
r.asimi said:
So I've tried every custom ROM for my E973 and I've noticed something odd. The ROMs built using the team LGOG tree seem to have an issue initializing bluetooth. It takes about 6-7 sec for bluetooth to come on, and android beam file transfer doesn't work. On the other hand, with Paulicat's AOKP and dvhexer's CM 10.1, bluetooth initializes within a second or two and android beam works fine. Is this down to drivers or some other difference in the bluetooth implementation? Would it be possible to create a flashable zip to apply to the ROMs with slow bluetooth to make it faster/more stable?
Click to expand...
Click to collapse
man, Still haven't had a response.
For what it's worth, I'm in the same boat as you. AOKP and AOSP will work everytime. Everything else won't work as well as stock. I got nothing to report that fixes bluetooth. If you find out why, let me know.
I use bluetooth a lot.
mathsz said:
man, Still haven't had a response.
For what it's worth, I'm in the same boat as you. AOKP and AOSP will work everytime. Everything else won't work as well as stock. I got nothing to report that fixes bluetooth. If you find out why, let me know.
I use bluetooth a lot.
Click to expand...
Click to collapse
Try dvhexer's cm 10.2
I was the kind of guy who want to try some of the new version for this phone...
One issue I saw on each version except the original from bell is ... the bluetooth is not always working propely... not sure if @tdm can see the difference between v20f and cm bluetooth but since i'm back with this one i don't have to fight to have it connected to my car radio!
Anyone else having issue like mine??
Sent from my LG-P930 using xda app-developers app
Even the stock Gingerbread firmware wouldn't work with bluetooth keyboards (the stock ICS just cops out and has a message pop up that says that the phone is not compatible with bluetooth keyboards!). I found that only Cyanogenmod 9 RC1 and RC2, and Cyanogenmod 10.1.x stable builds work with bluetooth keyboards. Try Cyanogenmod 10.1.3 and see if that fixes the bluetooth problem.
handofstand said:
Even the stock Gingerbread firmware wouldn't work with bluetooth keyboards (the stock ICS just cops out and has a message pop up that says that the phone is not compatible with bluetooth keyboards!). I found that only Cyanogenmod 9 RC1 and RC2, and Cyanogenmod 10.1.x stable builds work with bluetooth keyboards. Try Cyanogenmod 10.1.3 and see if that fixes the bluetooth problem.
Click to expand...
Click to collapse
I have also experienced no bluetooth issues with Mokee 02072014 release version. Very reliable, bluetooth works like stock, no BSODs or reboot problems, and best of all its Kit kat.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
I have also experienced no bluetooth issues with Mokee 02072014 release version. Very reliable, bluetooth works like stock, no BSODs or reboot problems, and best of all its Kit kat.
Click to expand...
Click to collapse
I should try that version.
HoNo!'s almost-stock V20F and Sphinx 4.1 are the ones I found to have a reliable BT connection to FORD Sync, automatic connection. Everything else I tried I have to manually connect it and sometimes I have to do it 3-4 times to get connected with the exception of Carbon ROM which is pretty much 1 shot and it would be connected. I wouldn't even care for BT if it is not for the cellphone use bylaw in our town.
Hi, I have a Chevy Volt and a Galaxy Note 2. When I was on a 4.1.2 based ROM, the integration with the car worked automagically (once BT paired). I recently updated to a 4.4 ROM (OmniRom), and now the link is broken. I can play audio through the BT as before, but the push to dial commanding will no longer dial the phone. The car just says "dialing failed", but the phone never even tries to dial! I think this may be a 4.4 issue because I had the same problem with another 4.4 CM based ROM.
Anybody have similar experiences, know of a workaround or way to get it to work?
Thanks!
lrsmr2 said:
Hi, I have a Chevy Volt and a Galaxy Note 2. When I was on a 4.1.2 based ROM, the integration with the car worked automagically (once BT paired). I recently updated to a 4.4 ROM (OmniRom), and now the link is broken. I can play audio through the BT as before, but the push to dial commanding will no longer dial the phone. The car just says "dialing failed", but the phone never even tries to dial! I think this may be a 4.4 issue because I had the same problem with another 4.4 CM based ROM.
Anybody have similar experiences, know of a workaround or way to get it to work?
Thanks!
Click to expand...
Click to collapse
Probably just go back to a Touchwizz based rom (Lots of 4.3 available) and you should be fine. But there may be other options but thats a suggestion
Yes as a test, works on 4.3, but
As a test, I loaded a 4.3 ROM and after I set the BT options for both media and phone it worked fine. I'm going to reload a 4.4 rom and see if it was simply that I did not have the BT set for audio and phone. duh.
Remember to update once you've tried it out. Could help out others in your situation.
no 4.4 yet, plan to though
Still running 4.3. SkyNote works pretty well, so I'm reluctant to move now.
Lots of threads about 4.4 BT problems. Sorry.