Everytime when I plug in the charging usb cable to phone, the phone will change to Landscape mode when there is incoming call!
Is there anyway to disable this function?
Hi, I can't replicate your problem, sorry. Do you have additional screen rotation software installed which you could disable? maybe its a glitch that would be fixed with a soft reset? (red button inside back cover or remove abattery for 10 seconds).
cMMY69 said:
Hi, I can't replicate your problem, sorry. Do you have additional screen rotation software installed which you could disable? maybe its a glitch that would be fixed with a soft reset? (red button inside back cover or remove abattery for 10 seconds).
Click to expand...
Click to collapse
I haven't installed any other rotation software, my ROM is HKCSL stock rom and I believe that this is the default settings.
did you try plug in the usb charging cable then press the phone button? I believe it will change to landscape mode.
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.
hi there!
I need some advice/info.
I found an sgs4 for a very good price, the person that's selling the phone says that he dropped it and screen it's not responding.
it's there any way to check that? mhl cable or pc?
I wanna make sure it's the screen only and not something else.
it's there a software that I can check with?
any suggestions will be appreciated.
thanks
nbnion said:
hi there!
I need some advice/info.
I found an sgs4 for a very good price, the person that's selling the phone says that he dropped it and screen it's not responding.
it's there any way to check that? mhl cable or pc?
I wanna make sure it's the screen only and not something else.
it's there a software that I can check with?
any suggestions will be appreciated.
thanks
Click to expand...
Click to collapse
You can use a free app like "AirDroid" to control the device from a PC/Mac.
https://play.google.com/store/apps/details?id=com.sand.airdroid&hl=en
Just follow the instructions on set up and connection and test it. If you use the app and the device itself is moving around via the software or doing the functions commanded from the PC, then it would seemingly be just the screen not responding.
Check the physical buttons too - make sure the volume rocker adjusts the volume, home button sends home or navigates to the Recent Apps screen. Make sure the power button will wake/sleep the device's state and power on/off.
If it does all that, a simple screen swap should do it.