Related
[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.
Hello,
Anyone have an idea of how to simply turn off LED button back lights?
It seems it could be done as there is already at least one app that uses them for notification.
Here is what I am trying to do:
I've downloaded a desktop alarm clock app that turns the screen back light WAY down so it is not disruptive in a completely dark room while sleeping. But, the buttons remain illuminated.
Basically 8 want to use tasker to launch those clock and turn off the button back lights if the phone is charging and the time is after a certain hour.
I am thinking I could fire off a script with tasked to do thwarting back lights portion of this as well, but I don't even know where to begin.
Any ideas? Thanks!
Sent from my Dell Streak using XDA App
I'm rooted, and use an app called AdjBrightness. Works wonders, and also via menu, you can totally turn off the LED lights.
Hope that helps.
Cool, I will check it out. Ideally I would like to do it automatically, without having to open another app, but this tells me it ostensibly at least doable.
Thanks!
Sent from my Dell Streak using XDA App
If you want the code, just do this from adb or from your phone's terminal.
echo "0" > /sys/class/leds/button-backlight/brightness
Thanks! I think that is getting pretty close to what I need. Any idea if/how this could be written or saved as a SL4A script that could be fired off with tasker?
Also, I'd need to configure an exit task as well for morning, so I will need to know how to set all the buttons back to normal.
I know this is kinda minor, but I am excited about it nonetheless. Looking forward to having a nice, super dim clock to check the time late at night.
Thanks again!
Sent from my Dell Streak using XDA App
Spleisher said:
Thanks! I think that is getting pretty close to what I need. Any idea if/how this could be written or saved as a SL4A script that could be fired off with tasker?
Also, I'd need to configure an exit task as well for morning, so I will need to know how to set all the buttons back to normal.
I know this is kinda minor, but I am excited about it nonetheless. Looking forward to having a nice, super dim clock to check the time late at night.
Thanks again!
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
You could always leave your computer on overnight and make a macro that executes the adb command to dim the leds and then executes another that makes them bright again at a certain time.
There must be something similar you can do on the phone though.
Thanks for the thoughts Meltus.
Well, I did it! I actually created a solution that is, at least to me, the first thing I have done that might actually be worth it to others and might be worth sharing.
I'll post this in more detail in the Apps/Themes forum as I am not sure it belongs here, but the short version is that you can use a plug-in called "Locale Execute" that allows you run SU commands in Tasker.
So, I created a profile in Tasker so that when the phone is plugged in to AC power between certain hours (I may add some other contexts to tweak it, like maybe say it has to be in landscape orientation), it launches my desk clock app, turns the screen down to the very lowest setting (not the "low" setting allowed at the user level), and turns the button lights off using the command you gave me.
Then, when the AC power is pulled, It automatically goes to my default home screen, returns the screen brightness to normal, and turns the button back-lights back on.
It really is pretty cool!
Spleisher said:
Thanks for the thoughts Meltus.
Well, I did it! I actually created a solution that is, at least to me, the first thing I have done that might actually be worth it to others and might be worth sharing.
I'll post this in more detail in the Apps/Themes forum as I am not sure it belongs here, but the short version is that you can use a plug-in called "Locale Execute" that allows you run SU commands in Tasker.
So, I created a profile in Tasker so that when the phone is plugged in to AC power between certain hours (I may add some other contexts to tweak it, like maybe say it has to be in landscape orientation), it launches my desk clock app, turns the screen down to the very lowest setting (not the "low" setting allowed at the user level), and turns the button lights off using the command you gave me.
Then, when the AC power is pulled, It automatically goes to my default home screen, returns the screen brightness to normal, and turns the button back-lights back on.
It really is pretty cool!
Click to expand...
Click to collapse
Good job, sounds pretty cool
I'm sure many people will find this useful!
Does the louder volume app work with the streak?
SeanH said:
Does the louder volume app work with the streak?
Click to expand...
Click to collapse
No i'm afraid it doesn't. Also, send me a pm next time rather than ask in someone else's thread
I did turne off button's back-light by adjusting the context of "/sys/class/leds/button-backlight/brightness" file from 255 to 0, it works great, but it gets back to normal after phone restart, I even went to properties of the file and removed all the "write" rights, but it won't give in.
The light coming from the 4 soft keys and the two physical home and end buttons is bugging the hell out of me. They hurt my eyes, especially when it's dark.
Is there some kind of script I can run to permanently turn them off? Preferably a zip file I can just flash in the recovery or something.
Interesting that you want them turned off.
I want to know how to turn ON the soft key lights, because sometimes I press the wrong key (as I came from a Droid-X).
Easy, if your rooted download gscript and run one of these scripts one for of is lightsout.sh one for one is lightson.sh
push them to your sdcard/gscript folder then load them in gscript and run from gscript
there is allso trackballon and trackballoff if you want to turn your trackball on or off for some reason. I will have the green and orange led up later
NOTE: if there is an error like the lights turn off after a bit then edit the gscript lightson.sh and remove the line that says sleep1.
NOTE#2: this may cause soft reboots were your phone will run the boot animation and restart the xserver of android shell blah blah. nothing to worry about doesnt hurt your phone
androidifyme said:
Easy, if your rooted download gscript and run one of these scripts one for of is lightsout.sh one for one is lightson.sh
push them to your sdcard/gscript folder then load them in gscript and run from gscript
there is allso trackballon and trackballoff if you want to turn your trackball on or off for some reason. I will have the green and orange led up later
NOTE: if there is an error like the lights turn off after a bit then edit the gscript lightson.sh and remove the line that says sleep1.
NOTE#2: this may cause soft reboots were your phone will run the boot animation and restart the xserver of android shell blah blah. nothing to worry about doesnt hurt your phone
Click to expand...
Click to collapse
First of all, thank you.
But I ran into some issues/have questions:
1) The lightsoff script works after I run it in gscript, but when I turn the screen off and back on again, the soft key lights turn right back on.
2) By the green and orange LEDs, do you mean the notification LED? Because if so, it's not necessary; I actually need those ones.
3) The green phone and red end/power lights still stay on.
4) I don't see a line that say "sleep1" in the lightson script.
If you are running a CyanogenMod ROM, there is a control for the automatic backlight that also lets you set the light levels fot when the softkey backlights go on (which you can set to 0 to never come on.) I don't have a CM ROM installed at the moment, but it's in settings->CyanogenMod ROM settings somewhere. if you cannot find it, I can dig around.
[edit] I think it's in user interface->automatic backlight. That's where it was in CM6 (Froyo).
doogald said:
If you are running a CyanogenMod ROM, there is a control for the automatic backlight that also lets you set the light levels fot when the softkey backlights go on (which you can set to 0 to never come on.) I don't have a CM ROM installed at the moment, but it's in settings->CyanogenMod ROM settings somewhere. if you cannot find it, I can dig around.
[edit] I think it's in user interface->automatic backlight. That's where it was in CM6 (Froyo).
Click to expand...
Click to collapse
Thank you! I found it after digging around the settings a bit.
on Arc S
while button-backlights are off value of
/sys/class/leds/button-backlight/brightness is 0
while its 0 change permissions to read only
they are disabled
I can also limit current to 150 in max_current which limits current and lights are dimmed if you want it running but not at max brightness...
added
echo 0 > /sys/devices/i2c-0/0-0040/leds/button-backlight/brightness
chmod 444 /sys/devices/i2c-0/0-0040/leds/button-backlight/brightness
Click to expand...
Click to collapse
to /system/etc/hw_config.sh
now they are set off on boot
another more hardcore approach is to unplug the leds. remove the back cover, sdcard, and battery. then use a t5 or t6 torx screwdriver to remove the four screws. remove the back casing, starting at the top, near the headphones. peel off the copper plate held on by 4 pieces of tape, but dont bend the copper. then in the middle of the circut board there will we a yellow film. peel it back to reveal a hole in the board where a long and skinny brown wire plugs in. unplug it, it just lifts straight off. follow these steps in reverse, and the softlights will be disabled.
WARNING: this WILL irrevocably void your warranty, although seeing how old the model is, i doubt it has one
Hey guys, can I use any of your solutions with my samsung galaxy s plus ?
Diablob555 said:
Hey guys, can I use any of your solutions with my samsung galaxy s plus ?
Click to expand...
Click to collapse
I hardly know anything about this aspect of the Eris (my phone), so I really can't say, but I would doubt it being such different hardware and of course different manufacturer.
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
settings - display- blue light filter - custom schedule
vivilxw said:
settings - display- blue light filter - custom schedule
Click to expand...
Click to collapse
Blue Light filter is disabled and schedule is disabled as well. I've tried turning ON the blue light filter when the issue happens and it actually kicks in on top of the other issue and makes it even MORE yellow.
Seems unrelated to that.
Have you checked the sunset to sunrise toggle..?
Anyone having this blue light issue...blue light is enabled. When I turn on phone from sleep mode it takes like a second to switch to blue. Very weird
Sent from my SM-G965U1 using Tapatalk
zeebone said:
snip.
Click to expand...
Click to collapse
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
(ORIGINAL, not needed, left for posterity)
This needs more attention. I know EXACTLY what this is. You came from a more recent Android device that uses Google's own "night mode" settings. I know, because I did too. I came from the Razer Phone and had night mode enabled on that on schedule. After my screen turned a real dank orange color at night, I started looking for the setting and discovered Samsung's "Blue Filter" setting and that enabling it made the orange color even more dank. So I immediately knew that the setting must have carried over when I logged into my google account and carried over my settings.
I have a workaround, but it is just that, it's not a permanent fix and I'm still trying to figure out how to fix it permanently. You need to install System UI tuner from the playstore. Follow the instructions to make the app work by granting permissions using ADB while connected to a PC. This is not root and will not void your warranty as such. From here, you can either just disable "Night Mode" under the miscellaneous tab or you can go to the playstore and install "Nougat / Oreo Quick Settings" which will allow you to add the toggle for "Night Mode" to your quick settings pull down bar. Unfortunately, you have to do this every night to get rid of the ugly orange color.
I've tried disabling the setting on my Razer and syncing everything in my google account from that phone, then restarting my galaxy and hoping that the settings would transfer over, but it hasn't worked. My fear is that I will have to factory reset the Galaxy, go back to Razer, toggle the night mode on and back off. Sync settings, then sign back into my galaxy and hopefully the settings will not come back this time. I just haven't because I don't want to set EVERYTHING back up again, ugh.
If anyone is aware of how to disable the "Night Mode" schedule feature in a different way without factory resetting the device, please let me know. Thanks!
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
cawith said:
There's an easy solution to this, if you hadn't switch off the night mode on your previous phone before transferring to the S9:
https://www.reddit.com/r/GalaxyS9/comments/85blz5/psa_night_light_and_blue_light_filter_overlap
Click to expand...
Click to collapse
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
lessthanzach said:
LOL. Jesus. My long-winded solution above yours looks barbaric now. Good thing I wasted a good evening sifting through ADB commands. Good on you for finding this and posting this. Nova saves the day again.
Click to expand...
Click to collapse
Wish I had waited a little bit longer and had done this. I ended up backing everything up to my SD Card using Smart Switch and then wiping and rebuilding the phone yesterday afternoon. However, I didn't choose to restore from Google and only from Smart Switch, so the night light setting didn't end up carrying over again.
Good to know I wasn't crazy and that my phone wasn't defective.
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
I was all ready to get adb working and use the above workaround, and / or install nova launcher and fix this issue but THIS WORKED.
THANK YOU it has been bugging me for WEEKS.
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
You are amazing! It was the Google play books settings.
Thank you so much! It just started happening last week so I knew that it didn't come from my smart switch settings. Google play books was on night light settings from 10p-6a. I can see my phone again at night without my screen being yellow or without having to restart my phone. Thank you so much!!! I NEVER would've looked there.
Works like magic on my S7. Thanks a lot!
Perfect!
This fixed my problem, so thank you!
Google play book... who would have guessed..
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
zeebone said:
So I got my T-Mobile S9+ on Tuesday. I got everything loaded up and restored and at 10pm, I noticed the color shift on the screen into a night mode type color scheme. Whites were turning a yellowish hue. I'm running Nova Launcher as my main launcher and checked all the settings in the phone itself, and nothing is enabled for Night mode. I ended up having to reboot the phone and it was back to normal.
It happened again the last two nights at 10pm EST. No idea why. I've tried everything short of rebuilding the phone (I know most will suggest this, but I'm trying to avoid it for the time factor). Rebooting seems to reset the clock on whatever is doing it and it goes back to normal.
My wife has the same phone and similar setup with Nova and hers doesn't do it. I've tried going back to the stock Samsung launcher when it is happening and nothing seems to fix it.
Anyone had this happen? I don't see any third party apps that would cause this that I have installed. the only app I can think of that even has a night mode is Nova, but that just effects menus and turns them black, not yellow.
*Edit* Sorry, I meant to put this in the Q&A Section.....
Click to expand...
Click to collapse
You might have your blue light filter turned on to a specific time. Mine is set to come on at 6 pm and go off at 6 am. Check that in settings.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Did you tripped your knox warranty, when using this ??..... I want to disable night mode on my note 9.....did adb trigger knox ??? Please advice sir... And thank you
Click to expand...
Click to collapse
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Buddy ur basically a lifesaver. Note 10+ fixed too, can confirm!
Buddy the workaround just saved me at least one trip to SES which is like 30 mins away from my house in Long Island, saved me from erasing the phone and restore it which would definitely be a nightmare and also u just saved my one big annoyance with this phone for the first week of usage!! U are the man!!
PorcoPorco said:
I had this problem too, and couldn't find an easy solution, until today.
The problem is that samsung will ask you out of the blue if you wanted to enable the "Nightmode" which is separate from "Blue Light Filter," and the two can overlap. Which is annoying. And you'll find yourself looking everywhere to find the setting to turn it off.
So, where is this setting hidden?
Google Playbook.
Launch google playbook, read something, anything. Click the screen and then the "Aa" icon, for changing brightness/fonts. Then there, click Setting again, and you'll find "Night Light" turned on and scheduled.
Simply turn it off and Voila!
No rooting, no launcher or nothing required.
Click to expand...
Click to collapse
Vinay_sandy said:
If nothing solves your peoblem then just download systemuituner app from playstore and give it some permission using adb commands and then turn off the night light option in the app.
It helped me .:fingers-crossed:
Click to expand...
Click to collapse
I tried it, both options switched off.
lessthanzach said:
EDIT: I Fixed it finally!
I have no idea if there's an easier way to fix this, but here's what I figured out sifting through adb commands. If you run the command
Code:
adb shell 'settings list secure
you will get a list of many of the device's settings. The one we're modifying is called "Night Display" which is different from what everyone has been calling "Twilight Mode" in my google searches. So all we have to do is run the two following codes:
Code:
adb shell 'settings put secure night_display_activated 0'
Code:
adb shell 'settings put secure night_display_auto_mode 0'
This fixed my issue immediately and it persisted through my manual date and time adjustments just to verify and also two reboots. I know ADB commands aren't everyone's cup of tea but it is also a very powerful tool at unfu**ing what manufacturers have fu**ed. Hope it helps others as well!
Click to expand...
Click to collapse
Huge thanks as you saved me from factory resetting my new Mi 9 Lite. That's why I love the internet.
After getting the S23U initially turned on backtap but found it too sensitive (2as getting too many screenshots that I was not intending) so I turned it off. However I am still seeing screenshots getting captured spuriously, particularly on my morning drive to work. Practically every morning I have screenshot notification and a gmap capture in my Pictures folder. Anyone else seeing this? I confirmed that backtap is not enabled, and I am being extra careful to make sure I am not accidentally triggering a volume down/power button press when I insert the phone in the car holder.
Palm swipe to capture maybe? Like, you might have this option enabled, and you might be capturing Screenshots by doing this accidentally...
ceftriaxone said:
Palm swipe to capture maybe? Like, you might have this option enabled, and you might be capturing Screenshots by doing this accidentally...
Click to expand...
Click to collapse
That is likely the case, did not even knew it existed. Thx
ceftriaxone said:
Palm swipe to capture maybe? Like, you might have this option enabled, and you might be capturing Screenshots by doing this accidentally...
Click to expand...
Click to collapse
Turns out that this is not the problem. Palm swipe is disabled yet I still see spurious screenshots of gmaps in drive mode exclusively. I am very careful not to insert the phone so that it triggers volume Dn + power.