Related
I have a MDA Vario. In SETTINGS --> TODAY --> ITEMS tab, what is "Today timeout", which is set at "4 hr" by default?? Does anyone know pls? I do not see any reference to it in the manual. Thx.
Tones
I think that's the amount of time after which it will return to the today screen if you left it with an app open and didn't touch it.
i tried it last night by leaving a game running, but it was still there when i got up the next day. it does seem to be the function u described, mate. Anyone else have any ideas pls?
A game will certainly work differently as it will request permanent focus and fullscreen. Just try with a standard app like calendar...
well, it was only a simple solitaire card game, but nonetheless I will try standard one like you suggested. But if this "timeout" function really is to return to TODAY screen, what is the real use of it? to timeout in 4 hours? and the longest possible time option is 12 hours.
Doesn't it simply stop refreshing the today screen (ie the clock and other values)?
It still refreshes the clock when you put it into sleep mode. However, after a number of hours it always takes some time for the clock to jump to the correct time.
It is the idle time before the Today screen is shown.
It's near useless, I almost always keep my today screen on anyway, because who wants to wait 4hours to see it
Use my TodayButton app if you want quick access to the Today screen...
V
personally, I always return to the TODAY screen anyway by shutting down applications after i'm done with them. I just thought this "timeout" thing was a sophisticated and useful function, but it turns out to be quite the opposite. But i will never understand why anyone want to design it to timeout in HOURS and not in minutes.
I'm the same, I shut down apps and always leave it on the Today screen!
V
vijay555 said:
Use my TodayButton app if you want quick access to the Today screen...
V
Click to expand...
Click to collapse
Doesn't the Red button do that anyway?
Nah, red button minimises apps to leave them running in the background (I think it actually just switches to the today screen). Some don't mind this, but for me, if I want the app open, I'll open it, and when I want it closed, I want it closed.
VJOkButt allows you to use the red button to minimse or close, and also properly close the phone to save around 3mb memory. But it does this sympathetically with the phone, so if you're in the phone, it hangs up, but otherwise it's a minimiser.
V
lolz
Morale of the story.... no one knows it. I always keep it disabled. So no big deal.
Had PDF softcopy of Reference Manual of my O2AL, and searched with no hint at all. Lets be it.....
I thought...
Guys,
I just stumbled upon this thread and thought it might be a good idea to get educated. I never knew it.
But this is what I thought - I thought it is the time slot to show appointments.
Means, if you chose a slot of 4 hours, and there are continuous meetings scheduled in your calender (and display of them enabled), then it would act like a rolling 4 hours window (read as slot).
Does this make sense? I never had so many appointmens, but always thought this was the use of it.
Comments please.
Are there any tweaks/apps that allow you to tailor the backlight's behaviour depending on what app you are using and set it up to suit each one?
I can't find anything like that but the reason I'm asking is as follows.
I want the backlight to stay on indefinitely when I have adobe reader open, but I don't want it to stay on indefinitely for anything else.
I read ebooks in adobe reader and it has no setting for this, so you either have to change the overall backlight settings to stay on then change them afterwards or just put up with constantly having to touch the screen to get the backlight on again.
What I'd like ideally is something almost like the Changescreen app (for rotation) where you can choose the apps you want and set how the backlight behaves when each app is in use.
Is there anything that does this? Or have I overlooked some really basic way of doing it?
Cheers
You can try Lumos: http://forum.xda-developers.com/showthread.php?t=450318
Thanks mate - that could be just the ticket.
Bah - tried to install it and as soon as I click it I get a "Installation Unsuccessful" error.
I'm on a custom rom but I forget which...
Bugger - looks like it could have been perfect.
Hmmm, I've installed Glight now to try that out but I can't get it to work for some reason.
It's enabled.
The phone's own auto backlight control is disabled.
I've added adobereaderle.exe as an exception and set it so it keeps the backlight on permanently.
I've done soft reset.
But it still switches off after a minute or two. I am talking about the backlight also, not the phone's standby. Ie with an acrobat doc open the light turns off after a minute or two then the phone goes into standby shortly afterwards. I guess ideally an app that deals with this would also be able to prevent standby for specific apps too.
Have I got the correct filename for Adobe reader or is there something else I've messed up? That's what I saw it as on the phone somewhere (I forget where but that's definitely what was written).
It will be nice obviously if I can make this work but I have to be honest and say that using Glight is a horrible user experience. It's a case of tapping the screen and waiting a few seconds for every single response. When you're trying to position the cursor in the exact right spot (ie to edit text or a typo etc) on the capacitive touchscreen with your finger this can take many screen taps, and it's pretty frustrating! But better that than nothing obviously!
I'm interested in this too. I tried Lumos and it works as for setting the backlight for certain apps (like max. brightness for Adobe Reader etc.), however it still doesn't prevent the phone going into standby, which is the main problem when trying to read something.
check this out:
http://forum.xda-developers.com/showthread.php?t=661472
Hi again..
I seem to have set the Nook ST glowlight to go to relaunch instead of the B&N homepage . Now when I click on 'n' and 'Home', it goes to the Relauncher instead.
Is there a way to reset this so it goes to the B&N page again?
I *think* that if you just install another launcher (anything from the market) you will be presented with the possible choices again when you try to access "Home". Then you can select the default B&N Home screen and later uninstall the added launcher.
Yeah, I installed Launcher 8 recently and this didn't trigger that option again. It is there when I do some things, but I think I asked it to remember my choice for the Home button. I am used to Windows OS and when you do something like that, you can always rectify it, by using either default programs or file associations etc. Android must have something similar, no?
When you make a default choice there is a message that tells you where you can reset the option but it seems to refer to a utility that is not accessible the way the Nook is configured. Can't remember exactly what it says but I've run into the problem before and what I offered seemed to work for me. Did you reboot after installing the additional launcher? I guess the other alternative is to UNinstall all of the Android launchers you've added and reboot. Then there would be no alternative to the Nook "Home". Assuming that works you could then reinstall your launcher of choice. It's a pain, I know. I've "rebuilt" my Nook many times while trying to get over the learning curve. Finally bought an additional SD card so I could save a backup every so often when I'm trying out something new. That's come in handy.
No, it's not like Windows at all (which some people would probably say is a good thing).
No need to uninstall anything. With reLaunch go to the app "nook touch mod". Using this app you can map the nook button to anything you want including the B&N Home page.
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
gozo81 said:
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
Click to expand...
Click to collapse
There is a Android App "Default App Manager" on Google play that may work.
gozo81 said:
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
Click to expand...
Click to collapse
I had a vague notion that NookTouchModManager didn't work with Glowlight, but I might be wrong. If it does work, then you don't want to set the "N" button to bring up Home. Rather you want to set the QuickNav Home button to "default". That's going to get you the B&N page you seek. But that means you will need a way to access your app drawer/launcher as well. For that purpose either one of the other QuickNav buttons could be reassigned OR you could assign a long press of the "N" button to initiate the launcher.
If NTMM doesn't work with Glowlight then I stand by the original idea: uninstall any launchers and reboot. With no alternative, you should get the B&N Home screen unless you have in some other way reassigned the QuickNav Home button.
Don't get discouraged. As a noob (still...) I had to start over quite a few times and there were times I was sure I had bricked my Nook. But I didn't.
Nook Color running CM 7.2 just started showing X and Y coordinates for touch events and don't know where the pointer option is located to disable this. I've gone into the Developer section under the apps, and there isn't a section there to remove or disable this either. Where might I find the option to disable this feature of seeing the X and Y coordinates and crosshairs when you touch the screen?
In effect, my 4 year old, who's tablet this is, never said that this effect was enabled, and it only happened in the past week. He doesn't know how or where he enabled it, and honestly, that makes sense because the desktop is locked down. He only has access to certain icons for his games, can't get into the apps or settings without the password, and always has to bring it to his mother or myself. There is even a firewall with the same basic setup. It's locked down.
I've gone through what I believe an exhaustive check through every option and just cannot find the pointer options like I can on my other android devices.
Any help would be appreciated.
SuD
standupdad said:
Nook Color running CM 7.2 just started showing X and Y coordinates for touch events and don't know where the pointer option is located to disable this. I've gone into the Developer section under the apps, and there isn't a section there to remove or disable this either. Where might I find the option to disable this feature of seeing the X and Y coordinates and crosshairs when you touch the screen?
In effect, my 4 year old, who's tablet this is, never said that this effect was enabled, and it only happened in the past week. He doesn't know how or where he enabled it, and honestly, that makes sense because the desktop is locked down. He only has access to certain icons for his games, can't get into the apps or settings without the password, and always has to bring it to his mother or myself. There is even a firewall with the same basic setup. It's locked down.
I've gone through what I believe an exhaustive check through every option and just cannot find the pointer options like I can on my other android devices.
Any help would be appreciated.
SuD
Click to expand...
Click to collapse
Go to developer options, scroll down to input, uncheck pointer location.
hwong96 said:
Go to developer options, scroll down to input, uncheck pointer location.
Click to expand...
Click to collapse
Thanks for this. Even though this isn't where it was, I found an icon for Dev Tools, I went into Development Settings, and there was a pointer location/no pointer location drop down. Totally different from what everyone else kept telling me, but it just happened to be under another section and option.
Thanks for the nudges, otherwise I would have reset the thing and started over. It's been running for years, and now I know what he got into... .just don't know how.
Thanks again.
SuD.
I found this post by user _ig_ on this thread:
https://forum.xda-developers.com/showthread.php?t=1693666&page=2
_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 anybody have this apk file or something similar in storage? If so, I would be more than grateful.
ALinkToTao said:
I found this post by user _ig_ on this thread:
https://forum.xda-developers.com/showthread.php?t=1693666&page=2
Does anybody have this apk file or something similar in storage? If so, I would be more than grateful.
Click to expand...
Click to collapse
So....I might be willing to help but I am not willing to mess up my NST. It seems to me that based on what @Renate NST has said that a "solution" that actually addresses the IR sensors is imperfect, at best. You can turn them off but not on. So why go there? What about a transparent screen overlay? I could easily create a little app that would produce one. My preference would be to have an "escape" in the form of a very small ghostly "x" at one corner of the screen (bottom right--you choose whether portrait or landscape). That way you have not done any partial mischief to the OS. The screen is blocked from touches but functional, and you can get at things if you need to easily by simply tapping that small, ghostly "x".
This does not, of course, address the supposed battery life gain of the more draconian solution. If you insist I could probably write a little app to turn off the sensors. If there is a response from a single press of the power button it's certainly possible to simulate that in the app. Seems to me a good goal would be a toggle that operates from a hardware button (using NTMM to assign one of the side buttons to the app).
I know I can make the transparent overlay app. The other will be guesswork.
nmyshkin said:
So....I might be willing to help but I am not willing to mess up my NST. It seems to me that based on what @Renate NST has said that a "solution" that actually addresses the IR sensors is imperfect, at best. You can turn them off but not on. So why go there? What about a transparent screen overlay? I could easily create a little app that would produce one. My preference would be to have an "escape" in the form of a very small ghostly "x" at one corner of the screen (bottom right--you choose whether portrait or landscape). That way you have not done any partial mischief to the OS. The screen is blocked from touches but functional, and you can get at things if you need to easily by simply tapping that small, ghostly "x".
This does not, of course, address the supposed battery life gain of the more draconian solution. If you insist I could probably write a little app to turn off the sensors. If there is a response from a single press of the power button it's certainly possible to simulate that in the app. Seems to me a good goal would be a toggle that operates from a hardware button (using NTMM to assign one of the side buttons to the app).
I know I can make the transparent overlay app. The other will be guesswork.
Click to expand...
Click to collapse
I really appreciate your reply and interest in this. I agree with you on that, a toggle that operates from a hardware button would work perfectly.
I believe what people learned when they experimented with the variable that Renate mentioned-- turning off the IR sensors would reset itself (the IR sensors would come back on) when the power button was long pressed, and the system rebooted.
This app would have many implications in re-using the NST not only as a super efficient reader (using only the hardware buttons), but also it could be used as a really efficient black and white photoframe, calendar, very readable digital clock, and anything that simply displays information like the daily weather, a looping video on display with fastmode enabled etcetera. This would extend the usable life of the Nook beyond its use as an awesome e-ink tablet, but beyond that to other household applications. This can also be used on Nooks with partially functioning IR arrays (functioning enough to install apps, but not functional enough to use as a tablet).
This is common if people open the Nook for some reason and mess up the positioning of the array on the screen or one of the infrared LEDs burn out. If this were to happen to someone, the nook could still have a legitimate use beyond its life as a reader/tablet, and it would not be tossed in the garbage.
If you're not willing to mess up your OS with experimentation. I am. I have a few Nooks I can mess with. I'll be your guinea pig if you're willing to take the time. If you need some fundage for your time, I'd be glad to supply some.
Here is Renate's post on the matter from that thread.
_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
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
Sorry, duplicate post
ALinkToTao said:
I found this post by user _ig_ on this thread:
https://forum.xda-developers.com/showthread.php?t=1693666&page=2
Does anybody have this apk file or something similar in storage? If so, I would be more than grateful.
Click to expand...
Click to collapse
I may have it trying to find it...
OK, so just to be sure, do you have Nook Touch ModManager on your device? Without that it will be difficult to assign the toggle to a hardware button.
Since rebooting seems to clear the IR-OFF condition, it seems like the place to start is a toggle that initially turns off the IR and then after that reboots the device when accessed again. Then it's set up to start over again.
Does that sound like it would work for you?
Edit: I've attached my first go at a toggle app. After installation the first run should disable the IR sensors. The next run should reboot the NST (and hopefully turn the sensors back on). Then it's reset to turn them off again, etc. If you do not have Nook Touch ModManager to assign the app to a hardware button I recommend against running it because it will likely leave you on the screen where you tapped it until a forced reboot.
I used Tasker to make this app so if you have not installed GApps on your device at some point in the past or don't have one of my other apps installed you will need two Google maps library files that Tasker and its daughter apps look for during installation. Without those files present (even though they are not used) the app will not install. I've attached everything in a zip. If you do need the two library files here's what to do with them before you install the IR Control app:
Copy the two files into the locations shown below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
You can also do:
Code:
# echo -n 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Be sure to leave a space between the '0' abd the '>'.)
This does turn the touch screen off.
echo -n 1 almost turns it back on.
Using the Touch.apk utility you can see that it is scanning and sensing.
Unfortunately, it doesn't get as far as spitting out events to /dev/input/event2, which is what it should be doing.
Semi-related: The NST apparently doesn't have uinput.
I use a daemon and uinput on my NG2 & NG3 to inject keystrokes from a external button box.
Renate NST said:
You can also do:
Code:
# echo -n 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Be sure to leave a space between the '0' abd the '>'.)
Click to expand...
Click to collapse
Yes, that's the technique used in the app. Hopefully I got all the spaces in the right places
nmyshkin said:
Hopefully I got all the spaces in the right places
Click to expand...
Click to collapse
Yeah, it's a little gotcha:
Code:
echo Hello > hello.txt [color=green]send "Hello\n" to the file hello.txt[/color]
echo Hello>hello.txt [color=green]send "Hello\n" to the file hello.txt, no problem here[/color]
echo 1 > one.txt [color=green]send "1\n" to the file one.txt[/color]
echo -n 1 > one.txt [color=green]send "1" to the file one.txt[/color]
echo 1 2> one.txt [color=red]send "1\n" to the terminal while redirecting all errors (stderr) to the file one.txt![/color]
echo 1> one.txt [color=red]send "\n" to the file one.txt![/color]
The only danger point is a single digit immediately to the left of the greater-than.
OK, foolhardy that I am, I decided to test the app I posted in #7 above. To my amazement, it does exactly what I said it does
First run requires SuperUser approval because of the shell command to turn off the IR. There's a little flash of the screen and then it goes "dead" (thankfully not literally). I assigned the app to one of my hardware buttons for testing and on the second press of the button the NST rebooted and..........all was restored!
So @ALinkToTao, I hope it does what you wanted in terms of power consumption. Sort of freaky to have the screen unresponsive, though
nmyshkin said:
ok, foolhardy that i am, i decided to test the app i posted in #7 above. To my amazement, it does exactly what i said it does :d
first run requires superuser approval because of the shell command to turn off the ir. There's a little flash of the screen and then it goes "dead" (thankfully not literally). I assigned the app to one of my hardware buttons for testing and on the second press of the button the nst rebooted and..........all was restored!
So @alinktotao, i hope it does what you wanted in terms of power consumption. Sort of freaky to have the screen unresponsive, though
Click to expand...
Click to collapse
duuuuude!!! Thanks!!
I would like to sincerely thank @Renate NST @nmyshkin and @_ig_ for all of your inputs and help.
I wish there was something I could do for you all to thank you for your time?? Can I give you guys a modest tip for your help??? This is so awesome!!
Is there a way to label or re-post this thread so that it indicates that it contains a new app for the NST in the forum for people interested in doing this?? Thanks so much again!
@nmyshkin This app works wonderfully! One suggestion for anyone that installs this on their own nook...
After install don't hit "Open" at the package installer screen and initiate until you have already set one of the hardware buttons to initiate the app! You can re-initiate the app as nmyshkin said to reboot the nook once there is a hardware button that can trigger the app.
If you accidentally do by force of habit tap "Open", definitely hit "Deny" at the superuser prompt!
If you accidentally hit "Accept" by force of habit, your Nook is not lost. If you do a hard shut off by holding down the power button, the IR will come back when it reboots.
Thank you all so much.
I do notice that if the Nook goes into deep sleep, the IR will also come back on.
@nmyshkin , I've been testing it today, and I think it may be better to remove the reboot trigger from the app and only have it turn the IR off. Simply having the app trigger IR off should be sufficient. The reason being that if you want to read with no IR, and you put the Nook to sleep or the screen times out and it goes into deep sleep, it will turn the IR back on.
In order to turn the IR off again, you have to trigger the app which will reboot the Nook, even though the IR is back on. That being said, it is still very useful for a huge majority of applications that I was planning on using this for. Again, I thank you so much for your time and effort putting this together.
If we were to remove the reboot function of this simple and awesome app:
Rather than having to reboot the Nook entirely to get IR back on, you can simply let it go into deep sleep by putting it to sleep and waiting probably as long as it takes to reboot the Nook and the IR array comes back on. If for some reason the Nook can't go into deep sleep, a hard power off and then power on will do the trick.
ALinkToTao said:
If we were to remove the reboot function of this simple and awesome app:
Rather than having to reboot the Nook entirely to get IR back on, you can simply let it go into deep sleep by putting it to sleep and waiting probably as long as it takes to reboot the Nook and the IR array comes back on. If for some reason the Nook can't go into deep sleep, a hard power off and then power on will do the trick.
Click to expand...
Click to collapse
Or, if we knew how to put the NST into deep sleep mode via command, said command could replace Reboot in the toggle, I guess.
Anyway, I've attached an app that only turns off the IR (no toggle).
nmyshkin said:
Or, if we knew how to put the NST into deep sleep mode via command, said command could replace Reboot in the toggle, I guess.
Anyway, I've attached an app that only turns off the IR (no toggle).
Click to expand...
Click to collapse
Thanks so much, man. I agree with you. If we knew the command for deep sleep, we could toggle it that way. Much appreciated. I hope this serves the xda NST community as well for anyone that would like this also. Thanks man. May you recognize the light of pure love shining in your life.
@nmyshkin Thanks again for writing this simple app!
I must say that this is significantly lengthening the battery life for apps that use the e-ink screen to display something for long periods of time without letting the Nook go to sleep. In particular, that clock app which I mentioned in an early post in this thread, it was draining the battery like 30% in a few hours. Now, with the IR off, the battery went down only 3% in a few hours! This was a very loose test--more like a casual observation. It wasn't a controlled experiment, so I would like to perform a controlled experiment with this and give you the results! It's looking really awesome though!
Also thanks again for removing the reboot! Now that we know that the IR comes back on after a deep sleep, it is much more convenient to not have it reboot.