Hello, guys. I am encountering what I think is a very weird bug with Smart Saver. I'm hoping that some other people can test this on their systems and if, it's just me, I'm going to return mine for a new unit.
With Smart Saving enabled, the screen will automatically increase and decrease brightness constantly as different pages and app's come up. In my case, the screen seems to flicker almost every time I swipe and I can't stand it, so I disabled Smart Saver. The icon is OFF on the pull down status panel and it's turned off under settings. However, whenever I reboot, I still encounter the screen flickering and dimming constantly (although it seems to be to a lesser degree). If I pull down the status panel, turn Smart Saving On and then off again, the problem goes away until I reboot the system. This is at least encouraging me that maybe it's just software and I can deal with it for a month or so.
Here's what I want someone else to test for me. Turn Smart Saver off. Turn the tablet off and then on again. Pull down the status menu and carefully watch the screen. The open portion of the home screen will dim once (which is normal). On my system, after about another 1/2 second or so, the screen will flicker or dim again slightly. It does this every time, but it might be hard to notice unless you are looking for it. When side scrolling between home screens, sometimes brightness will increase slightly and other times it will decrease. Pull down status panel, turn on smart saver, turn it off again and the problem goes away.
Help, please? Mine is a US model if that makes any difference on build 10.14.1.47.
Thank you very much in advance.
Did you download the used 10.14.1.47 manually from Asus website or was it an auto update from the device itself.
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD
Manually from the website.
I kinda have the same problem, though on my tab it is only the auto brightness that sometimes will increase/decreased constantly. Disabling Smart Saving or auto brightness helps in my case. I only have the problem when i'm in a room where there's light but the room isn't totally bright, and the tablet is with its back to the light source.
Others can correct me if I'm wrong but the 10.14.1.47 isn't being pushed through the device itself. I'm finding most people are downloading it manually from Asus website. . My estimation, I think Asus is aware that the update has some issues, thus not force updating it through the device until they come out with the latest fix.
Sent from my New Asus Transformer Pad TF701T using Tapatalk HD
You might be right about the update. Although I was thinking more people should have this issue. Maybe they aren't rebooting their tablet often enough to notice it as once I enable/disable Smart Saver, the problem goes away until I reboot. That is a satisfactory work around, but I was hoping for confirmation from at least one other person seeing the same thing in terms of returning the device. Amazon has decent return terms, so I'll probably wait until the next update and see if that fixes it. Thanks.
I'm on .47 and I have the same issue as well. I also noticed that the brightness will increase 2-3 steps every time I bring up "settings". This is regardless of auto-brightness on/off, smart saving on/off, outdoor mode on/off.
Auto-brightness is useless: Usually it's much too dark, and the auto-setting is changing with strange behaviors.... it's kinda jumping up and down as other described...
Thanks, since others are experiencing it too, at least I'm hopeful that it will be fixed in a SW update.
Did someone contact the asus-hotline?
derekk1 said:
Thanks, since others are experiencing it too, at least I'm hopeful that it will be fixed in a SW update.
Click to expand...
Click to collapse
Same thing here, bought the unit in the US and also experiencing the same awkward behavior. This would actually go away when Auto Brightness is turned off.
I am also getting issues when docked. Sometimes after some time (maybe a couple of hours) as soon as I tilt the tablet to its normal position, I would find it completely off. Had to turn the device back on a couple of times now.
These are too many annoyances for such an expensive unit.
Hope they fix the Auto Brightness setting at least.
Disabling Asus Splendid app in settings -> apps seems to stop this behavior.
vBoedefeld said:
Disabling Asus Splendid app in settings -> apps seems to stop this behavior.
Click to expand...
Click to collapse
I am now on 4.3 and it seems to be better (just some hours). It is not as dark as before and doesn't hop up and down every second :good:
Yezariael said:
I am now on 4.3 and it seems to be better (just some hours). It is not as dark as before and doesn't hop up and down every second :good:
Click to expand...
Click to collapse
How did you do the upgrade to 4.3? Seems like it is not yet available for the US. Would you install another SKU from TW lets say, if your tablet were from the US?
I really feel like upgrading cause there are too many things not working well on 4.2.2
efgyy said:
How did you do the upgrade to 4.3? Seems like it is not yet available for the US. Would you install another SKU from TW lets say, if your tablet were from the US?
I really feel like upgrading cause there are too many things not working well on 4.2.2
Click to expand...
Click to collapse
In Switzerland it was OTA :good:
Either download right version from asus.com or wait a bit, I guess it will not take long until it's rolled out everywhere...
Yezariael said:
Auto-brightness is useless: Usually it's much too dark, and the auto-setting is changing with strange behaviors.... it's kinda jumping up and down as other described...
Click to expand...
Click to collapse
I totally agree. It's much too dark on auto and the constant jumping around drives me bat$#! +. For a 4th Gen, nearly $500 tablet, you'd think this sort of thing would be figured out by now.
calimocho said:
I totally agree. It's much too dark on auto and the constant jumping around drives me bat$#! +. For a 4th Gen, nearly $500 tablet, you'd think this sort of thing would be figured out by now.
Click to expand...
Click to collapse
You did not read my statement about update to 4.3, no?
It's very fine now, bright and constant :good:
Yezariael said:
You did not read my statement about update to 4.3, no?
It's very fine now, bright and constant :good:
Click to expand...
Click to collapse
Mine is still the same after the 4.3 update. I can see whatever algorithm it is working. For example, switch to a dark screen, wait 2 seconds, watch it darken a little more once a second for the next three seconds. Then the reverse in switching to a mostly white screen/app.
The good news is the dock doesn't seem to disconnect anymore.
Just can't decide about this thing. I want to love it as much as I loved my TF101 but I just don't (yet?)
calimocho said:
Mine is still the same after the 4.3 update. I can see whatever algorithm it is working. For example, switch to a dark screen, wait 2 seconds, watch it darken a little more once a second for the next three seconds. Then the reverse in switching to a mostly white screen/app.
The good news is the dock doesn't seem to disconnect anymore.
Just can't decide about this thing. I want to love it as much as I loved my TF101 but I just don't (yet?)
Click to expand...
Click to collapse
Theirs nothing wrong with your device. It's the ambient light sensor built into the device. ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xRevilatioNx said:
Theirs nothing wrong with your device. It's the ambient light sensor built into the device. ..
Click to expand...
Click to collapse
Absolutely. It's just really freaking annoying.
I have it right here in a bright office with fluorescent lights, which I would think would vastly marginalize the amount of light reflected from the display itself back into its ambient light sensor. Merely dropping down the notification column causes visible shifts darker (when coming from a light background) in steps, over several seconds. (and it's in the dock on the desk, so the device isn't moving at all)
So my argument is the algorithm used to determine the backlight of the screen puts to much weight on the white balance of the screen. It's distracting and annoying. And it would be one thing if this only happened on "Auto Brightness," which it does not.
Related
Hello Guys,
I bought my HTC One from Dubai (Middle east) version 20 days ago, every thing was perfect with the mobile,
Today, the brightness of the mobile went to the highest mode automatically, I tried to reduce it but it hasn't been reduced technically, is there any solution for this ??
Thank You
I just came in here hoping that someone might have had similar to my issue and this seems fairly close.
At least once per day i have to restart my phone because the bightness seems to go so high that i cant control. If i change it, it does not change the screen brightness.
With a restart, it seems to reset the screen back to the regular brightness.
It is getting so annoying have to restart the phone at least twice a day.
I think its a software issue given the fact that it sorts itself with a restart, not sure what to do apart from a hard reset.
If anyone has any ideas or has seen this before, within a thread or not, advice would be appreciated.
Thanks :good:
trigger365 said:
I just came in here hoping that someone might have had similar to my issue and this seems fairly close.
At least once per day i have to restart my phone because the bightness seems to go so high that i cant control. If i change it, it does not change the screen brightness.
With a restart, it seems to reset the screen back to the regular brightness.
It is getting so annoying have to restart the phone at least twice a day.
I think its a software issue given the fact that it sorts itself with a restart, not sure what to do apart from a hard reset.
If anyone has any ideas or has seen this before, within a thread or not, advice would be appreciated.
Thanks :good:
Click to expand...
Click to collapse
for me even with restarting it doesn't work, some time I leave the phone for one hour then I come back to it and find it's brightness adjustment working, then eventually it goes to the highest brightness mode without any ability to adjust it and so on!
some times the Phone responds and adjust the brightness correctly (when I leave the phone and come back to it in an hour), then eventually it goes to the high brightness mode again without any ability to adjust it again and so on.
I'm afraid it might be a hardware problem since it's not happening with other users according to the reviews online !
Some people have been reporting defective light sensors. This basically causes the phone to believe you're in direct sunlight, turning off the button lights and setting the screen brightness to max. If your button lights do not light up when this happens, even when indoors, then you have a defective device. Contact HTC.
sauprankul said:
Some people have been reporting defective light sensors. This basically causes the phone to believe you're in direct sunlight, turning off the button lights and setting the screen brightness to max. If your button lights do not light up when this happens, even when indoors, then you have a defective device. Contact HTC.
Click to expand...
Click to collapse
Thank you for you reply,
but in this case will this happen even if I'm using the automatic brightness mode ??
Thank you
This is a hardware problem. Auto brightness relies on the light sensor. If the light sensor is broken, then the Auto-brightness feature will malfunction.
From http://www.digitaltrends.com/mobile/htc-one-problems/ :
Problem: Proximity sensors not working
A few people have reported that their sensors aren’t working correctly. You may notice that the capacitive buttons don’t light up and this could actually be a sign that the sensor isn’t working. Try covering the sensors (top left) with your finger and see if the capacitive buttons light up. You can also test the sensors using a free app called Android Sensor Box.
Solution: If they aren’t working then it’s a hardware fault and you’ll have to return the phone and get a replacement.
Click to expand...
Click to collapse
Seriously, if you don't like the way your phone is behaving, contact HTC. They will fix it.
I have done the factory reset now and the same thing happened
tareknet89 said:
I have done the factory reset now and the same thing happened
Click to expand...
Click to collapse
Hardware issues can't be solved by a factory reset. You MUST send the device in for repair or replacement.
sauprankul said:
Hardware issues can't be solved by a factory reset. You MUST send the device in for repair or replacement.
Click to expand...
Click to collapse
yes I was just trying to make sure that it's a hardware problem, now I'm contacting htc for help.
Thank you very much I really appreciate it.
Try this. This app will keep your brightness at the level you set it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent using my HTC One from that FBI van parked down the street.
ghostryder12 said:
Try this. This app will keep your brightness at the level you set it.
Sent using my HTC One from that FBI van parked down the street.
Click to expand...
Click to collapse
from the time I installed this app all the problems are solved even without using the app!!!!
wasn't it a hardware problem !
tareknet89 said:
from the time I installed this app all the problems are solved even without using the app!!!!
wasn't it a hardware problem !
Click to expand...
Click to collapse
Sweet. Maybe the apk itself shook something loose.
Sent from my HTC One using Tapatalk 2
ghostryder12 said:
Sweet. Maybe the apk itself shook something loose.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I don't know, even with factory reset the problem wasn't solved, that's strange
Thank you very much :good:
tareknet89 said:
I don't know, even with factory reset the problem wasn't solved, that's strange
Thank you very much :good:
Click to expand...
Click to collapse
Dude, I'm just glad you got it working again.
Sent from my HTC One using Tapatalk 2
Mine doesn't seem to have solved itself with that app
I tried putting my fingers ovetthe proximity sensors and it changed the screen back to normal from the original really bright problem.
Should I contact my network and ask for a replacement? That sounds like a hardware issue to me.
Also, whilst on this, what's the nearest to back up everything? HTC Backup? Does that work well? I'll need to back up launcher settings etc too I guess?
Sent from my HTC One using xda app-developers app
App called Lux Light also works very well.
So I just want to give a little status update with proof of what we have going so far. I am still trying to work out the bugs but I have managed to get root and TWRP on the Lg G Watch R (lenok) using much of the same files from Dory the original g watch because almost all the hardware is the same. All I had to do was open their recovery file and throw in our zImage and it booted, and I was actually quite surprised bahaha. And once we have TWRP we can flash anything we want, such as the SuperSU package from Chainfire which enables root for us. But because this is wear most of the rootey things will just allow us to access system files such as say the vibration motor. And I can tell the vibrataion motor on this device is weaker than it is capable of doing because on TWRP the thing's vibration was SUPER strong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
subscribed - looks promising, well done
My next step will be to find a good vibration boost setting and implement it. I can tell it has a very capable vibration motor and can match the Pebble in strength and duration.
Great work! Looking forward to seeing what develops.
tonu42 said:
So I just want to give a little status update with proof of what we have going so far. I am still trying to work out the bugs but I have managed to get root and TWRP on the Lg G Watch R (lenok) using much of the same files from Dory the original g watch because almost all the hardware is the same. All I had to do was open their recovery file and throw in our zImage and it booted, and I was actually quite surprised bahaha. And once we have TWRP we can flash anything we want, such as the SuperSU package from Chainfire which enables root for us. But because this is wear most of the rootey things will just allow us to access system files such as say the vibration motor. And I can tell the vibrataion motor on this device is weaker than it is capable of doing because on TWRP the thing's vibration was SUPER strong.
Click to expand...
Click to collapse
Awesome work, did you tried to relock your bootloader and was you able to grab a complete dump/backup of the Device befor testing the recovery? Coz there is no factory image yet
bluedragon1982 said:
Awesome work, did you tried to relock your bootloader and was you able to grab a complete dump/backup of the Device befor testing the recovery? Coz there is no factory image yet
Click to expand...
Click to collapse
We have stock boot, system and recovery already pulled. That's the bulk of a factory image. I don't plan to relock bootloader so I haven't tested that.
thanks for your work, tonu!
I'v seen that you are investigating various switches and tweaks - I was hoping you could look into the power-saving settings, maybe there is a way to solve the 2 minute bug
2k4ever said:
thanks for your work, tonu!
I'v seen that you are investigating various switches and tweaks - I was hoping you could look into the power-saving settings, maybe there is a way to solve the 2 minute bug
Click to expand...
Click to collapse
I thought the two minute "bug" was a feature to save battery and avoid screen burn. I will look into it but I think it lies in frameworks and I dont wanna go messing with them.
Maybe wear lollipop will change it.
tonu42 said:
I thought the two minute "bug" was a feature to save battery and avoid screen burn. I will look into it but I think it lies in frameworks and I dont wanna go messing with them.
Maybe wear lollipop will change it.
Click to expand...
Click to collapse
It maybe save battery - but a watch that purposefully displays a wrong time I wouldn't call a feature - and if it is at least let me turn it off @google
and it actually should make burn-in worse as the same image is displayed for a longer time
finally, from what I've read, the other AW watches don't have this "feature"
I wouldn't ask you to mess with the frameworks, but maybe the problem arises from a wrongly set power-saving switch or somthing
And yes, I'm hoping that Lollipop will fix it but I wouldn't mind a fix if you are willing and interested to look into it
thanks and good luck!
2k4ever said:
It maybe save battery - but a watch that purposefully displays a wrong time I wouldn't call a feature - and if it is at least let me turn it off @google
and it actually should make burn-in worse as the same image is displayed for a longer time
finally, from what I've read, the other AW watches don't have this "feature"
I wouldn't ask you to mess with the frameworks, but maybe the problem arises from a wrongly set power-saving switch or somthing
And yes, I'm hoping that Lollipop will fix it but I wouldn't mind a fix if you are willing and interested to look into it
thanks and good luck!
Click to expand...
Click to collapse
I've found some things that might point me in the right directions, idk if it will work but you can try to turn off ambient burn in protection all together, while I really do not recommend this on an led display it might fix it. I would estimate after a year or so the burn in would be pretty visible and might affect colors.
tonu42 said:
I've found some things that might point me in the right directions, idk if it will work but you can try to turn off ambient burn in protection all together, while I really do not recommend this on an led display it might fix it. I would estimate after a year or so the burn in would be pretty visible and might affect colors.
Click to expand...
Click to collapse
thanks, but I really wouldn't recommend doing that
besides, from what I can tell, the burn-in protection isn't the problem, as the watch face shifts around as it should, so the screen is redrawn, but the time is not updated simultaneously
2k4ever said:
thanks, but I really wouldn't recommend doing that
besides, from what I can tell, the burn-in protection isn't the problem, as the watch face shifts around as it should, so the screen is redrawn, but the time is not updated simultaneously
Click to expand...
Click to collapse
Thinking about it its a really weird issue. The system knows the correct time because the ambient protection uses the current system time as a sort of random number generator, it takes the system time in milliseconds divides by 60000 and uses that as a variable to shift the screen. Now on the shift I dont know why they didnt make it change the drawn time..... too weird.
tonu42 said:
Thinking about it its a really weird issue. The system knows the correct time because the ambient protection uses the current system time as a sort of random number generator, it takes the system time in milliseconds divides by 60000 and uses that as a variable to shift the screen. Now on the shift I dont know why they didnt make it change the drawn time..... too weird.
Click to expand...
Click to collapse
simple: its a bug
one reason could be that the cpu gets throttled so much that the update doesn't get out
I'v noticed that sometimes the minute hand jumps two minutes, first one and than a second later the hand moves again
and to me it seems to build up: if not activated for extended periods, the time seems to fall further and further behind
Our watch has some extensive power-saving features - at least LG claims that power consumption falls to 10% when in always on mode
I suspect that that's too much, as the other AW watches don't seem to have this problem
@tonu42 hey mate! was randomly checking your tread and saw that you have the twrp gui offcenterd issue like the moto360 tread witch im currently fixing.
i quickly realize that theme should work on both the moto360 and LG G Watch R! So once if i get fix, both should benefit from it!
Moto360 TWRP tread: http://forum.xda-developers.com/moto-360/development/unofficial-twrp-2-8-1-0-moto-360-t2966750
More info what is currently fix and Need to be fixed (including pictures) : http://forum.xda-developers.com/showpost.php?p=57573277&postcount=48
Fell free to add me on G+
mkaymuzik said:
@tonu42 hey mate! was randomly checking your tread and saw that you have the twrp gui offcenterd issue like the moto360 tread witch im currently fixing.
i quickly realize that theme should work on both the moto360 and LG G Watch R! So once if i get fix, both should benefit from it!
Moto360 TWRP tread: http://forum.xda-developers.com/moto-360/development/unofficial-twrp-2-8-1-0-moto-360-t2966750
More info what is currently fix and Need to be fixed (including pictures) : http://forum.xda-developers.com/showpost.php?p=57573277&postcount=48
Fell free to add me on G+
Click to expand...
Click to collapse
Sounds good, I could figure out how to make it look nice on device but I just don't have the time. Full time student and work almost full time, not enough time in the day. Hopefully over the next week I plan to pump some other stuff out related the GWR.
tonu42 said:
Sounds good, I could figure out how to make it look nice on device but I just don't have the time. Full time student and work almost full time, not enough time in the day. Hopefully over the next week I plan to pump some other stuff out related the GWR.
Click to expand...
Click to collapse
no worry man and nice to meet you by the way. im also im the same position ish but do have time but dont have job atm.
I don't know exactly what happened, but I think burn-in protection is NOT working on LCA44B. Since yesterday I've had Instaweather faces burn into my watch, and the Red face, which I've used intermittently for 9 months, has now burned into my screen in less than 12 hours of use. Screen brightness is less than 1, something is seriously messed up in the latest firmware. Anyone else experiencing this?
Sent from my Nexus 5 using Tapatalk
Display is shifting, turns out LG is absolutely stupid, so know that THE RED WATCH FACE WILL BURN IN TO YOUR SCREEN. They added massive grey circles to the date and month icons, which burn in. Every tick mark now burns in as well. I have never experienced any issues with burn in over the 10 months I've owned it, and now it's been burned in twice in 2 days. Something is amiss with the latest update, so definitely monitor your watch for signs of burn in.
Sent from my Nexus 5 using Tapatalk
I've been experiencing burn in even with the previous update
I've experienced burn with all my watch faces on this update, and have had issues with burn in ever since flashing the custom kernel to gain WiFI, with the issues persisting even after the burn in was fixed. Sometimes however I do notice the face moving as expected, so I am not sure what is causing the problem overall. If anybody has any ideas as to solutions to this, I'm sure a fair few people would be glad to hear them, as it isn't much fun seeing the hour icons when you're say in the settings menu.
Thanks,
x10man
I highly doubt this has something to do with the latest update.
1. I've had the red face burn into my watch before lollipop was on my watch even, just because the hour marks are too big to be properly shifted in ambient mode
2. I've observed my current watch face (FORM) and it seems to shift just normally
Do you guys happen to have Developer Options enabled? I tried enabling it today and just noticed that the option Force Burn-in Protection was disabled by default.
I don't know whether it was because of that option, the newest update, or just the fact that reading over this thread made me inspect my watch more carefully, but I now notice some burn in on my watch for the first time. It is quite apparent when the notification shade is pulled down.
My watch face also has very thin graphics and I even put a black transparent overlay on my watch face to make it even darker in ambient mode.
Edit: seems the burn-ins are only a temporary (at least for me). Left the screen off for a while and its good again.
I have developer options enabled, and enabling force protection disables again after a reboot. Burn ins are temporary for me too, but I'd still rather they didn't have them at all. I don't just experience burn in on the analogue faces such as red, I currently have a "9" burn onto my watch from 25 minutes of the "together" face and watches with very thin lines such as F04 for Round Wear also burn in, after very short periods of time. It is easy to get these to go again, however I'd prefer the burn in protection to work properly. I never had these issues on 5.0, they've only started since 5.1 for me, although I am not sure if that was 5.1 overall, or 5.1 after the custom kernel flash.
Thanks,
X10man
Forcing the burnin protection has no effect if you did not messed up the default burn-in protection files. The face will still shift no matter how the switch is being set.
If you will force the burnin protection settings file to not shift, then this switch will override that.
I have no burnin at all and I have the watch for almost a year now.
I don't have any problems with burn-in after update (or before). And I'm using Odyssey watchface red + disabled minimal ambient mode so according to everything I read here I should have huge burn-in. I have this watch over 6 months, 0 problems
this is how it looks also in ambient mode ( i have red color)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
timon12 said:
I don't have any problems with burn-in after update (or before). And I'm using Odyssey watchface red + disabled minimal ambient mode so according to everything I read here I should have huge burn-in. I have this watch over 6 months, 0 problems
this is how it looks also in ambient mode ( i have red color)
Click to expand...
Click to collapse
Are you rooted etc? I'm wondering if any of the non-stock portions of my watch are causing this. I have TWRP installed, and my bootloader unlocked. It doesn't seem to make sense that some people have it and some do not, on the same watch faces et cetera. I'm not rooted, and have the stock ROM and kernel installed.
Thanks,
X10man
EDIT: I have reflashed an entirely stock system, performed a factory reset and locked my bootloader, and I can verify my watch face is now moving. I will update further in regards to whether burn in is still an issue, or if this was a fix for me
I'm full stock, never rooted or anything and I have some burn in
x10man said:
Are you rooted etc? I'm wondering if any of the non-stock portions of my watch are causing this. I have TWRP installed, and my bootloader unlocked. It doesn't seem to make sense that some people have it and some do not, on the same watch faces et cetera. I'm not rooted, and have the stock ROM and kernel installed.
Thanks,
X10man
EDIT: I have reflashed an entirely stock system, performed a factory reset and locked my bootloader, and I can verify my watch face is now moving. I will update further in regards to whether burn in is still an issue, or if this was a fix for me
Click to expand...
Click to collapse
Now I'm on stock rom, kernel and recovery, with unlocked bootloader, not rooted. I had Leedroid rom but voice recognition wasn't working that good like on stock (dunno why). Before Leedroid I was on stock without any modifications so IMO software does not affect this burn-in thing. also I'm using 6 brightness all the time + screen always on
timon12 said:
I'm using 6 brightness all the time
Click to expand...
Click to collapse
This is the perfect recipe for a nice burn-in. Of course it all depends on the colours used and the thickness of the lines involved ... but in general, max brightness on an OLED display means burn-in and shorter life.
// sent from my phone //
again, no burn in after many months I'm still using 6 brightness + screen always on.
timon12 said:
again, no burn in after many months I'm still using 6 brightness + screen always on.
Click to expand...
Click to collapse
No burn in here either, had the same face for over 4 months at 3+ brightness and always screen on.
Until now, I've actively avoided AMOLED screens, in part due to the ability to get screen burn in. I'm still not thrilled about it, but it seems no flagship has LCD anymore and I'll have to make the trade-off.
I get some of the benefits of AMOLED, but this surprised me a bit to find on a gaming phone since games have static images (scores, gauges, maps, icons, etc). I also know that running an AMOLED at full brightness increases the burn in risk, but I'll be using this daily in bright sunlight and will need the screen fairly bright.
So what's the current expectation for the ROG 2 screen when it comes to that? Any word on if burn in will be much of a risk anymore? Would the Asus U.S. Warranty cover that, and for how long?
Burn in is probably a far smaller issue than you'd think. I've used AMOLED displays since 2010 on several different devices and never had an issue. It does happen but probably far less common than you'd think.
The only AMOLED device I've had that experienced burn in was a Samsung Galaxy Note 5, which I used for many years and was my daily phone up until I received this ROG Phone 2 a week ago. Even then, I didn't notice the burn in on it until about a year ago, and only found it by deliberately looking for it by using an app to show full screen solid colors. Even to this day I don't notice the burn in on that Note 5 during normal use. The entire time I used the Note 5 I had the brightness set to max with adaptive brightness on.
willhemmens said:
Burn in is probably a far smaller issue than you'd think. I've used AMOLED displays since 2010 on several different devices and never had an issue. It does happen but probably far less common than you'd think.
Click to expand...
Click to collapse
Especially with gestures replacing the static nav bar. Those would burn in over time. But the status bar stays pretty active, so there shouldn't be much chance their either
bluegizmo83 said:
The only AMOLED device I've had that experienced burn in was a Samsung Galaxy Note 5, which I used for many years and was my daily phone up until I received this ROG Phone 2 a week ago. Even then, I didn't notice the burn in on it until about a year ago, and only found it by deliberately looking for it by using an app to show full screen solid colors. Even to this day I don't notice the burn in on that Note 5 during normal use. The entire time I used the Note 5 I had the brightness set to max with adaptive brightness on.
Click to expand...
Click to collapse
My wife prefers the Notes and every one of hers got burn in. Her last one was the S7 (due to the N7 fiasco), and I noticed burn in within a year. She rarely has the brightness cranked, which is part of why I'm still on the fence.
Now that I have android auto radios in all my cars I don't expect to get much burn in from now on, but my note 8 always has Waze ghosted on the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As others have mentioned before the benefits of Amoled screens far out take the LCD ones in many areas. For example one thing I hated about LCD screens because of the technology was the uneven side/bottom light spots which can be easily seen in a dark room and were very annoying to see.
Regarding Burn in, there is an easy way to avoid it in the long run by using gestures for system navigation and in regards of the status bar you can use any 3rd party app which can hide the status bar. Personally I use "Immersive manager" app to hide the status bar on ASUS launcher and in some apps which I don't like to see it in, and so because of the switch between the home screen and apps, the status bar isn't static and for that reason i doubt burn in will be an issue.
I would caution about the "Always-On Display" option of the Asus Rog Phone 2. If you go to bed and leave the phone face-up (proximity sensor not covered) then it will leave the static clock graphics up all night. I could imagine that being burned in over time.
RogPhoney said:
I would caution about the "Always-On Display" option of the Asus Rog Phone 2. If you go to bed and leave the phone face-up (proximity sensor not covered) then it will leave the static clock graphics up all night. I could imagine that being burned in over time.
Click to expand...
Click to collapse
I was watching a review video on it yesterday and it showed what looked like the AOD clock shifting (it was a short cutaway shot, so could be mistaken). I will keep an eye on it, though, to see if it does move.
Just like you, I avoid AMOLED screens. I had an S3, burn ins from web browser... I watch YouTube a lot. I am not sure the AMOLED screen is for me. It became difficult to choose a phone.
SchnauzerZoom said:
Just like you, I avoid AMOLED screens. I had an S3, burn ins from web browser... I watch YouTube a lot. I am not sure the AMOLED screen is for me. It became difficult to choose a phone.
Click to expand...
Click to collapse
Just enable Dark Mode within YouTube and assuming you watch in full screen mode, you should not have any problems. I personally run YT for about 3-4 hours everyday: the phone sits below my monitor at work and I have earphones on. Glance at the screen from time to time, since what I usually do doesn't require full concentration at most times. Never faced burn in from YouTube.
I did face some issues on Quora though, but that was with a Moto G4+ and seemed to be temporary. The logo bar on top stayed for a while, ghosting as I used other apps but went away in a few minutes after I left the page.
Amoled screens burn-in is much less likely to happen now due to advancement in screen technology and also software implementation to counter it.
There used to be a time when averagely 30-40% of screens had a form of burn-in or another.
Unless you're unfortunate to get a defective screen, I doubt if burn-in will be an issue for you.
I have a 2-year old Huawei Mate 10 Pro which I've used so much and mostly outside (full screen brightness), but there isn't a sign of burn-in on it.
Though it would be important to know the screen manufacturer for the ROG II as not only you can have an idea of the quality but also aesthetics.
I already have some lines and screen uneveness in lower brightness and mostly gray color, i wouldnt call them burn-ins but the device screen is diffinitely defective as it's only 4 weeks old and the screen was uneven from the beginning
Btw the quality and sharpness of colors is nowhere close to my father's galaxy a40 so either my device is a complete defect or the screen is just not that high-end stuff
And lets not forget the rediculous issue of getting red tine when lowering the brightness it sometimes drives me crazy, still the 120hz refresh rate is so great i cant think about any other phone!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow.... Finally the update for multi-tasking
what does the update ade for multi tasking? And can you finally use custom icons on default launcher? I'm on x fold 2 and haven't gotten anything like that...
Unfortunately, the update is not yet displayed for me
It's currently out for me. If it isn't out yet, reboot your device and try again.
That being said the software experience is really REALLY similar to the vivo x fold 2. Just as snippy and I've been waiting on the implementation of the dock for a year.
For those with the original vivo x fold, there may not be a huge reason to upgrade given these fresh quality of life upgrades. Especially if you have a vivo x fold with a boot loader unlocked (or if you joined the developer beta/public beta in winter last year). I wish this came out last year like the Samsung ones but I can't really complain.
I still find it a pity that WhatsApp notifications are not displayed on the lock screen/always on screen
NeoGoku123 said:
I still find it a pity that WhatsApp notifications are not displayed on the lock screen/always on screen
Click to expand...
Click to collapse
I can see them with the app AOA: Always on display
I used that app, AOA, a few days ago and it worked great and then the next day never came back on. No matter what I did, even reboot the phone, it never appeared again. I turned the app off and on, I even locked it to the home screen so it didn't get shut down and nothing. Any ideas?
I tried the update. Like it. Only Battery seems to take a hit. Maybe it needs time.....
Cloverfield_33 said:
I used that app, AOA, a few days ago and it worked great and then the next day never came back on. No matter what I did, even reboot the phone, it never appeared again. I turned the app off and on, I even locked it to the home screen so it didn't get shut down and nothing. Any ideas?
Click to expand...
Click to collapse
Exactly the same issue for me with AOA. Never shows up even though I pinned it, set auto start, and battery mgmt to max. I also turned off Vivo's always on display, and all I see the fingerprint scanner image.
gkarkala said:
Exactly the same issue for me with AOA. Never shows up even though I pinned it, set auto start, and battery mgmt to max. I also turned off Vivo's always on display, and all I see the fingerprint scanner image.
Click to expand...
Click to collapse
I managed to get it working again today by turning off the custom time (I had it turn off 10pm to 5am). I ticked the ALWAYS ON box and now it's working again. For now...
Cloverfield_33 said:
I managed to get it working again today by turning off the custom time (I had it turn off 10pm to 5am). I ticked the ALWAYS ON box and now it's working again. For now...
Click to expand...
Click to collapse
Did not work. I never setup custom time, and just verified. Do you still see the fingerprint icon?
gkarkala said:
Did not work. I never setup custom time, and just verified. Do you still see the fingerprint icon?
Click to expand...
Click to collapse
No but even when I had the finger print button on on AOA, it didn't do anything, it was just there for show.
Cloverfield_33 said:
No but even when I had the finger print button on on AOA, it didn't do anything, it was just there for show.
Click to expand...
Click to collapse
okay. then somehow Vivo is killing the AOA process when I turn off the display.
gkarkala said:
okay. then somehow Vivo is killing the AOA process when I turn off the display.
Click to expand...
Click to collapse
I was stumped too. Was just about to delete it till I tried my fix. The stock aod is nice however can't get notifications for anything but phone and messages and the battery percentage is too small to see properly. I like the upside down purple triangle effect though and will go back to that if AOA fails again.
Cloverfield_33 said:
I was stumped too. Was just about to delete it till I tried my fix. The stock aod is nice however can't get notifications for anything but phone and messages and the battery percentage is too small to see properly. I like the upside down purple triangle effect though and will go back to that if AOA fails again.
Click to expand...
Click to collapse
Agree. Vivo's software philosophy is strange: no matter whether it is focused on Chinese or global users. Some of the restrictions does not even make sense even for the Chinese market.
But, damn the hardware is excellent! I am so sick of the narrow screen of Samsung Fold, I am tolerating the UX issues of Vivo. I also got Oppo Find N2, but that software is worse than Vivo.
gkarkala said:
Agree. Vivo's software philosophy is strange: no matter whether it is focused on Chinese or global users. Some of the restrictions does not even make sense even for the Chinese market.
But, damn the hardware is excellent! I am so sick of the narrow screen of Samsung Fold, I am tolerating the UX issues of Vivo. I also got Oppo Find N2, but that software is worse than Vivo.
Click to expand...
Click to collapse
Agreed. I was with Samsung since 2016 before this phone and my lost phone was the z fold 2 which was an amazing phone don't get me wrong but that narrow outside screen annoyed me more and more as the years went on. The fold 5 is going to he just as poor and the pixel fold will be too short and have problems of its own, plus just as expensive. Vivo was a no brainier, hundreds cheaper, amazing inside and outside screen, ridiculous battery life and charging speed, 1800 nits brightness plus much more. The software is definitely a learning curve and like you said, some things don't make sense at all. I'm struggling with notifications and I still, no matter what I do, can't get floating notifications for WhatsApp when I'm using the phone. If phone is on standby I get the message preview on lock screen, dark mode or not but when using the phone all I get is the icon at top left. I have every setting to allow notifications, I'm so stumped. Weirdly I'll get the message preview if I already have a WhatsApp message unread and then someone else sends, me a message. I get a line from each new message then. Very frustrating.
Cloverfield_33 said:
Agreed. I was with Samsung since 2016 before this phone and my lost phone was the z fold 2 which was an amazing phone don't get me wrong but that narrow outside screen annoyed me more and more as the years went on. The fold 5 is going to he just as poor and the pixel fold will be too short and have problems of its own, plus just as expensive. Vivo was a no brainier, hundreds cheaper, amazing inside and outside screen, ridiculous battery life and charging speed, 1800 nits brightness plus much more. The software is definitely a learning curve and like you said, some things don't make sense at all. I'm struggling with notifications and I still, no matter what I do, can't get floating notifications for WhatsApp when I'm using the phone. If phone is on standby I get the message preview on lock screen, dark mode or not but when using the phone all I get is the icon at top left. I have every setting to allow notifications, I'm so stumped. Weirdly I'll get the message preview if I already have a WhatsApp message unread and then someone else sends, me a message. I get a line from each new message then. Very frustrating.
Click to expand...
Click to collapse
Exactly the same issue for me for Whatsapp messages. No floating message notifications.
gkarkala said:
Exactly the same issue for me for Whatsapp messages. No floating message notifications.
Click to expand...
Click to collapse
OK so it's not just me. It's so weird isn't it. Hopefully it's something that can be fixed soon.
Google messages notifications works in dark mode now