Messaging Application Does not work. #11
Comments
|
I have updated the Mms patch and I believe this error has been fixed. Thanks for the log, and let us know if it works for you. Updated as of auto-patcherv3.0.2 |
|
I do not think that something has changed. LOGROOT= /home/deb8/Downloads/auto-patcher-master checking for updatesUpdater: Auto-Patcher is already up to date verify tools/usr/bin/patch verify ROMrunning ./auto_patcher FXP231.zip openpdroid cmPATH= /home/deb8/Downloads/auto-patcher-master/tmp20130813094555:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games unzip patch toolsunzip patch patches... result of ROM check: RIL= SemcRIL probe rom typeStandard Build Query... openpdroid patch date has been set to: 20130209 ... VER= v3.0.2OS= linux-gnu 32bitVID= 4.1.2PID= openpdroidMID= cm_anzu-userdebugRID= cmANDR= 4.1BDID= 20130805DID= anzuBID= 20130209Current HEAD: 514d153f827500490bd36b645f0f2536e26f1ce4 Add remade Mms.apk patch to Cm10 DELETE FILES=COPY FILES= system/media/PDroid.jpegJAR FILES= system/framework/framework.jar system/framework/core.jar system/framework/services.jarAPK FILES= system/app/Mms.apkIMG FILES=TXT FILES=unzip romcreate updater script... using Clockworkmod installer ... generated updater-scriptui_print(""); create restore.zipdecompile system files... decompile framework.jar ... ... extract preloaded-classes ... ... decompile core.jar ... ... decompile services.jar ... ... installing framework files ... ... decompile Mms.apk ... copy patch openpdroid/4.1/cm/20130209... copying system/media/PDroid.jpeg ... ... overwriting system/media/PDroid.jpeg from openpdroid ... ... overwriting GsmServiceStateTracker.smali ... delete patch openpdroid/4.1/cm/20130209jar patch openpdroid/4.1/cm/20130209... apply framework.patch ... ... apply preloaded.patch ... ... apply core.patch ... ... apply services.patch ... apk patch openpdroid/4.1/cm/20130209... apply Mms.apk.patch ... The text leading up to this was:|diff -Npru stock-mms/smali/com/android/mms/transaction/HttpUtils.smali opd-mms/smali/com/android/mms/transaction/HttpUtils.smali |+++ opd-mms/smali/com/android/mms/transaction/HttpUtils.smali 2013-08-12 20:59:27.273263015 -0500File to patch: img patch openpdroid/4.1/cm/20130209text patch openpdroid/4.1/cm/20130209rebuild jar... rebuild framework.jar ... ... rebuild core.jar ... ... rebuild services.jar ... rebuild apk... rebuild Mms.apk ... create update-cm-anzu-20130805-openpdroid.zipadded manifest finished�[1m�[31mCongratulations�(B�[m, the patching was �[1m�[31msuccessful�(B�[m. Any errors you may have seen were succesfully handled! !!! Only file a bug report if the software is �[1m�[32mnot�(B�[m behaving as expected !!! ---�[1m�[32mupdate-cm-anzu-20130805-openpdroid.zip�(B�[m to restore original system, flash: ---�[1m�[32mrestore-cm-anzu-20130805.zip�(B�[m |
|
Same for the tapioca_ss build. Let me know if I can help with log files or anything else. |
|
This is the log before patching No FATAL exceptions This is the log after patching 2 FATAL exceptions (identical) 1.08-13 12:02:31.260 E/AndroidRuntime( 1352): FATAL EXCEPTION: main 2.08-13 12:04:22.870 E/AndroidRuntime( 2116): FATAL EXCEPTION: main |
|
A fatal exception BEFORE patching? Or do you mean todays change by the word "patch" ? A bit cofusing if Zitat von deb8 [email protected]:
|
|
As I said, log BEFORE patching, NO FATAL EXCEPTIONS log AFTER patching, 2 IDENTICAL FATAL EXCEPTIONS with patching i mean installing the openpdroid patch. |
|
Ups, I'm sorry - my bad. |
|
Okay guys...I will look at this today. The problem is (at this point) I just tested the evita and I am see the same issue, so I will check it |
|
Dont know whether this helps, but heres my patcher log: Zitat von mateor [email protected]:
|
|
And corresponding ApG log: Zitat von mateor [email protected]:
|
|
I responded in the other thread about this issue #11 (comment). We have our repo spread out, so I understand it is hard to find others with the same issues. But this particular problem should now be resolved. |
|
sry, sms app still crashing on tapioca. If you can tell me how to cache+dalvik cache cleaned as usual. Is it necessary to wipe dalvik what do you mean by "larger picture CM10 problems" ? Zitat von mateor [email protected]:
|
|
Could you post your auto-patcher log? As for larger CM10 problems..the addition of the FM radio commits in Cm10 broke our patches. I was initially advising to use builds from before that commit (0201 or so) especially since the development was basically stoppped at around that point. But I was told that the source patches were working. So I rebuilt the Cm10 patches as a test several months ago. You two are the first response I have had about that. The Mms problems from the logs you two were originally showing had a definite cause...the Mms.apk was not getting patched at all. Now if the patches are successfully applying, then we the larger problem returns (or perhaps, remains). |
|
sure, The non-patched app crashes?! How is that possible?! ^^ Zitat von mateor [email protected]:
|
|
Well, I will have to take a look at the earlier logs that were posted to see the problem, but this looks like it may just be the same old Cm10 issue. Android 4.1 shipped with a ton of bugs, one of the most trooublesome from our point of view was the fact that the framework.jar was shipped JUST below the hard-coded method limit proscribed by dx. That is why you see things like framework2.jar in custom roms, there was no room for extra code. The upstream addition of CM10's fm radio was a huge addition and is still, I guess, causing us problems. I didn't know that was what was happening, because in my earlier tests, the FCs were in the phone process, not SMS. And as for your question, well, I am not certain it is possible. But we inject a ton of API into the other jar files, and if they were calling a process in SMS and not receiving the proper response, that is what a FC generally starts as. Also, the Mms app was being decompiled and recompiled, mixed with a failed patching process. So there is a lot of potential failures there, and since I could see the patching process failing in a unique way, it was not unreasonable to expect it might be the cause of a unique reported error. You can use ROMs from 0201 or before, but this looks to need greater investigation, sorry. |
|
also, I don't know what a fxp is, is that your build? We only officially support builds from the CM servers, although many kangs do work, we don't support that officially. But looking at your log, I don't necessarily think that the build is the problem. Send me the manifest to build for your rom, if you know where to find it. I just looked in the Cm lunch menu, but did not see it. I will build a source-patched build, and we will see if the errors continue. I have heard that the source patches work fine now, but in that case experience teaches me that these auto-patched builds can work. If we want to investigate further, building a patched rom from source is probably the next step. |
|
FCs? dx? FXP is unofficial, but afaik its just a port of CM to sony devices. Even the source code is in the official repository. Is there any reason why the cm team itself does not use/support a framework2? Zitat von mateor [email protected]:
|
|
Yeah, sorry. It is a lot of back information, to be sure. CM used the same The problem for us came again when CM added the FM radio. That again filled |
|
I quote from their site, so there is a repo here on github, but i clearly do not know where to look, except this repo "android_packages_apps_Mms" which is the only relevant to the Messaging app. Q: When you say you will built a test ROM, you mean a test patch for our ROM ? |
|
I meant the actual rom [edit: I mean a device tree and even better a full manifest) for your device...CyanogenMod does not support any of the devices your logs were from officially (as far as I could tell). That just means someone else is maintaining the tree, I was just hoping you knew who it was. But yes, I would like to build a OpenPDroid-patched rom for your device and see if it works for you...then we will know if we have an Autopatcher problem or a OpenPDroid problem. The distinction matters, for me to know best how to fix it. Think of the Autopatcher as merely a complicated installation method. I will search for a device tree this weekend. |
|
FreeXperia Team are the maintainers of CyanogenMod for Sony Xperia Devices |
|
No what I was trying to do was find out if the issue was coming from I have not forgotten about the issue...it is being looked into. I decided |
|
As you stated in this Link: mateor/auto-patcher#143 |
|
No I meant regular Pdroid. PDroid2.0 likely has the same issue that You can use OpenPDroid on 4.1 with a rom made from 02/01/13 or before I have looked at the issue, as I said, but I do not have a solution |
|
Why does PDroid 1.0 work?! thx |
|
The issue isn't the fm radio, it is the changes they made to allow the fm radio to work in CM10. I had to do some really crazzy stuff to allow PDroid and OpenPDroid support to CM10 due to a bug from upstream AOSP in the dx tool. Put simply, the dx tool has a hardcap limit on how many java methods can be placed in jarfiles of 65,000-ish. Adding Pdroid or OpenPDroid makes the framework.jar too full. We were able to install the PDroid framework by either working with, or creating, the framework2. When CM added the FM radio to CM10 around 020813, they moved around somethings in the framework2.jar and the framework.jar. Something they did is incompatible with our OpenPDroid patches, I have not discovered which. I am sure someone who was willing to investigate it fully could find the issue. I investigated just enough to determine that it was an overall OpenPDroid issue and not an Auto-patcher issue. I am marking it "won'tfix" because I just don't have the time. Generally speaking, the only people who are stuck on 4.1 are those with stock software, and since we only support custom roms, I moved my support forward to the latest version of Android. I realize that there might be some users like you who may only have custom rom support for 4.1, and I do feel guilty about that. But I am maintaining three arms of this project already, my time is simply limited. And I don't feel you are left unprotected, since original PDroid is still working for your rom. The issue isn't the FM radio, but the moving around of framework pieces they did to allow the FM radio to work. You can use a rom from before 020812, development of 4.1 stopped at about that time. OpenPdroid was written d for 4.2. We were able to backport it to 4.1 for awhile, but it wasn't written for 4.1. When upstream changed 4.1 sufficiently, support was lost. I would accept pull requests if someone fixes it, however I cannot fix it myself. |
Auto-Patcher : ApG 2.6.0.1
ROM: FXP231-cm-10-20130805-UNOFFICIAL-anzu
Patch is created successfully.
After applying patch, messaging app cannot start.
Clearing cache and dalvik-cache and fixing permissions did not solve the problem.
Installing mms.apk from the ROM.zip after applying patch also did not solve the problem.
LOGS
ApG.log
Pulling latest changes of autopatcher from GitHub...
error: could not lock config file /home/ndiama/.gitconfig: No such file or directory
No local changes to save
Already up-to-date.
Running autopatcher with the following arguments:
ROM_PATH: /cygdrive/d/Downloads/ApG/FXP231-cm-10-20130805-UNOFFICIAL-anzu.zip
PATCH_TYPE: openpdroid
ROM_TYPE: cm
The Auto-Patcher v3.0.19
verify tools
verify ROM
unzip patch tools
unzip patch patches
inflated: system/build.prop
... result of ROM check: RIL= SemcRIL
probe rom type
... result of ROM check: version= 4.1.2 rom= cm ...
... Using cm patches ...
... openpdroid patch date has been set to: 20130209 ...
unzip rom
inflated: system/app/Mms.apk
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
create updater script
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
create restore.zip
decompile system files
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
... installing framework files ...
I: Framework installed to: C:\Users\ndiama\apktool\framework\1.apk
... decompile Mms.apk ...
copy patch openpdroid/4.1/cm/20130209
... copying system/media/PDroid.jpeg ...
... overwriting system/media/PDroid.jpeg from openpdroid ...
... overwriting GsmServiceStateTracker.smali ...
jar patch openpdroid/4.1/cm/20130209
... apply framework.patch ...
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
apk patch openpdroid/4.1/cm/20130209
... apply Mms.apk.patch ...
rebuild jar
... rebuild framework.jar ...
... rebuild core.jar ...
... rebuild services.jar ...
rebuild apk
... rebuild Mms.apk ...
create update-cm-anzu-20130805-openpdroid.zip
finished
Congratulations, the patching was successful.
Any errors you may have seen were succesfully handled!
!!! Only file a bug report if the software is not behaving as expected !!!
to install patched files, flash:
---update-cm-anzu-20130805-openpdroid.zip
to restore original system, flash:
---restore-cm-anzu-20130805.zip
AP.log
ROOT= /cygdrive/d/Downloads/ApG/ApGPackages/ap
TOOL= /cygdrive/d/Downloads/ApG/ApGPackages/ap/patch_tools.tgz
ROM= /cygdrive/d/Downloads/ApG/FXP231-cm-10-20130805-UNOFFICIAL-anzu.zip
ROMX= D:\DOWNLO
1\ApG\FXP2313.ZIPverify tools
/cygdrive/d/Downloads/ApG/ApGPackages/cygwin/bin/tar
/cygdrive/d/Downloads/ApG/ApGPackages/Java/bin/jar
/cygdrive/d/Downloads/ApG/ApGPackages/Java/bin/java
/cygdrive/d/Downloads/ApG/ApGPackages/cygwin/bin/cpio
verify ROM
running ./auto_patcher /cygdrive/d/Downloads/ApG/FXP231-cm-10-20130805-UNOFFICIAL-anzu.zip openpdroid cm
PATH= /cygdrive/d/Downloads/ApG/ApGPackages/ap/tmp20130812181825:/cygdrive/d/Downloads/ApG/ApGPackages/Java/bin:/cygdrive/d/Downloads/ApG/ApGPackages/cygwin/bin:/cygdrive/d/Downloads/ApG/ApGPackages/cygwin/usr/sbin
unzip patch tools
unzip patch patches
... result of ROM check: RIL= SemcRIL
probe rom type
Standard Build Query
... openpdroid patch date has been set to: 20130209 ...
VER= v3.0.19
OS= cygwin 32bit
VID= 4.1.2
PID= openpdroid
MID= cm_anzu-userdebug
RID= cm
ANDR= 4.1
BDID= 20130805
DID= anzu
BID= 20130209
Current HEAD: 16dad8d1fedb578f6d87ed00ad52a42fd449c719 Merge pull request #145 from Urinophoria/master
5fab7e56d421b08fa0f3326b79857959714179c2 Added slim patches, and "latest" symlink. incremented auto_patcher ver and date. Think I got it all this time!
DELETE FILES=
COPY FILES= system/media/PDroid.jpeg
JAR FILES= system/framework/framework.jar system/framework/core.jar system/framework/services.jar
APK FILES= system/app/Mms.apk
IMG FILES=
TXT FILES=
unzip rom
create updater script
... using Clockworkmod installer ...
generated updater-script
ui_print("");
ui_print("");
ui_print("~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
ui_print("* ");
ui_print(" * The Auto-Patcher * ");
ui_print(" * * * * ");
ui_print(" * by mateor * ");
ui_print(" *");
ui_print("~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
ui_print("");
ui_print(" Attention");
ui_print(" ************************************");
ui_print("");
ui_print(" There is nothing that can go wrong here");
ui_print(" that reflashing your ROM won't fix.");
ui_print("");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 0, 0755, 0755, "/system/addon.d");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");
set_perm(0, 0, 0755, "/system/etc/init.d");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm(0, 0, 0644, "/system/vendor/etc/audio_effects.conf");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/librank");
set_perm(0, 0, 06755, "/system/xbin/procmem");
set_perm(0, 0, 06755, "/system/xbin/procrank");
set_perm(0, 0, 06755, "/system/xbin/su");
unmount("/system");
ui_print(" .");
ui_print(" .");
ui_print(" done!");
create restore.zip
decompile system files
... decompile framework.jar ...
... extract preloaded-classes ...
inflated: preloaded-classes
... decompile core.jar ...
... decompile services.jar ...
inflated: system/framework/framework-res.apk
... installing framework files ...
... decompile Mms.apk ...
I: Baksmaling...
I: Loading resource table...
I: Loaded.
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: C:\Users\ndiama\apktool\framework\1.apk
I: Loaded.
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values / XMLs...
I: Done.
I: Copying assets and libs...
copy patch openpdroid/4.1/cm/20130209
... copying system/media/PDroid.jpeg ...
... overwriting system/media/PDroid.jpeg from openpdroid ...
patches/openpdroid/4.1/cm/20130209/system/media/PDroid.jpeg' ->./system/media/PDroid.jpeg'... overwriting GsmServiceStateTracker.smali ...
delete patch openpdroid/4.1/cm/20130209
jar patch openpdroid/4.1/cm/20130209
... apply framework.patch ...
... apply preloaded.patch ...
GARBAGE=
GARBAGE=
... apply core.patch ...
GARBAGE=
GARBAGE=
... apply services.patch ...
GARBAGE=
GARBAGE=
apk patch openpdroid/4.1/cm/20130209
... apply Mms.apk.patch ...
The text leading up to this was:
|diff -Npru stock-mms/smali/com/android/mms/transaction/HttpUtils.smali pdroid-mms/smali/com/android/mms/transaction/HttpUtils.smali
|--- stock-mms/smali/com/android/mms/transaction/HttpUtils.smali 2013-07-14 11:42:04.274437468 -0500
|+++ pdroid-mms/smali/com/android/mms/transaction/HttpUtils.smali 2013-07-14 11:41:52.386437820 -0500
File to patch:
Skip this patch? [y]
4 out of 4 hunks ignored
GARBAGE=
GARBAGE=
img patch openpdroid/4.1/cm/20130209
text patch openpdroid/4.1/cm/20130209
rebuild jar
... rebuild framework.jar ...
adding: classes.dex(in = 8785584) (out= 3538095)(deflated 59%)
adding: preloaded-classes(in = 84887) (out= 14594)(deflated 82%)
... rebuild core.jar ...
adding: classes.dex(in = 2512356) (out= 1045997)(deflated 58%)
... rebuild services.jar ...
adding: classes.dex(in = 1818176) (out= 815814)(deflated 55%)
rebuild apk
... rebuild Mms.apk ...
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
I: Building apk file...
create update-cm-anzu-20130805-openpdroid.zip
added manifest
adding: system/framework/framework.jar(in = 3553274) (out= 3529681)(deflated 0%)
adding: system/framework/core.jar(in = 1050235) (out= 1043560)(deflated 0%)
adding: system/framework/services.jar(in = 816273) (out= 815222)(deflated 0%)
adding: system/app/Mms.apk(in = 2220697) (out= 2094119)(deflated 5%)
adding: system/media/PDroid.jpeg(in = 26898) (out= 25744)(deflated 4%)
ignoring entry META-INF/
adding: META-INF/com/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/update-binary(in = 193136) (out= 124459)(deflated 35%)
adding: META-INF/com/google/android/updater-script(in = 2266) (out= 515)(deflated 77%)
finished
Congratulations, the patching was successful.
Any errors you may have seen were succesfully handled!
!!! Only file a bug report if the software is not behaving as expected !!!
---update-cm-anzu-20130805-openpdroid.zip
to restore original system, flash:
---restore-cm-anzu-20130805.zip
==========================================================
The text was updated successfully, but these errors were encountered: