Has anyone else had problems using Bluetooth tethering with your Nexus 5?
I can pair just fine and have no problem accessing the Internet etc. initially; however, after a 5-20 minutes of use the phone stops forwarding bluetooth packets to the Internet. The phone's Internet connectivity remains and Chrome on the Nexus 5 works flawlessly. If I disconnect the PC I'm connecting to the my Nexus 5 and try reconnect then I'm unable to do so. Instead I have to turn the Nexus 5's bluetooth off and enable bluetooth tethering again.
This is my second Nexus 5 as the first one was RMA'd. My first device also had this exact same issue; and was one of many issues that caused me to RMA in the first place. However, given that this is happening again, it looks like this is likely some sort of driver bug rather than anything related to hardware.
I'll root the device and get some proper packet logs (in addition to kernel logs) when I get a chance. For now... has anyone else experienced this?
Interesting. I am having Bluetooth tethering issues with my Wimm, thought maybe T-Mobile was blocking, but hotspot worked fine and they said they weren't. Keep us posted.
Typed on the Nexus
Related
Hi!
Since Honeycomb 3.2 there is an issue with bluetooth tethering. The first time it works, but after disconnecting you won't be able to reconnect until you have rebooted the Xoom!
That's absolutely annoying... And I think at least for root-users (like me) there should be another way.
I couldn't find any fix on the internet. But I think it should be possible to maybe reload the bluetooth kernel module or something. Maybe it's mobule bcm4329? Does anyone know how to do that (modprobe doesn't work).
Or are there any other ideas?
Greetz
McDV
McDV said:
Hi!
Since Honeycomb 3.2 there is an issue with bluetooth tethering. The first time it works, but after disconnecting you won't be able to reconnect until you have rebooted the Xoom!
That's absolutely annoying... And I think at least for root-users (like me) there should be another way.
I couldn't find any fix on the internet. But I think it should be possible to maybe reload the bluetooth kernel module or something. Maybe it's mobule bcm4329? Does anyone know how to do that (modprobe doesn't work).
Or are there any other ideas?
Greetz
McDV
Click to expand...
Click to collapse
My bluetooth connection wasnt reliable with bluetooth tethering either. I found though that when i did tether id only use the connection for like 30 minutes at most. If thats the case you should update to the latest version of wifi tethering from google v3.1 beta. Because when you tether wifi with that it tethers in infrastructure mode instead of ad-hoc that way your xoom can see it and connect with no problem. its completely reliable for me. And works flawlessly. ive had countless issues using bluetooth (Almost never was able to connect to network. only able to be paired)
if you do go that route. After connecting your xoom, make sure you have access control checked and that your device is in the list and enabled in wifi tethering then save.
Generally WiFi-Tether is no problem. I'm accessing the internet through my HTC with CM7 and Gingerbread offers WiFi-Hotspot by stock. But the point is, that this really drains your phone's battery if you just leave it connected.
Using Bluetooth-Tethering with the root-app Wireless Tether installed on my phone, the battery lasts much longer. Of course the connection is slower, but for mails etc. that doesn't matter. With Honeycomb 3.1 it worked great, but since 3.2 it simply won't reconnect until you reboot... You can even unpair and repair the devices etc., it doesn't help. After rebooting the Xoom it connect like a charm...
I think there has to be a way to just restart the bluetooth-module or something... But I don't know how.
Hey guys,
is there no one out there, who can help? If you search the internet, you find a lot of people, who are having this problem - no one even has a workaround.
The fact is, during reboot all the services and kernel-modules are reloaded (of course). So if s.o. could just say which service/module is responsible for bluetooth-tethering and how to restart/reload it without a reboot, this could already be very helpful!
I have an idea!
OK, I'm a little stuck, but I've got new information.
Obviously it's a DHCP-issue. Seems like the DHCP-client on the Xoom doesn't pick up a new IP anymore... If you type netcfg in a terminal emulator, you'll find that.
With su dhcpcd you often can push it get an IP! Then, after that, you sometimes can connect several times without problems, but connecting to WiFi again can be problematic...
Any ideas? Is there another way to make the dhcp-client get an IP?
My idea is to set up a static IP for that interface bnep0, but I can't find the proper config-file... Can someone tell me how to set up a static IP only for that single interface?
i am running wireless tether 2.08 which has Bluetooth wifi built in and I also have the same issues. Hopefully someone will come up with a fix for this. I kind of prefer running my Evo with Bluetooth than wifi since it does not run hot
No one has found a fix, yet?
The connection is not dropped anywhere: 3G stays connected on the phone and the wifi signal is strong groing from the nexus/hotspot to the laptop connected to it and is not dropped.
But after a while, the laptop starts to get no data at all from the phone (as in, it requests data but nothing comes back). The laptop is fine as it works with no problems using my home's router via wireless.
I can usually ping the nexus fine when this problem occurs, but pings to the outside do not go through, as you'd expect.
I end up having to restart the hotspot function (a phone reboot fixes it too). Does anyone know what might be the problem? Or how I could troubleshoot it?
The nexus one is running CM 7.0.3. Google did not reveal any results (or I failed to find the correct keywords)...
So this has been one of the annoyances I've had with android for awhile but never really put any research in to it to know if its normal, or more so - why this would be normal. If I want to connect to certain devices that run as a wifi hotspot, but don't provide internet access - android does not appear to use those connections. The workaround seems to be to disable cell data and then I can connect to the device. Currently on a Nexus 6p on 7.1.1. The wifi will connect, but i can't hit the device unless I wack cell data. I guess really the two questions that matter are 1) is this normal? and 2) is there a workaround? Tried it on the fiance's iphone and it works without issue.
-Chris
This is my second phone to have this problem. First was my old S4, now my S7 has the same problem. Basically, I want to watch YouTube or Netflix on my phone over Wi-Fi, and I want to listen to it on a bluetooth headset. But after a few minutes of watching/listening, my Wi-Fi connection always dies, I get that little exclamation point next to the Wi-Fi symbol in my notification panel, and the only way to fix it is to turn off Wi-Fi and turn it back on. It'll work for another couple minutes, then die again and need to be reset. Bluetooth stays connected the whole time and never drops. It's just the Wi-Fi that gets dropped. If I turn Bluetooth off and just listen via phone speaker or wired headphones, no problem, Wi-Fi can cruise all day.
The research I've done suggested that 2.4GHz might be causing a problem, but my network is 5GHz. Another suggestion was to switch the phone to a static IP address, that didn't help. I'd also read that Android has problems with IPv6, so I went to disable that in my router and discovered that it's never been on.
So, I found three solutions on my own, and none of them worked. Now it's time to reach out to the brain trust here. Does anyone have any idea what might be the problem? Vanilla S7, no root or ROMs. Thanks!
dstarr3 said:
This is my second phone to have this problem. First was my old S4, now my S7 has the same problem. Basically, I want to watch YouTube or Netflix on my phone over Wi-Fi, and I want to listen to it on a bluetooth headset. But after a few minutes of watching/listening, my Wi-Fi connection always dies, I get that little exclamation point next to the Wi-Fi symbol in my notification panel, and the only way to fix it is to turn off Wi-Fi and turn it back on. It'll work for another couple minutes, then die again and need to be reset. Bluetooth stays connected the whole time and never drops. It's just the Wi-Fi that gets dropped. If I turn Bluetooth off and just listen via phone speaker or wired headphones, no problem, Wi-Fi can cruise all day.
The research I've done suggested that 2.4GHz might be causing a problem, but my network is 5GHz. Another suggestion was to switch the phone to a static IP address, that didn't help. I'd also read that Android has problems with IPv6, so I went to disable that in my router and discovered that it's never been on.
So, I found three solutions on my own, and none of them worked. Now it's time to reach out to the brain trust here. Does anyone have any idea what might be the problem? Vanilla S7, no root or ROMs. Thanks!
Click to expand...
Click to collapse
Have you tried the usual first step in troubleshooting, have you tried booting to recovery and wiping the cache partition?
You can also try flashing the stock firmware for your model number via Odin.
Sent from my LGL84VL using Tapatalk
Hi,
I have recently (last week) joined the OnePlus party by getting myself the 7 Pro after being with Samsung since the S2 days.
I like the phone but there are a few issues I am having.
The main issue I am having is the Bluetooth Tethering. I need this for when I am in my car (Mercedes use this method for internet connectivity). I switch it on and try to connect but after a while it just tells me that the data connection is temporarily unavailable. My mobile data works fine so I'm assuming that isn't the issue. When I am parked on my drive and in range of my home WiFi and I try and connect the connection is successful. It is as if the phone is blocking the mobile data connection when accessing via bluetooth tethering. This wasn't an issue on my Note 9 using the same SIM.
Does anybody have a fix for this or are having similar issues? If this cannot work then it is a deal breaker for me and I'll be reluctantly returning the phone to Amazon.
On a side note I have even tried changing the dun status via ADB Shell after finding what was supposed fix online but it did not help.
Thanks
I am no Bluetooth expert, and it may not apply here, but there are a number of various Bluetooth settings that can be altered in the Developers setting. Maybe something there can help???
Hi Jaseman,
I shall look into that. Currently doing a full backup of the phone to my PC before doing a downgrade from Android 10 to 9. I'm hearing that 10 is buggy so I'm hoping that is the culprit.
Thank you for your reply.