Softbuttons for N209

[Guest StarG]

Hi all, I'm a noob here, though I,ve been reading with interest for some time. I would like to flash N209 but I would also like Sej's Softbuttons and I don't know how to add them. Can anyone tell me how? Cheers.

[Guest]

Hi all, I'm a noob here, though I,ve been reading with interest for some time. I would like to flash N209 but I would also like Sej's Softbuttons and I don't know how to add them. Can anyone tell me how? Cheers.

You cant just add them,its something that has to be done in the compile stage of the build.

So unless you understand how to build a rom,its a no go I'm afraid :(

Edited September 28, 2011 by Guest

[Guest Kamikaze.]

I also loved the softbuttons :( Check out "Button Savior" from market. Not the same, but does the job.

[Guest Paden]

I also loved the softbuttons :( Check out "Button Savior" from market. Not the same, but does the job.

Looks like sej7278 has a patch available for the soft buttons.

Cheers, Paul

[Guest Kamikaze.]

Are those installable or are those lines installed to rom from dev?

Sent using Tapatalk

[Guest sej7278]

Looks like sej7278 has a patch available for the soft buttons.

Cheers, Paul

that's the patch to apply at compile time, its not something that can be done afterwards.

i also got notification today that the request on the issues tracker has been closed, so it seems unlikely softbuttons will ever get enabled by default on phones in cm7.

[Guest]

that's the patch to apply at compile time, its not something that can be done afterwards.

i also got notification today that the request on the issues tracker has been closed, so it seems unlikely softbuttons will ever get enabled by default on phones in cm7.

Softbuttons removed from issue tracker :o

It makes no sense for cm to not add them,as they are so useful,considering the blades weak buttons.

Will you be uploading anymore softbutton builds sej ?

I believe there is another way to get softkeys.

Its a method I used before you started sharing builds.

And that is to copy frameworkres.apk from a build with softkeys.Then overwrite current one in rom with root explorer and reboot.

But of course it still requires someone to have knowledge of compiling who could upload there frameworkres.apk to modaco..

Edited September 28, 2011 by Guest

[Guest KonstaT]

that's the patch to apply at compile time, its not something that can be done afterwards.

i also got notification today that the request on the issues tracker has been closed, so it seems unlikely softbuttons will ever get enabled by default on phones in cm7.

There is absolutely no reason this can't be done afterwards.

Just decompile framework-res.apk from any nightly with apktool. Edit few lines in /res/values/bools.xml as seen in sej's patch and compile again.

Just had a quick test and seems to work just fine. Five minute job for someone who knows how to use apktool. Problem is that CM7 doesn't use standard platform key to sign their .apks (where can I find the keys used?) so I had to copy the new resources.arsc to the original framework-res.apk which is not the optimal solution...

[Guest]

There is absolutely no reason this can't be done afterwards.

Just decompile framework-res.apk from any nightly with apktool. Edit few lines in /res/values/bools.xml as seen in sej's patch and compile again.

Just had a quick test and seems to work just fine. Five minute job for someone who knows how to use apktool. Problem is that CM7 doesn't use standard platform key to sign their .apks (where can I find the keys used?) so I had to copy the new resources.arsc to the original framework-res.apk which is not the optimal solution...

Any chance of a noobs guide ?

Would love to learn this one.

so used to those softkeys now,cannot imagine cm7 without them

[Guest leetron1]

+1 on the noobs guide...using button saviour which is ok but would love softbuttons back

[Guest Kamikaze.]

Why bother... Test Button Savior out. I think it's even better...

Sent using Tapatalk

[Guest KonstaT]

Any chance of a noobs guide ?

Would love to learn this one.

so used to those softkeys now,cannot imagine cm7 without them

I thought that the noobs guide was already in my previous post, I don't think I can do much better than that. ;) But seriously I don't see much point in this either. You'd have to do it to new framework-res.apk every time you update to new nightly.

I just wanted to point out that it isn't only a compile time thing and it can be done afterwards. It's maybe not the best way to do it, but it's possible. I'm also sure that sej7278 will continue to make his builds with softbuttons when ever there is a good reason for it.

Btw, does anyone know are these the keys that are used to sign the .apks in CM7?

https://github.com/CyanogenMod/android_build/tree/gingerbread/target/product/security

[Guest StarG]

Thanks for all the info, guys. I've now got Button Savior and it works, but if you'll pardon the pun, it's not a patch on Sej's! I prefer those buttons tucked away

in the Status Bar. Ah well, one can but hope. Cheers all.

[Guest sej7278]

I just wanted to point out that it isn't only a compile time thing and it can be done afterwards. It's maybe not the best way to do it, but it's possible. I'm also sure that sej7278 will continue to make his builds with softbuttons when ever there is a good reason for it.

Btw, does anyone know are these the keys that are used to sign the .apks in CM7?

https://github.com/C...roduct/security

i didn't really want to mention that method as it still requires compiling and you'd have to repeat it for every nightly.

someone did make a windows-only app for editting frameworks, which adb pulled the files from your phone running a nightly and then put it back with the patches, but its hacky as hell.

and yes those are the signing keys for use with signapk

as cm 7.1.0 just went final, you'd be better off opening a new ticket on the issue tracker.

[Guest Decadence]

I think you can use the patcher by zdune to add them in, well they worked for me on a nightly a while back.

http://zdune.mod2xtreme.com/android/tweaks.php

EDIT: Just noticed above post

Edited September 29, 2011 by Decadence

[Guest KonstaT]

and yes those are the signing keys for use with signapk

But those are not the keys that the actual .apks in CM7 are signed with. Set of keys must generated sometime during the build process?

I had a quick test with N209 framework-res.apk. I took unmodified framework-res.apk and all I did was that I resigned it with those different sets of keys. Pushed it back to phone and tried to boot after complete wipe.

signed with test key -> bootloop

signed with platform key -> bootloop

signed with shared key -> bootloop

signed with media key -> bootloop

[Guest sej7278]

But those are not the keys that the actual .apks in CM7 are signed with. Set of keys must generated sometime during the build process?

I had a quick test with N209 framework-res.apk. I took unmodified framework-res.apk and all I did was that I resigned it with those different sets of keys. Pushed it back to phone and tried to boot after complete wipe.

signed with test key -> bootloop

signed with platform key -> bootloop

signed with shared key -> bootloop

signed with media key -> bootloop

build/target/product/security/testkey.pk8 and testkey.x509.pem are the ones i use to sign patches just fine

they are the ones used in the build if you look at the compilation output as it scrolls by, they're not generated.

are you getting the signapk syntax right, you're using apktool or something aren't you?

java -jar signapk.jar testkey.x509.pem testkey.pk8 rom.zip rom-signed.zip

i don't think you can re-sign apk's, you have to unpack them and resign the repacked ones.

Edited September 30, 2011 by sej7278

[Guest KonstaT]

build/target/product/security/testkey.pk8 and testkey.x509.pem are the ones i use to sign patches just fine

they are the ones used in the build if you look at the compilation output as it scrolls by, they're not generated.

are you getting the signapk syntax right, you're using apktool or something aren't you?

java -jar signapk.jar testkey.x509.pem testkey.pk8 rom.zip rom-signed.zip

i don't think you can re-sign apk's, you have to unpack them and resign the repacked ones.

Signing a .zip is different because ClockWorkMod never checks .zip if it's signed (or with what key) or not. It installs just fine anyway. I don't even bother to sign my .zips most of the time.

Keys are the correct, signapk syntax is correct. I think you can resign .apks without unpacking/repacking. I've resigned whole ROMs (core .apks in /system/app and /system/framework/framework-res.apk) without any problem.

That's why I'm now thinking it's some build time thing. It's not even that important, I was just wondering. If I really want change stuff with CM7, I can do it before the build. With stock based ROMs I can only do that with apktool.

Edited September 30, 2011 by KonstaT

[Guest sej7278]

Signing a .zip is different because ClockWorkMod never checks .zip if it's signed (or with what key) or not. It installs just fine anyway. I don't even bother to sign my .zips most of the time.

Keys are the correct, signapk syntax is correct. I think you can resign .apks without unpacking/repacking. I've resigned whole ROMs (core .apks in /system/app and /system/framework/framework-res.apk) without any problem.

That's why I'm now thinking it's some build time thing. It's not even that important, I was just wondering. If I really want change stuff with CM7, I can do it before the build. With stock based ROMs I can only do that with apktool.

i think you're doing something wrong. have a google for patcher4windows_by_Z25.zip (xda thread) its a tool to patch the framework-res.apk to enable softbuttons.

signing an apk is no different to signing a zip or jar, they're all basically a zip archive.

Edited September 30, 2011 by sej7278

[Guest KonstaT]

i think you're doing something wrong. have a google for patcher4windows_by_Z25.zip (xda thread) its a tool to patch the framework-res.apk to enable softbuttons.

signing an apk is no different to signing a zip or jar, they're all basically a zip archive.

Could be, but what?

I just resigned the whole N210 with test key. 63 .apks in /system/app and /system/framework/framework-res.apk. Now it boots just fine after full wipe. :)

When I look at META-INF/CERT.RSA inside framework-res.apks, bytesize differs slightly between the framework-res.apk from cm_blade_full-210.zip that I downloaded and exact same file that I just resigned.

Could it be possible that builds that buildbot makes are signed with different key than usermade builds? Probably not.

I have to give up. I know now what I have to do to get softbuttons into any nightly. Lol and I don't care about the softbuttons that much and I don't even use CM7 as my every day ROM (haven't decided just yet). ;)

Edited September 30, 2011 by KonstaT

[Guest KonstaT]

i think you're doing something wrong. have a google for patcher4windows_by_Z25.zip (xda thread) its a tool to patch the framework-res.apk to enable softbuttons.

signing an apk is no different to signing a zip or jar, they're all basically a zip archive.

I said I'd give up but this still bothers me because I don't think I'm doing it wrong. Reading that xda thread you linked only confirms what I've been trying to say all along. Disclaimer in the first post:

Same for tablet tweaks, but after 1st patch you will get a bootloop, so put off and put it the battery, go to recovery install undo, reboot, install patch again and phone will work like a charm

That windows thingy also uses that exactly same (in this case) incorrect test key. That is precisely what happens when you sign framework-res.apk with the wrong key (different from other system .apks). Yes, it will work after original system is booted at least once (dalvik cache is created) and applied after that. If you wipe data/factory reset or wipe dalvik cache or restore nandroid backup (with that file in it), you'll end up in bootloop.

That codebox example you gave was for rom.zip so I just assumed it was a flashable zip. Yes, signing an apk is no different to signing a zip or jar. But signing a ClockWorkMod flashable .zip is different in that sense that ClockWorkMod couldn't care less if it's signed with test key, platform key, your private key or not signed at all. It will install it just fine in any of those cases. Signing a core system app is different in sense that it must be signed with exact same key as rest of the essential .apks. Otherwise depending on the .apk you'll end up in bootloop or you'll have repetitive force closes.

I'd really appreciate if someone knows what key is used to sign the .apks in CM7 (not the CM7-rom-KANG.zip). And before anyone says test key, please try this: Download latests nightly and extract framework-res.apk from it. Sign framework-res.apk with test key. Flash nightly into your phone. Push resigned framework-res.apk into your phone. Wipe data/factory reset and reboot. (-> Bootloop.)

If someone was to edit something in CM7 after build (which I don't necessary recommend), he/she would have to treat it like any other ROM signed with unknown key. Options would be:

1. Copy modified resources.arsc into original signed framework-res.apk as described in post #8. This is quite hacky solution.

2. Resign the whole ROM with any key you desire.

[Guest sej7278]

that's really odd.

do you get the bootloop if you edit a framework-res.apk from a kang and install it after a full wipe, or is it just limited to editing files within a nightly?

i doubt the nightlies are signed with a different key than is in git, i wonder if its related to ro.modversion being different for nightly/release to kang.

[Guest Sulthekk]

I'm wondering since we want to modify framework-res.apk, maybe it can be done automatically with metamorph?

Edited October 3, 2011 by Sulthekk