I am getting ready to, next weekend, finalize my build and install my Galaxy Tab 2 in my car as my main infotainment system... I have it set so you sadly will not have access to the power button, however it is wired to an ignition power circuit w/ a usb charger. So, this means that when the car turns on, the tablet powers up. Developer options set to never turn off while charging, so essentially my tablet will stay on while driving or when the key is on. Here's my concern... when you key on, you have about 10 seconds to swipe and open this thing otherwise it goes back off normally. Technically it is charging, so it may stay on (have not yet tested this as I just thought of it... lil slow today lol) but in the event it does not, can I change the delay when powered on to unlock to like, 60 seconds?? Tablet is stock, but rooted... Thanks!
It can be done with Tasker+secure settings plugin
Search in google "Tasker – How to Unlock Your Screen", with this guide you create the task , then you just have to create the tasker context that will trigger it, a simple "power any" context.
Double tapping the screen to wake is one of the options you get with Tasker.
Pp.
Related
Hello
How does ont turn off the XDA EXEC, i dont see any off button. the power button just turns the screen backlight on and off.
the reason why i wanted to know what it was is because i am porting my number across networks, and 02 told me to turn off my phone a number of times during the day, so that it could go into a boot up process.
There is no real way to trurn the device off, but what they will be wanting you to do is disable the phone section (do this by turning on flight mode, or by clicking on the green connections manager in the bottom and click on the phone button. Click the phone button again to turn it on.)
Start -> Programs - Wireless Manager -> All Off (This switches of the phone.
Then use the phone on/off button at the top of the screen there, to switch it back on and force your SIM to re-register with the network, which should have the desired effect your after.
Taking out the battery is the only real 'off' button.
thanks for the replies dudes
did you try holding the power button as well? that works on my wizard
not sure if it's true for all wm5 though
i held the power down button for some time and it blanked teh screen. when i held the power button again for a few seconds the screen came back to life, but this time there is no "back light(?)"
how do i get back the "back light(?)"
i held the power down button for some time and it blanked teh screen. when i held the power button again for a few seconds the screen came back to life, but this time there is no "back light(?)"
how do i get back the "back light(?)"
There remains a bug, it seems, that sometimes prevents the backlight from firing up when starting the device.
It used to happen on my XDA2i and still happens on my Exec.
I usually have to get it in a good light and go to settings and move the brightness slider to get it working.
Turning off the device, I find, is actually achieved by pressing the power switch before closing lid.
I find I get much more out of each charge if I do this rather than just close the lid.
That of course turns of the PDA functionality of the device. The radio (phone) service is still disabled via Flight Mode.
:wink:
somehow i double posted...sry
thanks for the reply
i guess by pressing the power button, the pda goes ito some sort of sleep mode, since it does not boot up later, correct?
when it is charging up using a usb cable connected to my pc, the backlight is turned of, and no amount of pressing buttons seems to turn on the backlight, is that correct?
i checked out the brightness level sliders, there are 2, the
1. on battery which is somewhere in between
2. on power which is "slided" to the left, is that its correct position?
you will probably find it will selfboot at midnight.. this appears to have been intentional in the design of all the XDA's.
Thia can be a nuisance but it is probably to do with reseting timers. alarms etc
The backlight is configured to be on/off during external power and on battery in which ever setup you choose.
The actual levels you set it at are your choice ..
I set mine to be off after 5 mins on external power i.e. when charging except when i use tomtom and want it to stay on whilst externally powered.
On these occasions I change the setting before the journey
Your original question with reference to O2 making changes that required you phone to be off, in my experience, means not having the O2 sim in the device.
thanks for the reply dude
i think my questions have exceeded the remit of this thread. i will start another thread for the backlight questions
How to configure button power for only turn screen off, dont suspend???? Because my device have issues with GSM when in suspend mode.
.................
..........................
Aren't you confusing something?
* On: The user is interacting with the device. Everything is on.
* BacklightOff: There has been a brief period of user inactivity (no one has pressed any buttons or touched a touchscreen). The backlight has been turned off, but everything else is on. When you set the backlight timeout values in the control panel, you're setting how long the system should wait before going into this state. (Note that this state is new for WM 5.)
* UserIdle: There has been a longer period of user inactivity. Both the backlight and LCD have been turned off. When you set the screen timeout value on a Smartphone control panel, you're setting how long the system should wait before going into this state. This state is generally not used on PocketPC. There's no reason to turn the screen off when the device is about to go to sleep (sleeping turns the screen off). However, if/when PocketPCs go to the "Always On" model, they'll start using this state.
* ScreenOff: You go into this state when someone specifically says to turn the screen (and backlight) off. For instance, in Media Player you can assign a button to turn the screen off. When you press it, we go into this state. This state is different than UserIdle, though. This state says, "The user wants the screen off and doesn't want it to turn back on." UserIdle says, "The user hasn't touched any buttons in a while, so we might as well turn the screen off to save power." In ScreenOff, pressing a button (other than the power button) doesn't turn the screen back on. In UserIdle, pressing a button does turn the screen back on. Both PocketPC and Smartphone use this state.
* Unattended: This is a confusing state in which the screen, the backlight, and the audio are off. I won't go into too many details, other than to say that this is a PocketPC-only state that is used by applications which need to do things without alerting the user. While the PocketPC is in this state, the user thinks the device is asleep. For instance, ActiveSync when it syncs every 5 minutes. It's waking up, syncing, and going back to sleep, but the user can't tell.
* Resuming: This is the state the PocketPC goes into when it wakes up from sleep. In this state, the screen is off, and there is a very short (15 second) timer before it goes back to sleep. The only way to keep the device from going back to sleep is to have something put it into one of the other states. This is really for dealing with spurious wakeups and for giving the system a way to get into Unattended without letting the user know about it.
* Suspended: This is the PocketPC "Sleep" state. Everything is off, and the system isn't going to wake back up until some piece of hardware wakes it up. It's not actually an official Power Manager state, the way the other six are, but I'm including it for completeness.
Click to expand...
Click to collapse
from here: http://blogs.msdn.com/windowsmobile/archive/2005/08/10/450186.aspx
When you hit power button once, you go to Screen Off (Sleep). Suspended is when your device 'completely' off.
Just over the past 2 days my GTab would go to sleep and refuse to wake up. Hitting the volume rocker did not wake it up and neither did hittng the power button. So I set the screen timer to never and set it in my Malata dock and had it sitting there running clock. After 2 or so hrs. (was not in the room) tab shut itself down.
Took about 30 min of hitting the volume and power button repeatedly before it decided to reboot.
Is this something to be concerned about? is my tab about to brick itself? It just happened all of sudden and I was caught of guard.
I have been running TnT lite 4.2 since purchase with no issue outside of market. Now all of sudden this.
Should I roll the rom back to stock and start over? or is there something I need to be looking at?
I know I can adjust the screen timer, but is there an actual "sleep" setting I can adjust?
machine73 said:
Just over the past 2 days my GTab would go to sleep and refuse to wake up. Hitting the volume rocker did not wake it up and neither did hittng the power button. So I set the screen timer to never and set it in my Malata dock and had it sitting there running clock. After 2 or so hrs. (was not in the room) tab shut itself down.
Took about 30 min of hitting the volume and power button repeatedly before it decided to reboot.
Is this something to be concerned about? is my tab about to brick itself? It just happened all of sudden and I was caught of guard.
I have been running TnT lite 4.2 since purchase with no issue outside of market. Now all of sudden this.
Should I roll the rom back to stock and start over? or is there something I need to be looking at?
I know I can adjust the screen timer, but is there an actual "sleep" setting I can adjust?
Click to expand...
Click to collapse
Hey, I don't know if this might help. I read this on the Nvidia dev. page a while back concerning the Tegra 250 & Tango board which is what I believe we have in the G Tablet (I could be wrong!)
"Due to a problem with the battery charge controller on some Tango units, you must charge the battery ever 2-3 weeks. If you find that the battery is plugged into the charger but remains at <7% charge, please try charging the battery for 6-12 hours. If the battery remains at <7%, please contact NVIDIA as the battery needs to be replaced.
In certain power saving configurations, touching the screen or "Android buttons" at the top of the device is not adequate to wake the device. To work around this, try inserting or ejecting the SD Card to wake the device. Failing that, you will need to reset or power cycle the Tango. Alternatively, please set the screen timeout to 30 minutes (Menu->Settings->Display->Screen Timeout)."
I have no idea if this will help, but hopefully it will.
Good Luck.
Thanx for that info. I did try pulled the SD card thinking that might force it to reboot, but it did nothing. The unit was is in fact shut down, not sleeping. It took alot of button pushing to get the unit power on. Now that it's up and running again, I have gone through all the sleep settings and it still happens. The longer I let it sleep, the more likely it shuts itself down.
Gonna call viewsonic today and see if I can get any help from their and.
Whats up XDA.
So I have a galaxy tab sch-i800 running on cyanogenmod 9. I plan to fit my tablet into the dashboard of my car. I have everything worked out except how I'm going to turn it on and off. since I won't be able to access the power button I need a way for it to power on/off by its self, that way its not occasionally dead when I start my car.
At first I planed to use tasker to turn the tablet on when plugged in (or when I start my car, it turns on). and then turn off after an hour of inactivity (or an hour after I've turned off my car).
But now that I'm looking at tasker it won't let me use the command "turn on" (even though I'm rooted) and I don't see a turn off command.
Is there any apps out there that can help do exactly what I want?
I have noticed that 4.2 and higher automatically boots the device when it is plugged in, I'm on 4.0, would upgrading screw up cyanogenmod?
Thanks!
So, I need to know which Kernel or app or anything I need to take my Galaxy Tab 2 7.0 - STOCK - but rooted and make the knock knock feature work like the LG phones have. Installing this in the dash and since there is no front button, turning this on my be a pain in the rear...
Actually, I may have answered my own problem... I am installing this tablet in a custom mount and using it for my car as the main source of audio/video/nav. Since there is no home button, I originally wanted the knock knock wake function, but in researching this it seems that it works on certain kernels (that are not compatible with this device) and it also drains the heck out of the battery... So let me run this by everyone who may have input and see if it makes sense. To me, it does, but I may be underthinking the solution...
The OTG connector will be home to a hub that has one input (for power) and two outputs (for expansion). I am going to have the USB power input hooked up to the USB power in my center console, which only has power when ignition is ON. So, my thought is this. The tablet will not have power when ignition is off, but when you key on the USB will have power and thus will charge the tablet. On charge, it should WAKE, yes? The dev option for STAY AWAKE will be used to, when charging, always stay on... then the 1 minute time out option will turn the screen off shortly after ignition is off.
Make sense? Should work?