Guest No Expert Posted November 9, 2010 Report Posted November 9, 2010 I see some of you are using myLock to avoid having to press the power button to wake the device. My experience with myLock has been that it kills the battery as it does not allow the device to properly sleep. This means that the battery drains extremely quickly.
Guest Bob@Desire Posted November 15, 2010 Report Posted November 15, 2010 Is it possible to create a flashable .zip file with the remapped key (Home or Menu) like this http://forum.xda-developers.com/showthread.php?t=683902
Guest meinnit Posted November 15, 2010 Report Posted November 15, 2010 (edited) Is it possible to create a flashable .zip file with the remapped key (Home or Menu) like this http://forum.xda-developers.com/showthread.php?t=683902 Remapping doesn't seem to fix the issue I should add that I didn't clear my dalvik cache when I applied the changes. Edited November 15, 2010 by meinnit
Guest buneech Posted November 15, 2010 Report Posted November 15, 2010 No, it doesn't fix the issue, because the keymap is set to wake the phone with any key, but it does so only while on AC. It's probably somewhere hidden in the kernel.
Guest RussellD Posted November 17, 2010 Report Posted November 17, 2010 Just upgraded to 2.2 and I'm still having problems with the power button so it must be hardware rather than a software issue. I think I'll have to give Orange a call soon and see if I can get a replacement. Anyone had any dealings with Orange customer services, will I run into any problems with the phone being rooted?
Guest oh!dougal Posted November 17, 2010 Report Posted November 17, 2010 Here is a list of the values for keys on the blade 102 HOME 115 VOLUME_UP 114 VOLUME_DOWN 139 MENU 142 POWER 158 BACK 330 SCREEN_TAP and in a stock 2.1 rom: 7k_handset.kl key 226 HEADSETHOOK WAKE #key 116 ZTE_EXTEND_1 WAKE_DROPPED #key 142 ZTE_EXTEND_1 WAKE_DROPPED # ZTE_KL_HLP_002 ,2009-12-5 #key 143 ZTE_EXTEND_3 WAKE_DROPPED # ZTE_KL_ZB_001 ,2010_02_04 # ZTE_KL_HLP_002,2010-3-3 #ZTE_KL_LYJ_001, 20100712 #key 116 POWER WAKE_DROPPED key 142 POWER WAKE_DROPPED key 143 ENDCALL WAKE_DROPPED <...> Ummm. Note that Key 226 "HEADSETHOOK" is assigned the action of "Wake" in the standard rom. However, the headset button/switch (which does answer and end calls properly) does NOT wake the phone from sleep (real sleep). It does not even wake the screen when only that is off (as when on the charger/usb).
Guest papa-nundo Posted November 28, 2010 Report Posted November 28, 2010 Hi, I am a complete newby, but I have the following idea: Whether the HOME button works to wake up the OSF depends on the tasks / programs running when the phone is in sleep mode. If this is true, the interesting question is: Which task makes the HOME button work and does not drain the battery? Does this make any sense to all you experts out there? Thanks, -- Papa-Nundo.
Guest targetbsp Posted November 28, 2010 Report Posted November 28, 2010 Which task makes the HOME button work and does not drain the battery? Unfortunately, tasks that stop the phone sleeping and therefore drain the battery by definition. It's not that certain tasks say 'lets make this button work'. It's that certain tasks keep the phone awake and when the phone is awake the buttons work.
Guest oh!dougal Posted November 28, 2010 Report Posted November 28, 2010 Which task makes the HOME button work and does not drain the battery? ... At present, the only way to 'activate' those buttons is by bringing the whole phone out of sleep. A task/program can do that. Its not a question of how much power the task itself uses, but the fact that any keep-awake task must wake (or keep awake) the whole phone (except the screen and the proximity, light and touch sensors). Power is used by the whole (awake) phone, not merely by the keep-awake task. ZTE have been contacted about the strangely all-or-nothing sleep behaviour, which principally gives a problem with wifi. However, it has proved difficult to communicate the details to them. A proper response is still awaited.
Guest papa-nundo Posted November 28, 2010 Report Posted November 28, 2010 Its not a question of how much power the task itself uses, but the fact that any keep-awake task must wake (or keep awake) the whole phone (except the screen and the proximity, light and touch sensors). Power is used by the whole (awake) phone, not merely by the keep-awake task. It seems to me the phone is never *completely* sleeping, right? Because it is always expected to receive a phone call. So this means from my naive point of view: I just have to "keep awake" another task that makes sure the HOME button is cared for. -- Papa-Nundo.
Guest oh!dougal Posted November 28, 2010 Report Posted November 28, 2010 (edited) It seems to me the phone is never *completely* sleeping, right? Because it is always expected to receive a phone call. So this means from my naive point of view: I just have to "keep awake" another task that makes sure the HOME button is cared for. Not really. Its not about the software definition of the keys that ought to wake it. That is described in the quoted section of my post in this thread on 17 Nov. Its about connecting the Home button to anything that's listening when the phone is in sleep. The problem is that when the computer part of the SF/Blade is in sleep, there is no power to the module containing the Home button. Or to the wifi. Of course the cell-radio is still powered and listening for calls. When it gets a call, its first job is going to be to wake the computer. When the computer is woken, the computer turns on the power to the other modules. If ZTE can be made to recognise that the Notification LED is 'broken', and they fix it so that it does notify even when asleep, that would mean that there was power to the switch module, and I expect that, with power to the module, you could (if you really wanted to) reconfigure the software so that Home would wake it. At present, the only reason that the front buttons appear to "wake" the phone when its on charge (or playing music, whatever) is because the phone is not really asleep -- the computer is fully awake, wifi has power, and its only the screen and its sensors that are turned off. You can run software that will keep the SF/Blade in that state - but it means the battery is drained relatively quickly. But the hardware control of power to the switch/led module does seem to be only for ZTE to fix. And they need to to fix the power to that module to fix the Notification led. Edited November 28, 2010 by oh!dougal
Guest mess17 Posted January 11, 2011 Report Posted January 11, 2011 I dont have a custom rom, i havent rooted my phone but my home, menu and back keys can unlock the screen on one press, allbeit rather sporadically. They work to unlock the screen more often than not but im wondering whether this is because the phone is not sleeping properly but i dont know how to check this. Any ideas would be helpful, although by the look of the response on this thread many of you would envy my situation lol
Guest oh!dougal Posted January 11, 2011 Report Posted January 11, 2011 I dont have a custom rom, i havent rooted my phone but my home, menu and back keys can unlock the screen on one press, allbeit rather sporadically. They work to unlock the screen more often than not but im wondering whether this is because the phone is not sleeping properly but i dont know how to check this. Any ideas would be helpful, although by the look of the response on this thread many of you would envy my situation lol You are pressing the buttons either when the phone is on charge or there is an app running that prevents sleep. In both cases the phone only screen saves. When it goes to sleep normally, its actually in screen save for the first few (five?) seconds.
Guest avenn Posted January 20, 2012 Report Posted January 20, 2012 Wake All in the android Market does exactly what you need without any other changes to your unlockscreen.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now