I dont know if you guys already know this.
But I just found out that you can completely hide the virtual keys completely, not moving it to the notification bar.
Here's how to do it:
1. Make sure your filesystem is r/w
2. Use root explorer, rename folder /system/board_properties to other name (i just put "z" in the end of the name)
3. Reboot!
I've test it in Urukdroid 1.1b2 and it works like charm. Buttons mode still can be used, but i prefer Button Savior. New version of Button Savior is perfect, no more bug like before.
Try it and tell me if it works!
[UPDATE]
Sibere method (if my method doesnt work) [Post #22]
1. rename or move /system/board_properties folder
2. add this to /data/local.prop:
Code:
ro.board.has_buttonbar=no
ro.board.has_soft_keys=yes
thanks sibere!
btw your kernel for uruk rocks!
Thank you, I will test that afterwards.
But which version is the latest version of button savior? And what's better in the pro version?
And can I undo it, if I rename the folder to board_properties?
Button Savior pro only enable us to change the button arrangement..
The latest version is 1.1.2
Yes, you can undo the change! Just rename it back and reboot..
Why I can't change the name? I've 2.1.08 with chulri's root and r/w filesystem and I can't rename the folder.
What can I do? Should I reinstall the SDE and root?
maybe it only works on UrukDroid because it is fully rooted..
sad to hear that
Now I put the folder to /board_propertiesx but it doesn't work. I could move the folder, and I could rename it, when it was in /.
There isn't a folder in system anymore, but the buttons are still there. Maybe because I don't have Urukdroid?
so you move the folder from /system to / ?
i think it should work..
have you reboot?
Yes, I've rebooted and put the folder from /system/ to / and I renamed it.
But I don't know, why I couldn't rename it in /system but could move it and renamed it in /?...
But is there maybe an other possibility in the local.prop? I tested ro.board.has_soft_keys=yes, but then the touchscreen doesn't work.
I'm still finding other ways to hide the virtualkeys..
Maybe this method only works in UrukDroid I guess..
thank you for trying!
But are there any other guys with stock firmware who want to try it? Maybe I'm not the only one can't hide the buttons.
But what about UrukDroid? Do my files and apps will be removed when I install Urukdroid? Is Urukdroid like the SDE with root?
during Urukdroid installation, there is an option to copy all apps from old firmware to Urukdroid..
but it is not recommended by sauron..
The installation guide can be found @ Urukdroid wiki - http://code.google.com/p/urukdroid/wiki/Installation#Step_one
I think, I will stay with the stock firmware.
But it would be great, if other people with stock firmware would test that, too.
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Edit: After every reboot the Archos-Widget App crashes. I think, it is looking for files in the board_properties folder and can't find them. I freezed this app with titanium-backup and now everything seems fine. Maybe it needs only to disable the archos-widget app without the need to rename the folder to get rid of the buttons.
glimmling said:
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Click to expand...
Click to collapse
nice..
glad to hear that its working
glimmling said:
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Click to expand...
Click to collapse
I tested the same, but it doesn't work.
I will reinstall the SDE and the kernel and will test it again.
I reformatted my Archos 70, put the SDE on it, but it still doesn't work.
Maybe it's because of the firmware 2.1.08?
Hey. Just recognized, that some games will work now without the softbuttons on my a70. Cut the rope and MonkeyBlast didn't run before the modification and now they do.
Sent from my A70S using Tapatalk
Anyone with Chulri's R/W root, try this:
Go into the board_properties folder, find the file that relates to your model(mine is an A101, so my file was virtualkeys.A101IT), and rename it(add .old to the end of it), and reboot. If that doesn't work, try opening the file as text and delete all the text in it, then save as the original filename(not with the .old extension). Also, make sure you haven't turned off the Soft Buttons through UrukConfig or manual edits. You have to reenable the softkeys(remove them from notification bar) to make them disappear completely with this method.
Another option is to hide them mostly--edit the right board_properties file and set their width to something really small, like 10 pixels. Then they remain usable (though the label will be cut-off), but they take up very little screen space.
Worked for me on Archos 101 Churli's R/W Root
I have the 101 with Chulri's R/W root. All I did was move the board_properties to my sd card and rebooted. Abracadabra, their gone. Renamed to board_properties.bak and put back into the system folder. Rebooted again just to make sure it stuck and it did, no soft buttons.
Hi, I have the rom European stock "root" I have used several applications to edit the build.prop and delete some files from /system/app and /system/priv-app, with is file explorer give the root permissions, I delete apps and I modify the build.prop and goes well but when I restart the terminal, applications are back in /system/app and build.prop is as if she had not changed. Any idea what it might be?
Your device, although rooted, still has protection against writing to /system.
Flash the file from THIS thread, then repeat what you did, and the changes will stay this time.
thank you very much, worked very well
Here is the scenario. I updated SuperSU v2.46 that came with the LG G4 root injection method with SuperSU v2.52 by running the Superuser.apk which basically installed /data/apps/<appname>/base.apk which worked as v2.52 except SuperSU will not install itself to /system even though I selected that option in SuperSU in which it said it will need to do a cleanup and reboot. So I manually renamed the base.apk to SuperSU.apk, changed the owner/group to root/root and kept the permissions as rw-r--r--, moved the file to /system/apps/SuperSU/SuperSU.apk, deleted the /data/apps/<appname> folder for SuperSU and restarted the phone. The only thing is SuperSU does not show up in the app launcher and the SuperSU.apk has the Android icon instead of the SuperSU app icon so I flashed the SuperSU v2.52 zip file with flashfire and it did restore /system/apps/SuperSU/SuperSU.apk with the correct icon except the problem is I noticed with Android 5.1 lollipop, you just can't replace a .apk in /system/app by moving it from /data/app as it will not even show up in the launcher. Not sure if this is a Lollipop thing or a LG thing as on previous Motorola phones running 4.4 Kitkat and below, replacing the .apk will usually work. I've cleared the app cache, deleted the files in /data/dalvik-cache/arm, /data/dalvik-cache/arm64 and /data/dalvik-cache/profiles without deleting the folders as I don't know if it's safe deleting the folders and also clearing the system /cache to see if it makes a difference. Didn't work. Does anyone know how I can fix this because it seems like once you updated to a newer version that installs in /data/apps, even if you delete the /data/apps version, it will not use the /system/apps version and simply ignore it. The only reason I still have root is probably because of the su binary still on the system.
Here is the scenario. I updated SuperSU v2.46 that came with the LG G4 root injection method with SuperSU v2.52 by running the Superuser.apk which basically installed /data/apps/<appname>/base.apk which worked as v2.52 except SuperSU will not install itself to /system even though I selected that option in SuperSU in which it said it will need to do a cleanup and reboot. So I manually renamed the base.apk to SuperSU.apk, changed the owner/group to root/root and kept the permissions as rw-r--r--, moved the file to /system/apps/SuperSU/SuperSU.apk, deleted the /data/apps/<appname> folder for SuperSU and restarted the phone. The only thing is SuperSU does not show up in the app launcher and the SuperSU.apk has the Android icon instead of the SuperSU app icon so I flashed the SuperSU v2.52 zip file with flashfire and it did restore /system/apps/SuperSU/SuperSU.apk with the correct icon except the problem is I noticed with Android 5.1 lollipop, you just can't replace a .apk in /system/app by moving it from /data/app as it will not even show up in the launcher. Not sure if this is a Lollipop thing or a LG thing as on previous Motorola phones running 4.4 Kitkat and below, replacing the .apk will usually work. I've cleared the app cache, deleted the files in /data/dalvik-cache/arm, /data/dalvik-cache/arm64 and /data/dalvik-cache/profiles without deleting the folders as I don't know if it's safe deleting the folders and also clearing the system /cache to see if it makes a difference. Didn't work. Does anyone know how I can fix this because it seems like once you updated to a newer version that installs in /data/apps, even if you delete the /data/apps version, it will not use the /system/apps version and simply ignore it. The only reason I still have root is probably because of the su binary still on the system.
I'm rooted with latest Magisk but it's not possible to delete system apps by using root explorer, even when mounted R/W.
Is there a trick or do i have to use TWRP?
Sui77 said:
I'm rooted with latest Magisk but it's not possible to delete system apps by using root explorer, even when mounted R/W.
Is there a trick or do i have to use TWRP?
Click to expand...
Click to collapse
Only trick I know is to download Titanium Backup for Android and give it Magisk root approval.
Use it to delete apps.
Take note: I have destroyed several 100% stock Oreo setups by removing system apps. Have not narrowed it
down to which apps caused that. But be ready for it to never reboot followed by flashing the entire system again.
Hm, I don't understand why it's not possible to delete system apps or folders (in fact apk kan be deletetd, but folder not),
You can delete them in TWRP, but be careful on which apps you delete because as already mentioned in this thread, you can be stuck with an unbootable system.
I'm planning on creating a custom flashable zip for myself that removes certain apps, changes the font, and boot animation in one go; just to streamline the process after I factory reset & update every month.
I can delete the APK by using ROOT EXPLORER, but I'm not able to delete the folder of the app.
Strange, on all other devices that was never a problem
Just freeze what you dont want. What did you want to get rid of anyways?