LG P880 cm10.1.3 stable
how can I enable On-screen Keys and navbar ?
I already tried to to add "qemu.hw.mainkeys=0" line to build.prop. No success here. Wont boot, not even go to the CM logo. Just black screen.
Any Ideas ?
Thx for your help
BTW,
the reason why I want to enable softkey and (if possible) disable the capacitive buttons is the following:
I have hugh fingers. And so often when I type I accidently hit the home button instead of the space bar. It is really annoying. However, I never had this issue with my old SGS and my GalaxyTab.
And another thing: Sometimes when I hit the upper end of the buttons, it fires the long click action, e.g. it goes directly to RecentApps instead of HOME.
There are actually plenty of tutorials all over XDA (general or software section).
Search for it.
If you want further help you have to tell us details about your current setup.
EDIT: Just to let you know,
I searched for 1 min and found 3 different ways. One last tip: don't use the XDA search but Google, way more reasonable outcome.
Sent from my LG-P880 using XDA Premium 4 mobile app
Well, the problem seems to be limited to cm10.1.3.
Code:
qemu.hw.mainkeys=0
works on cm11 nightlies just fine.
Well, thanks for mentioning google. Always helpful.
I still find no other ways than editing build.prop (or using apps that do that for you)
Omario-242 said:
If you want further help you have to tell us details about your current setup.
Click to expand...
Click to collapse
LG P880 cm10.1.3 stable
Click to expand...
Click to collapse
The qemu.hw.mainkeys=0 just means that your device has no hardware menu buttons.
Whether CM didn't set it so this will enable navigation bar or you did something wrong.
5 Mins of search also got me this build.prop line to add:
ro.show.navigationbar=1
Try it.
Sent from my LG-P880 using XDA Premium 4 mobile app
Omario-242 said:
ro.show.navigationbar=1
Click to expand...
Click to collapse
Same as qemu.hw.mainkeys=0 . Does not boot.
I guess i stick with cm11 nightlies then
but thanks anyway
how are you editing the build.prop?
many file editors give problems with boot after edit, the best option is to copy file, edit and then push to phone through adb
the quemu hw keys is universal on cm to tell if your phone has hw keys or not so it should not be causing problems
(also check if it is already present in the build.prop)
If still it isn't working and don't want to change rom you can always use xposed framework which has a few different modules for nav bar
Rudjgaard said:
how are you editing the build.prop?
many file editors give problems with boot after edit, the best option is to copy file, edit and then push to phone through adb
Click to expand...
Click to collapse
that is how i do it
Rudjgaard said:
If still it isn't working and don't want to change rom you can always use xposed framework which has a few different modules for nav bar
Click to expand...
Click to collapse
ehhh .... i guess i stay with the nightlies ... they seem pretty usable as a dailydriver so far
ok, one last option is edit build.prop then flash
the command is correct, the bootloop is not normal that's why i'm insisting on this point
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Adam77Root said:
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Click to expand...
Click to collapse
I forgot about the issues with win you are right.
OP you should edit build.prop with notepad++
open file with n++, add the line, highlight it and check that in the bottom right of the bar it says encoding "Unix"
Adam77Root said:
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Click to expand...
Click to collapse
Thx for the suggestion.
Actually I am on OSX using Sublime Text 2.
But I am looking into it
zzerozzero1 said:
Thx for the suggestion.
Actually I am on OSX using Sublime Text 2.
But I am looking into it
Click to expand...
Click to collapse
Hmm .... I checked : charset stays us-ascii after editing with ST2
Adam77Root said:
Take care of line endings. If you are on Windows, there might be incompatibility with Unix formats.
Click to expand...
Click to collapse
Adam, thank you very much. You pointed in the right direction.
I adb'd into the device and changed the build.prop via shell nano and viola everything works on cm10.1
Related
Hi!
The annoying sounds of my internal/external SD mounting/unmounting whenever I rebooted or changed my usb settings were driving me crazy and I ran across this line in my build.prop
It was set to 1 so I changed the value to 0 and rebooted. The sweet sound of silence!
Find this string in your build.prop and change it to 0, or manually add the string if it isn't there:
persist.service.mount.playsnd=0
Then reboot and enjoy the silence!
For those who don't know, build.prop is located in the /system folder and can be easily edited with Root Explorer. Root Explorer will also automatically back up your original build.prop
*EDIT* NFHimself also let me know you should be able to enter "setprop persist.service.mount.playsnd 0" from adb or in android terminal to add the value. You will have to su first to have root access. Thanks for the info!
This mod is only enabled by default in Gladiatrix, so all credit for this mod goes to Ririal. I just shared it with you all.
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
Thanks for information.
Working fine in my Atrix AT&T.
morocomolr said:
Thanks for information.
Working fine in my Atrix AT&T.
Click to expand...
Click to collapse
Did you FIND/MODIFY the entry already in your build.prop.....or did you have to ADD the entry?? I can't seem to find this entry already existing in my build.prop...??
baddison said:
Did you FIND/MODIFY the entry already in your build.prop.....or did you have to ADD the entry?? I can't seem to find this entry already existing in my build.prop...??
Click to expand...
Click to collapse
The OP stated if it's not there, ADD it... this was included in the latest Gladiatrix P-ROM
persist.service.mount.playsnd=0
baddison said:
Did you FIND/MODIFY the entry already in your build.prop.....or did you have to ADD the entry?? I can't seem to find this entry already existing in my build.prop...??
Click to expand...
Click to collapse
I also don't have this entry..
I don't have it either (but will add per OP instructions). I wonder if Ken removed it in Gingerblur 3.5 in an attempt to stop the mount/dismount notifications. I know he thought he had the issue fixed.
I did it but the sounds persist.... Any help? It´s very annoying sound.
worked for me. Did you restart after? If so, you might try restarting again.
brunnogama said:
I did it but the sounds persist.... Any help? It´s very annoying sound.
Click to expand...
Click to collapse
You have to reboot after.
jpinoy said:
The OP stated if it's not there, ADD it... this was included in the latest Gladiatrix P-ROM
persist.service.mount.playsnd=0
Click to expand...
Click to collapse
I am not sure what added it to mine to be honest. It was either Greyblur or the Cool Blue theme (which I think contains files from Gladiatrix).
Either way, credit goes to them for adding/discovering it to the build.prop in the first place. I am just passing the info along.
Yes, I rebooted twice and the sound still annoying!
EDIT: Wow! I´m so stupid! I put 0 in another line! Now it works! Really thanx!
brunnogama said:
Yes, I rebooted twice and the sound still annoying!
EDIT: Wow! I´m so stupid! I put 0 in another line! Now it works! Really thanx!
Click to expand...
Click to collapse
Hehehe. Glad you got it working.
Worked great. Had to add the entry at the bottom using root explorer. That sound was getting to be annoying.
I'm rooted and sideloaded for now. That's it.
SGTShark said:
Worked great. Had to add the entry at the bottom using root explorer. That sound was getting to be annoying.
I'm rooted and sideloaded for now. That's it.
Click to expand...
Click to collapse
That's great! I have no idea why they chose to default that sound on.
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
So, that´s any way to put off the mount usb sounds?
Again, thanx for this!
Thank you... works here!
Worked great. Thanks.
Sent from my MB860 using XDA App
brunnogama said:
So, that´s any way to put off the mount usb sounds?
Again, thanx for this!
Click to expand...
Click to collapse
Yes unfortunately. You have to edit it yourself or flash a p-rom that already has it edited.
There is no easy on/off setting.
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
You are all welcome! I have learned so much on here from others its nice to be able to contribute something back!
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
Works!! ...awesome job OP.
i saw this over the Nexus S thread, and thought it would be awesome if we had the Recent Apps on a click of a button, but not by holding the Home button..and since we don't use the Search button (at least i don't) , we could remap it so it could show the Recent Apps..
so.. here is the MOD : [MOD][19 JAN] Search key to ICS recent apps [add CM9, AOKP and Peter Alfonso version]
and the HOW-TO : [HOWTO] Remap hardware button to ICS recent apps
i tried to make it myself, but i couldn't, so i would like to make a request, or a little help for this MOD
Credits: evilisto
The first link is a flashable .zip, did you try it yourself? I feel tempted to... It's for IML74K so it should work I guess.
The second one is just the instructions on how to do it ourselves, I might try this tomorrow, right now I need some sleep.
So is the flashable zip usable with the teamhacksung ics version?
jonnyg1097 said:
So is the flashable zip usable with the teamhacksung ics version?
Click to expand...
Click to collapse
you gotta change the build.prop in the zip file so it would be flashable on i897
jerkysh said:
you gotta change the build.prop in the zip file so it would be flashable on i897
Click to expand...
Click to collapse
Did you get it to work jerkysh?
I am very interested in this. This would make they search key useful, as I never use it.
Sent from my GT-I9000 using XDA App
jerkysh said:
you gotta change the build.prop in the zip file so it would be flashable on i897
Click to expand...
Click to collapse
Or you can just remove the assertions from the update scripts. It seems to work, but it messes up some framework assets, as I was expecting, see the screenshots.
I'll see if I can the file from our build, decompile, make the changes and then recompile but I'm pretty new at this stuff. For instance.... do I have to sign the file to be able to use it, and how do I do that?
and yes, it works beautifully. having the app switcher just one tap away makes this a true multi tasking device to me. You will lose this button functionality though, so if you depend on it this won't work for you.
cumanzor said:
Or you can just remove the assertions from the update scripts. It seems to work, but it messes up some framework assets, as I was expecting, see the screenshots.
I'll see if I can the file from our build, decompile, make the changes and then recompile but I'm pretty new at this stuff. For instance.... do I have to sign the file to be able to use it, and how do I do that?
and yes, it works beautifully. having the app switcher just one tap away makes this a true multi tasking device to me. You will lose this button functionality though, so if you depend on it this won't work for you.
Click to expand...
Click to collapse
I probably can't help you in any way to get the job done, but I'm always willing to beta test while I learn how to do some of this stuff. Let me know if you need a second person to test and debug.
Sent from my SGH-I897 using XDA App
MrOpportunity said:
I probably can't help you in any way to get the job done, but I'm always willing to beta test while I learn how to do some of this stuff. Let me know if you need a second person to test and debug.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Cool.
I'm sure someone in this forum has to know what they are doing heh.
So far I'm stuck in here: I have to OneCosmic's source code, but how do I convert the new PhoneWindowManager.java to a smalli file??
PATCH NO LONGER NEEDED!
This post used to discuss a patch I made to show the Navigation Keys in Phone GUI mode. I am happy to announce that the patch is no longer needed.
In CM9 the Phone GUI is activated anytime you set the lcd density to anything higher than 160 dpi. With the Nook Color when you go to the Phone GUI the navigation keys are suppressed.
There is a method to activate the Navigation Bar that requires no patches or zip flashes. Just add the two lines below to your local.prop file in /data. I recommend using local.prop instead of build.prop so that it is not necessary to re-edit the file after each flash of a new ROM. If you do not have this file, create an empty txt file and put these two lines in it:
qemu.sf.lcd_density=240
qemu.hw.mainkeys=0
The first line tells your system to change lcd density to put it in phone gui. You can change the 240 number to any number above 160 and the phone gui will be displayed.
The second line tells your system that your hardware has no physical keys and enables the soft key navigation bar.
Reboot.
If you want to return to 160 dpi and the tablet gui, just delete or comment out the two lines above and reboot.
Also CM has added the ability to customize the navigation bar. Go to settings, system, navigation bar and it will tell you how to do it. You can move the buttons around, add buttons, change how they perform, etc.
5-28-2012 is the last day I will be making patches.
No-moar zips! Yay!
Edit (6-24): Removed last patch. Too many users will still downloading it and it does not work properly with the current nightlies.
Removed screenshots
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?
Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!
Sent from my NookColor using Tapatalk
bornagainpenguin said:
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?
Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I still see 4.1MB as the size of rev 11, which is the latest.
Okay, that's screwy. On my nook it said it was only a few bytes, but now on my phone it is listing the same size as the others. Sorry for wasting your time.
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Sent from my LG-VM670 using Tapatalk
bornagainpenguin said:
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Click to expand...
Click to collapse
Not sure what you mean by two status layout. Do you mean status at top and navigation on bottom?
160 always gives you the tablet layout with the status bar at the bottom, with the battery and time, etc there. You can use other launchers that allow you to modify such things as icon grid layout, etc, but the full status bar remains at the bottom.
If you set anything above 160 (180, for example), it goes to phone mode with the status bar at the top, and if you use my patch, the navigation bar will be at the bottom. You can change the density to anything above 160 and my patch will work. I just chose 240 because it is what I like and gives the most market compatibility. After applying my patch, just change the value in build.prop in /system (ro.sf.lcd_density=).
Yeah, that's what I meant. I will probably give 180dpi a try next time I use the nightlies. Going to mess around with CM7.2 Kang and see how it goes. Thanks for everything, I really hope your patch is made a default option once CM9 goes stable.
Sent from my LG-VM670 using Tapatalk
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.
I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.
--bornagainpenguin
bornagainpenguin said:
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.
I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.
--bornagainpenguin
Click to expand...
Click to collapse
It downloaded fine for me just now and 23 others have downloaded it.
Sent from my Nook Color running ICS and Tapatalk
I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
Sudonym said:
I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
Click to expand...
Click to collapse
The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.
leapinlar said:
It downloaded fine for me just now and 23 others have downloaded it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
At least ten of those were mine. I was out and about last night and yesterday morning so I tried at different places and times before asking about it. I didn't want a repeat of last time where I asked and it was fine later that day. I appreciate the effort you guys put into this kind of stuff and the last thing I want to be is a bother.
leapinlar said:
The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.
Click to expand...
Click to collapse
Just downloaded it on my phone and it looked like a complete package! Thanks!
update: how long is it supposed to take on reboot to apply? I'm stuck in reboot for a while now and starting to worry...
Sent from my LG-VM670 using Tapatalk
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:
Wish I knew what I was doing to screw things up.
Sent from my LG-VM670 using Tapatalk
bornagainpenguin said:
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:
Wish I knew what I was doing to screw things up.
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
Click to expand...
Click to collapse
Sudonym said:
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
Click to expand...
Click to collapse
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.
Really frustrating.
Sent from my NookColor using Tapatalk
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
bornagainpenguin said:
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.
Really frustrating.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
The update to the CM repo broke the packages I offer in Botbrew, which happens when they significantly update the framework apps. Leap's patches always seem to break at he same time. The behavior your describing is what happens when you match a patch and a ROM that are incompatible. I know you have had problems with the downloader, (trust me you're not alone.) Just, one more time, flash the latest build and the latest patch together. The repo did not update again, I can promise you that. I bet with all the flashing and patching, you just did not patch the right build.
I have swapped in the old system apps maybe fifteen times over the last couple days, I know what that behavior is. And I use my own version of leapinlar's patch, so I know exactly how it works and what that behavior means. If it is working for others it will work for you if it has downloaded correctly.
slack04 said:
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
Click to expand...
Click to collapse
The system apps work in any build for the Nook Color, opengl or not.
slack04 said:
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
Click to expand...
Click to collapse
This patch will work with eyeballer's, Samiam303's or your home built version. All you have to make sure of is that you are using a version that is reasonably close in date to the build. As CM9 evolves and improves the base files that I am patching change and old versions of the patch will not work on that build. For instance, the 4-15 patch will no longer work on 4-17 or newer builds. I try to upload new versions when that happens.
I just tested eyeballer's 4-19 non-opengl build with the 4-17 patch and it still works.
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.
Sounds like you are having download problems with with your devices so that might be the issue too.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.
Sounds like you are having download problems with with your devices so that might be the issue too.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.
I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:
Code:
Unfortunately, System UI has stopped.
I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...
Back to CM7 with me I suppose....
--bornagainpenguin
bornagainpenguin said:
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.
I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:
Code:
Unfortunately, System UI has stopped.
I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...
Back to CM7 with me I suppose....
--bornagainpenguin
Click to expand...
Click to collapse
What were you trying to set the dpi to? The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch. Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
What were you trying to set the dpi to?
Click to expand...
Click to collapse
180 DPI. Trying 160 DPI just means that I lose the phone GUI
leapinlar said:
The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch.
Click to expand...
Click to collapse
I've never had great luck remembering the adb commands to push and pull files. I could probably try using root explorer to copy to the SDCard and do it on the netbook? Will look into this....
leapinlar said:
Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Just checked that out and doesn't seem to be a factor. Thanks for bringing it up so I could eliminate it though.
Sent from my NookColor using Tapatalk
Hey guys anyone knows how to put cm9 softkeys? Obviously its for cm9 (by maclaw). I really want to experience full ICS with the soft keys and my back button is all worn out. So any1 has or can make a flashable zip of the soft keys Any help will be much appreciated. Thanks.
Thnx guys, i tried the search but in vain O.O guess im not so good at it.
EDIT: I've tried this : http://rohan999.wordpress.com/2012/03/31/how-to-enable-on-screen-ics-keys-on-any-ics-rom/
But the recompilation using "apktool b framework-res" without quotes fails D:< Help!
Search, there are plenty of tutorials available.
Sent from my GT-S5570 using XDA
if you know how to use adb and apktool, take a look here. but next time, use search option, lazyass...
*edit*
this method messes up statusbar, making it same height as softkeys bar, so there's more to do with it also lockscreen gets messed up... i don't have much time today, but it's interesting...
Buttons
http://forum.xda-developers.com/showthread.php?t=1625589 on SGM Working
Pro100Nikto said:
http://forum.xda-developers.com/showthread.php?t=1625589 on SGM Working
Click to expand...
Click to collapse
nope, it gave me bootloop.
Not working on beta 9
yackovsky said:
if you know how to use adb and apktool, take a look here. but next time, use search option, lazyass...
*edit*
this method messes up statusbar, making it same height as softkeys bar, so there's more to do with it also lockscreen gets messed up... i don't have much time today, but it's interesting...
Click to expand...
Click to collapse
Well i tried modding the values but it fails in recompilation step, see link in thread 1 D:<
kirakun said:
Well i tried modding the values but it fails in recompilation step, see link in thread 1 D:<
Click to expand...
Click to collapse
got same problem, use apkmanager to build it and then just drag resources.arsc to original apk
yackovsky said:
got same problem, use apkmanager to build it and then just drag resources.arsc to original apk
Click to expand...
Click to collapse
Hmm looks nice. I'll try and see what this gives
oh yeah, i used version 5.0.2
I'm not responsible for any of this. This someone else thread and development.
I'm simply posting a link for those who would like to play around with this.
Most of these are apks that will show up in under settings/display/front touch buttons/color. For your choosing.
I have tried pretty much all the softkeysin this thread (that are not girly) and have had no issues what so ever. Proceed on your own. I'm not responsible.
All credit goes to those that made these apps and mods in the thread I'm linking you to.
Link : http://forum.xda-developers.com/showthread.php?p=51905092
I would love to do this, but not having a custom recovery makes me leary.
all these are just apk's that you download and use what ever file manager you prefer and click and install. you dont have to replace any apks or modify anything. so due to that its pretty safe if softkeys apk doesnt work then in settings select another softkey theme and use your file manager to delete the one that doesnt work
Atratus said:
I would love to do this, but not having a custom recovery makes me leary.
Click to expand...
Click to collapse
You can download and install them. Tried it by myself and i'm stock, not rooted and no custom recovery installed!
All you have to do, is download what you want, install as normal apk (don't forget in settings-security to active 'unknown sources').
After you installed them, in the settings-display-front touch buttons-color you find them.
If the 'original' appear on homescreen, just deactivate 'transparent background'.
Sorry about my English.
Sent from my LG-D955 using XDA Free mobile app
Thanks for that. Yeah I've been trying to explain this is safe. Not a mod just normal apk's. I probably should have mentioned in the OP that you don't need root. And hey I learn something new everyday I.e. disable transparent to get them to show the new soft keys on home screen. I didn't know that. Thanks.
Sent from my LG-D959 using XDA Premium HD app
No doubt, I had been trying to get them to stay using the g2 tweak box, and I couldn't do it. That is a simple solution.
mattwheat said:
Thanks for that. Yeah I've been trying to explain this is safe. Not a mod just normal apk's. I probably should have mentioned in the OP that you don't need root. And hey I learn something new everyday I.e. disable transparent to get them to show the new soft keys on home screen. I didn't know that. Thanks.
Sent from my LG-D959 using XDA Premium HD app
Click to expand...
Click to collapse
Worked perfectly on my D959 and disabled transparent as well thanks!