Related
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
mattsolberg said:
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
Click to expand...
Click to collapse
check your time-out settings for screen and lock?
I have it set to time out after 10 minutes but my understanding was the screen should automatically shutoff and stay off when docked and closed. Am I wrong? Could it be a kernel issue? I'm using the Clemsyn kernel. OC'd to 1.4
mattsolberg said:
I have it set to time out after 10 minutes but my understanding was the screen should automatically shutoff and stay off when docked and closed. Am I wrong? Could it be a kernel issue? I'm using the Clemsyn kernel. OC'd to 1.4
Click to expand...
Click to collapse
In Applications -> Development. Is the option that says "Stay on when charging" turned on? That'll explain why. Since the dock is technically charging the tablet.
frosty5689 said:
In Applications -> Development. Is the option that says "Stay on when charging" turned on? That'll explain why. Since the dock is technically charging the tablet.
Click to expand...
Click to collapse
I was excited for a minute, hoped that might be it. But no, I don't have that option enabled. You're using the Netformer kernel? Maybe I will try flashing that. At worst it could rule out the kernel causing the problem.
mattsolberg said:
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
Click to expand...
Click to collapse
Check your tablet is properly docked?
The magnet under the "+=" key on the dock will turn off the screen on the tablet ONLY when the tablet is properly docked. When the tablet is loosly docked (hard to describe but has happened to me) the magnet will have no effect on the tablet screen dimming. For example, if you disconnect the tablet and dock and place a magnet over the tablet (same area above "+=" on keyboard) nothing happens.
All sorts of dock issues happen to me when I force stop services or delete data related to dock services. Nothing has recovered the dock for me, except a complete factory reset. For example, I force stopped and deleted data on three services related to android & asus keyboard and the top row of keys no longer functioned until factory reset (e.g. wireless, bluetooth, pad disable, etc. through settings key and some audio controls). This might be a related issue if you are not on stock OS/ROM.
Good luck!
my tablet is docked properly but is still got the issue that the screen turns on even when the lid is closed .. it turns off first but recovers a few seconds later ..
Mine is exactly the same--the stay awake option is not checked, the tablet is docked correctly (slider is all the way to the right), and the tablet comes on while docked and charging. However, it does charge. I haven't timed it to see how long it takes vs undocked, or docked being used. I'm running unrooted, latest updates.
Bob Smith42 said:
Check your tablet is properly docked?
The magnet under the "+=" key on the dock will turn off the screen on the tablet ONLY when the tablet is properly docked. When the tablet is loosly docked (hard to describe but has happened to me) the magnet will have no effect on the tablet screen dimming. For example, if you disconnect the tablet and dock and place a magnet over the tablet (same area above "+=" on keyboard) nothing happens.
All sorts of dock issues happen to me when I force stop services or delete data related to dock services. Nothing has recovered the dock for me, except a complete factory reset. For example, I force stopped and deleted data on three services related to android & asus keyboard and the top row of keys no longer functioned until factory reset (e.g. wireless, bluetooth, pad disable, etc. through settings key and some audio controls). This might be a related issue if you are not on stock OS/ROM.
Good luck!
Click to expand...
Click to collapse
It was exactly what happened to me! Check if the dock button go until the end. This is made by docking well, not forcing the button. After that the screen went off has supposed.
Good luck.
no .. ich checked it twice .. i can't push it harder to dock it .. the switch is all the way to the right.
Is there any known app that can handle the switching forced by opening and closing the lid ?
I think this happened to me one time and caused a huge scare.
I had been shutting the lid of the TF and putting it in it's case...and having no problems.
But one time I did that, and it came back on and got VERY HOT and ran the battery to 0%!
I got lucky and just recharged it, but now, I shut it off everytime I'm going to put it in the case...you can't trust the shut-off-feature.
Got the exact same issue, screen is initially turning off but when you fully close the lid it turns on. It's got something to do with the touchpad (for me at least), because I've got no problems at all when you turn the touchpad off!
Can you guys try this too? Just turn the touchpad off and see wether the screen will turn on or not. Might get us closer to a fix.
Gibeon said:
Got the exact same issue, screen is initially turning off but when you fully close the lid it turns on. It's got something to do with the touchpad (for me at least), because I've got no problems at all when you turn the touchpad off!
Can you guys try this too? Just turn the touchpad off and see wether the screen will turn on or not. Might get us closer to a fix.
Click to expand...
Click to collapse
Same for me, i also had the feeling that it depends on the touchpad because when you reopen it you can see the cursor somewhere on the screen. Will try it later when i'm at home! Maybe we have to use something like a script to deactivate the touchpad when closing the lid.
greetings
Awesome ! this seems to work (tested it several times now).. i think there might be a way to react to the intents fired by closing and opening the lid so we can use them to turn off the touchpad.. ill check it out later but im not that experienced in android so maybe someone wants to help
EDIT: There is a status change in LogCat made by the WindowManager. Its called notifyLidSwitchChanged but there is nothing in the log while enabling or disabling the touchpad...
Maybe this related to problem?
I killed a few application services and deleted their data, while in settings. Afterwards my dock was not working correctly, e.g. keys were disabled and other strange effects.
I copied the 3.1 update from the web to flash and re-updated but this did *not* fix the problem. Next I did a factory reset and this solved my dock problems.
Maybe your tablet is missing some ASUS control bits for the dock? If you can afford a factory reset it might help. Good luck.
I'll try, I'm rooted so I'll just nandroid and revert to stock 3.1. I'm glad the touchpad "fixes" it atleast, means we all have the same issue.
Fixed
Thanks for posting this question as I thought I was the only one experiencing this issue.
The fix for me was found when Gibeon mentioned the touch pad. Once I read that I realized that the cursor was always displayed when I would open the case. Not sure of the reason. All I have to do is turn the touch pad off and it works fine.
I will try a factory reset/data wipe when I am ready but for now this works fine for me. Perhaps there is a away to fix this in the kernel (I have used both clemsyn/blades and netformer and had the issue with both) Thanks for the info!
I made a thread about this too a few days ago, I still have this problem and it drains my dock battery in only 3-4 hours. (and that's WITHOUT using the TF at all for those 3-4 hours)
Tested on mine and it is definitely the touch pad. Thanks for the help everyone. At least we've got a work around to use until a more permanent fix is achieved.
Would tasker be able to automatically shut down touch pad when screen is closed?
Sent from my GT-I9000 using XDA App
Can you recommend an app or a mod which control wifi connection when the screen is off? I notice that if I enable wifi, I got 20% battery drop per a day, but I got 2% drop if I disabled wifi. Still, I like to have wifi on when I am using it, and clicking several time to enable wifi is quite irritating (relatively). So I thought there might be a good resolution to handle this my lazy problem.
I searched it on android market, and can find several. Can you recommend any one which will work well with NookTouch? I appreciate your inputs.
Same problem pal. But I also can't fix wifi not reconnecting when nook is up from sleep state issue. Suggestions?
I use the power widget that comes with ADW. I can turn WiFi on and off from my home screen with one tap.
Is it possible for it to be done automatically? Like on my smartphone? When wifi is turned on and my nook goes to sleep mode then when it wakes up wifi is off, in "disconnected" state.
I use the program Llama. It lets you set up all sorts of conditional changes for phones (similar to Tasker).
On my nook, I have one event trigger. When wifi turns on, Llama delays for 5 minutes, then turns wifi off.
It isn't exactly the same as turning off wifi when the screen turns off, but it helps me save battery. I currently have it send a notification to let me know it is turning off wifi, so I have the option to keep wifi on if I so choose.
Edit: Llama does have an event trigger for Screen Off, but I couldn't get it to work. Maybe the Nook doesn't turn off the screen in the way standard android phones do, so the trigger doesn't run.
Edit 2: I just realized you wanted one that turns wifi off when turning the screen of, then reconnects when turning the screen on. If Llama correctly detects the screen off/on triggers, you could set up two events, one to turn wifi off and one to turn it back on. I haven't gotten it to work, so maybe Llama isn't going to work for your particular needs.
sayno2quat said:
Edit 2: I just realized you wanted one that turns wifi off when turning the screen of, then reconnects when turning the screen on. If Llama correctly detects the screen off/on triggers, you could set up two events, one to turn wifi off and one to turn it back on. I haven't gotten it to work, so maybe Llama isn't going to work for your particular needs.
Click to expand...
Click to collapse
The NST is so heavily customized by B&N that you cannot rely on the "usual" events being triggered.
They only did what was necessary to save enough power and get the device to work and I don't blame them for that.
I'm pretty sure there's an event triggered that can be used for this particular task tho, if I get some spare time I might dig into it.
Well, I'm the impression, that my nook does that. I mean, when in sleeping mode - the WIFI is OFF. But when I awake the NOOK, wifi turns ON by it self and connect to internet. What I suspect, you might have the problem that other users experienced (including me) ... that you will have to change one file. Read more about it here.
I hope, this will help you.
Thx for all help !
Sent from my GT-I9100 using XDA App
In TorimuNooter I fixed the battery drain, pop on over to the TorimuNooter thread. The latest version (Ver 0.3) was just uploaded today!
Sent from my NOOK using XDA App
I am looking at using the nook for an application, where it would run from an uSD card and on power up would connect to a wireless router and open a web page which would update every second. The Screen saver and sleep functions need to be disabled such that all it will do is show this web page until the battery dies. I don't want to have any user input other then the power button unless that can be removed also so that the nook is always on if it has power.
I have seen that they can now run of a uSD image, so can android be configured to make the above happen?
Thanks
Been using NC with CM7 for over a year plus. Never any problems - until today. I haven't messed with any base settings for at least three months. The Nuance Swype and Dragon Trial app ran out today - the only thing that I messed with.
Was using it this afternoon on Google+ just cruising around. I put the NC down for about 20 minutes for an errand. Came back and I can't wake it up through the usual press of the "N". Long Press the N - no luck. Tap the Power button - no help. The only thing I could think to do was press and hold the Power button - nothing happened. Long press Power for about 15 seconds and I saw the screen flicker and the Cyanogen Mod green icon appear - like a normal start up. So the desktop arrives and I note that the Wi-Fi is turned off. Usually I have it set to autoconnect to my house router which it has faithfully done since forever. But Wi-Fi is turned off. I clicked it on and after a brief moment I see "Connecting..." up at the top of Wi-Fi Settings but every Access Point including the house router is "Not in Range". Eventually "Connecting..." turns into "Disconnected". Turn Wi-Fi off and then back on. No difference. I think that whatever caused the blowout earlier this afternoon has left the NC wi-fi system in some sort of in-between state.
Later on as I was working with this, I got up to answer the phone, came back and it's shut off again. I was able to re-engage it twice more after pressing this n' that trying to wake the Wi-Fi up. Once engaged it's fine. But as soon as you power down (or it blows up like earlier), Wi-Fi is disonnected, turned off and very hard to re-establish. Incidentally, all other Android devices, tablet, phones in the house off that router work just fine so I don't think it's a matter of a router issue.
Question: Is there a way to "reset" the Wi-Fi functions in the NC? I'm thinking some sort of hard reset is needed but I'm not sure.
Question: What would be my next step to figure out what is causing the unwanted shut down?
Thanks folks. If you need more info, I'm going to be around and will stay on top of this thread.
Hoibb
First that 'unwanted shutdown' is called SOD, Screen of Death. Very common with some devices and combination of apps. Do a little searching on that and you will get overwhelmed with info. Since you were not having it before, it must have something to do with that app or apps that you had to adjust recently. It is tied in with deep sleep and wifi.
Have you tried just forgetting the routers in your wifi list?
Edit: I just reread your post. How long have you had Google + installed? Did you recently just update that?
Edit2: Fortunately, for CM7 there is a patch that fixes SOD. If you want it, I can post a link.
Edit3: Here. Flash this with CWM. It will replace your wifi driver with a patched one that resists SOD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thank you and...
Lots of good information here. Google+ has been installed for at leat 6-9 months that I can recall. I could uninstall and reinstall, I guess. But...
It's seemed to have righted itself two days ago, so I haven't had a problem - until...
Last evening. I was doing some eMail using K-9 plus floating through Google+. And I put it down to go do something. Came back and it's still working (pulled up the desktop by clicking the "N") but the Wi-Fi is shut off again. Went to Wireless and Network Settings and what I see is "Wi-Fi" sitting on the words "Turning off...". Everything beneath it is greyed out. Decided to just leave it and see. Half hour or so later, it's still in a state of "Turning off...". I backed all the way out and did a restart. On restart, Wi-Fi is turned off so I hit the box to turn it on, it obeyed and went directly to my home router, signed in and I'm back on again.
As the evening progressed, what I got in the habit of doing is short-pressing the Power button to turn off the screen. I found I could reliably come back, wake it up and the Wi-Fi would start back up again on its own without intervention.
So until I get a chance to sort out all the stuff you gave me to do/patch, I'll try to just manually "sleep" the system. I have to study up more on what you said because the terminology and procedures, while probably very clear to most, are not exactly clear to me.
Thanks again for the info.
Hoib
leapinlar said:
First that 'unwanted shutdown' is called SOD, Screen of Death. Very common with some devices and combination of apps. Do a little searching on that and you will get overwhelmed with info. Since you were not having it before, it must have something to do with that app or apps that you had to adjust recently. It is tied in with deep sleep and wifi.
Have you tried just forgetting the routers in your wifi list?
Edit: I just reread your post. How long have you had Google + installed? Did you recently just update that?
Edit2: Fortunately, for CM7 there is a patch that fixes SOD. If you want it, I can post a link.
Edit3: Here. Flash this with CWM. It will replace your wifi driver with a patched one that resists SOD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
@leapin. I should have come back to post add info. My apologies. I believe I was able to resolve this a bit later. I looked at Juice Defender (free) and what it does. I uninstalled it. As soon as I did that, I suffered no more of these SOD problems. Been running great since June.
So was this the real SOD? Or was it Juice Defender setting the power profile in such a way that the Wi-Fi never got the signal to reawaken? What do you think?
Hoibb
Hoibb said:
@leapin. I should have come back to post add info. My apologies. I believe I was able to resolve this a bit later. I looked at Juice Defender (free) and what it does. I uninstalled it. As soon as I did that, I suffered no more of these SOD problems. Been running great since June.
So was this the real SOD? Or was it Juice Defender setting the power profile in such a way that the Wi-Fi never got the signal to reawaken? What do you think?
Hoibb
Click to expand...
Click to collapse
It could have been the real SOD being triggered by Juice Defender. Usually it is some app that triggers it (trying to use wifi while the device is in deep sleep), but the underlying problem is SOD. Some folks never experience an SOD.
Sent from my Nook HD+ running CM10.1 on emmc.
I have a couple of questions about my grandpa's Nook. We got him a new card and I have been able to get it to work. It wasn't as easy as it reads to be.
I can't get the wireless to stay set to turn on. When you shut down the Nook and then start it again later, you have to go into settings and turn on the WiFi. But if it goes into sleep most of the time it will turn back on and only once in a while stays off. I have looked through the settings and tried changing some of them, but none have worked so far.
It has a 8GB SD card that we got the cyanogen on. It says it only has 1 gb of storage when you check it in cyanogen. Can I make this larger? Can I put a movie in for Grandpa and get it to play? How do I do this?
iam12 said:
I have a couple of questions about my grandpa's Nook. We got him a new card and I have been able to get it to work. It wasn't as easy as it reads to be.
I can't get the wireless to stay set to turn on. When you shut down the Nook and then start it again later, you have to go into settings and turn on the WiFi. But if it goes into sleep most of the time it will turn back on and only once in a while stays off. I have looked through the settings and tried changing some of them, but none have worked so far.
It has a 8GB SD card that we got the cyanogen on. It says it only has 1 gb of storage when you check it in cyanogen. Can I make this larger? Can I put a movie in for Grandpa and get it to play? How do I do this?
Click to expand...
Click to collapse
I also had this problem. It is easily solved. From the CM7.2 MiRaGe thread:
http://forum.xda-developers.com/showpost.php?p=28185635&postcount=1470