This intends to be a one stop shop for everything E4GL, including but not limited to the latest tips and tricks from the forums, battery tips, the best Android apps, ROM Reviews, and more. Big thanks to my bud Biofall who much of the batter tips are sourced from.
If you've got anything that you think should be added, PM me with the subject "E4GL Thread Add" and I'll look at it as soon as I can.
◄●Best Android Apps●►
These are some of my favorite Android apps. More to come. Make a suggestion and I'll review it!
◄●Tips and Tricks●►
[HOW TO]Sanding Top Cover to Matte Black - DIY Instructions - Not to fond of the glossy cover on the back of your EVO? Make it matte!
Screenshots - To take a screenshot, Press Power Button [HOLD] + Press Home Button, then let go of both. Upon pressing the home button, the screen will flash white.
◄●FAQs●►
What is S-OFF?
Read this: S-OFF explained - by a Developer
◄●Troubleshooting●►
My device won't turn on - Check out these tips from Sprint.
◄●EVO 4G LTE Extras●►
EVO 4G LTE Reviews - by Legendary20
◄●EVO 4G LTE Battery Tips●►
◄●All Users●►
Turn off all radios when not in use (gps, Bluetooth, wifi, data, 4g). Use a widget (default or app like Switchpro) to quickly turn them on and off. The radios draw power even if not in use. Be sure to use WiFi over 3G when you can.
Stop using live wallpapers - I love them, but they are really only good for showing off due to their battery drain.
Set your screen timeout to something that fits you - This will prevent your phone from staying on when you don’t manually turn off the screen (which you should).
Everyone has that issue where the first ten percent go the fastest.
This is due to two things. One is that these types of batteries stop charging once they get to 100% to prevent damage, and begin charging again at 90%. This means that you could potentially unplug your seemingly fully charged phone at 90% actual charge. The second is below
Use the trick described in this thread, it works.
My idea behind how often you should do it is once a month, if you flash a new ROM, or if you stop noticing the benefits.
This is the calibration technique recommended by HTC themselves. Check it out!
Make sure your phone sleeps - I'm sure you have all heard around that your phone isn't "sleeping".
This is referring to the phone's "awake" time, hence the name. When you go to menu>settings>about phone>battery, you can compare the two numbers, "up time" vs. "awake time." Generally, up time refers to the amount of time since the last reboot. The "awake time" is how long the screen has been active. The problem is, a lot of the time, due to the endless possibilities of inconsistencies between apps/ROMs/kernels/phones, the phone will not go to "sleep", drawing power proportionate to the screen being in use when it reality the phone is sitting idle.
If you compare these numbers, and they are the same, or if you note the difference, turn off the screen for a minute, then re-check and they are the same, then your phone is not sleeping.
One solution is to reboot.
Usually, SystemPanel will show an app that has gone "rouge" and is keeping your phone awake.
Uninstall applications/reinstalling them slowly, checking after every install to see what is causing it is one tedious but surefire solution.
Lastly, follow these steps that I have discovered almost always work.
Reboot phone.
Instantly upon reboot, as soon as you gain control, open up some type of monitor/taskkiller
"kill all" tasks on startup; about 5 times in quick succession should do the trick.
Turn off the screen and leave it for about five minutes.
Check the up time v. awake time and see if they are the same.
If they are, repeat steps 1-5. If they are different, you are good.
Use Juice Defender - Basically it controls your data for you to maximize life. Learn more from my review of Juice Defender.
Task killers used to be the shiz, but no longer.
Here is the ultimate, in depth, graphically assisted, explanation by the famous Fresh ROM's chef, Flipz. In short, they aren't needed (and can do more harm than good).
A good alternative is the application SystemPanel Pro. It has a free version, but I highly reccomend purchasing the paid app. It basically monitors everything going on with your phone's usage both in real time an in terms of usage history. If your battery is draining fast, it tells you what app was doing it, how much it was doing it, and allows you to stop it.
◄●Rooted Users●►
Try out custom kernels - In the Android Development section of the forums, you can see all of the different kernels being developed. These allow for all kinds of modifications like underclocking the CPU and undervolting, both of which save battery. Here is a great guide to custom kernel's by mroneeyedboh.
Use SetCPU in compliance with whatever your custom kernel allows.
This site will explain the basics of SetCPU: http://www.pokedev.com/setcpu/
-Profiles from SetCPU should usually involve these for battery life optimization:
-Screen off at the minimum clock speed for both, with the max raised on level if sluggishness is apparent
-A temperature greater than “X”
-General power related profiles that lower cpu speed at lower battery levels
◄●Notes●►
Some apps or processes begin to run at startup and keep the phone awake. These apps are not detected by things like spare parts or system panel, unless sometimes represented in the "system" process, in which case its usage will be unusually high.
This shouldn't take more than three repeats, and if it does, you need to factory reset, and slowly add apps back to see what's causing the problem.
When it comes to actually "calibrating" one's battery, there are a couple of methods floating around. The method I first learned is to charge the phone all the way, boot into recovery immediately, and "wipe battery stats". Then reboot quickly, and run your phone all the way to death without charging it, then charge it all the way without interrupting it, and you should be good to go. Do this when changing ROMs/kernels for best results.
Big thanks to Biofall for the battery tips that you see her. Thanks dude.
I'll keep this updated as often as possible. Open to all suggestions, just send me a PM.
Click to expand...
Click to collapse
the enable/disable data always isn't really an option on ICS roms, if it is, it's def not in the same place
ticklemepinks said:
the enable/disable data always isn't really an option on ICS roms, if it is, it's def not in the same place
Click to expand...
Click to collapse
Right you are. I'll update that, thanks.
I'd suggest adding v6 supercharger but that isn't as easy as somethings...
Mostly due to it changing ram settings for apps n making.it kill them in x time or at x amount
Sent from my PG86100 using xda premium
1. Battery calibration for first runtime should just be using it until the phone shuts off, then go to bootloader until it shuts off. Then do a full charge to 4.2v.
I would HIGHLY suggest putting a button combination map.
With out the removable battery you know a ton of people are gonna flip out
without knowing them
Speaking of button combinations, there's an interesting tidbit here http://insidesprintnow.wordpress.com/2012/05/10/htc-evo-4g-lte-power-on-troubleshooting-steps/
Gordon Ramsay said:
Speaking of button combinations, there's an interesting tidbit here http://insidesprintnow.wordpress.com/2012/05/10/htc-evo-4g-lte-power-on-troubleshooting-steps/
Click to expand...
Click to collapse
I guess they allow 20 seconds for user error. Thts great though we dont have to worry about all tht. Smart move on their side
Hunt3r.j2 said:
1. Battery calibration for first runtime should just be using it until the phone shuts off, then go to bootloader until it shuts off. Then do a full charge to 4.2v.
Click to expand...
Click to collapse
Occasional recalibration is good just so you have accurate percentages.
coffeehandle said:
I would HIGHLY suggest putting a button combination map.
With out the removable battery you know a ton of people are gonna flip out
without knowing them
Click to expand...
Click to collapse
Good idea. Anybody got a list of them?
Gordon Ramsay said:
Speaking of button combinations, there's an interesting tidbit here http://insidesprintnow.wordpress.com/2012/05/10/htc-evo-4g-lte-power-on-troubleshooting-steps/
Click to expand...
Click to collapse
Oh nice. I'll include that. Thanks man.
Added in Legendary20's reviews thread.
Now that most of us have gotten our phones, be sure to post up your tips and tricks to add to the OP.
Screen shots can be taken with power+vol down
Check Me Out On The Google Play Store!!!
Sent From My Half Dead HTC Evo 3D, On The Now Network From Virgin Mobile?
It says Bluetooth 4 which if that's the case wouldn't make a difference if its on or off. Also there isn't a practical way to turn off 4g and doesn't make much of a difference. Incase you wanted to add notes to the battery part.
Sent from my EVO using xda premium
Screen photos can also be taken while holding down the power button and taping the home key. The screen will blink then you get a popup screen telling you image has been saved to your image file.
Sent from my mighty EVO 4G LTE
WUESTSIDER X!
I hear 3g and voice works simultaneously cuz of the chipset... awesome
Sent from my Galaxy Nexus
Yes, you can talk and internet browse (3G) at the sametime. I confirmed it with my EVOLTE.
Sent from my mighty EVO 4G LTE
WUESTSIDER X!
Added link to regaw_leinad's post about S-OFF
1) on the Gmail app when trying to copy text you used to be able to just click on the highlighted text to copy it to clipboard, now you have to go down to the bottom left and click on the icon to do it. This is only on the Gmail app.
2) The menu button will be sorely missed. Now the menu for each app appears, depending on the app, on a different part of the screen, as opposed to having it always on the same spot.
The "Recent Apps" button is UTTERLY USELESS! With the original Evo, you used to be able to press and hold the home button and see the most recent 8 apps without having to scroll at all!! WHAT WERE THEY THINKING?? (WERE THEY THINKING?!?!)
3) The text app, and for that matter Handcent and GoSMS DO NOT show the count for the unread messages, neither on the icon, nor on the notification bar, UNLESS you actually scroll down the notifications, then you can see how many unread messages you have.
4) Gmail app used to be awesome with the original Evo. Not only did it show the total unread messages you had but also, if you marked a message as unread (even a very old message), whether you did it from the phone or even from the computer, you would get a notification as if you just got a new message! Where's that?!?!
5) Sync seems to be having its own issues as well. On the regular email app, if I set it up to sync email every 5 minutes, it takes rather about 10-15 mins for the emails to come in. Original Evo was prompt at that...
6) on the regular email app in order to be able to go to the next or previous email, one has to first click on menu and only then do you have the "next" or "previous" option, unlike on the original Evo.
7) When already on max volume and want to make sure you still are with the volume rocker, you would hear a sound with the old Evo, now you got nothing are have to actually LOOK at the screen to make sure you got it to the max.
8 ) No option to play YouTube videos out of the YouTube app when clicking on a YouTube video on the browser.
That was a given with the original Evo. Annoying as hell on the LTE.
9) You MUST use both hands when holding the phone vertically if you want to have access to the whole screen (if you're laying down or sitting back on a sofa, for example), otherwise you will be unwillingly hitting the volume rocker or needing a chiropractor for your thumb. An issue which could be avoided with a gel cover, but could have been foreseen by HTC when producing such a smooth non-grippy back to the phone.
10) Gmail and Tasks are incompatible?! I mean, what's the point??
11) The regular email app can only be accessed a limited amount of times per 15 minutes? I already got quite a few of those error messages...
12) You used to be able to choose the input method and switch keyboards by long-pressing on any field. Now you have to exit whatever application you're on and go to settings, keyboard etc. to do it.
This isn't a cellphone war between the 4G and the LTE, obviously the LTE has lots of stuff over the original Evo. I'm not here to bash the LTE, on the contrary I would love to find solutions to all (or most) of those issues.
For the time being if I have to sum it up:
I love the speed and I LOVE the battery life but, in terms of practicality, I would stick with the original Evo.
P.S. I would rather not root my phone, and would like those problems to go away, help!
Gimme your thoughts!
txtmax4 said:
1) on the Gmail app when trying to copy text you used to be able to just click on the highlighted text to copy it to clipboard, now you have to go down to the bottom left and click on the icon to do it. This is only on the Gmail app.
2) The menu button will be sorely missed. Now the menu for each app appears, depending on the app, on a different part of the screen, as opposed to having it always on the same spot.
The "Recent Apps" button is UTTERLY USELESS! With the original Evo, you used to be able to press and hold the home button and see the most recent 8 apps without having to scroll at all!! WHAT WERE THEY THINKING?? (WERE THEY THINKING?!?!)
3) The text app, and for that matter Handcent and GoSMS DO NOT show the count for the unread messages, neither on the icon, nor on the notification bar, UNLESS you actually scroll down the notifications, then you can see how many unread messages you have.
4) Gmail app used to be awesome with the original Evo. Not only did it show the total unread messages you had but also, if you marked a message as unread (even a very old message), whether you did it from the phone or even from the computer, you would get a notification as if you just got a new message! Where's that?!?!
5) Sync seems to be having its own issues as well. On the regular email app, if I set it up to sync email every 5 minutes, it takes rather about 10-15 mins for the emails to come in. Original Evo was prompt at that...
6) on the regular email app in order to be able to go to the next or previous email, one has to first click on menu and only then do you have the "next" or "previous" option, unlike on the original Evo.
7) When already on max volume and want to make sure you still are with the volume rocker, you would hear a sound with the old Evo, now you got nothing are have to actually LOOK at the screen to make sure you got it to the max.
8 ) No option to play YouTube videos out of the YouTube app when clicking on a YouTube video on the browser.
That was a given with the original Evo. Annoying as hell on the LTE.
9) You MUST use both hands when holding the phone vertically if you want to have access to the whole screen (if you're laying down or sitting back on a sofa, for example), otherwise you will be unwillingly hitting the volume rocker or needing a chiropractor for your thumb. An issue which could be avoided with a gel cover, but could have been foreseen by HTC when producing such a smooth non-grippy back to the phone.
10) Gmail and Tasks are incompatible?! I mean, what's the point??
11) The regular email app can only be accessed a limited amount of times per 15 minutes? I already got quite a few of those error messages...
12) You used to be able to choose the input method and switch keyboards by long-pressing on any field. Now you have to exit whatever application you're on and go to settings, keyboard etc. to do it.
This isn't a cellphone war between the 4G and the LTE, obviously the LTE has lots of stuff over the original Evo. I'm not here to bash the LTE, on the contrary I would love to find solutions to all (or most) of those issues.
For the time being if I have to sum it up:
I love the speed and I LOVE the battery life but, in terms of practicality, I would stick with the original Evo.
P.S. I would rather not root my phone, and would like those problems to go away, help!
Gimme your thoughts!
Click to expand...
Click to collapse
Some on the stuff like not being able to open links in the YouTube app is an apple problem, choosing diferent keyboards was something the google did on ICS(annoyed as hell too), some issues is cause of ICS and some other is sense but I could live with them
Sent from my htc_jewel using Tapatalk 2
1 note about that long rant, with the keyboard a small icon appears in your taskbar that you can pull down to change input method without having to exit the app and go to settings
Sent from my EVO using XDA
Hello.
So I've been tampering with the android SDK and made an app for practice. However, while trying to stick to my basic level goals, it seemed like I was going against the grain of how stuff seemed to work. I'm gonna read up on theory now, but it'd be a real help if you could tell me if there were any glaring dumb/broken/bad things there.
Anyway, the general idea was to have a reverse-stopwatch that I could populate with types of laps with custom durations. So I'd have, for example, WALK 10sec, RUN 30sec JOG 15sec *10 times. I wanted the app to vibrate every time one of these laps ended (no matter what, even in screen lock) but I also wanted those laps and their duration-countdowns to be dynamically shown in a ListView inside the main Activity.
In order to do that, I populated an Object that extended Application with my dataset, plugged it into an Adapter to update the ListView with, then when I had a populated list, I'd invoke an IntentService which would make a deep copy of the data and do countdowns inside logic loops. That IntentService also periodically sent messages to a BroadcastReceiver, who would update durations and remove expired laps on the Original List (linked to the Adapter) and handle vibrations. The intentService could be aborted prematurely , I haven't been able to think of a way to pause it.
Well, it works if you don't ever let it re-orient screens and while phonecalls don't break it, some of the listview data appearance was corrupt after one (the timers were fine tho which is weird).
Hi,
I'm just letting everyone know that I have just pushed an update to my automation app MacroDroid http://forum.xda-developers.com/showthread.php?t=1694335 to add Android Wear support.
You can read about the functionality on my blog post here: http://macro-droid.blogspot.co.uk/2014/08/introducing-macrodroid-wear.html
This is a first release, so I strongly welcome all feedback and comments!
Cheers,
Jamie
Very impressive app ?, seriously quality app.
I need more time to test out all the different stuff in your app but so far everything works great whit my lg watch .
This is using 60mb of memory for the macrodroid process alone. Seems very high.
This is on a Moto G. Compared to Tasker which is running at the same time and only uses 12mb.
I have deleted all macrodroid profiles so it shouldn't have had anything running, but the memory use was still high.
Cossack101 said:
This is using 60mb of memory for the macrodroid process alone. Seems very high.
This is on a Moto G. Compared to Tasker which is running at the same time and only uses 12mb.
I have deleted all macrodroid profiles so it shouldn't have had anything running, but the memory use was still high.
Click to expand...
Click to collapse
You're right that does sound very high, I've got a bunch of macros configured and I'm at 19MB. Most likely you've hit a memory leak in the UI and the UI pages are still hanging around in memory. It can be hard to catch all cases as there are many many UI paths, but I'll certainly do some more memory profiling to see if I can spot anything naughty hanging around. If you kill the MacroDroid process and restart does the memory return to something sane for you?
Cheers,
Jamie
I killed the app and wiped the macros. Started again with only 1 simple low battery warning macro. It stayed at 15mb all day.
I just created a new location macro and it jumped to 38mb and stayed there.
I switched macrodroid off and restarted and it is now back to 17mb.
Cossack101 said:
I killed the app and wiped the macros. Started again with only 1 simple low battery warning macro. It stayed at 15mb all day.
I just created a new location macro and it jumped to 38mb and stayed there.
I switched macrodroid off and restarted and it is now back to 17mb.
Click to expand...
Click to collapse
Great thanks for the info. I've just had to move to Google Maps V2 and changed a load of UI, so I'm guessing I've got a little bug in there where I'm not releasing something. Hopefully I can get this squashed for the next update.
Cheers,
Jamie
I am trying to automate the screen intensity.
The worst thing about my Gear Live is battery live, if I am inside love to find a way to always have the screen minimum and the best I could do is have a manual macro to change the screen intensity.
I wonder if I can design a macro that every time the watch gets a notification the screen goes to 5, when it dims it goes back to 1.
Why not set the brightness to low when connected to WiFi and high when disconnected.
It should mean you always have a dim watch when indoors
AstroDigital said:
I am trying to automate the screen intensity.
The worst thing about my Gear Live is battery live, if I am inside love to find a way to always have the screen minimum and the best I could do is have a manual macro to change the screen intensity.
I wonder if I can design a macro that every time the watch gets a notification the screen goes to 5, when it dims it goes back to 1.
Click to expand...
Click to collapse
You could do something like on every incoming notification (using the incoming notification trigger), you set the brightness high and have a sleep before next (e.g 30 seconds) and set the brightness low again. Not perfect but might be of some use.
What I really wanted to do was find a way so that I could configure the Always on screen setting via the action, but after digging down into the code I'm pretty certain this would only be possible on a rooted Android Wear device and I don't really want to go adding 'root only' features for Wear just yet. Hopefully Google will open up this API at some point because as you point out battery life is critical on these devices.
Cossack101 said:
Why not set the brightness to low when connected to WiFi and high when disconnected.
It should mean you always have a dim watch when indoors
Click to expand...
Click to collapse
I do not use WiFi on my cell phone, just LTE data at least 95% of the time.
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
UndeadCretin said:
You could do something like on every incoming notification (using the incoming notification trigger), you set the brightness high and have a sleep before next (e.g 30 seconds) and set the brightness low again. Not perfect but might be of some use.
What I really wanted to do was find a way so that I could configure the Always on screen setting via the action, but after digging down into the code I'm pretty certain this would only be possible on a rooted Android Wear device and I don't really want to go adding 'root only' features for Wear just yet. Hopefully Google will open up this API at some point because as you point out battery life is critical on these devices.
Click to expand...
Click to collapse
If I set the app to listen for notifications it looks like it will disable much more than I would like to be disabled.
Manage Accessibliity, MacroDroid
-air gesture, air view interaction control, assistant menu, multi window, direct pen input, palm motion, one-handed operation will all be turned off....
I always lost "Jess" my customer voice synthesizer
Some of these I will miss on my Note 3 but I am trying it,
Toggle on Notification
Android Wear set the brightness to 6
Sleep before next action 20 seconds
Android Wear set the brightness to 1
If it works right notifications will crank the display for 20 seconds and then dim the display (may cut it back to 10 or 5 seconds)
You know I like your app, tried the other macro app .... (can not remember its name)
Found it too complicated..... Thanks for the tip.
AstroDigital said:
I do not use WiFi on my cell phone, just LTE data at least 95% of the time.
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
If I set the app to listen for notifications it looks like it will disable much more than I would like to be disabled.
Manage Accessibliity, MacroDroid
-air gesture, air view interaction control, assistant menu, multi window, direct pen input, palm motion, one-handed operation will all be turned off....
I always lost "Jess" my customer voice synthesizer
Some of these I will miss on my Note 3 but I am trying it,
Toggle on Notification
Android Wear set the brightness to 6
Sleep before next action 20 seconds
Android Wear set the brightness to 1
If it works right notifications will crank the display for 20 seconds and then dim the display (may cut it back to 10 or 5 seconds)
You know I like your app, tried the other macro app .... (can not remember its name)
Found it too complicated..... Thanks for the tip.
Click to expand...
Click to collapse
I've no idea why these should be turned off by enabling MacroDroids accessibility options, but I don't have any Samsung devices so I'm afraid I can't really look into it at the moment.
UndeadCretin said:
I've no idea why these should be turned off by enabling MacroDroids accessibility options, but I don't have any Samsung devices so I'm afraid I can't really look into it at the moment.
Click to expand...
Click to collapse
If the macro works may not care much about the disabled stuff.
May want to put constraint in, 5am do not need the watch display cranked.
OK so I got my Z4 tablet three days ago. Fantastic construction, fantastic specs on paper.
I had a Z tablet up until last weekend that I sold for a good price and got this as a much needed replacement.
Both are LTE versions.
Anyway, here are some things I've noticed and I would like to have your comments on.
1) The "antitheft" system for the first two days seemed to be a PITA. As my device is set for three users (me, my wife, my son), it kept popping for the others that it locked and needed MY credentials to unlock. I did unlock it at least five times for each, which means I can't really be... far from the device and let them use it. That I use two step authentication, makes things even harder. Once my "authenticator" phone was out of power and I had to wait several minutes to unlock the tablet. Yesterday I updated to latest firmware and I haven't noticed the issue since. But it's just one day, it may come back. Once (before updating firmware) I tried to disable My Xperia (although I love the find my device feature) so they could work, but it kept me "waiting". In the end I pressed back and it didn't get disabled. Any similar experiences with the theft protection?
2) Backlight (set in auto) seems to be too dark some times. I clicked on the intensity bar, set it brighter while STILL in auto (like it is now set to have a brighter "base value"?). Does this sound normal?
3) This is not a Z4 issue, I also had this in Z. It's probably a lollipop thing or I don't understand something properly. Clicking the volume buttons I can set it to "no" sound from home screen. Or so I think. Because even if I set it to "off", apps STILL have sound and I have to RE-adjust the volume to off from within the app (without the "priority buttons" under the volume bar)... Am I the only one to find this stupid?
4) Anybody notices some lag or ESPECIALLY stuck web browser, when other profiles (users) have run apps? If I reset the device and not visit the other profiles, the device is more snappy. If some other user goes in, even quiting every app they run, the device seems to get slower when back in "owner" user. Still fast but not as "snappy". Anybody noticed the same?
5) Any idea when we get Android M? Will we get 5.1 before that? I mean official firmware. Anybody?
6) Is there a way to go to test menu? The tablet Z method doesn't seem to work.
7) Serious. No restricted profiles. Why? Sony support replied that lollipop has this disabled only on 3G/LTE devices (that makes no sense), yet my Z was also LTE and both are on lollipop 5.0.2 and it DID have restricted profiles. What's up with that?
Thank you for your time people, have fun.
...wow
2) Yes.. brightness is usually set a little low at first for battery purposes.
3) There are different volumes for different things. Using the volume rocker on the home screen and putting it all the way down will only adjust ringer/notification volume. In-app sounds will use the media volume which you will need to adjust while media sounds are playing or you can adjust it in your sound settings. Not stupid imo, just gives more flexibility.
5) It'll come when it comes.. nobody knows except google and sony. I'd like to hope we'd get 5.1 before 6.
(pending something on the other questions above)
2) So the set value, when brightness is in "auto" is like a base value?
3) Well I find it stupid. Why: Because when I am in home screen I used to be able to manage the universal audio settings of the device. Turning device to mute, would turn it to mute. As simple as that. Also clicking a simple icon next to volume bar, you could separately adjust notification and ringer and stuff like that. Now? You THINK you set your device to mute, but you have only set the notifications. You sleep in a silent house (next to the wife or something), start a game, it YELLS with the last volume settings, ignoring that you set the device to mute in home screen and you have to "run" and re-adjust the volume to zero, usually with some delay (in the meantime waking everybody) since the device won't let you adjust anything while loading the game. No, I call this stupid.
5) Well if it won't delay 6, I don't mind for 5.1. But I want 6 the soonest possible.
..
First thing first: thanks a lot for the /sys file to change ambient brightness! Gives me ideas of things to play with, ie the ambient brightness being different from the awake brightness is among the top of what I find the most baffling with Android Wear (to me, the point of ambient is to update less frequently, and to move the displayed face a little to avoid burn in: I don't need every last drop of battery; 16-20h is really enough; also, if it's not bright enough by day, it's also not dim enough by night...).
Otherwise, with Tasker and AutoWear, maybe using the screen off state, and setting ambient anew when you exit that state would work? Obviously, the system rewrites that file (it takes more than mere permissions to prevent root from doing what he wants) somewhere between when the screen goes off, and when it goes to ambient again after having been turned on, so with a little tinkering, and maybe some delays, it should hopefully be workable.
MuF123 said:
Hi there!,
I've been trying to set ambient back-light to maximum by echoing 255 to /sys/class/leds/lcd-backlight/brightness and then chmodding it to 444 for readonly, so noone will ever change it.
This kinda works, when I enter ambient mode it really is at 255 level. However trouble stars after entering theater mode - somehow this value gets changed. How can this be?
Any ideas how to debug this?
Click to expand...
Click to collapse
I wish I could answer your question better than this, but wearshell can query brightness values or file values through tasker by having it read your settings once every few minutes, or per minute, or whatever you like if course. if it found the value not what you want it'd fix that .. you could sideload a tasker apk that does the same, but this is inflexible and cumbersome compared to the wearshell option.
..