Related
Turning the hero from portrait to landscape (or back), takes several seconds to work. Is there a setting somewhere to speed this up? It's unusable the way it is, life is just too short to wait for that!
iwillgetoutmore said:
Turning the hero from portrait to landscape (or back), takes several seconds to work. Is there a setting somewhere to speed this up? It's unusable the way it is, life is just too short to wait for that!
Click to expand...
Click to collapse
Unusable is rather strong! Takes about 2 seconds to happen, quickest rotation I have ever seen.
Anyway, I dont know of a way of tweaking this, though I support the intent
After watching my girlfriends iPhone switching instantly for the last year or so, it 'is' unusable to me. She laughed at it when she turned the phone. However, having said that, I've switched it back to standard andriod and now it works properly, certainly less than a second.
WIll have to play with perfmon and work out what's happening, maybe grabbing top while trying it in both UI's would be enlightening...
Seems to work fine for me, soooo much faster than Opera on WM.
You can calibrate it by going to Settings -> Sound and Display -> Calibrate G-Sensor.
Calibration only set up angle sensitivity, so is not relevant..
Ok i wanted to start new thread with this issue
got a question about the screen. Some times I can sense and see that despite of auto brightness off that the screen adjusts its brightness by itself. It is a little change but my sharp eyes can see this... Do you have a similar thing?
I can easly notice this when playing my country game. When I click on the building menu the screen gets brighter. When i cancel the menu the screen makes darker
Also in sprinkle when I use water the screen gets little brighter
I think this is because the Tegra 3 (or ASUS's implementation of it) adjusts contrast to conserve power. The changes in contrast make brightness seem to change.
I think their settings are too aggressive and they should either scale them back or add an option to turn it off, if possible. I'm sure it's nice for battery life but it does (in some very specific instances) seem to impact the experience.
Note: this is not a doom-and-gloom post. The Prime's screen performance is the best I've ever experienced on a mobile device, maybe any device, overall. So this is a bit of a nuisance but nowhere near enough for me to have an inkling of regret about buying the Prime.
This only happens on mine while in power saving mode.
TF201 / XDA premium
wynand32 said:
I think this is because the Tegra 3 (or ASUS's implementation of it) adjusts contrast to conserve power. The changes in contrast make brightness seem to change.
I think their settings are too aggressive and they should either scale them back or add an option to turn it off, if possible. I'm sure it's nice for battery life but it does (in some very specific instances) seem to impact the experience.
Note: this is not a doom-and-gloom post. The Prime's screen performance is the best I've ever experienced on a mobile device, maybe any device, overall. So this is a bit of a nuisance but nowhere near enough for me to have an inkling of regret about buying the Prime.
Click to expand...
Click to collapse
Do you experince the same issue as me?
tdrussell said:
This only happens on mine while in power saving mode.
TF201 / XDA premium
Click to expand...
Click to collapse
I'm not sure, I'll have to do some more testing. I seem to remember it happening across the board.
I'll note that Battery mode really does make a HUGE difference in the screen's performance. Colors become very washed out, so much so that I'm really surprised by the impact.
Well in my case this thing occurs on every mode with the same strenght... That sucks
so anyone of you can confirm if this is normal? Do you have the same isue on your primes?
It seems the light sensor has high resolution and Asus needs to smooth up a bit the auto-brightness algorithms If your screen goes up and down then simply disable auto-brightness or change lightning conditions
ankhazam said:
It seems the light sensor has high resolution and Asus needs to smooth up a bit the auto-brightness algorithms If your screen goes up and down then simply disable auto-brightness or change lightning conditions
Click to expand...
Click to collapse
Like i said auto brightness is off. Can anyone install my country and check his out for me? Just enter build menu and chec if the screen gets a little brighter
it has nothing to do with auto-brightness... Its a feature of tegra 3, it can change the brightness of each pixel to give you the best image and use the least amount of power.. unfortunately its just annoying and not implemented well.
And you cannot turn it off.
Ya I noticed this too last night and thought that I had a defective screen. Made a thread about it earlier. http://forum.xda-developers.com/showthread.php?t=1421002
jzen said:
it has nothing to do with auto-brightness... Its a feature of tegra 3, it can change the brightness of each pixel to give you the best image and use the least amount of power.. unfortunately its just annoying and not implemented well.
And you cannot turn it off.
Click to expand...
Click to collapse
I should b off in perormnce mode. I understand this feature in saving power mode but not on others two. I hope it will be changed
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 possibly an LG-exclusive mod to squeeze even more battery life) 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
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above 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 our friend with the 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, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please 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, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
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 you are 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".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Same here.
A temporary solution I have found is to enable in developer options 'stay awake while charging' now it stays on. But it is not the same. The display appears to be much brighter. probably because ambient mode (Not sure that's how its called) is not enabled.
Edit: That appears to be the fix. When turning on in settings 'always on display' it works like before. no need to enable stay awake while charging in developers settings.
Although this fixes the issue, I am somewhat disappointed because this option reduces battery life.
I noticed I should have put this question into 'troubleshoot and questions'. I am sorry for placing it here. Perhaps a moderator can place it in the right section for me?
Not a problem here.
Always on is normally activated.
Sent from my m1 note using Tapatalk
I've noticed the same behavior when I upgraded my Moto 360 to AW 2.0
For me, the clock stays on but the background is really bright whereas it used to be black before
Same thing here, background to bright. I don't think this is on purpose. They would probably get out fixed in an upcoming patch(?)
Same here.
I liked docking my watch on my bathroom counter and using it as my clock while getting ready in morning. Now it doesn't stay on and when I tap the screen I can see it for a few seconds. When it is on ....the brightness of the background is terrible.
I sure hope they fix this problem.
I have the same problem
Can't believe there is still no fix for this?
This is really annoying! I was hoping XDA had found an answer. Having always on screen on is not a solution since Moto made a bad design decision on the screen making it best to turn that option off. I assume everyone else's keep awake while charging option doesn't really solve it either because the screen turns off once the battery is full. Anyone think there's a workaround to be found in Tasker and maybe AutoInput (maybe turn always on screen on while charging, off otherwise, or even based on hours). I'm no tasker expert, so I'm not sure if that combo could work on android wear.
Sn0w0nS said:
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Click to expand...
Click to collapse
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
Not on mine. I'm using the factory charger.
vladfan said:
Not on mine. I'm using the factory charger.
Click to expand...
Click to collapse
That's so odd. I'm not having that problem at all
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
I am using Motorola's dock charger. I am positive that the issue lies with Android Wear 2.0 and not the charger. Before wear 2.0 it worked as it should.
I think it's random with AW2.
After flashing a new rom at my mobile, I had to forget and pair again the watch to the Android wear.
From now on, the clock stays on during charging.
This was not the case before that.
Sent from my m1 note using Tapatalk
I have the very same issue (watch paired with a Nexus 4, 5.1.1). Anything I can try? Thanks!
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
wesswei said:
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
Click to expand...
Click to collapse
What r u talking about?
Always On was there since Android Wear 1.5.
And come again?
1 week use of the watch with 1 charge?
How did u manage to do that?
By turning on the watch for 2 hours every day?
Sent from my m1 note using Tapatalk
Can't we just enable always on display? Aren't there any hack to enable it?
And if it's
Battery will not be able to stand 1Hour at least i think
Come on you own smartwatch
Keep raising your hand every few minutes, it will stay on always then. Problem solved.
Mostafa Virusx said:
And if it's
Battery will not be able to stand 1Hour at least i think
Come on you own smartwatch
Click to expand...
Click to collapse
No i think i will go for at least one day.. See other AMOLED watch from xiaomi.. they go for 7-10 days with always on display.. And compared to that mi band 4 can go for 1 day at least
kennyk09 said:
Keep raising your hand every few minutes, it will stay on always then. Problem solved.
Click to expand...
Click to collapse
You know that's not the solution.. And this function doesn't work Everytime
Rakibboss said:
You know that's not the solution.. And this function doesn't work Everytime
Click to expand...
Click to collapse
You know he was kidding, right?
AOD function must have support not only from the software, but also HW. In theory, you could enable AOD on Mi Band 4, but you'd risk AMOLED burn in and most probably very high power consumption. If you really must have this feature, buy a band/watch which supports it properly and out of the box.
Rakibboss said:
Can't we just enable always on display? Aren't there any hack to enable it?
Click to expand...
Click to collapse
It should be possible theoretically.
The latest firmware (1.0.6.24) has option change the display duration (Auto screen off time). But, it only let's to choose between 5 to 10 seconds. So, hopefully, the firmware update can take care of increasing the time to longer period (infinite).
A very light watch face with minimum color (black and white) theme should take care of the quick battery drain.
I think, is cool to have this option.
raghu13uk said:
It should be possible theoretically.
The latest firmware (1.0.6.24) has option change the display duration (Auto screen off time). But, it only let's to choose between 5 to 10 seconds. So, hopefully, the firmware update can take care of increasing the time to longer period (infinite).
A very light watch face with minimum color (black and white) theme should take care of the quick battery drain.
I think, is cool to have this option.
Click to expand...
Click to collapse
That's what i am thinking... It's possible actually although some are not agreeing with it..
That's nice that you think it, but I'm sure you would blame Xiaomi for adding this feature if it caused persistent image retention problem, desaturated colors over time and maybe some other HW defects due to prolonged use of OLED panel.
Yes, the burn-in could be a problem as well.
May be we can come up with some solution like the moving display (like the ones in old screensavers on CRT) or the one in Glitch watchface and UI (given below).
https://geekdoing.com/threads/glitch-ui-v83.1597/