Related
I remember someone wishing there was a way to do this, and i found this in the Nexus 7 forums:
http://forum.xda-developers.com/showthread.php?t=1985592
I tried it just for fun and it sorta worked, the nav bar was gone, but system ui kept force closing about every minute... but in the meantime i could browse around. But i hadn't installed a different launcher or nav app so it was kinda hard.
Anyway, i wonder if there was a further edit that could be made, perhaps in systemui, to make this work better? Anyway, try at your own risk, i was able to navigate to my /system folder and delete my new build.prop and take the .bak off my original one to get back to normal.
You can modify systemui to make the bar smaller maybe even remove/hide it altogether
Sent from my XT897 using Tapatalk 2
cool, thanks. would it be navigation_bar.xml? any advice on editing that? when i click edit it opens it up in a notepad, but it's a bit unintelligible to me. I also downloaded a trial of an XML editor, but it said the XML can't be opened.
you have to decompile the apk with a tool. apktool is most often used and then i use notepad++
Rangerbry said:
You can modify systemui to make the bar smaller maybe even remove/hide it altogether
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ohhh the nav bar smaller? Where can change this?
...Tapatalk
So, does anyone know of a way to get rid of the navigation bar?
I'm aware of some apps on the marketplace that can remove both the nav bar and notification bar. If it's possible to just remove the one, that would be epic. Or even something that just makes it totally opaque and removes the buttons from it, I dunno.
I'd like to lose it and gain some screen real estate while I use LMT (http://forum.xda-developers.com/showthread.php?t=1330150).
Hmmm... Back when I was trying CM9, I initially built without the overlay for the nav bar... that was distressing.
I wonder if there's something in the build.prop? I will look around.
arrrghhh said:
Hmmm... Back when I was trying CM9, I initially built without the overlay for the nav bar... that was distressing.
I wonder if there's something in the build.prop? I will look around.
Click to expand...
Click to collapse
I actually did come across something about a build.prop edit, but I lost the page that had that
*EDIT*
Found this:
Code:
qemu.hw.mainkeys=1
Putting it in build.prop got the nav bar away, but also sent Settings.apk into a continuous FC every 10 seconds.
I think the only *REAL* and *WORKING* way to do it would be to resize the thing to 0, which I've read is what works for people.
*EDIT 2*
Successfully made the nav bar size of 0.... But a lot of other weird stuff happened.
Maybe use some kind of transparency function? I wish there was a way to toggle it open and closed via the volume keys or something.
Sent from my XT897 using xda app-developers app
Improving this would be really lovely.
Could this help?
http://forum.xda-developers.com/showthread.php?t=2098723
Sent from my XT897 using Tapatalk 2
dwaynet89 said:
Could this help?
http://forum.xda-developers.com/showthread.php?t=2098723
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
That's basically what I did, but a lot of stuff was changed along with it. I've been meaning to post the screenshots I took.
It DID work, however.
Sent from my XT897 using Tapatalk 2
Did you manage to obtain a bugfree result?
Something like that.
The status bar resized itself, and I never went back in and tried different sizes for that. But if I did, I would have made it work.
I found this in framework-res.apk/res/values/bools.xml:
Code:
<bool name="config_showNavigationBar">false</bool>
It took away the navigation bar as expected, but also sent SystemUI into a constant FC.
What I need to edit the right way are these values:
Code:
<dimen name="navigation_bar_height">48.0dip</dimen>
<dimen name="navigation_bar_width">42.0dip</dimen>
from inside framework-res.apk/res/values/dimens.xml
Also not sure if these lines (from dimens.xml) play into it as well, but they might. Because I have the status bar issues and resized layouts and all if changing the above values to 0.
Code:
<dimen name="status_bar_height">25.0dip</dimen>
<dimen name="system_bar_height">48.0dip</dimen>
The values for all of these are not in terms of pixels. Not sure how exactly to interpret the dip values.
Code:
/* Disclaimer: This MOD is not officially endorsed or supported by the CyanogenMod team. */
Due to numerous requests, I decided to make this MOD publicly available.
What this MOD does is disable the hardware keys from the UI (wake functions will still work) and enable the softkeys via a build.prop edit. It also disables the softkey lights via an init.d script. You can disable that part of the MOD by creating an empty 99nobacklights file in init.d.
Download Enable Softkeys MOD v1.2
Download Disable Softkeys MOD v1.0
Just an FYI on what is being modified in this MOD:
/system/build.prop
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
If you backup the above files, you can undo the mod without reflashing it by dropping in the originals. As of v1.2 of the enable softkeys MOD, you can flash the latest disable softkeys MOD to disable the softkeys and get the hardware buttons back.
Also the following file is created by the MOD to disable the backlights only if the file doesn't exist:
/system/etc/init.d/99nobacklights
If you don't want to flash the new disable MOD, you can delete 99nobacklights and remove the # symbols from synaptics-rmi-touchscreen.kl as well as delete the line that says qemu.hw.mainkeys=0 and then reboot.
Delete it and reboot to regain the backlight functionality.
If you don't have init.d support in your ROM, the backlights will function as normal but the rest of the MOD will work. As an alternative to this, you can run this at boot or manually edit the below referenced file and set the value to 0:
echo 0 > /sys/class/leds/button-backlight/max_brightness
NOTE: One little aesthetic bug I've noticed of the current method is that each flash of the enable MOD puts an extra blank line before qemu.hw.mainkeys=0 and the disable MOD doesn't delete that extra line. If you flash back and forth between an enabled state and disabled state, you'll see a lot of blank lines at the bottom of your build.prop. There are no negative implications other than it looking kind of weird.
Changelog:
Enable softkeys
v1.2
make mod more universal by editing the files via instead of dropping them in
This also allows a simple disable softkeys MOD to be put in place.
v1.1
fix issue where capacitive buttons weren't actually getting disabled
v1.0
Initial release
disables backlight and capacitive buttons
enables softkeys via a build.prop edit
Disable softkeys
v1.0
Revert changes in v1.2 of the enable MOD via sed edits.
Thank you kindly.
I had the software buttons enabled already, it was just disabling the hardware buttons and backlighting that I didn't have yet.
[edited]
Finally got a chance to flash the mod.
While the mod did disable the backlighting to the capacitive buttons, it did not disable the capacitive buttons themselves. CM10.1 nightlies
msgnyc said:
Thank you kindly.
I had the software buttons enabled already, it was just disabling the hardware buttons and backlighting that I didn't have yet.
[edited]
Finally got a chance to flash the mod.
While the mod did disable the backlighting to the capacitive buttons, it did not disable the capacitive buttons themselves. CM10.1 nightlies
Click to expand...
Click to collapse
Fixed it for v1.1. If you don't want to reflash, you can edit the file /system/usr/keylayout/synaptics-rmi-touchscreen.kl and clear everything from that file and save and reboot.
Ahh Kool. Yeah I sorted everything out, but this'll make everything a few steps easier between nightlies.
You don't have to clear the file tho. Mearly commenting out each line with # does the trick..
msgnyc said:
Ahh Kool. Yeah I sorted everything out, but this'll make everything a few steps easier between nightlies.
You don't have to clear the file tho. Mearly commenting out each line with # does the trick..
Click to expand...
Click to collapse
I cleaned it up a bit more and wanted to do some more improvements for 1.2. I'm using more edits instead of replacing files. This should make it more universal.
I took your tip into consideration. I knew about the # being for comments but I didn't think about the OS ignoring it in non script files.
I'm setting it up for a revert mod now based on wanting to do more than just replace with a blank file to disable and to make it easily revertible. The next version will feature these improvements.
I'm actually surprised this thread isn't getting more responses with the number of requests I got. I guess Android development doesn't get as much viewing.
lol yeah im a bit surprised there arent many hits on this thread aswell. I get hit up about how to do it aswell.
I really wish HTC made the buttons transparent like the S3/4 rather then white and always there. Works fine for me now tho. I took the iBlasso screen protector and added a carbonfiber skin insert were the cutout is at the bottom. Looks real nice and still a flush fit.
Onscreen softkeys for nav n slide my finger across the carbon fiber strip to wake.
msgnyc said:
lol yeah im a bit surprised there arent many hits on this thread aswell. I get hit up about how to do it aswell.
I really wish HTC made the buttons transparent like the S3/4 rather then white and always there. Works fine for me now tho. I took the iBlasso screen protector and added a carbonfiber skin insert were the cutout is at the bottom. Looks real nice and still a flush fit.
Onscreen softkeys for nav n slide my finger across the carbon fiber strip to wake.
Click to expand...
Click to collapse
I've made progress on the mod. I should have a version that reverts the enable mod ready to go soon but I'll need to test it when I'm back on AOSP.
Heads up: this doesn't even work...
Sent from my HTC One using Tapatalk 4 Beta
Yeah it do
Sent from my HTC One using Xparent Skyblue Tapatalk 2
It works with aosp roms like the title says. Does not work with stock rom.
It didn't work on CM.. Had to restore from backup and do it manually with root browser..
Sent from my HTC One using Tapatalk 4 Beta
Toaster Strudels said:
It didn't work on CM.. Had to restore from backup and do it manually with root browser..
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same here
Sent from my One using xda premium
Is that the latest version of the mod? (1.1) if so, then I'll look at this sometime next week. I'm trying to hold out for in call audio to work on CM before checking this out. I have a updated version in the works anyway that should not have any issues.
What CM variant are you guys with issues on? The initial version used a build.prop in the mod. It wasn't a good idea so I'm having it edit it now for the upcoming version.
Sent from my HTC One using Tapatalk 2
It's worked for me fine for every nightly build... So I don't know.
V1.2 of the Enable MOD is up as well as an initial release of the Disable MOD. This should address the major concerns and issues with the previous version.
It's doesn't work on the Rootbox rom. Luckily I have gesture.
Sent from my HTC One using Tapatalk 4 Beta
yiwsg said:
It's doesn't work on the Rootbox rom. Luckily I have gesture.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's only been tested on CM so I don't know if there's something that'd make it fail on Rootbox or another ROM? Can you output the last 5 or 10 lines of the following files:
/system/build.prop
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
build.prop should have qemu.hw.mainkeys=0 at the end and synaptics-rmi-touchscreen.kl should have every line preceded with the # symbol. That's all the mod does in addition to turning off backlights by creating an init.d script.
Also, did you flash the latest versions listed in the OP?
works great on cm.10 latest nightly. but somehow i miss the sense rom, too bad it doesnt work on sense. btw does this mod work with google edition based roms?
adichandra said:
works great on cm.10 latest nightly. but somehow i miss the sense rom, too bad it doesnt work on sense. btw does this mod work with google edition based roms?
Click to expand...
Click to collapse
I don't know. I haven't tested. I'm leaning toward no.
Sent from my HTC One using Tapatalk 2
Twrp unable to open zip file. Same with es explorer.
Sent from my One using Tapatalk 4 Beta
Hi,
I have just remembered this app, I share it here:
Description
This application will let you change the SoftKeys / Navigation Buttons fast and easily. This app comes with more than 150+ different soft-buttons to choose from and more will be added with every update. If you got some navigation buttons you would like to see in this app just write an email about it. Until I've added them, you can just use the import feature for these soft keys. This application needs root and "BusyBox" to be installed. This app will NOT overwrite your applied themes, or enable the navigation buttons on devices without them.
Odexed ROM?: Some people are reporting small to bigger problems with odexed ROMs. Sometimes your choosen wallpaper can disappear.
WARNING: This app modifies system files and should only be used with a flashable backup of your current ROM on your device. The developer is not responsible for any damages.
Click to expand...
Click to collapse
Play Store
Original thread
It can be nice to change the look of the soft buttons , I have not tested yet so I don't know if it works well and maybe it can conflict with some Xposed modules for the navigation bar...
Feedbacks are welcome...
Doesn't work for me
Sent from my VS980 4G using Tapatalk
The guy that made the app made it to work on the nexus line. He didn't expect it to work on the g2. I tested also and as was expected it doesn't work. Steer clear of this thing until/unless the app developer okays it.
Sent from my LG-D800 using XDA Premium 4 mobile app
These work for me so far.
UDN - Needs Xposed and works really well. http://forum.xda-developers.com/showthread.php?t=2270198
LMT Launcher - Awesome pie nav bar. Select #9 in Gesture input. Works perfectly on my G2.
G2 Exposed - Use this to hide stock navbar. http://forum.xda-developers.com/showthread.php?t=2477586
Anyone find a way yet?
Just Found This
ok guys i found this app called "Floating Soft Keys *ROOT*"
https://play.google.com/store/apps/details?id=com.rhoadster91.floatingsoftkeys&hl=en
hope if works out for you guys
Works fine for me but I'm on cm based rom. Also anyone know where to find more icons? All I find are recolored stock ones mostly.
There is an online gallery
Gesendet von meinem LG-D802 mit Tapatalk
Is this working on KK based Roms ?
Lowresolution said:
Is this working on KK based Roms ?
Click to expand...
Click to collapse
Nope
Generally speaking I really prefer the AOSP Roms but I have a few things in the stock based roms that I can't seem to get away from. One of them is the sound. Its just better on stock. I won't go into detail because a) that's not the point of this post and b) I don't want any of the excellent devs working on AOSP roms to think I'm being critical of their work.
One of the things I preferred about the AOSP Roms was the lockscreen. I just don't like LG's implementation. I don't think it looks as good and I don't like having to press enter after typing in my pin. It's petty on my part, but it irks me. Anyway, I had been trying to figure out how to port the lockscreen from AOSP to work on stock based roms and as it turns out, it's already there. In a rather foolhearty attempt to learn more about LG's lockscreen, I decided to make a nandroid backup, then boot, and just erase the LGLockScreen.apk/LGLockScreen.odex files from the /system/app folder using ES file explorer. I also erased the LGLockSreenSettings.apk/LGLockScreenSetting.odex files as well.
Now I have the AOSP lockscreen but things aren't exactly 100 percent stable. I'm trying to find a solution to make the switch and not have weird force closes. Sometimes it works fine but every once and a while, it will behave strangely and spit error messages at me. I've searched but I haven't seen any threads where anyone has managed to do this. (I tried erasing the lockscreen and leaving the settings files but that didn't work 100% either) Any suggestions?
Before:
After:
a working AOSP lockscreen for stock would be more than a welcome addition.
I changed this line in my build.prop because i wanted a live wallpaper on my lockscreen. It also makes your lockscreen aosp style.
Find
ro.lge.capp_lockscreen=true
Change to
ro.lge.capp_lockscreen=false
Reboot
Enjoy
Also for whatever reason root explorer wouldn't let me change true to false. It would only let me spell out fals so i downloaded buildprop editor free from play store worked great.
Should mention i have Verizon G2
Jeff Zaugg said:
I changed this line in my build.prop because i wanted a live wallpaper on my lockscreen. It also makes your lockscreen aosp style.
Find
ro.lge.capp_lockscreen=true
Change to
ro.lge.capp_lockscreen=false
Enjoy
Also for whatever reason root explorer wouldn't let me change true to false. It would only let me spell out fals so i downloaded buildprop editor free from play store worked great.
Click to expand...
Click to collapse
Sweet, thanks man! That seems to work great.
Glad i could help
Sent from my VS980 4G using xda app-developers app
Well setting the LG lockscreen to false enabled the AOSP lockscreen. I was able to get the lockscreen to unlock when the correct PIN was entered without having to press the enter button, which was not possible previously. I did notice that my navigation bar transparency was disabled when I was not using the LG lockscreen. With the QuickWindow cover I have I reverted back to LG lockscreen for the window effect and the transparent nav bar.
I went ahead and changed the line in my build.prop as stated above, and it definitely cleaned up the lockscreen how I wanted, but now my wallpaper is gone. Its just a black screen and I've tried changing it to other wallpapers but it just stays black. Any ideas?
Sent from my VS980 4G using xda app-developers app
I did this to have my homescreen live wallpaper on my lockscreen to mimic the look of Gummys kitkat rom while running lg based rom. I really havent tested beyond that. I set live wallpaper of choice ( phase bean ) onn homescreen then modified the build.prop. After reboot ive got a aosp style live wallpaper lockscreen.
Edit
Just tried and whatever wallpaper i set to homescreen is on lockscreen live or from gallery. Tried changing just lockscreen alone with no luck so if you want to separate wallpapers this might not be for you
Sent from my VS980 4G using xda app-developers app
Jeff Zaugg said:
I did this to have my homescreen live wallpaper on my lockscreen to mimic the look of Gummys kitkat rom while running lg based rom. I really havent tested beyond that. I set live wallpaper of choice ( phase bean ) onn homescreen then modified the build.prop. After reboot ive got a aosp style live wallpaper lockscreen.
Edit
Just tried and whatever wallpaper i set to homescreen is on lockscreen live or from gallery. Tried changing just lockscreen alone with no luck so if you want to separate wallpapers this might not be for you
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Agreed, actually one of the things I wanted from the AOSP lockscreen was to use the same wallpaper as the desktop. I thought it looked weird having different ones and when I would choose the same one for the desktop and the LG based lockscreen, they would be clipped differently and just looked even weirder to me....
FYI, for those of you doing this, I'm noticing some strange issues when combined with some Xposed modules. I'm actually thinking I might install a fresh rom and do this so that I can try to figure out which module(s) might be of concern...
Tried the build prop thing too but although i am able to save it it gets revertet to "true" directly after...
EDIT: Forget it! Altered the build.prop manually with root browser and now the lockscreen has changed. But still i have to press enter after the pin...
EDIT: Forget that too. In xposed g2 settings i could activate "quick unlock".
Thanbks Guys
Chris
MasterTRL said:
Tried the build prop thing too but although i am able to save it it gets revertet to "true" directly after...
EDIT: Forget it! Altered the build.prop manually with root browser and now the lockscreen has changed. But still i have to press enter after the pin...
EDIT: Forget that too. In xposed g2 settings i could activate "quick unlock".
Thanbks Guys
Chris
Click to expand...
Click to collapse
What menu is the quick unlock option under? I can't find it.
youngpic48 said:
What menu is the quick unlock option under? I can't find it.
Click to expand...
Click to collapse
I found it under the gravity box module. I'm not sure it's in the G2 module since our G2 wouldn't normally use this lockscreen...
Jeff Zaugg said:
I changed this line in my build.prop because i wanted a live wallpaper on my lockscreen. It also makes your lockscreen aosp style.
Find
ro.lge.capp_lockscreen=true
Change to
ro.lge.capp_lockscreen=false
Reboot
Enjoy
Also for whatever reason root explorer wouldn't let me change true to false. It would only let me spell out fals so i downloaded buildprop editor free from play store worked great.
Should mention i have Verizon G2
Click to expand...
Click to collapse
Anyone try this on the canadian d803?
GetPatriotized said:
Anyone try this on the canadian d803?
Click to expand...
Click to collapse
this little mod should work on any version.
MasterTRL said:
Tried the build prop thing too but although i am able to save it it gets revertet to "true" directly after...
EDIT: Forget it! Altered the build.prop manually with root browser and now the lockscreen has changed. But still i have to press enter after the pin...
EDIT: Forget that too. In xposed g2 settings i could activate "quick unlock".
Thanbks Guys
Chris
Click to expand...
Click to collapse
Which G2 Xposed module did you use? Nevermind
noticed a small issue with using this tweak: sometimes after a phone call when it goes back to the home screen it's just an empty wallpaper instead without any icons and the only way to get out of is to bring the notification shade and go into settings from there and then go back to the home screen.
I've seen that too. It's kind of annoying and really strange. I wish I knew how to stop it from happening because I really don't like the lg lockscren...
Sent from my LG-D800 using xda app-developers app
Just wanted to mention that the latest Malladus 1.2.3 has the aosp lock screen baked into the rom. Very nice!
Sent from my VS980 4G
Jeff Zaugg said:
Just wanted to mention that the latest Malladus 1.2.3 has the aosp lock screen baked into the rom. Very nice!
Sent from my VS980 4G
Click to expand...
Click to collapse
Can u ask the dev to make a flashable zip for that mod.. that rom isnt supported for my device do i dont know alot about it, if its a lg rom withaosp lockscreen a zip would make LG roms alot better
Sent from my LG-D802 using XDA Premium 4 mobile app
razrlover said:
Can u ask the dev to make a flashable zip for that mod.. that rom isnt supported for my device do i dont know alot about it, if its a lg rom withaosp lockscreen a zip would make LG roms alot better
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What carrier are you on? If you just want the aosp lock screen this thread explains how to make the change in your build.prop very simple
Sent from my VS980 4G