Hey there,
I'm having a problem with the bluetooth on my desire...
I'm running stock android 2.2, unrooted...
The phone seems to work totally fine, but the bluetooth refuses to connect to my car kit... it has worked fine from day one and now all of a sudden it connects for a few seconds and then disconnects, and then when you go into the bluetooth settings to re-connect it, the menu just hangs... if you leave it for a few seconds the phone then reboots...
TrueTenacity said:
Hey there,
I'm having a problem with the bluetooth on my desire...
I'm running stock android 2.2, unrooted...
The phone seems to work totally fine, but the bluetooth refuses to connect to my car kit... it has worked fine from day one and now all of a sudden it connects for a few seconds and then disconnects, and then when you go into the bluetooth settings to re-connect it, the menu just hangs... if you leave it for a few seconds the phone then reboots...
Click to expand...
Click to collapse
Hi,
Have a look here: http://forum.xda-developers.com/showpost.php?p=9511037&postcount=2
jmelhus said:
Hi,
Have a look here: http://forum.xda-developers.com/showpost.php?p=9511037&postcount=2
Click to expand...
Click to collapse
THANK YOU so much! That looks like it'll do the trick, now my only problem is how the eff do I install it? I've tried to copy it to the root of the mem card but it looks like the recovery thing on my phone is toast... even though it's got stock firmware on it...
Will it be easier to root the phone?
Ok, I am now Rooted and running LeeDrOiD 2.2f which apparently includes the Bluetooth fix as mentioned above...
But the problem persists...
It's definitely not the radio, because it pairs and works perfectly with another phone.
Any other ideas?
TrueTenacity said:
Ok, I am now Rooted and running LeeDrOiD 2.2f which apparently includes the Bluetooth fix as mentioned above...
But the problem persists...
It's definitely not the radio, because it pairs and works perfectly with another phone.
Any other ideas?
Click to expand...
Click to collapse
Which bluetooth fix is implemented in leedroid? I would rather recommend you a cyanogenmod 6.1 ROM, or a ROM that's built on CM. For me this fix implemented there has worked. FYI, CM are AOSP and without sense.
Sent from my HTC Desire using XDA App
The fix is "[MOD][21-July] Fix Bluetooth CarKit disconnection" and apparently fixes the issue...
Hmm, I kinda like the sense interface so would be sad to see it go...
My Desire also has a bluetooth problem in connecting with my car. Not the disconnections, but phonebook/callist access fails. Installing an AOSP Rom (or MIUI) fixes the problem, but I do like sense too.
I've concluded the sense-bluetooth stack is the culprit, however I don't have the knowledge to change the stack. Thus, I'll wait until somebody has fixed it or HTC updates the stack or until I'll buy a new phone
I am happy to say that the problem is gone when using Cyanogen Mod 6.1.0
It doesn't transfer the phone book, but the phone function works... so I'm happy...
Just have to now get used to android without sense... hmmm...
TrueTenacity said:
I am happy to say that the problem is gone when using Cyanogen Mod 6.1.0
It doesn't transfer the phone book, but the phone function works... so I'm happy...
Just have to now get used to android without sense... hmmm...
Click to expand...
Click to collapse
Hi, as i am having the same issue and dont really want to use a Cyanogen rom , before i do what vehicle did you get it to work with.
cheers
It was with a Pioneer DEH-P710BT head unit with built-in bluetooth...
The strange thing is that it worked absolutely perfectly for MONTHS and now all of a sudden is giving problems...
It is however, definitely the phone giving the problem because the head unit pairs perfectly with any other phone, and when using the cyanogen mod rom, the desire works perfectly with it.
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Aerowinder said:
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Click to expand...
Click to collapse
Yeah, that bug alone didn't happen when I first started using 10.1. Not sure when it started to be honest.
Update google search for the keyboard I think
mt3g said:
Update google search for the keyboard I think
Click to expand...
Click to collapse
That's very possible. It's one of the first things I try when I get the latest nightlies, so I probably try it each time before I have updated anything.
Is there any reason to think that the hot-spot issue will be resolved in 4.2.2?
Ya, and I don't know, it might be coding that is needed within AOSP, does wifi tether encrypted not work on the Nexus 4 or GNEX?
Just an update for anyone who is searching and finds this thread by some chance...
It looks like 4.2.2 did not fix the HotSpot issue, but it did fix the Bluetooth streaming. I tried the SmoothRom 4.2.2 release, to test these things.
PAC-man rom 4.2.1 is my current favorite rom, and they did somehow fix both of those issues recently. Probably had something to do with 4.2.2's release this week. So if someone is looking for a 4.2 rom with working Bluetooth, and WiFi tether encryption, you might want to give that rom a try.
It is right here:
http://forum.xda-developers.com/showthread.php?t=2015525
4.2.2 has working everything. On Liquid Illusion you need to flash a custom kernel that is updated to have encrypted hotspot.
Sent from my SGH-T999 using xda premium
ArkAngel06 said:
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Click to expand...
Click to collapse
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
milesmarrero said:
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
Click to expand...
Click to collapse
Thanks for the info, but updating to the newest Google App from the PlayStore fixed it for me.
Your solution would probably fix the need to reflash.
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
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
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.