Hey guys,
i tried to hide the navbar on my N4 with Stock 4.2.1 firmware.
I added to build.prop the line: "qemu.hw.mainkeys=1"
now the Nexus 4 won't boot up. I had to restore the old build.prop.
Permissions of the build.prop were set right.
Has anyone a solution for hiding the navbar?
I want to use the Pie Controls of LMT, so i don't need the navbar.
Perhaps you messed something like else up? I'm using that right now, albeit on Bionic pure AOSP. It works fine.
smicbee said:
Hey guys,
i tried to hide the navbar on my N4 with Stock 4.2.1 firmware.
I added to build.prop the line: "qemu.hw.mainkeys=1"
now the Nexus 4 won't boot up. I had to restore the old build.prop.
Permissions of the build.prop were set right.
Has anyone a solution for hiding the navbar?
I want to use the Pie Controls of LMT, so i don't need the navbar.
Click to expand...
Click to collapse
I added the same line to build.prop with root explorer and use Button Savior without any difficulty. Try again-you must have done something wrong. Maybe you didn't put the new text on a separate line at the end. Make sure you do not use the quote marks. Root explorer renamed the original file and saved it for me. Another thing you can do is use custom roms that have an option to remove the soft keys.
okay I found out what the problem was.
I didn't update Root Explorer and the Version 2.14.<something> messed my build.prop up, everytime i saved it.
With the newest Version of Root Explorer it works fine.
Thank you for your help.
Smicbee
Related
Hey Guys, I updated and rooted my phone to 2.3.4 HK...
Anyways, I remember seeing a post about an app that lets you enable the whole screen.
It appears that I have some dead space on the main home screen and I can not place any widgets in it (Its in the bottom)...
Any way I can fix that ? I cant remember the app name for the life of me.
thank you,
Alex
Hey, just use root explorer or shell in order to edit the build.prop in your system folder (or just use CWM and mount your /system folder to your computer). in the build.prop, there is a section that describes the ppi and for some reason, it's set as default to 240. Change it to 275 and it should fix all screen issues.
thanks for your response!! I checked thru Root Explorer, and only found
dpi... not PPI.. is that what you meant? Cause I see that listed as 240.
Also, do I need to reset after the edit?
Thanks a lot!!
The stock launcher seems to be messed up, get a different launcher.
Sent from my MB860 using XDA App
Some people have complained about the resulting effects of changing the build.prop file with this fix. Better to just use a different launcher than stock as was said.
LCD density for root I believe it is the 270 setting you need to select.
Sent from my MB860 using XDA App
can someone take the time to school a noob on DPI? I change the dpi n my ro.build and I see no difference... pretty sure I am misunderstanding some part of it.
From my understanding you change the build.prop... save and exit the text editor (must be rooted) and restart the device... I've been using that method on my galaxy nexus and now nexus 7 and it works perfect... think of lowing the dpi as in tricking the OS into thinking you have a bigger screen than you actually have... thus making everything smaller and also triggering tablet mode
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
player911 said:
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It should work if the folder is R/W and you save and exit. Maybe you should try es Flie Explorer?
I was rushed while posting that and I believe I was completely unclear. I did edit the you Build.prop, I am on a custom rom sgt7 and the dpi and build.prop and DPI was 213 I think maybe 216, I changed it to 180 and I saw no difference at all. this is possibly because there are other modifications to the Rom that aren't dpi dependent or something.
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:
qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore
in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar
How do I know if it's just a commented line and not necessary to the program?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.
Use build.prop editor app from playstore
_____________________________________Read more write less and be smart
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Hello,
I was trying to edit the build prop file using the ES Explorer, but the same happened to me, I could edit the file by downloading the "build prop editor" from play store.
Edit the file by pressing the button in shape of a pencil and later press the save button. If you only search for the line you want to edit in the main screen of the app you will be able to modify the line but the changes are not saved.
Thanks/rate
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Never mind.
ES File doesn't always save, you'll just have to try a different app. Root explorer should work or fx file manager.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
This is a quick walk through for editing the build.prop to allow lock screen and launcher rotation.
I got tired of looking at my phone sideways while it was propped up landscape wise, in my case.
1. Locate "build.prop" in /system using your favorite file explore
2. Open it up and at the bottom add the lines
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
3. Save your edit and reboot.
Lockscreen rotation still not working for you???
A few users have reported that adding a blank line between the two, fixes this issue.
Once the phone reboots your lockscreen and Google Now launcher will rotate with the orientation of the device just like other apps do.
To undo this, simply remove the lines we added
:good:
Update: 11/10/2015
enigma9o7 Has figured out how to get this to stick even after an update! Head over to his post for the walkthrough and install guide!! Remember to give them a "thanks" for sharing the work!
Awesome I been wondering how to get this done.
Nice tip. I've always just used an app called Ultimate Rotation Control. Seems to work just fine on the Nexus 6. A quick build.prop tweak removes the need for a separate app for it, though. I might get around to trying this...eventually
can someone make a flash able zip for this please ?
thanks in advance
Anybody know how one would do this with adb?
N6
I used an app for quite some time but i disliked it running in the background.
Im not able to make a flashable zip. Maybe in time I will see if i can.
For adb, youd have to pull the build.prop, edit on computer then push it back. The instructions to do that are unclear to me
mrfuzzie23 said:
can someone make a flash able zip for this please ?
thanks in advance
Click to expand...
Click to collapse
You can install Nova Launcher and toggle the setting in there, or use the ultimate rotation app someone else mentioned.
Thx
If you set the DPI to 384 or less, this happens by default.
pavankp said:
If you set the DPI to 384 or less, this happens by default.
Click to expand...
Click to collapse
Thats good to know! Not surprising, the device is most likely changed to "tablet size" to the system. And they have full rotation.
Works great, thanks! (AT&T Nexus 6)
Would not work for me I get error saving
techrider6262 said:
Would not work for me I get error saving
Click to expand...
Click to collapse
Thats not good. What error are you getting?
eqbirvin said:
Thats not good. What error are you getting?
Click to expand...
Click to collapse
It just said error can't save and I tried a couple different time
techrider6262 said:
It just said error can't save and I tried a couple different time
Click to expand...
Click to collapse
gotcha. You are rooted, correct? and if so what file manager are you using to locate the build.prop?
es file explorer and i'm rooted.
in ES file explorer when you grant it root permissions, click on root, then mount R/W, make sure "/system" is RW instead of RO. (sorry if you already know this, im just trying to save time and figure your error out haha)
Thanks I got it working.:good:
Glad to hear it!
to each their own, I like being able to get OTAs so I'll stick with Ultimate Rotation Control