I know there are many posts about this but it took me a while to understand how it works and there is no single thread which has the information gathered in the first post, so I decided to make this. Sorry if it uneeded.
Anyone who want's to use on screen NavBar buttons, he's lucky! (at least compared to ICS).
Now, by adding in
/system/build.prop
Click to expand...
Click to collapse
the line
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
you get the navigation bar (after reboot) and at the same time Android system recognizes this and adds the three dot menu icon whenever needed*!
If you want to disable the hardware keys, edit the file
/system/usr/layout/Generic.kl
Click to expand...
Click to collapse
These are the three hardware buttons
key 172HOME
key 158BACK
key 139MENU
Click to expand...
Click to collapse
Add a # before any you don't wan't to use any more. I did for 158 and 139 and left my Home button working.
There is a mod** (flash it in recovery) which makes the bar almost half the size. It's better looking and less space is wasted but it does get some time to get used to it and you might need a couple of tries sometimes when trying to hit those buttons.
*This wasn't the case for ICS.
**mod by houssam10001
http://forum.xda-developers.com/showthread.php?t=1960460
you can also do it via a framework mod
http://forum.xda-developers.com/showthread.php?t=1924327
Why would somebody use this on the s3? You got buttons under your screen already
Sent from my GT-I9300 using xda app-developers app
kahraman11 said:
Why would somebody use this on the s3? You got buttons under your screen already
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
For people to want it, there must be a reason.
I've got 2!
a) I accidentally press the back button when watching videos and is ANNOYING!
b) I am a "fast" user and multitask a lot. Replacing the Menu button with Recents button makes my life easier and faster. And less annoying again, because pressing and holding the crappy home button is not so convenient.
Adding the line to build.prop hasn't added the navbar after a reboot for me, does it need to go in a specific place, or does something else need changing as well?
delsus said:
Adding the line to build.prop hasn't added the navbar after a reboot for me, does it need to go in a specific place, or does something else need changing as well?
Click to expand...
Click to collapse
Yesss! I'm really sorry, I messed up. I fixed OP with correct line to add.
qemu.hw.mainkeys=0
Sent from my GT-I9300 using Tapatalk 2
jastonas said:
Yesss! I'm really sorry, I messed up. I fixed OP with correct line to add.
qemu.hw.mainkeys=0
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
It's working now, just one problem the home screen indicator is now behind the bottom shortcuts, is there any way to remove them or move them?
Sent from my GT-I9300 using xda premium
delsus said:
It's working now, just one problem the home screen indicator is now behind the bottom shortcuts, is there any way to remove them or move them?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Unfortunately no. I use Nova launcher. Any other will do. Almost all Samsung touchwiz apps have a problem with this mood but I can live with that.
Sent from my Nexus 7 using Tapatalk 2
jastonas said:
Unfortunately no. I use Nova launcher. Any other will do. Almost all Samsung touchwiz apps have a problem with this mood but I can live with that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Aww thanks again though
Sent from my GT-I9300 using xda premium
Awesome, these look great on beans jb build 2. Useing nova launcher they fit on screen well. My back button hard key is shot so this makes life a lot easier!
Sent from my SCH-I535 using Tapatalk 2
jastonas said:
you get the navigation bar (after reboot) and at the same time Android system recognizes this and adds the three dot menu icon whenever needed*!
If you want to disable the hardware keys, edit the file
These are the three hardware buttons
Add a # before any you don't wan't to use any more. I did for 158 and 139 and left my Home button working.
There is a mod** (flash it in recovery) which makes the bar almost half the size. It's better looking and less space is wasted but it does get some time to get used to it and you might need a couple of tries sometimes when trying to hit those buttons.
*This wasn't the case for ICS.
**mod by houssam10001
Click to expand...
Click to collapse
Great post.
I tried switching the Menu and the back button but it did not change the layout. I want to have the same layout as the Nexus devices with the back button first, home, menu(task). Is generic.kl is the right area to make the change? Thanks in advance.
Deca4 said:
Great post.
I tried switching the Menu and the back button but it did not change the layout. I want to have the same layout as the Nexus devices with the back button first, home, menu(task). Is generic.kl is the right area to make the change? Thanks in advance.
Click to expand...
Click to collapse
In order to change the order you have to decompile SystemUI.apk, edit the tw_navi_bar.XML file, recompile, then merge the edits into the original apk, then replace the app.
tw_navi_bar.xml can be found in /res/layout/
you simply need to switch the lines of code for the back and recents buttons to look like what is below. Note that the code below is from beans rom build 8 for the verizon s3. The code should be very similar for your rom though. Also note that you will need to do it for landscape too.
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/nav_buttons" android:background="@drawable/tw_navigationbar_bg" android:clipChildren="false" android:clipToPadding="false" android:layout_width="fill_parent" android:layout_height="fill_parent" android:animateLayoutChanges="false">
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/tw_navigationbar_back" android:layout_weight="1.0" android:contentDescription="@string/accessibility_back" systemui:keyCode="4" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/home" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/tw_navigationbar_home" android:layout_weight="1.0" android:contentDescription="@string/accessibility_home" systemui:keyCode="3" systemui:keyRepeat="true" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/recent_apps" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/tw_navigationbar_recent" android:layout_weight="1.0" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/menu" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="fill_parent" android:src="@drawable/tw_navigationbar_menu" android:layout_weight="1.0" android:contentDescription="@string/accessibility_menu" systemui:keyCode="82" systemui:glowBackground="@drawable/tw_sysbar_highlight" />
</LinearLayout>
Go into system/usr/keylayout/gpio-keys.kl and you can change "home" to camera if you want home button to snap pics
Skickat från min GT-I9300 via Tapatalk 2
There is a way to change the menu button function to pops the multitasks window and place the 3 dots in all aplications like when you have the navigation bar active without the navigation bar?
Hope you undestand it
Best regards
fridlack said:
There is a way to change the menu button function to pops the multitasks window and place the 3 dots in all aplications like when you have the navigation bar active without the navigation bar?
Hope you undestand it
Best regards
Click to expand...
Click to collapse
Is this a question or a statement? It's hard to understand when it has the structure of a statement but ends with a question mark.
---------- Post added at 04:56 PM ---------- Previous post was at 04:47 PM ----------
What of these zips? They're supposed to automate the change (I've used them before when I used CM10.1). I dunno if they work with touchwiz, tho.
http://forum.xda-developers.com/showthread.php?t=1918166
jastonas said:
b) I am a "fast" user and multitask a lot. Replacing the Menu button with Recents button makes my life easier and faster. And less annoying again, because pressing and holding the crappy home button is not so convenient.
Click to expand...
Click to collapse
how do you replace menu hard button with recent list?
I mean, what's the the "key word" to use?
Theshawty said:
Is this a question or a statement? It's hard to understand when it has the structure of a statement but ends with a question mark.
---------- Post added at 04:56 PM ---------- Previous post was at 04:47 PM ----------
What of these zips? They're supposed to automate the change (I've used them before when I used CM10.1). I dunno if they work with touchwiz, tho.
http://forum.xda-developers.com/showthread.php?t=1918166
Click to expand...
Click to collapse
You're right, my English is so bad, I tried to make a question
I'll check the link you posted, thanks for it
Best regards
jastonas said:
Yesss! I'm really sorry, I messed up. I fixed OP with correct line to add.
qemu.hw.mainkeys=0
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Nothing happen.
I have adding on the button of document build.prop, save then reboot but nothing change. Is there a spesific adding for this?
Be back for this.. I find the middle button a bit sticky and as I multitask between chat and translate programs its kinda laggy compared to the old evo
Sent from my GT-I9300 using Tapatalk 2
Enabling the navbar on sammy rom (omega in my case) causes my phone to freeze while playing The Dark Knight Rises. Disabled it and does not freeze anymore.
Sent from my GT-I9300 using xda app-developers app
Related
Is there anyway to change your default homescreen? I really love touchwiz's customizability and app drawer but really dislike the fact that the defualt home screen is the first one.
Can anyone help?
Sent from my GT-I9100 using XDA App
You can edit the screens by menu edit delete what you dont want add what you want to each screen .
jje
JJEgan said:
You can edit the screens by menu edit delete what you dont want add what you want to each screen .
jje
Click to expand...
Click to collapse
He didn't ask that.
Use another launcher?
JuWa said:
He didn't ask that.
Click to expand...
Click to collapse
So answer his question then .
Pointless clogging up the forum with no reply to the OP .
jje
Use sgs tools to change default page.
I am currently using launcher pro but i am not really a fan of its dock or app drawer. Btw my phone is not rooted so i cant use sgs tools.
Is there any way i can change it if i root my device?
Sent from my GT-I9100 using XDA App
DocRambone said:
Use sgs tools to change default page.
Click to expand...
Click to collapse
i just installed the latest version 4.1.9, but there is no option to change the default homescreen any suggestions? thanks
kar111 said:
Is there anyway to change your default homescreen? I really love touchwiz's customizability and app drawer but really dislike the fact that the defualt home screen is the first one.
Can anyone help?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I know it's not what you asked but stick your finger on the little numbers before the bottom layer of apps (drawer, phone, etc) and drag left and right. It'll make switching quicker and so the fact it's first won't be as annoying.
This may sound stupid, leave the default homescreen as 1 and just change what 1 is?
menu->edit or pinch to get the homescreens up and just press and hold then move the one you want as default to the 1st spot?
kar111 said:
Is there anyway to change your default homescreen? I really love touchwiz's customizability and app drawer but really dislike the fact that the defualt home screen is the first one.
Click to expand...
Click to collapse
Not possible without rooting the device!
It's one of the reasons why I ditched TouchWiz from the first day on. I use launcher pro now because I really like the dock with three pages for all my important apps.
If you root, you can edit default.prop to change this to another default screen
Download : http://forum.xda-developers.com/showthread.php?t=775154&highlight=homescreen&page=37
open SGS tools and go to .prop Editor and edit default.prop
#sets TouchWiz Launcher default screen
ro.csc.homescreen.defaultscreen=4
press menu and save I rebooted and it worked
(forgot to try if it's gonna work without rebooting )
enjoy
NoOneCanHelpMe said:
Download : http://forum.xda-developers.com/showthread.php?t=775154&highlight=homescreen&page=37
open SGS tools and go to .prop Editor and edit default.prop
#sets TouchWiz Launcher default screen
ro.csc.homescreen.defaultscreen=4
press menu and save I rebooted and it worked
(forgot to try if it's gonna work without rebooting )
enjoy
Click to expand...
Click to collapse
I downloaded sgstools and went into default.prop. It just comes up with a black screen I cant see anything to edit. If I press menu and go into free edit mode this comes up : #############################
# ro.com.google.clientidbase
# defined in gms.mk
# and must be FIXED
#############################
Help?
Sent from my GT-I9100 using XDA App
have you tried this http://forum.xda-developers.com/showthread.php?t=1096521 allready?
worked for me
the_Calen said:
have you tried this http://forum.xda-developers.com/showthread.php?t=1096521 allready?
worked for me
Click to expand...
Click to collapse
Cheers buddy, works great now
Sent from my GT-I9100 using XDA App
Maybe it is a stupid question, but suddenly I lost the software buttons on the bottom of the home. Is there a way to restore them?
Thanks
swipe left or right on the dock
jelle2503 said:
swipe left or right on the dock
Click to expand...
Click to collapse
Nothing happens if I do it
You should be able.to drag and drop them from the applications menu
Sent via that ninja standing right behind you
Latrop said:
You should be able.to drag and drop them from the applications menu
Sent via that ninja standing right behind you
Click to expand...
Click to collapse
If I drag them then the bar dissapears and the" remove" button appears. Cannot drug them to the bar
Odd Im not familiar with that launcher sorry
Sent via that ninja standing right behind you
dentalan said:
Maybe it is a stupid question, but suddenly I lost the software buttons on the bottom of the home. Is there a way to restore them?
Thanks
Click to expand...
Click to collapse
what launcher are you using? ...
you need to use your launcher menu> First you may need to long press the phone , contacts and message apps to bring them to the desktop, than use edit to place them in the Dock ( will depend on launcher and settings will vary according to their menu)
If too confusing just download a different launcher from play store and use it
This is stock Touchwiz, right? Looks like it, so I'll assume so...
Go into Applications.
You should see the icons for Phone/Contacts/Applications along with your other apps.
Press the menu button, and click edit. Now you should be able to move the icons around.
Drag the phone/contacts/messages icon down to the dock. It should drop there, and then you'll have your shortcuts back.
Sent from my GT-I9000 using xda premium
It worked
Soryuu said:
This is stock Touchwiz, right? Looks like it, so I'll assume so...
Go into Applications.
You should see the icons for Phone/Contacts/Applications along with your other apps.
Press the menu button, and click edit. Now you should be able to move the icons around.
Drag the phone/contacts/messages icon down to the dock. It should drop there, and then you'll have your shortcuts back.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It worked. Thank you. It was realy a stupid condition I was in.
Thanks again.
By the way, what is "stock Touchwiz"?
Touchwiz is the stock (or default launcher) that comes with the phone
Sent from my GT-I9000 using xda premium
dentalan said:
It worked. Thank you. It was realy a stupid condition I was in.
Thanks again.
By the way, what is "stock Touchwiz"?
Click to expand...
Click to collapse
Someone forgetting to say thanks?.....
Sent from my GT-I9000 using Tapatalk 2
Hi everyone,
Since I use a menu button in my navbar, I was wondering if there was a mod, that I could flash to remove the 3 dot menu. If there are none, I am willing to do it myself and have tried the following methods but they don't work for me. So if anyone knows of a mod or a guide, that would be great:
http://forum.xda-developers.com/showthread.php?t=2297692
The above link was the only one I could find, the rest mostly relate to HTC One threads.
Rom: Vanir Nighlty, Android 4.3 (AOSP Base)
EDIT 1: Here are the steps I tried:
To remove 3-dot menu:
Decompile your framework-res.apk
Go to values folder
Open bools.xml
Search for
<bool name="config_showNavigationBar">true</bool>
and change it to
<bool name="config_showNavigationBar">false</bool>
Recompile your framework-res.apk
I also made sure to sign the apk and zipalign it before putting it in a flashable zip
One thing I also tried, it was a long shot & it didn't work but I decompiled the framework of an MIUI rom since they have it enabled, and tried taking a few things from there but it didn't work
EDIT 2: I have already tried editing the build prop with a line from a HTC thread but it didn't work (phone wouldn't turn on)
Also, if anyone knows where menu-related stuff is within framework res that would be great because that would be a good place to test. (That's if the solution lies within framework res)
EDIT 3: Update: AOKP unofficial 14th September (4.3) still has the bug
Updated post with screenshots
I'm using Full screen toggle apk and LMT pie for navigation on stock 4.3 rooted and working well. See here http://forum.xda-developers.com/showthread.php?t=1497558
Melt1down said:
I'm using Full screen toggle apk and LMT pie for navigation on stock 4.3 rooted and working well. See here http://forum.xda-developers.com/showthread.php?t=1497558
Click to expand...
Click to collapse
I think you have misunderstood me. I mean the 3 dot menu in apps
bump
anyone??
22sl22 said:
bump
anyone??
Click to expand...
Click to collapse
Checking to see what I can do now
Sent from my Nexus 4 using XDA Premium 4 mobile app
melbourne408 said:
Checking to see what I can do now
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, much appreciated
Sent from my Nexus 4 using xda app-developers app
Bump, anyone?
Sent from my Nexus 4 using xda app-developers app
bump
bump too ...
as a start ... http://forum.xda-developers.com/showthread.php?t=1645052
http://mobility.forumsee.com/a/m/s/...hree-dot-menu-and-remap-multitask-button.html
xanthrax said:
bump too ...
as a start ... http://forum.xda-developers.com/showthread.php?t=1645052
http://mobility.forumsee.com/a/m/s/...hree-dot-menu-and-remap-multitask-button.html
Click to expand...
Click to collapse
Thanks xanthrax but I already tried that a while ago, I edited the build prop and my phone wouldn't turn on, so the search continues.....
Correct me if I'm wrong but I believe that the overflow menus you are referring to is coded into the app and not really dependent on anything else. Meaning that it is part of the app itself and not something the OS shows. Isn't that what Google's android interface guidelines suggests?
Sent from my Nexus 7 using Tapatalk 4
PMentior said:
Correct me if I'm wrong but I believe that the overflow menus you are referring to is coded into the app and not really dependent on anything else. Meaning that it is part of the app itself and not something the OS shows. Isn't that what Google's android interface guidelines suggests?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'm not a dev or app developer so I can't really comment on that. But I do know that some roms do have this feature on 4.3, it's just that it it doesn't work.
So im pretty sure the answer lies within the rom itself, not the apps maybe. Although im not even sure if the solution lies within framework res, it could be system ui or even at source, in git, which would make it out of my hands
I know that there are roms that can add the menus button permanently to the nav bar (PA can do this) but I have never seen one get rid of the menu overflow button within any apps themselves. Even back to 4.2 roms I never saw that type of behavior.
In fact now that I think about it when I still had my GS3 which has a physical menu button there still was the menu overflow button in some apps because that is what Google's app guidelines say to do.
Edit - I think what you are seeing about the htc one is about removing the black onscreen nav bar that shows up in apps that don't use the menu overflow button on app because the htc one has hardware keys but not a menu key.
Sent from my Nexus 4 using Tapatalk 4
PMentior said:
I know that there are roms that can add the menus button permanently to the nav bar (PA can do this) but I have never seen one get rid of the menu overflow button within any apps themselves. Even back to 4.2 roms I never saw that type of behavior.
In fact now that I think about it when I still had my GS3 which has a physical menu button there still was the menu overflow button in some apps because that is what Google's app guidelines say to do.
Edit - I think what you are seeing about the htc one is about removing the black onscreen nav bar that shows up in apps that don't use the menu overflow button on app because the htc one has hardware keys but not a menu key.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
There are roms on 4.2 that can remove the 3 dot menu because I used them. All roms (Or at least most) on 4.2 based off AOKP have the feature, i used to use Rootbox rom on 4.2.2 and Xylon rom and the feature worked perfectly. But if you look now on 4.3 AOKP builds, it just doesn't work for some reason
bump, updated first post
Bump
PMentior said:
Correct me if I'm wrong but I believe that the overflow menus you are referring to is coded into the app and not really dependent on anything else. Meaning that it is part of the app itself and not something the OS shows. Isn't that what Google's android interface guidelines suggests?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The apps seem to know if the phone has a menu button or not.
Just throwing this out there but PAC has the overflow menu disabled by default!
If there was a way to port this to other roms I would be ecstatic!
But alas I do not know how to cherry pick commits and I have no idea where the commit is in PAC's GIT
You find me that commit and I might be able to add it and build it with a friend of mines help.
I currently have a Galaxy Nexus which I like outside of the awful battery life, it's just old and just outclassed. I have finally settled on the G2 but there are a few things I need to know I can change before hand.
The on-screen buttons, the fact that LG chose to use a menu button is regressive and dumb. I want the standard AOSP "back,home,multitask;contextual3-dot" and to make sure the rest of the phone realizes that it needs to use the contextual 3 dot.
Proper Roboto font
Those are the biggies, everything else I know I can change or I can deal with. Has anyone figured these out?
qwirked said:
I currently have a Galaxy Nexus which I like outside of the awful battery life, it's just old and just outclassed. I have finally settled on the G2 but there are a few things I need to know I can change before hand.
The on-screen buttons, the fact that LG chose to use a menu button is regressive and dumb. I want the standard AOSP "back,home,multitask;contextual3-dot" and to make sure the rest of the phone realizes that it needs to use the contextual 3 dot.
Proper Roboto font
Those are the biggies, everything else I know I can change or I can deal with. Has anyone figured these out?
Click to expand...
Click to collapse
I would love to switch to a contextual 3-bot menu system as well. Would make using PIE a lot easier. Is the contextual 3-dot a system wide option somewhere? I looked through the build.prop and didn't see anything standout, but I really don't know exactly what I am looking for either.
There are 6 different configurations to use for the on screen buttons, but there isn't a dedicated recent button. You can, however, longpress home for recents. The menu/three dot issue I don't believe there is a solution yet. There is also a font changer with 6 or 8 fonts to choose from, including Roboto.
Thank you Devs. From my LG G2.
trickster2369 said:
There are 6 different configurations to use for the on screen buttons, but there isn't a dedicated recent button. You can, however, longpress home for recents. The menu/three dot issue I don't believe there is a solution yet. There is also a font changer with 6 or 8 fonts to choose from, including Roboto.
Thank you Devs. From my LG G2.
Click to expand...
Click to collapse
Looks like you can edit the build.prop and add qemu.hw.mainkeys=0 to the bottom to enable the system wide context aware 3 dot menu. Haven't got to verify yet. Anyone else try it?
trickster2369 said:
There are 6 different configurations to use for the on screen buttons, but there isn't a dedicated recent button. You can, however, longpress home for recents. The menu/three dot issue I don't believe there is a solution yet. There is also a font changer with 6 or 8 fonts to choose from, including Roboto.
Thank you Devs. From my LG G2.
Click to expand...
Click to collapse
I don't want to hold down the home button and wait... as for the font, apparently LG tweaked it slightly.
Also: Thanks Brian.. hopefully someone confirms this.
BrianTDI said:
Looks like you can edit the build.prop and add qemu.hw.mainkeys=0 to the bottom to enable the system wide context aware 3 dot menu. Haven't got to verify yet. Anyone else try it?
Click to expand...
Click to collapse
Trying this now, will report back.
---------- Post added at 03:16 PM ---------- Previous post was at 03:05 PM ----------
stetsonaw said:
Trying this now, will report back.
Click to expand...
Click to collapse
No go, tried it with both 0 and 1.
---------- Post added at 03:39 PM ---------- Previous post was at 03:16 PM ----------
stetsonaw said:
Trying this now, will report back.
---------- Post added at 03:16 PM ---------- Previous post was at 03:05 PM ----------
No go, tried it with both 0 and 1.
Click to expand...
Click to collapse
And before you try it, it isn't default.prop either (reverts back to the original version upon boot)
In the Verizon development section someone just posted a mod to do this. Only tested on Verizon right now.
Download AutoHideSoftKeys app from the play store. It's the bomb
bworley50 said:
Download AutoHideSoftKeys app from the play store. It's the bomb
Click to expand...
Click to collapse
Only a partial fix though, while i'm loving the app, i would still like to have it be context sensitive.
stetsonaw said:
Only a partial fix though, while i'm loving the app, i would still like to have it be context sensitive.
Click to expand...
Click to collapse
What does that mean?
bworley50 said:
What does that mean?
Click to expand...
Click to collapse
Meaning the menu button shows up in apps like Gmail, and when they use the legacy menu, the button shows up on the nav bar.
stetsonaw said:
Meaning the menu button shows up in apps like Gmail, and when they use the legacy menu, the button shows up on the nav bar.
Click to expand...
Click to collapse
Understand. I actually like this setup better than Nexus. That's what I love about android. Surely AOSP will be here sometime
ZIP is up in the Verizon Dev section. You can just activate the menu buttons while changing nothing else.
bworley50 said:
Download AutoHideSoftKeys app from the play store. It's the bomb
Click to expand...
Click to collapse
It covers the bottom part of the screen so it's pretty useless for replicating a standard navbar.
Sent from my LG-D800 using XDA Premium 4 mobile app
colbyfink said:
It covers the bottom part of the screen so it's pretty useless for replicating a standard navbar.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Then you're not using it correctly.
So there's no solution for AOSP on screen buttons that don't hide themselves and contextual overflow?
qwirked said:
... as for the font, apparently LG tweaked it slightly.
Click to expand...
Click to collapse
Wondering about this one too, based on whichever overly negative and biased review I read about that (Ars?).
qwirked said:
So there's no solution for AOSP on screen buttons that don't hide themselves and contextual overflow?
Click to expand...
Click to collapse
There is a solution in the vzw development area.
qwirked said:
I currently have a Galaxy Nexus which I like outside of the awful battery life, it's just old and just outclassed. I have finally settled on the G2 but there are a few things I need to know I can change before hand.
The on-screen buttons, the fact that LG chose to use a menu button is regressive and dumb. I want the standard AOSP "back,home,multitask;contextual3-dot" and to make sure the rest of the phone realizes that it needs to use the contextual 3 dot.
Proper Roboto font
Those are the biggies, everything else I know I can change or I can deal with. Has anyone figured these out?
Click to expand...
Click to collapse
There is a fix for this but it is a Verizon MOD only, it might work on other carriers but you would have to read the thread to find out of it is working with all carriers.
bworley50 said:
What does that mean?
Click to expand...
Click to collapse
He means that it would be even better if the menu burns know when to be visible and when they should be hiding.
Sent from my LG-F320L using XDA Premium 4 mobile app
Does anyone know how could I use a build prop edit to safely hide the bottom navigation bar without using unnecessary RAM? I use LMT so it isn't necessary.
I believe its in the build . prop file because when I replaced it to do a status bar mod, the bar disappeared momentarily when the file was missing.
However, I'm new to Android and I don't want to put myself into a boot loop or worse by blindly deleting things. I don't even know how to use a recovery yet. So does anyone know where this is? Thanks
LG G2
I just use an app. Auto hide soft keys. It's in the play store. Also use LMT myself. Let me ask you something, what setting do you set gesture input to?
Sent from my LG-D800 using xda app-developers app
chiballer20 said:
I just use an app. Auto hide soft keys. It's in the play store. Also use LMT myself. Let me ask you something, what setting do you set gesture input to?
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I find that app kind of bugging, and there are moments when my buttons are no longer being displayed and I have to reboot to get them back.
Sent from my LG-D801 using xda app-developers app
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
That is what do do with all of my phone using LMT, and not barely crash, I've had one during this year and s restart made it normal.
Sent from my LG-D801 using Tapatalk now Free
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
Thanks, i'll try it.. hopefully it will free up a good amount of RAM :fingers-crossed:
IamPro said:
Thanks, i'll try it.. hopefully it will free up a good amount of RAM :fingers-crossed:
Click to expand...
Click to collapse
sry for the stupid question....what is LMT?
energie said:
sry for the stupid question....what is LMT?
Click to expand...
Click to collapse
Gesture based launcher:
http://forum.xda-developers.com/showthread.php?t=1330150
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
IamPro said:
Thanks, i'll try it.. hopefully it will free up a good amount of RAM :fingers-crossed:
Click to expand...
Click to collapse
Softbricked my phone and had to restore to stock then re-root etc :crying:
what is LMT?
This is LMT, or one of its functions. Its a really customizable navigation bar that replaces the stock one, along with any of other gesture control you could think of. Its great, you should try it out
LG G2
It swipes in from the bottom, top or sides. You can hold the gesture and lift your finger on the button or just swipe through in the direction you want and the function will activate. It gets much more complex than my setup but I'm just keeping it simple for now
LG G2
IamPro said:
Softbricked my phone and had to restore to stock then re-root etc :crying:
Click to expand...
Click to collapse
Sorry, you softbricked after inserting the string in build.prop? I'm interested to this mod (hiding soft keys and activate LMT)
nimo182 said:
Sorry, you softbricked after inserting the string in build.prop? I'm interested to this mod (hiding soft keys and activate LMT)
Click to expand...
Click to collapse
Yea, maybe I did something wrong.. idk
Its pretty easy to get back to stock so not huge deal tho
wy2sl0 said:
add
qemu.hw.mainkeys=1
to your build.prop file. That is all I did. Just don't be stupid like me and do it before you turned LMT on. I had to think up some creative ways to open it from within other programs without the back button or home available :laugh:
Click to expand...
Click to collapse
How did you do this safely? Many people have been getting it wrong and I'd like to get it right the first time lol
LG G2
I have no idea.
Downloaded build.prop editor from the play store
go to VERY BOTTOM of build.prop
make a new blank line
enter what I said
save
...profit
The best app to hide soft keys is UDN (ultimate dynamic navbar),it can hide your keys without the need to modify them in build prop....And replace them with its soft keys that are not only customisable but you can also make them as tiny as you want in order not ot occupy as much space...
woof123 said:
The best app to hide soft keys is UDN (ultimate dynamic navbar),it can hide your keys without the need to modify them in build prop....And replace them with its soft keys that are not only customisable but you can also make them as tiny as you want in order not ot occupy as much space...
Click to expand...
Click to collapse
woof i tried UDN, to hide nav bar it requires xposed with it's module..i'm not too much interested to install other sw indeed, and IMHO it's the same of autohide
Then the build.prop string qemu.hw..... works??
nimo182 said:
woof i tried UDN, to hide nav bar it requires xposed with it's module..i'm not too much interested to install other sw indeed, and IMHO it's the same of autohide
Then the build.prop string qemu.hw..... works??
Click to expand...
Click to collapse
It worked for me.Without xposed,i just ticked the option in the settings.Also you can make the keys as tiny as you want,even if you want them visible all the time and not hidden it will help alot to make them tiny.
nimo182 said:
woof i tried UDN, to hide nav bar it requires xposed with it's module..i'm not too much interested to install other sw indeed, and IMHO it's the same of autohide
Then the build.prop string qemu.hw..... works??
Click to expand...
Click to collapse
can't make it working....it adds another bar above the stock one