yashsingh1/xdaforums huggingface dataset:
[Android Software Development] sixfearstheseven:
Could you do me a favor and upload your custom framework-res.apk for preview 5 so I can download it. I've been stuck on preview 4 because last time I ran p5, I edited build.prop and didn't know it broke compatibility. So if your framework has the nav bar height changed, could you share because I don't have access to a laptop right now to edit it myself

EDIT - If you have the CM9 Launcher2.apk that nebkat posted on Google+, use Droid Explorer to navigate to system/app/ to delete the old launcher and paste the new one in. Boot up your phone and press the menu hard key on your phone. In the pop up, you have a new menu item - Preferences. Click it, click Home Screens, and disable the Google search bar to open up more screen space.

If you dont have the launcher, you can download it from nebkat's server which is, unfortunately, down at the moment. I have the previous version of the launcher and will post it as soon as I find it on my SD card. It has the ability to remove the search bar, but lacks a few other features like setting the number of home screens.

You can also search XDA for NovaLauncher and put tthat in /system/app/ as well. I like it because it has a 4x5 home screen, no search bar, and a 3 page sliding dock. You don't have to delete the old launcher to use it, and you don't need Droid Explorer. Just use Root Browser (a free root explorer. Another tip: to remove ads after downloading it, open it and go to system/etc/ and click the + button up top and create a folder called ".root_browser" without the quotes then back out of the app. Open it up again and it won't have ads) from the Market. After downloading the NovaLauncher apk, press and hold it in Root Browser, click move, go to system/app/ and click paste. Set the permissions: first column: all 3 boxes; second and third column: first box. Reboot. When your phone comes back on, press the home button to choose what launcher you want to use.

NovaLauncher apparently can be installed like a normal apk, but if you do it that way, the Widgets won't be in the app drawer like they are with the standard launcher.
[Android Software Development] thisisepic0727:
That is what I needed to know. I've been searching Google and XDA for the steps to do this, but it's been kind of murky. I'll try it after I get off of work; I'm trying to get the on-screen buttons for OMX at the moment.

I was going to change the build.prop, but if it's causing these issues, I'll change the nav_bar_height instead.

Also, is it necessary to turn off the capacitive buttons backlight? Does this affect anything?

Thanks again for your help!
[Android Software Development] sixfearstheseven:
No, you don't have to turn the backlights off if you don't want to.

For those of you that want the CM9 Launcher, the link is below. I'm only going to leave it up until nebkat's server is back online with the updated launcher. This one will allow you to remove the search bar and use the extra space. Replace old launcher2 in system/app/ with Root Browser and remember to set the permissions before rebooting. I highly suggest using Root Browser. ES File Explorer has issues with not wanting to delete files from system/apparently/ even with root access enabled and system mounted as R/W

INSTALL ADW OR LAUNCHER PRO BEFORE DELETING. Just in case something happens, you have a home screen to go back to

https://www.box.net/shared/9nx7yjo77injb45dxy5y
[Android Software Development] thisisepic0727:
Downloaded, and I will definitely have a go at it this evening. I can't wait to test out the on-screen nav buttons and the CM9 launcher -- though I admit, I do like the static search bar at the top on the stock launcher. Darn 3.7 inch display!
[Android Software Development] sixfearstheseven:
You don't have to turn the search bar off. It will still work if you keep it on.
[Android Software Development] thisisepic0727:
It worked! Here is the on-screen nav buttons working on the Incredible running OMX.

I left the search bar on, but it doesn't leave room for much else. Also, it looks like my status bar suddenly got bloated, and I'm 99.9% sure I didn't touch any values there. Also, my lockscreen went jumbo size on me, can't figure out why.

Thanks sixfearstheseven! I'm going to play around with this some more to make it just right.
[Android Software Development] sixfearstheseven:
Awesome. Glad it's working for you.

What all did you change? That's strange that your lock screen and status bar look different. Did you change the LCD dpi in build.prop? That could explain it, but if all you changed was the FALSE to TRUE in bools and the nav bar height in dimens, it shouldn't affect anything else.

Edit - hmm, looking at your screen shot, its obvious you didn't change build.prop, which is a good thing, but very weird that it messed up that other stuff
[Android Software Development] thisisepic0727:
Literally the only two things I changed were the two things you mentioned above (bools & dimens) and nothing else. I didn't even touch the build.prop (as you noted) after you warned me about the compatibility issues.

I followed the rest of the steps you described -- used apktool & changed compression and heap size, used droid explorer to pull and push framework in the steps you described.

I just restored a previous nandroid backup before the changes and I am going to pull that framework and edit it again and see if I get different results. Maybe I accidentally touched something in dimens that affected the status bar and lockscreen (thought I can't see how, I swear I was really careful).

Either way, I'm really happy with the nav buttons, they are a really nice addition. Though I may push the CM9 launcher so I can remove the Google bar to free up some space.
[Android Software Development] aztex00:
Here is the link for my "frameworks-res.apk" file. This is for Evervolv Preview 5 ONLY (as far as I know):

http://www.megaupload.com/?d=EVBKNG31

Changes made in this .apk:

1. Modified nav bar variable to "true" (see step #3 in OP)

2. Modified arrays.xml from:

<integer-array name="config_autoBrightnessButtonBacklightValues">

<item>255</item>

<item>255</item>

<item>255</item>

<item>255</item>

<item>255</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

</integer-array>

to this:

<integer-array name="config_autoBrightnessButtonBacklightValues">

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

<item>0</item>

</integer-array>

3. Modified nav bar height to 37.0dip (See step #5 in OP).

Regarding the backlights for the buttons: I am not sure the lights turned on before I changed the frameworks file. I changed the frameworks file last night. This morning when I woke up and checked my phone, the backlights turned on. Should I edit the arrays.xml file to remove the extra <item> entries so it matches the OP?

I will post a follow up to this with some screenshots that show the current issues I'm facing (keyboard overlap. I only edited the nav bar height. I did not touch my build.prop. I do not have any issues with music or any other apps, save for calendar).
[Android Software Development] sixfearstheseven:
Nebkat posted the updated CM9 Launcher2 on a new server

Here's the link...

http://176.31.247.124/nebkat/
[Android Software Development] aztex00:
Steps taken:

Wipe data/factory reset x 2.

Wipe dalvik cache x 2.

Install Evervolvp5 rom with modified frameworks-res.apk.

Reboot and wait for home screen. Wait 5 minutes.

Turn off phone. Boot to recovery.

Flash gapps.

Reboot and wait for home screen.

Please note that these ARE NOT problems with the rom. These are problems that only occur when you change the frameworks-res.apk file to enable the on-screen buttons. I am convinced that making these changes makes your phone behave like a tablet.

Note: The colors are off in my screenshots as I had to pull these off via Droid Explorer.

Problem #1 - The lock screen. The time is displayed mostly off screen, and the black bar for the on-screen buttons appears at the bottom. It looks as if it's zoomed in, as in meant for a tablet.

Problem #2 - The top bar is about 40% taller now.

Problem #3 - The bottom of the on-screen keyboard is covered up by the nav buttons. They also cover up by buttons in spotify, but I dont have a screen of that.

Problem #4 - The settings menu is split up like like it would be on a tablet. I have not used honeycomb or ICS on a tablet, but I imagine this is how it works. It's split in half down the middle. On the left hand side you have your settings menu, and on the right hand side, a view of those settings. It works best in landscape mode.

As for problem #2, I see the following lines in dimens.xml:

<dimen name="status_bar_height">25.0dip</dimen>

<dimen name="system_bar_height">48.0dip</dimen>

<dimen name="navigation_bar_height">37.0dip</dimen>

<dimen name="navigation_bar_width">42.0dip</dimen>

<dimen name="status_bar_icon_size">24.0dip</dimen>

<dimen name="status_bar_content_number_size">48.0sp</dimen>

<dimen name="system_bar_icon_size">32.0dip</dimen>

<dimen name="status_bar_edge_ignore">5.0dip</dimen>

I may mess with these to see what happens. Regardless, I don't know how to fix the settings and lock screen issues.
[Android Software Development] sixfearstheseven:
Thank you! I appreciate it.

Let me know what happens with the issues you're having when you try modifying again.

Here's another ssomething you all might be interested in. It's an app that lets you remap the hardware buttons to do all kinds of things like pause/play music, skip track, power, even d-pad controls for games. Since the on screen nav buttons are enabled, there hard buttons are redundant, so might as well make them function in a way that makes them usable again.

Link - http://www.androidpolice.com/2010/12/20/modder%E2%80%99s-column-how-to-remap-your-android-phone%E2%80%99s-hardware-buttons-without-touching-a-single-line-of-code/
[Android Software Development] cowboyv:
Quick question, would this work on JB-based AOKP roms?
[Android Software Development] zachf714:
AOKP has an enable switch in rom control

Sent from my Transformer using Xparent Red Tapatalk 2
[Android Software Development] cowboyv:
OK, so since the one I'm using doesn't have one, that means it's a JB-AOSP rom.
[Android Software Development] zachf714:
yep and yeah it should work

Sent from my Transformer using Xparent Red Tapatalk 2
[Android Software Development] cowboyv:
Hypothetically speaking, wouldn't it be easier if I were to copy the res-framework folder from one rom that has the appropriate values, images et al to another one?
[Android Software Development] mattmanwrx:
No, almost all framework-res.apk files are different... for almost every build...
[Android Software Development] asp2010:
This would only work if the (original) framework files in the roms you're copying from/to are identical, which is rarely the case. Unless it's just a minor rom update and the dev states explicitly he hasn't modified the framework in any way, you'd end up with a bootloop.

Ahh, just one moment too late xD
[Android Software Development] mybeshoo:
Dear all , Thank you in advanced about this wonderful Post . i have some questions!

Phone : SGS3 GT-I9300 / Stock TW . JB 4.1.1 "Dont know if you support JB but i wana try :)"

I did follow the steps :

Edit : system/build.prop

qemu.hw.mainkeys=0

/ restart !

And it work with as charm !

But i dont like how it behaves . eg , if you are in T/W home . and you want to go to settings , normally you will press the physical menu button .

but now if you press it nothing happened.

And there is no menu button in the soft keys nav bar ! while you are in the TW / home.

I dont like to have a soft button for recent tasks ! long press on soft home button is good but in this modification , long press on soft home button open "S Voice" !

NOW

What i am looking for is to clone the physical keys order of SGS3 and functions ! " I want to save my home button "

look Number 1 :

###############

Menu - Home - Back

==================

Long press on home i got resent task manager .

Long press on Menu i got Google Now !

====== and i DONT want to disable the real keys ! ==========

The physical home Button i want to make it to take photo if i pressed it while i am on Camera Program .

And if i pressed while the Screen Off , Mob will turn on , if i press it while i am in TW , NOT the camera app . Go Home / Long press . Bring Task !

===========================================

Lock 2

########

Just home key in the middle - Long press bring task manager

and the physical home key still as it

the physical menu key and back key stay as it is !

PS , i did read this ::

Is there any other way , clean and simple

Thank you for your reply !

beshoo
[Android Software Development] AgentSmith:
On a cheap IQ1 by Thai brand i-Mobile I managed to enable the on-screen buttons through modding and recompiling framework-res.apk. The buttons work fine but then a lot of apps such as Play Store, Talk and even the keyboard crash, and they keep crashing as long as the system keeps trying to restart them. This renders a lot of system popups in a short time. Unfortunately changing the navigation bar height in framework-res.apk does not solve this problem. I haven't tried changing the system dpi yet but something tells me it won't be the solution either. Plus I don't want to lower the dpi for usability reasons.

Normally I can find a solution to every IT related problem such as this but this time it seems no one has ever reported a problem like this before. But this is XDA so I hope to get some answers this way.
[Android Software Development] asp2010:
Getting a lot of FCs in a short time usually happens when you don't wipe the dalvik cache after you change something to your framework. Try doing this, or switching back to the original files to see if it still happens.
[Android Software Development] AgentSmith:
Thanks. I actually tried that already. I usually wipe both cache and dalvik cache. After putting back the original the force closes disappeared and everything was back to normal. I could try a complete data wipe.
[Android Software Development] asp2010:
If FCs don't happen any more with the original file, I doubt a full wipe will change anything. It's likely that something goes wrong when you mod the framework. You could try decompiling it and making the changes again, and be sure to use the latest version of the tools.

If this doesn't work, it probably means there is something different with your device's configuration and you need to do additional things to enable this mod. Unfortunately, I don't know where you could find it... :(
[Android Software Development] rajit:
thnx dude..

i am a noob.

so, if upload the femwor...... & sytemui could u plz modify it ??

plzzzzz

:confused:
[Android Software Development] AgentSmith:
Thanks again for your reply. Yes I already used the latest tools. Today I discovered something else however. After manually copying back the original .apk the phone seemed ok. However the Google Play store crashed every time a downloaded app started to install, right after the download was complete. I solved the problem by simply restoring the complete system+data backup. Somehow there must have been something wrong in the copy process as even the original file caused problems.

I don't know if the two issues are related. In any case I always changed the permissions of framework-res.apk with chmod to 644 just like it says in certain how-to's. In fact these are the original permissions of the original .apk so it starts to look a little mysterious to me...
[Android Software Development] pratikmore:
I cant see on screen button on my hcl me u1 tab,so I made the modified framework-res.apk from here but same result.any help?system ui fc?
[Android Software Development] RomWiz:
Hi!

I made this work on an ICS rom for p970 and i wounder if i could add buttons to it, like power, search and so on?

Also does this work on 4.1 and up?

Thanks in advance :)
[Android Software Development] mattmanwrx:
Works on all above 4.0 :) may even work on 3.2, but what still has 3.2 lol...

Yes, u can add buttons to it... U need to add the line in systemui res/layout/navbar.xml is where it is usually.. You need to change the widths (to make it display properly), and you need the correct system button code... You'll also need to add the image in systemui drawable... I think there may also need string changes too... I'll see if I can find the thread...

EDIT: the only one I could find in the limited time I have... - http://rootzwiki.com/topic/33400-how-to-adding-a-button-to-the-navbar-manually-jb-or-ics/

Looks like a good guide though...
[Android Software Development] RomWiz:
So!

I enabled what was in op but when i flashed and booted nothing happened :/

Using HTC sensation with ViperS rom!
[Android Software Development] mattmanwrx:
ViperS is sense based? if so, that is why... com.htc.resources overides the frameworks-res (to an extent)... speak to the dev of your rom :)
[Android Software Development] RomWiz:
Sv: [HOWTO] enable on-screen buttons in ICS rom

Aha, can i do anything about it?

/Daniel
[Android Software Development] mattmanwrx:
speak to the dev of your rom, they might no what to do..
[Android Software Development] KBanause:
AW: [HOWTO] enable on-screen buttons in ICS rom

As long as you want to use Sense: no
[Android Software Development] jerasimo:
After coping the res folder to the original apk the size of the apk goes from 8mb to 14mb. is this mormal?:confused:
[Android Software Development] bhumik147:
Thanx...but will it run in sola?? Ics
[Android Software Development] mattmanwrx:
but check the original that you decompiled? As the original original will have the signing certs (meta-inf folder), while the one you compiled, wouldnt, hence moving it back to the original with the certs in there...

What is sola? It will should work on most roms with stock AOSP ICS+ (maybe even honeycomb+)

EDIT, See you sig is Xperia Sola, so it is an Xperia... It may not work with a manufacturers overlay..
[Android Software Development] dargor1406:
I dont get this tutorial..

in the "how to compile apk tut" says that any edited .xml files must be decompressed but the one that we edited are not in the .zip folder
[Android Software Development] Attitude.SSJ:
Yep that's normal...continue...
[Android Software Development] jacobmacek:
it would be awesome if you could post how to add a toggle to the settings to turn nav bar on/off and turn soft key back light on/off

---------- Post added at 03:49 AM ---------- Previous post was at 03:47 AM ----------

Just install virtuous ten studio, it's an all-in-one tool for apk, jar, and boot.img modification, it will make your life 10x easire when it comes to this stuff :)
[Android Software Development] TheTehk17:
I just tried this with CM10.1 on my Galaxy Player 4.0 and at boot all I get is a bunch of System UI force closes. I can see the dark space where the navbar should be but no buttons come up and then it FC's, and repeats.

I'm attempting to implement in a ROM, so clearing dalvik cache is definitely not a potential fix as I wipe everything before installing.
[Android Software Development] alvanyap:
tried decompile the framework-res.apk, from the bools.xml show that the navbar is true by default but i didnt get the soft button, any clue?
[Android Software Development] plegdroid:
Afternoon matey. There is another way to enable softkeys by editing your build prop. So much easier than decompiling an apk:)

http://xdaforums.com/showthread.php?t=2012551

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[Android Software Development] aztex00:
Reflashing didn't fix the problem. :( See my edited post for screenshots.
[Android Software Development] sixfearstheseven:
The only way to make the ROM think your phone is a tablet is to change the dpi in build.prop to 160 or less. There was just an article about this on Android Community. I can't see how modifying franework-res is the cause for those problems when myself and others are enabling the keys and not having these problems.

Then again, I haven't tried it on Evervolv p5. I had to switch back to p4 for now because I was getting too many random reboots. I'll mess around with it in the morning and report back. Of I have the same issues I'll dig and test and see if I can help you out.

Edit - wow, OK, just saw your screenshots. That is strange indeed. Wtf is up with the colors being off too? My guess is maybe something got screwed up when recompiling. That's just a guess. Are you using apktool? Try APK Multi Tool. When recompiling, it will ask if its a system file. Enter y. It will then ask if you want to keep unedited files to avoid errors. Enter y. It will then say press any key to continue, but before hitting any key, delete resources.arsc from the keep folder within the APK multi tool folder, then hit any key to continue
[Android Software Development] jioleight:
ill try this
[Android Software Development] hackergnome:
m having problem recompiling it...

can anyone make it for me?

here's the framework...

http://db.tt/anm2mtl3
[Android Software Development] thisisepic0727:
I had the same issues with the framework for OMX, the lockscreen got really big and the status bar decided to put on some extra pounds for the holidays. I haven't tried to mess with it anymore, but when I do I'll look around to see what I can find.
[Android Software Development] sixfearstheseven:
I can do it for you. Give me an hour or so to wake up. What ROM are you using?

I'm gonna try it with the OMX and Evervolv ROM as well to see if I get the same issues you guys are having. I had it working with Evervolv 5 the other day and didn't have any issues other than app compatibility being broken because I had edited build.prop, but I'll try again without editing build.prop this time and see what happens.I know with ics-deck 4 and 5 it works just fine, so if you guys want to try it with that ROM maybe. Kush just released p7 with improved hardware acceleration. I haven't tried it yet, but I've liked ics-deck better than OMX and Evervolv anyway since p4
[Android Software Development] aztex00:
I installed ics-deck-inc pre-alpha 8 this morning and it runs like a dream. Boots quickly and feels faster than Gingerbread. No reboots and only one crash: maps labs.

However, replacing the framework-res.apk file does indeed cause the same tablet behavior (see attachments).

The lock screen now shows a garbled clock.You cannot unlock the phone in portrait mode as the unlock button is off the screen. You will have to rotate your phone so that the optical button is to the right of the screen. You can then unlock.

Conclusion: You probably won't want to enable on-screen buttons until we can fix this.

EDIT - The /build folder is created when the apk is being compiled. It is not part of the apk immediately after decompilation. Putting this back in makes no difference.
[Android Software Development] aztex00:
On a side note, if you like the ICS boot animation as much as I do, you can add it to any ROM that doesn't have it by copying the bootanimation.zip file from the Evervolv Preview 5 ROM and move it to the system/media folder on your phone or ROM .zip file. :D
[Android Software Development] sixfearstheseven:
For what it's worth, the new size of the apk doesn't matter (unless, of course, files and folders are actually being excluded. I don't understand why the newer roms would compile differently than previous versions though). With ics-deck 4 (the build I'm using now with working on screen keys) the modified framework-res is 4mb smaller than the original and it works flawlessly.

Sorry I haven't contributed much today. Been out with the wife Christmas shopping. I'll be home in a little bit and will test things out to see what happens on my end. Hopefully we can figure this thing out.

Sent from my Ice Cream Sandwiched-out Droid Incredible