Im looking for a ROM or maybe a Kernel would work as well?
Either way some sort of software that would give me a reasonably stock android experience, but would also disable the capacitive buttons on the ONE and add android on-screen buttons.
Anyone care to point me in the right direction?
Related
I would like to find a way to modify the amount of time the backlight is on for the bottom buttons. I know there is a MOD that uses these for notification in place of the LED we don't have; so I am guessing someone knows how to modify this setting. I would like to be able to make the backlight remain on anytime the screen is on. I am more than willing (and would actually like to) to do the work if someone here can get me started.
Thanks
Jeff
no one has yet found a way to do this, not sure if it's possible, but who knows.
https://github.com/project-voodoo/backlightnotification/tree/master/liblights/
^ that's neldar's work for backlight notifications, lights.c is the modified file and lights.c.original is what was modified. go ahead and play with that to see what you can find out.
Thanks for the info and link. I will certainly look into it and see what I can do. Persistance may pay off eventually!
Jeff
actually the epic 4g has this setting built in. on that phone the slide-out keyboard back light has the same timer as the 4 soft keys and you have the option to sync both to the screen.
so maybe posting over there to or just getting the epic source would help.
a.vandelay said:
actually the epic 4g has this setting built in. on that phone the slide-out keyboard back light has the same timer as the 4 soft keys and you have the option to sync both to the screen.
so maybe posting over there to or just getting the epic source would help.
Click to expand...
Click to collapse
the setting is still tied to liblights.c and it isn't tied to the length of the screen timeout, it's the softkeys tied to the keyboard keys (which use the same settings/binary)... the keyboard is just an extension of the softkeys so the solution would still lie in modifying liblights.c
Just get one of the i9000 roms with the setiron kernel, it has backlight notifications among other things.
I know a lot of people aren't happy with HTC getting rid of the multitasking button. Is it possible for devs to add on-screen buttons onto the One? You'll lose screen space and it'll probably look weird, but you'll get a proper multiasking button back and bring all the benefits of on-screen buttons as far as customization and stuff go. Any thoughts?
B757-200 said:
I know a lot of people aren't happy with HTC getting rid of the multitasking button. Is it possible for devs to add on-screen buttons onto the One? You'll lose screen space and it'll probably look weird, but you'll get a proper multiasking button back and bring all the benefits of on-screen buttons as far as customization and stuff go. Any thoughts?
Click to expand...
Click to collapse
Some think there may be hope in mapping the "HTC" logo to a button task......HERE
In Touchwiz adding on-screen buttons is as easy as adding a line to build.prop file (needs root). Does it work the same in Sense ROMs ?
craftycarper1 said:
Some think there may be hope in mapping the "HTC" logo to a button task......HERE
Click to expand...
Click to collapse
I def would prefer on screen then worrying about remapping a button that plainly wasn't suppose to be one. Disable cap and on screen only. Enable cm customization and profit (once available).
doakills said:
I def would prefer on screen then worrying about remapping a button that plainly wasn't suppose to be one. Disable cap and on screen only. Enable cm customization and profit (once available).
Click to expand...
Click to collapse
both buttons are just areas on the touchscreen (digitizer) with backlights and a symbol, the htc logo is no different (well i don't know if it has a backlight) but it's just another area on the digitizer
yea on-screen button is so much more better..at the bottom center and transparent
CreepyDroid said:
In Touchwiz adding on-screen buttons is as easy as adding a line to build.prop file (needs root). Does it work the same in Sense ROMs ?
Click to expand...
Click to collapse
Just FYI it won't boot for me when I add the line.
I'm using a custom Sense 5 rom, and was wondering how do you enable it. I already tried the build.prop trick, but it didn't work. Anything i'm missing? Yes I know there's the capacitive buttons, but there's already a on-screen menu button. Might as well turn it into the whole nav button. And yes, I know I can disable the on-screen menu button, but I like to SEE if there's a menu button in the app. Plus i'm coming from a GNex, so i'm used to the nav bar.
Anyone?
I want softkeys as well, but my experience is that it doesn't work with other than cm/aosp roms. Anyone that knows why or a workaround?
I've already got a great app to dim my capacitive buttons completely (there's only two, no need to awkwardly guess where they are), I would like to know if anyone has found a working solution for enabling Nexus-style software navigation keys.
If not, are there any developers willing to figure it out?
Anyone?
I tried the build.prop hack to no avail, so that's a no-go.
I just switched to maclaw's PACman ROM and I want to use the built-in android soft buttons, I want to know if there's a way to both disable the capacitive buttons themselves and the lights they have, I know it's possible using the stock ROM but I don't really want to use Touchwiz.
DustArma said:
I just switched to maclaw's PACman ROM and I want to use the built-in android soft buttons, I want to know if there's a way to both disable the capacitive buttons themselves and the lights they have, I know it's possible using the stock ROM but I don't really want to use Touchwiz.
Click to expand...
Click to collapse
There's suppose to be a setting to turn off capacitive buttons but its not available in all maclaw's rom, i dont know why