Hi guys,
I did a bit of looking around for a way to fix the problem I am having and some others may have as well. It seems like my screen brightness is turned down CONSTANTLY due to temp of the phone. Well not anymore!
***I AM NOT RESPONSIBLE FOR YOUR PHONE CATCHING ON FIRE AFTER YOU DO THIS. It has worked for me but could potentially damage your phone.***
I am assuming you need to be rooted at the least.
METHOD 1 Safest for now!
1. Download a file manager that lets you have access to the root directory IE: /
2. go to /ETC and find a file named thermaled.conf
3. open the file in a text editor.
4. Raise the values of the thresholds as shown in red
5. Reboot your phone and enjoy!
[pa_therm0]
sampling 5000
thresholds 49 52 55 59
thresholds_clr 49 52 55 59
actions cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery
action_info 1512000+255+400000000+0 1512000+237+325000000+0 1188000+215+200000000+1 1188000+202+200000000+1
METHOD 2 (not as safe as Method 1
1. Download a file manager that lets you have access to the root directory IE: /
2. go to /ETC and find a file named thermaled.conf
3. open the file in a text editor and remove the LCD references in the file and save.
4. Don't forget to remove the extra "+" symbol so you don't have two "++" together.
5. Reboot your phone and enjoy!
[pa_therm0]
sampling 5000
thresholds 35 42 44 46
thresholds_clr 34 40 43 45
actions cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery
action_info 1512000+255+400000000+0 1512000+237+325000000+0 1188000+215+200000000+1 1188000+202+200000000+1
Would a better solution be to edit the values higher, and leave the lcd references ?
adfurgerson said:
Would a better solution be to edit the values higher, and leave the lcd references ?
Click to expand...
Click to collapse
You are probably right. However I haven't the slightest idea on how much to change the values. Someone smarter than me can pick it up from here lol or at least more willing to tinker with the values. I am not a dev nor claim to be. I am just trying to make our experience with this phone a bit better. I haven't had any adverse effects by doing this YET.
Actually I think I may have figured out how to just change values! Raise the threshold values in the "pa therm 0" column from 35 42 44 46. Add maybe 2-3 on top of those numbers? I am not sure but it may work?
Looks like it would be easier/safer to change the temperature thresholds (35C seems low) to be higher so that it doesnt start throttling until a higher temp. It seems that the throttle is CPU Freq, then display brightness (0-255), then GPU freq (with extra 0's) and I am not sure what that battery 0 or 1 does..
UPDATED OP!!!! Safer method!!! Send thanks if this works for you!
Think I can get this thread in the Android Development section Mods?
59C seems pretty high, especially for the battery. Might want to lower that upper limit a bit.
I get an error when trying to save the changes. Any reason for that?
SkriblZz said:
I get an error when trying to save the changes. Any reason for that?
Click to expand...
Click to collapse
Did you enable R/W for that folder? Or is it still showing RO? RO= read only; RW= read/write
Nastybutler said:
Did you enable R/W for that folder? Or is it still showing RO? RO= read only; RW= read/write
Click to expand...
Click to collapse
Ah. I've been using a file manager app, haven't seen an option for such. I assume then I need to access the file on a computer. Quite honestly, not sure how to access the root from a computer.
SkriblZz said:
Ah. I've been using a file manager app, haven't seen an option for such. I assume then I need to access the file on a computer. Quite honestly, not sure how to access the root from a computer.
Click to expand...
Click to collapse
Never mind. I edited the file via Android commander.
Well.. I have used the Method 1 but still feels like it is not working. Though it changes the brightness, but I personally think brightness adjustments were much better in galaxy devices than in Optimus G. Is there anyway to change it to those of Galaxy devices?
woopsgoops said:
Well.. I have used the Method 1 but still feels like it is not working. Though it changes the brightness, but I personally think brightness adjustments were much better in galaxy devices than in Optimus G. Is there anyway to change it to those of Galaxy devices?
Click to expand...
Click to collapse
Figuring this is an LG device with totally different sensors...no. This just allows no thermal throttling
Sent from my LG-E970 using xda app-developers app
Anyone else got this working? Especially the safer method.
Shadow on the screen by means of temperature
Thanks for the input. I live in Dominican Republic, here enough heat, now decreased enough temperature, before they burned my fingers, now gets less than before. Only thing is that I to become spots on the screen that were formed by medium to temperature, think they are deleted eventually, because it avece when hard a time without using my device feel they removed a little
I've got thermal-8960.conf and two other numbered thermal files in addition to thermal.conf
Is that normal anyone else verify? One for each core maybe?
OG e970 stock+
mystery emotionz 5.1
1.72 GHz oc/uv
Try this http://forum.xda-developers.com/showthread.php?t=2296447
Related
How fast is everyone running their STRTrk/S300/8500/3125?
Mine is 100% stable running at 252mhz all the time. It makes videos and menus a lot smoother.
252 Mhz too
I've used it at 240 a bit...but I used OMAP Clock and it resets to 180 after a few minutes.
Is there a way to make it stay permanently at a set speed?
thelostsoul said:
I've used it at 240 a bit...but I used OMAP Clock and it resets to 180 after a few minutes.
Is there a way to make it stay permanently at a set speed?
Click to expand...
Click to collapse
Well I could never get omapclockplus to work at making it stick, so I use Tornado Power Control and manually modify the speed in the registry so it goes up to 252 instead of stopping at 228.
could you please give us details on the registry keys and where to get the program. thanks in advance.
bigdooky said:
could you please give us details on the registry keys and where to get the program. thanks in advance.
Click to expand...
Click to collapse
http://www.modaco.com/lofiversion/index.php/t237427.html
Install it and then open it and set CPU speed to "Ultra Fast" and make sure it is not set to "Automatic CPU Speed". I personally disable the CPU speed indicator because I think it clutters the screen, but that is your choice. Then exit and go into whatever registry editor you use.
And they keys to change are:
HKEY_LOCAL_MACHINE\SOFTWARE\TornadoPowerControl\CPUAuto3
HKEY_LOCAL_MACHINE\SOFTWARE\TornadoPowerControl\CPUSpeed
Change them both to 252.
Exit your editor and then reopen Tornado Power Control. Don't change any of the speed settings from within or you will have to re-edit the registry. Just leave it running in the background and it will keep the speed at 252. You can independently verify with OMAPClock.
*I am not responsible if you damage your device by overclocking!*
What happens when you restart?
Hi Since you stated to leave the Tornado Power Control open, what happens when you restart the phone?
Since the information is in the registry all I have to do is open the Tornado Power Control?
Thanks
sacosta74 said:
Hi Since you stated to leave the Tornado Power Control open, what happens when you restart the phone?
Since the information is in the registry all I have to do is open the Tornado Power Control?
Thanks
Click to expand...
Click to collapse
I have it set to start up in the back ground when the device turns on, so if I restart, it automatically launches and overclocks without any intervention.
I noted that running omap clock at 252 makes yahoo go run much better. TPC with registry modifications does not. Thoughts and ideas?
thelostsoul said:
I noted that running omap clock at 252 makes yahoo go run much better. TPC with registry modifications does not. Thoughts and ideas?
Click to expand...
Click to collapse
It has more processing capacity at a higher clock rate...
Is v0.2 the latest omapclock?
I have version 0.2 from way long ago for my MPx220 - is that really the latest version of omapclock?
TIA,
Richard
Ok, I am having some problems with this on my StarTrek. For some reason, when I open up TPC, it keeps telling me that it can't map I/O and the initialization failed. Any help?
killerbeans said:
Ok, I am having some problems with this on my StarTrek. For some reason, when I open up TPC, it keeps telling me that it can't map I/O and the initialization failed. Any help?
Click to expand...
Click to collapse
A search should have found the answer to this: you must application unlock your phone before any of the overclock utils will work.
Richard
Ok, how do i app unlock the phone?
[Solved] TS FREEZE FIXED / Orientation offset calibration & G-SENSOR CALIBRATION FIX
UPDATE: (13/11) A patch has been developed that completely eliminates TS FREEZE for good.
Thanks to mdebeljuh and jdivic, I tested it and it seems to be working perfectly.
Check post 140 on page 14:
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140
UPDATE: (20/11)A new patched 8.2 kernel without logging (better for daily use) is available.
Check post 234 on page 24:
http://forum.xda-developers.com/showpost.php?p=9304396&postcount=234
-----
EDIT: If you did autocalibration and messed your g-sensor, read post 10 & 11 to see a fix for it. (before going through post 1)
EDIT 2: Freezes of sensors and touch screen seem to be related to offset values. See post 10 & 11
Post 1 is for orientation offset. Check post 10 & 11 for g-sensor and ts freeze fix.
----
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Install an app that displays sensor information along with pitch and roll. (such as SensorDebug from Android market)
Put your phone on a level surface such as the floor or a table.
Note your pitch and roll values.
Use rootexplorer or similar file manager to edit /data/misc/AK8973Prms.txt file. (open in text editor) (For ASTRO CHECK POST 70 in page 7)
You will see AOFFSET.x and AOFFSET.y at the bottom. (May be on top if you autocalibrated previously)
y affects pitch and x affects roll, there is about 4 to 1 ratio.
What you are trying to do is make pitch and roll 0 with minimum flicker.
Press and hold home button to switch between rootexplorer and sensordebug. Your changes will be reflected in realtime (with most builds). Go back and forth a few times to get perfect result. (You can press and hold home button to go back and forth) If you think changing values don't have an affect, try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting, use different sensor app and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
For example:
If pitch is 3 and roll is -1
you may start by
AOFFSET.x=4
AOFFSET.y=-12
Then adjust with 1 increments to get rid of flicker.
It is best to adjust one value at a time.
EDIT: IF YOU WANT TO CALIBRATE Z AXIS, CHECK POST 61 in page 7
Calibrated AOFFSET values for my phone are x=2 y=-9 z=12
You can use gpsstatus or bubble app (to find bubble app search the market for bz.ktk.bubble and enable "show angle" from bubble apps settings.) for visual check of orientation calibration. Because of the protruding camera lens of hd2, there can be 1 degree difference between sideways and normal orientation. (It seems you can adjust in about 0.25 degree increments by each 1 increment of AOFFSET and compansate by lowering AOFFSET=y by 2 that gives 0 degrees in both normal and sideways orientation in bubble app)
- You don't need to reboot for most builds (if there is no affect check post 11)
- You don't need to kill/restart akmd
- You don't even need to close sensor app
- Because of not perfect kernel/build support for sensors, you may see them freeze when you move the phone (TS will also freeze). With evo kernels, just wait a few seconds and it will resume. (With nexus kernels they may freeze until sleep/wakeup) Interestingly the values of AK8973Prms.txt affect shake/move freezes. I wrote about this in post 10 and 11.
IT IS A GOOD IDEA TO BACKUP COMPLETE ANDROID FOLDER BEFOREHAND just in case something goes wrong. Chefs say you shouldn't auto calibrate your g-sensor under Android because with many people it gets messed up. Also good idea to backup your /data/misc/AK8973Prms.txt
You may have trouble accessing data folder with a file manager other than rootexplorer. Your build must be rooted. (most are) It is a good idea to update your su binary inside superuser app settings TWICE. If you change permissions of /data /data/misc folders you may access them even with standart astro file manager. Try chmod 777 /data from terminal emulator.
This procedure is also possible with adb or droidexplorer. But my way of doing is practical and it is in realtime. If your build has different file name, please tell us.
This IS a development thread, please don't tell me to post in generic section or clutter.
This is manual workaround for non-working auto calibration. If auto-calibration works in the future, it may very well fix your freezes.
Values of AK8973Prms.txt file may solve touch screen/sensor freeze problems with your games. Feedbacks are always welcome. We should find out what the other values do exactly. Also check post 10 & 11
Wow, thank you. I will certainly try this when I am sober (tomorrow morning).
I appreciate your taking the time to share this.
Have a good weekend!
Thanks! worked great....
thanks! worked perfectly
haha.. funny, this is the RIGHT way to do it: (credit goes to me )
1) put your phone on the surface and then
2) Gscript to stop gsen.
3) Go to callibration tool and press callibrate..
4) activate Gsensor through Gscript.
thats it and gsensor is fully callibrated to your way. no need to mess with system files.
eeeeeee said:
haha.. funny, this is the RIGHT way to do it: (credit goes to me )
1) put your phone on the surface and then
2) Gscript to stop gsen.
3) Go to callibration tool and press callibrate..
4) activate Gsensor through Gscript.
thats it and gsensor is fully callibrated to your way. no need to mess with system files.
Click to expand...
Click to collapse
Don't you think I already knew that? I wrote this long procedure because calibration tool corrupts calibration and doesn't work with many people. With many builds, chefs write don't calibrate your sensor. You need the gsensor script to be able to stop gsensor (kill akmd) since you didn't share it, people won't be able to do it anyway.
I suggest backing up complete Android folder before attempting to auto calibrate g-sensor within Android. Forum is full of people who calibrated under android and everything is messed up.
memin1857 said:
Don't you think I already knew that? I wrote this long procedure because calibration tool corrupts calibration and doesn't work with many people. With many builds, chefs write don't calibrate your sensor. You need the gsensor script to be able to stop gsensor (kill akmd) since you didn't share it. People won't be able to it anyway.
I suggest backing up complete Android folder before attempting to auto calibrate g-sensor within Android. Forum is full of people who calibrated under android and everything is messed up.
Click to expand...
Click to collapse
gsensor calibration tool causes nothing.. in my way -> t does exactly what you do..
i know that with the evo kernel the gsensor callibration is kinda corrupted, but it still works perfectly when following my orders.
although i would suggest not doing this with gsensor on.
as long as the gsensor is off when calibrating, there is no risk to mess the gsensor up.
although when callibrating with gsensor on messes the whole thing up, you can fix it following my orders again.
although its still nice that you edited the beginning of your tutorial:
memin1857 said:
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Click to expand...
Click to collapse
eeeeeee said:
gsensor calibration tool causes nothing.. in my way -> t does exactly what you do..
i know that with the evo kernel the gsensor callibration is kinda corrupted, but it still works perfectly when following my orders.
although i would suggest not doing this with gsensor on.
as long as the gsensor is off when calibrating, there is no risk to mess the gsensor up.
although when callibrating with gsensor on messes the whole thing up, you can fix it following my orders again.
Click to expand...
Click to collapse
I have made extensive tests and found out that you are actually doing no proper calibration. You are breaking other things.
- If you disable g-sensor before you open your sensor app (calibration tool) than you get no data from the g-sensor (since you disabled it) and can't calibrate.
- Phone must be very still while you disable g-sensor or the orientation data will get frozen at wrong values. And sensor app must be open beforehand.
If you fail calibration (y axis) will get messed up badly and won't work again. It wil flicker between full up and full down and further calibration attempts will make compass constantly spin.
- Still if you could do it all, nothing changes, offset is still there and calibration is wrong after following your instructions. (Try bubble app or sensor app with real sensitive degree values and you will see)
I searched your posts and saw that you are complaining about touch freezes. Maybe if you don't do auto calibration you may get less freezes?
Also please DO share anything you know. It is not enough to just say -disable g-sensor with gscript- People don't know that script, and if you don't share they can't do it. I saw your thread, you got 0 replies in 20 days, maybe because it doesn't work.
I advise against doing autocalibration. And remember, this is not a pissing contest. We are not doing this for the credit. We should be doing this for helping community. (You should have written nicer, instead of looking like showing off how genious you are and how fool we are. We know some things too.)
My way of doing it is NOT direct calibration. It is providing offset to g-sensor data that many people can do without the risk and can be restored back easily.
Note: I have found out that calibration tool generates a file named AccPrmsF.ini in the same folder with extreme z value. Sometimes a bma_result.txt gets created again with wrong values. Its content is input to AK8973Prms.txt again with extreme z value. If you restore your original AK8973Prms.txt g-sensor starts working properly again. (see post 10 & 11)
eywallah bro
How to restore g-sensor
If you calibrated with android calibration tool and your g-sensor freaked out. Here is how to fix it:
Use rootexplorer to
Delete AccPrmsF.ini and bma_result.txt file in /data/misc (if they exist)
Edit AK8973Prms.txt in /data/misc folder with rootexplorer to these values:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=1
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=114
HDAC_SLIDER_OPEN.x=128
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=4
HOFFSET_SLIDER_OPEN.x=250
HOFFSET_SLIDER_OPEN.y=593
HOFFSET_SLIDER_OPEN.z=175
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
(These values may not solve freezes, check post 11 for different values that may fix freezes)
Some nexus based builds don't have slider open/close lines.
No need to reboot, just save and it should work instantly with most builds. (If it doesn't check post 11) If you delete AK8973Prms.txt or it may get recreated with wrong values (full zeroes) and freak out again. AOFFSET.z=xxx seems to be the culprit of calibrate tools vertical corruption. (Becomes full up or full down like digital when z=veryhigh). Only editing it to zero may solve the problem.
These values may change in time, or between builds. Those were my values, you may try to boot a new version of your android build and rip the file from it and use that instead.
If your g-sensor does not work at all after reboot you may need to restart it. Open terminal emulator and enter these commands:
su
/system/bin/akmd
Now it should be working.
Please tell if it worked for you. By comparing values and working on these values we may as well make g-sensor much better. (Accelerometer doesn't seem to be calibrated) If your build has different file name, please tell us. The instructions in post 10 may not be perfect and I am still working on this and will post if I find anything new. Of course kernel support is also required for getting less flickers, no freezes, proper poll intervall, correct i2c frequency and proper calibration.
EDIT: The values keep changing by itself. Interesting part is I am getting less shake/move freezes (or freezes in only one direction) in sensor apps or games now! I am experimenting with different values and it definitely affects how often freezes happen. I am trying to get the values of what a real calibration would do. Maybe sensor freezes happen when values are out of range. I am sure a proper calibration will get rid of these freezes but since with the current kernels we can't do proper auto calibration, maybe we can do manual one for now. Seems usual x y z accelerometer values are between 10 and -10. When freezes happen they seem to be more than 10 or less than -10. ASENSE values change the range of x y z (minimum working asense is 45 and the more you set the less range x y z has). Also ppp data seem to freeze/restart when sensor freezes happen. If freezes are eliminated even ppp data might work better! Some of the findings might be wrong, of course.
It seems you can update AK8973Prms.txt in realtime with droidexplorer and changes are reflected in realtime when you reopen, switch to the sensor app or sleep/wakeup. This makes testing easier.
It seems I have found non freezing values. Check next post. (Post 11)
Freezes are fixed now.
EVEN IF YOU ARE NOT GETTING TOUCH SCREEN / G-SENSOR FREEZES WITH USUAL USAGE OF YOUR PHONE, INSTALL SENSOR DEBUG, BUBBLE, COMPASS APP OR GAMES AND TRY IF THEY FREEZE WHEN YOU SHAKE/MOVE THE PHONE OR WALK WITH THE PHONE IN YOUR HAND. Bubble app is the most freezing app. To find it ssearch the market for bz.ktk.bubble. Enable "show angle" from bubble apps settings. Game example: Teeter
Make sure it has been at least 2 minutes since Android has booted. (Or it may fool you as it is busy when first home screen appears after boot)
Freezes have been mostly eliminated with newer builds/kernels, but they are not completely gone.
I am no longer getting any freezes in any app now. Not in compass apps, not in games, not in sensor displaying apps, not in calibration tool. I am also not getting freezes while I am walking with the phone.
I am not yet sure how this exactly happened (as I always had freezes in those apps when the phone moved) but currently my android build updates the AK8973Prms.txt file every minute by itself (doesn't change very much, but quite different from the beginning) and the current values have absolutely no freezes.
These values have no more freezes. (since they keep changing it may not last for days) Please try:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=2
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=111
HDAC_SLIDER_OPEN.x=4
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=8
HOFFSET_SLIDER_OPEN.x=-849
HOFFSET_SLIDER_OPEN.y=1179
HOFFSET_SLIDER_OPEN.z=-653
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
Seems
A low HDAC_SLIDER_OPEN.x value
A large negative HOFFSET_SLIDER_OPEN.x value
A high HOFFSET_SLIDER_OPEN.y value
A large negative HOFFSET_SLIDER_OPEN.z value
and along with some other thing I did/happened fixed my freeze problems.
Some nexus based builds don't have slider open/close lines.
Change the AOFFSET.x y and z values to your device to level it on a table. (check post 1)
I am not attaching the file itself to this post because of differences between windows and linux with text files, just to be safe. (Paragraphs get messed up)
Also using the calibration tool with the phone face down gives better results with z axis. (to be able to tap on calibrate, put your phone on the table and make it just go over the edge of the table and tap from underside)
We need some feedback from other people now. Devs are welcome to use this information to open up ways to fix g-sensor in kernel.
I am using mdeejay desire hd 3.4 build. These may be different in other builds. If you find out please share.
Freezes returned after reboot. I am trying to find out how refix again.
I AM ASKING EVERYBODY TO TELL
1) If they have the freezes with their default configuration with bubble/sensor app moving/walking etc.
2) If my values fix the freeezes
3) If their filenames etc is different
4) Please also write your build and kernel type/version/base winmo rom and radio
Example: (copy paste and edit in your post please)
Default configuration have freezes: YES
New values fix freezes: YES
Different files: NO
Build/Kernel: mdeejay desire hd 3.4 / huanyu #21 evo base miri WM6.5 (21916) v19.1 (3.14 base) 2.15.50 radio
This is not over yet, with feedback we might find exact long term fix for everyone.
EDIT: These values work with some people. If they don't work you, experiment with different values. Since the results are reflected in realtime for most builds (no reboot required) it is much easier. Also don't edit the file on windows pc, it may get messed up. Some builds auto update the values when sensor app is reopened/switched to.
IMPORTANT: Try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
EDIT 2: My sensors seem to be working perfectly since I also calibrated the z-axis. (post 61 on page 7) I need confirmation on this.
wow! thank you very much!
will try and post results soon.
Default configuration have freezes: YES (from time to time, not always)
New values fix freezes: YES. Post 11
Different files: NO
Build/Kernel: hyperdroid 1.6 / michyprima R11
before, using a live wallpaper called shake them all, the phone would insta-freeze on me.
using your values from post 11 (simple copy paste), no more freezes. And i really abused the wallpaper!
If this changes, i'll report here
EDIT: new answers
Post 1 is not for freeze fixes.
The solution is not long term.
I am extensively trying to find out what exactly made the freezes go away.
Because while it worked for many hours. After reboot freezes came back. I will hopefully find out why. Also the reason why the values change every minute is mistery. Contents of the file (values) change after you start or switch to any app that accesses the sensors. After android has booted it won't get updated unless the sensor reading apps are working.
I have been trying with many builds and kernels for theese freezes and they were never gone before. This time it never froze for several testing hours till I rebooted. That must be something.
Fixing the g-sensor after calibration corruption is ok. Adjusting level offset is also ok. But freezes need some more testing.
new answers in my above post.
you said that after the reboot freezes would happen. i change the permissions to read only on the AK8973Prms file, rebooted and no freezes.
crawlingcity said:
before, using a live wallpaper called shake them all, the phone would insta-freeze on me.
using your values from post 11 (simple copy paste), no more freezes. And i really abused the wallpaper!
...
new answers in my above post.
you said that after the reboot freezes would happen. i change the permissions to read only on the AK8973Prms file, rebooted and no freezes.
Click to expand...
Click to collapse
I am glad it worked for you and we are making progress.
I also had tried changing permissions before but after one minute permissions revert back to writable and the files is updated by the system.
just tested again. restored the default file (with the default values) and as soon as the little droids (or homers in my case) start moving - freeze.
Changed again to your values in post 11, changed permissions to read only, rebooted, played with the phone, i even juggled my HD2! No freezes. I think i won't change anything, unless i need to correct the pitch and the roll.
crawlingcity said:
just tested again. restored the default file (with the default values) and as soon as the little droids (or homers in my case) start moving - freeze.
Changed again to your values in post 11, changed permissions to read only, rebooted, played with the phone, i even juggled my HD2! No freezes. I think i won't change anything, unless i need to correct the pitch and the roll.
Click to expand...
Click to collapse
How are you changing the permissions?
I change permissions to readonly with rootexplorer and after I switch to sensordebug or bubble or phone tester app, the file reverts its permissions back to writable and gets updated.
BTW bubble app freezes more frequently than other apps. But when my freezes were gone, even bubble app never froze even when abused.
I'm just using root explorer. Select the file, uncheck the "write" option, close root explorer. Open sensor debug or whatever, check the file, untouched.
crawlingcity said:
I'm just using root explorer. Select the file, uncheck the "write" option, close root explorer. Open sensor debug or whatever, check the file, untouched.
Click to expand...
Click to collapse
I am doing the same but it becomes writable again. Must be because of different sensors.xxx.so file and build or maybe because you are trying with a wallpaper and not an app.
BTW editing the file on windows pc may not work because of paragraphing difference between windows and linux. If this happens, my phone just adds new zero values to the end of the file.
I am dying to reproduce the fix. I will test with some different builds. That constant file updating is killing me.
To give everyone who wants to start over/underclocking there Razr's a head-start with some values, I think it would be best to gather some real-world data from the XDA community. You can drastically reduce your device's power consumption by undervolting, extending your battery life.
The data presented in this thread should be used as a general guideline, and will not be stable on all devices. At such a small die size (~45nm), imperfections in the semiconductor are unavoidable, and as such, each device will have a (slightly) different stability point. That being said, it's a lot easier to over/underclock properly when you have a set of known, working values on other devices (even acknowledging the fact that all CPUs have different stability points).
I personally have left my phone at stock speeds, but undervolted the CPU drastically to improve my battery life. For the technically inclined, power consumption of a CMOS circuit decreases quadratically as a function of voltage. So for the majority, halving the voltage of a CPU at the same frequency will reduce the power consumption to only one quarter of the original.
So, without further ado, here are my new set V_SEL values (as well as the stock, original ones). I manually tested the undervolted settings using the free StabilityTest application, which cycles through all clock frequencies in the table below, and ensures the CPU is stable at all frequency/voltage combinations.
Code:
Frequency | Stock | Undervolted
[MHz] | [V_SEL] | [V_SEL]
-------------------------------------
1200 | 61 | 45
1000 | 61 | 38
800 | 55 | 31
600 | 43 | 28
300 | 26 | 18***
(aside: does anyone know what units the V_SEL values are in?)
After the change, not only does the phone consume a lot less power (I can manage over 3 days on a single charge now, before it was around 2), it also gets less hot under use as well. Note that the values I got above do have some room for further adjustment, but they're very close to the minimum voltage values (the phone is very unstable when V_SEL = 40 at 1200 MHz).
*** Edit: You need to set the minimum voltage in the Calibration menu in QuickClock Advanced to set V_SEL lower than the stock value of 26 (thanks spikegibeault).
For those who are curious, you can manually set the V_SEL and clock speed values without using a tool by simply executing the following script (must be root, and should be done on every boot since the values revert to the default when the phone reboots).
Code:
echo 1 300000000 26 > /proc/overclock/mpu_opps
echo 2 600000000 28 > /proc/overclock/mpu_opps
echo 3 800000000 31 > /proc/overclock/mpu_opps
echo 4 1000000000 38 > /proc/overclock/mpu_opps
echo 5 1200000000 45 > /proc/overclock/mpu_opps
echo 0 1200000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 800000 > /proc/overclock/freq_table
echo 3 600000 > /proc/overclock/freq_table
echo 4 300000 > /proc/overclock/freq_table
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Note that in the script above, I changed the minimum V_SEL to 26 so most people can just try the script after installing the kernel modules. To go lower than 26, you still need to use QuickClock Advanced to change the Calibration values. If anyone knows what value is modified in the system, please let me know so we can avoid having to use a discrete application (and thus, can simply use shell scripts to set all values).
Thanks, I was weary of changing the vsel of my phone because I didn't want to go through the trial and error of changing over and over again. My phone is underclocked, undervolted and stable.
How can I undervolt my Maxx? I've under and over clocked but I've never messed with voltage. I'm also running eclipse 1.3
Thanks
Sent from my DROID RAZR using XDA
prsterero said:
How can I undervolt my Maxx? I've under and over clocked but I've never messed with voltage. I'm also running eclipse 1.3
Thanks
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
Just flash the .zip found here and install Quickclock Advanced. Mess with Vsels.
Leviathan26 said:
Just flash the .zip found here and install Quickclock Advanced. Mess with Vsels.
Click to expand...
Click to collapse
found where? i dont see a zip on this thread and no link haha. just in case your talking about the mo_simp_1.5 zip thats already flashed with the 1300mhz overclock script. i tried undervolting but any values i change when i exit out it reverts back even if i hit save. i tried changing the values in quickclock-advanced-scripter and i tried toggling the fulledit option found in the advanced menu as well.
Edit: now it says vsel unknown and when I go to advanced - scripter the vsel values are listed as null
prsterero said:
found where? i dont see a zip on this thread and no link haha. just in case your talking about the mo_simp_1.5 zip thats already flashed with the 1300mhz overclock script. i tried undervolting but any values i change when i exit out it reverts back even if i hit save. i tried changing the values in quickclock-advanced-scripter and i tried toggling the fulledit option found in the advanced menu as well.
Edit: now it says vsel unknown and when I go to advanced - scripter the vsel values are listed as null
Click to expand...
Click to collapse
Yeah, that is what I meant, sorry, forgot to put a link there. I'm sorry, I can't help you with that problem, I've never had it.
prsterero said:
Edit: now it says vsel unknown and when I go to advanced - scripter the vsel values are listed as null
Click to expand...
Click to collapse
I've noticed that bug on occasion, and was always fixed when I restarted my phone... With Quickclock, once I enabled the Full Edit option, I was able to change the V_SEL values right from the Overclock menu. If you look at the overclocking scripts, try running them manually and then checking back in Quickclock Advanced to see if your changes were made. Once you have a stable and working overclock, you will probably not need Quickclock anymore (and just get an app like ROM Toolbox or a scripting app), and can just set the script to work on boot.
I added my script to the original post, so you can see how it looks (must be run as root).
As an aside, does anyone know why my phone just crashes whenever I set a V_SEL value less than 26? (It never used to before I recovered back to the pre-patch and re-applied it, not sure what else I changed...)
I believe I successfully undervolted now with a 1300mhz over clock 300mhz is set to 18 and seems to be running fine
Edit: I ran the stress test in quickclock for 100 seconds and got 2 lag spikes and reached 91 degrees. Not sure if the lag spikes is a good result or not since this is my first experience under volting
Sent from my DROID RAZR using XDA
1500 MHz at 63 vsel running stable, i havent messed around much. i've beeen keeping it at 1300 at 60 for daily use
also, when using 18 as a vsel for 300mhz my system crashes
i'm running eclipse rom
Edit, after changing the bare minimum under calibration to 20 and setting at 20 i'm running smooth
spikegibeault said:
Edit, after changing the bare minimum under calibration to 20 and setting at 20 i'm running smooth
Click to expand...
Click to collapse
Thank you so much, this is what fixed it. I had to set the calibration value, reboot, and then I was able to set my V_SEL back to 18.
Does anyone know what value is modified when this is set? It would be nice to know, so we can have an initialize script and a boot-up script (so you don't need to keep a discrete application installed once your OC is fine and running).
after a reboot since the values reset i went to change them again and everytime i do the phone freezes up and i have to do a hard shut down. how come it worked before with the same values and now it wont? nothing has changed in the system
edit: i think the problem was it reset itself to a max of 1200mhz when before it was 1300 so the value that i used before at the 1300mhz level wasnt working with the 1200, causing the phone to freeze.
edit 2: actually it just froze again haha. maybe the 1300mhz kicked back in after i did my editing or something.
edit 3: seems like i cant do any undervolting anymore because after about 5 minutes the phone freezes.
prsterero said:
edit 3: seems like i cant do any undervolting anymore because after about 5 minutes the phone freezes.
Click to expand...
Click to collapse
What values are you using? Did you modify the appropriate parameters in the Calibration menu (assuming you're using QuickClock Advanced)? Remember, not all phones are equal, so you might have to raise the voltages I posted a little bit.
I'm still going strong on my posted settings (currently 35 hours on battery, with 40% battery left). Stock speeds but undervolted.
ice9tech said:
What values are you using? Did you modify the appropriate parameters in the Calibration menu (assuming you're using QuickClock Advanced)? Remember, not all phones are equal, so you might have to raise the voltages I posted a little bit.
I'm still going strong on my posted settings (currently 35 hours on battery, with 40% battery left). Stock speeds but undervolted.
Click to expand...
Click to collapse
im using the same values you listed, which before was working just fine. but after that first reboot it wont work anymore. the parameters in the calibration menu are as follows: 18, 300, 1560, 1300, 300. which made me realized the stock max speed was still set to 1300 but i put it back to stock 1200 as im typing this. tried the same values again after changing the max stock speed in the calibration menu and it froze instantly after applying ^_^
edit: just out of curiosity how much have u used the phone for that kinda battery life? and screen on time?
edit 2: i just changed the values to 58, 55, 45, 38, 26 and so far no freezing. to do this as trial and error would i have to keep going down more and more till i freeze to find the lowest values possible? and would i have to do one clock speed at a time or bring them all down 1 unit then test? also, isnt the biggest one the 300mhz voltage since thats where it is most of the time with the screen off? so with it staying the same as stock value, it wouldnt make much of a difference?
ice9tech said:
Did you modify the appropriate parameters in the Calibration menu (assuming you're using QuickClock Advanced)?
Click to expand...
Click to collapse
How are you getting quick clock adv installed, i had purchased for my og DROID, but it says not compatible with my RAZR.
Sent from my DROID RAZR using xda premium
Ronin3178 said:
How are you getting quick clock adv installed, i had purchased for my og DROID, but it says not compatible with my RAZR.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I downloaded it on my computer and moved it to the downloads folder then installed from there
Sent from my DROID RAZR using XDA
prsterero said:
I downloaded it on my computer and moved it to the downloads folder then installed from there
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
Ok, I went around a long way and installed on my NookColor and then backed up thru TB sync'd to dropbox and my pc, unzipped the apk, shared the apk thru dropbox to my RAZR.......
Anyway, with QC Adv, anytime I try editing or using the auto-cal function, the app freezes and nothing happens. The only way I can get it to do anything is to force stop and clear data -> back to square one.
When I go into CPU Speed scale and hit the calc, this is what populates.
1200 75
1000 64
800 53
600 44
300 29
BTW, just thought of this, what is everyone using GB or ICS? I am on ICS 6.14.75XT912.Verizon (leak from early April/late March) That could be my problem too.
Ronin3178 said:
Anyway, with QC Adv, anytime I try editing or using the auto-cal function, the app freezes and nothing happens. The only way I can get it to do anything is to force stop and clear data -> back to square one.
Click to expand...
Click to collapse
I've noticed the same behaviour, and I think it's fairly well known by most users. I wouldn't worry about it though, it's not difficult to manually overclock/undervolt your phone.
Ronin3178 said:
When I go into CPU Speed scale and hit the calc, this is what populates.
[...]
Click to expand...
Click to collapse
That's what I get as well, and note that they are higher values than even the stock ones! Why, you ask?
Remember, the purpose of QuickClock is to make overclocking easy for most users. Those values are calculated based on predetermined "guaranteed" stable values by the application developer. I would not exceed the stock values I posted on the stock page under any circumstances, unless you are very familiar with overclocking (especially since you should be able to get a decent overclock without modifying the V_SELs). By all means though, if you want to reduce the V_SEL values (and it's stable on your phone), you should - it saves quite a bit of power (hit over 2 days on my last charge).
Also, I'm on GB, but I think you should be fine doing this with ICS (the kernel module should work with both IIRC).[/QUOTE]
ice9tech said:
I've noticed the same behaviour, and I think it's fairly well known by most users. I wouldn't worry about it though, it's not difficult to manually overclock/undervolt your phone.
Click to expand...
Click to collapse
Ok, is there a tutorial somewhere on how to do the undervolting manually? Because QCA is useless on this phone, it doesn't even load the modules for testing vsel or clockspeed on my phone. The script editor only looks like it shows speed.
Sent from my DROID RAZR using xda premium
Ronin3178 said:
Ok, is there a tutorial somewhere on how to do the undervolting manually? Because QCA is useless on this phone, it doesn't even load the modules for testing vsel or clockspeed on my phone. The script editor only looks like it shows speed.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
In quick clock go into advanced and enable full edit. Then go to over clock and edit the voltage on the right side of the screen
Sent from my DROID RAZR using XDA
can we do this using SETCPU?
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
Netrunner157 said:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Click to expand...
Click to collapse
Mpdecision.. Qualcomm closed source. Hate it.
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
How do I do this?
> Mpdecision.. Qualcomm closed source. Hate it.
Is this a tool that fixes this?
So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
This is from the program kernel adiutor program you can find here( http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
Davinci50 said:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
Click to expand...
Click to collapse
Oh man I did not know how to use google. You opened my eyes. /s
> kernel adiutor
kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
CM drops to 300.. Turn off mpdecision.
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol
Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
Moody66 said:
CM drops to 300.. Turn off mpdecision.
Click to expand...
Click to collapse
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
Its in snapshot phase. Of course its stable.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
Its fine. Read the cm forum thread.
@Moody66
No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.
Make a backup, load the rom ,and test drive it like we all do.
God I love Google NO /s
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Moody66 said:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Click to expand...
Click to collapse
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
Isn't that easy. It will always default of there isn't something to takes its place.
Moody66 said:
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.
Noone has made a custom kernel for it. Obviously since it has emui.
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?
The app is setedit and you'll need to hand over almost $3 Canadian if you want these tweaks. 1 of them will work for sure without needing to enforce but I think it's a sweet deal and 3 of these are working on Pie. 2 of them, or even 1 is worth the price.
You'll need to go into a shell and enter exactly:
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Copy and paste it. If you don't know how to do that just look up ADB, android developer options, and Samsung USB drivers.
First the freebie. Go into Secure Table and click +add new setting (your first entry may ask you to grant a permission. DO IT)! enter: clock_seconds value: 1 BOOM! Hope you like it because it'll NEVER go away! Just kidding. If you factory reset... or simply enter a value of 0 you'll be rid of the ticker.
Next up I think is a freebie, too. Still in Secure Table, scroll down to sysui_qs_tiles delete everything. NO DON'T! Carefully, without erasing the entire list, add in MobileData exactly like that. So actually it'll be a comma first. Have a look around for other tiles because 'ol Sammy likes to keep things real tight with the carriers. You can also remove some but I think it's best to not potentially freezing your phone up.
Now, pretty sure these ones will need the guardian to stick so if you can manage 3 bucks it'll be worth it, especially the last 2!
Change tile rows and columns.
Right above the tile edit in Secure Table is sysui_qqs_count I like a value of 7. Don't go too small or too high. Or do it and see what happens. Please don't. I can only vouch for 7 and 8. I have heard of 3 but never tried it. This changes the first row, first pull on notification menu.
Now to change the rows, the long pull I guess you can call it, qs_tile_row in Secure Table still. I do 4. I heard if you enter in 50 you get a widescreen TV. No idea. I only tried 4.
Screen Timeout not long enough?
While some of you may not need it, I need more than 10 minutes. Head to System Table and... not sure why, but I think this needs both screen_off_timeout_rollback AND screen_off_timeout to work. I set mine to 1800000 (yes 5 zeroes) to get 30 minutes. Do it on both. Double that, 3600000 will give you an hour. So if you want 13 minutes and 27 seconds, figure it out. I think entering a value of 1 will get you a free trip to the ODIN app. Don't know what that is? You'll find out pretty quick if you screw this one up. Of course you're gonna head to the menu and look to see a new entry of 18 minutes and 55 seconds. Not happening. What you will see is that no selection is made. DON'T TOUCH IT! Just leave it alone. It's working. This one works in Pie. Only one setting is needed. Can't remember but you'll find it.
These 2 are the bestest and they work in Pie.
Goodbye HIGH BRIGHTNESS and HEADPHONE VOLUME warning!
In Global System set audio_safe_volume_state to a value of 2. "But mine's already at 2." So then you've been warned. Now add it to the guardian.
In System Table, you'll want to alter a value of 1 in the shown_max_brightness_dialog "But I don't have that entry." So close the app, crank up the brightness and be told how evil it is. Wasn't that fun? Now fix up the entry. Add it to the guardian with the 1 value and if set to 0 don't forget to change to 1
*NOTE* most of these values take about 15-45 seconds to kick in after every reboot. So, before you reboot and say it doesn't work, well, you're kinda right. But you'll soon forget about it and one day be able to reboot without seeing if it works or not. Finally, one day, you'll go to turn up the brightness, or volume, and that warning will not appear. And THAT'S when the real joy is felt. As you're cranking up that slider, in all of .02876 seconds, you're going to think, "Stupid warning" "OMG I am not gonna get a warning" "Hey cool I didn't get the warning. Anyone see that?"
Bonus Feature! When bored I random;y change values of random entries. See how fast you can screw yours up! Don't play with anything unless it's your friend's phone. We're not friends.
I can't vouch this works on any other device except A8. It's a representation of what's on your phone. Adding a custom ROM will change the output and results. Use your noggin, yo
Finally, I turned off battery optimization for the app and feature pack, and turned off notifications. It works fine. No usage pops up because it's very small and no problems with enforcing the edits. No annoying notification required.
mindlery,
I'm doing an article about Drone flight and high NITS display devices. A tablet or phablet that can display the sun equivalent brightness is very expensive so most pilots use cell phones. Of these cell phones samsung and lg both have models that will BOOST brightness (manually at least on the lg G7) but it will only boost for up to 3 minutes. one might think its' a heat issue but the timer is probably a battery saver because when flying I keep resetting my boosted brightness on the Lg-G7 and the phone never gets warm.
So you appear t6o have knowledge on this and there may be an opportunity to help a bunch of pilots if a boost timeout can be changed (easily via app or some easy method) to fix the boosted time to about 30 minutes or make it a manual switch.
If you are at all interested, I'm going to do an article and video for other pilots on this if I can get a solution down.
Bill