So I bought my Google Play S4 from the Play store maybe 6 months ago. I unlocked it at one point to be able to write to my memory card. But I didn't run any custom roms, and I'm currently running the stock 4.4.2 rom on the phone.
After the update, I got an error nearly every startup. Realizing I hadn't cleared the cache or data since I'd updated, I did this over the weekend and that error went away. First day of use had no problem, but yesterday the phone's battery drained 85% in just 3-4 hours. I put it on a charger at work, got through my dinner plans, and went to pair the phone to the car as usual last night.
Normally when I paired my Note II or S 4, there would be the usual deal, but when it wanted to access the address book, etc... there would be a check box for "don't ask me again". Left unchecked, the phone would disconnect and reconnect to the car fairly regularly. Obviously, I'm used to leaving that box checked and accepting. But after the wipe and reload of 4.4.2, I have no checkbox. And whether I accept syncing the phone book, etc... the phone isn't staying connected to the car!
Anyone else having this problem with 4.4.2? I'm starting to wish I hadn't upgraded past 4.4, since it seemed to work fine for my purposes. And I'm already tired of the problems upgrading seems to have caused.
Same problem to me on S4 I 9505.
The phone disconnect and reconnect to the car bluetooth module regularly (5 - 10 seconds) and when is connected from car's bluetooth can't acces the adress book at all.
I wish I hadn't update yesterday to 4.4.2 and have remained at 4.3 where everything was ok.
LE:
Tested now with my second phone (HTC Desire 600 dual sim) running 4.1.2 and everything it's ok.
Seems that the big problem is in the 4.4.2 not in the car, neither in the car's bluetooth preparation module.
Hope somebody will repair this bluetooth bug soon.
HATE GOOGLE FOR THIS!!! :crying:
After many hours of searching for an workaround about this bug/issue, seems that it's a Google bug, not a Samsung.
Same (plus many others) problems with bluetooth are present in last google 4.4.2 firmwares in Nexus 4 phones.
It's an older issue, has been reported to google since the date of 30.11.2013 and seems that google didn't find a solution for this since now.
Google forum 1
Google forum 2
Related
Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
I'm working with a Nexus 7 (2013) and a Nexus 4. I've had both devices for quite awhile, the 4 for well over a year and the 7 for a year. Both are rooted and using stock ROMs, 4.4.4.
I have the two devices Bluetooth paired and sometimes connect them. For the most part, over the last year, there have been no problems doing that. Once in awhile, they won't connect, but if I reboot, they will. Now, all of a sudden, I can't get them to connect under any circumstances. They're paired. But they won't connect. They both connect to an external Bluetooth speaker and the phone connects to my car bluetooth. That happens with 100% reliability. But these devices just won't connect with each other. And I need them to for certain work related purposes.
What could have happened?
I've unpaired and repaired them a few times. I've rebooted both devices. Potentially competing Bluetooth devices (like my car and the speaker I mentioned) are turned off. The devices aren't connected to any other Bluetooth devices.
Strangely, someone I work with who's doing the same sort of thing (and whose urgency to make them work together is greater than mine) with the same exact devices as I am is having the exact same problems.
What could be going on? Please let me know if you have any ideas.
Thanks.
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
pjc123 said:
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
Click to expand...
Click to collapse
Thanks for the commentary, pjc123. At least someone said something.
I restored one of my Nexus devices to stock 4.4.3, then 4.4.4. Didn't change anything. Maybe I need to take a couple of them back to 4.4.2 or earlier and see what happens. But AFAIK, my friend who has the same problem hasn't ever even updated to those versions of the OS. And it worked fine for him, doing these Bluetooth connections on no less than a weekly basis for a year.
Google's tech support, fwiw, told me that the first thing I needed to do was to update to 4.4.4. Not that I took that as anything other than their reading off a script.
Please let me know if you ever figure anything out with this. I'll report here if I do, too.
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
pjc123 said:
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
Click to expand...
Click to collapse
Interesting. I temporarily turned XPrivacy off just for that purpose. The app that's failing for me wasn't being protected, anyway, but it doesn't matter. I can't even get to that point, because the devices don't connect, even though they're paired. Furthermore, only one of my devices even has XPrivacy installed. I can't get any two of my, or my friend's, Nexus devices to connect, even though they're all paired. And they all used to.
I'm waking up this thread again to see if anyone has any ideas. I just can't connect two Bluetooth devices anymore by using the list of Bluetooth devices in settings on a Nexus device. This prevents an app that's dependent on that from working.
I CAN connect two devices via Bluetooth using ES File Explorer and see the contents of the other device and make file transfers. But the Bluetooth icon remains unlit and the connection isn't made in the settings. Maybe it's a different aspect of Bluetooth. When I close the connection with ES File Explorer, the toast says that the OBEX connection has been discontinued.
Why would I be able to connect two Nexus devices regularly for a year, then not be able to anymore?
I've tried to get Google support on this. Unlike some companies who provide inept support, even laughably so, Google just blows off the notion altogether.
Some months later...
This problem remains unresolved. I've now tested this on multiple devices (about ten of them) running various different versions of Android. I just tried it today with another, a stock, factory state N4 trying to connect to a stock, factory state N7 (2012). I wiped the devices, reinstalled the OS and then tried to pair and connect as the very first act on the clean systems once I got past the initiation routine.. I even loaded a few different versions of Android from distant past (4.2) to present. I CAN NOT connect two paired Android devices using Bluetooth, even if they're successfully paired and Bluetooth is turned on for both devices. All these devices connect fine with things like external speakers and cars. I've shown this to Google employees, some of whom have tried it on their own devices. Nobody succeeds.
As mentioned earlier in the thread, this used to work every time on every set of paired devices, regardless of the Android version.
What could possibly be going on here?
I struggled with this for awhile today. Same symptom: the devices can pair, but will quickly go from "Conecting..." to "not connected". I eventually stumbled on the solution: one device must have internet tethering enabled. This setting is in the "Tethering & portable hotspot" section, not in the bluetooth settings. This will enable the two devices to connect, and it will also enable the second device to use the "Internet access" feature in the bluetooth configuration for its connection with the first device. Hope that helps!
After Android 5.0 upgrade my Note 3 has many bluetooth problems that stops me from using my smartwatches (Moto 360 and Pebble Time). Frequent dropped connection on bluetooth, both moto 360 and pebble can`t connect, i have problems with my car stereo, and sometimes when i push the back or home button on an app, nothing happens. Tried everything, wipe cache, phone reset, deleted cache from the Bluetooth and Bluetooth test app, factory reset the pebble and moto 360, no luck.
Android 5.0 is a big mess and i can`t use my bluetooth devices, that worked perfect on Android 4.4.4.
My phone is still in warranty, i have never done root on it, only installed stock updates, OTA, from Samsung.
I want now to downgrade back to Android 4.4.4 stock with ODIN. I want to download stock Android 4.4.4 for my Samsung Note 3 and flash it with ODIN. Can i do that?
Please help, Android 5.0 messed up my phone.
It's better to do a reset after every OTA update...
I personally feel the performance never goes down if I do a reset after update...
And I'm using my Moto 360 with my Aryamod Lollipop Note 3 (had no issues with stock Lollipop as well for 6 months)
Sent from my Nexus 7 using Tapatalk
I tried delete cache from Bluetooth and Bluetooth Test apps, factory reset from phone settings, reseted my watches Moto 360 and Pebble Time, deleted all paired bluetooth devices and paired again. Still connections are dropped, android wear says moto 360 is connected but watch is not, the same with Pebble drops connections, unable to connect, it ask for some bluetooth key, sometimes the pairing is gone by it self and i have to repair, etc., just a nightmare. Moto 360 and my car stereo worked perfect on Android 4.4. The Pebble Time is 3 days old, never worked fine on Android 5.0.
Now i did a full reset (wipe data) by restarting the phone into Recovery Mode. Contacted Samsung and i`m waiting for a reply.
I downloaded stock Android 4.4.2 from sammobile for my Note 3 LTE. If i can`t find a fix for bluetooth issues i will use ODIN and flash back the stock Android 4.4.2 ROM...
I can not believe that Samsung and Android will push out this update terrible. On the Pebble forums i see lots of users complaining about Android 5 ruined their bluetooth connections.
Just downgraded my Note 3 to Android 4.4.2 this morning. So far my Pebble Time works like a dream, no more dropped connection, no more unable cu connect, all bluetooth issues are gone.
Because i never rooted my Note 3 and downgraded to stock firmware, the downgrade process was pretty simple using ODIN, just uncheck F.reset.
great then!
Anturaju93 said:
Just downgraded my Note 3 to Android 4.4.2 this morning. So far my Pebble Time works like a dream, no more dropped connection, no more unable cu connect, all bluetooth issues are gone.
Because i never rooted my Note 3 and downgraded to stock firmware, the downgrade process was pretty simple using ODIN, just uncheck F.reset.
Click to expand...
Click to collapse
great then.. I believe there were no great features to miss Lollipop... other than the fact that Touchwiz looked better...
the biggest feature I would miss is Trusted device, so the Pebble can keep my phone unlocked and I don't need to type the PIN every time. Also S View cover issues are resolved with Android 5. So I am really not happy to downgrade. Did anybody receive any official statement from Pebble or Samsung where is the problem and when we can expect it to be resolved? There are several threads around like
sammobile.com/forum/showthread.php?t=27542
or
forums.getpebble.com/discussion/26926/bluetooth-connectivity-issue-after-android-5-0-update
but no statement
I own two smartwatches, Motorola Moto 360 and Pebble Time, and both not working on Android 5.0, but are working fine on Android 4.4.2. This is not Pebble fault. I had problems even with my car stereo with Android 5.0 , and now, after downgrade, all are working fine. My Pebble is connected for 2 days now, with no disconnect
I do like Android 5.0 and i like to keep my devices up to date, but i need bluetooth connection to work with all my devices.
Anturaju93 said:
I own two smartwatches, Motorola Moto 360 and Pebble Time, and both not working on Android 5.0, but are working fine on Android 4.4.2. This is not Pebble fault. I had problems even with my car stereo with Android 5.0 , and now, after downgrade, all are working fine. My Pebble is connected for 2 days now, with no disconnect
I do like Android 5.0 and i like to keep my devices up to date, but i need bluetooth connection to work with all my devices.
Click to expand...
Click to collapse
hey i just want to knw which firmware 4.4.2 u flashed ? and did u use LTE on 4.4.2 rom .... ?
my note 3 model is SM-N9005 and is the LTE version. I did use the last firmware available here http://www.sammobile.com/firmwares/database/SM-N9005/ROM/
L POF3 sol ce BT problems for most users......
There was OTA update last days that has resolved the bluetooth problems! Connection to Pebble is now stable!
yeah, switched to iphone 6 now. Samsung said they don't care if my watch is not working, they guarantee connections only with gear devices.
Hi All,
New here and first and my first Android headunit (Dodge 2009 Ram truck).
Purchased this unit ebay.com/itm/282734637463 on ebay Hizpo using android 7.1.
Got it and installed. While it came with no install directions, it was straight forward and went in easily. First off would like to say the quality and what does work I really like. But, I really purchased it to have Bluetooth in my truck. Being purchasing a new headunit versus adding Uconnect to stock radio, thought this was the better value.
I am having problems getting Bluetooth and WIFI to discover any of the phones I have tried (apple and android phones). After 50+ atemps Bluetooth and WIFI discovery and connection was successful only twice and only once lasted as long as about 8 minutes then failed and no longer able to see bluetooth devices again. This was on achieved after going into factory settings and changing BT adapter to No rebooting and then changing adapter setting in factory settings back rebooting. That is when it worked, but as I mentioned for a very short time and would have to go through the same process all over again for discovery and connection to only be short lived.
Have bee in contact with the ebay seller. They have been very little help. He did send me an update of which I tried to install. After I plugged USB in it found the update and reboots but on black reboot screen almost immediately I get just Error! message then reboots and tells me would I like to retry. Again after many attempts same results will not update.
Needless to say seller now making very dificult to return. If I can find a solution I really like the radio and would like to keep but being the main reason I bought for Bluetooth if I can not get it to work a $300.00 dollar waste of money.
I am hoping it is a firmware issue and can be corrected.
Any help would be much appreciated.
I have an Atoto S8, and this is my first Android powered head unit (coming from their linux-based F7, which was more of an appliance UI instead of a smart OS). I love the extra functionality it gives me, running apps and video players directly on the unit. But Bluetooth support is wonky.
My wife and I share the car, and ever since swapping to the Android powered unit, it only reconnects to whoever drove last. So if I drive the car all the time, its fine. But when my wife drives, she says bluetooth isn't working, so I have to go into settings on the BT app (BT1 as they call it) and see the three phones listed as paired (my old phone, my new phone and my wife's phone), and click on hers. Wait a bit, and then she is good to go. But then next time I drive, I realize my phone isn't connecting now, so I have to go do it again. Which means she's going to complain next time that her phone isn't working again.
I've installed a few bluetooth powered head units before, and even the Android Auto supporting F7 before this one, worked as expected: If the last device isn't available, try to connect to another recent paired one. It seems to just get stuck on the last one for some reason. Is this a limitation of how bluetooth works on these units?
have you solved this issue
i am finding it very frustrating
i thought i would solve it using the app "automate"
this would star a sequence of checks and sytematic attempted connections
but, oddly enough you cant automate the triggering o fthe flow
so it would only start if actioned
Yes, or rather THEY solved it.
Reach out to customer support. There is an update to the Bluetooth module that makes this work the way I described.
I got an A6pf in my other car and had them make an update for that one too. Much happier now.