Related
I had this in Cyanogen's thread but I figured I'd pull it out of there because 1) his great work doesn't need to be corrupted by my miniscule offerings and 2) other people may want to see this.
If anyone is looking to get the IM app working on other builds, it's doable now.
You'll need to grab Cyanogen's build and yank some stuff out of it, specifically:
Need to do the following:
Grab the following files from the Cyanogen build:
/system/framework/com.android.im.plugin.jar
/system/app/IM.apk
/system/app/ImProvider.apk
/system/app/TmoImPlugin.apk
/system/lib/libwbxml.so
/system/lib/libwbxml_jni.so
/system/lib/libxml2wbxml.so
You'll need to push those files to the same directories on the build that you're using (haykuro, whatever) - copy them all to the same local directory on your pc or something, then adb remount, then adb push them to the appropriate directories (as listed above)
then do an adb shell reboot and you should have it working. FWIW I haven't been able to get yahoo IM working, but really..if you're using yahoo messenger, you are probably one of those people who want video ringtones, and I don't have any desire to help you
I just extracted the following from Dude's Cupcake 1.2 Full and installed them using appmanager. No ADB pushing and everything works great, including Yahoo messenger. I am currently using Dude 1.1a lite.
IM.apk
ImProvider.apk
TmoImPlugin.apk
MetalMessiah78 said:
I just extracted the following from Dude's Cupcake 1.2 Full and installed them using appmanager. No ADB pushing and everything works great, including Yahoo messenger. I am currently using Dude 1.1a lite.
IM.apk
ImProvider.apk
TmoImPlugin.apk
Click to expand...
Click to collapse
That worked perfectly with Haykuro's ION build. Fantastic find mate. Cheers.
Neither approach seems to work on the Rogers rom.
As soon as I boot up:
"The process com.google.process.gapps has stopped unexpectedly. Please try again. Force close"
I get this error 2 or 3 times consecutively before I can use the phone. The IM app doesn't show up at all. Back to a 3rd part app I suppose. Thanks for the info anyways
This method DOES NOT work on any of the hero roms. The IM app force closes on launch.
Add the files plz ?
Any chance you can add the required files to the post ?
danigman said:
Any chance you can add the required files to the post ?
Click to expand...
Click to collapse
Here ya go.
afflaq said:
I had this in Cyanogen's thread but I figured I'd pull it out of there because 1) his great work doesn't need to be corrupted by my miniscule offerings and 2) other people may want to see this.
If anyone is looking to get the IM app working on other builds, it's doable now.
You'll need to grab Cyanogen's build and yank some stuff out of it, specifically:
Need to do the following:
Grab the following files from the Cyanogen build:
/system/framework/com.android.im.plugin.jar
/system/app/IM.apk
/system/app/ImProvider.apk
/system/app/TmoImPlugin.apk
/system/lib/libwbxml.so
/system/lib/libwbxml_jni.so
/system/lib/libxml2wbxml.so
You'll need to push those files to the same directories on the build that you're using (haykuro, whatever) - copy them all to the same local directory on your pc or something, then adb remount, then adb push them to the appropriate directories (as listed above)
then do an adb shell reboot and you should have it working. FWIW I haven't been able to get yahoo IM working, but really..if you're using yahoo messenger, you are probably one of those people who want video ringtones, and I don't have any desire to help you
Click to expand...
Click to collapse
Hi, I used adb and followed your instructions, but I can't get the IM app up and running. I even used this post as a reference:
http://forum.xda-developers.com/showpost.php?p=3851087&postcount=319
I adb rebooted and after running the IM app, I get this:
"The process android.process.acore has stopped unexpectedly. Please try again."
I tried re-running it several times and I get the same error message. Any pointers? Thanks in advance!
-out
I also tried these steps on the Roger's build. I also got the same errors. I wonder what's different with this build that won't allow the IM app to install?
i tried the adb push n that didnt do the trick....i just installed the 3 apk files with the package installer from linda file manager n it did the trick.....
thank you guys
gringo69 said:
i tried the adb push n that didnt do the trick....i just installed the 3 apk files with the package installer from linda file manager n it did the trick.....
thank you guys
Click to expand...
Click to collapse
Im on JF 1.51 ADP and just installed the three .apk's too
It also worked Thanks a lot i've been looking for this for awhile now.
pantlessjim said:
That worked perfectly with Haykuro's ION build. Fantastic find mate. Cheers.
Click to expand...
Click to collapse
You are welcome. Glad it worked for you.
JUST TO CLARIFY. This only works on Google builds, such as Dude, ION, JF, etc, which most already include as default anyway, minus ION. If you are using an HTC build, like some of the Haykuro or Rogers build, it will not work. The HTC framework is different from the Google framework, and unless someone patches them to work, they won't. Don't know enough about each framework that I can patch them.
If you are able to get those files from an HTC build, in theory, they should work with other HTC builds, but I don't think one exists with those files at the moment. Sorry.
gringo69 said:
i tried the adb push n that didnt do the trick....i just installed the 3 apk files with the package installer from linda file manager n it did the trick.....
thank you guys
Click to expand...
Click to collapse
SWEET!!! Finally i have my IM's back!
I am on the "Cyanogenized Rogers Rom" and I tried this just for the hell of it. It failed.. obviously... so I pulled the logs using log collector. Maybe if someone knows what they are doing they can look at the logs that I got. I just pulled what I thought was important...
Code:
D/PackageManager( 114): Scanning app dir /system/framework
D/PackageManager( 114): Scanning app dir /system/app
D/dalvikvm( 114): GC freed 6807 objects / 381744 bytes in 140ms
I/PackageManager( 114): /system/app/ImProvider.apk changed; collecting certs
D/dalvikvm( 114): GC freed 3530 objects / 193256 bytes in 118ms
E/PackageManager( 114): Package com.android.providers.im signatures do not match the previously installed version; ignoring!
I/PackageManager( 114): /system/app/TmoImPlugin.apk changed; collecting certs
D/dalvikvm( 114): GC freed 5357 objects / 367768 bytes in 120ms
D/installd( 45): DexInv: --- BEGIN '/system/app/TmoImPlugin.apk' ---
D/dalvikvm( 130): DexOpt: load 11ms, verify 3ms, opt 0ms
D/installd( 45): DexInv: --- END '/system/app/TmoImPlugin.apk' (success) ---
I/PackageManager( 114): /system/app/im.apk changed; collecting certs
D/dalvikvm( 114): GC freed 6082 objects / 364680 bytes in 144ms
I/PackageManager( 114): New shared user android.uid.im: id=10052
D/installd( 45): DexInv: --- BEGIN '/system/app/im.apk' ---
D/dalvikvm( 131): DexOpt: load 152ms, verify 914ms, opt 34ms
D/installd( 45): DexInv: --- END '/system/app/im.apk' (success) ---
W/PackageParser( 114): Intent filter for activity ActivityIntentInfo{43895b38 com.android.contacts.ContactsPreferenceActivity} defines no actions
W/PackageManager( 114): Skipping provider name android.server.checkin (in package com.android.providers.htcCheckin): name already used by com.google.android.server.checkin
D/PackageManager( 114): Scanning app dir /data/app
W/PackageParser( 114): Skipping non-package file: /data/app/com.rerware.android.MyBackupPro.zip
W/PackageParser( 114): Skipping non-package file: /data/app/com.maize.digitalClock.zip
D/dalvikvm( 114): GC freed 9219 objects / 534392 bytes in 141ms
W/PackageParser( 114): Skipping non-package file: /data/app/com.schwimmer.android.hidenseek.zip
D/PackageManager( 114): Scanning app dir /data/app-private
I/PackageManager( 114): Time to scan packages: 16.536 seconds
W/PackageManager( 114): Removing dangling permission: com.android.providers.im.permission.WRITE_ONLY from package com.android.providers.im
W/PackageManager( 114): Removing dangling permission: com.android.providers.im.permission.READ_ONLY from package com.android.providers.im
W/PackageManager( 114): Unknown permission com.android.email.permission.READ_ATTACHMENT in package com.google.android.apps.uploader
W/PackageManager( 114): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.android.im
W/PackageManager( 114): Unknown permission com.android.providers.im.permission.WRITE_ONLY in package com.android.im
For fun, try pushing these through adb from the 1st post.
/system/framework/com.android.im.plugin.jar
/system/lib/libwbxml.so
/system/lib/libwbxml_jni.so
/system/lib/libxml2wbxml.so
I'm thinking that might be required to get it working on HTC roms, but if it overwrites something that the htc rom needs, it might cause problems with something else.
The Google roms must already have the information contained in these files and thus not require that they be pushed. I would do a Nandroid back up first, push the files, and test everything out. If you start getting weird problems, Nandroid back to your backup.
st00p1d question on AT&T with ADP1
This just isn't gonna work for me, is it.
@MorphWVUtuba Here's what I've gathered so far. If you're using a Google build then you should be able to get T-Mo's IM installed. However, you're SOL if you're on an HTC build.
Thanks for the reply. I have JF build, which IIRC is a Google build. I get an error saying "unable to read your phone number" off of the sim card. Do you or anyone else know what that means?
Thanks a lot guys, i've been looking for this for a while now n& everything is working perfectly.
For all of you running HTC roms that have been unable to make IM work, Dude just released a Rogers rom with IM included. Try pulling the files from his rom and see if it works. It might give those of you who haven't been successful a better chance of making this work. Even if you can't just copy over the apk's, he might have patched up he framework files.
I would try the apk's first. If that doesn't work, adb the framework files and apk's like the first post suggests.
Hi,
I created a custom Phone.apk, I changed a bit the behavior, the Dialpad etc.etc so this works great, I compiled it against the Platform and it works on the Emulator.
But now I'm trying to put it on the Wildfire (I did an adb pull from the Emulator) and I've now the Phone.apk, I tried to put it with adb rm and then adb push.
So the Problem is not the installation, the Problem is that I can't get it to work.... on the Wildfire...what's wrong?
Any Ideas would be highly appreciated
Thanks
Does really no-one has clue? In which Direction should I go? What can I try?
Please help-me also if I've not 1000 Posts :-(
I've no logged with adb what happens on the Device, the following Error I get, but this make's no sense for me :-(
FATAL EXCEPTION: main
E/AndroidRuntime( 413): android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.CALL_PRIVILEGED dat=tel:123 flg=0x10000000 }
Any Ideas?
I tried now to flash the Phone.apk with several strategies...
-> update.zip
-> adb & cat
-> custom Rom (cooked)
But i really don't now why it fails...omg...
Upload the file and I will try and install it.
Thanks already, I will do it, but maybe I've found the Error...
I now recompiled the Phone.apk...
And tried it with adb install and terminal was saying that I've an OLD SDK...
Failure [INSTALL_FAILED_OLDER_SDK]
So, on the Device there's running Froyo...so it can't be OLD?
But when I'm compiling it, I'm doing a source envsetup.sh and then a lunch 1.
Could it be that I've to compile it some how different???
Thanks for EVERY reply!
Update:
I'm building with this config:
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=AOSP
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=user
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=darwin
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
So I really don't now why I'm getting the OLDER_SDK message...I was looking in the make files and there's the SDK 8....
So I've uploaded it, maybe someone could help me to go a step further
link to Phone.apk
Problem solved...I updated the use-sdk Version in the AndroidManifest.xml of the Phone app.
Can be closed
link dead. do you have any screenshot of your new phone.apk, what do you change? when you say behavior
It's changed relatively static for my Phone Number and my Voicemail Number...so it isn't handy for others...but I will keep up my Work and try several things and If I've something to give to the XDA-Users I will do it.
Thanks for you interest
Sorry, I originally posted this into the wrong category.
Hi all,
I have searched Google and this forum but cannot find a solution to a problem that I thought would be a little more common.
I have created an application from a guide in a book I am reading but when I try to run the app in the AVD I receive the following error:
Code:
The application ****** stopped unexpectedly. Please try again. FORCE CLOSE
This is not much help so I looked into logcat and found the following error:
Code:
E/dalvikvm( 493): Unable to open stack trace file '/data/anr/traces.txt': Permission denied
I don't know if this is the cause of my problem or maybe a second problem. I am running the AVD on Linux and there is no /data directory in the root of the filesystem. I (relucantly) created the directories in questions and set the permissions to 777. However this has not resolved the problem.
Is anyone able to help me understand what these errors mean?
Thanks.
I believe many people wanted to learn how to do this. Well I was one of them until a while ago..
First of all I want to Thank Lens_flare for his awesome MIUIv4 porting guide! I actually learned porting after following his guide..
Anyways,
WHAT YOU'LL NEED:
apktool
ddms for logcat(or adb, whichever you like. I prefer ddms as its more detailed and easy to understand)
File comparison and merging tool.
Araxis Merge(I've been using Araxis Merge during the time I was on Windows. Its a paid tool but its available for free for 30 days)
WinMerge(Windows)
Meld(if you are on linux. Its available on Ubuntu Software Center)
Alternatively, you can google for other file comparison tools; https://www.google.com/search?clien...e+comparison+and+merge+tool&ie=utf-8&oe=utf-8
LET'S BEGIN!
Now ,I don't want to write the instructions on how to make a basic port as rishabh has already written one over here(Don't forget to thank him!). My actual purpose was to make a support post in his thread as a further info on porting but the info which needed to be written was way too big so I decided to post a new thread.. Anyways, follow his guide to get over with the simple porting process .. I highly recommend you to use dsixda's Android Kitchen. It will help a lot in porting. (from deodexing to easily unpacking/re-building ROM zips, signing, zipaligning apks, etc. etc.)
dsixda's Kitchen
Guide for installing and using the Kitchen
The actual porting begins now!..
I assume you already got built your zip following the above given guide, now we can go on..
Firstly flash the zip you built. It will obviously not boot.. so called 'bootloop'... What we are going to do is to observe the logcat and find errors causing bootloop, and fix them..
COMPARING AND PATCHING/DIFFING
We are going to fix errors by finding the error causing .smali files by observing the log (There might of course be other factors for a bootloop, but that doesn't interest us yet. If in the porting process we get different kind of errors we are goin to look into them then..)
Please look below at "UNDESTANDING LOGS AND DEBUGGING" section for better understanding of logcat and what we are gonna do exactly!
Patching?? What's that?
Lens_flare said:
Patching (usually named diffing, diff that means "find differences and eliminate them") in our context is a process of comparing two files and adding contents of one of them to another and not replacing anything.
Click to expand...
Click to collapse
OK! Let's imagine logcat gave us this info;
Code:
E/dalvikvm( 8925): ERROR: couldn't find native method
E/dalvikvm( 8925): Requested: Landroid/content/res/AssetManager;.splitThemePackage:(Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;)I
E/JNIHelp ( 8925): RegisterNatives failed for 'android/content/res/AssetManager', aborting
I'm pretty sure you can all see
Code:
android/content/res/AssetManager
and
Code:
ERROR: couldn't find native method
these show us that there is a missing native method in AssetManager.smali file under android/content/res of framework.jar
Now, I assume you already got apktool set up, we should decompile both base framework.jar(the one in the base rom, obviously) and port framework.jar(the one you are porting). Rename the base framework.jar file to "framework_base.jar" and leave the port stay "framework.jar" and put them in apktool directory..
Run a cmd, cd to the apktool directory and decompile the jars by typing
Code:
apktool d framework.jar
Code:
apktool d framework_base.jar
Once the de-compilation is finished you will get two folders in the apktool directory. One "framework.jar.out" and the other "framework_base.jar.out"
Navigate to "smali/android/content/res" in both the folders and find AssetManager.smali.
Get your comparison tool opened up and import the base AssetManager.smali to one side and the port to the other.
Now, you can start adding missing stuff.. NOTE: While patching AssetManager.smali, DO NOT REPLACE ANYTHING! JUST ADD MISSING LINES!!
Ok after you make sure you have added missing lines, save files and close the program.
Switch back to apktool and recompile the port framework.jar by typing the following command:
Code:
apktool b framework.jar.out
OK! you are good to go. Now either put this in a small flashable.zip for sake of time. or put it in your WORKING_FOLDER and rebuild the whole zip. Flash it and you shouldn't see the AssetManager.smali error any more.
But wait! You didn't think you would get you Port booting? did you? Well, if you did you were to be happy too fast! You are going to face this kind of errors again and again.. Then sometime you'll see you rom booting and will be the happiest guy
Anyways, when you see other similar errors just apply the same technique to them. The technique of "patching"!
Porting ARMv7 to v6 might throw up some other errors except smali files. If something happens and you can't fix feel free to post a log here I'll do my best to solve it. If I cant, then I hope some others, more experienced people can contribute..
UNDERSTANDING LOGS AND DEBUGGING
This section is a slightly modified version of the "understanding logs and debugging" section of Lens_flare's guide on MIUI porting(make sure you thank him too!) to better fit our purpose.. (I've got his permission)
I've put his word under this show/hide button for a cleaner thread
Most likely people are going to forum and just posting logcat (that might contain common error). My goal is show you - logcat is not you should fear to see!
First of all, let's assume something:
adb - powerful tool, in our case the must have thing to make a log. Article on android devs most likely describes all the moments about adb power: http://developer.android.com/tools/help/adb.html
logcat/log - one of the android advantages that allows you to debug what's going on with your system. by "make log" I will assume issuing
Code:
adb logcat >log.txt
command, last argument - log.txt is a text file with log system provided to you (you could use any name).
debug/debugging - process of analyzing code which helps to eliminate bugs (that's why de-bug)
You could also use ddms instead, it has a nice GUI. You can find the logcat at the right bottom of the ddms window..
Some people experiencing problems with log, most common are:
-no/corrupted/wrong usb drivers on PC
-Windows :crying: most likely is about new usb subsystems etc, so advice is the only one - try on ubuntu (not working without udev rules)
-somewhat corrupted/inconsistent usb port
Note: if your log only consists of:
Code:
link system/bin/sh failed: no such file or directory
or something like that, you should contact a CM dev, else, you are most likely know what happened ;]
Alright when we got a log, it consist of many many lines that are looping if your system not boots. That's why it is sometimes called bootloop. System may repeat a error eternal time it lives, so log might be huge.
To parse what's going on there are some advice:
keywords:
search in log you got some keywords, that might be useful on debugging boot issue;
most common keywords are:
"E/" - error
"E/dalvikvm" - possibly crucial system error
"No such file or directory" - says it all
"couldn't" - android likes that, mostly shows faulty things.
"fail"/"failed" - mostly crucial error
"W/"/"warning" - says it all, but not always warm could be a boot failure cause
"exception"(especially NullPointerException) - points you that something went wrong in framework or application work
I/ tags could be also useful at debugging, but most helpful are errors and warnings.
Most common constructs:
"couldn't find native method", the most common reason of a bootloop.
For instance:
Code:
E/dalvikvm( 100): ERROR: couldn't find native method
E/dalvikvm( 100): Requested: Landroid/view/GLES20Canvas;.nStartTileRendering:(IIIII)V
E/JNIHelp ( 100): RegisterNatives failed for 'android/view/GLES20Canvas', aborting
Let's parse that construct to extract parts we will fix.
First of all. smali path might be extracted from that line:
Code:
E/JNIHelp ( 100): RegisterNatives failed for 'android/view/GLES20Canvas', aborting
->
Code:
android/view/GLES20Canvas
that's it, smali we are looking for is GLES20Canvas.smali. But.. android/view.. where it is? Answer comes from android source, it took some time to analyze frameworks.. Just let's assume: all that starting with "android" in path belongs to framework,jar.
What if path doesn't contain "android" at the beginning?
Again the answer is in source. Paths like"org/" are belong to framework.jar.
"com/android/server" - services.jar (there is the same folder at framework.jar but most likely you don't need to touch it).
another place we could be mixed up:
"com/android/internal" - framework.jar
"com/android/internal/policy/impl/" - android.policy.jar
for framework.jar path ends up on internal, which represents telephony folder. policy/impl is the only android.policy.jar folder.
Other frameworks are actually not used in port as they contain core android functionality which is common.
Note about smali you found:
it might be not smali you are looking for, most likely when code points you to android functionality and widgets (control elements) like combobox or listview, it's a sign to think twice what have you done on your system to port it
it might be tree of smali, to ease of use, always replace smali with its tree, and only if error becomes worse, think about single smali or about diff )
from
Code:
E/dalvikvm( 100): Requested: Landroid/view/GLES20Canvas;.nStartTileRendering:(IIIII)V
we could extract a method which is missing - nStartTileRendering. In some cases only that method should be added and nothing more.
" Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)"
Hope all of you heared about C language. That error is a form of C "exceptional case"(in other words - exception).
You will see if it happen:
Code:
F/libc ( 2698): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 130): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 130): Build fingerprint: 'tmous/htc_doubleshot/doubleshot:4.0.3/IML
74K/275847.101:user/release-keys'
I/DEBUG ( 130): pid: 2698, tid: 2698 >>> zygote <<<
I/DEBUG ( 130): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaa
d
I/DEBUG ( 130): r0 deadbaad r1 00000001 r2 a0000000 r3 00000000
I/DEBUG ( 130): r4 00000000 r5 00000027 r6 4086fbfd r7 00000036
I/DEBUG ( 130): r8 40253f04 r9 40233a7e 10 0000904c fp 00009062
I/DEBUG ( 130): ip 4028b240 sp befcfa60 lr 401043c1 pc 40100adc cpsr 600
00030
I/DEBUG ( 130): d0 2f64696f72646e61 d1 2f746e65746e6f63
I/DEBUG ( 130): d2 657373412f736572 d3 726567616e614d74
I/DEBUG ( 130): d4 0000d4cc0000d4b1 d5 0000d4e80000d4cd
yaa.. ENORMOUS code block, build fingerprint, fatal signal and stack trace.. welcome to hell
One little thing: error is right above that block, don't even try to parse its contents, ignore it.
"Unable to extract+optimize DEX from '/system/framework/framework.jar'" and other WTF cases
examples:
Code:
D/dalvikvm( 103): DexOpt: --- BEGIN 'framework.jar' (bootstrap=1) ---
E/dalvikvm( 172): Duplicate class definition: 'Landroid/media/MediaRecorder;'
E/dalvikvm( 172): Trouble with item 2900 @ offset 0x17a86c
E/dalvikvm( 172): Cross-item verify of section type 0006 failed
E/dalvikvm( 172): ERROR: Byte swap + verify failed
E/dalvikvm( 172): Optimization failed
W/dalvikvm( 103): DexOpt: --- END 'framework.jar' --- status=0xff00, process failed
E/dalvikvm( 103): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 103): Unable to process classpath element '/system/framework/framework.jar'
E/JNIHelp ( 103): Native registration unable to find class 'android/debug/JNITest', aborting
Code:
05-30 14:15:15.970: E/NetworkLocationRealOs(2304): no android ID; can't access encrypted cache
05-30 14:15:15.970: E/NetworkLocationRealOs(2304): java.io.IOException: no android ID; can't access encrypted cache
Code:
1012: 07-03 03:28:21.350: E/System(1538): ************ Failure starting core service
07-03 03:28:21.350: E/System(1538): java.lang.NullPointerException
07-03 03:28:21.350: E/System(1538): at com.android.server.pm.PackageManagerService.grantPermissionsLPw(PackageManagerService.java:4299)
07-03 03:28:21.350: E/System(1538): at com.android.server.pm.PackageManagerService.updatePermissionsLPw(PackageManagerService.java:4247)
07-03 03:28:21.350: E/System(1538): at com.android.server.pm.PackageManagerService.<init>(PackageManagerService.java:1170)
07-03 03:28:21.350: E/System(1538): at com.android.server.pm.PackageManagerService.main(PackageManagerService.java:858)
07-03 03:28:21.350: E/System(1538): at com.android.server.ServerThread.run(SystemServer.java:167)
07-03 03:28:21.350: I/SystemServer(1538): Input Method Service
07-03 03:28:21.360: W/SystemServer(1538): ***********************************************
1021: 07-03 03:28:21.370: A/SystemServer(1538): BOOT FAILURE starting Input Manager Service
1022: 07-03 03:28:21.370: A/SystemServer(1538): java.lang.NullPointerException
1023: 07-03 03:28:21.370: A/SystemServer(1538): at android.app.PendingIntent.getBroadcast(PendingIntent.java:293)
1024: 07-03 03:28:21.370: A/SystemServer(1538): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java:548)
1025: 07-03 03:28:21.370: A/SystemServer(1538): at com.android.server.ServerThread.run(SystemServer.java:271)
1026: 07-03 03:28:21.400: E/AndroidRuntime(1538): Error reporting WTF
1027: 07-03 03:28:21.400: E/AndroidRuntime(1538): java.lang.NullPointerException
1028: 07-03 03:28:21.400: E/AndroidRuntime(1538): at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:345)
1029: 07-03 03:28:21.400: E/AndroidRuntime(1538): at android.util.Log$1.onTerribleFailure(Log.java:103)
1030: 07-03 03:28:21.400: E/AndroidRuntime(1538): at android.util.Log.wtf(Log.java:278)
1031: 07-03 03:28:21.400: E/AndroidRuntime(1538): at com.android.server.ServerThread.reportWtf(SystemServer.java:77)
1032: 07-03 03:28:21.400: E/AndroidRuntime(1538): at com.android.server.ServerThread.run(SystemServer.java:274)
mostly likely is about way assembling framework files. Also some of them might be just corrupted by accident. Sometimes these errors caused by wrong smali replacement or wrong diff methodology. Or it might be just banal reason - no place in system or cache partitions.
English []
Most log parts are in mere, not technician English,log might be read as little book with bright characters. Find what you are looking for and fix it..
Source code is your best friend in porting
I'd recommend to have an android source code [from internet or on your local PC] to port something that outstands of rules I listed. For example CM frameworks source could be found here: https://github.com/CyanogenMod/android_frameworks_base .
Any log line represents a line of code in source, that one could search and debug from there. Each smali represents a java source code or its part(- subclass which is signed by $), each java is in frameworks folder on source (mostly frameworks/base). Log line is a message, which formed with C rules about these rules, so you have to avoid ciphers or guess how could code represent that message. You may search guessed line in source to locate java file, or locate it manually according to smali location and my advice and search in it.
I WISH YOU A SUCCESSFUL AND HAPPY PORTING PROCESS!! :good:
wow,i've been looking for this for longtime..
gonna try it now..
Sent from my GT-S5660 using Tapatalk 2
AiphNday said:
wow,i've been looking for this for longtime..
gonna try it now..
Sent from my GT-S5660 using Tapatalk 2
Click to expand...
Click to collapse
Good Luck!
XiproX said:
Good Luck!
Click to expand...
Click to collapse
thanks..
you dont mind if i send you a PM to ask for help dont you??
Sent from my GT-S5660 using Tapatalk 2
AiphNday said:
thanks..
you dont mind if i send you a PM to ask for help dont you??
Sent from my GT-S5660 using Tapatalk 2
Click to expand...
Click to collapse
Well, its better to ask here. Some other people having the same issue might benefit from your question and its answer...
XiproX said:
Well, its better to ask here. Some other people having the same issue might benefit from your question and its answer...
Click to expand...
Click to collapse
sure,i'll do that..
Sent from my GT-S5660 using Tapatalk 2
Do not use dsixda's Kitchen to port. Use it for anything else except porting.
It's best to do your ports Manually, or make a tool yourself to do it automatically for you.
That way, you'll know what your doing and how to fix the upcoming errors.
Try not to use apktool to decompile JARs. Because inside JARs are classes.dex
You want to rename the classes.dex to anything you want, then decompile it using smali/baksmali:
Code:
java -jar baksmali-1.4.0.jar -a 10 classes.dex -o classes_output
The [highlight]-a[/highlight] switch determines the api level. See more here
Try not to refer the technique as "patching", instead, call it "diffing". It's just more common
P.S Nice job on the Guide. Could be a little more detailed..
Peteragent5 said:
Do not use dsixda's Kitchen to port. Use it for anything else except porting.
It's best to do your ports Manually, or make a tool yourself to do it automatically for you.
That way, you'll know what your doing and how to fix the upcoming errors.
Try not to use apktool to decompile JARs. Because inside JARs are classes.dex
You want to rename the classes.dex to anything you want, then decompile it using smali/baksmali:
Code:
java -jar baksmali-1.4.0.jar -a 10 classes.dex -o classes_output
The [highlight]-a[/highlight] switch determines the api level. See more here
Try not to refer the technique as "patching", instead, call it "diffing". It's just more common
P.S Nice job on the Guide. Could be a little more detailed..
Click to expand...
Click to collapse
wait,i dont get it..
classes.dex was inside the framework.jar right??
so i have to decompile the jar first to get the classes.dex,or just simply take the classes.dex inside the jar using 7zip then decompile the classes.dex with smali/baksmali??
Sent from my GT-S5660 using Tapatalk 2
AiphNday said:
wait,i dont get it..
classes.dex was inside the framework.jar right??
so i have to decompile the jar first to get the classes.dex,or just simply take the classes.dex inside the jar using 7zip then decompile the classes.dex with smali/baksmali??
Sent from my GT-S5660 using Tapatalk 2
Click to expand...
Click to collapse
classes.dex is what make the JAR file.
Do not decompile the JAR
Just simply extract the classes.dex inside the JAR with any Archiver, then decompile it using baksmali
After recompiling, you should sign the JAR file.
Peteragent5 said:
Do not use dsixda's Kitchen to port. Use it for anything else except porting.
It's best to do your ports Manually, or make a tool yourself to do it automatically for you.
That way, you'll know what your doing and how to fix the upcoming errors.
Try not to use apktool to decompile JARs. Because inside JARs are classes.dex
You want to rename the classes.dex to anything you want, then decompile it using smali/baksmali:
Code:
java -jar baksmali-1.4.0.jar -a 10 classes.dex -o classes_output
The [highlight]-a[/highlight] switch determines the api level. See more here
Try not to refer the technique as "patching", instead, call it "diffing". It's just more common
P.S Nice job on the Guide. Could be a little more detailed..
Click to expand...
Click to collapse
Well, thanks! I don't have a huge experience at porting. but you know many people want to know how to port ARMv7 -> v6.. and there wasnt any tutorial for it.. I decided to write this as a beginning. Im open to any kind improvements.
BTW, has anyone found a file comparison tool to exclude specific values like: .line foo
Please let me know! It'll help a lot in my porting, as well as with everyone else's
Peteragent5 said:
classes.dex is what make the JAR file.
Do not decompile the JAR
Just simply extract the classes.dex inside the JAR with any Archiver, then decompile it using baksmali
After recompiling, you should sign the JAR file.
Click to expand...
Click to collapse
so after i finished,compile with smali and put the classes.dex back inside the jar again right??
Peteragent5 said:
BTW, has anyone found a file comparison tool to exclude specific values like: .line foo
Please le me know! It'll help alot in my porting, as well as with everyone else's
Click to expand...
Click to collapse
did you try Araxis Merge its paid software, there is a 30 day trial version, and there are some alternative ways of getting the full version. You know... I used it for some time and it was great.. But Im not sure if it has that feature.. You can check if you want.
Peteragent5 said:
Do not use dsixda's Kitchen to port. Use it for anything else except porting.
It's best to do your ports Manually, or make a tool yourself to do it automatically for you.
That way, you'll know what your doing and how to fix the upcoming errors.
Click to expand...
Click to collapse
I don't really understand. I mean, the kitchen just does the extracting and rebuilding job. What could that cause?
AiphNday said:
so after i finished,compile with smali and put the classes.dex back inside the jar again right??
Click to expand...
Click to collapse
Yes.
To compile:
Code:
java -jar smali-1.4.0.jar classes_output -o classes.dex
Then make a zip file, place classes.dex into it (the name has to be classes.dex for any JAR).
Rename the zip to a JAR. Then sign it.
XiproX said:
did you try Araxis Merge its paid software, there is a 30 day trial version, and there are some alternative ways of getting the full version. You know... I used it for some time and it was great.. But Im not sure if it has that feature.. You can check if you want.
Click to expand...
Click to collapse
I'll check it out.
XiproX said:
I don't really understand. I mean, the kitchen just does the extracting and rebuilding job. What could that cause?
Click to expand...
Click to collapse
The kitchen does everything automatically, even up to modifying the kernel. That's good and all, but we all have different devices, and the kitchen is too General & Broad when it comes to its porting features. It could brick your device.
Peteragent5 said:
The kitchen does everything automatically, even up to modifying the kernel. That's good and all, but we all have different devices, and the kitchen is too General & Broad when it comes to its porting features. It could brick your device.
Click to expand...
Click to collapse
Well, yes, but Im not telling that we should use its porting tools. I too know that it wouldnt do much of a work even if it worked properly for every device and that the manual way is the best.. Im just talking about 4/5 main functions which are creating WORKING_FOLDER from rom/zip, de-odexing, signing, zipaligning, and finally building(creating zip from WORKING_FOLDER)
How could these features affect the porting process? I dont really think they could. Again Im talking about only these above written features..
XiproX said:
Well, yes, but Im not telling that we should use its porting tools. I too know that it wouldnt do much of a work even if it worked properly for every device and that the manual way is the best.. Im just talking about 4/5 main functions which are creating WORKING_FOLDER from rom/zip, de-odexing, signing, zipaligning, and finally building(creating zip from WORKING_FOLDER)
How could these features affect the porting process? I dont really think they could. Again Im talking about only these above written features..
Click to expand...
Click to collapse
Some of the features you shouldn't use from the kitchen are these:
Making an updater-script/update-binary
Create a working Folder, you can just extract your rom and rename it to WORKING_[highlight]ROM[/highlight]
and it's porting tools
these result to an unsuccessful port.
Peteragent5 said:
Some of the features you shouldn't use from the kitchen are these:
Making an updater-script/update-binary
Create a working Folder, you can just extract your rom and rename it to WORKING_[highlight]ROM[/highlight]
and it's porting tools
these result to an unsuccessful port.
Click to expand...
Click to collapse
"Making an updater-script/update-binary" I agree! I never was using it
"Create a working Folder" Weird. I ported MIUI ics and jellybean both by using this method and it all was fine. Anyways not so important. can live without it.
Peteragent5 said:
Yes.
To compile:
Code:
java -jar smali-1.4.0.jar classes_output -o classes.dex
Then make a zip file, place classes.dex into it (the name has to be classes.dex for any JAR).
Rename the zip to a JAR. Then sign it.
I'll check it out.
The kitchen does everything automatically, even up to modifying the kernel. That's good and all, but we all have different devices, and the kitchen is too General & Broad when it comes to its porting features. It could brick your device.
Click to expand...
Click to collapse
can you help me with this?? http://pastebin.com/7uMdU3EX
i was runout of idea.. :silly:
AiphNday said:
can you help me with this?? http://pastebin.com/7uMdU3EX
i was runout of idea.. :silly:
Click to expand...
Click to collapse
there is a problem with pastebin at the moment(for me). you could try to post the log as an attachment text file?
I have tried to deodex using xUltimate, but deodex fails (I have managed to get the odex files from the phone).
What is to be used for deodexing, and how to setup the environment? (there seems to be a problem with Java libs, as far as I can understand the error - Using Windows 7, latest Java)
okty2k said:
I have tried to deodex using xUltimate, but deodex fails (I have managed to get the odex files from the phone).
What is to be used for deodexing, and how to setup the environment? (there seems to be a problem with Java libs, as far as I can understand the error - Using Windows 7, latest Java)
Click to expand...
Click to collapse
http://bit.ly/S1oMMX
LeJolly said:
http://bit.ly/S1oMMX
Click to expand...
Click to collapse
Nice one, I appreciate the effort.
However, maybe you can show where is explained the solution for this:
Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ValidationException: Class Lcom/android/internal/app/ActionBarImpl; has the interface Landroid/app/ActionBar; as its superclass
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadSuperclass(ClassPath.java:834)
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.<init>(ClassPath.java:683)
at org.jf.dexlib.Code.Analysis.ClassPath.loadClassDef(ClassPath.java:280)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:163)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:104)
at org.jf.baksmali.main.main(main.java:293)
Error while loading class Lcom/android/internal/app/ActionBarImpl; from file .\origi_frame\framework.zip
Error while loading ClassPath class Lcom/android/internal/app/ActionBarImpl;
okty2k said:
Nice one, I appreciate the effort.
However, maybe you can show where is explained the solution for this:
Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ValidationException: Class Lcom/android/internal/app/ActionBarImpl; has the interface Landroid/app/ActionBar; as its superclass
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadSuperclass(ClassPath.java:834)
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.<init>(ClassPath.java:683)
at org.jf.dexlib.Code.Analysis.ClassPath.loadClassDef(ClassPath.java:280)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:163)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:104)
at org.jf.baksmali.main.main(main.java:293)
Error while loading class Lcom/android/internal/app/ActionBarImpl; from file .\origi_frame\framework.zip
Error while loading ClassPath class Lcom/android/internal/app/ActionBarImpl;
Click to expand...
Click to collapse
Sorry, your explanation was so short and your question was how to deodex, so I chose to be a smart ass Maybe you could try another tool from the link that I gave and see if it's the problem of the tool or actually the libraries?
It's OK, no offence taken.
Well, I tried several tools, to be honest, all have some kind of errors (some I don't see, but as the script fails, I assume it's the same problem).
You gave me some ideas and I further dig. It seems that xUltimate does not setup the right way BOOTCLASSPATH. it seems that I have to do a lot of manual work to set up the environment. I will try it one of these days....
However, to go back to the initial question (rephrase it):
Devs that are creating ROM's for I9505, what tools are you using to deodex the stock ROM? Or you just create the whole environment manually and use your own created scripts and tools?