I just got my MoKo case for this. The smart cover is great and turns the screen off and on without having to mess with the power button all the time. But when the cover is closed for any long period of time, the screen does not turn on when the cover is opened. Why is that?
This has come up in a few threads. For me, it seems to be correlated with having no wifi connection. I've never seen the delay when wifi is operational, only when I've either turned off wifi or am no longer in range of the wifi I was connected to. At home, where I always leave wifi on, I can have it off overnight and it still comes on instantly when I open the case the next day.
If you set WiFi to turn off when the tablet is a sleep it will not turn back on after 15-30 minutes. I have mine set to WiFi always on and it works fine. If you want to save a little battery you can turn wifi off manually at night. Shame it doesn't work like the original Nexus 7.
Sent from my Nexus 7 using xda premium
ncguy68 said:
If you set WiFi to turn off when the tablet is a sleep it will not turn back on after 15-30 minutes. I have mine set to WiFi always on and it works fine. If you want to save a little battery you can turn wifi off manually at night. Shame it doesn't work like the original Nexus 7.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Although I don't have any of my wifi settings set to limit anything and are all set as suggested above, this was still occurring. I just tested this out with WiFi off and wifi settings don't appear to be the factor at all. With the tablet plugged in, I closed the smart cover and opened it about 45 minutes later and the screen came on fine. I unplugged it from the charger and closed the cover again for 45 more minutes and this time the screen did not turn on. Any ideas?
There is one setting that I do not have turned on and it's new to 4.3:
"Scanning always available
Let Google's location services and other apps scan for networks, even when WiFi is off"
When my Nexus is plugged in it never enters deep sleep and the auto on/off works fine.
When I changed the WiFi advanced setting to Keep WiFi awake during sleep to Always auto on/off works fine. If I turn WiFi off or set it to turn off during sleep the auto on/off will not work after 15-20 minutes.
I figure it has something to do with WiFi and/or deep sleep mode.
Sent from my Nexus 7 using xda premium
I had this issue when I was on stock. I believe the device has crashed. At this point, only option I had was to hold the power button until a full reboot.
Ever since switching to the CM10.2 nightlies, have never seen this issue again.
So my recommendation, get off of stock ASAP. :laugh:
That has nothing to do with it here, nothing is crashing. I think it's the smart cover not having the capability to waken the screen when the tablet is in deep sleep. It sounds to me like you traded crashes for something preventing deep sleep.
N7 had been closed for an hour.. I have Wifi off when screen is off... so *IF* that is the cause
- picked up the tablet, opened the cover.. did not turn on
- closed the cover
- opened again, N7 came on
so.. I ask, exactly how did the 1st failed opening wake up the Wifi (but not the tablet) if that is the culprit?
ie. if the determining failure condition is Wifi off rendering the cover unable to wake the tablet, I should be able to open/close/open the cover 100 times in a row without having it come on.
I don't know what the mechanism is, I just know it has never failed to come on instantly when it had a valid wifi connection.
It sometimes (but by no means always) has a big delay when wifi is off.
Those are the only two data points that seem consistent to me. Perhaps it does have to be off a long time and also have no wifi for the cover to not wake it immediately, but I haven't actually noticed if that is the case.
zim2dive said:
N7 had been closed for an hour.. I have Wifi off when screen is off... so *IF* that is the cause
- picked up the tablet, opened the cover.. did not turn on
- closed the cover
- opened again, N7 came on
so.. I ask, exactly how did the 1st failed opening wake up the Wifi (but not the tablet) if that is the culprit?
ie. if the determining failure condition is Wifi off rendering the cover unable to wake the tablet, I should be able to open/close/open the cover 100 times in a row without having it come on.
Click to expand...
Click to collapse
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
muyoso said:
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
Click to expand...
Click to collapse
I actually just got this case too well this one (http://amzn.com/B00CKA1IYU). Not sure if its the one you purchased. Mine was sitting in my office closed for about 45 minutes with WiFi off. I went over to open it and the screen turned on. I put it in my backpack later in the day and it sat there for about 30 minutes and I drove home. I got home and took it out of my backpack and set it on my desk unopened and with WiFi still off. I let it sit there for about another 30 minutes. I read this post and thought "I haven't opened the cover since before leaving work". So out of curiosity I opened it and the screen turned on.
So either my Nexus 7 isn't going into sleep with WiFi off or it actually works?
BTW: I like the case for the price! Bought 2 days ago so I paid 12.99 w/ free shipping.
Not the same but it's the same manufacturer so probably the same magnet
muyoso said:
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
Click to expand...
Click to collapse
You have asked the magic question.
Left the N7 overnight.. got up, opened the case.. and watched... it took 10-15 seconds and then the screen came on, certainly very delayed, but as a consequence of opening the 1st time, as it should.
Just repeated the experiment after an hour.. ~9 seconds from flap open to display on.
cowabunga said:
I had this issue when I was on stock. I believe the device has crashed. At this point, only option I had was to hold the power button until a full reboot.
Ever since switching to the CM10.2 nightlies, have never seen this issue again.
So my recommendation, get off of stock ASAP. :laugh:
Click to expand...
Click to collapse
which CM10.2 nightlies are you using?
because i found there are few CM ROM in here.
thank you
prowede said:
which CM10.2 nightlies are you using?
because i found there are few CM ROM in here.
thank you
Click to expand...
Click to collapse
I run the official one from http://get.cm/?device=flo
Just get the most recent one (ie. dated 8/21 as of right now)
cowabunga said:
I run the official one from http://get.cm/?device=flo
Just get the most recent one (ie. dated 8/21 as of right now)
Click to expand...
Click to collapse
I just tried the official CM Rom today, however, the problem still exists.
I have tried different version (21, 23,24/8), still the same....
Very strange...
Problem still exists with Spet 11 build.
A pretty long lagtime for the wifi to reconnect before turning on the screen.
Turning on bluetooth is a workaround.
So smart wake waits for a wireless connection?
Wasn't the case in the old Nexus 7.
bland.life said:
Problem still exists with Spet 11 build.
A pretty long lagtime for the wifi to reconnect before turning on the screen.
Turning on bluetooth is a workaround.
So smart wake waits for a wireless connection?
Wasn't the case in the old Nexus 7.
Click to expand...
Click to collapse
For now (until there is a fix), turn on bluetooth and leave that enabled.. very little power drain, and prevents the delay turning back on.
zim2dive said:
For now (until there is a fix), turn on bluetooth and leave that enabled.. very little power drain, and prevents the delay turning back on.
Click to expand...
Click to collapse
If I have Bluetooth on and leave the cover closed for a long time and when I open the cover again the WiFi will not turn on.
In one instance I can flip the WiFi switch in Settings to on but it will revert to off, in another instance the switch simply refuse to barge.
Rebooting the device fixes it and brings WiFi back (until the next long cover closure).
bland.life said:
If I have Bluetooth on and leave the cover closed for a long time and when I open the cover again the WiFi will not turn on.
In one instance I can flip the WiFi switch in Settings to on but it will revert to off, in another instance the switch simply refuse to barge.
Rebooting the device fixes it and brings WiFi back (until the next long cover closure).
Click to expand...
Click to collapse
then you have a different/worse issue from everyone else (ie. the delay turning on after cover is opened).
I'd do a restore from a factory image, and try that for 2 days.. if it still won't turn on, you need to RMA yours.
Related
I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Try it without any off your apps installed. If the problem goes away you know it's an app causing the problem. Then start adding them back in batches until the problem re-occurs. Eventually you'll narrow the issue down to one app.
mark_w said:
I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
This is happening to me too.
At random times, the phone will refuse to wake from sleep.
Nothing but a battery pull will fix it.
I don't have skype installed.
Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1360880&highlight=sleep+of+death
Mine started today. Really hope this does not keep happening or I need to return this right away. Missed a few phone calls today and didnt realize until I looked down any my phone was just simply black. Will not wake up or do anything at all. You have to pull the battery. Right before this happened my data was dropping non stop about every 5 minutes for an hour.
I'm trying to stay calm because I love this phone, but between the data drops and the phone turning off im loosing patience quick.
This is happening to me as well. With TWO different phones. The first one I returned to Verizon and now its happening on the second one.
Phone will power off while doing random tasks. The two I've noticed is browsing on the stock browser and texting on the stock texting app.
I'm having the same problem. It's happened twice in the 3 days I've had the phone. It hasn't happened while I'm using it, both times it was when the screen was already off -- it just wouldn't waku up. Nothing short of pulling the battery, letting it sit, then powering on would work.
Couldn't have come at a worse time either, my daughter is in the hospital and I get updates from the surgeons via phone. So now I have to check every 5 minutes and make sure the phone is still on.
Phone is bone stock, out-of-the-box.
Sent from my Galaxy Nexus using Tapatalk
i just had my first turned off this morning... my friend's SGN happened 5 days ago too. very unreliable....
I had that happen to me as well. Turns out I forgot that I had an app scheduled to do a backup at like 3 AM.
Sent from Galaxy Nexus
CodenameDroid 1.2 cdma & Franco 14.4
My sgn turned off every night now. Anyone got any ideas why? I turned my verizon backup already.
reboot durring skype call
mark_w said:
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
it does it when i have skype running too. also i have other other audio apps open. (power amp, tunein, pandora) It's happened twice to me and each time it has been during a skype call while the other apps were running. (in widget form)
shock sensitive in the area right below the camera?
My device just "randomly" switches off (sometimes several times a day). After a long search for a reproducible cause, it seems safe to say that at least some devices seem to be extremely shock sensitive in the area right below the camera (on the back of the device). Even minuscule shocks to this area switch these devices off. Youtube-user 'jardinepatten' demonstrates this problem nicely in a video called "Galaxy Nexus Turning Off".
I noticed that sometimes when I use the power button to turn off my screen, after 1-2secs later, the screen turns back on again automatically on its own. Happened quite a few times Already. Anyone with the same experience?
Haven't seen it happen.
Not seen this personally but there were some occasions when I picked up the phone and the screen was on. I'd assume I'd accidentally pressed the power button when picking it up.
Didbyou enable some options in S-Motion? Some of those options will turn screen on.
Sent from my GT-N7105 using Tapatalk 2
My galaxy s2 would do that all the time just come and go off ... Blahhhhhhhhhh
Sent from my SGH-T889 using xda premium
It happens mostly after a new app installation. The app is usually a spam and hence it keeps on turning the screen. Try to figure it own by removing apps one by one ever since the problem started.
fried.egg said:
Didbyou enable some options in S-Motion? Some of those options will turn screen on.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Yes I think this could happen when "Quick Glance " is enabled. A few days ago, I was cleaning with a cloth the screen of my Note 2 and the screen went on (I haven't pressed accidentally the power button of my phone)
Daniel
No no its not quick glance.. It's almost like my power buttonmay be too ssensitive. And the screen typically turns on just 1-2secs after I turn off the screen manually. Doesn't happen frequently but still about once a day?
kEvinErd said:
No no its not quick glance.. It's almost like my power buttonmay be too ssensitive. And the screen typically turns on just 1-2secs after I turn off the screen manually. Doesn't happen frequently but still about once a day?
Click to expand...
Click to collapse
Have you installed any app like Pocket Sensor?
I use this amazing app, which can behave like this sometime when anything overshadows the proximity sensor.
kEvinErd said:
I noticed that sometimes when I use the power button to turn off my screen, after 1-2secs later, the screen turns back on again automatically on its own. Happened quite a few times Already. Anyone with the same experience?
Click to expand...
Click to collapse
I had exactly the same issue and maybe it's coincidence but the issue went away after I disabled Quick Glance. Been over a week now and this used to happen at least once a day.
Sent from my GT-N7100 using Tapatalk 2
kEvinErd said:
I noticed that sometimes when I use the power button to turn off my screen, after 1-2secs later, the screen turns back on again automatically on its own. Happened quite a few times Already. Anyone with the same experience?
Click to expand...
Click to collapse
I have EXACTLY..this problem.. it happens a few times a week to me.. Quite annoying sometimes.
I've been suspecting that its because of a application, namely, Kakao-talk, which is a IM application. I can't really recall my screen turning on suddenly when using any other app, but I will wait and see if it happens outside of Kakaotalk.
If the problem persists, i might hand it in to service...
its quite annoying sometimes. I have heard of other people having the same problem though...
i noticed my my galaxy nexus after updating to 4.2 buring more oil ! than 4.12 and i was wondering why
!!!!
i installed odex and pre rooted on Gnexus forum and now i found why it burns more battery than before !
screen in my phone turn on automatically every 1 minutes and sure it will stay for 15 second to turn off automatically , its bug ! actually i hope it getting fixed
any other guy faced this issue ?
Had this problem occassionally on Nexus S and Galaxy Nexus. As far as I recall, this is android bug, sometimes triggered by third party apps. Google 'screen turning on by itself' to find out more.
Sent from my GT-N7100 using Tapatalk 2
kEvinErd said:
I noticed that sometimes when I use the power button to turn off my screen, after 1-2secs later, the screen turns back on again automatically on its own. Happened quite a few times Already. Anyone with the same experience?
Click to expand...
Click to collapse
I thought only I had this weird issue... its really annoying and my battery is getting drained up very fast...
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good:
More often than not, when I start up my G pad, the Wifi does not turn on regardless of the way it was set before. Toggling the button on quick settings, or tying to turn it on manually in settings, does nothing; it says "turning on wifi", but it hangs. Rebooting usually fixes it, but sometimes requires more than one try.
Has anyone else experienced this? I'm hoping that it's a software glitch that will get fixed in the next ota update or when I flash my next rom, whichever comes first. If it's a hardware problem, however, I'd better return it before my rma period expires. Any ideas?
Thanks!
In the advanced setting under WiFi do you have the tablet set to keep WiFi on during sleep? I never turn mine off and do not have a problem. Using a v500 not a v510.
Sent from my LG-V500 using XDA Premium HD app
yojimboj said:
More often than not, when I start up my G pad, the Wifi does not turn on regardless of the way it was set before. Toggling the button on quick settings, or tying to turn it on manually in settings, does nothing; it says "turning on wifi", but it hangs. Rebooting usually fixes it, but sometimes requires more than one try.
Has anyone else experienced this? I'm hoping that it's a software glitch that will get fixed in the next ota update or when I flash my next rom, whichever comes first. If it's a hardware problem, however, I'd better return it before my rma period expires. Any ideas?
Thanks!
Click to expand...
Click to collapse
Yes, I've experienced it, if by starting up the G Pad you mean from it bring completely shut down, rather than sleeping. Also happens when doing a restart sometimes. As you say, a further restart sorts it out. I very rarely shut the tablet down or restart it though, usually I just let it sleep, so it hasn't really bothered me, except for the first time when I thought for a horrible moment the wireless hardware had died!
Wht if you don't want to use wifi when you boot the tablet? Then you have the wifi radio wasting battery from the start. Can't you install an app tht turns on the wifi at boot?
It took 6 reboots to get wifi working this mornino! Previously it had only taken 1-2 tries. It also had seemed on previous occasions that rebooting while unplugged would be more likely to successfully turn it on, but no luck; it failed multiple times both plugged and unplugged.
Needless to say, I will never turn the damn thing off if I can help it, but I'm not exactly happy about it.
LBJM, I rarely want to start up without having wifi enabled, but I suppose you could use apps like Tasker or Llama to turn it on or off under certain conditions.
LBJM said:
Wht if you don't want to use wifi when you boot the tablet? Then you have the wifi radio wasting battery from the start. Can't you install an app tht turns on the wifi at boot?
Click to expand...
Click to collapse
The issue isn't simply that Wi-Fi is off when the tablet first boots up, it's that it refuses to switch Wi-Fi on until it's restarted a second time, so don't think this would help.
---------- Post added 30th January 2014 at 12:01 AM ---------- Previous post was 29th January 2014 at 11:55 PM ----------
yojimboj said:
It took 6 reboots to get wifi working this mornino.
Click to expand...
Click to collapse
6 is getting a bit crazy! Thankfully a single restart worked for me on the couple of occasions it happened. I've actually ended up restarting a few times over the past week for other reasons, but haven't seen this issue occur again. I'm going to shut it down completely shortly, so will see what happens then.
I would take that in for a warranty replacement. That sounds like a dodgy network chip on the main board. I just restarted today and had no problem like what you mention.
Sent from my LG-V500 using XDA Premium 4 mobile app
I turn it off every night and in the almost couple of months that I have had my G Pad I have never had this problem.
Yeah I would RMA your Gpad. You shouldn't have to jump through hoops to turn on wifi.
Oddly, the issue has pretty much stopped - - just as well, since I was past my RMA date! I'm going to chalk this one up to some odd app interference, since it resolved with any rom updates or re-flashing.
Thanks again to everyone for their help!
So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.
Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk
droidkevlar said:
So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.
Click to expand...
Click to collapse
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.
I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?
kpjimmy said:
Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
JayRyu said:
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
euroclie said:
I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?
Click to expand...
Click to collapse
Thought this too, but it just happened out of the blue. It wasnt right after the update.
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.
So just tested and it still takes a long time to reconnect. Next step will be wiping watch completely and seeing if it resolves the issue. Will try this over the next few days when I get some free time to really mess with it.
My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.
fwayfarer said:
My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.
Click to expand...
Click to collapse
Good to hear I am not the only one. Which phone do you have? Mine does reconnect, but takes 1-3mins. Im not using a stop watch, just looking at clock and watching the time before it reconnects.
Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.
fwayfarer said:
Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.
Click to expand...
Click to collapse
OK, Im on LG G3 Verizon rooted. Its just weird that either I didnt notice it after the update, or it happened shortly after the update. Either way, batt life has been a lot better, I just wanted to make sure something I did didnt screw it up.
And let us know about your test for the disconnect.
droidkevlar said:
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.
Click to expand...
Click to collapse
FWIW I don't have Xposed installed (but a custom ROM on a i9502 Dual-SIM Samsung Galaxy S4, which might contain some Xposed stuff even though it's unlikeley).
I didn't notice the same reconnect delay today, so maybe this isn't a permanent phenomenon...
I have same issue with reconnecting after walking away. I have a Galaxy S5.
Walked upstairs and watch disconnected, got alert. Came back down and put phone in my pocket. Took three minutes to reconnect.
Bluetooth reconnect takes ages
Same issue with my 360. I have a xperia z2 and its taking a good 2-3 mins to recconect. Such a pain as this is really important to me and work.
Any ideas on if its a downloaded app or not?
Everyone's timeout is looking about equal. It was probably put in for battery savings.
Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed
fwayfarer said:
Everyone's timeout is looking about equal. It was probably put in for battery savings.
Click to expand...
Click to collapse
robber said:
Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed
Click to expand...
Click to collapse
Yep. Just wanted to make sure as it seemed to happen not right after the update. Thanks everyone.