Database Users

How long does it take to your tytn to wake up?

Hello
My tytn require a quite large amount of time to wake up and I was wondering if I was the only one in this case.
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.
The virtual keyboard used for inputing the code is also getting on my nerv; most of the time it start with the landscape layout (without any reason) and it take 2 sec to adjust to the portrait layout; during that time it is hard for me to input my code correctly because the size of the key is changing.
So, 2-4 seconds for waking up plus 2 seconds for keyboard adjustement is in my opinion quite slow. Am I the only one experiencing this? Are there fixes out there?
I also have some trouble with notification; it wake the device up! If the device is not password protected (only after 15 minutes on my phone) it start most of the time PIE (because of the hardware button). All this lead so to my second question: Is there a way not to wake up the device (at least the input) in order to avoid unwanted press on the hardwares buttons.
Thank you in advance !

fun_key said:
Is there a way not to wake up the device (at least the input) in order to avoid unwanted press on the hardwares buttons.
Click to expand...
Click to collapse
Settings -> System -> Key Lock -> When device is off: "Lock all buttons except Power button"

Thanks for your fast answer, i ll give a try!
Concerning the screen orientation issue I found out that it is related to the HTC case magnet.
EDIT:
In fact it was already configured like this; the device is not waked up by the hardware buttons, but by the notifications.

if you use the key lock you can avoid unwanted key presses. As for wake up times. I don't think anyone who has this device wants to admit that it takes to long cause they paid sooo much for it. However, I will admit that it does take a long time to wake up. I am comfortable saying this because its much like a turbo car, at first its not as fast as most naturally aspirated cars (turbo lag), then it blows their doors off. So it takes a couple seconds to wake up, then its faster then most other devices.
Later, Lew

Agreed. Coming from standby I get two rings of the "Old Phone" ringtone before it goes to voice mail.

I am hoping that new firmware will resolve this issue - my wizard was certainly more responsive when i presses the poer button to bring it out of standby. This is furthur delayed by the fact that i keep scabbling around the top of the device for the power button insted of the side!

pof said:
Settings -> System -> Key Lock -> When device is off: "Lock all buttons except Power button"
Click to expand...
Click to collapse
This doesn't help with the particular problem. What I think fun_key is trying to say is that whenever he gets a notification (for example when he gets a new sms message or a notification for a meeting) the phone will come out of sleep mode, so the key lock setting for "when device is off" won't be in effect. Instead the device will be powered up and accepting all keypresses, like the IE / Messaging- buttons, not to mention any presses on the screen.
I too find this annoying, and wish there was a way to make the phone go back to sleep after showing me a notification, instead of waiting for the default sleep time to go by. There are programs out there that have this functionality (for example MortSaver) though, so my advice would be to use those.
- Pud.0

thank for the mortsaver ip; i ll give a try!

Have exactly the same problems as fun_key (power button, keyboard in landscape, etc), and I suspect most of other people do. The wizard was definitely more responsive.

fun_key said:
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.QUOTE]
I've found a solution to the problem regarding the length of time before a call is missed (this is probably known by most people, I only found it after tinkering with the settings):
Start>Settings>Phone>Services(Tab). Choose Call Forwarding in the list, then click Get Settings. Change the 'Forward After' setting to a higher number. I changed mine to 25 seconds. Problem solved for me!
Click to expand...
Click to collapse

g00nerz said:
fun_key said:
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.QUOTE]
I've found a solution to the problem regarding the length of time before a call is missed (this is probably known by most people, I only found it after tinkering with the settings):
Start>Settings>Phone>Services(Tab). Choose Call Forwarding in the list, then click Get Settings. Change the 'Forward After' setting to a higher number. I changed mine to 25 seconds. Problem solved for me!
Click to expand...
Click to collapse
Glad your problem is solved. Perhaps others may find the following of note as well as your solution above:
http://forum.xda-developers.com/archive/index.php/t-258109.html
Mike
Click to expand...
Click to collapse

Hi team
I have the same issue, every time i turn my hermes on after its been off for more than say 30seconds it starts in landscape mode then switches to portraite mode, its driving me mad, at least i now know i am not the only person. maybe this will be fixed in the next rom update, fingers crossed aye
UPDATE: i also found this thread
http://forum.xda-developers.com/showthread.php?t=286552&highlight=standby+landscape
does anyone have any thoughts on his comments?

I actually think that the reply in the thread i posted above is correct,
My Hermes is an IMATE JASJAM (same thing of course) and i use the original belt holder that came with it, it has two (2) magnets in it to keep the cover shut, when ever i get a msg and i pull it out of the case (turns on automatically to show me the msg) its always comes out in landscape mode.
I turned my phone on and passed the cover with magnet side down over the phone and sure enough as i did that the screen changed from portrait to landscape mode, thus confirming its the magnet that causes it and not a defect with the phone.

Prevent screen switching off during phone call

Hi,
I have read and tried what I could find, but it does not work on my Jade.
Are there any new ideas how to keep the screen from swithching off?
Joe
This is copied from the Jade Manual:
Call functions
When a call is in progress, tap the available buttons on the Phone screen to put a
call on hold, dial another contact for a phone conference, enter notes about the
conversation, and more.
None of the above is possible because the screen disappears by itself.
Do HTC know about it? This seems to be a major f...up.

This problem has been discussed in many threads, there is no real solution.
If you activate the speaker for hands-free immediately after connecting the screen keeps on.

on mine the screen goes off... but if i press one fo the direction buttons it comes back on and stays on so i can use the keypad or look at contacts etc

Thank you guys.
I will try to contact HTC because I think this is a major fault. There is no access to those Call Functions if the screen disappears.
But people should also have the choice of switching the screen off to conserve battery during long conversations. That should be one of the Call Functions.
I tried to bring the screen back by pressing the OK button, but instead it ended the call. So why do we need the END button ?? Poor HTC. They are in front of themselves. Ever producing new half-baked models without thinking it properly out.
I have not tried the < or > buttons, but it would be risky because usually the OK button gets activated as well.
Has anybody on any HTC forum tried to petition HTC? I think this issue would be a nice one for a petition.
Joe

you say you dont want the screen to switch off but u dont want the < and > active?
tring to understand what you want/dont want here?
if i press < or > the screen comes on fully functional...

I did not say I did not want the < > keys active. I don't care what those keys do because I don't use them. The reason is that when I use them, I always inadvertently activate the Enter button. On my phone that terminates the call - the same as the End key.
It would be nice (and even logical) to have the Enter (OK) button to wake up the screen instead of the directional buttons. Maybe there is a registry tweak to do that.
Joe

jfranek said:
I did not say I did not want the < > keys active. I don't care what those keys do because I don't use them. The reason is that when I use them, I always inadvertently activate the Enter button. On my phone that terminates the call - the same as the End key.
It would be nice (and even logical) to have the Enter (OK) button to wake up the screen instead of the directional buttons. Maybe there is a registry tweak to do that.
Joe
Click to expand...
Click to collapse
I think it's about getting used to and familiarising with the intended design and button functions. Now after nearly 12 months using Jade I have no complaints. Even using phone banking, no problem with inputting the required numbers. Concur with MvBoe and DJHicks. It should also be acknowledged that this is 80% PDA and 20%phone (roughly).
MvBoe said:
This problem has been discussed in many threads, there is no real solution.
If you activate the speaker for hands-free immediately after connecting the screen keeps on.
Click to expand...
Click to collapse
DJHicks said:
on mine the screen goes off... but if i press one fo the direction buttons it comes back on and stays on so i can use the keypad or look at contacts etc
Click to expand...
Click to collapse

I was playing with the < and > keys to try to bring the screen back on, and I can definitelly tell you it does not work on my phone.
While doing that, I accidentally pressed the Power on/off switch - and voilá - the screen came back on and stayed on.
I repeated the experiment to confirm it.
Why didn't I think of it earlier? So obvious.
Joe

jfranek said:
I was playing with the < and > keys to try to bring the screen back on, and I can definitelly tell you it does not work on my phone.
While doing that, I accidentally pressed the Power on/off switch - and voilá - the screen came back on and stayed on. I repeated the experiment to confirm it. Why didn't I think of it earlier? So obvious. Joe
Click to expand...
Click to collapse
Good for you Joe. I suppose many other Jade users are already using that method. I thought you knew it already but wanting something more simpler.

azahidi said:
Good for you Joe. I suppose many other Jade users are already using that method. I thought you knew it already but wanting something more simpler.
Click to expand...
Click to collapse
Quote:
Originally Posted by jfranek View Post
I was playing with the < and > keys to try to bring the screen back on, and I can definitelly tell you it does not work on my phone.
While doing that, I accidentally pressed the Power on/off switch - and voilá - the screen came back on and stayed on. I repeated the experiment to confirm it. Why didn't I think of it earlier? So obvious. Joe
Hi azadhidi
correct me if im wrong is this not the only method to wake ur phone while making a call ie pressing the power button

haree said:
Quote: correct me if im wrong is this not the only method to wake ur phone while making a call ie pressing the power button
Click to expand...
Click to collapse
Also with other buttons if you set your phone to wake up with all buttons. See item #10 here http://forum.xda-developers.com/showthread.php?t=476493

Disabling the lockscreen after waking the phone up

Hi guys!
So I'll have to wait for my preordered HD2 untill 20th November here in Poland, but watching all the preview videos, a question arose in my head. I know the device isn't out yet, but its rom builds are already flying around, so maybe someone knows the answer. Will it be possible to disable showing of the lock screen after waking up the phone with the end call/power button and the device taking you immediately to the homescreen? I'm used to that on my TD2, and I think that using the phone this way is just much faster.

If i have undersood ur question correctly by completely disabling lock screen of ur future Leo, then yeah, thats possible. If u navigate through ur moving cursor to Settings, then Sound and Display and finally to Backlight options, there two options exist, when phone its on battery and/or External power, to either set the time limit to have the screen locked (and dim backlight of course) or to completely diselect it, which actually disables Leo to show and/or show lock screen.
Hope that clarification helped you

It sure did, thanks a lot I just hope that the buttons on the face of the HD2 will turn out to be as "shallow", flat and "stiff" as they look like in the vids, so that no accidental pressing of the end key while the device is in the pocket will be possible in practice

jgal said:
It sure did, thanks a lot I just hope that the buttons on the face of the HD2 will turn out to be as "shallow", flat and "stiff" as they look like in the vids, so that no accidental pressing of the end key while the device is in the pocket will be possible in practice
Click to expand...
Click to collapse
I did not think about the accidental pressing of END key before, but this will surely worry me, atleast I get the handset myself and test it in real-life...

Well even if any accidental cliks will be happening, then the lock screen will actually come in handy

well even if the buttons get pressed somehow, the screen won't react to pressure so only buttons will work if there's no lockscreen

You're right, good point hehe I guess all of us WM fans will have to get used to capacitive screens and their advantages/disadvantages

I think there will be 2 potential risks...
1. "Send" button is pressed accidentally more than once (last dialed number will be dialed)
2. Any keys get accidentally pressed continuously (device will remain on impacting battery life)
So yet a good screen locking solution will be recommended

3. "end call/power" button pressed and hold -> device turns off (at least I think so..or is there a "confirmation screen"??) -> you don't get any incoming calls/messages/etc at all =)
Btw, if you turn off the stuff as B3ler3fonte said, would there be any locking at all? So would touchscreen etc be allways "ready" and consuming battery?

In my Diamond2 (I dont use any lock screen or anything) when the screen is turned off and I press long the power button, the confirmation for powering off the device does in fact pop up, but the screen remains turned off, so its impossible to confirm the power off prompt (I see the prompt popped up when I press the pwr button once again to turn on the screen). So probably no threat from here. And even if the screen activates and the prompt for turning off the phone does come out, there's no way of confirming it in your pocket - thats the capacitive screen advantage. But the battery draining issues may occur at some scale... I guess we'll see how it all turns out in real life. The probably unavoidable problem will be if the end button would be possible to get pressed by accident - then we would be facing constant battery drainage with the lockscreen always appearing for no reason.

kabakara said:
...
Btw, if you turn off the stuff as B3ler3fonte said, would there be any locking at all? So would touchscreen etc be allways "ready" and consuming battery?
Click to expand...
Click to collapse
That could help but won't much, because(at least current models) they wake up upon any reminder, battery low, call, text, etc. Besides you will have to use both hands to turn phone on (the top button, unless you got ET fingers ) HD is tall...

Cannot see that menu item
B3ler3fonte said:
. If u navigate through ur moving cursor to Settings, then Sound and Display and finally to Backlight options, there two options exist, when phone its on battery and/or External power, to either set the time limit to have the screen locked (and dim backlight of course) or to completely diselect it, which actually disables Leo to show and/or show lock screen.
Hope that clarification helped you
Click to expand...
Click to collapse
Sorry but there is no setting for lockscreen in this menu. There is only settings for the backlight in battery or charged mode.
There is no control for the lockscreen at all Still looking for a way to completely disable this damned lockscreen.

Agreed - even the entry in the Settings tab that claims to control the lockscreen seems to have no impact (I have mine set to 12 hours and it completely ignores that) and the standard registry hacks don't seem to have any effect.
This is a real puzzler!

jgal said:
Hi guys!
So I'll have to wait for my preordered HD2 untill 20th November here in Poland, but watching all the preview videos, a question arose in my head. I know the device isn't out yet, but its rom builds are already flying around, so maybe someone knows the answer. Will it be possible to disable showing of the lock screen after waking up the phone with the end call/power button and the device taking you immediately to the homescreen? I'm used to that on my TD2, and I think that using the phone this way is just much faster.
Click to expand...
Click to collapse
back to the original topic:
changing the registry key: HKey_current_user/ControlPanel/Backlight/AutodevicelockEnable to value '0' (zero) works with other 6.5 roms
by default it must have seen to '1'
edit: my bad, its been solved already

idrisito said:
back to the original topic:
changing the registry key: HKey_current_user/ControlPanel/Backlight/AutodevicelockEnable to value '0' (zero) works with other 6.5 roms
by default it must have seen to '1'
edit: my bad, its been solved already
Click to expand...
Click to collapse
Is it solved already?? i can`t find it

mika34 said:
Is it solved already?? i can`t find it
Click to expand...
Click to collapse
the clarification was made to the guy who started the thread in post 3. if thats not it then the reg change i have put it should disable/enable the lock screen if the power button is pressed

[Q] Is there a way to disable the touchscreen while reading?

I just bought the new nook with glowlight. Previously, my wife and I shared the basic kindle 4 without touch. My experience so far has been great. I prefer the nook interface to the kindle, and the glowlight has been a godsend - my wife hates any light while she is sleeping, and the glowlight at its lowest setting doesn't bother her and is perfect for reading in the dark.
The biggest adjustment for me coming from the non-touchscreen kindle, is having to deal with incidental page turns. While looking for the optimal position to read and hold the nook, I often find it most comfortable to have my hand on the actual screen. Sometimes I also like to follow along with my finger. Both of these actions will cause the nook to perform unintended page turns, or at the very least bring up the menu. Sometimes I have to spend a large portion of my reading time just finding my page again.
I realize that with time I can learn to be more careful and only hold the nook by the bezel. But, since the nook has those wonderful physical page turn buttons, I figured it has to be possible (assuming the nook is rooted), to disable the touchscreen while reading a book. Maybe a button could be added to the nook menu (the options that display when you hit the n button) that toggles between enabling/disabling the touchscreen. I’ve searched for a way to implement a feature similar to this but haven’t been able to find anything. Does anyone know if there is a way that I can accomplish this for my nook?

Is it possible to disable the Zforce touch screen? Yes
Is it possible to enable the Zforce touch screen? No
Apparently there is a bug in the driver.
To disable the touch screen:
Code:
# cat /sdcard/zero.txt>/sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Where zero.txt is a single byte file of the digit zero without any line termination.)
There is also the issue that if you do turn off the touch screen you would have to use a hard button to turn it back on.

Renate NST said:
Is it possible to disable the Zforce touch screen? Yes
Is it possible to enable the Zforce touch screen? No
Apparently there is a bug in the driver.
To disable the touch screen:
Code:
# cat /sdcard/zero.txt>/sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Where zero.txt is a single byte file of the digit zero without any line termination.)
There is also the issue that if you do turn off the touch screen you would have to use a hard button to turn it back on.
Click to expand...
Click to collapse
So I take it then that there is no existing method to do this. Does this mean that we can disable it but would never be able to re-enable it due to the bug?
Regarding the issue of using a hard button to turn it back on, I figure the n button could be used, but there is still the bug.

davidsimon said:
So I take it then that there is no existing method to do this. Does this mean that we can disable it but would never be able to re-enable it due to the bug?
Regarding the issue of using a hard button to turn it back on, I figure the n button could be used, but there is still the bug.
Click to expand...
Click to collapse
If i remember right its been a while... Cool reader allows you to customize the touch screen zones (there i 9 i think) to do different things... one of the options is to do nothing. You can also set cool reader to be the default app so when you click a book in the library it automatically opens in cool reader. By setting ever touch screen zone to do nothing its would technically disable the touch screen while reading. because none of the zones would turn the pages. but once you exit the app or hit the N button the screen would still work.
check it out if your rooted.

Well, that's another way to do things, have an app over the target app that captures the touches and does nothing.
You could also patch the stock Reader so that it doesn't respond to any screen touches.
That's actually quite easy.
It would have the advantage of not affecting anything else.
Personally, I find the hard keys too hard and I always use touches on the stock Reader to turn pages.

persichini said:
If i remember right its been a while... Cool reader allows you to customize the touch screen zones (there i 9 i think) to do different things... one of the options is to do nothing. You can also set cool reader to be the default app so when you click a book in the library it automatically opens in cool reader. By setting ever touch screen zone to do nothing its would technically disable the touch screen while reading. because none of the zones would turn the pages. but once you exit the app or hit the N button the screen would still work.
check it out if your rooted.
Click to expand...
Click to collapse
You actually don't need to do that in coolreader it has a disable touch screen option I have just set one of the buttons to disable and enable touch when I double press.

Dopedangel said:
You actually don't need to do that in coolreader it has a disable touch screen option I have just set one of the buttons to disable and enable touch when I double press.
Click to expand...
Click to collapse
Way cool, but I can't find the option. Where is the disable touch screen option?
Thanks!

Dopedangel said:
You actually don't need to do that in coolreader it has a disable touch screen option I have just set one of the buttons to disable and enable touch when I double press.
Click to expand...
Click to collapse
I'm interested in this, too. Send us the instructions!!

_ig_ said:
I'm interested in this, too. Send us the instructions!!
Click to expand...
Click to collapse
Open Options, and go to the fourth tab (this one with a pin icon). There u have 'Key actions'. You can assign to your buttons different actions - eg. Lock/unlock touch screen. Works great

Rafsen said:
Open Options, and go to the fourth tab (this one with a pin icon). There u have 'Key actions'. You can assign to your buttons different actions - eg. Lock/unlock touch screen. Works great
Click to expand...
Click to collapse
Awesome.

davidsimon said:
So I take it then that there is no existing method to do this. Does this mean that we can disable it but would never be able to re-enable it due to the bug?
Regarding the issue of using a hard button to turn it back on, I figure the n button could be used, but there is still the bug.
Click to expand...
Click to collapse
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.

_ig_ said:
[...] Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Not sure about such battery life with wifi on. If I leave wifi on but the device otherwise off, I lose 3-5% battery per hour. With wifi off, it's good for a week or more, easily. I think the idea of disabling the IR sensors is great, but I'm not sure the battery savings will be enough to allow you to leave the screen active and wifi on.

had a look at the kernel code in zforce.c which I believe is the one in my multitouch hacked kernel (https://github.com/arkusuma/nook-touch-multitouch/blob/master/zforce.c)... basically
echo 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
works to switch it off, but
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
doesn't work, nor does
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/cmd
which should have a similar effect (ret = i2c_smbus_write_byte(tsc->client, cmd); where cmd = #define COMMAND_ACTIVATE 0x01)
all this said, when I get the nook to sleep by pressing the on/off button on the back I believe it goes into "deep_sleep" after a couple of secs; at this point, pressing the "n" button on the front restores the IR, so I suspect it's calling "static int zforce_resume(struct i2c_client *client)" which in turn checks whether the device was indeed on deep_sleep mode before re-initializing touch (IR) and the interrupt as per below code snippet. So, re-enabling IR should be OK but I don't want to monkey around with zforce.c... in terms of battery life, I am still checking stats before/after and I believe it goes from a 4% drop w/screen + IR + wi-fi on to about 1.5% drop if IR is disabled, but I need more time to quantify this gain in battery life.
if (deep_sleep == 0)
return 0;
zforce_touch_hw_init(1);
enable_irq(tsc->irq);

I want a way to do this too.
I already ruined a touch glow screen by simply handling it for a week without a case. No one had any idea at that time how ridiculously delicate the light-carrying film was and how it makes big starburst lights around every crack and blemish, and how effortlessly those cracks form.
So now I DO know I have to be fanatically paranoid about letting anything touch the screen that might put a crack or a scratch in it.
That means at the beach it simply must be inside a ziplock bag to keep sand off.
We need a way to disable the IR so things like a plastic bag don't activate it, and operate the device entirely from hardware buttons EVEN THOUGH yes I agree I don't like the bezel buttons for page turns either, NORMALLY.
Sent from my EVO using xda premium

I have a rooted nook simpletouch I got at Goodwill and wanted to chime in on how to disable touch for books:
Moon+ Reader allows you to disable screen touches too. Tap the center screen while in a book, press the cog that appears in the lower right, change everything in control options to "none" (the side clicky-buttons will still flip pages), then go to Miscellaneous and check "Disable vertical scrolling on touch" and uncheck "Allow fling horizontally to turn page."
I still have to touch the center of the screen to bring up options, but it's very intelligent and only responds to a quick tap -- not a long press of my thumb as I hold the nook awkwardly while reading in bed.

_ig_ said:
had a look at the kernel code in zforce.c which I believe is the one in my multitouch hacked kernel (https://github.com/arkusuma/nook-touch-multitouch/blob/master/zforce.c)... basically
echo 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
works to switch it off, but
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
doesn't work, nor does
echo 1 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/cmd
which should have a similar effect (ret = i2c_smbus_write_byte(tsc->client, cmd); where cmd = #define COMMAND_ACTIVATE 0x01)
all this said, when I get the nook to sleep by pressing the on/off button on the back I believe it goes into "deep_sleep" after a couple of secs; at this point, pressing the "n" button on the front restores the IR, so I suspect it's calling "static int zforce_resume(struct i2c_client *client)" which in turn checks whether the device was indeed on deep_sleep mode before re-initializing touch (IR) and the interrupt as per below code snippet. So, re-enabling IR should be OK but I don't want to monkey around with zforce.c... in terms of battery life, I am still checking stats before/after and I believe it goes from a 4% drop w/screen + IR + wi-fi on to about 1.5% drop if IR is disabled, but I need more time to quantify this gain in battery life.
if (deep_sleep == 0)
return 0;
zforce_touch_hw_init(1);
enable_irq(tsc->irq);
Click to expand...
Click to collapse
_ig_ said:
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Has anyone worked on this at all? IG, if you have that apk to turn the IR off still, I would greatly appreciate it. I have been messing a lot with the NST and I would love to be able to conveniently turn off the IR. I don't mind having to turn the Nook off and on again with a long press to get the IR back on.

ALinkToTao said:
Has anyone worked on this at all? IG, if you have that apk to turn the IR off still, I would greatly appreciate it. I have been messing a lot with the NST and I would love to be able to conveniently turn off the IR. I don't mind having to turn the Nook off and on again with a long press to get the IR back on.
Click to expand...
Click to collapse
The reason why I want to do this is to save battery life while running a large print clock app which I found called NightClock which came from android 1.6 donut. I can leave the clock app open but turn off the IR sensors to save battery and let it run longer without a charge. I'd also like to do this using renate's simple reader app and using the side buttons to turn pages.

_ig_ said:
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Does anyone have his apk or anything similar that will disable the IR array? I'd really like to use this for various applications. I don't mind at all having to reboot by holding the power button down. This could be used for Nooks with bad IR arrays to re-use them as really low battery clocks or calendars, and would also be good for extreme battery savings while reading (using the side buttons only for page turning).

ALinkToTao said:
Does anyone have his apk or anything similar that will disable the IR array? I'd really like to use this for various applications. I don't mind at all having to reboot by holding the power button down. This could be used for Nooks with bad IR arrays to re-use them as really low battery clocks or calendars, and would also be good for extreme battery savings while reading (using the side buttons only for page turning).
Click to expand...
Click to collapse
it's been a while... 6 years... let me see if I can find it...

When the NST is not actively tracking your finger only one IR LED is being flashed occasionally.
I really don't think the current usage is that high, although I can check.
If you are having trouble with the IR touch screen the problem could be a) dirt, b) alignment of the plastic lenses.
You can try the Touch.apk (in the signature) to visualize where the problem is.

Nvidia Shield TV (2015) random problems with Apps,Leanback UI and Controller buttons.

Hi Guys, After a random problem one day that included missing apps on the home screen and controller not functioning at all -- I did the following:
Memory card in card slot removed and re-inserted (32gb set as storage and many apps transferred to it freeing up the first 16gb). Rebooted shield and could now find apps , but controller was still only working via USB lead connected to Shield TV. Previously i had experienced similar problems and this had worked before, along with holding controller buttons for 20+ seconds to reset it.
Next step was:
I fully charged the controller as this had proved to be a problem a few times before when having strange controller issues. THIS WAS WHEN I REALISED the following also;
1) Had to input all account details again for Google account, Nvidia Account, You tube account, Steam account etc.etc..
2) Home button no longer works as the home button and also cannot double click to get the screen showing all open apps. It does make audio clicks as normal AND does show the streaming options/picture saving options when you long press it, (so the button is functioning of sorts.) I have since realised that the back button next to the Nvidia light button now works like the home button but you cannot double click it to show all open apps.
3) When I click on the google icon at the top left of the home screen next to the KB icon for voice searches. It does not work. ( though you tube speech searches work fine) It does accept searches after pressing the Nvidia button though when on the home screen.
4) The developer options in the settings menu were always on previously but, now it says that these options are on but "unavailable for this user" when pressed and are greyed out.
5) on/off sensor button on the top of the shield no longer works. (this is very similar to my wife Shield upstairs but hers is a 2017 model. She uses the remote or controller to turn off via the settings menu.
So......thinking of just resetting the Shield to factory settings and starting again but wanted advice before doing this and perhaps adding to the issues???
It seems to me that given all the different problems this is the only way??? My gut is actually telling me that it's an update that has happened and it has confused the 2017 model with mine???? or am I just seeing GHOSTS???
Any constructive advice would be appreciated.