After updating to emui9.1 I noticed something weird with my watch(gear s3) when phones screen turns off immediately watch disconnects but after 1 or 2 sec it reconnects
So it will relaunch services in another state?
Related
I like keeping my wifi on while my screen is asleep so that I can receive chat messages or e-mails without being at my computer. I never had this problem while running ICS on an unrooted TF201, but ever since I installed the upgrade to JB my wifi will always disconnect after the screen has been asleep for a few minutes. I've checked every setting I can think of. In the Wifi Advanced menu, I have it set so Wifi is always on, and in the ASUS customized setting I have Disconnect network during sleep to off. Under Power Saver I have Enable low battery settings off, set Low battery level to 0%, and even set Wifi OFF to off. Despite all of this, it seems like the tablet under JB goes into some sort of deep sleep and disconnects the wifi after about 5 minutes of inactivity.
I have noticed that this problem does not occur when the screen is on. I also have the dock, and set the screen to always on during meetings in the event that I don't need to enter any notes for a few minutes so I don't have to fool with any delays from screen wake .
Is there some setting I'm missing? Is it a hidden setting that I could access by rooting? Or am I dealing with something internal to the build that I can't change at all? This may not seem like a huge deal to most, but it has become one of my main uses for the tablet when I'm at home. I'm very disappointed with JB so far even though the wifi does feel more responsive on the Prime after the update (when it's not sleeping, of course!).
EDIT: I noticed this evening that the wifi turns off even when I'm running something that uses it while the screen is off. I was listening to Pandora, and about 5 minutes after the screen went off, my music stopped. When I turned the screen back on, I saw that the wifi had indeed become disconnected.
hey,
I have exactly the same problem with my tablet. I have checked every option, I did a factory reset several time, I have checked it on 2 different routers but it is still disconnecting the wife when it goes in the sleep modus. Did you or anyone else find a solution?
For some reason my watch constantly disconnects from my phone (a One plus 2)
The Android wear app says trying to connect, but the only way is to reboot the phone. It connects again, but then will disconnect later, I'm assuming when the phone goes into deep sleep?
The android wear app has been set to "not optimised" in the phone settings.
Is there anything else to check?
I've removed Greenify and Power Nap to see if that helps, but it's the same.
Phone is running latest Marshmallow from and watch is all up to date
Sent from my oneplus2 using Tapatalk
Are you using OxygenOS? I'm on CM13 and having same disconnects with my Oneplus2 - watch get disconnected 1-2 times per day.
Thought toggling Bluetooth Off/On resolves the issue for me, but temporary.
Is there a way to have constant connection between phone and watch?
Since changing my OS to paranoid android on my phone and removing things like, Power Nap and Amplify, I have had no more disconnect from the watch.
Not sure what services were being stopped to extend battery life
Sent from my ONE A2003 using Tapatalk
Still the same for me, I search and search, but don't find anything
Sometime a sync works for 1day, next day it's disconnected,
If I try to sync it again it takes ~1 to pair, and I dont see my apps, just default apps.
After press multiple times in WearApp to sync all apps I see it again.
Next hour or next day it's again disconnected.
I see the PlayService version on my watch is a older like my version on my phone (Note4)
Any ideas ?
I have a question about using Llama on Marshmallow. I wrote a basic script that enables airplane mode every 10 minutes and queues another task called disable airplane mode that has a delayed start of 9 minutes. So basically every 10 minutes my device turns off airplane mode for a minute then turns it back on. I left the script running over night, with my phone plugged in and it worked perfect. When I run the script without the phone plugged in, it only works for about 60 to 90 minutes. Sometimes it says conditions no longer true so repeating event canceled and sometimes I see nothing indicating why the repeating event stopped. My initial thought is that when plugged in, Marshmallow does not use Doze. Could Doze be causing a problem and preventing the task from running? I have whitelisted Llama along with 30 or 40 other apps and I am continuing testing. If you have any thoughts, I would greatly appreciate it!
Llama on Marshmallow
Not sure if anyone else is still trying to use llama on Marshmallow, but I found a work around. Polling wouldn't work at all for me so I started using WiFi connections and deleting out the entering / exiting location conditions. Wifi is everywhere now a days. This seems to work well unless you were trying to turn your WiFi off and on based on location. I'd tried e-robot for the same thing and it worked sometimes but not others. Couldn't figure what was going wrong there. Llama is still way easier to set up and more reliable than the alternatives I've tried.
Since i'm playing with amplify and power nap on my asus ze551ml (lollipop 5.0 with boret's kernel), i faced the following:
When the screen is off, the device doesn't go to sleep mode, or at least i think so.
I'm doing my testing with telegram; i said to amplify to limit his alarms to 1 every 10 minutes, and it is working fine undernight (BBS confirms that)
Now i'm even trying Power Nap, which is supposed to completely stop Telegram (and others).
Anyway, if i put the screen off, and then send a message to my telegram account, the phone still receives it almost instantly (3 seconds delay).
This clearly means that telegram is still active and kicking, it is not using any wakelock, it is alive all the time.
But, i repeat, it works overnight (Better battery stats confirms that amplify is limiting his alarms).
Another strange thing, is that i've configured com.asus.powersave to disable wifi as soon as the device enters sleep state, but when i wakeup my phone in the morning and see the BBS statistics from "screen off" to "screen on", it shows that wifi has been active for more than 18 minutes, so here's the question:
Is there a time/timeout to wait after one tunr off the screen for the phone to enter in standby/sleep mode?
And if yes, is that time configurable?
Thanks.
I made a test that confirmed what BBS said; i turned the screen off and start to ping my android wifi ip.
After about 18 minutes (that's the time BBS said wifi was active after the whole night), it stopped responding to pings and telegram of course wasn't workling anymore.
Is it possible to change that timeout to something lower?
I have an LG L90 running cm13.
normally, after the screen turns off, the wifi will cut out after 30 minutes, and start using cellular connection.
I hate this. I want wifi always on.
"Wifi always on during sleep" is enabled, but cm13 ignores this setting.
"global wifi_sleep_policy 2" also confirmed.
So I don't know why wifi keeps cutting off.
Is Doze causing this?
I tried dumpsys deviceidle disable, and pinged my phone every 15 minutes. I got ping replies for ~6 hours before it started to ping timeout, and only when I woke the phone did it start ping reply again.
So disabling doze didn't do much.
Wifilock apps don't solve this either. They will falsely keep the wifi connection logo in the status bar, but if you ping the phone, you get no response.
something is broken about the OS, cuz back in oem stock lollipop, the phone has no problem keeping wifi on all the time.