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();
}
Related
EDIT: updated with step-by-step instructions.
Step 1. Download the Android SDK (http://developer.android.com/sdk/)
Step 2. Make sure to configure the ADB usb interface drivers (search the forums for more information on this if you're confused.)
Step 3. Plug your G1 into your computer (via usb). (Settings -> Application -> Development -> USB Debugging, must be enabled [it is enabled by default in JesusFreke releases i think])
Step 4. Open command prompt and enter the following:
Code:
> adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
Step 5. Now power off the phone, and turn it back on. Tada! No more pattern lock.
Sorry, Im speaking on behalf of the simpler folk, but how exactly do you go about doing this, and if so can you make an update.zip that would do this?
hey haykuro, probably you should post this in the development sub-forums..
anyways great stuff man..the code looks so simple lol..i am sure you toiled hard tho!
thanks again.
Joeriginal said:
Sorry, Im speaking on behalf of the simpler folk, but how exactly do you go about doing this, and if so can you make an update.zip that would do this?
Click to expand...
Click to collapse
None of this is done on the phone itself. It's done using the adb utility for your computer. Just download the adb.exe file and the USB drivers then repeat the commands shown above at your command prompt.
whats the point of this?
The Great NY said:
whats the point of this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=485903
Yay! Now I can finally use that stolen G1!
J/k I already got rid of the previous owner's account by flashing DREAIMG.NBH
(No, I did not really steal a G1 )
interesting to know
thx.
Could be useful if you forget your own pattern Maybe we can remove the regular lock screen now?
As a follow-up, how difficult would it be to replace the regular lock screen with a different one (non-pattern based)? I struggle with the pattern one, because it's pretty easy for anybody to hold the phone up to the light to see the pattern. Would be useful to have a different, more secure lock screen.
That would be awsome if you could get rid of the first unlock with hitting menu
ICBM said:
As a follow-up, how difficult would it be to replace the regular lock screen with a different one (non-pattern based)? I struggle with the pattern one, because it's pretty easy for anybody to hold the phone up to the light to see the pattern. Would be useful to have a different, more secure lock screen.
Click to expand...
Click to collapse
what the hell are you talking about? hold the phone up to the light to see a DIGITAL screen unlock pattern? maybe if you leave giant greasy fingerprints all over the screen...
Yes that's exactly right. The low-tech, looks at the fingerprint pattern works like a charm. Don't believe me? Try it yourself. I don't consider myself particularly greasy, but if you use the G1 as is, without screen covers or anything, you can usually see enough to figure out what the unlock pattern is.
cboy007 said:
what the hell are you talking about? hold the phone up to the light to see a DIGITAL screen unlock pattern? maybe if you leave giant greasy fingerprints all over the screen...
Click to expand...
Click to collapse
That's what he meant. And it's very plausible to do, even if your fingers are a little greasy. Try it.
This is nothing revolutionary. All you are doing here is hitting the "Require pattern" switch to off, just doing it the more "intrusive" method.
This is not any sort of insight to replacing the lock activity.
as far as that goes, you'd have to completely rebuild the OS.
Code:
>adb shell logcat -d V | grep -i lock
D/KeyguardViewMediator( 54): wakeWhenReadyLocked(82)
D/KeyguardViewMediator( 54): pokeWakelock(10000)
D/KeyguardViewMediator( 54): pokeWakelock(7000)
D/KeyguardViewMediator( 54): pokeWakelock(10000)
D/KeyguardViewMediator( 54): pokeWakelock(5000)
D/KeyguardViewMediator( 54): pokeWakelock(7000)
this is the action of turning on the screen.
for further information on REPLACING the lock screen you can follow up in this thread http://groups.google.com/group/andr...b512cb203b/8324f7ff7ed232b3?#8324f7ff7ed232b3 (this is just one of the many i googled up.)
yea.. another issue with the lock is that as it may be confusing and magical to a non G1 user.. but i tell you.. .. if a g1 user sees you put your code in... its easily retained to the "allready used it, understand how it works" mind.
two things: since you enter an adb shell does this mean you can do this from a terminal on the phone?
also, cool thing i found,
first you need to have an unlock code set
then you need to have mybackup from the market,
create a backup up of your system settings
do a wipe/factory reset (i dont know if you had to but thats what i did when it happened to me)
now restore your system settings
now you will have an unlock screen that opens with ANY pattern even if its only one dot
haitiankid4lyf said:
two things: since you enter an adb shell does this mean you can do this from a terminal on the phone?
Click to expand...
Click to collapse
yes. but if you are on the terminal of the phone, i'd guess you wouldn't need to bypass the lock screen now would you?
haitiankid4lyf said:
also, cool thing i found,
first you need to have an unlock code set
then you need to have mybackup from the market,
create a backup up of your system settings
do a wipe/factory reset (i dont know if you had to but thats what i did when it happened to me)
now restore your system settings
now you will have an unlock screen that opens with ANY pattern even if its only one dot
Click to expand...
Click to collapse
cool
i got a quick question, if the phone is locked out how do u get into the settings to turn on usb debugging
wesgarner said:
i got a quick question, if the phone is locked out how do u get into the settings to turn on usb debugging
Click to expand...
Click to collapse
haykuro said:
Step 3. Plug your G1 into your computer (via usb). (Settings -> Application -> Development -> USB Debugging, must be enabled [it is enabled by default in JesusFreke releases i think])
Click to expand...
Click to collapse
Just update the phone using JF v1.42 update.zip and you should be good to go
Is it possible to completely disable the automatic activation of the screensaver? I don't see it in settings, the longest interval for this to happen is 1 hour, but no option to disable it completely. I already installed the No Lock app, but this only helped me to get rid of the slide to unlock screen. Thank you for any ideas.
Martin
Martin2603 said:
Is it possible to completely disable the automatic activation of the screensaver? I don't see it in settings, the longest interval for this to happen is 1 hour, but no option to disable it completely. I already installed the No Lock app, but this only helped me to get rid of the slide to unlock screen. Thank you for any ideas.
Martin
Click to expand...
Click to collapse
All settings are here:
http://developer.android.com/reference/android/provider/Settings.System.html
In you case you'll need:
adb shell
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
-- check current value
select * from system where name='screen_off_timeout';
120000 - 2 min
3600000 - 1 hour
2147483647 = 596.5 hours
-- set
update system set value='2147483647' where name='screen_off_timeout';
.q
^d
or you can pull/mod/push alternatively.
Won't disabling the screensaver keep the screen and IR sensors active, thus eating up battery life significantly when not in use?
I know some folks would like to get rid of the swipe, waking up on a screen tap (mostly for accessibility issues), but I think some sort of screen (actually, battery) saver is still important.
Great link, ApokrifX. Would you happen to know if WIFI_SLEEP_POLICY does anything on the NST? I use Tasker to shut wifi off when the screen goes off, but I wonder if that might be easier?
bobstro said:
Great link, ApokrifX. Would you happen to know if WIFI_SLEEP_POLICY does anything on the NST? I use Tasker to shut wifi off when the screen goes off, but I wonder if that might be easier?
Click to expand...
Click to collapse
No idea.
I bet, it won't work...
Try and let us know?
ApokrifX said:
No idea.
I bet, it won't work...
Try and let us know?
Click to expand...
Click to collapse
I need to find a program that will let me know when wifi is on or off relative to the screen. On other devices, I can see that info in the battery status, but I'm not finding a similar option for the NST.
I *did* find a little program that would toggle it, but the NST lasts so long on battery, it's hard to tell if it's making any difference.
Actually, to disable the screensaver completely:
Code:
update system set value=-1 where name='screen_off_timeout';
I haven't found a way to disable the keyguard yet, but if you have one of the side keys set as Menu that dismisses the keyguard.
Renate NST said:
Actually, to disable the screensaver completely:
Code:
update system set value=-1 where name='screen_off_timeout';
Click to expand...
Click to collapse
Hi Renate again ( you adviced me with manual time set in NST
http://forum.xda-developers.com/showthread.php?p=30560605#post30560605, thanks).
I like the tweak (to disable the screensaver completely) also. But not understanding how to do this in internal terminal. Not shell and not busybox know the sqlite3 app and update command?
I fixed it so:
you must install SQLite3 to the NST you can just push it to the device. [unzip sqlite3 (push to n2e).zip]
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push sqlite3 /system/bin
download it from here:
http://forum.xda-developers.com/showpost.php?p=14747007&postcount=2
bobstro said:
Won't disabling the screensaver keep the screen and IR sensors active, thus eating up battery life significantly when not in use?
Click to expand...
Click to collapse
This makes a lot of sense... it explains my battery drain when the screen gets stuck on the "drag to unlock your NOOK" page after a reboot. Basically you have to make sure the Nook really goes to sleep.
Disabling the IR sensors and wifi are then the key to long battery life on the NST.
For anyone trying this technique: I used the pull/mod/push approach and Renate's recommendation of a -1 value, and everything seems to be working well, but I had to powercyle (power down, then power up) my Nook to get the change to take effect.
Call me a bit old fashioned, but I have a specific set of "keybinds" that I always work to achieve one way or another on my android devices.
The "Menu" button of old is more important to me than a "Recents" button - really just hoping to achieve inverted behavior of the square button: short press for menu, long press for recents.
Long pressing the "Back" button should kill the foreground app.
Any other bind to quickly toggle the torch light.
Using the menus in OxygenOS, I can't seem to achieve this. Any suggestions or secrets I've yet to find out about?
In Oxygen os you can set LONG PRESS RECENT BUTTON to perform MENU Action. I use it all the time.
About long press back button to kill app, I think this feature was removed in PIE.
Me too was looking for it but didn't find a solution.
Anyway I quickly realized that I don't need it. Op6t can keep a lot of app in memory so there's no need to kill.
When i want to kill one or all i use Recents.
Not a big deal for me.
Yep that's how I'm using everything now. It gets the job done, though I find myself reverting to old habits absent-mindedly. I'm sure I'll be perfectly adapted in a matter of days.
bigcc32 said:
Call me a bit old fashioned, but I have a specific set of "keybinds" that I always work to achieve one way or another on my android devices.
The "Menu" button of old is more important to me than a "Recents" button - really just hoping to achieve inverted behavior of the square button: short press for menu, long press for recents.
Long pressing the "Back" button should kill the foreground app.
Any other bind to quickly toggle the torch light.
Using the menus in OxygenOS, I can't seem to achieve this. Any suggestions or secrets I've yet to find out about?
Click to expand...
Click to collapse
Try this app: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
dannejanne said:
Try this app: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Click to expand...
Click to collapse
Permissions granted using root. It won't get past the compatibility check (The screen says "If you don't see anything your device is incompatible," and I certainly dont see anything). Thanks for the suggestion, though.
bigcc32 said:
Permissions granted using root. It won't get past the compatibility check (The screen says "If you don't see anything your device is incompatible," and I certainly dont see anything). Thanks for the suggestion, though.
Click to expand...
Click to collapse
It can be granted access with ADB (PC). It should work I've had it work even on LG phones and such.
dannejanne said:
It can be granted access with ADB (PC). It should work I've had it work even on LG phones and such.
Click to expand...
Click to collapse
I don't think the permissions are the problem. The app doesn't complain about that, it just doesn't do anything to the nav bar during setup, and according to the app that's indicative of incompatibility.
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.
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.