Anyone else find that the home button will no longer light the S view window. The on/off button and the volume button does but not the home button as in the past.????
dacbeth said:
Anyone else find that the home button will no longer light the S view window. The on/off button and the volume button does but not the home button as in the past.????
Click to expand...
Click to collapse
Same issue here. Friend with same situation also did a factory reset, which didn't help.
mihaelb said:
Same issue here. Friend with same situation also did a factory reset, which didn't help.
Click to expand...
Click to collapse
I haven't found an answer?
dacbeth said:
I haven't found an answer?
Click to expand...
Click to collapse
other than using the power button to turn it on, and crossing my fingers that this will get re-enabled in Android 4.5/5 around July/August, no :/
Also annoyed that the auto-brightness+ setting is now gone, but that at least was fixable through the Lux app.
Brightness button did not disappear on mine. Sprint S4
Any solution for the home button?
It's a world wide issue with all tw KitKat updates.
Sent from my SPH-L720 using Tapatalk
Hi there,
Any solution till now?
Some hack, xposed module, alternatives?
Gachmuret said:
Hi there,
Any solution till now?
Some hack, xposed module, alternatives?
Click to expand...
Click to collapse
Couple alternatives. Wanam with Xposed could fix it. Also, a different launcher would let you set it too.
VandyCWG said:
Couple alternatives. Wanam with Xposed could fix it. Also, a different launcher would let you set it too.
Click to expand...
Click to collapse
Thx bud,
I don't think that the prob is from the launcher, as it doesn't work with other launchers neither (I don't use TW, also it is working normally with s-view cover opened).
I have Wanam with xposed, but don't find any option like that... could you help me out? Thx a lot!
I found another strange issue, don't know if you have it , too. If I deactivate auto-unlock when I open s-view cover, it still unlocks when I open it... even after restart.
Edit: Found the solution for other issue: Nils Notification was set to always unlock when cover opened, nothing to do with rom... My fault
Gachmuret said:
Thx bud,
I don't think that the prob is from the launcher, as it doesn't work with other launchers neither (I don't use TW, also it is working normally with s-view cover opened).
I have Wanam with xposed, but don't find any option like that... could you help me out? Thx a lot!
I found another strange issue, don't know if you have it , too. If I deactivate auto-unlock when I open s-view cover, it still unlocks whne I open it... even after restart.
Click to expand...
Click to collapse
In Wanam, under System, there is a section for Long Home key behavior, can you not, Launch S Voice from there?
I use Google Now, and this is how I launch that.
As for S-view, I can't help with that, I dont have that.
Related
Hi guys,
I would like to hear any recommendations or experience from you. What is the way you used to hide soft keys and use pie control?
I found many apps in the market or this xposed thread. I have rooted D802 and I would like to follow some well working combination instead of spending time to install & try & uninstall.
Thanks a lot for answers.
p.valenta said:
Hi guys,
I would like to hear any recommendations or experience from you. What is the way you used to hide soft keys and use pie control?
I found many apps in the market or this xposed thread. I have rooted D802 and I would like to follow some well working combination instead of spending time to install & try & uninstall.
Thanks a lot for answers.
Click to expand...
Click to collapse
Install lmt launcher and set pie up.
http://forum.xda-developers.com/showthread.php?t=1330150
Then add this to the bottom of build.prop, it disables the soft keys without an app.
qemu.hw.mainkeys=1
Do it with an build.prop editor to get the right permissions and so on.
Cheers.
qsec said:
Install lmt launcher and set pie up.
http://forum.xda-developers.com/showthread.php?t=1330150
Then add this to the bottom of build.prop, it disables the soft keys without an app.
qemu.hw.mainkeys=1
Do it with an build.prop editor to get the right permissions and so on.
Cheers.
Click to expand...
Click to collapse
Thanks, works great! :victory:
I got only one issue:
I got FC message when connect USB cable, headphones. I think it's related to "LG animation of plugging cable" on the bottom of screen (attachment). Do you have it same? Did you solve it somehow?
p.valenta said:
Thanks, works great! :victory:
I got only one issue:
I got FC message when connect USB cable, headphones. I think it's related to "LG animation of plugging cable" on the bottom of screen (attachment). Do you have it same? Did you solve it somehow?
Click to expand...
Click to collapse
I have the same issue as well. Then all of a sudden it started to work again, I have no idea why tho.
Tapatalked.
qsec said:
I have the same issue as well. Then all of a sudden it started to work again, I have no idea why tho.
Tapatalked.
Click to expand...
Click to collapse
Well, that FC bothered me so much that I made Xposed Mod to get rid of it. If you will experience it again, you can get it here.
p.valenta said:
Well, that FC bothered me so much that I made Xposed Mod to get rid of it. If you will experience it again, you can get it here.
Click to expand...
Click to collapse
Thanks, but I have moved on to Nexus 5.
Tapatalked.
Hello,
I already started to solve my problem in the SView-Mod-Thread, but before I spam it with too much off-topic, I created a thread in the right place.
The problem ist self-explaining, since the update to KitKat and UENB ROM, SView is working properly for the genuine SView-Cover. I am using the Spigen S View Cover and this cover has a home button, in detail it has a lay-in in the front cover to push the home button of the phone. On 4.3 it was possible to wake up the device with the home button, also it was possible to activate the torch by pushing the VolUp button. On 4.4 it is neither possible to wake up the device with the homebutton nor activate the torch.
It seems that some users have the possibility to use the buttons, but no one can explain what they did or what the reason is. So anyone, who could give some advice, how it is possible to reactivate the buttons in closed mode?
THanks in advance.
Silberpfeil3110 said:
Hello,
I already started to solve my problem in the SView-Mod-Thread, but before I spam it with too much off-topic, I created a thread in the right place.
The problem ist self-explaining, since the update to KitKat and UENB ROM, SView is working properly for the genuine SView-Cover. I am using the Spigen S View Cover and this cover has a home button, in detail it has a lay-in in the front cover to push the home button of the phone. On 4.3 it was possible to wake up the device with the home button, also it was possible to activate the torch by pushing the VolUp button. On 4.4 it is neither possible to wake up the device with the homebutton nor activate the torch.
It seems that some users have the possibility to use the buttons, but no one can explain what they did or what the reason is. So anyone, who could give some advice, how it is possible to reactivate the buttons in closed mode?
THanks in advance.
Click to expand...
Click to collapse
Xposed framework... Allows the use of torch using volume buttons when screen is off.
Not sure if the "home button" is supported by the sview case mod....
ultramag69 said:
Xposed framework... Allows the use of torch using volume buttons when screen is off.
Not sure if the "home button" is supported by the sview case mod....
Click to expand...
Click to collapse
My ROM supports the genuine Samsung torch, that is enabled with VolUp, no Mod needed. This Mod doesn't change the behavior of the buttons at all, so there must be another way. And I am looking around for it since a while now, because it annoys me to not be able to use the full functionality of my cover.
Gesendet von meinem SM-N9005 mit Tapatalk
Having The same issues with the spigen s-view cover and it is most annoying
+1, did anyone find a solution?
Same problem here. Also Galaxy S4 (not SII as my sig says..) with Spigen Armor View in combination with 4.4.2. Anybody got a olution yet?
It's a pity that Samsung always changes the running system. Maybe some users complained about false wakeups because of pushing the button through the cover. Samsung neverminds about third party accessoires.
We have to encounter, where the hardware button lock is triggered or maybe port the old SView apk to KK. But just too little knowledge about that on my side.
Gesendet von meinem SM-N9005 mit Tapatalk
No luck with this anyone
Sent from my GT-I9505 using Tapatalk
having the same issue. it drives me insane so much so that im debating rolling back to 4.2
This was one thing I noticed straight after I upgraded to KitKat, I have the official s view cover and I used the home button all the time to wake my phone up as it's just easier and I could do it with one hand. Now since Its been disabled I have use lock button which is just a pain in the arse! Also when on a phone call with s view cover closed I have to press the luck button, not big issues but I hate it when things get changed for no reason!
Sent from my SM-N9005 using Tapatalk
Let's all pray to the Android gods for a fix.
Dear Android Gods, please fix this one for me:angel:
bretto99 said:
Dear Android Gods, please fix this one for me:angel:
Click to expand...
Click to collapse
+1.. I have the same problem after 4.4.2 upgrade with spigen slim armor view cover.. Home button does not awake.. I would appreciate any advise
cemgec said:
+1.. I have the same problem after 4.4.2 upgrade with spigen slim armor view cover.. Home button does not awake.. I would appreciate any advise
Click to expand...
Click to collapse
+1 also i have the same problem with Spigen Slim Armor View after upgrade to 4.4.2
+1 here... Any news for the topoc? Any xposed module, hack, alternatives?
Thx for any advice as missing this function really made 4.4 unusable for me... Would like to downgrade to 4.3 but no way...
I have the samsung galaxy s4 and today i install the 4.4.2 and i have the same issue.
Is there any chance that samsung going to re-enable the home button support for 3rd party sview cases?
Hey all. I have enabled: both s-view xposed modules available and disabled the xuimod module. When I disabled that, my home button worked. Let me know if that works for you.
Sent from my SM-N900V using Tapatalk
So is there any solution for NON root mobile phones with 4.4.2?
And does samsung announcement anywhere that it solves this issue at the next update?
boostin91tsi said:
Hey all. I have enabled: both s-view xposed modules available and disabled the xuimod module. When I disabled that, my home button worked. Let me know if that works for you.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi, could you please explain some more? What exactly did you do to get it working? Thx!
Is there any chance to make home button work at 3rd party sview cases to NO ROOT mobiles?
If it can be done how exactly we can do that?
boostin91tsi said:
Hey all. I have enabled: both s-view xposed modules available and disabled the xuimod module. When I disabled that, my home button worked. Let me know if that works for you.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yes, more detail please. I've tried both sview modules in xposed framework and home button still dead with closed spigen slim armor cover.
Good morning all,
I feel so stupid for asking this, but the menu button does not seem to work the way my other androids did in the past. Is there a function that I need to turn on or something? Thanks
install GravityBox and reassign buttons)) or just try to long press Recent button
Ok will do. thanks for your help sir.
nickhowell25 said:
Good morning all,
I feel so stupid for asking this, but the menu button does not seem to work the way my other androids did in the past. Is there a function that I need to turn on or something? Thanks
Click to expand...
Click to collapse
Not sure if this is launcher specific but I'm using Nova Prime and if you long press the menu button, then the original menu items pop up instead of recent apps. I never test with TW launcher. Discovered this later. But this way you don't have to remap with gravity box.
Docmjldds said:
Not sure if this is launcher specific but I'm using Nova Prime and if you long press the menu button, then the original menu items pop up instead of recent apps. I never test with TW launcher. Discovered this later. But this way you don't have to remap with gravity box.
Click to expand...
Click to collapse
I'm not even sure what gravitybox even is. I tried to see if it was in the app storre. someone else in the thread recommended to do so....
FYI - the layout used in the S5 is the standard Android button layout and you will see fewer and fewer devices using a dedicated menu button, as there's no need for it in Android 4.x+
tdrussell said:
FYI - the layout used in the S5 is the standard Android button layout and you will see fewer and fewer devices using a dedicated menu button, as there's no need for it in Android 4.x+
Click to expand...
Click to collapse
okay. thanks for the info!
nickhowell25 said:
I'm not even sure what gravitybox even is. I tried to see if it was in the app storre. someone else in the thread recommended to do so....
Click to expand...
Click to collapse
Gravity BOX is a module that is installed after you first use Xposed Installer. Google this or look it up in a search here on XDA.
Hello, all. I'm trying to disable the home button. I've tried everything I've read and searched up, it's a no-go. It doesn't wake the phone which is halfway there but it still functions after the lockscreen. What am I doing wrong? Thanks.
totbl said:
Hello, all. I'm trying to disable the home button. I've tried everything I've read and searched up, it's a no-go. It doesn't wake the phone which is halfway there but it still functions after the lockscreen. What am I doing wrong? Thanks.
Click to expand...
Click to collapse
Root your phone, install xposed framework and install xposed additions from playstore, re-map your button with your fav. action :good:
boyrobbie said:
Root your phone, install xposed framework and install xposed additions from playstore, re-map your button with your fav. action :good:
Click to expand...
Click to collapse
Will try right now and get back to you. Thanks a lot. Hope it's that simple.
totbl said:
Will try right now and get back to you. Thanks a lot. Hope it's that simple.
Click to expand...
Click to collapse
let's me see
It didn't work for any of the capacitive buttons nor the home. But I'm already good with the capacitives through another method. Hardware home seems impenetrable. Anything else?
All right. I finally got it! I edited gpio-keys.kl (separate from the rest of the buttons from down there for some reason) and I added a # in front of key 172 HOME and saved it.
I don't know at which time this got activated, maybe its a "feature" of the CarHD mod I am using, but its so annoying and I cant find how to disable it. I googled it, searched it here and in the phone menu, but no luck. Taping the front camera notch locks the phone, and holding it brings up the power menu. Its so useless and annoying, because I press it by mistake and lock my phone. The actual power button is much more easy to press. Anyone has the same issue? Have you found how to disable it?
Thanks in advance.
There would be an option in the carhd rom control app, perhaps in the status at section
stefan243546 said:
There would be an option in the carhd rom control app, perhaps in the status at section
Click to expand...
Click to collapse
Finally! Thank you. I don't know how i missed that... Please delete this topic, I doubt it will be helpful to someone else.
Hello,
take a look here maybe it cans helps : https://www.digitaltrends.com/mobile/common-oneplus-6-problems-and-how-to-fix-them/
Tutuapp 9apps Showbox