[Q] Bluetooth connectivity and BMW hands free no longer works with 4.3 update - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

Hello. I've only joined today as a result of the Samsung 9305 Jellybean Update 4.3.
I am on an EE T-Mobile UK i9305 LTE handset in factory condition, no rooting or any other modifications. I have just upgraded to the new update on 20 Jan 2014.
Apart from all the usual observations such as WI FI and battery life, I have another issue which I cannot find anywhere else.
Before the update and for the last year my i9305 worked fine with the bluetooth in my car. I have a 2004 X3 E83 BMW and the car paired absolutely fine. I would talk and connect with no problems. Since the update the phone connects to the bluetooth then drops after 3 seconds.
I have done the following:
Unpaired the phone and repaired;
Deleted the cache for bluetooth
Deleted the cache from the engineers mode
Samsung tells me that I now need to go to the dealer to ask them to upgrade my bluetooth software in the BMW, I explained that 1st I'm not sure if that could be done and second that would cost me money and time for something that was working perfectly fine 3 days ago for over a year. The only change is the update. Therefore I explained that there should be another update to correct this and all other problems immediately.
Has anyone encountered this issue with a car's bluetooth and anyone been able to figure out a fix. I don't really want to go down the avenue of trying a factory reset and testing if that works.
Many thanks

Havent had any issues like that with stock 4.3 and bluetooth so may or may not help but try clear the data for bluetooth share in application manager as well as un pair and re pair the device again after that has been done

Related

Milestone Wi-fi/3G connects but not send data

Hello there,
As a newcomer, I found out these foruns filled up with great information and guys willing to help, so came here to ask for some help ....I am both excited and dissapointed with my brand new Milestone. Bought the handset about 5 days ago, which came with Android 2.0. Then updated it straight away to version 2.1 via "Motorola Software Update". So far so good ...here´s the problem I am facing :
While connected to wi-fi or 3g(issue is easier to notice due to 3G icon at the task bar, which points out in those small arrows data that is being sent/received) phone stops to receive data out of the blue. All connectios are cut off(it also happens when the handset is locked up). Some basic trouble shooting i did:
- tested all pcs connected to the same wi-fi network. No issues detected for these
- reset wi-fi router configs. Didn´t work
- tried other wi-fi router. Presented same issue
- swapped another carrier chip to test 3g connection. Presented the same issue
- tested my GSM chip on ther phone. Worked properly
- Reset phone to default settings. This time the connection took longer to drop, like 30 minutes, instead of the usual 10 minutes. After the first drop, it´s started behaving the same way again.​
It seems pretty much that there an issue going on here (obvious...hehehe). I am considering the following:
- Might be a software issue. So, right now i am downgrading it back to 2.0 version, check if it works properly and then move to 2.1 hopping to get the issue fixed.
- Use retailer warranty and claim for a new phone =/​
Could you guys help me out ??
Thanks in advance and Best Regards !!!
Guys, after downgrading version to 2.0, phone stills presenting the same issue. I think it´s turning into hardware issue =/....does anyone have a clue about it?
Thanks and Best Regards!!!

Wifi turning off when phone idle or sleeping

I've got an annoying problem with my phone where the Wifi turns off when my phone is idle or asleep. This means my WhatsApp for Web disconnects and also my Moto Connect plays up too.
I've got the same problem at home, work and parents house so can't be an issue with all 3 networks. The keep wifi on during sleep option is set to Always before anyone mentions this to me.
Phone is running Lollipop 5.0 in the UK and is NOT rooted.
I noticed it doesn't happen when the phone is charging though.
Any ideas?
Right I've now tried changing the Sleep setting to Never but get the same problem.
Also tried connecting to the router via WPS but no luck.
Router is a Superhub 2. I've ruled out that it's the Superhub as I have a Samsung Galaxy S4 Mini that is running fine without a single drop out.
Definitely something Moto X related.
I've also tried on both the 2.4GHz and 5GHz bands with same results!
Try looking within the WiFi settings on the phone. Mine has this
. Added photo
Sent from my HTC One using XDA Free mobile app
Mine is identical to yours other than the fact that I don't have the wifi optimization option.
Right I've just cleared the cache as instructed by Motorola support.
Still have the same problem even after clearing cache.
Ok I can confirm that the issue goes away when in safe mode.
This is starting to piss me off as I don't have any way of checking if it's an app affecting my wifi disconnections!!!
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Wutang200 said:
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Click to expand...
Click to collapse
It's a known bug of 5.0, and already fixed for 5.1. Source, at the "Bug fixes section".
Great that you found a workarround.
Cheers!
Manuel.
Hey glad to know it's a well known bug. The work around still doesn't work. It still keeps disconnecting all the time! Driving me mad!! If the 5.1 update doesn't fix it for me, I'll need to try and get a refund and go for something else. Shame as I really like the Moto X but I can't live with an issue as stupid as this!
I'm not sure Motorola are aware of this issue at all. See their comment below from one of their support staff I'm speaking to now:
Santhosh: We have not received any reports regarding Wi-FI issue after the Android Lollipop update but please give me a moment I will provide the solution for this issue.
His solution for the issue was to get me to do a factory reset lol. I already did this when I first got updated to Lollipop!!
Going to try doing another one now to see if it actually makes any difference. Then will install a few apps at a time or something.
I am connected to WiFi just about all of time, and I have never experienced this.
Right I've done a factory reset and started completely afresh with none of my data or apps restored. WiFi has been solid; I've not had a single drop out!
I'm going to install just a couple of apps at a time and keep an eye out if the issue comes back until I find the culprit.
Hi
My phone was perfect (until now) with the WIFI since november 2014 even after I upgraded it to 5.0
But today, it suddenly starts with this problem by itself. so I restored it to factory defaults with no luck, I installed a new firmware, and still has the bug.
So, why it shows up until now by itself without any mod, app or update?
Sorry for my English.
Today I upgraded it to 5.1 and the issue persists
I had to back to stock 4.4.4. and now my wifi has been fixed so far, working good without interruption until now.
I hope this has fix the problem from sourse, and I'll wait a few days to upgrade it again.
EDIT: Has been a month since my downgrade to 4.4.4. and my WIFI still rocks.
Just want to say that I'm having the same issue since the update to 5.1. Wifi is set to be always on during sleep, but I regularly wake up my phone only to find it connected to 4G, and switching to wifi a few seconds after waking up.
I'm on a locked bootloader (unrooted of course). I did a full reset after the update...
I'm sorry to say that I've seen more little glitches since 5.1 than anything I noticed on 5.0.
EDIT: another issue I'm having is the stock mail client not syncing saying that there is no network connection. My exchange account (push) works fine however...
Just to say the issue has started for me too since the update to 5.1.
I've done 2 factory resets but no luck trying to fix this very annoying problem.
Motorola have asked me to send my phone in for repair so I'll try that and see what happens.

Wifi, Wifi tethering and Bluetooth is not working

Hi,
I have Xperia ZR C5503 phone about a year. Until 2 months ago I was using Android 4.3. When Lollipop update distributed I upgraded it to 5.0.2.(official)
But sometime after the upgrade my phone started not connecting wifi. It sees the available networks but not connecting them. The signal drops to lowest level about a second while trying to connect and it fails. Also I was using my phone's wifi tethering feature to share my internet to my pc. However wifi tethering is also not working. I enable it but I think it can't work as router. And lastly, I tried to send a file to my phone via bluetooth and it also enables but no other device sees it. I also have low sound on the phone and I can't hear people I am talking to.
So I got frustrated this saturday and downgraded to official 4.4.4. But it was same. Later I unlocked the bootloader and rooted my phone, installed recovery software. With that recovery mode I cleared all caches but the problem still countinued. Lastly I installed an unofficial modified kitkat to my phone but those problems still appears. I don't know why this phone is so problematic for me. I don't know if it is software related or hardware related. Now that my warranty is no longer valid.
Could you give me some ideas to attempt to solve these issues?
llama50 said:
Hi,
I have Xperia ZR C5503 phone about a year. Until 2 months ago I was using Android 4.3. When Lollipop update distributed I upgraded it to 5.0.2.(official)
But sometime after the upgrade my phone started not connecting wifi. It sees the available networks but not connecting them. The signal drops to lowest level about a second while trying to connect and it fails. Also I was using my phone's wifi tethering feature to share my internet to my pc. However wifi tethering is also not working. I enable it but I think it can't work as router. And lastly, I tried to send a file to my phone via bluetooth and it also enables but no other device sees it. I also have low sound on the phone and I can't hear people I am talking to.
So I got frustrated this saturday and downgraded to official 4.4.4. But it was same. Later I unlocked the bootloader and rooted my phone, installed recovery software. With that recovery mode I cleared all caches but the problem still countinued. Lastly I installed an unofficial modified kitkat to my phone but those problems still appears. I don't know why this phone is so problematic for me. I don't know if it is software related or hardware related. Now that my warranty is no longer valid.
Could you give me some ideas to attempt to solve these issues?
Click to expand...
Click to collapse
i think you must have dropped the phone because wifi and blutooth hardware in sony xperia zr is delicate , i too have dropped phone 4-5 time but still i dont have any problem with my cell , approach sony service centre because i heard may problem of XZR problem of bluetooth & Wifi after mobile accidents
rkumbhar said:
i think you must have dropped the phone because wifi and blutooth hardware in sony xperia zr is delicate , i too have dropped phone 4-5 time but still i dont have any problem with my cell , approach sony service centre because i heard may problem of XZR problem of bluetooth & Wifi after mobile accidents
Click to expand...
Click to collapse
Hi,
I had dropped my phone maybe 1 or 2 times but not from high heights.(~ a meter) But that was more than 5 months ago. I am having this issue since last 2 months and I am sure that I didn't drop or harm my phone in any way. However I wash my phone, do you think that could cause that? Just effecting wifi and bluetooth components?
It's not true about dropping the phone make that errors appear, there are many people with same issues, this phone have manufacturing problems, it's not software
My brother have same problem and he never dropped the phone. Just take a look in Sony forums.
Btw, my brother's phone lost Bluetooth connection, NFC, WiFi, Sometimes WiFi works making some pressing in the NFC spot some seconds, but sucks anyway :/
rickymanx said:
It's not true about dropping the phone make that errors appear, there are many people with same issues, this phone have manufacturing problems, it's not software
My brother have same problem and he never dropped the phone. Just take a look in Sony forums.
Btw, my brother's phone lost Bluetooth connection, NFC, WiFi, Sometimes WiFi works making some pressing in the NFC spot some seconds, but sucks anyway :/
Click to expand...
Click to collapse
How can i make the wifi stable? it drops in and out sometimes.
Wifi problem
my sony xperia zr has the same wifi problem it says scanning trys to connect the signal drops and again starts scanning..
I stopped the wifi service and restarted my phone and the wifi worked for a day and again the same proble.
Do anyone has a solution for this??
I have been facing the issue of wifi not connecting, since my upgrade to 5.1.1.
My research has led me to believe that the issue may be software based. However I'm not an expert in the field. And i was thinking of downgrading back to an older version of lollipop when the wifi was not dropping.
Can anyone advise on whether this may be a smart move, or a completely useless one?
Also is there a diagnostic protocol I can go through that could help me figure out for sure whether my wifi is busted physically, as some of you suggest here.
Thanks
Josette
I've tried the method "settings global put tether_dun_required 0" but when i reboot my Z5, the value comes back to 1 ... (and of course wifi tethering is not working, going thru USB is ok)
I'm discussing various points here. Check out everyone of this point and get a fair idea from where problem is originating.
1) Go to WiFi Settings > Keep wifi awake during sleep. Here the string value should be "Always"
2) Under stock firmware there are numerous battery optimisation. Some of them kill WiFi so battery can saved. Now disable this features if you want no drops in WiFi.
3) If both of don't work, head over to Xperia ZR General > Search for your specific device FTF. Flash it via flash tool. This should reset all wifi drivers. Don't opt or apply any battery features and use WiFi. If still issue exits then you're in bad luck.
4) Check for other WiFi access points. Check your own router's webpanel and see somewhere broadcasting and multicast signals are ticked. Also check your WiFi is at 100% of it's performance ( 100% transmit power)
5) Hardware issue. Most of the software part is not causing issues so it's safe to say a hardware issue is causing this. Now, long time ago when 5.0 was released for our device I read article regarding ZR. The user had constant WiFi drops. His issue was that his WiFi soldering was poor inside hardware. He soldered it again and his wifi drops were no longer a problem.
People also experience various bluetooth/tethering issue. It's important that people should gain knowledge about firmware flashing techniques so that device would get reset and you yourself could diagnose the problem. 1 in 0.7k unit has software/hardware issue in manufacturing. Sony provides diagnostic app, search in play store ( I'm not sure about this). Hope this answer helps many.
hii.. so did u get any solution for the problem ?
i am facing this problem since one month. i tried rebooting my phone many times. i even tried factory reset. but nothing has worked till know.
if u have any solution please inform me.thanku
Wifi Issue.
Hello Guys,
I have same issue in wifi after 1.5 Year of phone. Can you please help me on that. Does any one knows any other technician are repairing this phone? as SONY says they are not able to repair phone which even they developed. I do n't why such phones developed.
1. I have repaired phone using PCC.
2. tried reset
3. tried without stamina mode
4. tried with wifimanager app
but nothing works....
If you guys any suggestion any hope please let me know.
Thanks.

Bluetooth is driving me nuts! Need help please.....

Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.

Bluetooth Auto-connect issues...?

Hello all,
I hope everyone is fine...
Is anyone facing issues with auto-connect after pairing...
After pairing my galaxy watch and my car, connection is fine...
But if I restarted the phone or the watch or even get in the car start it...
The phone keeps asking for pairing code confirmation but never connects...
I tried removing the the paired devices but that didn't work...
Every time I want to connect to the car or the watch or anything, I have to pair. it again...
It's annoying but acceptable for the watch and other devices since after hitting pair they're connected...
But the car... I have to remove the device and add it again whenever I want to connect...
My phone wasn't tested as stock,
I immediately rooted (which was a mistake, with root, I can't tell if the root is the problem or not),
I noticed that after 2 days from rooting as it was when I decided to pair my device...
I used Dr.ketan aroma installer to root with custom magisk since it wasn't supported for note 9 (now Magisk 17 and above supports it)...
So, I kindly ask if any non rooted users have Bluetooth issues or not as well rooted users...
As I plan on re-flashing latest stock and test it then root it and test one more time...
Highly appreciated for any help...
Sincerely,
Dante
same issue happen with me, Also I rooted my SM-N960F with Dr.ketan rom.
NOW I am rooted but with stock firmware everything is fine.
Found the problem, it was Xposed, there is an issue and they released a workaround... You can find it on Dr ketan thread or github... I'll post the github link later...

Categories

Resources