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.
Hi all, I've tried so many app's over the last couple of days that claim to stop the screen from locking but they have all just bypassed the lock screen... Well, they've tried to anyway. These kind of work arounds don't actually stop my phone from locking in the first place though.
My phone is a W008+ iPhone clone with Android 2.3.3. When it's charging, the screen will time out and switch off; But it doesn't lock. So I can hit any key to bring the screen back on and as it wasn't locked in the first place, I'm taken straight back to where I was.
When not charging, I get the same behaviour for ~2 or 3 seconds... Any longer and it locks forcing me to use the power key and swipe the lock screen along with any other security measures I may have in place.
What I'd like is to be able to set the 'lock' timeout in the way that I can set the 'screen' timeout. This is obviously possible but the question is: How far will I have to go to get this functionality?
Is there a setting I've missed? I'm very new to Android so there's lots I don't know yet.
Are there any app's that can really do this? Maybe this would need a root app?
Or would I need a custom rom?
Any ideas?
https://market.android.com/details?id=org.jraf.android.nolock
try this
or you could flash cyanogenmod, in cm there is an option to disable the lockscreen in cyanogemnod settings -> tablet tweaks -> disable lockscreen
'No Lock' is one of the many I've tried. This type of approach isn't what I'm after.
Someone mentioned on the AndroidForums that some systems have a 'Set Lock Timeout' setting in the location & security settings. This sounds like the kind of thing I'm after but I don't have it on my 2.3.3 system. Maybe there's some kind of tweaking app that adds this?
I will most likely get round to using a custom rom but being so new to Android at the moment, I haven't quite got the confidence for it yet. I keep finding so many stories from people bricking their similar Chinese clone-phones.
hello,
newbee here. I have acquire a sansung galaxy S2, and have a lot of fun with it.
trouble started when it rebooted at night. I figured out that some update or application crashes were the cause of it.
I think i rid of most of the issues, and got it pretty stable.
To avoid future complication, I even rid of the startup sound, but I can not rid off the vibration (especially the one when shutting down....)
I think it is part of the basic settings, and I did a lot of researches... no luck
Apps like Silent boot would not work either....
Do anyone know if it's even possible ?
If impossible, is ICS having the same issue, or can this be tuned ?
(i just can't believe no one thought of making that optional ...)
Please help me...
I'm on ICS and don't have that. It is part of system settings - sound. It usually is affected by the mode you have your phone set to (like if you have sound set to Sound and Vibrate or just Vibrate, etc). Try changing to just sound and see if that stops it from vibrating (or just silent mode with no vibrate).
Can also try to untick Vibrate on screen tap.
ICS is sweet... can't go back to GB... what you waiting for?!
Sorry, but this does not work (phone is rooted)
. tried vibration off no luck
. tried silent mode no luck
Is there someone who knows where is configured the vibration settings ?
I mean in which filesystem (full path if possible) ... ?
note: Official Samsung ICS for Unlocked Phones will come soon... unless there is a safe ROM and method to install it. For now I would concentrate on my Vibration issue.
Firstly, be patient. People will try to help you, doesn't mean the first answer fixes your problem.
As I stated... ICS does not have this problem. Phone makes no sound and no vibrate, if you set it that way on ICS.
How about give us more information. You said you're rooted but on GB. Are you using any different type of kernel other than stock? Like Siyah 2.xx?
As the filesystem where you can doodle with removing vibrations... I will leave someone with more experience to deal with that (even if I know the path)... in case I advise you something that can screw things up after.
*you might want to reset the phone - as the system notification/vibration settings should have done the trick.
hello
I upgraded to 4 versions of ICS.
Each one of them did not correct the issue : it still vibrate when shutting down the phone. (darkyrom, OCA, Pure and a "4.0.4" version having a clever 3 way option to launch (Nova, TW and Apex)).
I did not reset the settings yet but I will give it a go.
I will the thread updated.
That's a very strange bug then. The settings to control that though, is not with the launchers but with System Settings.
Maybe try this:
System Settings - Volume <inside there you have 4 settings. Try changing System to very low or all the way off. Then go to the whatever mode you have it set to (like Silent Mode or whatever)... and select Mute.
Then the lower categories of System... uncheck all of them: Keytones, Touch sounds, Screen lock sound, Vibrate on screen tap.
See if that works. If it does, then can narrow it down to one of those settings.
Thank you very much
The simplest things are not always obvious to the common....
It works, the vibration disappeared when /SOUNDS/VIBRATION SETTINGS/Vibrate on touch was set to the lowest. Meantime, the little vibration at startup disappeared as well. Now the phone can crash, update and reboot at night without waking me up ! .. a good logcat reader (just in case) running in background will help cleaning up when some error occurs....
Once again, thank you: that drove me mad.
Glad that worked. You're right, sometimes the simplest things are not always obvious, for everyone ;-)
LeFrog1310 said:
Thank you very much
The simplest things are not always obvious to the common....
It works, the vibration disappeared when /SOUNDS/VIBRATION SETTINGS/Vibrate on touch was set to the lowest. Meantime, the little vibration at startup disappeared as well. Now the phone can crash, update and reboot at night without waking me up ! .. a good logcat reader (just in case) running in background will help cleaning up when some error occurs....
Once again, thank you: that drove me mad.
Click to expand...
Click to collapse
I have chinese copy of Nexus One phone, android 2.2.1 and I don`t have VIBRATION SETTINGS tab in my menu, I can only turn vibrate on and off,
and I don`t have SOUNDS on SETINGS, I enter in AUDIO PROFILES to menage vibration,
how to turn off vibration on power on and off?
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
luizlee86 said:
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
Click to expand...
Click to collapse
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
shimp208 said:
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
Click to expand...
Click to collapse
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
luizlee86 said:
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
Click to expand...
Click to collapse
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
shimp208 said:
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
Click to expand...
Click to collapse
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
luizlee86 said:
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
Click to expand...
Click to collapse
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
shimp208 said:
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
Click to expand...
Click to collapse
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
luizlee86 said:
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
Click to expand...
Click to collapse
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
shimp208 said:
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
Click to expand...
Click to collapse
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
luizlee86 said:
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
Click to expand...
Click to collapse
Unfortunately a factory reset would probably be the best thing to do.
shimp208 said:
Unfortunately a factory reset would probably be the best thing to do.
Click to expand...
Click to collapse
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
luizlee86 said:
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
Click to expand...
Click to collapse
You could also try re-flashing the stock ROM to see if that fixes it, another suggestion that could possibly work is running a fix permissions utlity.
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
EDIT: found what was causing it! It is the latest version of Floating Notifications (when show on lockscreen is enabled)!
Thanks a lot shimp!
luizlee86 said:
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
Click to expand...
Click to collapse
That's wicked bizarre that even after all those things the problem still persists. You could try bringing it in to Verizon to see if they can do anything otherwise a hardware issue may have arisen.
Sent from my SCH-I535 using xda premium
I've noticed that no matter what setting I have it on, my tablet (M5 8.4) automatically lowers the screen brightness in Chrome and YouTube, but more noticeably in Chrome.
Any way to disable this?
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
thref23 said:
Have you checked the setting menus?
Using Firefox might be a solution.
Also, Youtube in FF has background playback as long as you are using a desktop user agent.
Click to expand...
Click to collapse
I've checked every possible setting, and read online everywhere, but to no avail. It also dims in Firefox. It dims as soon as you go into the app. After an online search, I found many Huawei owners with EMUI 8.0 having this issue. There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Funny. Would love a solution as well as this is rather annoying
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
thref23 said:
Do you guys have auto brightness turned on or off?
I never really experienced this issue, but I did observe strange brightness behavior before I began to keep auto brightness permanently enabled.
Doing a quick search, I saw one person say to turn auto brightness on, I saw one person say to make sure animations aren't disabled in dev options, some say unclick 'increase readability in sunlight' in dev options. I personally wonder if the stock launcher (which I don't use) maybe is set to override the brightness level.
Click to expand...
Click to collapse
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
There is one solution, but it requires root and I don't want to root my device after having it for a few hours.
Click to expand...
Click to collapse
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
kev1807 said:
I somehow doubt that. I am using Nova Pro and am experiencing some weird behavior when attached to the Keyboard ... (the dimming function mentioned here is, what I believe, the erroneous function, as it works quite nice when not attached to the keyboard ...
All "your" suggestions do not work - I find this "function" somewhat annoying, even without the keyboard-thing ...
may I get a link for the root-solution? I'd like to have a look at it ...
SO I forgot to mention: M5 Pro!
Click to expand...
Click to collapse
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
xKevin said:
Well, I went through with it and rooted it. I tried the fix, and... it worked! After you're rooted, simply freeze the system process (I used Titanium Backup) called PowerGenius, reboot and no more forced-auto brightness dimming.
Click to expand...
Click to collapse
hmhm. I was quite sure it was a System process - since the "bug" (dunno whether you read the thread on keyboard and brightness ...) appears with the system-icon when in Desktop-Mode ...
Great. there is a fix for this. now I need a non-root fix ... :-/
Yes, try the app ilux. Let that control brightness.
Steffe89 said:
Yes, try the app ilux. Let that control brightness.
Click to expand...
Click to collapse
Do you have a link to this app? I can't seem to find anything relevant when searching for ilux.
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Up until now I thought a reboot would bring the "wonderful" feature back ...
How comes that you mention a reboot is needed?
How do you disable it? I can only do a force stop
I'm not sure how to disable it without root (I imagine adb might work). With root, most use Titanium Backup to freeze it. I'm using Service Disabler to disable the associated services instead. Service Disabler is awesome if you are rooted, underrated app and great for EMUI because, for example, you can disable individual parts of the Tablet Manager app without breaking the features you want.
You might not need to reboot. When I initially froze it using Xposed Edge Pro, but didn't reboot, it didn't change anything for me. Could have been due to Xposed Edge Pro.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
scott.eden said:
Just disable "power genius" this has worked for me. without root. No More auto dimming.
Click to expand...
Click to collapse
Was there any negative outcome from disabling power genius?
krisu253 said:
Was there any negative outcome from disabling power genius?
Click to expand...
Click to collapse
None for me.
thref23 said:
Disabling Power Genius will also get rid of issues involving bluetooth music playback, and will prevent apps like Google Maps from getting killed off semi-aggressively in the background (i.e. so when you map out driving directions you won't have to reenter the address as you get close to your destination).
Quick note: you have to reboot after disabling Power Genius. Merely disabling it won't immediately change anything.
Click to expand...
Click to collapse
I cannot find Power Genius?
I can confirm following the above article will allow you to remove the power genius package from the Mediapad M5 8.4 on EUMI 9.1 without root.
Thank you sooooo much... You can't believe how annoying this was. No need to even reboot either and it doesn't return if you do.
Now I just need a way to too keep the custom 740DPI after reboot and this tablet will be perfect