Database Users

[Q] CM10 Brightness issues!

Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter

thejrcrafter2 said:
Well, as you may or may not know, CM10 has an option to slide your finger on the status bar on the top to change brightness. I enabled that, and initially it worked. I then started using the brightness button in the notification bar, and after like 3 clicks it got stuck on auto mode. Now no matter how many times I click it or go into display and turn off auto, restart, remove the button from the notification bar, etc, the widget stays on auto (it still changes brightness, it just says its on auto) and I can't enable the status bar brightness slide, which I personally favor over the button. Does anybody know how to get rid of the glitch? Would reflashing work?
Thanks,
thejrcrafter
Click to expand...
Click to collapse
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.

leapinlar said:
I had this same issue on CM9. For some reason once you turn on auto with the notification bar you cannot turn it off with the other setting. The way I fixed it was to use SQLiteEditor (a paid app by root explorer) to manually edit the settings database. Then I went into the setup for the notification bar to remove the option to toggle through auto so it would not happen again. If you don't want to use the paid app, another solution is to wipe data and start over, then immediately go to the notification setting and disable the auto toggle.
Click to expand...
Click to collapse
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!

thejrcrafter2 said:
Thanks. I already tried removing data for the "Settings Data" App. Should I disable auto toggle first? It also has this error in the homescreen widget (the one with all the system toggles like btooth, wifi, brightness, etc). Also, would any SQLite or other database editor work? Where would the database file be found?
Thanks again!
Click to expand...
Click to collapse
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db

leapinlar said:
Yes it is probably a good idea to turn off the toggle first.
Any database editor that works will do. But I don't know of any free ones that have a GUI to make it easy. The free ones are command line apps that are a pain.
The settings database is in /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Had the same problem on my Nook HD running CM10.1 on the hybrid install and this fixed it today. My issue was that I think I clicked "auto" while adjusting on the slider and then the brightness was stuck and the "auto" was not checked nor was it selectable. Flipped the bit from 1 to 0 and now it's working ok. Doing a CWM backup now so I'll have the fix in my gold install.

Had this problem on my Samsung T679. Just fixed it and figured I'd record the steps for my own and other's reference. I'm cheap and like doing things the hard way, so I didn't spring for SQLiteEditor. I found that sqlite3 was already installed on the phone.
Before starting: use cwm to make backup, just in case.
1. Force-stop Settings app.
2. Get /data mounted read-write.
3. Open a shell (recommend via ssh/adb, because we have some typing to do).
4. cd /data/data/com.android.providers.settings/databases
5. rm settings.db-shm settings.db-wal (not sure about this step, but the change didn't seem to stick otherwise.)
6. sqlite3 settings.db
Here is my session, you should get the idea:
Code:
sqlite> .tables
android_metadata bookmarks system
bluetooth_devices secure
sqlite> select * from system
...> where name like "%bright%";
71|status_bar_brightness_control|1
278|screen_brightness_mode|1
605|expanded_brightness_mode|0OV=I=XseparatorX=I=VO1OV=I=XseparatorX=I=VO3OV=I=XseparatorX=I=VO5
607|screen_brightness|30
sqlite> update system
...> set value=0
...> where _id=278;
sqlite> .quit
screen_brightness_mode needs to be changed to 0. Don't forget the semi-colons. Now fire up the Settings app and you should be able to enable the status-bar swipe brightness control. I had to toggle it once before it worked.

[Q] Scheduled Shutdown

Hi,
I recently got fed up with forgetting to power off my nook. So I figured out I could use Tasker to shut it down at night when it is idle, etc., but I while I was testing it I realized that when my Nook is shut down, it shows the last state of the screen before having been shut down. It is quite annoying, especially that I cannot find a workaround, since Tasker cannot unlock the locked screen.
So, my question is, that does somebody know whether there is a shell command to power off the Nook like when you press the power off button?
Or any other suggestions would also be great.

In my experience letting the nook go into standby for 8-12 hours before using it again uses less battery than shutting down completely and rebooting it.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

I use Quick Boot v4.2, Plus version which has an additional command useful for phones: Hot Boot. Free version is good enough for NST:
http://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
I use a WiFi shutdown timer on my phone though, as sleep function on shoutcast radio.
P.S. As mentioned before in my apps listings thread for standby & screen blanking I use Screen Off FX:
http://play.google.com/store/apps/details?id=jp.co.kixx.tool.offwidget

Well, maybe I wasn't making myself clear enough. The most important part here is automation. So while screen off fx is awesome, I can't really use it in this situation since my screen is already locked when I want to turn my Nook off.
The thing I am searching for is a command or an app that could shut down my Nook (even when my screen is locked) in a way that it shows the usual "Your Nook has turned off completely" picture. (Every app that I tried has made the Nook show the screen that is has shown before having been shut down.) And I would like to do all of that automated, probably with Tasker.

Sagittarius0 said:
Well, maybe I wasn't making myself clear enough. The most important part here is automation. So while screen off fx is awesome, I can't really use it in this situation since my screen is already locked when I want to turn my Nook off.
Click to expand...
Click to collapse
The way I would do it is unlock the screen, overlay an image of whatever you want to be shown using a scene, and then shutdown.
To unlock the screen, try Simulating the "n" button command with tasker to unlock the screen before shutting down. (assuming slide to unlock is disabled):
Procedure for simulating button:
In your Tasker task, Create a new Run Shell Action. (Found in the "Script" category)
In the command section, put the following:
Code:
sendevent /dev/input/event1 1 102 1
sendevent /dev/input/event1 0 0 0
sendevent /dev/input/event1 1 102 0
sendevent /dev/input/event1 0 0 0
This will send a press and a release event of the n button.
​
Check the Use Root Option.
NOTE: If this is the first time you've used root with tasker, the root confirmation dialog will appear. Make sure to check the always allow option so that it doesn't pop up again.
Just For Reference:
If you would want to use other buttons do the following:
Replace 102 with:
Power Button: 116
Replace event1 with event0 AND 102 with:
Top Left Page Button: 412
Bottom Left Page Button: 139
Top Right Page Button: 407
Bottom Right Page Button: 158
Good Luck!

Absolutely woderful!
This is exactly how I wanted to do it. :victory:
It works perfectly, thank you very much.

Pushing stuff into /dev/input is lower level than it need be.
You'll be working with scan codes there.
In a shell this sends a press of the power button (using a KEYCODE)
Code:
input keyevent 26
Shutdown is easy enough (with one small hitch).
Simply send a android.intent.action.ACTION_REQUEST_SHUTDOWN
The problem is that this is a privileged intent and can only be sent by system apps.
System apps are those that have the system signature.
You can do that by re-signing your system.
You need to have android.permission.SHUTDOWN in the manifest.

You can do that by re-signing your system.
Click to expand...
Click to collapse
Well, how can I do that?
And does this command you mentioned have the same efect as reboot -p?

Sagittarius0 said:
Absolutely woderful!
This is exactly how I wanted to do it. :victory:
It works perfectly, thank you very much.
Click to expand...
Click to collapse
Glad I could help! :good:
Renate NST said:
Pushing stuff into /dev/input is lower level than it need be.
You'll be working with scan codes there.
In a shell this sends a press of the power button (using a KEYCODE)
Code:
input keyevent 26
Click to expand...
Click to collapse
Ok, good to know. I just went for the scan codes because I knew how to quickly get them from shell getevents.
Sagittarius0 said:
Well, how can I do that?
And does this command you mentioned have the same efect as reboot -p?
Click to expand...
Click to collapse
If all your looking for is to do a shutdown or reboot, and are already using a Tasker task, the action Misc > Reboot has the ability to shutdown or do a reboot. My guess is that it does exactly what Renate NST is telling you to do - send a shutdown intent - behind the scenes. Granted, I don't know, and I don't have Tasker installed on my nook so I can't confirm that it will actually work, I have just used Tasker on other devices and it seems to work fine.
Just seems like the easiest, cleanest way would be to keep all the actions under one roof.

cuff21 said:
I don't have Tasker installed on my nook so I can't confirm that it will actually work
Click to expand...
Click to collapse
It does work seamlessly.

cuff21 said:
My guess is that it does exactly what Renate NST is telling you to do - send a shutdown intent - behind the scenes.
Click to expand...
Click to collapse
Hmm, I don't know. A regular root and su won't work.
You'd either have to have a system-signed app or hack the permission system.
There is no clear info on the difference between an Android shutdown and a Linux shutdown.
Given the choice, I'd go for the Android shutdown.

Renate NST said:
Hmm, I don't know. A regular root and su won't work.
You'd either have to have a system-signed app or hack the permission system.
Click to expand...
Click to collapse
Well I had a stack overflow link that shows a way to do it, but I can't post links yet. Either way, apparently there is a way with only root. The code from the link was:
Code:
try {
Process proc = Runtime.getRuntime()
.exec(new String[]{ "su", "-c", "reboot -p" });
proc.waitFor();
} catch (Exception ex) {
ex.printStackTrace();
}

Enable comfort view with Tasker

Hi,
I'm trying to enable the comfort view with Tasker.
Does anybody know how to do that?
Regard
fanello

You'd probably have better luck asking over at the Tasker Forum.

fanello123 said:
Hi,
I'm trying to enable the comfort view with Tasker.
Does anybody know how to do that?
Regard
fanello
Click to expand...
Click to collapse
I used a java code action to set the reader_mode_enable to a 0/1 value. It works well.

art.montesinos said:
I used a java code action to set the reader_mode_enable to a 0/1 value. It works well.
Click to expand...
Click to collapse
Could you please give a quick walkthrough on how to add this code in tasker? I have an LG V20 and would like to set comfort view to turn on at 10pm and turn off at 7am everyday.
Thanks!

Thank you, I've been trying to figure this out as well. I head set a task for the AOD, so it was easy to modify for comfort view. I attached the XML export from tasker. Change the parameter in the second step to 0 to turn off.

lemmyslender said:
Thank you, I've been trying to figure this out as well. I head set a task for the AOD, so it was easy to modify for comfort view. I attached the XML export from tasker. Change the parameter in the second step to 0 to turn off.
Click to expand...
Click to collapse
So I used this xml to create an on and off profile and set it to a schedule in tasker. However, sometimes the off profile toggles the comfort view off, but the screen is still the same color.
Does anyone else have this problem?
Also, Why would you have this setting and not be able to schedule it. LG needs to fix this, along with the ability to adjust screen brightness without having to turn off the auto brightness option ( I can do it on an LG V20, why not the G6??!).

supadoggie said:
So I used this xml to create an on and off profile and set it to a schedule in tasker. However, sometimes the off profile toggles the comfort view off, but the screen is still the same color.
Does anyone else have this problem?
Also, Why would you have this setting and not be able to schedule it. LG needs to fix this, along with the ability to adjust screen brightness without having to turn off the auto brightness option ( I can do it on an LG V20, why not the G6??!).
Click to expand...
Click to collapse
I don't use it often, although I obviously have it set up in tasker, never got around to creating a task. I don't think I ever saw it not turn off though.

supadoggie said:
So I used this xml to create an on and off profile and set it to a schedule in tasker. However, sometimes the off profile toggles the comfort view off, but the screen is still the same color.
Does anyone else have this problem?
Click to expand...
Click to collapse
I have the same problem here. Did you find a solution?

Airmaxchen said:
I have the same problem here. Did you find a solution?
Click to expand...
Click to collapse
Just figured a way out using shell commands. Works beautifully. This does require root though - just so you know.
Here is a great site on using shell commands http://www.notenoughtech.com/tasker/tasker-run-shell-commands/
The setting you want is "reader_mode_enable" It takes a 0 or a 1, 1 being enabled and 0 disabled. The command you want to use is:
settings put system reader_mode_enable 1
That will turn it on. In Tasker you need to add an action Code>Run Shell and then use that Shell command and make sure "Use Root" is checked. Hope this helps the next person searching this information out!
Sent from my LGUS997 using XDA Labs

Sobek5150 said:
Just figured a way out using shell commands. Works beautifully. This does require root though - just so you know.
Here is a great site on using shell commands http://www.notenoughtech.com/tasker/tasker-run-shell-commands/
The setting you want is "reader_mode_enable" It takes a 0 or a 1, 1 being enabled and 0 disabled. The command you want to use is:
settings put system reader_mode_enable 1
That will turn it on. In Tasker you need to add an action Code>Run Shell and then use that Shell command and make sure "Use Root" is checked. Hope this helps the next person searching this information out!
Click to expand...
Click to collapse
So a quick addition to this. The screen must be on for this to work. Use Secure Settings app or possibly one of the Auto tools apps to trigger the screen to pop on just before the shell command runs.
Sent from my LGUS997 using XDA Labs

How to change power-off timeout on Nook Simple Touch?

Hi, does anyone know how to change the power-off timeout on the Nook Simple touch? When it automatically switches off and leaves a screen saying "Your Nook has been turned off to conserve battery power" or something.
I've looked in /data/data/com.android.providers.settings/databases/settings.db but there is no setting available.

Pkill-9 said:
Hi, does anyone know how to change the power-off timeout on the Nook Simple touch? When it automatically switches off and leaves a screen saying "Your Nook has been turned off to conserve battery power" or something.
I've looked in /data/data/com.android.providers.settings/databases/settings.db but there is no setting available.
Click to expand...
Click to collapse
What do you mean by "power-off timeout"? That screen appears only when you have intentionally shut down your device by long pressing the power button and then confirming through the onscreen dialog that you want to power off the device.
Or are you talking about the forced shutdown when the device decides there is not enough battery power to stay on?
The only "timeout" I can think of is the screensaver timeout which is found in Settings.

nmyshkin said:
What do you mean by "power-off timeout"? That screen appears only when you have intentionally shut down your device by long pressing the power button and then confirming through the onscreen dialog that you want to power off the device.
Or are you talking about the forced shutdown when the device decides there is not enough battery power to stay on?
The only "timeout" I can think of is the screensaver timeout which is found in Settings.
Click to expand...
Click to collapse
My Nook will shutdown at 60% battery power, or 40%, or 20% or something, and it will say that. I remember the word in particular is 'conserve'. I think when it's run out of battery it says something different.
Is there another way to have it shutdown after a period of time? I've seen a thread about using Tasker, but you have to purchase that from the Google Play store. I'd prefer to use a script or something.

Pkill-9 said:
My Nook will shutdown at 60% battery power, or 40%, or 20% or something, and it will say that. I remember the word in particular is 'conserve'. I think when it's run out of battery it says something different.
Is there another way to have it shutdown after a period of time? I've seen a thread about using Tasker, but you have to purchase that from the Google Play store. I'd prefer to use a script or something.
Click to expand...
Click to collapse
It should not be shutting down until it's in the 20's, maybe less. Something is not right--but you knew that.
The question is, hardware or software? If it's software and you do a backup, factory reset and restore the backup, you may be right back where you started. If it's hardware, nothing you do will fix it.
A third option is to do a factory restore and rebuild your system, rather than restore a potentially corrupted backup. That way if it's not hardware, you may solve the problem.
As an afterthought, there are some "battery recalibration" apps out there--not sure if any for Eclair, though. I'm a little leery of their promises, but it might be another thing to look into.
Tasker can do many things, but I'm not sure this is one of them. There is only one version that runs on the NST. PM me for more info if you want to go that route.

I think I will make an app that does what I want. Where can I find documentation on Android 2.1 and/or information on building an app for Android 2.1? I can't find any on google, nor and the official documentation seems to only be for the newest Android versions.

Pkill-9 said:
I'd prefer to use a script or something.
Click to expand...
Click to collapse
You can prepare custom tailored file named "debuglog.sh".
Then put it into /system/bin folder.
NST's android will run it every ~10 seconds.

ucy74 said:
You can prepare custom tailored file named "debuglog.sh".
Then put it into /system/bin folder.
NST's android will run it every ~10 seconds.
Click to expand...
Click to collapse
Thanks, this is working really well.
EDIT: I did it! I used wake locks to keep the script running when suspended, here is my final script, which will shutdown the nook if it is in sleep mode for a day:
Code:
#!/system/bin/sh
# debuglog.sh is an unused path, with a service definition in /init.rc that calls this file. init.rc can't be modified because the root filesystem is created from an
# I am using debuglog.sh for my shutdown script, and if I have any other scripts I want to run in the future, I can use it for that.
wakeup_timeout=86400
wait_until_sleep() {
cat /sys/power/wait_for_fb_sleep # https://stackoverflow.com/a/11275032
}
echo shutdown-on-sleep >/sys/power/wake_lock # Prevent this process from suspending when the device is suspended: https://stackoverflow.com/a/40518240
while
do
wait_until_sleep
timeout -t $wakeup_timeout cat /sys/power/wait_for_fb_wake
if [[ $? -ne 0 ]] ; then # If the command timed out, then it reached the scheduled shutdown timeout. If the command succeeded, then the Nook was awoken from it's slu
reboot -p
fi
done
I will check that running the script doesn't significantly increase battery consumption. If not, then this should be very very helpful in extending the battery life
---------------------------------------------------------------------------
Old post:
I've created a script, but I can't seem to get the NST to wakeup when scheduled. This is the script I am using:
Code:
#!/system/bin/sh
# debuglog.sh is an unused path, with a service definition in /init.rc that calls this file. init.rc can't be modified because the root filesystem is created from an image.
# I am using debuglog.sh for my shutdown script, and if I have any other scripts I want to run in the future, I can use it for that.
wakeup_timeout=60
get_current_unix_time() {
date '+%s'
}
set_wakeup_timeout() {
#echo $wakeup_timeout > /sys/power/wakeup_timer_seconds
echo $(expr $(get_current_unix_time) + $wakeup_timeout) > /sys/class/rtc/rtc0/wakealarm
}
wait_until_sleep() {
cat /sys/power/wait_for_fb_sleep # [url]https://stackoverflow.com/a/11275032[/url]
}
wait_until_wake() {
cat /sys/power/wait_for_fb_wake #
}
set_wakeup_timeout
while
do
wait_until_sleep
went_to_sleep=$(get_current_unix_time)
scheduled_wakeup=$(expr $(get_current_unix_time) + $wakeup_timeout)
wait_until_wake
if expr $(get_current_unix_time) \> $(expr $scheduled_wakeup - 5) ; then
reboot -p
fi
done

Pkill-9 said:
I did it!
Click to expand...
Click to collapse
You can check also parameters shown via
Code:
cat /sys/class/power_supply/bq27510-0/uevent
or drain percentage directly
Code:
cat /sys/class/power_supply/bq27510-0/capacity
but remember not to drain battery completely!
nook cannot wakup easily from case like this

So after running my script for the night, the battery has gone down by 11%, so running it with a wakelock is not a viable solution.
Ideally I could have the kernel schedule wake-ups, like I was trying before, but I can't seem to do that.
Apparently /dev/alarm is used by Android to schedule wakeups, but everything I find talks about using it from an app, instead of writing to it directly from commandline.

Pkill-9 said:
...battery has gone down by 11%...
Click to expand...
Click to collapse
What service/task would You like to keep running against battery saving? Epaper driver may be power hungry, but maybe You can turn off some android services or wifi driver?

ucy74 said:
What service/task would You like to keep running against battery saving? Epaper driver may be power hungry, but maybe You can turn off some android services or wifi driver?
Click to expand...
Click to collapse
The script is what eats up battery, nothing much I can do to improve it, it's running the 'timeout cat ...' command.

I'm a little late to the thread, but I use a simple app called AutoPowerOff to control this. It doesn't seem to have any affect on battery when the system is on.
AutoPowerOff for Android - APK Download
Download AutoPowerOff apk 1.0.2 for Android. Auto power off your device to save battery life.
apkpure.com
In the app itself, you can only set the timeout to a maximum of 23 hours 59 minutes. I wanted a bit of a longer timeout, though, and found that if you edit the app's settings XML file in /data/data, you can set whatever timeout you want. I use 72 hours, which is perfect for my habits. If I go three days without using my Nook, usually it means I'm going to go a few weeks. This way, I still have a nice charged battery when I do come back.

the screensaver program on NST

I've two rooted NSTs ( https://forum.xda-developers.com/nook-touch/general/nookmanager-updated-1-2-2-t3973967 ), one has been working fine. The other, however, seems to have its screensaver malfunctioning: it turns itself on from time to time, regardless of what the timeout value is. I even tried to set timeout value to be -1 as in (https://forum.xda-developers.com/showthread.php?p=29113425#post29113425 ).
So I guess there must be something wrong in the screensaver program itself. My plan is to copy the correct screensaver program from the working NST to the malfunctioning one. But I cannot find which program manages screensaver. I tried to look in /system/bin, yet screenshot doesn't seem to be the one.
Any ideas on which program to look for?
Thanks in advance for any help.

smjohn1 said:
The other, however, seems to have its screensaver malfunctioning.
Click to expand...
Click to collapse
Well, there's "Daydream" and then there is sleep.
What happens when you just normally hit the power button when you lay your Nook down to go to bed?
Code:
# pm disable com.nook.partner/.daydream.DayDream
All that stuff is (like too much stuff) shoveled into /system/priv-app/partner.apk
Also /system/framework/android.policy.jar is involved.
I don't have a timeout, I just turn my Nook off.
There are various modifications in GlowHacks45 that you can use to make a regular cycling of sleep images.

Renate NST said:
Well, there's "Daydream" and then there is sleep.
What happens when you just normally hit the power button when you lay your Nook down to go to bed?
Click to expand...
Click to collapse
Thanks a lot. If hit the power button, then it goes to sleep normally.
Code:
# pm disable com.nook.partner/.daydream.DayDream
Click to expand...
Click to collapse
Disabling daydream seems to fix the problem. But will daydream come back after rebooting? I will see what happens after rebooting.

smjohn1 said:
Disabling daydream seems to fix the problem. But will daydream come back after rebooting?
Click to expand...
Click to collapse
No, it's off permanently (until you pm enable it).

Renate NST said:
No, it's off permanently (until you pm enable it).
Click to expand...
Click to collapse
Seems so. No problem so far ( for 5 hours now ).
Not sure why DayDream was there at the 1st place. Doesn't seem to have value.