Sent from my One X using xda app-developers app
is the default brightness the full-bright option for whatever ROM you're running? To phrase it a little better, what's the default brightness before installing the app: the half-bright or full-bright option? And does uninstalling the app revert everything back to normal?
Thanks for the feedback! Good questions too. I've added the answers to the FAQ section of the OP. Does it answer your questions:
Frequently Asked Questions
I updated to the latest version a couple days ago, and it's been working great! But as of yesterday, the settings don't stick after boot, even though the option is checked under the settings. Any way I can fix this? If it helps, my phone rebooted on me once, and then I had to hard reset it shortly after because it froze up on me. I'm on the 10-12 nightly. Thanks!
Thanks for reporting this. Can you answer a few questions for me?
1. Which ROM are you running? (it's possible that your ROM overrides the capacitive button brightness setting)
2. Which brightness levels (off, dim, or bright) have you noticed are not sticking?
3. Can you reboot and capture a logcat log after the device boots back up? With this log output I can see if it even tried to set the brightness.
If you are unsure how to capture the logcat log, try this:
1. Install "Android Terminal Emulator" from the Google Play store: https://play.google.com/store/apps/d...al.androidterm
2. Start "Terminal Emulator" on the device
3. Type "su" into the Terminal Emulator app and press ENTER
4. Type "logcat -d >/sdcard/logcat.txt" into the Terminal Emulator app and press ENTER
This will create a file named "logcat.txt" on your SDCard. Attach that log here. If you want, you can scrub logcat.txt to remove your email address and any other personal info that might be in there.
No problem! I'm running the 10-12 CM10 nightly right now. It was sticking after boot previously. I've been setting the capacitive buttons to off, and that seems to not be sticking recently (however, I've only noticed this once, so it may have just been a fluke). I know I sound really stupid, but I'm not too comfortable with doing a logcat lol... thanks for the steps though, it does seem quite easy. I'm just being really paranoid with my device right now because I can't afford another one if something happens. I'll try shutting down with the checkbox unticked, then shut down again with the checkbox ticked and see if that makes a difference. Thanks for the reply!
Okay, fair enough. When you say "It was sticking after boot previously" are you saying that it worked with a previous version of the app (v1.0.2 or older) or earlier in time with the latest version of the app (v1.0.3)? If you muster up the courage to take a logcat, I'll take a look and see if I can help. Otherwise, I'm afraid there's not much I can do since it works for me.
|Thread Tools||Search this Thread|