Related
Hi All
I have only been using these forums for a week but it is clear that a lot of people (like me) have concerns about how best to set up their G Watch R to avoid burn in, prolong battery life, etc. I have put together some of the advice that users have kindly given me. I’d welcome people’s input on this, to clarify anything I’ve missed and in particular answer the questions I have added below. It would great to set this up as a Sticky so new users could set their watches up correctly.
Colour Schemes
• ALWAYS use more green/red themes (and combinations - yellow, orange) because red and green are the most resilient OLED compounds.
• AVOID using BLUE in "always on" mode.
• WHITE has a lot of blue in it ... so, a long time of white theme usage will create burn-in in all colours, especially in the blue colour.
• Remember on OLED, black means "off". A mostly black watchface burns almost no juice.
• When you define a bright text or colour, look at the hex code of the colour : XXYYZZTT where XX is hexa code for transparency, YY is red level, ZZ is green level and TT is blue level. ... so try keeping the last two hex numbers in the low area, meaning below 100 (00 means 0, FF means 256, as colour intensity). – HOW TO DO THIS?
• HANDS AND HAND MAKERS ARE OFTEN WHITE, HOW CAN WE BEST USE THEM?
Style
• Avoid thick bright lines
• Keeping one pixel bright (because it's in the middle of a thick line) is something you absolutely need to avoid, for example, on analogue hands the middle won’t move.
• Display digital clock in small thin font
• Android wear shifts the whole face a few pixels in different directions every now and then to try to eliminate some of the burn in.
• If the respective elements are no more than 2 pixels wide, they will not cause that much burn-in because the dim mode pixel shifting will move that object around enough to let the main pixels "rest".
• The time, if is displayed in the analog style (with dials) will not cause burn-in because the bright part of the image is moving around so one can use brighter clock hands for this.
• WHAT ARE THE BEST STYLES TO USE FOR DIGITAL AND ANALOGUE?
Brightness
• NEVER use it at max (or high) brightness more than few seconds with a static image.
• Use very very VERY LOW brightness always on/dim mode.
• It's not constant illumination that is causing burn-in in the first place, but constant illumination with "high brightness".
• Default DIM mode of the Watch G is waaaaay to bright for the purpose of the "dim" mode - HOW TO CHANGE THIS?
• A black, transparent layer is needed on top of the dim mode in order to prevent this – HOW TO DO THIS?
• To adjust just the dim mode face only you'll need to use one of the face making apps and duplicate the parts and make a separate dim mode.
• HOW CAN WE BEST SET UP BRIGHTNESS FOR “ON” and “DIM” (USING APPS LIKE SWAPP TRUE DARK WEAR)?
Good Watchfaces
• Almost all the watchfaces from Smartwatch Bureau F01,F03, V01, V02... A45, A42.... have a setting for brightness in dim mode. So we can have a dim mode very dark and we can choose the face color for dim between 7 colors : green, blue, cyan, red..... so with this faces we can avoid easily all burn issue.
• Also the digital from Smartwatch Bureau which can be displayed in green in dim mode to avoid burning
• CAN PEOPLE OFFER SOME EXAMPLES OF GOOD WATCHFACES (INCLUDING CUSTOM FACES) AND DISPLAY SETTINGS THAT WOULD HELP TO AVOID BURN-IN?
Useful Apps
• SWApp True Dark Wear – to set the brightness below the lowest default on the watch
• Stuck Pixel Fixer for Wear app - Try running "stuck pixel fixer" for few hours, with the display set to max brightness. That should help getting rid of the ghosting and also will "age" your pixels in order to be able to display static images w/o burning.
• Mini Wear launcher – also allows you to set lower brightness setting
• CAN PEOPLE OFFER TUTORIALS ON HOW BEST TO USE THESE TO SET BRIGHTNESS AND “ALWAYS ON” AND FIX ANY GHOSTING ISSUES?
Your input would be most welcome
Steham said:
Hi All
I have only been using these forums for a week but it is clear that a lot of people (like me) have concerns about how best to set up their G Watch R to avoid burn in, prolong battery life, etc. I have put together some of the advice that users have kindly given me. I’d welcome people’s input on this, to clarify anything I’ve missed and in particular answer the questions I have added below. It would great to set this up as a Sticky so new users could set their watches up correctly.
Colour Schemes
• ALWAYS use more green/red themes (and combinations - yellow, orange) because red and green are the most resilient OLED compounds.
• AVOID using BLUE in "always on" mode.
• WHITE has a lot of blue in it ... so, a long time of white theme usage will create burn-in in all colours, especially in the blue colour.
• Remember on OLED, black means "off". A mostly black watchface burns almost no juice.
• When you define a bright text or colour, look at the hex code of the colour : XXYYZZTT where XX is hexa code for transparency, YY is red level, ZZ is green level and TT is blue level. ... so try keeping the last two hex numbers in the low area, meaning below 100 (00 means 0, FF means 256, as colour intensity). – HOW TO DO THIS?
• HANDS AND HAND MAKERS ARE OFTEN WHITE, HOW CAN WE BEST USE THEM?
Style
• Avoid thick bright lines
• Keeping one pixel bright (because it's in the middle of a thick line) is something you absolutely need to avoid, for example, on analogue hands the middle won’t move.
• Display digital clock in small thin font
• Android wear shifts the whole face a few pixels in different directions every now and then to try to eliminate some of the burn in.
• If the respective elements are no more than 2 pixels wide, they will not cause that much burn-in because the dim mode pixel shifting will move that object around enough to let the main pixels "rest".
• The time, if is displayed in the analog style (with dials) will not cause burn-in because the bright part of the image is moving around so one can use brighter clock hands for this.
• WHAT ARE THE BEST STYLES TO USE FOR DIGITAL AND ANALOGUE?
Brightness
• NEVER use it at max (or high) brightness more than few seconds with a static image.
• Use very very VERY LOW brightness always on/dim mode.
• It's not constant illumination that is causing burn-in in the first place, but constant illumination with "high brightness".
• Default DIM mode of the Watch G is waaaaay to bright for the purpose of the "dim" mode - HOW TO CHANGE THIS?
• A black, transparent layer is needed on top of the dim mode in order to prevent this – HOW TO DO THIS?
• To adjust just the dim mode face only you'll need to use one of the face making apps and duplicate the parts and make a separate dim mode.
• HOW CAN WE BEST SET UP BRIGHTNESS FOR “ON” and “DIM” (USING APPS LIKE SWAPP TRUE DARK WEAR)?
Good Watchfaces
• Almost all the watchfaces from Smartwatch Bureau F01,F03, V01, V02... A45, A42.... have a setting for brightness in dim mode. So we can have a dim mode very dark and we can choose the face color for dim between 7 colors : green, blue, cyan, red..... so with this faces we can avoid easily all burn issue.
• Also the digital from Smartwatch Bureau which can be displayed in green in dim mode to avoid burning
• CAN PEOPLE OFFER SOME EXAMPLES OF GOOD WATCHFACES (INCLUDING CUSTOM FACES) AND DISPLAY SETTINGS THAT WOULD HELP TO AVOID BURN-IN?
Useful Apps
• SWApp True Dark Wear – to set the brightness below the lowest default on the watch
• Stuck Pixel Fixer for Wear app - Try running "stuck pixel fixer" for few hours, with the display set to max brightness. That should help getting rid of the ghosting and also will "age" your pixels in order to be able to display static images w/o burning.
• Mini Wear launcher – also allows you to set lower brightness setting
• CAN PEOPLE OFFER TUTORIALS ON HOW BEST TO USE THESE TO SET BRIGHTNESS AND “ALWAYS ON” AND FIX ANY GHOSTING ISSUES?
Your input would be most welcome
Click to expand...
Click to collapse
Mate i think your over analysing ! its only a watch!
All i have done is change my watch face every day and use it as normal! ok i do have it set to screen off but even so i do think you can over worry about things like burn in. The majority of people who own these watches dont come on forums and i bet none of them suffer burn in!
And be honest, by the time it could get a problem you probably already got the other latest greatest. I bought it, use it and didn't even check if there's burn in. I change faces now and then, finished!
Steham said:
•CAN PEOPLE OFFER TUTORIALS ON HOW BEST TO USE THESE TO SET BRIGHTNESS AND “ALWAYS ON” AND FIX ANY GHOSTING ISSUES?
Your input would be most welcome
Click to expand...
Click to collapse
You could have given some credits for the source of information in the first post ....
As a tutorial: Create your custom watch face using WatchMaker or Facer (I also bought Facer to test it but I personally use WatchMaker because it's more versatile).
All the hex codes described above were in direct relation with custom watch faces or with image editors where you can choose all those parameters.
You can simply download a watch face that you like (for these custom build softwares) and learn from its internal settings.
Good luck with your new toy.
Here's an updated and simplified thread on installation and configuration for LED.
Video Tutorial https://youtu.be/3rREUOK52sQ
• Disable ROM LED Notifications. Go to Settings > Notifications. Tap on the cog on the top right corner and go to
-Battery Charging Light > Disable
-Notifications Light > Disable
• Install Light Flow Lite.
https://play.google.com/store/apps/details?id=com.rageconsulting.android.lightflowlite&hl=fr
• Go to Settings > Device & Root > activate "Direct Mode" & "Root Mode".
• Again go to Settings > LED Control > scroll down and activate "RGB Control".
• Now go to Notification Settings and choose the app you wish to add LED to, open menu (3 dots menu) and go to settings.
• Once there swipe left 2 times to get to "Light".
• Make sure that the first box "Enable Light" is on.
• Scroll down until you see RGB LED & RGB Brightness boxes respectively.
• In RGB LED choose "solid" or "flash" whichever you prefer.
• In RGB Brightness set the color value (table below).
• Test it by pressing "TEST" button on top right corner.
RGB Colors Lenovo P2:
Yellow = 256256256
Pale Blue = 255255255
Marine Blue = 255
Green = 255255
Purple = 128128128
White = 256128128
Red = 128256256
Pink = 128256128
Huge shout out to @xewonder for being the first to make a tutorial. This wouldn't be possible without you.
Original thread:
https://forum.xda-developers.com/lenovo-p2/themes/lenovo-p2-rooted-custom-led-t3589859/
Thanks for the tut, but it didnt work
i am on RR 7.1.2 rom ( by default Blue led was working) but even after doing all these.. the LED didnt showup with new colour .. its just BLANK ..
i doubted the free app, and purchased it..
same result with purchased app too ..
it didnt work
nandakis4 said:
Thanks for the tut, but it didnt work
i am on RR 7.1.2 rom ( by default Blue led was working) but even after doing all these.. the LED didnt showup with new colour .. its just BLANK ..
i doubted the free app, and purchased it..
same result with purchased app too ..
it didnt work
Click to expand...
Click to collapse
Sorry to hear that, i'm on AOSP extended ROM (AEX) 7.1.2
As per your info i'll update the title of thread.
Have your tried the old method that's posted at the end? Might be worth a shot.
Milan-XDA said:
Sorry to hear that, i'm on AOSP extended ROM (AEX) 7.1.2
As per your info i'll update the title of thread.
Have your tried the old method that's posted at the end? Might be worth a shot.
Click to expand...
Click to collapse
Thanks for replying .. I saw the old method too ..
There was only one step extra : to disable led on phone ..
I have tried that too ,no luck ..
Restored someone's working settings backup.txt ..but it didn't work ..
I guess it's wrong with rr ROM ..
It works on AEX! Thanks for the fix @Milan-XDA
I did some more changes (underlined) and works 100% by using Light Flow Legacy :Led Control!
• Disable Battery Charging Light + Notifications Light from the settings!
• Install Light Flow Legacy :Led Control.
https://play.google.com/store/apps/details?id=com.rageconsulting.android.lightflowlegacy&hl=en
• Go to Settings > Device & Root > activate "Direct Mode" & "Root Mode".
> Again go to Settings > LED Control > scroll down and activate "RGB Control" + Activate "wled control"
• Now go to Notification Settings and choose the app you wish to add LED to, open menu (3 dots menu) and go to settings.
• Once there swipe left 2 times to get to "Light".
• Make sure that the first box "Enable Light" is on.
• Scroll down until you see RGB LED & RGB Brightness boxes respectively.
> In RGB LED choose Flash - Hardware controlled.
• In RGB Brightness set the color value (table below).
• Test it by pressing "TEST" button on top right corner.
Working LED:
Marine Blue = 255
Green = 255255
Bright red = 13631488
Pale Blue = 6316128
Crabapple Red (pink) = 11796512
Orange = 12607488
Green = 35840
Cyan Blue = 32896
Sea Blue = 8388
Dark Purple = 3876477
Not Working:
Yellow = 256256256
Pale Blue = 255255255
Purple = 128128128
White = 256128128
Red = 128256256
Pink = 128256128
Hey there guys did you disabled the default LEDs from settings I think that may be the problem for light flow app not working
Sent from my Lenovo P2 using Tapatalk
abhayruparel said:
Hey there guys did you disabled the default LEDs from settings I think that may be the problem for light flow app not working
Sent from my Lenovo P2 using Tapatalk
Click to expand...
Click to collapse
Yup ..disabled it ..
Works !!!
Disabling only the charging and notification light didnt help. Disabled Ambient Display as well and the trick worked. Custom LED Finally Working. Ive used the Brightness levels mentioned below
Pale Blue:6316128
Crabapple Red :11796512
Orange: 12607488
Green: 35840
Cyan Blue: 32896
Sea Blue: 8388
Bright red: 13631488
Dark Purple : 3876477
Working on AEX 5 Oreo ..
That's great news guys.
Ambient Display is where?
Milan-XDA said:
Here's an updated and simplified thread on installation and configuration for LED.
Video Tutorial
• Disable ROM LED Notifications. Go to Settings > Notifications. Tap on the cog on the top right corner and go to
-Battery Charging Light > Disable
-Notifications Light > Disable
• Install Light Flow Lite.
https://play.google.com/store/apps/details?id=com.rageconsulting.android.lightflowlite&hl=fr
• Go to Settings > Device & Root > activate "Direct Mode" & "Root Mode".
• Again go to Settings > LED Control > scroll down and activate "RGB Control".
• Now go to Notification Settings and choose the app you wish to add LED to, open menu (3 dots menu) and go to settings.
• Once there swipe left 2 times to get to "Light".
• Make sure that the first box "Enable Light" is on.
• Scroll down until you see RGB LED & RGB Brightness boxes respectively.
• In RGB LED choose "solid" or "flash" whichever you prefer.
• In RGB Brightness set the color value (table below).
• Test it by pressing "TEST" button on top right corner.
RGB Colors Lenovo P2:
Yellow = 256256256
Pale Blue = 255255255
Marine Blue = 255
Green = 255255
Purple = 128128128
White = 256128128
Red = 128256256
Pink = 128256128
Huge shout out to @xewonder for being the first to make a tutorial. This wouldn't be possible without you.
Original thread:
https://forum.xda-developers.com/lenovo-p2/themes/lenovo-p2-rooted-custom-led-t3589859/
Click to expand...
Click to collapse
Appreciated ?
clxer said:
Ambient Display is where?
Click to expand...
Click to collapse
Not functional. But it's in "Display" menu in settings.
CO.Wildfire.OL said:
It works on AEX! Thanks for the fix @Milan-XDA
I did some more changes (underlined) and works 100% by using Light Flow Legacy :Led Control!
• Disable Battery Charging Light + Notifications Light from the settings!
• Install Light Flow Legacy :Led Control.
https://play.google.com/store/apps/details?id=com.rageconsulting.android.lightflowlegacy&hl=en
• Go to Settings > Device & Root > activate "Direct Mode" & "Root Mode".
> Again go to Settings > LED Control > scroll down and activate "RGB Control" + Activate "wled control"
• Now go to Notification Settings and choose the app you wish to add LED to, open menu (3 dots menu) and go to settings.
• Once there swipe left 2 times to get to "Light".
• Make sure that the first box "Enable Light" is on.
• Scroll down until you see RGB LED & RGB Brightness boxes respectively.
> In RGB LED choose Flash - Hardware controlled.
• In RGB Brightness set the color value (table below).
• Test it by pressing "TEST" button on top right corner.
Working LED:
Marine Blue = 255
Green = 255255
Bright red = 13631488
Pale Blue = 6316128
Crabapple Red (pink) = 11796512
Orange = 12607488
Green = 35840
Cyan Blue = 32896
Sea Blue = 8388
Dark Purple = 3876477
Not Working:
Yellow = 256256256
Pale Blue = 255255255
Purple = 128128128
White = 256128128
Red = 128256256
Pink = 128256128
Click to expand...
Click to collapse
Thx for the update. It seems that it's a miss and hit situation when it comes to LED codes, but hey it could be worse. You could be using an iPhone
How to enable blinking !!?
I keep having Dark Theme switching off when I connect to Android Auto in My 2020 Kia Soul. It happens about 50% of the time. I notice when it brings up Google Maps and it is in Light Theme. Is anyone else seeing this issue? Or have suggestions on how to correct this?
Stock, unlocked from Google Store & running on T-Mobile
Dark theme is heavily tied to the messages app, and when Android auto accesses messages it overrides the system theme with the current Android auto theme. There's no know did as I'm aware of, besides using a substrantum theme.
Sent from my Pixel 4 XL using Tapatalk
Try override force dark on developer options
This is nothing new. Every time I connect to android auto, dark theme is turned off.... It did this on all my pixels
Enable developer options in android auto, and then select it to be always dark.
There is also a setting to make it respect the phone, instead of the car, should you wish to do it that way,
uicnren said:
Enable developer options in android auto, and then select it to be always dark.
There is also a setting to make it respect the phone, instead of the car, should you wish to do it that way,
Click to expand...
Click to collapse
What he's saying is the theme on the phone changes from dark to light when Android auto is connected. He's not talking about the display on the infotainment system. I just started using an Android 10 rom on my 5t, and today I experienced the same thing he's talking about. Not really a big deal as I don't use my phone while I'm driving. The display on the vehicle will coincide with the panel dimmer switch on the vehicle. Keep it maxed out it will never go into night mode, back it down 1 click and the Android auto display will automatically toggle between white and dark background as necessary
srimay said:
What he's saying is the theme on the phone changes from dark to light when Android auto is connected. He's not talking about the display on the infotainment system. I just started using an Android 10 rom on my 5t, and today I experienced the same thing he's talking about. Not really a big deal as I don't use my phone while I'm driving. The display on the vehicle will coincide with the panel dimmer switch on the vehicle. Keep it maxed out it will never go into night mode, back it down 1 click and the Android auto display will automatically toggle between white and dark background as necessary
Click to expand...
Click to collapse
That's what me and the previous poster are talking about....
srimay said:
What he's saying is the theme on the phone changes from dark to light when Android auto is connected. He's not talking about the display on the infotainment system. I just started using an Android 10 rom on my 5t, and today I experienced the same thing he's talking about. Not really a big deal as I don't use my phone while I'm driving. The display on the vehicle will coincide with the panel dimmer switch on the vehicle. Keep it maxed out it will never go into night mode, back it down 1 click and the Android auto display will automatically toggle between white and dark background as necessary
Click to expand...
Click to collapse
I know exactly what he is talking about, and if they force Android Auto to dark mode, the phone will stay in dark mode when connected to the vehicle.
As it is now, Android Auto is what controls the light/dark mode on the phone. If you override it on Android Auto developer settings, the phone will respect it how he wants.
You can also alternatively set it so that as opposed to the vehicle controlling it, the phone will determine it instead.
uicnren said:
Enable developer options in android auto, and then select it to be always dark.
There is also a setting to make it respect the phone, instead of the car, should you wish to do it that way,
Click to expand...
Click to collapse
Yes, I could always tell when Android Auto would flip the Dark Theme off because Google Maps on the car display would flip to light mode. Once turning on developer mode in Android Auto and forcing the dark option, I have not had one instance of rebellion.
Thank you all for the troubleshooting and conversating!!
Hi.
When will Xiaomi fix Dark mode for Mi 9? I am on latest V12.0.3.0.QFAEUXM and dark mode is still not fixed! They are not fixing bugs anymore with recent updates.
Its annoying because in dark mode almost every app displays colours weird. Its half in dark mode.
In most apps status bar icon, text stays black and is hard to read.
Its really annoying and cant use dark mode because of this.
In every aosp ROM its ok and dont know what is reason that its not working in MIUI.
ASUS has officially released Android 13. Maybe it's good for the owners to share the experience.
This is what I read from the ASUS' support website:
ZenFone 8/8Z (ZS590KS) Android 13 software Image：WW-33.0210.0210.210 for WW/EU/RU/IN/TW SKUs
Version WW-33.0210.0210.210 3.2 GB 2023/01/13
Improved Item:
#Updated from previous Android 13 version:
1. Updated Android security patch to 2023-01-05
#Updated from Android 12:
1. Please back up your data before upgrading to Android 13. If you want to downgrade your device’s software version to Android 12 by official software package, it will erase all data from your device’s internal storage.
2. Upgraded system to Android 13
3. Revamped Mobile Manager, Contacts, Phone, Emergency Dialer, File Manager, Calculator, Clock, Gallery, Weather, Sound recorder, Settings, Data Transfer, Local backup, and so on.
4. Adjusted Quick Settings panel, notification tray, and volume panel to Android 13 design
5. Added the notification permission feature. You can adjust the permission of each apps in the Apps & notifications Settings.
6. System clipboard added "Auto delete" and editor features
7. Added the QR code scanner option for the lock screen shortcut feature, and the Control from locked device feature in the Security & lock screen setting
8. According to Digital Wellbeing setting, system color scheme can be set to automatically switched by the bedtime option
9. Adjusted the Vibration & haptic strength setting, Display and font size setting, and the width/length of navigation white bar when choosing gesture navigation
10. Changed to the Blocked numbers setting in Phone to stock behavior. You will not receive calls or texts from blocked numbers.
11. Removed the Call duration setting
12. Replaced original Style settings to new Wallpaper & style settings - Remove shape option, support Themed icons, and the system color is reset to blue.
13. Added link quick share feature in ASUS Launcher
14. Added Asus customization preferences setting. Allows applying the collection of commonly used customization settings with one click.
15. Removed the ‘Calm’ and ‘Elegant’ options in the Power button menu style setting.
16. Adjusted the design of the dialpad and contacts details page in the Phone app to display information more clearly.
17. Some 3rd party apps are not compatible with Android 13 yet
18. Upgrade system modes to the latest version, including "High performance", "Dynamic", "Durable" and "Ultra durable." Game Genie is also upgraded to the latest version, to allow quick switching of system modes in games.
Im on beta at Version WW-33.0210.0210.180 and if they don't broke anythink i can recommend upgrade to A13. It works much better
Good to hear. Just want do double-check, the upgrade won't erase anything, right? I understand it's always recommended to perform a backup first.
The upgrade won't erase anything, don't worry
Yea, A13 work perflecty
Confirmed working on the EU variant.
Of this update, what I like most is the possibility to shrink the enormous quick tiles to smaller icons. But the first time you boot Android 13 it's hard to tell the difference from the previous version.
I also updated to this firmware. It's great. Much smoother and less bugs (so far). Also, the small quick setting tiles are back!
Does it have the edge tool / sidebar which we see in Zenfone 9?
viv_jen said:
Does it have the edge tool / sidebar which we see in Zenfone 9?
Click to expand...
Click to collapse
Yes it does
Is the call recording available after upgrade?
Yes
bohrek said:
Is the call recording available after upgrade?
Click to expand...
Click to collapse
skothiya said:
Yes
Click to expand...
Click to collapse
Is it activated differently? The REC button wasn't showing on my phone app
Xt1d36 said:
Is it activated differently? The REC button wasn't showing on my phone a
Click to expand...
Click to collapse
No, it REC button shows the same as on A12.
No need to activate it differently.
Thanks. I had to downgrade because it doesn't show for me. I tried googling it, but Google has kinda sucked for about two years now. Are there any troubleshooting guides for this?
Just received OTA update to version TKQ1.220807.001.33.0210.0210.296
Update information
1.Updated Android security patch to 2023-05-01
2.Optimized System Stability
3.Fixed issue where certain apps would not display correctly when using 'Hide gesture bar' option