Hello everyone,
I have a problem with 2 Android smartphone, both with Android 6.0.1. One is an Alcatel Idol 4s and the other one a Samsung Galaxy s7.
I read on the internet and many forums that several people are having the same problem as me. I think it's linked with Android 6.0.1 but not sure.
My problem is, the bluetooth randomly shut down on the smartphone and launch again, resulting in disconnecting the handset connected to it (and so stopping the music). This problem occurs quite often, sometime after 1 hour, sometime every 3 mins.
I would like to know if anyone else has that kind of problem, and if any fix i known for now cause actually nothing i tried worked...
Thanks for your help!
Related
Alright, I've been scouring the net for a solution and tried various things here but I am at my wits end. My laptop (Dell XPS 15 9530) will not connect with my Galaxy Note 10.1. Now get this, before I rooted my tablet, connecting the two behaved as expected. After rooting, all that happens is the disconnect sound from Windows 8.1 playing repeatedly.
I've noticed a similar issue with my Galaxy Note II, also rooted. I managed to find a workaround for that, it's not stable though and it doesn't seem to work with my tablet.
Link to workaround:
http://forum.xda-developers.com/showpost.php?p=43304157
Please tell me that I'm not the only one with this issue and more importantly, how to fix it. I'm quite limited if I can't connect these two devices.
Well, I feel pretty silly. The issue was the cable. It's just surprising because I tried 3 different cables prior. Just decided to try one more that I had laying around for sh$ts and giggles, and voila, all issues gone. I've spent the better part of the last week on this...
LOL
This almost happens to every samsung`s user. It happened to me a lot of time.
I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk
Recently bought this tablet and sometimes webpages seem to hang when loading. In Twitch I can use source quality with no problem but every now and then it just freezes and continues playing, same for medium and up. (buffering?). I don't have this problem on my pc or on my phone. What I did to my tablet: updated to latest firmware which is lollipop, and rooted it. That's it.
My question is if this problem is common? I don't think it's my WiFi causing it.
Even if you don't know, could you verify using Twitch and see if you have the same problem as described, it will help me out and I will probably do a factory reset if this only occurs with me.
Thanks in advance guys!
you will have to go to the other forums... this is too advanced for us
Pretty sure this is the general and Q&A forum, and even so, asking if the WiFi is a common problem is too advanced? Lol wut
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I sometimes have issues reconnecting to my bluetooth headset (fixed by repairing) but no issues when it is connected. And I have a moto 360 always connected that has no disconnection problems. I would go with a factory reset!
Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I know this is several weeks old, but yes I have this issue, and have done everything imaginable to get rid of it, to no avail.
My phone pretty reliably connects to my 360 (or, currently, Pebble), but is almost useless in my car. Fine for phone calls, but audio works 1 time out of 5 at best, otherwise it just does thta jumpy skip thing.
I initially thought it was because of Android Wear -- connecting to the watch was using too much bandwidth and interfering with the ability to talk stream audio -- but a) it's ONLY aproblem in my car (and my wife's car, so it's not JUST my car), never to, like, a standalone bluetooth speaker, and b) I completely wiped my phone and didn't install Android Wear or pear with a watch at all, and the problem resurfaced. A clean wipe almost always results in reliable bluetooth for 2 or 3 days, and then it gets jumpy, which HAS to be a clue (some state or buffer being corrupted / filled?) but I haven't been able to figure out what it's clueing me into.
This thread dives into the potential Android Wear connection, but no real solution.
If anyone who HAS experienced this figures out a solution, I'd really love to hear it.
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
insanedc said:
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
Click to expand...
Click to collapse
I can usually toggle off Bluetooth then back on and it's okay, but sometimes it does require a restart. SUPER frustrating when you're driving! I'm glad I'm not the only one, I just wish we'd get more info on this and maybe someday a patch.
Hey everyone,
I checked the similar threads but it seems everyone else has issues while playing music. My issue is only during calls.
Very often, almost every time, I have my V20 connected to a car through Bluetooth I get a really bad stuttering during calls. It is pretty much impossible to take a call like this. Sometimes the problem will go away but most of the time I just can't take any calls through Bluetooth. This has happened on a 2012 and a 2016 Toyota Prius C.
I recently got the Jaybird X3 and I experienced the same issue. Which leads me to believe that the issue is with the phone and not the car. I have a Note 4 and I never experienced this issue.
I tried stopping the Bluetooth system app (apps?) and clearing the cache and data but the problem is still there. I mention apps because I see 2 Bluetooth apps. One says its version 7.0 and the other one version 5.30.13. It seems both are active since both have memory used in the last few hours.
I've also tried the unpairing, deleting, and pairing the phone several times and the problem persists.
To be honest the problem is really annoying to the point I've considered getting something else. It is just frustrating to not be able to take calls over BT.
Anyone else having this issue? Is it maybe just my phone? Any ideas what could it be or how to solve the issue?
Thanks
I tried the phone with a MB CLA 250 and the issue is still there.
I also noticed there is a lag on the audio both while listening to music and while playing a video. It is more noticeable when playing a video since the audio is clearly out of sync by about half to one second.
Any ideas? Anyone else experiencing this?
Or is it just me?
I can't say I've had this problem. What model v20 do you have? Are you stock or rooted (and if rooted, what ROM/kernel)?
I also have 2 system BT apps but one of mine differs from yours - 5.30.12.1
I'm using a rooted VS995 with a stock 11a rom and the NSSR 5.5 kernel.