Hey people!
I tried searching the forums for this issue but couldn't find anything, so if this is already discussed please forgive me and redirect me.
Anyway, when I am using wifi the 3g connection disappears (which I've set it to) but sometimes, especially after a long while, when I turn the wifi off the 3G connection won't reappear. I tried turning 3G off and on again without success. The only thing that helps is a soft reset of the phone, which is really annoying.
Has anyone else had a similar problem like this?
I did see the other thread about the 3G connection stopping and hanging, but since they at least still had the 3G connection icon in the top bar I consider this to be a totally different issue.
Anyone knows what might cause this?
Thanks!
If you carefully search, this has been discussed many times.
Basically, HTC Desire is not that good on waking up the 3G connection after turned off.
When you use WiFi, the 3G will not be turned off, but it will not be used.
Yes, it happens to me several times ... usually I just "wait" ... 1 or 2 minutes.
Other user said by turning ON then OFF flight mode will help.
Yeah ... this issue is bad
Cheers man. Waiting won't help me since I've waited up to an hour just to see what happens. But I'll try the flight mode trick
I have an interesting problem, I couldn't find this issue on anywhere else therefore I wanted to share with you;
Sometimes after 3-4 days usage (in this time period sometimes I use wireless, sometimes 3g or sometimes turn off the connection), my phone gets stuck on edge connection and never goes to 3g unless I restart it.
I tried switching air plane mode on/off and several other things. Only restart fixes this. This is not a new issue, it is happening almost for 6-7 months (on 2.1 and 2.2). It doesn't matter much to restart in a few days but I wonder anyone else has the same problem.
Am I the only one ? surprised
So I just purchased the tablet brand new about 2 weeks ago. Love it for the most part!
Over the past couple of days though, the wifi has really started to act up, and it's passing me off.. About every half hour or so, sometimes longer, sometimes shorter, the wifi will just stop working for a while. The bars will still be there, as will the little "download" and "upload" arrows lighting up as though data is still being sent and received. However, the wifi just isn't working. Pages won't load, speed test . net app won't work, nothing requiring wifi.
I usually have to go into wifi settings to disconnect and reconnect for it to start working again.
I haven't done anything different to my wifi router, and my other wifi connected devices don't seem to be having any trouble staying properly connected, so it doesn't seem like it'd be an interference issue.
Can anyone provide me with some help?
Hi,
I've had my Galaxy Nexus for over 2 years now, and never had any major problems with it. However, over the past month I've been having a problem where my network connection stops working. I can't call, text or go online. I also can't receive calls or texts. When this happens, the connectivity icon still has 4 bars (or 3 or whatever).
In the past if I had network problems, I would put it in airplane mode and then turn it off, and this would reset the connection and fix it. Now, when I try to put it in airplane mode, nothing happens. The connectivity icon disappears, but the airplane icon does not appear. Then there's nothing I can do except reboot the phone. I can't even turn airplane mode off because the option is greyed out.
At first I thought I could fix the problem by resetting the phone to factory settings. That didn't work. So 2 weeks ago I installed Cyanogenmod 11, and the problem persists.
Yesterday I installed an app called "Restart Connection", but it hasn't happened since yesterday so I'm not sure if this will work or not. The problem is not regular. It can happen twice in a day, or it can not happen for 3-4 days in a row.
I'm not sure where to go from here. I've tried Googling but can't really find anything quite like this. It wouldn't be so bad if I knew when it happened, but if I don't happen to be using my phone, it can happen and then no one can call or text me until I realize that the problem is happening, so I can be without a connection for hours at a time before noticing.
Anyone have any idea what could be causing this and if there is a fix?
Thanks!
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....