OK I have a modded Verizon galaxy nexus with 4.0.4,in tab mode. Every thing is customized ,except one thing....with that said, I bring you to my question. Can you make a call button for the navigation menu,. My reason for that is there are two menus one on screen and the other on the navigation bar.a standard call button on that bar would make more space thus elements the on screen menu bar altogether. CAN U DO IT. send answers to [email protected] thanks.
I got a G2 from my friend and 4 navigation buttons on phone bottom cannot use
And now my rom is "Andromadus Test builds CM10"
How can i show the virtual navigation bar (Like tablet or Galaxy Nexus) on my G2?
Hey guys:
I have enabled the Navigation Bar on my Note II, but now there are a few issues and I was wondering if anyone knows how to resolve them.
Basically I have:
Recent Apps | Home | Back
When I rotate to landscape, the keys are really messed up (tiny and all crammed in)
Also, I am coming from a Galaxy Nexus, with AOKP so I am looking to edit the softkeys so that I have a persistent menu button and a back button in the other side, also a search button.
I have tried some editing of the. kl files in /system and editing the framewrok-Res.API and I either get keys that don't work, or a bootloop.
I am running an i317m, so am currently running Saurom. Does anyone have any insite on how to fix the navbar rotation issue/customize the keys?
Thanks
Sent from my Galaxy Note II on Rogers Wireless
Anyone successfully enable on the onscreen nav keys on the Mini? I'm using the Mini as a running/biking gps device and use it in a forearm cradle that covers the capacitive keys. Would be nice to enable the on screen nav keys, but the build prop edit to do so causes the System UI to crash. Basically you add the line
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
to the end of the build.prop and reboot. Haven't been successful with it.
Anyone else try?
Hi guys,
Ok, so I'm coming from an old Nexus 4 on which I was used to do everything with one hand (right).
I was used to Pie Control, and completely remove my software navigation bar (qemu.hw.mainkeys=1 in build.prop)
Now, I'd like to do quite the same thing with my OP3, but I'm struggling a bit.
As you know, with OOS, we can use either:
Capacitive Buttons
On-screen navigation bar
When I use Pie Controls (either LMT or GravityBox) and set the navigation to capacitive buttons, it's mostly OK, but there's always the unintentional touch, especially when holding the device in landscape mode.
When I set the navigation to on-screen buttons (but don't use them), "Back" and "Home" simple tap on Pie Control doesn't work at all (Longpress's and Recent simple tap work fine, though).
I tried fiddling with build.prop but didn't manage to disable both altogether.
Code:
# enable navigation bar
#ifdef VENDOR_EDIT
#[email protected] disable navigation bar
#qemu.hw.mainkeys=1
#else
qemu.hw.mainkeys=0
#endif
Anyone knows how to disable both capacitive buttons AND standard software navigation bar ?
If it's possible to stay on OOS for the moment, that would be great
Thanks in advance.
Yes, something is strange in OOS in that respect.
I use GMD Gesture Control (like I do always on every device), but if I use the on-screen navbar instead of the capacitve buttons, "back" gesture doesn't work anymore. Home gesture works.
Perhaps someone could shed some light onto what the causes could be...
Anyone find a fix for this?