Database Users

Screen timeout / profile / for lapdock reboot issue

Good morning,
I was wondering if anyone knows of a way to vary the screen time out as part of changing the profile for CM10?
I am using a lapdock for various things (including a chroot) and it seems that I am getting reboots along with it. sometimes they may be random, which I accept, but it seems that very often they occur when the display goes to sleep. I've done a fresh boot and just placed it on the lapdock and waiting for it to sleep and it seems that it's about 50% of the time that it will soft reboot. (and if it reboots on the dock it comes up in a different display mode and I can't unlock my sim card... but that's another story...)
So along with the notifications, and radios, is there a way to tie screen time out to profile?
thanks.

Display turning OFF after a while..

I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA

No replies here but several in the LG G Watch forum.
Other G Watch owners are seeing the same behaviour I described here so I can rule out that it's something which has been triggered by my having had the Slumber app installed.
One poster there says that his G Watch turns off after 30 minutes leaving it lying on a table. I am timing mine.
So based on all of those replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from a poster there with a Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, may somebody else here with Wear watches from other makers please confirm you get the same behaviour on your watches (on 5.0.1)? And may you also confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think this might be a good feature to keep ON in many cases but it absolutely should be an *option*!

UPDATE: Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think the poster StuBFrost, in the other thread, is right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...

"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".

Doze?

Is there a way to modify Doze to enable it to work when the phone is unused in your pocket? Seems like a flaw that it only works while sitting flat on a desk.

check out naptime
https://play.google.com/store/apps/details?id=com.franco.doze&hl=en

I wouldn't say it's a flaw when the device detects movement. It goes into deep hibernation while in Doze, so all those sensors get a rest.

Does anyone know if this app will break android pay?

steveo17 said:
check out naptime
https://play.google.com/store/apps/details?id=com.franco.doze&hl=en
Click to expand...
Click to collapse
Naptime breaks the Play Store for a lot of us. You can't download a new app until you re-boot the phone. Hoping that gets fixed soon.

Try the aggressive Doze on greenify
Sent from my Nexus 6P using Tapatalk

jejb said:
Naptime breaks the Play Store for a lot of us. You can't download a new app until you re-boot the phone. Hoping that gets fixed soon.
Click to expand...
Click to collapse
You could run naptime without the aggressive Doze feature and tweak the settings manually. I think if you set sensing timeout and motion inactive timeout to 0, it shouldn't trigger the sensors.

Just to let you guys know that turning off the sensors completely isn't possible yet.
I've done multiple tests with the logcat and verified this. Using agressive doze on naptime or greenify will cause the device to go straight into doze BUT, if you move your phone significantly (in a pocket etc) it will leave doze and go back to sensing and locating.
Don't believe me? Try it yourself, use aggressive doze, put it on a table send yourself an email or Whatsapp, it shouldn't come through, the pick up your phone and move It a bit, without turning on the screen. Your notifications will come through, meaning you're out if doze.
Therfore, if you are someone who moves around a lot, this can actually be worse for your battery.
My advice? Decrease the times on the timers, but don't put them at 0 ( they still fire anyway) I've set my inactive time to about 15 mins instead of 30
If you're someone who moves bunch, don't use aggressive doze at the moment.
Sent from my Nexus 6P using Tapatalk

italia0101 said:
Just to let you guys know that turning off the sensors completely isn't possible yet.
I've done multiple tests with the logcat and verified this. Using agressive doze on naptime or greenify will cause the device to go straight into doze BUT, if you move your phone significantly (in a pocket etc) it will leave doze and go back to sensing and locating.
Don't believe me? Try it yourself, use aggressive doze, put it on a table send yourself an email or Whatsapp, it shouldn't come through, the pick up your phone and move It a bit, without turning on the screen. Your notifications will come through, meaning you're out if doze.
Therfore, if you are someone who moves around a lot, this can actually be worse for your battery.
My advice? Decrease the times on the timers, but don't put them at 0 ( they still fire anyway) I've set my inactive time to about 15 mins instead of 30
If you're someone who moves bunch, don't use aggressive doze at the moment.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I knew Doze breaks with significant motion, but didn't realize leaving it in the pocket counts as significant motion.
Following this post http://forum.xda-developers.com/showpost.php?p=63962529&postcount=700, I think we should be able to leave the sensing and locating timeouts to 0 but set the motion inactive timeout to something high.This way if the phone breaks Doze (moving in your pocket or whatever) it won't try to enter Doze immediately again. However, if you're not moving, it will enter Doze quickly.

Vishal90 said:
I knew Doze breaks with significant motion, but didn't realize leaving it in the pocket counts as significant motion.
Following this post http://forum.xda-developers.com/showpost.php?p=63962529&postcount=700, I think we should be able to leave the sensing and locating timeouts to 0 but set the motion inactive timeout to something high.This way if the phone breaks Doze (moving in your pocket or whatever) it won't try to enter Doze immediately again. However, if you're not moving, it will enter Doze quickly.
Click to expand...
Click to collapse
Not a bad idea actually.
Sent from my Nexus 6P using Tapatalk

Vishal90 said:
I knew Doze breaks with significant motion, but didn't realize leaving it in the pocket counts as significant motion.
Following this post http://forum.xda-developers.com/showpost.php?p=63962529&postcount=700, I think we should be able to leave the sensing and locating timeouts to 0 but set the motion inactive timeout to something high.This way if the phone breaks Doze (moving in your pocket or whatever) it won't try to enter Doze immediately again. However, if you're not moving, it will enter Doze quickly.
Click to expand...
Click to collapse
Thanks for the input, but a little confused. Just above, you recommended setting motion inactive timeout to 0, but here you say to leave it a high number and set locating timeout to 0. Sensing timeout to zero in both cases. Is the change in settings from considering italia0101's input?
What do you recommend for the motion inactive timeout?

jejb said:
Thanks for the input, but a little confused. Just above, you recommended setting motion inactive timeout to 0, but here you say to leave it a high number and set locating timeout to 0. Sensing timeout to zero in both cases. Is the change in settings from considering italia0101's input?
What do you recommend for the motion inactive timeout?
Click to expand...
Click to collapse
Yeah it is. Doze uses two motion triggers, the normal motion sensor and the significant motion sensor. Before, I had just assumed significant motion meant something more drastic than leaving it in your pocket, but as italia0101 pointed out even that triggers the significant motion detector. This means that because of the way Google implemented Doze, you can't get it to Doze while your phone is in your pocket. So the best you can do is get it to Doze as soon as possible. The only problem is that if Doze breaks, your phone will instantly try to Doze again, and it will break again, killing your battery. The link I posted should help you understand how Doze works and might help you set out own values. With that said, I keep sensing and locating timeouts to 0, and motion inactive to something higher. Right now I'm trying 900s (15 mins) for that value. This way after screen off and the inactive timeout, it will not waste any time on motion sensing. And if Doze breaks (by being in your pocket) from the significant motion sensor, it will wait for the motion inactive timeout setting before attempting to Doze again. This, to my understanding, should prevent your phone from instantly trying to Doze in your pocket of Doze breaks. Therefore it should prevent your motion sensor from being on too much, saving you some battery if you're walking around a lot.

Thanks for the explanation. I did look at your link, and learned a lot.
I wish there was a way to disconnect the link between movement and the phone coming out of Doze. I'd like it to go into Doze pretty much immediately after shutting the screen off and not wake until I unlock/turn the screen on again. Still want text and phone calls to come through, though. That's one thing I noticed about the iPhone 6S+ I had for 2 weeks. It was excellent about not using battery if the phone was not on. It'd lose like 5-10% all day if I carried it around and only got a call or two and a few texts. I don't want that phone back, at least not with iOS, but I'd sure like to see that kind of battery life.

50% more battery tip on Wear24 (and other LTE AW watches) -> ~3 Days /w Min Usage

so i have been seeing REALLY crappy battery usage on my wear24 on aw2.7 despite turning off alot of things and barely using any apps.
now i EVEN have always-on ambient , and my watch lasts almost 3 days. since its always on, i rarely need to use the watch (eg. wake). i use the Sleek face which shows my agenda , weather, date, various other info on my face all the time so i just look at it. and incoming messages are shown still. here is what i do:
-KEY THING: AIRPLANE MODE! eventho i turn off LTE in connecticvity, i dont know if its a bug, but it's super annoying it keeps coming back on. this is the #1 change that improved it IMMENSELY. i think this turns off alot of useless wake functions and sync'ing
-turn off wifi (auto still keeps searching)
-only use BT
-delete msg+ / my verizon
-turn off OK google / tilt to wake
- no gestures
- no location
-turn on always on
One more thing if anyone can figure out, the watch auto turns on battery saver when under 10%. i'm curious if we can force this mode when its at 100%.

How did you delete msg+ / my verizon? With "adb?
Thanks,
Rob

update to AW 2.7, u can disable via system apps

turning off every thing is not called smart, better buy a normal watch then

I'm not going to try all of these things, but I have noticed that it re-enables the cellular radio. I'm going to try putting it in airplane mode and just keeping the bluetooth connection on. My only issue is, is there any way to get rid of the airplane icon on the watchface?
geminihc said:
so i have been seeing REALLY crappy battery usage on my wear24 on aw2.7 despite turning off alot of things and barely using any apps.
now i EVEN have always-on ambient , and my watch lasts almost 3 days. since its always on, i rarely need to use the watch (eg. wake). i use the Sleek face which shows my agenda , weather, date, various other info on my face all the time so i just look at it. and incoming messages are shown still. here is what i do:
-KEY THING: AIRPLANE MODE! eventho i turn off LTE in connecticvity, i dont know if its a bug, but it's super annoying it keeps coming back on. this is the #1 change that improved it IMMENSELY. i think this turns off alot of useless wake functions and sync'ing
-turn off wifi (auto still keeps searching)
-only use BT
-delete msg+ / my verizon
-turn off OK google / tilt to wake
- no gestures
- no location
-turn on always on
One more thing if anyone can figure out, the watch auto turns on battery saver when under 10%. i'm curious if we can force this mode when its at 100%.
Click to expand...
Click to collapse

mistermojorizin said:
I'm not going to try all of these things, but I have noticed that it re-enables the cellular radio. I'm going to try putting it in airplane mode and just keeping the bluetooth connection on. My only issue is, is there any way to get rid of the airplane icon on the watchface?
Click to expand...
Click to collapse
I believe rebooting the watch is what turns on the cell signal. Mine stays off until I reboot. You don't need to turn on airplane mode to turn off the cell signal. I was going to write an app to do this automatically on boot, but can't unless someone finds a method to root it.

For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
And how do you guy update to 2.7? Mine updated to 2.0 and it says it's the latest version.
And where is the setting for the power saving mode? Mine enter power saving at 15%.

Jackson1983 said:
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
And how do you guy update to 2.7? Mine updated to 2.0 and it says it's the latest version.
And where is the setting for the power saving mode? Mine enter power saving at 15%.
Click to expand...
Click to collapse
I installed 2.8 on mine through ADB

Jackson1983 said:
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
Click to expand...
Click to collapse
You can disable the charging display by going into app settings and disabling the charging app. I never found a way to keep the screen lit up while charging even with the always on enabled so I wrote an app to do it. https://play.google.com/store/apps/details?id=com.turndapage.watchwake

Jackson1983 said:
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
And how do you guy update to 2.7? Mine updated to 2.0 and it says it's the latest version.
And where is the setting for the power saving mode? Mine enter power saving at 15%.
Click to expand...
Click to collapse
You're taking about ambient display. The app that sets your watch face controls that. Some have settings for this either on watch or on phone, some don't and you can't change it if you're using that face. I use watchmaker, which lets me edit every image layer in my faces and select which parts stay on. Also can create layers only visible in ambient mode.

mistermojorizin said:
I installed 2.8 on mine through ADB
Click to expand...
Click to collapse
How did you update through ADB?

nastynate435 said:
How did you update through ADB?
Click to expand...
Click to collapse
got adb over wifi going, got the apk from apk mirror (the watch specific wear apk), then did something like
adb connect 192.168.0.102 (or whichever ip your watch gets)
put the apk in the directory where my command window was
adb -s 192.168.0.102 install -r wearapp.apk
BUT, this is not necessary anymore. 2.8 just installs automatically now from play store on the watch.

You can just block message+ in the notifications screen, and install messages from play store

Always Best Imformation
geminihc said:
so i have been seeing REALLY crappy battery usage on my wear24 on aw2.7 despite turning off alot of things and barely using any apps.
now i EVEN have always-on ambient , and my watch lasts almost 3 days. since its always on, i rarely need to use the watch (eg. wake). i use the Sleek face which shows my agenda , weather, date, various other info on my face all the time so i just look at it. and incoming messages are shown still. here is what i do:
-KEY THING: AIRPLANE MODE! eventho i turn off LTE in connecticvity, i dont know if its a bug, but it's super annoying it keeps coming back on. this is the #1 change that improved it IMMENSELY. i think this turns off alot of useless wake functions and sync'ing
-turn off wifi (auto still keeps searching)
-only use BT
-delete msg+ / my verizon
-turn off OK google / tilt to wake
- no gestures
- no location
-turn on always on
One more thing if anyone can figure out, the watch auto turns on battery saver when under 10%. i'm curious if we can force this mode when its at 100%.
Click to expand...
Click to collapse
Always Best Information

My wear24 the battery is draining down so fast, i think its be bad battery. How can i replace the battery for my wear24?

I can't find the apk on apkmirror. Can you please post the link or the exact name of the apk.

abusalad said:
My wear24 the battery is draining down so fast, i think its be bad battery. How can i replace the battery for my wear24?
Click to expand...
Click to collapse
I just got mine for $43 on eBay and it went from 93% down to 2% on a single reboot. It then stayed on 2% from 6:30pm til 6:50am when it finally died. So I charged it from 0% to 59% then it jumped to 100%. Then it discharged to 77% and then dropped to 43%. sounds like a calibration issue.
On the plus side, unlike the moto 360 it appears the back is actually screwed on instead of glued on which is great news. I may unscrew it when I get home and see how easy the battery is to access.

Is screen totally smooth?

Hi,
I wonder if you see some totally random sort of very short flashes /light ups of and on the screen. Sometimes the display flashes up to the status bar at the top another times it is visible just below it.
Meanwhile I think this happens when the 120Hz-display switches from areas of lots of white or black to the opposite color. It is totally random, but it annoys me. I can't reproduce it, because if it happens and I repeat what I have done that caused the flash on the display, it doesn't do it anymore. Very strange.....
I wonder if the 120Hz display can break technically not the glass itself, when it falls on the ground.

I have mine locked to 120hz
Haven't witnessed this anomaly as yet.
If recommend leaning Res on FHD and seeing 120 permanently, I hit 9-11 hours consistently with 120 so very little benefit to leave it off

gerega said:
Hi,
I wonder if you see some totally random sort of very short flashes /light ups of and on the screen. Sometimes the display flashes up to the status bar at the top another times it is visible just below it.
Meanwhile I think this happens when the 120Hz-display switches from areas of lots of white or black to the opposite color. It is totally random, but it annoys me. I can't reproduce it, because if it happens and I repeat what I have done that caused the flash on the display, it doesn't do it anymore. Very strange.....
I wonder if the 120Hz display can break technically not the glass itself, when it falls on the ground.
Click to expand...
Click to collapse
Yup, this is the screen switching from 120Hz back to 60Hz. Only way to fix this is to lock the screen to 120Hz (Force 120Hz)
To change the refresh rate mode to this hidden full-time 120Hz mode, you simply need to enter the following ADB command:
adb shell settings put global oneplus_screen_refresh_rate 0
If you dont know what ADB is:
https://www.xda-developers.com/install-adb-windows-macos-linux/

Mine is pretty smooth locked at 120hz...

RicardoDimm said:
Only way to fix this is to lock the screen to 120Hz (Force 120Hz)
adb shell settings put global oneplus_screen_refresh_rate 0
Click to expand...
Click to collapse
Does this survive a reboot? How can I test if 120Hz is switched on?

You can enable the frames indicator in the developers options