Does anyone know if there is a particular e-reader app, or any kind of hack, that will allow the S4 to turn off the capacitive button backlights while reading, but leave them on the rest of the time? (I realize I could turn them off entirely, which is what I normally have to do.) This worked fine for me with Cool Reader on my S3, but the "Turn off key backlight" setting doesn't work on my S4, and it is a real annoyance to have the buttons light up each time you turn the page, especially when reading in the dark. I'm assuming this is related to the S4 itself, since I've tried a bunch of different e-reader apps (FBReader, Moon+ Reader, etc), and can't find any that this will work with. Is there any way to get it to function like the S3 did with regard to the button lights?
Related
Hi everybody,
Question: I'd like the backlight from the keyboard to be always on when loading, or most ideally: to have manual control over it. Right now the only control there is, is the setting 'Light Sensor Enable', but this turns it only on for some period of time. Usefull to save batterypower, but when on AC (like at night in the car) I really find it annoying to have to press whatever button in order to get the keyboard lit.
Anyone knows a solution for this, or can write a small program to handle it? Or change values via Regedit?
Found another thread here about keyboard backlight, but there it didn't work at all.
Durree
Until recently I had a phone with no search button. this was frustrating, so I rooted and altered the keypad layout file to change the trackball click (a nice bouns feature on phones, it turns out) to launch the search function. However, there was a problem: occasionally, it wouldn't work. not all the time, just sometimes. I figured maybe it was a side effect of the hack, that maybe the stock rom I had just got confused sometimes thinking there shouldn't be a search available at the time.
But recently, I upgraded to a new phone that does have its own search button, a real one. but once in a while, it won't work. the other face buttons do, just not this one, sometimes. this is both when launching google search fromt hehome screen, and the in-app search function.
and thinking back, my first Android was sometimes like that too, but I just thought it was due to the search "button" being one of those capacitive spots (shudder) that just tend to be naturally less responsive at times.
so, what gives? is this a common thing on some phones, i.e. does the function lag or something? to be clear, on all three phones, I never had problems with the other three buttons.
The accelerometer on my Razr Maxx works promptly and perfectly except under two conditions. The first -- if I'm lying down, say on a couch or in bed, and holding the device over my head facing down. In this position the device will almost immediately shut off over and over. It won't reboot, just shut down. I can always restart it the same way I would from any "sleep". I can get the device to stay on merely by rotating it to face "up" no matter whether I change position or location or run or do not run any particular application. Is this common? Is it by design for some reason? The second -- if I have Button Savior installed, the Maxx accelerometer will work but there will be a significant delay in responding. Like 15-30 seconds delay! No Button Savior - no delay. Install Button Savior - delay. Uninstall Button Savior again - no delay. This troubles me as I really like Button Savior even on devices that have "hard" buttons. Having these controls right under my thumb is the fastest way to navigate, for me. Button Savior (updated) works perfectly for me on other Android phones, on my rooted Nook Color (CM7), even on my rooted Nook Touch. Any cures for either ill?
Hi
The accelerometer issue... does this happens from the first day you bought it? I trying searching similar issues, could not find anything. I am almost sure it is physical defect of some kind, you should probably take it back for replacement.
I don't know if the accelerometer issue related to Button Savior began when I first installed the app (as opposed to coming from a particular app update, for instance) as it took a long process of elimination to find the connection. As to the "upside down" issue I believe it has always done that. However -- it only does it if I TURN ON the device while it is upside down. If I start using it facing up, say watching a video, and then turn it upside down the video continues to play flawlessly. Bizarre!
I know there is an option to use the light sensor to detect when your phone is in your pocket, and turn off. Maybe it's on on your phone, and it's detecting lower light when you flip it over and shutting the screen off?
ok, so i misunderstood the issue, i thought the phone turns off completely...
if it only goes into "silent" or "lock" mode... maybe you installed some kind of app that does that when you flip? or maybe your player has one of those settings? like... say you are in a meeting, with your phone on the table, it rings... you just flip it and it goes silent.... some android build have that as a default setting already...
here, check this so u understand better what i mean :
http://www.appbrain.com/app/flip4silence/org.failedprojects.flip4silence
hope this helps!
tried updating yet? i had the same problems prior to the 65.1.40 update
I use Cool Reader every day on my Nexus 7 to read while at work. I like to recline back in my chair and read but then have to constantly lean forward to touch the screen and turn the page.
Then I heard about Muku Shuttr on Kickstarter and figured I might be able to use it as a remote control page turning device. It pairs with the tablet using Bluetooth and it's single button emulates a VOLUME + button press.
Despite setting the VOL+ to the NEXT PAGE action in Cool Reader's options, it doesn't work. Cool Reader is sensing the input somehow, because when I press the button it immediately switches to a black screen with DOCUMENT LOADING displayed and then returns back to the page I was on. If I press it 2 or 3 times, it will freeze on the DOCUMENT LOADING screen requiring an app restart.
Anyone have any ideas or suggestions of how I can get this to work?
If no one has any ideas, can anyone at least point me at a better place to ask?
No one?????????
Problem solved. Developer of Shuttr suggested I switch the device into iOS mode, which works perfectly!
So I've noticed when using smart view to cast to a TV screen, the phone screen will turn to a low power mode, that says smart view, press power or swipe to turn on. My concern is that this image causes image persistence once smart view is done, and could eventually lead to burn in. Does anyone know if this screen moves, like the Always on Display images do; or if there is a way to disable this screen without disabling the screen staying potentially awake the whole time. It may not be possible, but I wanted to see if anyone had any experience. The only possible workaround I've come up with is to use the android native casting feature (via nova and a widgets activity) and perhaps the following app.
https://play.google.com/store/apps/details?id=com.skin1980.screenoffkeepplaying
I'm finding that mine doesn't always enter the power saving while mirroring which I wish it would when I want it to. If I turn the screen off while mirroring, then ask Google voice to play next song or something the screen mirroring wakes up and display on the external screen and puts the power save mode on the phone which is what I'd expect.
I wish mine did this without having to turn the screen off and the wake it up with voice. If I wake it up with the power button then screen mirror comes on b I t so does the normal screen on the phone.
Maybe we can swap ha ha.
Anyone else not getting the power save option when mirroring? I need to turn the screen off then ask Google to do something for the power save to work. Turning the screen back on doesn't help, just asking Google voice seems to bring it back. I was hoping it would just time out and start automatically. Samsung don't seem to understand their own options, with them telling me that it's not possible until I pointed out it's a software feature if their phone then they went silent.