Develop Bugs

[Bugfix][Gingerbread-JV*] Oversized/Unaligned browser combobox in themes.

Hi! I noticed this bug in ock's theme originally and then when I was trying to make my own theme banged heads with it myself.
The issue is that in the browser the combobox button seems to spill over into the text and generally is stretched poorly.
Like this:
I tried at first simply creating a .9.png version and removing the originals and replacing with the .9s. This made the bar vanish completely.
Eventually I got it working with a bit of a work-around, by compiling the .apk twice and extracting the images.
Having to explain that process recently lead me to the real answer though.
combobox_disabled.png and combobox_nohighlight.png ARE .9.pngs even though they do not have the .9.png extension.
apkmanager won't decompile (or compile) them as .9's because they don't have the right extension (and the right extension 'breaks' the theme).
Attatched are my .9.png versions of both images. I added the guidelines from scratch, but they seem to be correct. If your theme has this issue and you need to fix it, just drop the 'compiled' versions into your res/drawable-hdpi and apk-manager should happily compile it and the issue should be resolved.

tried both versions to just replace the ones in my framework-res.apk (didn't decompile the file but just replaced the files) and both didn't solve the problem.

XlAfbk said:
tried both versions to just replace the ones in my framework-res.apk (didn't decompile the file but just replaced the files) and both didn't solve the problem.
Click to expand...
Click to collapse
That -may- not work. That was one of the first things I tried to do - replace with .pngs straight from stock without a decompile/recompile of the whole apk.
The format of the zip file might be slightly ambiguous.
9s - are the raw pngs with draw9patch guidelines.
compiled - are the compiled draw9patch pngs. If you use a draw9patch compiler on the files in the 9s directory you get these.
Even though the pngs are compiled you still need to go through the decompile/recompile procedure with apk manager. (using the 'compiled' pngs).

sargorn, I've tried several times to decompile and recompile the framework with no luck. The new framework is ok, except this damn combo box rendering.
I personally gave up trying :|.

Toss me the framework and I'll give it a shot.

here's mine, based on JVB. thx fo giving it a try

XlAfbk said:
here's mine, based on JVB. thx fo giving it a try
Click to expand...
Click to collapse
Hi,
I tried decompiling and then recompiling your framework and it does not recompile.
zzzzz_tw_quickcontact_slider_btn_pressed.9.png and zzzzz_tw_quickcontact_slider_btn_selected.9.png were both 0 bytes.
If you've just been replacing images this probably won't work
Here it is decompiled and recompiled with stock copies of those two files and the combo box 'fix'.
The filesize seems very 'off' so I'm not sure if it'll work or not.

ro_explorer said:
sargorn, I've tried several times to decompile and recompile the framework with no luck. The new framework is ok, except this damn combo box rendering.
I personally gave up trying :|.
Click to expand...
Click to collapse
I've just de/recompiled JVH's framework-res and the combobox fix still seems to work. (Although maybe it's not needed in JVH, didn't test it!).

I tried it again with JVH and failed again. What I did:
1. decompile framework-res.apk with apkmanager
(2. make some of my changes to some xml files)
3. place the 2 files from compiled in drawable-hdpi-v4
4. recompile the apk
Everything but the comboboxes works as expected.
I'm attaching the apk, maybe you could have a look at it. If you can make it work please tell me what I did wrong. Many thx

XlAfbk said:
I tried it again with JVH and failed again. What I did:
1. decompile framework-res.apk with apkmanager
(2. make some of my changes to some xml files)
3. place the 2 files from compiled in drawable-hdpi-v4
4. recompile the apk
Everything but the comboboxes works as expected.
I'm attaching the apk, maybe you could have a look at it. If you can make it work please tell me what I did wrong. Many thx
Click to expand...
Click to collapse
As im here looking for the fix for my dhd I thought I might be able to help
Looking at your framework I can clearly see that those images in there are not fixed.
Try simply dragging and dropping the fixed pngs straight into your framework

liamstears said:
Try simply dragging and dropping the fixed pngs straight into your framework
Click to expand...
Click to collapse
that won't work, was said before, needs to be compiled in

Try out the jvo rom - I think this issue may be resolved in that framework.
Sent from my GT-I9000 using XDA Premium App

I still have that issue with my JVO theme

[Q] Theming: Including the 9-lock-mod in a theme

Can anyone please point me to a tutorial (or write one) on how I can "inject" the 9-lockscreen-mod into the theme I'm currently running?
I have both the CWM-zip for the theme, as well as the source for the 9-lock-mod.
As I understand it there are 3 files that needs modification:
- framework-res.apk
- framework.jar
- android.policy.jar
I have modded the framework-res.apk using APK Manager (although I haven't tested it). But I'm unsure as to what I'm supposed to do with the .jar-files.

whaave said:
Can anyone please point me to a tutorial (or write one) on how I can "inject" the 9-lockscreen-mod into the theme I'm currently running?
I have both the CWM-zip for the theme, as well as the source for the 9-lock-mod.
As I understand it there are 3 files that needs modification:
- framework-res.apk
- framework.jar
- android.policy.jar
I have modded the framework-res.apk using APK Manager (although I haven't tested it). But I'm unsure as to what I'm supposed to do with the .jar-files.
Click to expand...
Click to collapse
You should be able to decompile them like .apk files. Try renaming their extensions to apk.

Thanks, man!
And it's actually your theme I want to keep (with LockeOn' mod), but I also want the 9-lock. (Specifically the MIUI).
I'll try to rename and decompile. Should I decompile any of the above mentioned files with dependancies?
Sent from my GT-I9000 using XDA App

Well... Im using a galaxy 3 but i believe the method must be somewhat same for all phones... So indirectly... SAME QUESTION HERE...

Android 4.0 SDK Dump

http://evervolv.turnertechrepair.info/Clark44/Android4.0-System-Dump.zip
Courtesy of Jrbourque
EDIT: Thanks Efrant, Title changed.
EDITED WITH ALTERNATE LINK

link didnt work for me

The correct link http://evervolv.turnertechrepair.info/Clark44/Android4.0-System-Dump.zip

from twitter.com/#!/ts0cha0tik/status/126506123288248320 the correct download link is t.co/MagyJCbm

Thanks! Now to see what I can rip off and put on my incredible.

Is there any confirmed way to deodex the apps and framework? The latest smali/baksmali didn't work for me.

sdk dump. same as before..

Why do people keep posting SDK dumps? We all know where the SDK dump is available...
OP, please change the title to reflect that this is the SDK dump...

I just jumped into their irc channel to check if anyone had analyzed the reason for baksmali failing on the ICS odex files. It seems it was basically a function that had changed syntax, requiring several other changes but HomerSp sent me a working baksmali.jar. Smali then doesn't complain when compiling the result.
Unfortunately he went offline just after that so I'm not sure he would be ok with me posting it here so I won't. I'll write a script to deodex the files instead and upload the results if nobody else does so.
I was actually just curious about why it failed, didn't expect at working version just like that.
EDIT: Done and uploaded. Thanks again to HomerSp for the working baksmali.jar!
framework-deodexed.zip
app-deodexed.zip
NOTE: I just realized I forgot to fix the signatures so for the apps it will probably fail unless resigned. I leave that to someone else though. I have not verified that these are valid but as I said, at least smali didn't have a problem compiling them so they are hopefully ok.

blunden said:
I just jumped into their irc channel to check if anyone had analyzed the reason for baksmali failing on the ICS odex files. It seems it was basically a function that had changed syntax, requiring several other changes but HomerSp sent me a working baksmali.jar. Smali then doesn't complain when compiling the result.
Unfortunately he went offline just after that so I'm not sure he would be ok with me posting it here so I won't. I'll write a script to deodex the files instead and upload the results if nobody else does so.
I was actually just curious about why it failed, didn't expect at working version just like that.
EDIT: Done and uploaded. Thanks again to HomerSp for the working baksmali.jar!
framework-deodexed.zip
app-deodexed.zip
NOTE: I just realized I forgot to fix the signatures so for the apps it will probably fail unless resigned. I leave that to someone else though. I have not verified that these are valid but as I said, at least smali didn't have a problem compiling them so they are hopefully ok.
Click to expand...
Click to collapse
First i will like to say thanks, great work, the APKs will still not install, it keeps saying "there is a problem parsing the package." Is there any fix???

max63094 said:
First i will like to say thanks, great work, the APKs will still not install, it keeps saying "there is a problem parsing the package." Is there any fix???
Click to expand...
Click to collapse
As I said, they are not signed correctly as that would require me to remove the current signature files and resign them. I am currently sick so I didn't feel like doing it since anyone else could fix that if they wanted to.
To fix it, remove the META-INF folder from the apk and then sign it using jarsigner (part of Java JDK) or signapk. If you want to install them as normal apps you would need to make sure you pack any libs needed in the apk in a lib folder and then sign the apk using your own keystore. I mostly posted it in the hope that it would help someone make an SDK port though but use them however you like.

blunden said:
As I said, they are not signed correctly as that would require me to remove the current signature files and resign them. I am currently sick so I didn't feel like doing it since anyone else could fix that if they wanted to.
To fix it, remove the META-INF folder from the apk and then sign it using jarsigner (part of Java JDK) or signapk. If you want to install them as normal apps you would need to make sure you pack any libs needed in the apk in a lib folder and then sign the apk using your own keystore. I mostly posted it in the hope that it would help someone make an SDK port though but use them however you like.
Click to expand...
Click to collapse
Deleted META-INF, signed the launcher via Kitchen & tried to install via ADB, getting error [INSTALLED FAILED - OLDER SDK]..
Any clue?

fshami said:
Deleted META-INF, signed the launcher via Kitchen & tried to install via ADB, getting error [INSTALLED FAILED - OLDER SDK]..
Any clue?
Click to expand...
Click to collapse
Yes, you need to change the minimum SDK version in AndroidManifest.xml to Gingerbread.
Code:
<uses-sdk
android:minSdkVersion="14"
android:targetSdkVersion="14"
>
</uses-sdk>
You need to change android:minSdkVersion="14" to 9 (for 2.3-2.3.2) or 10 (for 2.3.3-2.3.7). I have a feeling it probably won't work completely as it probably uses some ICS APIs.
The problem is that apktool doesn't work since it uses the non-working baksmali. Because of that, I don't know how to convert the file back to it's binary form.

Anyone has yet installed the ICS live wallpapers?

ilbeppez said:
Anyone has yet installed the ICS live wallpapers?
Click to expand...
Click to collapse
The SDK doesn't include any live wallpapers other than a rotating wireframe cube.

So is anyone going to port the apps to gingerbread? I've seen them posted everywhere but so far no ports

Link_of_Hyrule said:
So is anyone going to port the apps to gingerbread? I've seen them posted everywhere but so far no ports
Click to expand...
Click to collapse
I have already explained just a few posts earlier why it's currently not as easy to do as it normally is.

So no one can do it because the apk tool can't recompile it properly?

[Xperia S] [FIX] CM SMS 160 character limit patcher (v0.5 released 08-OCT-2012)

JunThis little tool should work on all CM9/10 builds so far and may work on other ROM releases based on FXP's CM.
IF YOU HAVE ALREADY INSTALLED A PATCH FROM THE FIRST RELEASE MAKE SURE YOU REVERT BACK TO STOCK FRAMEWORK.JAR BEFORE USING v0.2
I have consolidated the two files into one batch file for both CM9 and CM10. You can choose between them when you start the batch file.
There are now two modes of operation. Simply running smsfix.bat will work as per the previous versions. The framework.jar will be pulled from your phone, modified
and then pushed back. You need JAVA runtime and ADB installed for this to work.
The second mode you can extract the framework.jar from your phone manually and drag the file onto the smsfix.bat (or run smsfix.bat and add the filename as a parameter) and it will make the necessary patches and provide you with a flashable zip that will be copied to your desktop.
This should keep us going until a real sms fix is released.
Let me know how you get on with this.
Release history
08 - Oct - 2012 - v0.5 - Support for the new RIL in builds FXP141 onwards (both CM9/10 - Select option 3)
01 - Oct - 2012 - v0.4 - Added more heap space for java calls as the script fails with latest builds (fxp 140 onwards). Added more error checking to ensure it fails cleanly.
18 - Sep - 2012 - v0.3 - Consolidate to a single batch file for both CM9 and CM10 and added a flashable zip mode. The patch itself has not changed in this release so no need to update from previous versions.
14 - Sep - 2012 - v0.2 - Added version for CM10 too.
13 - Sep - 2012 - v0.2 - Should now work with messages of >2 parts - based on a Smali rough implementation of this fix (http://review.cyanogenmod.com/#/c/2...droid/internal/telephony/SonyQualcommRIL.java)
11 - Sep - 2012 - v0.1 - very hacky fix that didnt work with >2 messages and was not thread safe.
Thanks to whooper90 for the adb remount and thanks to the Samsung CM dev team who did the fix that v0.2 is based upon.

Thank you for your contribution to the community.
Is there any way you can post the actual files/code here that we can patch manually? I'm on a Mac, for example, and would still like to use this application.

Static-Noise said:
Thank you for your contribution to the community.
Is there any way you can post the actual files/code here that we can patch manually? I'm on a Mac, for example, and would still like to use this application.
Click to expand...
Click to collapse
the files that it patches are all included. if you can drive apktool you should be able to decompile and copy the patched files over and recompile without too much difficulty
just use the mac apktool files from here
http://code.google.com/p/android-apktool/
and manually run the steps from the batch file

That's great. That suits perfectly, so thank you very much. I'll try it out and report back in the morning.

"Installation aborded" ...

jerwaz said:
"Installation aborded" ...
Click to expand...
Click to collapse
It's not a flashable zip, extract the folder to anywhere on your PC then run "smsfix.bat" from the folder you just extracted. This should work providing you have the correct drivers and have read the instrcutions in the OP

Nice, good job!
Sent from my Xperia S using xda premium

fareeed said:
It's not a flashable zip, extract the folder to anywhere on your PC then run "smsfix.bat" from the folder you just extracted. This should work providing you have the correct drivers and have read the instrcutions in the OP
Click to expand...
Click to collapse
Ohhhh right sry ^^'
Working perfectly =)
Edit: working for a 320 character long message but not for more than 320 character ....

which lines on the smali are actually getting changed ??

Hi!
Thanks for the fix!
I've had an issue with the bat script when it was pushing the edited file. Seems like you've forgot an adb remount.
Here's the (I believe) fixed bat script.
EDIT: I can only send messages of 1 or 2 messages.. 3 messages fail.. Thanks anyway! huge improvement
Code:
@echo off
echo Pulling framework.jar from phone...
md working
adb pull /system/framework/framework.jar working
echo Decompiling and patching files
java -jar apktool.jar d working\framework.jar working\framework.jar.out
copy /y ril.smali working\framework.jar.out\smali\com\android\internal\telephony\
copy /y GsmSMSDispatcher.smali working\framework.jar.out\smali\com\android\internal\telephony\gsm\
copy /y CdmaSMSDispatcher.smali working\framework.jar.out\smali\com\android\internal\telephony\cdma\
java -jar apktool.jar b working\framework.jar.out working\fw.jar
7za -oworking x working\fw.jar classes.dex
cd working
..\7za u framework.jar classes.dex
echo Ready to push and reboot
..\adb remount
Pause
..\adb push framework.jar /system/framework/framework.jar
..\adb shell chmod 644 /system/framework/framework.jar
..\adb reboot
echo Cleaning up
cd..
rd /q /s working
echo Operation complete
Pause

championswimmer said:
which lines on the smali are actually getting changed ??
Click to expand...
Click to collapse
i was basically adding a public static field to the RIL class that is picked up when sending a message and setting it to SEND_SMS or SEND_SMS_EXPECT_MORE from the SMSDispatcher.
Very dirty hack. The new version is much nicer and is a rough implementation of this fix:
http://review.cyanogenmod.com/#/c/2...droid/internal/telephony/SonyQualcommRIL.java
i'm missing some of the niceties of this fix above but im new to dalvik/smali and i couldnt quite get the exception handling to work.

thnx it worked.. :good::good: btw i can send sms more than 320 characters any way thnx

lahirukkk said:
thnx it worked.. :good::good: btw i can send sms more than 320 characters any way thnx
Click to expand...
Click to collapse
Didn't worked for me
I receive an error about classes.dex
FXP137 for Xperia S

dying_sun said:
Didn't worked for me
I receive an error about classes.dex
FXP137 for Xperia S
Click to expand...
Click to collapse
it would help if you could provide information about exactly what error you got

I also got that first time when i'm trying to install. What i did is install java run time environment 1.7 on my pc. Then it worked with out giving error msg.
Sent from my Xperia S using xda app-developers app

lahirukkk said:
I also got that first time when i'm trying to install. What i did is install java run time environment 1.7 on my pc. Then it worked with out giving error msg.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot, I installed Java about two weeks ago (for Jdownloader) so I think I didn't needed this, but downloading JRE 1.7.0.7 everything goes ok. Thanks again
Flavio

Glad to hear that you slove the problem.
Sent from my Xperia S using xda app-developers app

A question
It works for me! Thank you very much! :laugh:
But I am wondering that, if I upgrade from FXP136 to FXP137 by flashing zip file, should I patch it again? Or should I keep my patched "framework.jar" unreplaced?

Just apply again whenever you flash a new release
Sent from my Xperia S using xda app-developers app

This will work on AOKP too?
Sent from my LT26i with Tapatalk 2

Theming / Editing Settings.apk

Hi,
i have themed/edited Settings.apk, then i recompiled/signed/zipaligned without warnings with ApkTool, but once overwritten original Settings.apk and chmoded to 0644 i can't restart the phone, it is stuck on "Android starting" or "updating" (i can't remember the correct text showing). Now i resored the original Settings.apk and all is working fine.
Am i missing something? I have used framework-res and framework-res-htc.
I'm on rooted stock rom latest firmware, no xposed.
Thanks and sorry for my bad english.

which version of apktool?
you need to manually resign the rebuild apk in newer apktool versions
In order to run a rebuilt application. You must resign the application. Android documentation can help with this.
Click to expand...
Click to collapse
and why the double post?

peteter said:
which version of apktool?
you need to manually resign the rebuild apk in newer apktool versions
and why the double post?
Click to expand...
Click to collapse
I'm using "Advanced ApkTool v4.2.0", apktool.jar is a compatible version for marshmallow but i don't remember the version number, previously i themed various xperia themes for marshmallow without issues.
What do you mean with "you need to manually resign the rebuild apk in newer apktool versions"? Like i said i'm using Advanced ApkToo and it has sign command.
Double post is an error, i have requested the deletion.
Thank you

ah ok, thought you were using the standalone apktool from ibotpeaches, there you have to resign the rebuild apk yourself.
just check the link in the quote