Develop Bugs

What's the point of software keys if they aren't being used properly?

I'm hoping the discussion in this thread can inspire devs to really tweak Android.
An article I read a while back through Daring Fireball really got me thinking on how to fix the back button. This quote in particular:
They’ve replaced dumb hardware buttons with equally dumb software buttons.
Click to expand...
Click to collapse
http://daringfireball.net/linked/2012/01/16/android-buttons
This is also a good discussion on the topic:
http://www.theverge.com/2012/4/10/2...uidelines-update-settings-navigation#98209921
This is what I've come up with:
The back button should be dimmed or not visible at all when looking at the home screen.
This should also be the case for looking at the home/main scene of an app, for this reason:
The back button should never take you out of an app to the home screen, that is what the home button is for.
Instead of using the back button to close apps, use the task switcher to swipe away and actually close unwanted apps.
I know all this is possible, I just don't know how feasible it would be. I would love to see these changes in Android, what do you think?

I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Having it on the home screen maintains a consistent look that many people appreciate. What i find is fantastic now is how the button rotate to the right place regardless of orientation, I KNOW that if I'm in landscape, the buttons will always be on the right hand side.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.

I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.

If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
EDIT:
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
The Android Documentation states that developers should save their data when onStop is called. onStop will be called both when user presses the home button, and when users presses the back button. So in theory, both buttons should work fine.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
Click to expand...
Click to collapse
Yes, that's an API. It's possible to dim those buttons in some apps(like gallery/camera), and it's also possible to hide those buttons. The buttons will re-appear as soon as the user touches the screen. Look at the YouTube app if you want to see the buttons disappear and re-appear.

fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
Click to expand...
Click to collapse
I agree. I dont think it is "broken". It works well for me and I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.

Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
I'm not talking about force closing apps, just regularly exiting apps only when they are swiped away from the multitask menu. I agree with everything else.
miketoasty said:
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
Click to expand...
Click to collapse
I'm not talking about removing the icons altogether, just make them contextually aware.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
Click to expand...
Click to collapse
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
fifarunnerr said:
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
Click to expand...
Click to collapse
I don't think that should happen. I realize that I'm arguing against actions Android has done since it's inception, but I believe that they are wrong now.
fifarunnerr said:
The home button doesn't close the app, but tells the app that it's moved to the background.
Click to expand...
Click to collapse
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.

juliano_q said:
I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Click to expand...
Click to collapse
The same is for me as well, muscle memory is much faster. I just think the potential of the virtual back button is not even being scratched at yet.

thereddog said:
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
Click to expand...
Click to collapse
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
Click to expand...
Click to collapse
In some cases, the back button would fit better. When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).

In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
Click to expand...
Click to collapse
I actually agree with this. The back button would be used to to back into the store. GMail was never really opened though so it wouldn't have to be closed.
When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
Click to expand...
Click to collapse
In this case, I believe it is up to PayPal to have a Log Off button on the main scene of their app, and possibly in a context menu in other scenes.

although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.

martonikaj said:
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
Click to expand...
Click to collapse
Maybe not disappear, dim would work

thereddog said:
Maybe not disappear, dim would work
Click to expand...
Click to collapse
Possibly. But I think what you're looking for is a fundamental reworking of the OS here. The "Back" button is meant to work a certain way (completely at the OS level), and changing that changes everything.
What you're really looking for is the iPhone setup, where all you have is a "Home" and "Multitasking" (just double tap home, could be a separate button). All "Back" functions are handled at the app level, not the OS level. Back buttons are placed at the discretion of the developer.
The consistency provided by the Android way of handling "Back" at the OS level has many advantages I think.

The software keys actually work great. I've never had a problem with them. The menu key always comes up when its needed and I'm not finding myself missing the search key either.
Sent from my Galaxy Nexus using XDA

the whole back button talk has got me thinking. do you guys think the back virtual button will go away any time soon since the new style guides want a back button in the top left corner.?

The way the android back button works is simply brilliant and I hope it never changes. The application stack is very thoroughly thought out and designed for a specific reason. As already mentioned there are many examples/situations that wouldn't be possible if there was no activity stack history with the back button function. You just have to learn how the activity stack works.
And yes you should ALWAYS use the back button to leave an app, never home. It clears that activity stack. Only time to use home is when you want to background said app to come back to later, ie multitasking.

I pray to god they don't change the way the back button functions. I like having all my keys lit up whenever I'm not using a full screen application. I like that the back button goes through different apps/pages when you close out of it. This just integrates multi-tasking soooo much better. I don't want to have to wade through different clicks and apps just to get to a place I was before (i.e. backing into a different application). I'm not sure I understand the premise of this... please elaborate?

It is entirely possible to implement this in the OS, it's just a question if Google wants to do this. I personally am well adapted to Android's back button, and find it much better for multitasking than Apple's iOS design. Example:
1. Open Twitter, click on link from Tweet
2. Android opens the browser, I read whatever was posted, then hit back
3. I return to my Twitter feed, ready to move onto the next Tweet
This works in a multitude of apps, from Reader to Google Music to anything that wants to keep the previous app alive in the background. Can you imagine having a back button in the Browser that could both take you back a page and also take you back to the app you used to launch it? Apple's iOS solves this by eliminating any form of efficient multitasking in my opinion, as you have to double press home and select the previous app. The iPad does it better with gestures, but a soft back-key would easily suffice.
Additionally, Apple's iOS also has a varying design for the back-key, it's in different places for different apps. I personally love the static back-key on Android, and I've used both on a daily basis. You could dim the back button when on the home screen, but that would leave a gaping hole in the Navigation bar, in addition of wasting RAM/Processing power continuously disappearing and reappearing the key when you move from home-screen to app.

Decrease Multitasking Menu Delay?

Been searching around, but couldn't find anything directly on this issue--
Is there any way to decrease the time that you need to hold the Home button to get the multitasking menu to pop up? As a side note, I've already disabled animations in the Developer Options, which helps to cut the time that it takes for the multitasking menu to become usable.
Thanks in advance.

davidrqli said:
Been searching around, but couldn't find anything directly on this issue--
Is there any way to decrease the time that you need to hold the Home button to get the multitasking menu to pop up? As a side note, I've already disabled animations in the Developer Options, which helps to cut the time that it takes for the multitasking menu to become usable.
Thanks in advance.
Click to expand...
Click to collapse
well idk if this will be useful, but just use a gesture on a launcher to open up the multitasking menu. I didn't like how long the delay was either so now all I have to do is pinch n zoom with apex launcher and it opens it up.

davidrqli said:
Been searching around, but couldn't find anything directly on this issue--
Is there any way to decrease the time that you need to hold the Home button to get the multitasking menu to pop up? As a side note, I've already disabled animations in the Developer Options, which helps to cut the time that it takes for the multitasking menu to become usable.
Thanks in advance.
Click to expand...
Click to collapse
Disable S-Voice if you're not using it , it adds about half a seconds to long press waiting for double click action.
Its under S-Voice settings menu , and or just freeze the whole application.

CaLiSwEEPeR said:
well idk if this will be useful, but just use a gesture on a launcher to open up the multitasking menu. I didn't like how long the delay was either so now all I have to do is pinch n zoom with apex launcher and it opens it up.
Click to expand...
Click to collapse
I've been considering that, but I generally don't like mucking with launchers. We'll see, though--thanks for the suggestion.
ghost77 said:
Disable S-Voice if you're not using it , it adds about half a seconds to long press waiting for double click action.
Its under S-Voice settings menu , and or just freeze the whole application.
Click to expand...
Click to collapse
Do you mean disabling the double-tap to launch or the entire application? The former doesn't seem to impact the multitasking menu launch delay, and I'd rather not go with the second option.

davidrqli said:
I've been considering that, but I generally don't like mucking with launchers. We'll see, though--thanks for the suggestion.
Do you mean disabling the double-tap to launch or the entire application? The former doesn't seem to impact the multitasking menu launch delay, and I'd rather not go with the second option.
Click to expand...
Click to collapse
no problem I hope you find a solution!

Anyone have additional ideas on this? Thanks!

I read that Wanam was working on a "no home button lag", coming son I guess.Keep an eye on the dev forum during the week to see if it pops up. I know it will sooner or later.

The JB roms we have have virtually no delay for the recent app window.

'Button Savior', I liked it so much I ended up getting the paid version. There is a free version to try. This allows me so much control without having to beat up my hardware buttons. Even the volume. Use it with a different launcher or not. It works either way.

DudeWatsThat said:
I read that Wanam was working on a "no home button lag", coming son I guess.Keep an eye on the dev forum during the week to see if it pops up. I know it will sooner or later.
Click to expand...
Click to collapse
I think that was applicable only to short-pressing the menu button (disabling double-tap to launch Siri gets rid of this delay anyways), and not the long-press Recent Apps menu, unfortunately.

[JB][BUG] Using home button to wake device always returns to launcher

As some have now noticed, there is a new bug in JB related to waking the device using the home screen under certain configurations.
[size=+1]How to reproduce:[/size]
Set lockscreen to None (might affect others types?? - default Swipe is NOT affected)
Open any app
Lock screen with power button
Press home button
[size=+1]Expected result (and how it worked in ICS):[/size]
The phone wakes, and you're back at the app you had opened before locking the screen
[size=+1]Actual result:[/size]
The phone wakes, but the home key press is processed as if the phone WAS NOT asleep.
In other words: it's like you hit the home key and you're taken to the launcher as normal. Or alternatively, if you locked the phone while at the launcher, whatever action you have configured for the home key in the launcher is triggered (for example, opening the app drawer).
[size=+1]Some notes:[/size]
Tested with both stock TW launcher and Apex - same result
Tested after OTA update, and full wipe - same result
[size=+1]Some related topics for a possible fix:[/size]
http://forum.xda-developers.com/showthread.php?t=2009218
http://forum.xda-developers.com/showthread.php?t=1836758
I've tried these suggestions in various combinations... so far no fix that works.
So lets see if we can use our collective intelligence and fix this.

Yes please! It's bugging me like hell!

After some further testing:
If you have S-Voice installed, and the "Open via the home key" option enabled, this bug will not happen.
Which is fine and good if you want a 1 second delay every time you press the home button.
And who wouldn't want that - right Samsung? /sarcasm

any fix for this yet?
nvmd, looks like the fix could be here http://forum.xda-developers.com/showthread.php?t=2009218

nope, so far the existing solutions do not work

radeon_x said:
As some have now noticed, there is a new bug in JB related to waking the device using the home screen under certain configurations.
[size=+1]How to reproduce:[/size]
Set lockscreen to None (might affect others types?? - default Swipe is NOT affected)
Open any app
Lock screen with power button
Press home button
[size=+1]Expected result (and how it worked in ICS):[/size]
The phone wakes, and you're back at the app you had opened before locking the screen
[size=+1]Actual result:[/size]
The phone wakes, but the home key press is processed as if the phone WAS NOT asleep.
In other words: it's like you hit the home key and you're taken to the launcher as normal. Or alternatively, if you locked the phone while at the launcher, whatever action you have configured for the home key in the launcher is triggered (for example, opening the app drawer).
[size=+1]Some notes:[/size]
Tested with both stock TW launcher and Apex - same result
Tested after OTA update, and full wipe - same result
[size=+1]Some related topics for a possible fix:[/size]
http://forum.xda-developers.com/showthread.php?t=2009218
http://forum.xda-developers.com/showthread.php?t=1836758
I've tried these suggestions in various combinations... so far no fix that works.
So lets see if we can use our collective intelligence and fix this.
Click to expand...
Click to collapse
No bug in here. I did what you said and after i press home button i get back to app not home screen.

that's very weird, many people I've read on XDA have this problem.
What launcher do you use?
Are you using 4.1.1. stock rom?

norbarb said:
No bug in here. I did what you said and after i press home button i get back to app not home screen.
Click to expand...
Click to collapse
Did you see my follow up?
You probably have S-Voice enabled on home button double press, right?

radeon_x said:
Did you see my follow up?
You probably have S-Voice enabled on home button double press, right?
Click to expand...
Click to collapse
No i have google now on home button

norbarb said:
No i have google now on home button
Click to expand...
Click to collapse
Same difference, I guess. The problem is only present when you don't have a double-press function assigned on the home button.

radeon_x said:
Same difference, I guess. The problem is only present when you don't have a double-press function assigned on the home button.
Click to expand...
Click to collapse
that explain..

norbarb said:
that explain..
Click to expand...
Click to collapse
Sorry to ask but I am also very irritated with this bug. How do you guys set this option for google? I don't want S Voice.

jkabooter said:
Sorry to ask but I am also very irritated with this bug. How do you guys set this option for google? I don't want S Voice.
Click to expand...
Click to collapse
I use Home Button Shortcut

[Q] Anyone know of a way to get menu overflow button?

Anyway to get the menu overflow button into all apps and disable menu key or make it multitask key? Xposed modules or Roms? I loathe the menu key. All of my other devices have software buttons so I'm always thrown off when going to my note. Thanks

supremekizzle said:
Anyway to get the menu overflow button into all apps and disable menu key or make it multitask key? Xposed modules or Roms? I loathe the menu key. All of my other devices have software buttons so I'm always thrown off when going to my note. Thanks
Click to expand...
Click to collapse
xposed module: 3-dot menu mod do the job(add soft menu key). Install it, activate in xposed and restart.
PS. And Samsung did it again wrong, because the menus are ugly in all their apps (light grey icons on a white background).

delete

Good stuff. This restored the 3 dot menu in Chrome after Google yanked it out in the last update.

I peronwly love the menu button

Duly.noted said:
I peronwly love the menu button
Click to expand...
Click to collapse
Agreed.
Sent from my SCH-I545 using Tapatalk

wingdo said:
Agreed.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Now to find a way to turn the menu button into a task switcher button and set long press home to google now

Youre right ... Listen to me get xposed modules install gravity box jellybean version... and use their pie controls.... make them appear on left side.... so use ur left thumb to acces home button and recent task on pie.... and your right thumb for the return button ... i know the feels... since that threw me off too ... this way you can comfortably navigate without sacrificing screen estate... .. trust me it rocks... contact me if you have more questions .. youre welcome

rajackar said:
Now to find a way to turn the menu button into a task switcher button and set long press home to google now
Click to expand...
Click to collapse
Long press home to Google Now can be done with Xposed. Both my phone and tablet work like that. I use Switchr for task switching with the activator in the bottom left and Button Savior Pro on the bottom right.

mine does that automatically. it also tried opening dolphin for some reason LoL

Navigation Bar Questions

Got my G3 today and have been spending a good amount of time setting it up.
I am rooted and have Xposed w/G3 Tweaksbox.
I have a couple of things that still annoy me.
Is there a way to swap the behavior of the recent apps button? I want short press to be menu and long press to be recent apps. I figured out I can add a menu button using G3 Tweaksbox that does exactly that, but I can't remove the stock recent apps button, so I have 4 buttons there and I don't really like that.
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?

lexluthor said:
Got my G3 today and have been spending a good amount of time setting it up.
I am rooted and have Xposed w/G3 Tweaksbox.
I have a couple of things that still annoy me.
Is there a way to swap the behavior of the recent apps button? I want short press to be menu and long press to be recent apps. I figured out I can add a menu button using G3 Tweaksbox that does exactly that, but I can't remove the stock recent apps button, so I have 4 buttons there and I don't really like that.
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
Click to expand...
Click to collapse
Most modern apps use the 3 dot menu button in the app interface and that is why most modern phones tablets do away with dedicated menu button so why would you want to do this?

rkirmeier said:
Most modern apps use the 3 dot menu button in the app interface and that is why most modern phones tablets do away with dedicated menu button so why would you want to do this?
Click to expand...
Click to collapse
Probably because I'm used to it coming from the Galaxy S3.

lexluthor said:
Probably because I'm used to it coming from the Galaxy S3.
Click to expand...
Click to collapse
You'll get used to the new buttons in no time. Just give it a little time and you'll look back at the S3 thinking the button layout was dumb.i had an S3 and S4. Love the G3 and the on screen buttons!

rkirmeier said:
You'll get used to the new buttons in no time. Just give it a little time and you'll look back at the S3 thinking the button layout was dumb.i had an S3 and S4. Love the G3 and the on screen buttons!
Click to expand...
Click to collapse
We'll see.
Anyone have a solution to my other issue?
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?

I have the exact thing you want; but I don't want it. I'm rooted with Xposed framework and I randomly rebooted my phone earlier to have it turn back on with a functioning menu button. I looked through all the modules I had downloaded and even booted into safe mode but to no avail. I desperately need help with this.

Sorry that's not what you want, but if anyone knows how to get that, that's why I want.

I'm rooted with Xposed framework and I randomly rebooted my phone earlier to have it turn back on with a functioning menu button. I looked through all the modules I had downloaded and even booted into safe mode but to no avail. I desperately need help with this.
Sorry for reposting this... Thought I posted in a different thread but I guess I'm wrong. Please don't crucify me

As a long time samsung user, I'd say try without the menu button and see how you get on first.
But you can change the swipe up (and thats a swipe up from anywhere on the navigation bar btw, try it out), using tweaksbo, it's under:
theme > ring pad
And you can either turn it off, or add up to 5 custom apps.
The recent apps button is kinda key to android, it's like asking to remove the home button. Maybe instead of adding a menu button, make double tap on home be the menu button instead? Then you'd still have your three icons, and wouldn't lost out on recent apps, which you should end up using more now it's easier to reach (as opposed to a long press on the home button on samsung).

As noted most apps should use the 3 dot menu button so unless you have an outdated app you use regularly you really shouldn't even want a dedicated menu button. Ask the developer to update the app. It's the way forward and most all modern phones don't have a dedicated menu button, even the S5 replaced the menu button with the multitask button. It you really can't adapt ask the G3 Tweaks xposed developer if he can add a menu button option as the G3 already has the framework to change nav buttons.

How can you change them?

steviewunderr said:
How can you change them?
Click to expand...
Click to collapse
Just use the LG Display menu in settings to remove that button and xposed to add other button options. I'd like to know what people use, I'm on a 4 button system. I'll post pics when I get a chance

I somehow managed to change them on a system level if that's even possible. I disabled all modules and even booted into safe mode and they were still there. I'd like to change it back on whatever level it got modified. And the settings app crashes when I try to change the button combination.

The OP did not want to replace the resents button with menu, but only change its behavior: short press - menu, long press- resents. I am very interested in the same setup.

lexluthor said:
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
Click to expand...
Click to collapse
In TweaksBox under theme tweaks, then ring pad. It let's you select one in the free version. In the donate version you can select up to 5 shortcuts in the ring pad or disable it altogether.

settings / display / home touch buttons / button combination
I think they are standard options and not something I've added in. let's you add/remove a button such as the menu button or recent apps. screen is wide so I use 5 buttons.
Sent from my LG-D855 using XDA Premium 4 mobile app

personally don't use program #1 the ring selector as it is accidentally opening all the time with use of the back button.
Sent from my LG-D855 using XDA Premium 4 mobile app

Hold the recents and thats your menu button. Thats a default setting i believe. No need for g3 tweakbox unless a longpress isnt what you want. Idk which model you have but the tmobile version doesnt let you add the menu button on the nav bar.
Sent from my LG-D851 using XDA Free mobile app

lexluthor said:
We'll see.
Anyone have a solution to my other issue?
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
Click to expand...
Click to collapse
Did you ever find an answer that I'd love to able stick a few more bits on there seems like the only thing lg have forgotten let customise! Lol

jonny_blagwind said:
Did you ever find an answer that I'd love to able stick a few more bits on there seems like the only thing lg have forgotten let customise! Lol
Click to expand...
Click to collapse
G3 Tweaksbox,theme, ring pad, disable ring pad.