I'm running a stock Desire and have problems with bluetooth keyboard drivers e.g. "BlueKeyboard JP" not working. I believe this is down to the stock bluetooth implementation on the Desire as other Android devices are working with the driver, including the N1.
So I can either root and use a custom rom with better bluetooth implementation or wait for froyo release. But will froyo release likely have better bluetooth? As if not, I may start experimenting with custom roms now.
I would also like to know this! I am having problems with the bluetooth in my car!
With official Froyo now just around the corner (hopefully) can anyone shed any more light on this? I want to know if my hopes are going to be dashed.
OK, an update. Having installed official Froyo, bluetooth seems exactly the same.
So no keyboard drivers are working with the Desire.
Related
Hi All
I'm trying to track down a rom which has Bluetooth DUN installed. CyanogenMod 5.0.8 test 7 has it installed but the rom is a wee bit buggy. Any recommends?
TiA
I.
Bumpty Bump
I'm just wondering, why do you need BT DUN when you have wifi tethering?
I need bluetooth DUN so my TomTom GPS can talk to my phone
Try to search "pda net" in Market. Is it what you want ?
Hi
Nope been there, tried that
It does not have full DUN, i.e. it won't talk to TomTom. Sent them a email asking for help.
IrishBiker said:
I need bluetooth DUN so my TomTom GPS can talk to my phone
Click to expand...
Click to collapse
does tomtom work on android ???
Yes, install CyanogenMod 5.0.8 test 7 and Tomtom will work with traffic updates (which is what I want DUN for). This early test is just a wee bit buggy for day 2 day use.
Its an issue that has been long outstanding:
https://code.google.com/p/android/issues/detail?id=1416&colspec=ID Type Status Owner Summary Stars
There is even a module which could be compliled, which is in 5.0.8 test 7:
http://github.com/wertarbyte/android_vendor_cyanogen/blob/omni-tether/prebuilt/common/bin/tether
pmub bump
I agree, it would be nice to have this
Might have a play see if its possible somehow. Busy schedule though, but I'll say if I have any success...
because CM5 supports it, maybe CM6 supports it, too. And if CM6 supports it, then maybe OpenDesire and DeFrost which are mods of CM6, too.
I've tried both cm6 and frost. Both from what I can see neither has it installed. Anyone else confirm?
Sent from my HTC Desire using XDA App
*UPDATE*
I've now tried both (thanks to Rom Manager) and neither have BT DUN.
Bumpty Bump
Things that go BUMP in the night
.PMUB|BUMP.
Any luck in finding anything?
So it seems Bluetooth DUN is not very popular these days (probably because most are using WiFi which is faster, in terms of speed and battery drain).
But I really need it for my new Mercedes C-class which has 'Comand Online' with internet connectivity based on BT DUN. Currently only most Nokia and Blackberry models are supported because they have native Bluetooth DUN.
Programs like PdaNet won't work because they need a client running on the device and I obviously cannot install anything on the Comand Online (no it's not a typo ) system of the Mercedes.
Any suggestions for a decent BT DUN program or Android ROM/kernel? A proper BT DUN implementation should obviously be done in the kernel. I read reports that Moto Droid X devices had success in similar scenario's and CM5 was supposed to have it in it's kernel... :-(
Anyone?
Bump...anyone?
This would be great but i think its a goooooole thing...
The only way i think thiswill happen is with a custom rom.
I'm looking forward to 2.2 but the biggest feature that was lacking in the older version was the Bluetooth Stack. Does anyone know if the OTA Froyo on the Incredible fixes the functionality of SSP?
Yes
Voice dialing through my Blue Ant Z9 worked perfectly on stock 2.2. I believe full HID support (bluetooth keyboards, etc) may still not be present in stock, and I believe it is present in Cryanogen, if you are willing to flash that.
jdmba said:
...I believe full HID support (bluetooth keyboards, etc) may still not be present in stock, ...
Click to expand...
Click to collapse
Hopefully someone can test this with the Stock version. I'll be accepting the upgrade tomorrow. I'll be flashing my phone in the future if bluetooth doesn't work properly.
Oh, and thanks for the reply.
Bingo. Froyo Fixes the Bluetooth stack. Bluetooth SPP now works with Freedom Pro Keyboard Android drivers. http://freedominput.com/freedom-accessories/freedom-pro-keyboard . If you're ever looking for a full size keyboard for your phone, this is very nice. Comes with a little phone holder too.
Now if I could only learn to type!
F. McNeely
Has anyone had any luck with the iGo slim keyboards? I've read that there is an issue with HTC's bluetooth stack but supposedly there is a way to "fix" the issue. Has anyone created an update for Froyo (or know the steps to do it manually) that would enable the keyboard?
Thanks
fmcneely said:
I'm looking forward to 2.2 but the biggest feature that was lacking in the older version was the Bluetooth Stack. Does anyone know if the OTA Froyo on the Incredible fixes the functionality of SSP?
Click to expand...
Click to collapse
on Dinc Froyo 2.2:
I cannot get my iGo keyboard or MoGo Mouse x54 Pro to work via Bluetooth.
I show paired, but the status will never switch to "connected".
hi,
i was under the (possibly wrong) impression that gingerbread natively supported bluetooth keyboards. (bt hid)
im at the moment stuck with the OTA update and cant seem to get my igo bluetooth keyboard to work.
any drivers that i can use with gb + igo keyboard?
regards,
asmd.
As far as I know, the problem has been with Sense (which was not upgraded with the OTA) and not with the version of android. I have used CM7 in the past and the HID profile works great. Maybe someone here who is using a Sense 3.0 Rom can validate if HID keyboards or even Wiimotes will work with the new Sense. My guess is no...
thanks for the reply.
Snap!! anybody know how to get a Igo bluetooth keyboard working with the current evo 4G GB OTA?
regards,
asmd.
My microsoft BT keyboard pairs, but doesn't connect. Same issue I had with froyo. Running Mikg 2.15 rom. When i tried the same with cm7, it pair perfectly. Not a complete deal breaker, but would of been nice. I recall reading previously that HID support had to be part of the BT stack. Whether the BT stack is a function of sense or not, I don't know. Practical testing suggests it is.
I realize this thread became a little bit old, but did anyone ever find a solution here? Or is Sense just totally incapable of working with a BT hid keyboard?
I just this past week got a new mini BT keyboard and was excited about all the prospects of using it. I'm currently on Sense MikG 2.5 and have been for about the last 6-8 months, after about a 6 month run on CM7.
I didn't realize, I guess, that there was such a vast difference in terms of BT HID devices. Anyway, I'd seen reference to an Anthrax kernel, but now see no way of downloading it.
Can anyone help out in that regard? And would the Anthrax kernel solve that issue? I might be looking to use the Anthrax kernel anyway.
I have been working to find a way to get my Igo connected. There was some small progress last night. I've been running sense 3.5. Last night I threw in a se of but hid files. Before it would even pair. Now the keyboard pairs but will not connect. For now I am using an ics rom to be adle to use my mouse. It connects with no problem. On sense 3.5 it pairs and connects. But it disconnects in less than a second
I'm having the same problems I have an LG Bluetooth keyboard and sadly running sense I can never get it to work aosp Roms seem to work fine though
I have been running SkyNote 8.2 for a while now and have really liked Sean's ROM. I flashed Liquid last week (also a great ROM) and noticed something that I found confusing. With the TW Bluetooth (including the stock ROM), my 2009 car didn't really react well to the Bluetooth in my Note II. The connection between the car and phone would constantly connect and then drop off, connect again then drop off. Once I was on the phone (call), after initialing disconnecting me, the connection would stay but once I hung up it would go back to the on off cycle. My contacts would not sync either and yes I did grant access to the contacts. I just assumed it was because the phone has a newer Bluetooth profile (4) than my car (3). But after flashing Liquid my Bluetooth connection was fine, never dropped off and my contacts were all visible. I don't know much about the inner workings of Bluetooth, is the difference a TW thing?
Just looking for some insight from folks smarter than me.
Bump.... I would also like to know
AOSP only has Bluetooth 3.0 right now, so that's probably why you get more information. I have a FitBit and it only works with TouchWiz since it uses Bluetooth 4.0.
This is a fairly well known issue, but I haven't see a good summary anywhere, so I'll try here.
The problem isn't so much TW vs AOSP, it is Jellybean versions 4.1.x vs 4.2.x. Touchwiz is 4.1.2 and most maintained AOSP ROMs are 4.2.x.
Google, though their ultimate wisdom, decided to effectively castrate 4.2 by switching the Bluetooth stack.
From Android.com
New Bluetooth stack
Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Click to expand...
Click to collapse
So...
Jellybean versions 4.1.x use the opensource BlueZ stack
Jellybean versions 4.2.x use the quasi-opensource Broadcom/Google stack called Bluedroid,
4.2.x has documented issues with audio streaming which are attributed to A2DP, or the Advanced Audio Distribution Profile. Google has proposed a fix, but the community consensus is that the issue remains.
Another problem with 4.2.x is that it doesn't support AVRCP 1.3 like 4.1.x did. This means that track metadata is not available to devices on 4.2. This is bad for me since I like to see track information when I connect the phone to my BMW M3.
I'm sure there are some workarounds on this problem, but I am not aware of a single, silver-bullet solution to make BT work flawlessly on 4.2.x Roms.
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Anyone know of any updates to this? There are so many 4.2.x ROMs out there that i love, but without a good BT A2DP connection, i just cant use that as the regular ROM.
ZoinksS2k said:
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Click to expand...
Click to collapse
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
It worked fine for me with KitKat.
Friday evening I upgraded to LolliPop. (Did a clean install, no data restore from backup)
Since then I have the same problem. Once you lose your Bluetooth connection it won't reconnect anymore.
You have to unpair and the repair in order to be connected again. A real pain in the ass, as I use it only for the notifications on the bracelet.
I have had a Vivosmart since the week they came out. I had a lot of the BT issues the first few months (mainly due to their software being released before it was really production ready) but has been fine since. I'm rooted and have ran a few different roms without an issue. Currently I'm using SkyDragon's Sense 7 rom. I haven't had to pair to my phone due to disconnects for at least a couple months. Are you pairing from with-in the Connect app? At one time the pairing was done via the regular android BT devices but they got rid of that and now pair from the app only. So technically your Vivosmart shouldn't ever show up on the list of installed/connected BT devices because it's only paired from the Connect app. I'm sure you've been on the garmin forum but if you haven't or someone else reading this hasn't it's here https://forums.garmin.com/forumdisplay.php?478-vivosmart. I've seen posts over there about m8 users having problems but don't remember reading if anyone was able to get the problem fixed and what they did. It doesn't make sense that it works for some (like me).
Hello,
I have same problem with Garmin Fenix 3. Apparently there is some bug in HTC ONE M8 Android 5.0.1
I am able to connect and connection is quite stable but watch wont reconnect automatically.
Usually it will reconnect once you reset BT on phone and than on watch. But its quite annoying so I am also looking for solutions. Any idea? Ive tried to add watch to trusted device under smart lock but its not working either. I know most Garmin devices worked on previous version of android on HTC ONE M8 but with Lollipop its bugged..
wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
great_lumbuey said:
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
Click to expand...
Click to collapse
Cheers for the reply i might try a few different rom's i presumed that lollipop was the issue from what your saying maybe not then i'll let you know...
I have any M8 stock lollipop and vivosmart. When vivosmart go out of range lose connection. When vivosmart come Back near smartphone, if I want to connect it, i must switch off Bluetooth and switch on manually.
It is not auto.
Can you help me?
Thank you
Inviato dal mio HTC One_M8 utilizzando Tapatalk
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Samyterje said:
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Click to expand...
Click to collapse
Solution found on my side by realizing that one dialog box is not scaled in Garmin Connect and so the "yes" button is not visible in material design. I've understood this by rolling back to Cyanogenmod 11 and see the process.
Workaround is to use a language with shorter words like english. My initial set was in French. So if it can help somebody else with Garmin Connect, use it