Hey guys,
Just received my Google Play Edition Galaxy S4, and one of the first things I notice is that the capacitive button (Menu and Back) timeout is set to approx 1-2 seconds.
This is the case with the regular (international) version of the Galaxy S4 as well, but in the regular version you can easily disable the key light timeout under Display -> Touch key light duration. I cannot however find a setting to keep the buttons lit (with the screen) in the Google Play Edition S4.
The questions:
Could a third party app fix this problem? Are there such apps available already? Would root be necessary?
Buying this device I had no intentions of rooting and loading a custom ROM onto it, but this key light thing is going to bug me no end so I might have to reconsider.
I'm sorry if the answer is obvious and I'm just a blind fool, or if the question has been asked and answered before. I did a few searches but could not find anything relevant to the i9505G.
Cheers!
mannyb said:
Hey guys,
Just received my Google Play Edition Galaxy S4, and one of the first things I notice is that the capacitive button (Menu and Back) timeout is set to approx 1-2 seconds.
This is the case with the regular (international) version of the Galaxy S4 as well, but in the regular version you can easily disable the key light timeout under Display -> Touch key light duration. I cannot however find a setting to keep the buttons lit (with the screen) in the Google Play Edition S4.
The questions:
Could a third party app fix this problem? Are there such apps available already? Would root be necessary?
Buying this device I had no intentions of rooting and loading a custom ROM onto it, but this key light thing is going to bug me no end so I might have to reconsider.
I'm sorry if the answer is obvious and I'm just a blind fool, or if the question has been asked and answered before. I did a few searches but could not find anything relevant to the i9505G.
Cheers!
Click to expand...
Click to collapse
BUMP.
I've enabled the software navigation bar on the Google Edition on a US AT&T S4,
The only problem is that the capacitive lights come on when I press home/back/recent apps software keys.
Is there any way to modify settings of the light duration?
Help greatly appreciated
Keeping capacitive buttons lit in Google Edition S4 [i9505G]
BUMP
This is so annoying. How could Google even think about shipping the Google Edition with this BUG?
Such a flaw is in no way excusable. You really have to be not testing Google Edition S4 to not see this.
Any chance of a solution here?
Anybody sort this out??
Capacitive light app for GE Galaxy S4
For control of the Capacitive lights on the Google Edition Galaxy S4 go to the link below to get the app. It works great!
http://forum.xda-developers.com/showthread.php?p=43256528
Related
Does anyone know if it's possible to adjust the delay before the capacitive buttons turn off?
The issue I'm having is while using the phone in the dark. The buttons light up and a couple seconds later they turn off. Finding the right button in the dark is a pain.
The only way to get the buttons to light up again is by touching the screen.
Thanks.
Came here looking for the same info. There is at least one thread in the captivate forum asking the same thing, so it looks like it's a problem for the whole galaxy line. It does not appear to be adjustable in the current firmware. I'm really hoping for a fix from Samsung or one of the homebrew developers soon.
Hey guys,
I've searched but I can't find an answer. I'm using an Incredible S ROM on my HD2 at the moment that leaves the hardware keys constantly on when the screen is on - I don't like this, and don't ever need the backlight for the keys as I know where they are now. Is there any way I can disable this totally?
Thanks,
Zuka
Bumpity bump
zukа said:
Hey guys,
I've searched but I can't find an answer. I'm using an Incredible S ROM on my HD2 at the moment that leaves the hardware keys constantly on when the screen is on - I don't like this, and don't ever need the backlight for the keys as I know where they are now. Is there any way I can disable this totally?
Thanks,
Zuka
Click to expand...
Click to collapse
Hey,
if your build is using the same init script as rafdroid you can try this:
create a file called "config.txt" on the root of your sdcard copy/type this line: auto_btn_backlight=0 - then reboot.
this is also worked with dandiest builds, so Might work for you.
Hi, thanks for your reply
I'm not running one of Raf's or Dandiest's ROMs, mine doesn't have an init script so this won't work. Is there any other way? Seeing as those ROMs have different button backlight drivers I'm assuming there has to be a way to control their on/off states
I'm not trying to be annoying by bumping, but this keeps falling off the radar and I'm sure there's a way to do this, if anyone could point me in the right direction that'd be awesome
zukа said:
I'm not trying to be annoying by bumping, but this keeps falling off the radar and I'm sure there's a way to do this, if anyone could point me in the right direction that'd be awesome
Click to expand...
Click to collapse
Sound like an unstable ROM. My only advice is to try a different one. If you like pure android you can try tytung's ROM. It's the best, just follow my sig.
...what?
Why does my ROM sound unstable? The button backlights aren't actually causing a problem, I just don't need them. Ever. I'm looking for a way to disable them, but I like (love) my ROM after months of searching
zukа said:
Hi, thanks for your reply
I'm not running one of Raf's or Dandiest's ROMs, mine doesn't have an init script so this won't work. Is there any other way? Seeing as those ROMs have different button backlight drivers I'm assuming there has to be a way to control their on/off states
Click to expand...
Click to collapse
Hey
guessed u didnt have a rom from raf or dandi, they havent released an Incredible S build yet.
mind telling us which Incredible S you have or is it a secret
& you are right, it has nothing to do with stability, its the newer light drivers, this was implemented to fix the led notifications, not sure if you can change this (always on) behavior without going back to the old drivers.
p.s. how do you know your build doesnt have an init script, have you tried the config.txt?
Hey mate,
I'm using Korand's stripped down Incredible S build - http://forum.xda-developers.com/showthread.php?t=1019489
The reason I'm assuming it doesn't have an init script is because, apart from the battery percentage icon, I think everything else is stock, judging from Korand's first psot. It's hard to tell because there's not much support for the ROM
I wouldn't mind going back to the old light drivers though, or just rendering both the notification LEDs and button backlights inoperable. Don't use either really
bumpity bumpity yeah
zukа said:
Hey guys,
I've searched but I can't find an answer. I'm using an Incredible S ROM on my HD2 at the moment that leaves the hardware keys constantly on when the screen is on - I don't like this, and don't ever need the backlight for the keys as I know where they are now. Is there any way I can disable this totally?
Thanks,
Zuka
Click to expand...
Click to collapse
Theres an app in android market for that...its called "ADJ Brightness" which basically allows yoy to adjust and lock the screen brightness. It can be set to extremely low (much lower than android lowest setting...or extremely high, again higher than android default max
But if you hit menu then chose "options" there near the bottom you will see the option to Lock the button lights OFF...works a treat and saves me a lot of battery jiuce. Also in this options menu you can chose to have the little charging led either On or Off...I find this used in conjunction with "button saviour" and another app that allows me to wake the phone with the volume rocker means i dont need to use the H/W keys at all
Dont know if this is what your after but hopefully it may help.
Thanks Con, I installed the app
It does let me control the hardware buttons, allows me to turn them off, but whenever I press them they just come back on again, despite checking "always off" in the settings
But at least this shows that they can be controlled, even on an HD2
any other ideas?
Ah, sorry zuka, i have only just noticed this as well...yes it seems the backlight does reactivate when i again use the buttons. However i am using Rafdroid 4.2 rom which allows the backlight to off after 10 seconds. So i guess your issue does lie within your rom
I no longer use the hardware buttons (or very rarely) instead i opt to use the onscreen replacments within button savior, Which is why i didnt notice that the backlight does re-activate when the buttons are used...this seems to overide the adj.bright app. But like i say my light is only on for 10 secs or not at all using adj & BS.
Sorry dude am at a loss as to how you could fix this as it does sound frustrating
Nah, thanks for your reply anyway. It's not like this is a horrible bug, it's just annoying because I don't want the hardware buttons at all, I know that they can be controlled but I just can't figure out how to keep the damn things off...
if anybody has any other ideas, I'd welcome them. at this point I'm stumped
Has anybody been thinking about this for a while and has a solution?
Hey
ADJ Brightness should do the work for you
just play with the setting( Menu-option)
lock screen brightness, so it stays off.
good luck
tried this app a while a go and it solved this problem.
Hi all,
I'm wondering if there's any alternative ways to put the Nexus 7 (or any Android device I guess) to sleep/wake it up. I'm thinking something along the lines of an app that forces the touch screen to stay active but turns the display off so you can use touch input to activate wake/sleep.
Might be a bit of a stupid question. The reason I ask is because my N7 is mounted in my car and the power button isn't easily accessible.
Cheers for any tips..
UnitedWeFall said:
Hi all,
I'm wondering if there's any alternative ways to put the Nexus 7 (or any Android device I guess) to sleep/wake it up. I'm thinking something along the lines of an app that forces the touch screen to stay active but turns the display off so you can use touch input to activate wake/sleep.
Might be a bit of a stupid question. The reason I ask is because my N7 is mounted in my car and the power button isn't easily accessible.
Cheers for any tips..
Click to expand...
Click to collapse
Not sure if this helps but I have a case that I bought for my N7 and when I open it and close it the screen turns on and off.
Here it is http://www.amazon.com/gp/product/B0...ASIN=B008D2POAS&linkCode=as2&tag=newyormus-20
MineralGray02K said:
Not sure if this helps but I have a case that I bought for my N7 and when I open it and close it the screen turns on and off.
Here it is http://www.amazon.com/gp/product/B0...ASIN=B008D2POAS&linkCode=as2&tag=newyormus-20
Click to expand...
Click to collapse
Thanks for that but nah, it's mounted in my car dash so a case won't fit..
But that give me an idea.. does sliding a magnet across a specific point on the screen turn it on/off? That's the idea with the smart cases right?
UnitedWeFall said:
Thanks for that but nah, it's mounted in my car dash so a case won't fit..
But that give me an idea.. does sliding a magnet across a specific point on the screen turn it on/off? That's the idea with the smart cases right?
Click to expand...
Click to collapse
Yes,
The magnet is somewhere to the bottom left of the device (i would say to about a quarter from bottom up and on the black contour) . If you can add an sliding magnet (make sure is weak) then you can lock/unlock screen.
Nfc tags dude i wonder if they would work
Sent from my Nexus 7 using Tapatalk 2
I know some kernels can enable touch wake. I imagine it can incorporated soon. On my Galaxy Nexus, there's an app I downloaded that allowed a specific screen swipe to wake the screen.
Sent from my Galaxy Nexus using Tapatalk 2
wyattyoss said:
On my Galaxy Nexus, there's an app I downloaded that allowed a specific screen swipe to wake the screen.
Click to expand...
Click to collapse
What was the app?
Sent from the third Galaxy on the left.
That would be awesome. Do you remember the name of the app?
Gesture Control?
UnitedWeFall said:
Hi all,
I'm wondering if there's any alternative ways to put the Nexus 7 (or any Android device I guess) to sleep/wake it up. I'm thinking something along the lines of an app that forces the touch screen to stay active but turns the display off so you can use touch input to activate wake/sleep.
Might be a bit of a stupid question. The reason I ask is because my N7 is mounted in my car and the power button isn't easily accessible.
Cheers for any tips..
Click to expand...
Click to collapse
Hey man. I used to have an awesome app on my very first Android tab years ago. It would turn the screen completely black (via home screen or notification icon) without actually putting it to sleep. Because it wasn't really asleep, a double tab would turn the screen back on. I CANNOT FIND IT FOR THE LIFE OF ME! Anyway, after reading your question, I searched for an hour, because I could use something like this for my setup in my car.
So, I found something that turns the screen both on and off, and actually works on my N7. Search for Proximity Screen Off. I installed the free lite version, and it works. I found out the screen won't turn on though, unless you disable your lock screen. Play with the settings to your liking.
Oh, and since we don't have prox sensors, you can use your ambient light sensor. Good luck, lmk if it works for ya.
joelhon said:
What was the app?
Sent from the third Galaxy on the left.
Click to expand...
Click to collapse
It's called PGM Nexus. I almost don't want to give up my Galaxy Nexus (but I sadly still plan to) just because of this one app alone...it is so godawful nice to be able to swipe, or simply double tap the screen to fire up the screen. Unfortunately this app apparently requires some deep voodoo to work as its kernel related, and applies strictly to the Galaxy Nexus. I know a bunch of people have already started bugging the developer to make a version for the Nexus 7, I'd suggest piling on. :fingers-crossed:
It's apps like these that make you realize how superior the Nexus devices are at getting really good customized software over other devices.
I do wish there were some other options for the Nexus 7, like using the front camera as a proximity sensor of sorts to detect a handwave, or simply shaking the tablet.
jaycustom said:
Hey man. I used to have an awesome app on my very first Android tab years ago. It would turn the screen completely black (via home screen or notification icon) without actually putting it to sleep. Because it wasn't really asleep, a double tab would turn the screen back on. I CANNOT FIND IT FOR THE LIFE OF ME! Anyway, after reading your question, I searched for an hour, because I could use something like this for my setup in my car.
So, I found something that turns the screen both on and off, and actually works on my N7. Search for Proximity Screen Off. I installed the free lite version, and it works. I found out the screen won't turn on though, unless you disable your lock screen. Play with the settings to your liking.
Oh, and since we don't have prox sensors, you can use your ambient light sensor. Good luck, lmk if it works for ya.
Click to expand...
Click to collapse
Thanks for that! Appreciate it. I'll give it a try when I get home after work and report back.
jaycustom said:
Hey man. I used to have an awesome app on my very first Android tab years ago. It would turn the screen completely black (via home screen or notification icon) without actually putting it to sleep. Because it wasn't really asleep, a double tab would turn the screen back on. I CANNOT FIND IT FOR THE LIFE OF ME! Anyway, after reading your question, I searched for an hour, because I could use something like this for my setup in my car.
So, I found something that turns the screen both on and off, and actually works on my N7. Search for Proximity Screen Off. I installed the free lite version, and it works. I found out the screen won't turn on though, unless you disable your lock screen. Play with the settings to your liking.
Oh, and since we don't have prox sensors, you can use your ambient light sensor. Good luck, lmk if it works for ya.
Click to expand...
Click to collapse
Could you please post the settings you are using? Specifically the light sensor settings. I am having trouble getting this to work properly. Thanks!
Screen Off
gtdRR said:
Could you please post the settings you are using? Specifically the light sensor settings. I am having trouble getting this to work properly. Thanks!
Click to expand...
Click to collapse
Hello. I'm not sure if it helps you, but for turning off screen I use Nova Launcer (alternatively you could use Apex Launcher - as far as I remember, it has gestures in its free version) with Screen Off app by Katecca. I've set Nova Launcher to react to swiping up screen by executing Screen Off app. So I have to turn on screen by pressing button, but to turn off I just swipe up screen.
Best regards,
Artur
Added support for nexus 7 to ProximityScreenOffPro v6.0
https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoffpro
Hi,
I have a Galaxy S4 i9505 (Snapdragon version) running a google play edition rom (4.3).
ROM - http://forum.xda-developers.com/showthread.php?t=2348272
I noticed recently after holding my phone in front of my webcam that the gesture sensor is active whilst the screen is on, its constantly blinking . As there is no use for it in this rom I'm sure this must either be a bug or that it does this by default.
Webcam photo (Sorry for bad quality) - http://img20.imageshack.us/img20/4639/bdgf.jpg
My question is... Is this normal for the google play edition roms, Or is it just my device?
Thanks,
Sly
After testing the note 4 nexus 6 and s5 prime, i have come to the conclusion that the always on feature of the note 4 is not always on.
With the google search bar widget floating on the homescreen with the screen on the note 4 would pick up the okay google command 100% of the time.
Now with the screen off or locked, it would pick up the command 100% of the time at times, 0% sometimes( doing this test makes me feel retarded). This leads me to believe that when it doesnt respond, the mic simply isnt listening, an s voice issue. And that the google floating widget uses a completely separate routine for its listening.
Anyone have any inputs on this? Will lollipop fix it? Or is it something that cannot be fixed?
It works for me - on, off, locked or not.
It does for me. Just not consistently.
shinasurada said:
After testing the note 4 nexus 6 and s5 prime, i have come to the conclusion that the always on feature of the note 4 is not always on.
With the google search bar widget floating on the homescreen with the screen on the note 4 would pick up the okay google command 100% of the time.
Now with the screen off or locked, it would pick up the command 100% of the time at times, 0% sometimes( doing this test makes me feel retarded). This leads me to believe that when it doesnt respond, the mic simply isnt listening, an s voice issue. And that the google floating widget uses a completely separate routine for its listening.
Anyone have any inputs on this? Will lollipop fix it? Or is it something that cannot be fixed?
Click to expand...
Click to collapse
Im having the same issue. Ive just got my self a wear watch and configured now to take instructions. Also like being able to wake my note 4 by shouting at it.
I think its when it goes in to deep sleep... still testing...
I always felt like there was a conflict between Svoice and Google Now so I usually uninstall or disable Svoice (cos i prefer GN) but i read somewhere the always listening only works with Google Now Launcher. What launcher are you using? But anyway, Svoice should work with TW, otherwise Samsung are selling defective phones!
Im on the google launcher.
I dont think its a deep sleep issue since it fails to register ok google sometimes even when the screen is on.
E.g. in an app, lock screen and screen off.
however it never fails in any screen with a google now microphone. E.g. maps, google now or any homescreen with the google now search bar widget.
It's because it keeps Un ticking listen all the time in Google now as soon as I set s voice. As stated earlier, I think only one can be the always listening and now doesn't do screen off.
I have got round it by setting tasker profiles to open now when svoice is open.
So I can shout galaxy to wake it, ok google then instruct it to do a billion other tasks I have set through commandr. This set till slows me to use Google now with my LG round. All round it's working pretty good, exept it not waking from time to time...
I use nova launcher (has enable ok google for nova in settings)
But unfortunately have failed to get all other non Google apps to work with ok google, the 3rd party ok google x posed module breaks commandr.
Hope this helps some one.
Looking forward to fixing this "not listening" from time to time.
Everyone still having the same issue? I am still no solution, can't identify the problem or what's causing it either...
Same issue here. Works 100% from home screen or Google search/now. Very unreliable everywhere else
snowblind2142 said:
Everyone still having the same issue? I am still no solution, can't identify the problem or what's causing it either...
Click to expand...
Click to collapse
After making S-Voice a Phone Admin, the problem appears to have been solved - for myself at least. S-Voice still has some issues recognizing my voice if I'm in a particularly loud area, but I can always count on it otherwise.
Just a suggestion (for those who haven't tried yet): Try to record your wake-up command in different ways to help its accuracy (kind of like how you did your fingerprint). Oh and be as relaxed and natural as possible :good:
Can you elaborate on making s voice a phone admin please?
shinasurada said:
Can you elaborate on making s voice a phone admin please?
Click to expand...
Click to collapse
I assume he means in accessibility. I did this but still seemed to have the problem but will try again. I even left double home tap as s voice as I heard it makes it "always wait" to be pressed, and I assumed this would ensure it was running in the background.
Will let you know if it solves the issue for me.