Database Users

Sky Raider ROM 3.3 Final [UPDATED: 10/12/10] FAQ & HOW TO

Decided to help out and with the ok from ihtfp69 i wrote up a FAQ page
for everyone who uses Sky Raider Rom 3.3 Final
feel free to add.
zip is 180,304 kb
Sense 3.3 Requires a FULL WIPE
to avoid reboots make sure you have S-Off, Upgrade the radio to the OTA version
Wipe everything:
Factory Reset
Data Cache
Dalvik Cache
then apply SR 3.3
The initial boot animation is only there for the first boot and reverts to the original thereafter.
The fix for Rom Manager for fix permissions requires you to open Rom Manager once and then it will work after a reboot
Q: How to flash the ROM?
A:good info here... http://forum.xda-developers.com/showthread.php?t=709220
Q: Since 3.3 requires a full wipe, due to all the changes, I was wondering if the MM mappings for the rosie launcher are still compatible with this new release.
A: All of the mappings are new so make sure you clear out the old ones and download the new ones.
Q:how to Change your lock screens from adb or terminal shellLock
A: there are 13 different lock screens including the HTC one
You must be on SP1 or higher to use them
Change your lock screens from adb or terminal shell
Type 'tabunlock' or 'rotaryunlock' to get the menu seen below
Please choose from the menu - S-OFF REQUIRED
1) normal
2) normal+menu unlock
3) normal+trackball unlock
4) music buttons
5) music buttons+menu unlock
6) music buttons+trackball unlock
7) restore HTC lock screen
8) get me out of here!
reboot
Q: how do you get a logcat?
A: Run CMD prompt and in while in the root folder sdk/tools/ run the command "adb logcat" copy paste all you see onto pastebin.com and post the link. or download logcat from market

"HTC Mail Mod for EAS Admin Removal" You just go to settings -> security -> remove admin policy

Any chance someone wants to actually put this on the wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Droid_Incredible
There is a ROM section in there and would be a much better location than in a forum post.
What do you guys think?

supagene said:
Any chance someone wants to actually put this on the wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Droid_Incredible
There is a ROM section in there and would be a much better location than in a forum post.
What do you guys think?
Click to expand...
Click to collapse
up to our mod overground

Baseband version 1.00.03.03.06
hi
I am running SkyRaider 3.0 Sense RC3 but I have been unsuccessful in updating the radio. I've tried HBOOT but it doesn't like the image, tried renaming to update.zip, tried running the zip from Recovery.
Please advise.
thanks
Jack

Hello,
I would like to know what is "HTC Mail Mod for EAS Admin Removal". Is this some kind of feature?
I would like to disable the PIN Lock on my phone that is enforced by my companies security policy. I used to use LockPicker on Android 2.1 but that no longer works. Is there another solution for Android 2.2?
Thanks.
Nevermind I found it. You should add this to the FAQ. You just go to settings -> security -> remove admin policy (forgot the actual name since after I removed it, the option is no longer there)

Im having a couple of problems
1) I cant get my Yahoo mail account to set up, I have installed the Mail Mod from ROM manager.
2) I am trying to install an application from the market and i am getting the error saying I dont have enough space to install. I really dont have many apps so i dont think thats accurate. I have cleared the market's cache, data, and restarted the application, problem still persists.
Thanks for the help

surfboard3r said:
2) I am trying to install an application from the market and i am getting the error saying I dont have enough space to install. I really dont have many apps so i dont think thats accurate. I have cleared the market's cache, data, and restarted the application, problem still persists.
Click to expand...
Click to collapse
Check to see how many saved backups you have. Each backup can be upwards of 300mb's. If you have more than three that could be the problem. Happened to me once before. I got rid of a couple unnecessary backup files and freed up over half a gig of space. Apps from the market installed with no problems again afterward.

chrisloveskaos said:
Q: How to enable Tab Lock Screen with Sound Controls?
A: You need to remove the HTC lock screen to get to the underlying stock lock screen, get into Recovery, mount system, I go into adb shell to remove
cmd prompt
Code:
c:/sdk/tools>adb shell
~# (showsup) mkdir /system/app.disabled/
~# mv /system/app HtcLockScreen.apk /system/app.disabled/
~# exit
Click to expand...
Click to collapse
I keep getting stuck in a boot loop...

Stu_Gotti said:
I keep getting stuck in a boot loop...
Click to expand...
Click to collapse
There was a missing / between app and HtcLockScreen.apk

Can I just install SP2, or do I have to do SP1 first? ROM Manager is not pulling up SP1.....

gobluejd said:
Can I just install SP2, or do I have to do SP1 first? ROM Manager is not pulling up SP1.....
Click to expand...
Click to collapse
i thk just 2 is fine

Hi I just loaded skyraider 3.3 a couple days ago and tried out the lock screens, and up til now I've had no trouble loading the service packs or the lock screens thru ROM Manager but after activating a lock screen and rebooting thru terminal, I'm now stuck on the boot animation, batt pulls don't work, and I can get to recovery but I don't know what to do from there. Please HELP!!!!

m89maru said:
Hi I just loaded skyraider 3.3 a couple days ago and tried out the lock screens, and up til now I've had no trouble loading the service packs or the lock screens thru ROM Manager but after activating a lock screen and rebooting thru terminal, I'm now stuck on the boot animation, batt pulls don't work, and I can get to recovery but I don't know what to do from there. Please HELP!!!!
Click to expand...
Click to collapse
You have to let it sit for a good while... mine took like 5 minutes after changing the lock screen.

Is it normal for it to take up to 3 hours to complete? Cuz that's what keeps happening
Sent from my ADR6300 using XDA App

m89maru said:
Is it normal for it to take up to 3 hours to complete? Cuz that's what keeps happening
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no only 5 mins maybe

Can you update this ROM please? I dont have any bugs that need fixing, but i realllly love this ROM and my A.D.D kicks in if i dont make some sort of change
Already added circle battery and 6bar hehe

Update what exactly though? If you have no bugs then the Rom is fine.
Sent from my ADR6300 using XDA App

m89maru said:
Update what exactly though? If you have no bugs then the Rom is fine.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes i know
How about the lockscreen update? I think he asked if there was any interest, i would love it! Basically eliminate the lock screen altogether

rsarno said:
Yes i know
How about the lockscreen update? I think he asked if there was any interest, i would love it! Basically eliminate the lock screen altogether
Click to expand...
Click to collapse
There icons that can b changed through metamorph. I made mods to mine with colored icons like bluetooth, car mode, sms, gmail, email. Two kinds of email- basic email app icon r have one made for me for yahoo. So now when I get a email a yahoo icon pops up in my notification. Ask a themer to make you some. Themes and apps has some. I suggest using sysinterwolf cuz he is the man.

Don't do it: Reduce LCD Density Setting in Build.Prop For Higher Res Look

hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx

futureshock said:
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
Click to expand...
Click to collapse
The quickest way would be to load up another clean version changing the original to froyo boot it up & go to astro copy the build from system to SD or to the froyo version & restart then delete new version and paste the build into the original froyo & reboot

so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet

Next time, try backing up the android folder on ur SD card before changing anything.. that way a quick format and a trip to ur computer will get ur phone working again..
Sent from my HTC HD2 using XDA App

futureshock said:
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Click to expand...
Click to collapse
Can you share this file here? i got the same problem that many applications can't work with full screen, and i didn't backup this file...
thx~

Sorry for my Englisch.
Problems with the screen in fullscreen games.It is easy to change it.
Open the file with a text editor Build.Prop and edit the line of "ro.sf.lcd_density = 220" to "ro.sf.lcd_density = 240"

Followed the instructions and did this mod.
I sorta of like it. Didn't encounter any problems at all. It's hard to tell the difference. Some apps will support it, Sense UI does not.
The bigger question is. Does this impact battery life. I am still testing this..so right now that's debatable.

I set dpi to 192 and love it. Most apps show more info on screen, a few games are not clever enough.
After using WinMo for 2 years, I'm used to high precision "touching" :-D
A tip: download Spare Parts and use it to turn off compatibility mode.

i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2

vua777 said:
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
Click to expand...
Click to collapse
Not exactly.
The app works but doesn't really make any difference to build.prop file nor does reboot the device.
Your can manually make the changes.
I set it to 200 and I use adw launcher to make usage of the extra space.

Black screen from changing build.prop
So i really wish I found this thread before i tried to change anything. So i also have the black screen when loading android after changing build.prop file, I did copy the file before I changed it. Now i just dont know how to get into the system folder to change it back because when i load android its all black. Can anybody help me here?

[MOD] HTC_CIME v1

Thanks jonasl for this great work for HTC_IME!
However I was looking for HTC_CIME to work on froyo but couldn't find it, so I took some some spare time and modified the HTC_CIME from Hero 2.1
I have tested on froydvillain 1.5.0 and another device with eclair and it works.
And also, the settings for changing input method does not since it requires HtcAlertDialog Builder, I will look more into this another time.
hxxp://img840.imageshack.us/img840/1919/hero1v.png
hxxp://img529.imageshack.us/img529/2010/hero2n.png
Download
hxxp://hotfile.com/dl/69318051/bc2ea22/HTC_CIME_mod_v1.zip.html
Installation
1. adb install HTC_CIME_mod_v1.apk
2. put everything in system to the phone.
Sorry I don't have any permission to put outside links...

gonna try this out on my galaxy s...ill let you know how it goes

alright so it *works* but i have a few issues
the keyboard is squished to the left side of the screen..i dont think the resolution is correct for my phone.
another thing is that whenever i try to change any of the settings, it force closes on me
i am really looking for a usable copy of this for my galaxy, keep it up

Remove fade effect for screen lock/unlock - 2.2.1 - Darky's ROM

Hello
I'm using Darky's ROM v9.5 and I don't like the fade effect when the screen is locked/unlocked. It seems that some lag is present and I want to have no effect at all.
I've done some search but found no solution. The files used for this effect are lock_screen_enter.xml, lock_screen_exit.xml, but how to modify them? They are not plain text files.

You might want to take a look at that....It works perfectly on my SGS running Darky's 9.5
If you want to change the lockscreen animation only;not the whole UI's anim, you could replace the xml files you already have with the ones of your choice.

Thanks for the quick answer..
I tried those files (including stock) but my problem is what is happening right after you press the power button and the unlock screen appears. The files you mention in that thread are related to the animation shown after sliding the lock button.
So, is there any way to turn on the lights instantly when the unlock screen appears?

giony said:
The files used for this effect are lock_screen_enter.xml, lock_screen_exit.xml.
Click to expand...
Click to collapse
I can't really find those two xmls existing in any other archive than "framework-res.apk" under res/anim folder. So, you could try replacing them, unless we are referring to different files.

That are the files, but after you point me on that thread I realized that the files does not control what happens when the unlock screen appears. They controls what happens after you slide to unlock.
I think that is something built in ..in the end I could live with it because the ROM is just wonderful
Anyway, would be nice to be a way so that the lock/unlock will just turn on/off the screen without any effect (it is more like a turn on in three steps, from low light - middle light - normal light level)

I see your point Is it really that gradient that it gets annoying? I mean to say that running 9.5 I don't even get to notice that! Which kernel are you on, btw?

Yes, is pretty annoying...I have used only stock roms until now and this issue was obviously for me from the first uses
The current kernel on my phone is Speedmod. Should I choose the Voodo(recommended) ?
To be honest, I don't know the diff between them..I just heard that Speedmod is better..
LE: with voodoo kernel the problem is solved, no fade effect anymore but I will continue using speedmod(more ram)

Well, as you can see from my signature, I use Speedmod, too, and have no such effect
Could it be that you haven't activated its tweaks or using RFS? You could do it, by booting into recovery.Activate all the <RECOMMENDED> and <OPTIONAL> ones. Not the <NOT RECOMMENDED>. As for the RFS conversion, you should use the "enable lagfix option"+"Convert system" to ext4. And, last but no least, I recommend installing Speedmod with HZ=500 version
Let me know!

Enabled that tweaks and the phone seems to run faster with no additional battery drain, thanks
As for the initial issue(same effect), I already get used with it and is not bother me anymore

Hi, I have Samsung Galaxy and I'm a noob at doing roms for it, I bricked my last one. I would like to know do you have the step by step for the Darky's 9.5 extreme with the speed kernel? Just a question, hope you can help me out.
I used superoneclick to root my phone and when I booted into the bootloader it didn't give me the right prompt to prepare for the rom. Got impatient and said F it and did it anyway well I got what I asked for.

daddyhall2010 said:
Hi, I have Samsung Galaxy and I'm a noob at doing roms for it, I bricked my last one. I would like to know do you have the step by step for the Darky's 9.5 extreme with the speed kernel? Just a question, hope you can help me out.
I used superoneclick to root my phone and when I booted into the bootloader it didn't give me the right prompt to prepare for the rom. Got impatient and said F it and did it anyway well I got what I asked for.
Click to expand...
Click to collapse
Go to darkyrom.com and search for installation guides in the forum. Sorry I can't post the link, but haven't got enough posts...

Remove ONLY NavBar and get full screen space.

Created a new thread to save you some effort
MUST be on JB 4.1.2 or earlier and rooted, if not
You can get JB 4.1.2 from Telstra, look in Android development and flash it via RSD Lite, You must have an alternative input method (I use gmd gesture control), not free but do not consume any screen space; Now add to the buil.prop at the end (qemu.hw.mainkeys=1) and U will have the status bar but not the navbar and no fc.
I have some issues with menu action (auto hiddes and must retry), solved with cm 10 instead of Telstra ROM, little more batt consumption and no blutooth music at the moment.
UPDATE: No need to use another ROM, In Telstra ROM go to config in Your phone, developer options, and check "Disable HW overlays", Ready!
You can use other ROM (4.1.2+) if U want, I like Telstra Rom cause it have good battery and all features in your cell phone works.

Can you expand on what issues you had after making the edit in rsd lite?
Edit: pls disregard. My tired morning brain was thinking SQL lite.
Sent from my DROID RAZR HD using xda app-developers app

Where are you finding Telstra 4.1.2 for the Razr HD? I've done Google searches and found lots of dialog but no downloadable file.

How do you go about bringing the bar back up? Is it easy to add it as a power button menu item?
Edit: nvm i see the gesture suggestion now
Edit2: I've found an app called Taskarou, which puts a nav bar menu as a side of screen overlay. Check it out, send very promising.
http://imageshack.us/scaled/landing/818/screenshot2013030608344.png
http://imageshack.us/scaled/landing/268/screenshot2013030608345.png

Here is the link to Telstra Rom
lesdense said:
Where are you finding Telstra 4.1.2 for the Razr HD? I've done Google searches and found lots of dialog but no downloadable file.
Click to expand...
Click to collapse
Here is the link, I had to change two files because I live in Mexico and my carrier is Telcel, there is the explanation.
http://forum.xda-developers.com/showthread.php?t=2054906

Gesture Control
krucifix85 said:
How do you go about bringing the bar back up? Is it easy to add it as a power button menu item?
Edit: nvm i see the gesture suggestion now
Edit2: I've found an app called Taskarou, which puts a nav bar menu as a side of screen overlay. Check it out, send very promising.
http://imageshack.us/scaled/landing/818/screenshot2013030608344.png
http://imageshack.us/scaled/landing/268/screenshot2013030608345.png
Click to expand...
Click to collapse
Yes look good, but I like GMD gesture control because you can use gestures like an iPad or iPhone, no need to a NavBar tu pop up touching some place in the screen, well the matter is we have options

It's not a good thing to do. Next day one, you miss the bar.

correct ewsnadmy
krucifix85 said:
How do you go about bringing the bar back up? Is it easy to add it as a power button menu item?
Edit: nvm i see the gesture suggestion now
Edit2: I've found an app called Taskarou, which puts a nav bar menu as a side of screen overlay. Check it out, send very promising.
http://imageshack.us/scaled/landing/818/screenshot2013030608344.png
http://imageshack.us/scaled/landing/268/screenshot2013030608345.png
Click to expand...
Click to collapse
Taskarou looks similar to LMT (http://forum.xda-developers.com/showthread.php?t=1330150). But LMT has some lag and, at times, some bugginess. Does Taskarou tend to run smoothly for you?

Probably not possible to remove buttons without root huh?
Droid RAZR HD (current)
LG Optimus One P-504 (For Sale)

Says so in the op..
Sent from my MB886 using xda app-developers app

Now that 4.1.2 is widely available to Verizon users of Razr HD in the US can anyone confirm that you can simply upgrade to 4.1.2 (retaining root), add qemu.hw.mainkeys=1 to build.prop, and then have the Navigation Bar GO, the System Bar STAY, and no FCs? Because that would seem to be a straight-forward solution to what should be an easy problem to solve. I know this solution CAN work because I did exactly this to my Nexus 7. It removed the NavBar (and kept the System Bar), extended the wallpaper to full screen and resized all the icons. I have never had a Force Close. Every app sizes correctly. I use Button Savior to put exactly the function buttons I want in the order I want them right where I want them on screen (normally right under my thumb). Works flawlessly on the Nexus 7. Hope with 4.1.2 it'll become easy to install on Razr Maxx HD.

lesdense said:
Now that 4.1.2 is widely available to Verizon users of Razr HD in the US can anyone confirm that you can simply upgrade to 4.1.2 (retaining root), add qemu.hw.mainkeys=1 to build.prop, and then have the Navigation Bar GO, the System Bar STAY, and no FCs? Because that would seem to be a straight-forward solution to what should be an easy problem to solve. I know this solution CAN work because I did exactly this to my Nexus 7. It removed the NavBar (and kept the System Bar), extended the wallpaper to full screen and resized all the icons. I have never had a Force Close. Every app sizes correctly. I use Button Savior to put exactly the function buttons I want in the order I want them right where I want them on screen (normally right under my thumb). Works flawlessly on the Nexus 7. Hope with 4.1.2 it'll become easy to install on Razr Maxx HD.
Click to expand...
Click to collapse
Now that Root is available for 4.1.2, I tried this out and it worked.
You have to do the following:
1) Make sure to install LMT or PIE control
2) Make sure to install LMT or PIE control
3) edit build prop file qemu.hw.mainkeys=0
4) reboot
5) edit build prop file qemu.hw.mainkeys=1
6) reboot
You shouldn't get force closes. I'm on stock 4.1.2 rooted

Are you urging the installation of LMT or PIE because one of them is specifically necessary for this remedy to work or because you have to have SOMETHING to navigate with if you remove NavBar? As I said in the original post, I prefer Button Savior, which works fine on my Nexus 7. Would using Button Savior instead of LMT or PIE change the result of the mod?
Sent from my DROID RAZR HD using xda premium

lesdense said:
Are you urging the installation of LMT or PIE because one of them is specifically necessary for this remedy to work or because you have to have SOMETHING to navigate with if you remove NavBar? As I said in the original post, I prefer Button Savior, which works fine on my Nexus 7. Would using Button Savior instead of LMT or PIE change the result of the mod?
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Nope. I was only aware of LMT and PIE control as a replacement. I'll check out Button Savior.

To my great frustration, this method did NOT work for me. Getting rid of NavBar while keeping System Bar on my Razr Maxx HD is a near obsession with me at this point. Because I was on a leaked version of 4.1.1 and couldn't upgrade to 4.1.2 I used the incredible information available on XDA (thanks to all) to downgrade to 4.0.4, update the version of 4.0.4, update to 4.1.1 and then update to 4.1.2. I used the VZ OTA updates for every upgrade step. Every step proceeded without error. Once I was on 4.1.2 I used the new root for 4.1.2 to establish root, which also went smoothly. Then I followed the directions in the earlier post -- I installed Button Savior so I'd have an alternate means of navigation, installed Root Explorer, edited build.prop to add a new line reading "qemu.hk.mainkeys=0", rebooted, edited that line to read "qemu.hk.mainkeys=1" (no quotes in either case), rebooted. It should have worked. IT DIDN'T! My NavBar is gone, which is good. My System Bar is gone, which is bad. And I still get "SystemUI has crashed"-type errors. After all these steps that's the same result I was getting on a leaked, rooted version of 4.1.1. I'd love to finally get this right. How?

lesdense said:
To my great frustration, this method did NOT work for me. Getting rid of NavBar while keeping System Bar on my Razr Maxx HD is a near obsession with me at this point. Because I was on a leaked version of 4.1.1 and couldn't upgrade to 4.1.2 I used the incredible information available on XDA (thanks to all) to downgrade to 4.0.4, update the version of 4.0.4, update to 4.1.1 and then update to 4.1.2. I used the VZ OTA updates for every upgrade step. Every step proceeded without error. Once I was on 4.1.2 I used the new root for 4.1.2 to establish root, which also went smoothly. Then I followed the directions in the earlier post -- I installed Button Savior so I'd have an alternate means of navigation, installed Root Explorer, edited build.prop to add a new line reading "qemu.hk.mainkeys=0", rebooted, edited that line to read "qemu.hk.mainkeys=1" (no quotes in either case), rebooted. It should have worked. IT DIDN'T! My NavBar is gone, which is good. My System Bar is gone, which is bad. And I still get "SystemUI has crashed"-type errors. After all these steps that's the same result I was getting on a leaked, rooted version of 4.1.1. I'd love to finally get this right. How?
Click to expand...
Click to collapse
That's not how the edit goes.
Its
qemu.hw.mainkeys=1
Not hk
Replace it. That may be what is messing your phone.
I have my navigation bar hidden and im using pie control which i like more than button savior.
Sent from my RAZR HD using Tapatalk 2

Unfortunately, while I typed the edit wrong in my post I typed it CORRECTLY in my build.prop edit. So, that's not the problem, evidently. Thanks for the great catch though!

lesdense said:
Unfortunately, while I typed the edit wrong in my post I typed it CORRECTLY in my build.prop edit. So, that's not the problem, evidently. Thanks for the great catch though!
Click to expand...
Click to collapse
I am having same issues with my Razr HD. Mine is new which came with 4.1.2 already but I have rooted with the new method, have safestrap installed, all root apps work, root is solid. I followed these steps to a T:
1) Make sure to install LMT or PIE control (** I installed PIE, got it working)
2) Make sure to install LMT or PIE control
3) edit build prop file qemu.hw.mainkeys=0
4) reboot
5) edit build prop file qemu.hw.mainkeys=1
6) reboot
When it says "reboot" I just do a shutdown, wait 10 secs, then power back up (the Razr HD doesn't have reboot option when you press hold the power, only airplane mode and shutdown). I assume that is fine, but tell me if I need to be doing one of those soft resets (i.e. Vol down + power).
System UI FC's after it is set to =1. Not sure why. I have added the line above to the end of the build.prop file (in /system). Does it need to be at the top??
Also, wonder if the launcher has anything to do with it. I am on GO Launcher. I say this since the GO Launcher menu (swiping up on home screen) shows up just below the edge of my wallpaper but behind the wallpaper (so I only see a little bit of the menu then it disappears behind the wallpaper). I can still swipe up to pull a functioning menu in foreground, but this seems odd to me. Anyone else on GO Launcher getting this to work?
Would really love to claim the screen real estate the Nav bar takes up. I can't really understand by Moto/Verizon did this. They say the screen is 4.7, but with the Nav I bet you only have 4.5 or so....
UPDATE: I tried it with Apex Launcher and got same problems. I heard from someone else saying they also have issue on Nova Pro. So it appears not to be linked to launcher being used. I hope something can be found to make this work, having that extra room is SO nice

india23 said:
Now that Root is available for 4.1.2, I tried this out and it worked.
You have to do the following:
1) Make sure to install LMT or PIE control
2) Make sure to install LMT or PIE control
3) edit build prop file qemu.hw.mainkeys=0
4) reboot
5) edit build prop file qemu.hw.mainkeys=1
6) reboot
You shouldn't get force closes. I'm on stock 4.1.2 rooted
Click to expand...
Click to collapse
@india23... can you please enlighten us on the setup of your phone so we can try and understand why this is not working for many others on stock rooted 4.1.2?
- Do you have stock 4.1.2 received from OTA updated and then rooted with motochopper? If not, what do you have?
- What root explorer tool did you use to make edit?
- How did you edit the file, where did you place the new line, any spaces or empty rows before or after that line, etc
- what launcher are you using?
- what are the permissions on your build.prop file?
- anything else you think can help.
There are a number of us on stock OTA 4.1.2 that is rooted and this option doesn't work. It removed BOTH Nav and Status bar, AND there are System UI FC's. Many are saying this is not doable on Stock ROM but you are saying it works for you, so just need to try and understand how and why.
Thanks

surfmly said:
@india23... can you please enlighten us on the setup of your phone so we can try and understand why this is not working for many others on stock rooted 4.1.2?
- Do you have stock 4.1.2 received from OTA updated and then rooted with motochopper? If not, what do you have?
- What root explorer tool did you use to make edit?
- How did you edit the file, where did you place the new line, any spaces or empty rows before or after that line, etc
- what launcher are you using?
- what are the permissions on your build.prop file?
- anything else you think can help.
There are a number of us on stock OTA 4.1.2 that is rooted and this option doesn't work. It removed BOTH Nav and Status bar, AND there are System UI FC's. Many are saying this is not doable on Stock ROM but you are saying it works for you, so just need to try and understand how and why.
Thanks
Click to expand...
Click to collapse
I am using the Rogers XT925 version. It is running Stock 4.1.2 and has been rooted using Dan R's motochopper tool.
I used build prop editor from the play store to add the "qemu.hw.mainkeys" property:
https://play.google.com/store/apps/...vbS5qcnVtbXkuYXBwcy5idWlsZC5wcm9wLmVkaXRvciJd
I am using apex launhcer.
Hope this answers your questions. If not, I can clarify as needed.
Thanks.