Any work around for this? I do not use soft keys, and don't enjoy the reboot required
Bump, running an s5 on cm12 and I was really looking forward to this feature but with a reboot required every time I turn it on it's just not usable.
Related
Hi All.
Just got my DX last week. I am liking the DX, except for the bootloader issue and the back/home/menu/search "hard" keys. I really miss the "soft" keys on the D1. These feel a little awkward and I also worry that they will wear out or break over time.
I installed an app called "softkeys" that gives me a floating bar with on-screen back/home/menu/search buttons and I am pretty happy with that. I have also seen the soft key application that places the keys on the side of the screen and lets them slide in or out.
But I would love to find one that shifts the screen up to allow soft back/home/menu/search to always remain on the bottom of the screen and out of the way?
Is it possible? Anyone know of such an app?
Thanks,
Rob
This may or may not work for you. Use this at you own risk.
http://forum.xda-developers.com/showthread.php?t=850464
The soft key lights on this device seem to work differently then most other android devices with back light soft keys. I've been trying to figure this out for a while. When exactly does the phone decide to turn them off, and and why can't I turn them off using apps like screen filter, and even on the stock t mobile rom?
Is this a hardware or software issue?
What I know is that the soft key lights in kj6 (gingerbread) roms turn on every time you turn the screen on or touch the screen, and turn off after 3 seconds of inactivity (not touching the screen or pressing any buttons).
But it seems that in some situations the soft keys turn off and stay off, even when touching the screen, which is seemingly random. Why does it do this?
Does anybody know when exactly the soft key lights decide to turn off?
From what I can tell, the Team Acid ICS driver does what it is supposed to do -- turn on and off the lights when the magic number is written to the right sysfs location.
The control of the lights is supposed to happen in the Android world with PowerManager and LightsService. The "problem" is that it seems as though the chip that controls the touchkeys and their backlight have a mind of their own and turn on the lights when you touch them. This gets the Android world's idea of if they are on or not confused, resulting in LightsService not "turning off" the light as it thinks they are already off.
I'm working through a good way to resolve this. Messing with the framework code is not the best as it means that TeamAcid would have their own version, and keeping up with upstream changes would be more difficult. Unfortunately, how it was done in GB is something of a mystery as it isn't clear to me from the Samsung code drop.
https://github.com/teamacid/android_device_samsung_galaxys4gmtd/issues/32
Are the soft key lights on the sgs4g the same as the original us versions of the Samsung galaxy (the vibrant/captivate)? If they have a fix for this (I assume they might because they have a larger development community) , would it work for our device?
I'm looking into if I can find some dev information for the Cypress/Melfas key controller, and possibly the Atmel mXT224 and looking for other devices that use it (Motorola Atrix, for example). If I can disable the "LED on when touched" behavior, things are a lot easier.
i was wondering about this as well... my back button, is messed up and has no sensitivity at all so im trying to disable the whole bar and just use an onscreen nav bar. i know that paranoid as it in their settings but that rom eats up the battery like a mad man ill be down to zero by noon i dont get that problem with CM9 BUT CM9 doesnt have the onscreen Nav Bar
does any one know where i can find more info on adding this nav bar to CM9?
Aokp has it too
V1R3Z said:
my back button, is messed up and has no sensitivity at all
Click to expand...
Click to collapse
You might try Hefe Kernel Of Darkness (second post in that thread) to mainly turn off the touchkey backlight.
I'm curious as to what poor back-button sensitivity problems you are seeing. You can PM to keep the thread clean.
Am using daniel_hk's 4.2mr1 wonderful port as above. Having a problem getting editing navbar button changes stick. All I want to do is switch the order around lol not they match my s4 so I don't have to keep switching mindset. I know its not working right now... And here is what I know so far:
* ROM Control changes to navbar button transparency sticks, so its not a general ROM Control problem with applying settings.
* Button changes do not apply at all, either visually or in method, e.g. if I leave a button as it is but change the long press to another action, it will not change.
* I suspect that some other element of settings application is app,ying following ROM Control and overwriting the button changes.
* If the above is this case I am unable to find another setting section which allows me to edit button order/action so cannot correct the problem in that way.
* PIE is disabled. I'm not a fan, just personal taste but I'd rather lose half inch of screen space and not have to thumb for a button set every time. So I don't think PIE is the problem, unless ROM Control is trying to apply changes to PIE, not the navbar (though I assume they both reference the same button settings table if its coded efficiently).
Does anyone have any idea on what's wrong? I have spent hours fiddling and googling now and am at the end of my capabilities to fix this. Is there a problem with the ROM Control in AOKP itself with applying navbar button changes?
Any advice appreciated... or someone who has a 7.7 and has figured out how to bend the navbar button order to their will with some step-by-step replication instructions would be appreciated. Cheers.
Hello all,
Recently the power button on my Nexus 5 has been acting really weird. Sometimes it works flawlessly, others it requires pressing it really hard to work. In order to prevent it to stop working indefinetely, I am looking for a way to remap my volume-up button so it can work as a power button. I don't need it to turn my phone on or to work in the recovery mode (from what I read, it seems to be impossible), only when Android is running.
I've already tried some workarounds:
1) Volume Unlock Power Button Fix app: I tried it, but it just allowed me to turn on my phone with volume but not turning off. Also, it drains a LOT of power.
2) Buttonremapper app: It would theoretically do exactly what I wanted, but did not work at all.
3) Editing generic.kl: I tried switching volume-up and power buttons codes in generic.kl, but also did not work. Maybe I need to modify another file?
3) Xposed Framework + Additions: The installation of Xposed went Ok, but after installing Additions module I got stucked in bootloop. I am running Android 5.1 stock, maybe this module is not yet compatible.
So, can anyone help me? Do I need to install a custom ROM?
PS: I live outside US, so no warranty for me. Otherwise I would just use it
Thanks in advance for any help!
Cheers,
Humberto
Hi folks,
Just a heads up for anyone who might be facing the same issue. I decided to change from stock to Cataclysm ROM due to some specific features (listed below). After the installation, here's what I did to work around this problem:
1) Enabled "Volume wake" and "Sleep button on status bar" in "Cataclysm Settings / Miscellaneous".
2) Enabled "Swipe to sleep" and resized NavBar to 115% in "Cataclysm Settings / Navigation bar options". -> This way I can swipe in NavBar at any time (except lockscreen) to turn off screen. I raised it a little to facilitate the swipe gesture.
3) Changed Lockscreen Dialer shortcut to ""Turn off Screen" app shortcut (just search for it in the play store) in "Cataclysm Settings / Lockscreen options" -> This allows me to just swipe right and turn off the screen when my security settings are disabled (which accounts for most of the time). I found it way faster than pressing sleep button in status bar, especially when I'm driving and I can't look at the screen. Plus, I don't really use the dialer function of my phone so often since the invention of Whatsapp ;P
I realize this is not the perfect solution, but I don't see a better way to deal with this power button malfunction problem (except from a hardware fix).
Hope this helps!
Cheers,
Humberto
PS: I am really enjoying Cataclysm. It's a very nice ROM, completely stable and with a lot of other interesting features aside from the ones mentioned above. I strongly encourage anyone to give it a try!
I'm facing the exact same problem but I really need to eliminate the power button or I will need a power button fix soon.
The solutions you found hthiengo are good if not needing to turn off (or worst: running out of battery, something that happens me sometimes). I'm in the situation that next time I hit power button I will need to replace the button, or throw the nexus away
I did installed the xposed additions for lollipop but it is not working, and the Cataclysm trick is not enough in this case
Ok, after some research I've found a temporary solution:
For the power button you can remap modifying the file gpio-keys.kl under system/usr/keylaout (i wonder why anyone could figure out thise before, no that difficult). I would like to map power button leeaving it useless but I've found it impossible to remap the power button (probably because the key number is not 116). I would have liked to see xposed additions to help me map the keys but is not functional at least for me.
If the phone runs out of battery I've found that if I plug the power cable by pressing both volume buttons at the same time, eventually it starts up with the bootloader so I can plug the pc cable and it will reboot sucessfully.
So despite the phone know is pretty disfunctional (not the best phone for a hurry without battery), I can still use it for some weeks before I plan buying a new one or something (or I find a place for reparing). Its a shame I could not find a better solution for example, ADT when powered off so I could just reboot it by using ADT reboot command while powered off.
And It would be really amazing if the volume up button could also power it on from the powered off state.
In my case the power button is broken, but sometimes it gets stuck and puts the phone in a reboot loop: To avoid pressing the power button accidentally I've made a hole in the protective case so its pretty difficult to access it.
That's all for now. If anyone can make it better I will be glad to hear him/her
Hi guys!
I was wondering if there is an app or a tweak that I can use in order to customize the behavior of the buttons on our device, S2 PLUS. Shortly put, I would like to use the long-press menu button action to lock the device. I have searched for apps to lock/wake the device without using the physical button, but most of them use the proximity sensor or drain the battery - and I do not want apps that do that. Btw, I am running the stock version of Android 4.2.2 on my S2 PLUS, and the phone is rooted. Thanks!