Hi all,
After moving to Android 5.01 from 5.0, I noticed that the following method to hid soft keys is no longer working. I wanted to use LMT Pie control and hide the original soft keys.
- Add qemu.hw.mainkeys=1 to the bottom of the "build.prop" in /system folder.
The device wont boot after I made the change.
It worked fine with Android 5.0. Anyone has any idea on how to hide the original soft keys.
qemu.hw.mainkeys=1
You have to be rooted to do that. I've done it on 5.0, 5.0.1, 5.0.2 and it always work. If your device isn't booting, you screwed something up.
Build prop method still works.
really?! My device is rooted. I use the RE explorer to make the change in the build prop file. It just won't boot and stopped at the google boot screen.... I did not see any mis-spelling... so wired.
Yep, build.prop method worked fine for me on 5.01. Look for a typo (watch for autocorrect on the previous line...), and make sure you hit return after the new line.
Don't forget busy box, I was having the same issue until I reinstalled busy box
Sent from my Nexus 6 using XDA Premium HD app
I use Auto Hide Soft Keys, from the playstore, better than modifying Build prop imo
Related
EDIT: I have figured out how to make the EPTT work on any rooted android phone. Skip to post #6 for the tutorial and proof.
ProStreetCamaro said:
I have rooted and installed SU. I have tried Helium to backup the app on my old S3 then install the app on my new S5. It wont register that way. I tried Device spoofer to make it look like an S3 and it still wont register. I found an older thread where the guy said it worked with both above mentioned methods on his Note 3. But they dont seem to work on the S5. Anybody have any other ideas? Is the network possibly seeing the S5 sim card and simply going NOPE not happening or does it read the device info instead? If it is the sim maybe they can reactivate my S3 sim and maybe I can get it working that way?
Any thoughts or help would be greatly appreciated.
Click to expand...
Click to collapse
Try using Titanium Backup and doing the exact same thing; back up the app on your S3 to your SD card, move the card to your S5, restore the app. Should work fine. I've never worked with Helium.
cmerlyn said:
Try using Titanium Backup and doing the exact same thing; back up the app on your S3 to your SD card, move the card to your S5, restore the app. Should work fine. I've never worked with Helium.
Click to expand...
Click to collapse
I will give that a try. It seems like helium backs everything up except for the registration data and the network even when i spoof it still knows it is an S5. They told me at the store they expect eptt to be updated to work with the S5 soon but how long is "soon"? A week or two is no big deal but any longer becomes a real issue. I use it all the time. Luckily I have a paid subscription to titanium so when i get home I will give her a whirl and see what happens.
Same issue. It tries to activate on the network and it wont allow it.
You have to fix your sd permissions use this app.
https://play.google.com/store/apps/details?id=nextapp.sdfix
Ok guys here is the way to do it if anybody else ever runs into this situation. Device spoofer does work but it makes everything on the screen super small and after you activate EPTT and get it up and working then switch back to the stock profile it then stops working again.
In order to get the EPTT app to work on all non supported ATT android phones you must change the phones model number. I followed this tutorial and it worked perfectly. You must be rooted.
http://www.skytechblog.com/2013/01/change-mode-number-to-galaxy-s4-or.html
"Requirements:- A rooted Android device, Root explorer & patience
So let's Start..!! Video Tutorial
1. Start the Root Explorer app.
2. Go to System folder its in the root if the device
3. Make sure that System is in Read/Write from the top right
corner.
4. Look for a file named
build.prop in system folder.
5. Long press it for Options and then choose Text editor.
7. Search the line as followed ro.product.model= and then change the text after = sign to whatever you like your Model number to be displayed.
8. Press back and hit Save.
9. Exit the app and Reboot or simply Power off and on it.
That's it...its done now check the edited name in Settings>About phone> Model number
To get back to the original:- Just delete the build.prop and rename the build.prop.bak again to build.prop and reboot "
I changed mine to an S4 which is supported. The registration network looks for the Model number to verify it is being used on a supported device. Simply change it to the name of a supported device and waaa laaaa working EPTT.
As you can see by the icon at the top left I am signed in to EPTT and it does work great on the S5.
I know very few use this but for those that do and want a newer phone then here is your 100% working answer if you are willing to root your phone.
Change the dpi on your Galaxy S5!
Requirements: Root, Supersu, and a nandroid or build.prop backup to go back to in case you mess up.
I tried this out on the Stock S5 Rom and the Extreme Debloat 2.1.2 Rom
1. download build.prop editor from the play store.
2. Click on the '+' at the bottom, click predefined properties, then find ro.sf.lcd_density then put in the desired dpi value.
3. 480 is stock for the S5, 422 is what you see when you use a rom-slot When you make the change, approve it with Supersu. Make sure it happens.
4*. If you're being safe and using a rom slot to try this out, you have to shutdown the device, let it vibrate, then take out the battery because the shutdown sequence freezes. After that pop it back in and turn on your phone. If you're on the stock slot, just reboot
5. If you're new dpi number works, your phone will boot properly, if it doesnt you will get a 'device memory damaged' alert and even if you click 'reset device' it will continue to do this whenever you turn on your phone forcing you to restore the build.prop or nandroid with a backup.
Apparently, my method overwrites the hidden ro.sf.lcd_density that doesnt appear when you search build.prop with a new and visible one! Hopefully I've discovered something that will contribute to this board. Enjoy!
To fix the small camera problem, you can use xposed framework module app settings and change the dpi back to 480. Im having difficulty fixing it for the phone dialer. Hopefully somebody can find the solution.
Please post working dpi's below.
Confirmed working dpis: 480, 422, 420
psm510 said:
Change the dpi on your Galaxy S5!
Requirements: Root, Supersu, and a nandroid or build.prop backup to go back to in case you mess up.
I tried this out on the Stock S5 Rom and the Extreme Debloat 2.1.2 Rom
1. download build.prop editor from the play store.
2. Click on the '+' at the bottom, click predefined properties, then find ro.sf.lcd_density then put in the desired dpi value.
3. 480 is stock for the S5, 422 is what you see when you use a rom-slot When you make the change, approve it with Supersu. Make sure it happens.
4*. If you're being safe and using a rom slot to try this out, you have to shutdown the device, let it vibrate, then take out the battery because the shutdown sequence freezes. After that pop it back in and turn on your phone. If you're on the stock slot, just reboot
5. If you're new dpi number works, your phone will boot properly, if it doesnt you will get a 'device memory damaged' alert and even if you click 'reset device' it will continue to do this whenever you turn on your phone forcing you to restore the build.prop or nandroid with a backup.
Apparently, my method overwrites the hidden ro.sf.lcd_density that doesnt appear when you search build.prop with a new and visible one! Hopefully I've discovered something that will contribute to this board. Enjoy!
To fix the small camera problem, you can use xposed framework module app settings and change the dpi back to 480. Im having difficulty fixing it for the phone dialer. Hopefully somebody can find the solution.
Please post working dpi's below.
Confirmed working dpis: 480, 422, 420
Click to expand...
Click to collapse
Good work. Been seeing people trying to do this. hopefully you found the correct fix. Thanks for letting the community know.:thumbup:
I changes dpi to 380 but lock screen is smaller, contacts etc....i changes dpi back to stock inside app with xposed appsettings... All work good only lock screen still small... I don't now find files for edit for biggest lockscreen..
Druss81 said:
I changes dpi to 380 but lock screen is smaller, contacts etc....i changes dpi back to stock inside app with xposed appsettings... All work good only lock screen still small... I don't now find files for edit for biggest lockscreen..
Click to expand...
Click to collapse
You would change SystemUI, that changes the notification bar/panel as well though among other things and makes having your dpi lower pretty much pointless in my opinion.
Sent from my SM-G900A using Tapatalk
Hey guys,
so I flashed the Android M preview from Vomer, despair M Kernel, and SuperSU and everything is working fine/I have working root access. I am trying to go into the build.prop to edit a few things but every app I use to try and edit it is giving me an error and saying it failed. It is also not saving any changes that I make and try to push through ADB. Does anyone have any idea what is happening here and/or how to fix it?
Thank you in advance.
Try pushing it using and whilst in recovery as a work around. As for the main issue, no idea
I used root explorer(with m and despair kernel) to edit my build.prop, without any issues.
Tried all the major explorer apps while running the M preview on my Nexus 6. None seem to be able to successfully save (some say they did, others report a failed save) the build.prop edit.
Sent from my Nexus 6 using XDA Free mobile app
natemup said:
Tried all the major explorer apps while running the M preview on my Nexus 6. None seem to be able to successfully save (some say they did, others report a failed save) the build.prop edit.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
sounds like you might not be doing it right. I use root explorer, copy/paste whatever into the build.prop, save it, then reboot for it to take affect. and it works every single time.
I edited mine just fine with a regular Build Prop Editor from the play store. Runing JDX M preview with despair kernel as well. I needed to get rid of the pesky NAV buttons so I could use LMT.
Hi guys! I was wondering if anyone knows how to enable the Android built in NavBar on this device. I tried very different methods, from apps to manually mods, but nothing worked. I've added the line "qemu.hw.mainkeys=0" at the end of build.prop and nothing happened, so i tried to make a local.prop file containing that line in /data folder and still nothing happened. I've also tried by adding "ro.show.navigationbar=yes" in both build.pro and local.prop but still nothing happened. In the last i've installed Xposed, Gravity Box for MM end tried to enable the navbar from here....guess what? Still nothing happened. Please, does someone know how to achieve this? I need to use the nav bar.
P.s i know about the huge amount of alternatives on Google Play, but i don't want to use third part apps that eats my RAM. If i can enable the system built in there's no reason to download a separate app.
Thanks for everyone who reads this.
How can I temporarily root Lineage 13 in order to edit build.prop and then fully unroot? (looking to disable the capacitive buttons, but maintain PokemonGo functionality)
Okay, so I did an adb edit of build.prop and that worked, NOW I need to disable the capacitive buttons. I've tried commenting out "BACK", "HOME" and "MENU" in the Generic.kl file, but they're all still fully functional.
Any ideas?
Okay, I found the solution, editing the file "synaptics_dsx_s2.kl" and commenting out the virtual mappings works. However the backlight remains on, time to find that fix. ALMOST THERE!
further edit: it looks like it's already an option in Lineage, w00t!
xeper said:
How can I temporarily root Lineage 13 in order to edit build.prop and then fully unroot? (looking to disable the capacitive buttons, but maintain PokemonGo functionality)
Click to expand...
Click to collapse
You can download here: http://www.supersu.com/download
Works perfectly.
To unroot you can search in superSU settings full unroot option.