Database Info

Transfering Libraries from Hero to Ion/other ROM?

Hello all,
In my noobishness I tried to install the HtcMusic.apk from the Hero ROM onto a G1 running the Google Ion ROM. Well it gave me a MISSING_SHARED_LIBRARY error so in my ignorance I thought that I would be able to find whatever libraries were missing and transfer them to the Ion build and reflash the update.zip. The update flashed but the apk still cannot be installed. Do I have the concept of libraries wrong here and should just realize that it's not possible without doing other things or am I still missing libraries that should be transferred?
Thanks =)

thelamacmdr said:
Hello all,
In my noobishness I tried to install the HtcMusic.apk from the Hero ROM onto a G1 running the Google Ion ROM. Well it gave me a MISSING_SHARED_LIBRARY error so in my ignorance I thought that I would be able to find whatever libraries were missing and transfer them to the Ion build and reflash the update.zip. The update flashed but the apk still cannot be installed. Do I have the concept of libraries wrong here and should just realize that it's not possible without doing other things or am I still missing libraries that should be transferred?
Thanks =)
Click to expand...
Click to collapse
just adp push the libHtcMusic_jni.so from /system/lib and the HtcMusic.apk to /system/apps and you'll be set.

so i was missing a lib because the update.zip i downloaded doesn't have that...the search begins

Can't find this .so too.

Lib
this one is from a 6.0

And you think this would work for it?
Bcause this lib isn't requiered in the hero build.. *irritated*

Ok I did
Code:
adb remount
adb push libhtcmusic_jni.apk system/lib
adb install HtcMusic.apk
I still get the shared library error, maybe I have to push it to somewhere else or update.zip with the library included?

First Post:,
I've actually been working on this too. I've managed to get it to install. I followed another thread, pushing some stuff from /system/etc/permission and Platform.xml for the HTC stuff. I used the same lib a1t linked (although pulled mine right from the rom).
Although when running it on the phone I get this fun little log message:
Code:
E/dalvikvm( 347): Could not find method android.provider.DrmStore.getDrmConstra
int, referenced from method com.htc.music.MusicUtils.getDrmStatus
W/dalvikvm( 347): VFY: unable to resolve static method 403: Landroid/provider/D
rmStore;.getDrmConstraint (Landroid/content/ContentResolver;Landroid/net/Uri;I)L
android/provider/DrmStore$DrmConstraint;
W/dalvikvm( 347): VFY: rejecting opcode 0x71 at 0x00aa
W/dalvikvm( 347): VFY: rejected Lcom/htc/music/MusicUtils;.getDrmStatus (Landr
oid/content/Context;Landroid/net/Uri;)I
W/dalvikvm( 347): Verifier rejected class Lcom/htc/music/MusicUtils;
D/AndroidRuntime( 347): Shutting down VM
W/dalvikvm( 347): threadid=3: thread exiting with uncaught exception (group=0x4
000fe70)
E/AndroidRuntime( 347): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 347): java.lang.VerifyError: com.htc.music.MusicUtils
E/AndroidRuntime( 347): at com.htc.music.HtcMusic.onStart(HtcMusic.java:
338)
E/AndroidRuntime( 347): at android.app.Instrumentation.callActivityOnSta
rt(Instrumentation.java:1205)
E/AndroidRuntime( 347): at android.app.Activity.performStart(Activity.ja
va:3490)
E/AndroidRuntime( 347): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2240)
E/AndroidRuntime( 347): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2284)
E/AndroidRuntime( 347): at android.app.ActivityThread.access$1800(Activi
tyThread.java:112)
E/AndroidRuntime( 347): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1692)
E/AndroidRuntime( 347): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 347): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 347): at android.app.ActivityThread.main(ActivityThrea
d.java:3948)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:782)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:540)
E/AndroidRuntime( 347): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 60): Sending signal. PID: 347 SIG: 3
I/dalvikvm( 347): threadid=7: reacting to signal 3
I/dalvikvm( 347): Wrote stack trace to '/data/anr/traces.txt'
W/ActivityManager( 60): Launch timeout has expired, giving up wake lock!
Not in the loop as far as the HTC builds go, but there'ls definitely something I'm missing. android.provider is in the sdk, but the DRM stuff isn't (or doesn't seem to be). I tried pushing a few more things to the phone, hoping for a solution, but I ran out of room, I don't have the new SPL.

I can't really tell the problem from looking at this ( I'm kind of inexperienced in the way of Java/Android Application Dev.). Did you push the whole entire library from the HTC Hero ROM or rather the libs that aren't in the Haykuro/JF 1.51

sherlok said:
First Post:,
I've actually been working on this too. I've managed to get it to install. I followed another thread, pushing some stuff from /system/etc/permission and Platform.xml for the HTC stuff. I used the same lib a1t linked (although pulled mine right from the rom).
Although when running it on the phone I get this fun little log message:
Code:
E/dalvikvm( 347): Could not find method android.provider.DrmStore.getDrmConstra
int, referenced from method com.htc.music.MusicUtils.getDrmStatus
W/dalvikvm( 347): VFY: unable to resolve static method 403: Landroid/provider/D
rmStore;.getDrmConstraint (Landroid/content/ContentResolver;Landroid/net/Uri;I)L
android/provider/DrmStore$DrmConstraint;
W/dalvikvm( 347): VFY: rejecting opcode 0x71 at 0x00aa
W/dalvikvm( 347): VFY: rejected Lcom/htc/music/MusicUtils;.getDrmStatus (Landr
oid/content/Context;Landroid/net/Uri;)I
W/dalvikvm( 347): Verifier rejected class Lcom/htc/music/MusicUtils;
D/AndroidRuntime( 347): Shutting down VM
W/dalvikvm( 347): threadid=3: thread exiting with uncaught exception (group=0x4
000fe70)
E/AndroidRuntime( 347): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 347): java.lang.VerifyError: com.htc.music.MusicUtils
E/AndroidRuntime( 347): at com.htc.music.HtcMusic.onStart(HtcMusic.java:
338)
E/AndroidRuntime( 347): at android.app.Instrumentation.callActivityOnSta
rt(Instrumentation.java:1205)
E/AndroidRuntime( 347): at android.app.Activity.performStart(Activity.ja
va:3490)
E/AndroidRuntime( 347): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2240)
E/AndroidRuntime( 347): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2284)
E/AndroidRuntime( 347): at android.app.ActivityThread.access$1800(Activi
tyThread.java:112)
E/AndroidRuntime( 347): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1692)
E/AndroidRuntime( 347): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 347): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 347): at android.app.ActivityThread.main(ActivityThrea
d.java:3948)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 347): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:782)
E/AndroidRuntime( 347): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:540)
E/AndroidRuntime( 347): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 60): Sending signal. PID: 347 SIG: 3
I/dalvikvm( 347): threadid=7: reacting to signal 3
I/dalvikvm( 347): Wrote stack trace to '/data/anr/traces.txt'
W/ActivityManager( 60): Launch timeout has expired, giving up wake lock!
Not in the loop as far as the HTC builds go, but there'ls definitely something I'm missing. android.provider is in the sdk, but the DRM stuff isn't (or doesn't seem to be). I tried pushing a few more things to the phone, hoping for a solution, but I ran out of room, I don't have the new SPL.
Click to expand...
Click to collapse
looks like you're missing the DRM stuff.
libdrmdec_jni.so
libdrmdec.so
libdrm1_jni.so
libdrm1.so
and probably the DrmProvider.apk
If you get this working, def let us know. the music player from that rom is sexy.

I've actually been working on this too. I've managed to get it to install. I followed another thread, pushing some stuff from /system/etc/permission and Platform.xml for the HTC stuff. I used the same lib a1t linked (although pulled mine right from the rom).
Click to expand...
Click to collapse
Hmm what files from system/etc/permissions did you push all of them or just Platform.xml and com.Htc.framework.xml? Cause as far as i know that's the only difference I have from whatt you've been doing except I pushed all of the libraries.

Any of you guys have luck porting the white clock over to Ion? From Hero build or JF? I can get the white notifications, but the clock refuses to budge. Unfortunately my normal goto guy is a bit under the weather.

blackeyedbrian said:
looks like you're missing the DRM stuff.
libdrmdec_jni.so
libdrmdec.so
libdrm1_jni.so
libdrm1.so
and probably the DrmProvider.apk
If you get this working, def let us know. the music player from that rom is sexy.
Click to expand...
Click to collapse
Ok i decided to play with this a little bit.
the method "getDrmConstraint" that is missing, is part of /system/framework/framework.jar on the hero rom. how to get that working on the other builds? i have no idea =D

Anyone got it working now?

Still workin on it, I'm trying to figure out what needs to be transferred. I'm thinking about just transfering all the files that have different file sizes (might check the sums too). I'll get back once I find out.
Edit: Just saw the framework.jar; the files have a difference of 2 mill in file size....
Edit2: Restarted phone after push, it's installed now

thelamacmdr said:
Still workin on it, I'm trying to figure out what needs to be transferred. I'm thinking about just transfering all the files that have different file sizes (might check the sums too). I'll get back once I find out.
Edit: Just saw the framework.jar; the files have a difference of 2 mill in file size....
Edit2: Restarted phone after push, it's installed now
Click to expand...
Click to collapse
so u pushed the lib, apk, n what else? would you mind just clarifying how u got it to work?

I didn't get it to work yet but I did manage to install it, I'm trying to find the location of class com.htc.widget. If anyone can please point it out it would be much appreciated. Once I figure out what I did and then do it again I'll post how to do it.
So far I transferred all of the HTC made libs, platform.xml, com.htc.framework.xml, and libhtcmusic_jni.so
For obvious reasons I won't post the Hero Rom (to get the libs from) and I'm not sure if I'm going too far just trying to use the Music app.

sorry for double post

check the diffs between the two images, this file will show the differences and files that only appear in one image but not the other.
update --> ion
updatehero --> hero
*i removed ringtones and notifications ogg mp3 just to focus on the rest

How did you manage to get this text file? I've been doing it manually....comparing the two zip files.
EDIT: Ok logcat shows
Code:
Could not find class 'com.htc.widget.AboutDialog$Builder', referenced from method com.htc.music.BaseHtcMusic.onCreateDialog
this is followed by a series of verify errors. These classes are located in a lib somewhere I'm assuming?
EDIT2: No longer have class errors, pushed files from system/framework
now receive error
Code:
E/dalvikvm( 330): Could not find method android.provider.DrmStore.getDrmConstra
int, referenced from method com.htc.music.MusicUtils.getDrmStatus

Help with deodexing

First of all - I've never tried to deodex anything before, so I've got zero experience with this or with Java development. So maybe I'm doing something fundamentaly wrong without even realising it.
Anyway. For days now I've been trying to deodex the Legend WWE files or any other odexed ROM for that matter (ie. I've tried deodexing the official Sense UI 32A ROM), but still no success. I'm getting really desperate (thus me asking here instead of trying to solve this on my own), cause I really don't know what I'm doing wrong and I can't find anything relevant to help.
I decompress and deodex the apks/jars like this:
Code:
unzip filename.apk
baksmali -d ./core -c :necessar_classfile1.jar:necessary_classfile2.jar -x filename.odex
smali out -o classes.dex
The "core" dir obviously contains a copy of the ROM framework files (unodexed). This works just fine and deodexes any apk/jar from the Legend RUU without any errors except for RSS.apk and com.htc.rss.jar which throw up dependency errors, but I don't think those two files are that essential, at least not for succesful basic startup of the ROM itself. And besides, as I've said, I've tried other ROMs which didn't give me any errors at all and all files deodexed without a hitch.
Then I recreate the apk/jar like this:
Code:
aapt p -F filename.zip apkdir
zipalign 4 filename.zip filename.apk
I get a nice full set of APKs/JARs. However, if I make a ROM package with these files, there's a *slight* problem - none of the ROMs have made it past boot animation. The best I've managed to do on any of the ROMs I've tested was to get to the point just before the boot screen should switch to system/lockscreen and show the PIN keyboard. Every time this happens, there are misc. uncaught exceptions in log and system server just dies. So obviously my deodexed files are somehow corrupted. The question is - what do I do wrong?
The zipalign has nothing to do with it, I've tried. I've tried using dedexer instead of baksmali. Nothing. I've heard that you need JDK 1.5 for the deodexing - tried the whole process on my usual setup, which is Arch64 box with JDK 1.6, but also on Ubuntu 32bit with JDK 1.5 and on XP with JDK 1.5 - no dice, the end result is always the same (although the JDK was always a newer version than the odexed apps/jars show in the MANIFEST.MF file - can this be a problem?). If I try to decompile some already deodexed jar/apk using baksmali to get the .smali files and then compile them again using smali back to classes.dex, the resulting app/jar works just fine.
Am I missing something here? Any ideas on what's wrong? Thanks for any idea or suggestion.

Case_ said:
Code:
unzip filename.apk
baksmali -d ./core -c :necessar_classfile1.jar:necessary_classfile2.jar -x filename.odex
smali out -o classes.dex
Click to expand...
Click to collapse
Well, the main problem here is that you aren't deodexing anything . Deodexing is the process of reversing odex files so that they only use normal dex instructions. You are just disassembling the dex file. There is no reason to disassemble the dex file, and then immediately re-assemble it with smali, if you're not making any changes to the disassembled files. In short, if there are no .odex files, there is no need to deodex it, because there is nothing to deodex
Also, you don't have to unzip an apk to use baksmali on it. If you are just disassembling an application, you can specify the apk/jar file directly, instead of unzipping it and specifying the classes.dex file. For example, you can simply do:
baksmali filename.apk
Finally, the -d option is used to tell baksmali where it can find the framework files that the odex file is dependent on. If you have extracted the rom and left it in the normal structure (i.e. you have a system/apps dir and a system/framework dir), then assuming you are currently in system/apps, then you would specify -d ../framework. If you want to change the name of the directory that all the smali files are output into, use the -o option.
Case_ said:
Then I recreate the apk/jar like this:
Code:
aapt p -F filename.zip apkdir
zipalign 4 filename.zip filename.apk
Click to expand...
Click to collapse
This is mostly correct. But you can also simply replace the classes.dex file in the zip/apk/jar directly, with any program that can work on zip files.
The problems you are experiencing are likely due to signing issues. Most system applications use shared ids with other system applications and with the system itself, and all apks using a shared user must be signed with the same keys. If you are working with an "official" rom, you obviously don't have the key that was used to sign everything. The solution is to resign everything yourself, either with your own key or with the standard "test key".
Also, you can use adb logcat to show a log while the phone is booting. It should show any errors that occur, and help you debug what is going wrong.

JesusFreke said:
Well, the main problem here is that you aren't deodexing anything . Deodexing is the process of reversing odex files so that they only use normal dex instructions. You are just disassembling the dex file. There is no reason to disassemble the dex file, and then immediately re-assemble it with smali, if you're not making any changes to the disassembled files. In short, if there are no .odex files, there is no need to deodex it, because there is nothing to deodex
Click to expand...
Click to collapse
Oh, in that case I really don't get it at all I guess, because I thought that in order to "deodex" a file, I need to disassemble the .odex file using "baksmali -x file.odex" and then just reassemble it again with smali as classes.dex, which is what I'm doing here. I did get this impression from your deodexing guide on baksmali pages (although you don't mention the part about reassembling the files, yeah) and a few other mentions about deodexing here and there on XDA and other forums and also solidified it by having a look at crzyruski's "auto deodexing script" for Windows, because I think that's precisely what the script is doing. I thought that just by disassembling the .odex baksmali in effect "pulls" classes that the file depends on from other core files into the one being disassembled and reassembling with smali integrates those into the internal classes.dex so that the APK/JAR becomes self-standing and does not depend on other files anymore.
But if what I'm doing is not the correct way to deodex a file, as you say, then I obviously have absolutely no idea how the deodexing really is done So after disasembling the odex file into smali files I need to modify those further (manually and with the knowledge of Java/Dalvik, I presume?) and THEN reassemble them?
JesusFreke said:
Also, you don't have to unzip an apk to use baksmali on it.
Click to expand...
Click to collapse
Yeah, sorry, I forgot to remove that unzip part from my example, I took it out of a very basic script I've made and just modified the filenames to generic ones before posting the example here. I'm unzipping the files because I want to optipng them before repackaging, not because I thought it's a necessary step for using baksmali. Sorry about the confusion.
JesusFreke said:
This is mostly correct. But you can also simply replace the classes.dex file in the zip/apk/jar directly, with any program that can work on zip files.
Click to expand...
Click to collapse
See before. And I wanted to use the proper tool for repackaging the APKs/JARs because I've seen APKs that were corrupted by using regular ZIP on them, ie. I've seen "the OGG problem" a few times as also mentioned by brut here: http://forum.xda-developers.com/showpost.php?p=5136912&postcount=871
JesusFreke said:
The problems you are experiencing are likely due to signing issues. Most system applications use shared ids with other system applications and with the system itself, and all apks using a shared user must be signed with the same keys. If you are working with an "official" rom, you obviously don't have the key that was used to sign everything. The solution is to resign everything yourself, either with your own key or with the standard "test key".
Also, you can use adb logcat to show a log while the phone is booting. It should show any errors that occur, and help you debug what is going wrong.
Click to expand...
Click to collapse
I've had those problems with signing and did resign the whole ROM and they disappeared, at least from the log, so I don't think what I'm experiencing is related to that - at least the log no longer shows any problems with signatures, it's just those uncaught exceptions coming up that are not there when using the original .apk+.odex. I don't see anything obvious in log pointing at some kind of specific problem with the files.
Anyway, thanks for the reply, much appreciated, even though now I'm even more lost than I thought I was...

Case_ said:
Oh, in that case I really don't get it at all I guess, because I thought that in order to "deodex" a file, I need to disassemble the .odex file using "baksmali -x file.odex" and then just reassemble it again with smali as classes.dex, which is what I'm doing here. I did get this impression from your deodexing guide on baksmali pages (although you don't mention the part about reassembling the files, yeah) and a few other mentions about deodexing here and there on XDA and other forums and also solidified it by having a look at crzyruski's "auto deodexing script" for Windows, because I think that's precisely what the script is doing.
Click to expand...
Click to collapse
sorry, I had misread your example commands. I just saw that you were unzipping the apk, and I guess I assumed you were running baksmali on a classes.dex file. The commands do look mostly correct, now that I've re-read them .
Are you touching the framework files at all? Or does anything else depend on what you are deodexing? Because when you deodex something, you have to deodex everything that depends on it as well (and everything depends on the framework files, so you would have to deodex everything if you touch them).
An example of the exceptions that you get might be helpful

I'm trying to basically deodex the whole ROM, so yes, I'm touching both framework and all of the apps. I deodex the framework files and then, using those deodexed files, I deodex the apps as well.
The exception and the following crash I'm mostly getting is this one:
Code:
I/ActivityThread( 305): Publishing provider sms: com.android.providers.telephony.SmsProvider
I/ActivityThread( 305): Publishing provider mms-sms: com.android.providers.telephony.MmsSmsProvider
I/ActivityThread( 305): Publishing provider qtext: com.android.providers.telephony.QTextProvider
I/ActivityThread( 305): Publishing provider cbchannels: com.android.providers.telephony.CBProvider
I/ActivityThread( 305): Publishing provider icc: com.android.phone.IccProvider
I/ActivityThread( 305): Publishing provider htcmsgs: com.android.providers.telephony.HtcMsgsProvider
I/ActivityThread( 305): Publishing provider mms: com.android.providers.telephony.MmsProvider
D/dalvikvm( 102): GC freed 5316 objects / 475320 bytes in 807ms
I/OOBE_MainActivity( 322): onCreate OOBE 1.1
V/htcCheckinService( 102): Checkin service onCreate()!
I/RecoverySystem( 102): No recovery log file
D/htcCheckinProvider( 102): htcCheckinProvider::onCreate(SQLiteDatabase) start
D/htcCheckinProvider( 102): htcCheckinProvider::onCreate(SQLiteDatabase) end
W/dalvikvm( 102): VFY: bad exception entry: startAddr=95 endAddr=95 (size=681)
W/dalvikvm( 102): VFY: rejected Lcom/android/providers/htcCheckin/htcCheckinService$htcCheckinReceiver;.run ()V
W/dalvikvm( 102): Verifier rejected class Lcom/android/providers/htcCheckin/htcCheckinService$htcCheckinReceiver;
W/dalvikvm( 102): threadid=15: thread exiting with uncaught exception (group=0x4001e390)
E/AndroidRuntime( 102): Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
E/AndroidRuntime( 102): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 102): java.lang.VerifyError: com.android.providers.htcCheckin.htcCheckinService$htcCheckinReceiver
E/AndroidRuntime( 102): at com.android.providers.htcCheckin.htcCheckinService.onCreate(htcCheckinService.java:289)
E/AndroidRuntime( 102): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2894)
E/AndroidRuntime( 102): at android.app.ActivityThread.access$3200(ActivityThread.java:126)
E/AndroidRuntime( 102): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1986)
E/AndroidRuntime( 102): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 102): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 102): at com.android.server.ServerThread.run(SystemServer.java:509)
D/OOBE_MainActivity( 322): hasSetupWizRun = 0
D/dalvikvm( 305): Note: class Lcom/android/internal/telephony/BaseCommands; has 158 unimplemented (abstract) methods
I/Process ( 102): Sending signal. PID: 102 SIG: 9
D/OOBE_MainActivity( 322): startActivityForResult nRequestCode == 1, mnCurStep == 0
V/OOBE_MainActivity( 322): No previous activity to back aftert back key pressed
V/OOBE_MainActivity( 322): Customization has not run.
I/ServiceManager( 68): service 'activity' died
I/ServiceManager( 68): service 'activity.senders' died
I/ServiceManager( 68): service 'telephony.registry' died
I/ServiceManager( 68): service 'power' died
I/ServiceManager( 68): service 'batteryinfo' died
I/ServiceManager( 68): service 'SurfaceFlinger' died
I/ServiceManager( 68): service 'permission' died
I/ServiceManager( 68): service 'usagestats' died
I/ServiceManager( 68): service 'entropy' died
I/ServiceManager( 68): service 'devicestoragemonitor' died
I/ServiceManager( 68): service 'location' died
I/ServiceManager( 68): service 'notification' died
I/ServiceManager( 68): service 'bluetooth_spp' died
I/ServiceManager( 68): service 'activity.providers' died
I/ServiceManager( 68): service 'package' died
I/ServiceManager( 68): service 'meminfo' died
I/ServiceManager( 68): service 'activity.services' died
I/ServiceManager( 68): service 'cpuinfo' died
I/ServiceManager( 68): service 'window' died
I/ServiceManager( 68): service 'input_method' died
I/ServiceManager( 68): service 'wifi' died
I/ServiceManager( 68): service 'mount' died
I/ServiceManager( 68): service 'activity.broadcasts' died
I/ServiceManager( 68): service 'bluetooth_pbap' died
I/ServiceManager( 68): service 'bluetooth_avrcp' died
I/ServiceManager( 68): service 'statusbar' died
I/ServiceManager( 68): service 'bluetooth' died
I/ServiceManager( 68): service 'account' died
I/ServiceManager( 68): service 'clipboard' died
I/ServiceManager( 68): service 'netstat' died
I/ServiceManager( 68): service 'audio' died
I/ServiceManager( 68): service 'bluetooth_a2dp' died
I/ServiceManager( 68): service 'content' died
I/ServiceManager( 68): service 'mcp_monitor' died
I/ServiceManager( 68): service 'search' died
I/ServiceManager( 68): service 'connectivity' died
I/ServiceManager( 68): service 'accessibility' died
I/ServiceManager( 68): service 'wallpaper' died
I/ServiceManager( 68): service 'battery' died
I/ServiceManager( 68): service 'hardware' died
I/ServiceManager( 68): service 'alarm' died
I/ServiceManager( 68): service 'sensor' died
I/ServiceManager( 68): service 'backup' died
I/ServiceManager( 68): service 'appwidget' died
I/ServiceManager( 68): service 'htc_checkin' died
I/ServiceManager( 68): service 'checkin' died
E/SearchManager( 308): getSearchablesInGlobalSearch() failed: android.os.DeadObjectException
D/AndroidRuntime( 308): Shutting down VM
W/dalvikvm( 308): threadid=3: thread exiting with uncaught exception (group=0x4001e390)
E/AndroidRuntime( 308): Uncaught handler: thread main exiting due to uncaught exception
I/ActivityThread( 322): Removing dead content provider: settings
I/ActivityThread( 305): Removing dead content provider: settings
D/BootAnimation( 111): SurfaceFlinger died, exiting...
I/OOBE_MainActivity( 322): onResume
E/installd( 75): eof
E/installd( 75): failed to read size
I/installd( 75): closing connection
E/AndroidRuntime( 308): java.lang.RuntimeException: Unable to get provider com.android.globalsearch.SuggestionProvider: java.lang.NullPointerException
E/AndroidRuntime( 308): at android.app.ActivityThread.installProvider(ActivityThread.java:4502)
E/AndroidRuntime( 308): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4229)
E/AndroidRuntime( 308): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4188)
E/AndroidRuntime( 308): at android.app.ActivityThread.access$2900(ActivityThread.java:126)
E/AndroidRuntime( 308): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1970)
E/AndroidRuntime( 308): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 308): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 308): at android.app.ActivityThread.main(ActivityThread.java:4595)
E/AndroidRuntime( 308): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 308): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 308): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 308): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 308): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 308): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 308): at com.android.globalsearch.SuggestionSources.addExternalSources(SuggestionSources.java:249)
E/AndroidRuntime( 308): at com.android.globalsearch.SuggestionSources.updateSources(SuggestionSources.java:240)
E/AndroidRuntime( 308): at com.android.globalsearch.SuggestionSources.load(SuggestionSources.java:194)
E/AndroidRuntime( 308): at com.android.globalsearch.SuggestionProvider.onCreate(SuggestionProvider.java:100)
E/AndroidRuntime( 308): at android.content.ContentProvider.attachInfo(ContentProvider.java:710)
E/AndroidRuntime( 308): at android.app.ActivityThread.installProvider(ActivityThread.java:4499)
E/AndroidRuntime( 308): ... 12 more
I/Zygote ( 72): Exit zygote because system server (102) has terminated
I/Process ( 308): Sending signal. PID: 308 SIG: 9
E/ActivityThread( 305): Failed to find provider info for settings
D/AndroidRuntime( 305): Shutting down VM
W/dalvikvm( 305): threadid=3: thread exiting with uncaught exception (group=0x4001e390)
E/AndroidRuntime( 305): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 305): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NullPointerException
E/AndroidRuntime( 305): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4195)
E/AndroidRuntime( 305): at android.app.ActivityThread.access$2900(ActivityThread.java:126)
E/AndroidRuntime( 305): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1970)
E/AndroidRuntime( 305): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 305): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 305): at android.app.ActivityThread.main(ActivityThread.java:4595)
E/AndroidRuntime( 305): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 305): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 305): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 305): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 305): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 305): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 305): at android.content.ContentResolver.registerContentObserver(ContentResolver.java:831)
E/AndroidRuntime( 305): at com.android.internal.telephony.gsm.GsmServiceStateTracker.<init>(GsmServiceStateTracker.java:250)
E/AndroidRuntime( 305): at com.android.internal.telephony.gsm.GSMPhone.<init>(GSMPhone.java:216)
E/AndroidRuntime( 305): at com.android.internal.telephony.gsm.GSMPhone.<init>(GSMPhone.java:203)
E/AndroidRuntime( 305): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:117)
E/AndroidRuntime( 305): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:52)
E/AndroidRuntime( 305): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:941)
E/AndroidRuntime( 305): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:969)
E/AndroidRuntime( 305): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4192)
E/AndroidRuntime( 305): ... 10 more
I/Process ( 305): Sending signal. PID: 305 SIG: 9
Happens right at the end of the first boot, just before the screen should switch from boot animation to system. DexInv runs through all the apps during the boot and doesn't really show anything I'd call out of the ordinary. Replacing or removing the CheckinProvider.apk doesn't really help anything, the crash is just caused a bit later by some other app.
The thing I'm thinking about now after your mention of reodexing everything the deodexed file depends upon is if it's not possible that I'm deodexing the framework in the wrong order instead of some specific one I should be following. I'm just deodexing it alphabetically, pretty much - it showed no errors during the process so I didn't really think about that this might be the problem.

Have u tried -> auto-deodexer??

http://forum.xda-developers.com/showpost.php?p=5806405&postcount=78
http://forum.xda-developers.com/showthread.php?t=560271

Yes, I have tried crzyruski's script (that's the "on XP with JDK 1.5" part of my original post, and I also mentioned in my second post that I've looked into that script to see if I'm not missing anything I should be doing).
I'm doing exactly what both of those scripts do, except that I do it on Linux (but again, as I've said, have tried crzyruski's script directly on Windows XP with the same results).
But then again why not, I'll try it one more time, just to be sure I didn't miss anything the first time, but I doubt the result will be any different.

So, I've tried czyruski's script one more time in XP. No change. I've tried not touching the framework files at all and leaving them odexed, thinking I might have some problems with deodexing them. No change. Tried resigning all apps in the ROM, not signing them at all, skipping zipalign...nothing. The deodexing seems to go just fine, no errors whatsoever. The deodexed APKs I create are exactly the same, to the very last bit, whether I deodex in Arch 64 using JDK 1.6 or in Ubuntu using JDK 1.5. No changes at all, yet the ROM starts just fine with odexed APKs and crashes on startup once I deodex them.
Any idea what might be wrong? Am I missing something obvious? Do I need to have some kind of build setup for deodexing or do I really just install JDK, run baksmali/smali and be done with it (which is what I'm doing)? I really don't get it why this fails when it seems like it's going fine...

For any HTC Sense stuff, you have to add the HTC Framework bootclasspaths (which you prob have, just make sure you have them all)
You can get these by looking in the boot.img's init.rc (will say bootclasspath right at the top with the files u need to include)

Yeah, I did add those and of course added the other necessary JARs as well. I'm testing it for now on the Eris dump, mostly. To be specific, for deodexing framework, I'm using this:
Code:
baksmali -d ~/deodex/core -c :core.jar:ext.jar:framework.jar:android.policy.jar:services.jar:com.htc.framework.jar:com.htc.android.pimlib.jar:com.htc.android.easopen.jar:com.scalado.util.ScaladoUtil.jar -x ../filename.odex
and for deodexing the APKs this:
Code:
baksmali -d ~/deodex/core -c :core.jar:ext.jar:framework.jar:android.policy.jar:services.jar:com.htc.framework.jar:com.htc.android.pimlib.jar:com.htc.android.easopen.jar:com.scalado.util.ScaladoUtil.jar:javax.obex.jar:com.google.android.maps.jar -x ../filename.odex
Where ~/deodex/core is of course the directory I put the original odexed framework into.
The deodexing seems to go just fine, no errors, no missing classes, nothing. That's why I'm so stumped by this and asking for help here, I have spent literally days over this and really have no idea what am I possibly doing wrong here, everything seems to go just as it should, it's just that the result doesn't work for some reason.

I have the same problem with you ~com.htc.rss.odex~

That file, as far as I can tell, is a special case, cause it seems to have dependencies to classes not contained within any of the framework files.

It has driven me crazy~

+ 1 with this issue, I've tried all types of combos to get this working. I will try to talk with JF in #smali channel for help

Same problem here, did you make any progress?

If you're reffering to my original problem that I can't get anything deodexed to work, then no, I didn't make any progress. Wasted an awful lot of time on that without any result and any understanding what am I doing wrong and finally gave up. I've again tried deodexing the latest Sprint Hero leak about two weeks ago, still the same - deodexing goes fine, the result crashes on startup.

Same problem.
I'm trying to deodex sprint release.
All your errors are mine also.
As I understand there is no need to deodex framework and most of the apps, cause usually you don't edit it's assemble code, you edit resources (pngs for example). Just re-sign it to be compatible with other apps which you really change (Correct me, if I'm wrong)
I've tried it, it boots, but I have other exceptions from different apps. One was ogg-error, mentioned by you.
PS. and yep. sorry for my bloody English

Please don't hijack the thread, thanks. Also, some of your questions are already answered here.

Case_ said:
Please don't hijack the thread, thanks. Also, some of your questions are already answered here.
Click to expand...
Click to collapse
I'm sorry. Wasn't going to do so. Just want to point, that usually there is no need to do full deodex.

A2SD for Sense Froyo 2.2 (DJDroid) - Nearly done.

UPDATE:
I managed my problem, checked and tried.
BUT: WTF?! ALL IS DONE - AND IT SAYS: No Ext mounted? WTF - now I need help - and it's done. :>
IF I GET FASTLY HELP WE HAVE THE OLD A2SD IN THE NEXT 20 MINUTES
It only says:
[X] Ext partition found, but not mounted.
Your rom may not be setup to run A2SD.
Check with your rom developer if the boot image
is programmed to run A2SD.
I checked the Boot.img 2 times - all is prepared. My SD haza 512mb A2SD - Ext - Partition. And what now? ...

great news, m8!

You could install linux in a virtual machine quite easily
Sent from my HTC Desire using XDA App

DarkMio said:
Hey guys. I'm nearly done with a superfast way for our A2SD for the new Sense ROM. My only problem ist atm that I can't edit the boot.img, because I don't have any linuxmachine with gunzip here. Only 2 Win XP PCs.
Now I need someone, who can work with basics of Perl, unpack the boot.img, gunzip the RAMDisk file, made simply changes and repack them.
So we have a full-working A2SD-Bootimg and can start with the real one.
Click to expand...
Click to collapse
why not try virtualbox? one of the easiest ways to use linux on a windows machine

ubuntu will infact install as a program in windows, making a VM for itself all automatic.
Just pop in the CD in windows and run "wubi.exe"

Okay - UPDATE:
I managed my problem, checked and tried.
BUT: WTF?! ALL IS DONE - AND IT SAYS: No Ext mounted? WTF - now I need help - and it's done. :>

you tried to mount and unmount the ext in recovery and then reboot.

Nekromantik said:
you tried to mount and unmount the ext in recovery and then reboot.
Click to expand...
Click to collapse
Which task was it in the clockwork-recovery?
mount /Sd-ext?
Okay - done - need to flash a new a2sd - I bricked my version a lil'... ^^'

can't find the following line: “setprop net.tcp.buffersize.wimax4096,87380,110208,4096,163 84,110208”
only default, wifi, umts, edge, gprs

I think so

DarkMio said:
Which task was it in the clockwork-recovery?
mount /Sd-ext?
Okay - done - need to flash a new a2sd - I bricked my version a lil'... ^^'
Click to expand...
Click to collapse
yes mount /sd-ext

peewster said:
can't find the following line: “setprop net.tcp.buffersize.wimax4096,87380,110208,4096,163 84,110208”
only default, wifi, umts, edge, gprs
Click to expand...
Click to collapse
only search 'net.tcp.buffersize' ...
:> But I had done it... And it's still there - I am wondering why...

Ext support is compiled in the kernel isn't it?

DarkMio said:
only search 'net.tcp.buffersize' ...
:> But I had done it... And it's still there - I am wondering why...
Click to expand...
Click to collapse
that shows me 5 lines of net.tcp.buffersize but no wimax. Only default, wifi, gprs etc

Klutsh said:
Ext support is compiled in the kernel isn't it?
Click to expand...
Click to collapse
I think so - in the recovery I can read the ext ...
And I managed to copy the ext - but the system boot the sd first.
If I try to reboot - It does it - without bootloops.
Anyone knows more about it? It maybe could help, If some know a lot more about A2SD and the right kernel...

peewster said:
that shows me 5 lines of net.tcp.buffersize but no wimax. Only default, wifi, gprs etc
Click to expand...
Click to collapse
wimax isn't neccesary... :> But look two lines under that... There is still the lines. ...

i think you need to modify the kernal to support ext.
might be wrong

Good news - now I tried ... I think ... the first a2sd-app.
Need to check a lot more, but the first try now worked. ... Maybe it's only a flashing and a line. ... Let it boot.
Bah, It worked - only if it was booted.
Now ...:
I/Process ( 101): Sending signal. PID: 101 SIG: 9
E/AndroidRuntime( 101): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 101): java.lang.NullPointerException
E/AndroidRuntime( 101): at android.app.ActivityThread.getProvider(Activi
tyThread.java:4523)
E/AndroidRuntime( 101): at android.app.ActivityThread.acquireProvider(Ac
tivityThread.java:4563)
E/AndroidRuntime( 101): at android.app.ContextImpl$ApplicationContentRes
olver.acquireProvider(ContextImpl.java:1660)
E/AndroidRuntime( 101): at android.content.ContentResolver.acquireProvid
er(ContentResolver.java:744)
E/AndroidRuntime( 101): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:638)
E/AndroidRuntime( 101): at android.provider.Settings$Secure.getString(Se
ttings.java:2422)
E/AndroidRuntime( 101): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:292)
E/AndroidRuntime( 101): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:67)
E/AndroidRuntime( 101): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:257)
E/AndroidRuntime( 101): Error reporting crash
E/AndroidRuntime( 101): java.lang.NullPointerException
E/AndroidRuntime( 101): at com.android.internal.os.RuntimeInit$UncaughtH
andler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 101): at java.lang.ThreadGroup.uncaughtException(Threa
dGroup.java:887)
E/AndroidRuntime( 101): at java.lang.ThreadGroup.uncaughtException(Threa
dGroup.java:884)
I/ServiceManager( 63): service 'SurfaceFlinger' died
I/ServiceManager( 63): service 'entropy' died
I/ServiceManager( 63): service 'power' died
I/ServiceManager( 63): service 'network_management' died
I/ServiceManager( 63): service 'netstat' died
I/ServiceManager( 63): service 'telephony.registry' died
I/ServiceManager( 63): service 'batteryinfo' died
I/ServiceManager( 63): service 'usagestats' died
I/ServiceManager( 63): service 'clipboard' died
D/HtcBootAnimation( 113): SurfaceFlinger died, exiting...
E/installd( 71): eof
E/installd( 71): failed to read size
I/installd( 71): closing connection
I/Zygote ( 68): Exit zygote because system server (101) has terminated
And it is dead. ...

So it's worth a shot ?

I'm not sure, what it done.
Why It's stucked.
Atm I'm in tha bootscreen - the logcat says the last one - nothing more.
A2SD said: Hey, I running perfectly, I dunno what you mean - I feel fine.
Mhmhmh. I need someone, who had done an A2SD for Desire-Roms.

[Q] Force close on ALL applications when keyboard input is requested

This one is fun - I'm getting an FC every time an application requests keyboard input. If I hit the Google search icon on the top left of the home screen, it immediately FCs - that's what I'm using to test.
I downloaded aLogCat to the device via Google Play on my desktop, and ran it. Here is what I believe to be the relevant log section , from tapping the search icon, to re-entering aLogCat.
I believe the ClipboardEx service is causing the issue, possibly as an interference with another app I have installed - but I don't know what, or how to give you guys a list of apps installed without just typing each one.
This issue happened once to me, and a factory restore fixed it - two weeks later, and it's back. I'm not an experience Android guy, though I am a nerd and a developer. Surely this is something fixable. Does anyone have any thoughts on what could be causing this?
Code:
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=1, s=]
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/ActivityManager( 184): START {intent.toShortString} from pid 383
D/PowerManagerService( 184): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1008000 uid : 1000 pid : 184 tag : ActivityManager
W/ActivityManager( 184): mDVFSLock.acquire()
D/Launcher.HomeFragment( 383): onPause
D/Launcher( 383): onPause
V/TaskCloserActivity( 3234): TaskCloserActivity onReceive()
D/KeyguardViewMediator( 184): setHidden false
D/ActivityManager( 184): Trying to launch applicationName
D/ControlPanelRemoteService( 3246): onDestroy()
D/OpenGLRenderer( 383): Flushing caches (mode 1)
D/dalvikvm( 3157): GC_CONCURRENT freed 259K, 5% free 6784K/7111K, paused 2ms+3ms
D/KeyguardViewMediator( 184): setHidden false
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/libEGL ( 3157): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 3157): Enabling debug mode 0
E/ClipboardServiceEx( 3157): Had failed to obtaining clipboardEx service.
D/AndroidRuntime( 3157): Shutting down VM
W/dalvikvm( 3157): threadid=1: thread exiting with uncaught exception (group=0x40bb01f8)
E/AndroidRuntime( 3157): FATAL EXCEPTION: main
E/AndroidRuntime( 3157): java.lang.NullPointerException
E/AndroidRuntime( 3157): at android.sec.clipboard.ClipboardExManager.updateData(ClipboardExManager.java:241)
E/AndroidRuntime( 3157): at android.widget.EditText.onFocusChanged(EditText.java:134)
E/AndroidRuntime( 3157): at android.view.View.handleFocusGainInternal(View.java:3727)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5420)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2113)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5370)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1598)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2459)
E/AndroidRuntime( 3157): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3157): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3157): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime( 3157): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 184): Force finishing activity com.google.android.googlequicksearchbox/.SearchActivity
E/android.os.Debug( 184): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate( 3272): begin
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{423f3fe0 com.google.android.googlequicksearchbox/.SearchActivity}
W/PowerManagerService( 184): Timer 0x7->0x3|0x0
I/PowerManagerService( 184): Ulight 7->3|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 0
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/InputReader( 184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.70 ]
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/PowerManagerService( 184): Ulight 3->7|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 140
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/VoldCmdListener( 89): asec list
D/VoldCmdListener( 89): CommandListener::AsecCmd::runCommand -> --
I/dumpstate( 3272): done
D/KeyguardViewMediator( 184): setHidden false
D/Launcher( 383): onResume
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/myTest ( 383): [MonthTheme] onResume!!
D/KeyguardViewMediator( 184): setHidden false
D/myTest ( 383): firstDayOfWeek = -1
I/power ( 184): *** release_dvfs_lock : lockType : 1
D/myTest ( 383): [MonthView] updateView.mStartDay: 1
D/DEFERED_APP_VISIBILITY( 184): tweaking closing app
D/PowerManagerService( 184): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 184): mDVFSLock.release()
D/Launcher.HomeFragment( 383): onResume

I've now removed all downloaded applications from my Tab. No dice.
I'm going to see if I can dig up any more logs, then reset it I guess.

I've discovered that copying something to the clipboard also causes the FC. This is definitely an issue with TouchWiz's clipboard as far as I can figure out.

Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium

jamesd86 said:
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It works for me, too, until the whole thing starts crashing, lol.
I reset to factory and re-installed all my stuff; it seems to be working now. I guess it's Samsung's way of reminding me to keep regular backups...

My tab crashed and then this same exact thing started happening. The logs mentioned ClipboardServiceEx.
I am rooted, so I started an adb shell and found that /data/clipboard has all the persistent clipboard entries (I love that feature by the way).
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
This fixed it, although it cleared all my "held" info in the clipboard. A small price to pay. If you really had to, you could probably fish in /data/oldclipboard for it. Of course, now I will go delete oldclipboard.
Hope that helps someone.

Thanks for that info, you never know!
Pp.
Transmitted from another galaxy with an Infected P-5113.

same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt

dorkmo said:
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
Click to expand...
Click to collapse
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.

wd5gnr said:
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
Click to expand...
Click to collapse
ok newbie here with samsung tabs having same problem, how do you boot into recovery and do an adb shell ? can see above how to clear the clipboard directory and i dont want to factory reset too hard to reload all the crap on ....
thanks

I had the same problem, I do not want to root my device, but I like to use the standard key board from Sumsung. I send a a-mail to a lot of dutch companies (resellers) to tell them about the problem. I think that Sansung must make a firware update to solve this problem. I what to ask all people who have problems with the keyboard to e-mail Samsung and there reseller to put preasure on Samsung to make a firmware.
I use a work a round, I use a 3e party keyboard untill Samsung makes a firmware update.

wd5gnr said:
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
Hope that helps someone.
Click to expand...
Click to collapse
YEZZZZZ THANK YOU VERY MUCH!!!:good::laugh:
This worked perfectly on my Samsung Galaxy Tab 2 10.1 (P5110)

Thanks wd5gnr for the solution, worked very well!
Regards.

Glad it helped. I noticed someone asked earlier for more details.
There are plenty of root tutorials here. As for installing ADB there are a few ways to go and it depends on your PC's OS and if you want to get someone's simplified package or not. Read: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and the comments on that page too. If you google something like "installing ADB" you should find lots of help.
Once you have adb installed and can get to a shell, you should be good with my earlier instructions.

[Q] PA install stuck in bootloop

Hi Guys,
I have tried to get PA working on my TAB for three days - and im still stuck. I would appreciate any help you can give.
Installed ICS stock (that works)
Did a CWM install via ODIN.
Install the latest PA zip for my 6800
reboot to recovery
factory reset (reboots the device)
reset cache and davlik
stuck in a bootloop
My logfile is at pastebin
pastebin . com/LM35NZYu
Any help is appreciated.
I think this is where i dies, but i have no clue on how to fix it - and google is not much help.
Code:
E/ActivityThread( 2226): Failed to find provider info for settings
E/System ( 2226): ******************************************
E/System ( 2226): ************ Failure starting core service
E/System ( 2226): java.lang.NullPointerException
E/System ( 2226): at android.provider.Settings$NameValueCache.getString(Settings.java:737)
E/System ( 2226): at android.provider.Settings$Secure.getString(Settings.java:3210)
E/System ( 2226): at android.provider.Settings$Secure.getInt(Settings.java:3278)
E/System ( 2226): at com.android.server.am.CoreSettingsObserver.populateCoreSettings(CoreSettingsObserver.java:93)
E/System ( 2226): at com.android.server.am.CoreSettingsObserver.sendCoreSettings(CoreSettingsObserver.java:70)
E/System ( 2226): at com.android.server.am.CoreSettingsObserver.<init>(CoreSettingsObserver.java:55)
E/System ( 2226): at com.android.server.am.ActivityManagerService.installSystemProviders(ActivityManagerService.java:6732)
E/System ( 2226): at com.android.server.ServerThread.run(SystemServer.java:222)
I/SystemServer( 2226): Input Method Service
W/InputMethodManagerService( 2226): Couldn't create dir.: /data/system/inputmethod
F/SystemServer( 2226): BOOT FAILURE starting Input Manager Service
F/SystemServer( 2226): java.lang.NullPointerException
F/SystemServer( 2226): at android.provider.Settings$NameValueCache.getString(Settings.java:737)
F/SystemServer( 2226): at android.provider.Settings$Secure.getString(Settings.java:3210)
F/SystemServer( 2226): at com.android.server.InputMethodManagerService.<init>(InputMethodManagerService.java:627)
F/SystemServer( 2226): at com.android.server.ServerThread.run(SystemServer.java:309)
E/ActivityThread( 2226): Failed to find provider info for settings
W/SystemServer( 2226): ***********************************************
I/SystemServer( 2226): Accessibility Manager
W/SystemServer( 2226): ***********************************************
F/SystemServer( 2226): BOOT FAILURE making display ready
F/SystemServer( 2226): java.lang.NullPointerException
F/SystemServer( 2226): at com.android.server.ServerThread.run(SystemServer.java:325)
F/SystemServer( 2226): BOOT FAILURE performing boot dexopt
F/SystemServer( 2226): java.lang.NullPointerExceptionF/SystemServer( 2226): at com.android.server.am.ActivityManagerService.showBootMessage(ActivityManagerService.java:4201)
F/SystemServer( 2226): at com.android.server.pm.PackageManagerService.performBootDexOpt(PackageManagerService.java:3357)
F/SystemServer( 2226): at com.android.server.ServerThread.run(SystemServer.java:331)
W/SystemServer( 2226): ***********************************************
W/dalvikvm( 2226): threadid=12: thread exiting with uncaught exception (group=0x40f4e300)
I/Process ( 2226): Sending signal. PID: 2226 SIG: 9
E/AndroidRuntime( 2226): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 2226): java.lang.NullPointerException
E/AndroidRuntime( 2226): at com.android.server.am.ActivityManagerService.showBootMessage(ActivityManagerService.java:4201)
E/AndroidRuntime( 2226): at com.android.server.ServerThread.run(SystemServer.java:337)
I/Zygote ( 2090): Exit zygote because system server (2226) has terminated
I/Netd ( 2262): Netd 1.0 starting
I/ServiceManager( 1741): service 'media.yamahaplayer' died
E/installd( 1751): eof
E/installd( 1751): failed to read size
I/installd( 1751): closing connection
I/ServiceManager( 1741): service 'SecTVOutService' died
I/ServiceManager( 1741): service 'media.audio_flinger' died
I/ServiceManager( 1741): service 'media.player' died
I/ServiceManager( 1741): service 'media.camera' died
I/ServiceManager( 1741): service 'media.audio_policy' died
I/ServiceManager( 1741): service 'activity' died
I/ServiceManager( 1741): service 'meminfo' died

No gapps?
Try this:
- Flash PA
- Reboot recovery
- Flash PA and then flash gapps (No reboot in between this flashing)
- Full wipe (data, cache and dalvik)
- Fix permission
- Reboot.

Still does not work
Astrix Ashburn said:
No gapps?
Try this:
- Flash PA
- Reboot recovery
- Flash PA and then flash gapps (No reboot in between this flashing)
- Full wipe (data, cache and dalvik)
- Fix permission
- Reboot.
Click to expand...
Click to collapse
I have tried, and it still does not work.
I also did a full redownload of PA and gapps, verified the hash, to make sure it was correct. Still a no-go.
It worries me a bit, because either something is wrong with my tablet, or my skillset.
A lot of ppl have figured out how to install PA.

jhojgaard said:
I have tried, and it still does not work.
I also did a full redownload of PA and gapps, verified the hash, to make sure it was correct. Still a no-go.
It worries me a bit, because either something is wrong with my tablet, or my skillset.
A lot of ppl have figured out how to install PA.
Click to expand...
Click to collapse
Same problem with my 7.7, mine was success running PA, but sometimes random bootlop or stuck on jellybean logo, after restart.
Than I choose to flash zeta rom 4.0 And running smoothly , yes because I think jellybean port for 7.7 is not stable right now.
So I think you better use ics rom / custom ics right now.