Related
[ROM] [G1/MAGIC] 14/OCT/09 Android 1.6 AKIRAH "Phoenix" 3.1 - BFS303 memory patch
Back from ashes...
This is official android 1.6 release for ADP1 + some AOSP, rooted and modified.
Current version
HTML:
3.1
* Fixed data synchronization
* Better terminal instead of terminal.apk
* WIFI Tether 1.6pre3
* More languages
* Camera should be fixed
* IM is back
* comes with ROM Updater
Suggest to wipe ext, and wipe data. You know the rules, might not be really required, but expect some FC's and problems.
Known issues
HTML:
[I]No T-Mobile IM[/I]
Past versions
HTML:
3.0.2a Comes with BFS-303 + memory patch kernel (107 Mb RAM)
* most of problems should be fixed now
* Terminal, Wifi-Tether 1.6pre3
[ problems: no data synchronization, gmail push broken ]
3.0.1
kernel 2.6.29-mkk5 BFS 303
Japanese keyboard fixed
New cyanogen init.d
Cyanogen phone.apk and mms.apk
3.0
- updated frameworks and apks from official framework and SDK.
- Supported languages: Czech, German, English, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Russian
- added some parts of text to speech and accessibility
- Full package update (no wipe required)
I suggest to cleanup /system/sd/dalvik-cache (might work without, but it's better to do that).
2.1 - upgraded kernel to 2.6.29.6-bfs300-mkk2
see 2.0
2.0 - apps2sd
cm kernel 2.6.29 from 4.1.11.1
all donut goodies
compcache enabled by default
terminal, pdfreader, htc ime, and few things that I've forget to mention
What it requires:
HTML:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
DangerSPL / HaykuroSPL
Installation
HTML:
Backup
Wipe
* You might need to format your linux partition
Flash
Downloads
Akirah 3.1
ANDROID1.6 Akirah.3.0
Upgrade from 2.0 to 2.1
ANDROID1.6 Akirah.2.1
ANDROID1.6 Akirah.2.0
Click to expand...
Click to collapse
Themes
Blackened by jonnybueno
Chimera by d750
Minus theme by david1171 for v.2x
Blur theme by Brandenk - for v2.x
Click to expand...
Click to collapse
Theme template by david1171
Click to expand...
Click to collapse
Thank you for reposting, it was locked to me too! flashing later today...
I might try this later, seems okay
akirah said:
What it requires:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is the sdcard partition really required or is it only required if one wishes to use the A2SD?
And does the Cyanogenized 1.4 Recovery image count here?
I have a feeling they are going to lock this one too, probably because the Google Apps are included.
So they should close all HERO and Rogers and almost all others.
If they lock this one, then someone high up at xda needs to write a clear policy about what is and isn't allowed on this site, Rom-wise. At the moment I'm sure its individal mods acting alone, each with differing interpretations of what the current site policy is.
If this Rom gets grief, I assume the same standards will apply to Hero roms? Have they closed down the theme boards yet? The problem is (in my view) is that there are far too many mods with itchy trigger fingers (see the raspberry link at the bottom of the first post in my BetterBrowser thread in my sig for a prime example)
Cyanogen is the subject of a cease and desist. Akirah isn't, neither is xda as a site. As long as the files are offsite thus ensuring xda isn't liable, why are different standards being applied here versus the WinMo boards?
have flashed and have no complaints, it zoom zoom super fast!!, everything seems to work have just installed advanced launcher.
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
akirah said:
Installation
HTML:
Backup
Wipe
erase dalvik-cache
You might need to format your linux partition
Click to expand...
Click to collapse
Where is the step in which you actually flash?
Downloaded before google SHUTS YOU DOWN SON
pinetreehater said:
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
Click to expand...
Click to collapse
same exact results here..
sstang2006 said:
same exact results here..
Click to expand...
Click to collapse
Try moving app app-private to some folder on /system/sd
and see if it helps
also blankscreen after trying update from 4.1.1.1
can i see some screen shot of this? D;
tnx!
pinetreehater said:
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
Click to expand...
Click to collapse
Use the latest drivers from the 1.6 SDK, works fine for me on win7.
makethetick said:
Use the latest drivers from the 1.6 SDK, works fine for me on win7.
Click to expand...
Click to collapse
Same results here. Using Win7 x64 and it's worked perfect from day 1, but I started with the updated drivers.
Don't hate Google just yet
kreat1ve said:
Downloaded before Google SHUTS YOU DOWN SON
Click to expand...
Click to collapse
I'm not sure, but I think, the reason Cyanogen received a C&D is because he has an application on the android market that is open to the public that distributes Google copyright applications exclusive to those only on Google experience phones such as the G1. This website is for developers, and it sucks that this website has become more of a popularity contest than what it is meant to do, which Google promotes, the developing part of it. Being that Android is for everyone and can be accessed from non-Google experience phones, that is why he was ordered to stop before legal action is taken. If they were smart, they would have waited until Cyanogen became rich and then sued him for millions for copyright infringement, HOWEVER, they do believe in open-source projects such as Android. Google sells there brand in different packages, if you want the Google brand it will cost you more. They want to take down Microsoft down as much as all of us do. So I wouldn't hate them just yet, they still believe in something good.
Yes this is off-topic, felt i should actually post on an off topic post already. thnx
I adb pulled system/sd/*
then formatted ext, wiped and flashed rom no problems.
I then used adb file explorer to bulk install app-private and app back to phone.
from previous thread it seemd people had the black screen when trying to update straight from 4.1.11.1 so decided formatting ext is best bet
+1 for black screen. Wipe and delete dalvik-cache.
D/dalvikvm( 2520): GC freed 8907 objects / 492664 bytes in 142ms
E/System ( 2520): Failure starting core service
E/System ( 2520): java.lang.NullPointerException
E/System ( 2520): at com.android.server.PackageManagerService.scanPackageL
I(PackageManagerService.java:1875)
E/System ( 2520): at com.android.server.PackageManagerService.scanDirLI(Pa
ckageManagerService.java:1771)
E/System ( 2520): at com.android.server.PackageManagerService.<init>(Packa
geManagerService.java:497)
E/System ( 2520): at com.android.server.PackageManagerService.main(Package
ManagerService.java:266)
E/System ( 2520): at com.android.server.ServerThread.run(SystemServer.java
:112)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting Status Bar Service.
E/SystemServer( 2520): Failure starting StatusBarService
E/SystemServer( 2520): java.lang.NullPointerException
E/SystemServer( 2520): at com.android.server.status.StatusBarIcon.getIcon(Statu
sBarIcon.java:143)
E/SystemServer( 2520): at com.android.server.status.StatusBarIcon.<init>(Status
BarIcon.java:65)
E/SystemServer( 2520): at com.android.server.status.StatusBarService.makeStatus
BarView(StatusBarService.java:306)
E/SystemServer( 2520): at com.android.server.status.StatusBarService.<init>(Sta
tusBarService.java:237)
E/SystemServer( 2520): at com.android.server.ServerThread.run(SystemServer.java
:194)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting Clipboard Service.
I/SystemServer( 2520): Starting Input Method Service.
E/SystemServer( 2520): Failure starting Input Manager Service
E/SystemServer( 2520): java.lang.NullPointerException
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiverIntern
al(ApplicationContext.java:782)
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiver(Appli
cationContext.java:757)
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiver(Appli
cationContext.java:751)
E/SystemServer( 2520): at com.android.server.InputMethodManagerService.<init>(I
nputMethodManagerService.java:437)
E/SystemServer( 2520): at com.android.server.ServerThread.run(SystemServer.java
:209)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting NetStat Service.
I/SystemServer( 2520): Starting Connectivity Service.
W/dalvikvm( 2520): threadid=25: thread exiting with uncaught exception (group=0x
4001da68)
E/AndroidRuntime( 2520): Uncaught handler: thread ConnectivityThread exiting due
to uncaught exception
E/AndroidRuntime( 2520): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 2520): java.lang.NullPointerException
E/AndroidRuntime( 2520): at android.app.ActivityThread.getProvider(Activi
tyThread.java:3938)
E/AndroidRuntime( 2520): at android.app.ActivityThread.acquireProvider(Ac
tivityThread.java:3967)
E/AndroidRuntime( 2520): at android.app.ApplicationContext$ApplicationCon
tentResolver.acquireProvider(ApplicationContext.java:1514)
E/AndroidRuntime( 2520): at android.content.ContentResolver.acquireProvid
er(ContentResolver.java:579)
E/AndroidRuntime( 2520): at android.content.ContentResolver.query(Content
Resolver.java:147)
E/AndroidRuntime( 2520): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:472)
E/AndroidRuntime( 2520): at android.provider.Settings$Secure.getString(Se
ttings.java:1649)
E/AndroidRuntime( 2520): at android.provider.Settings$Secure.getInt(Setti
ngs.java:1689)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.getPer
sistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:123)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:47)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:87)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/Process ( 2520): Sending signal. PID: 2520 SIG: 9
I/Zygote ( 2519): Exit zygote because system server (2520) has terminated
E/installd( 2361): eof
E/installd( 2361): failed to read size
I/installd( 2361): closing connection
I/ServiceManager( 2354): service 'batteryinfo' died
I/ServiceManager( 2354): service 'usagestats' died
I/ServiceManager( 2354): service 'telephony.registry' died
I/ServiceManager( 2354): service 'SurfaceFlinger' died
I/ServiceManager( 2354): service 'entropy' died
I/ServiceManager( 2354): service 'power' died
I/ServiceManager( 2354): service 'clipboard' died
I/ServiceManager( 2354): service 'netstat' died
D/AndroidRuntime( 2534):
D/AndroidRuntime( 2534): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 2534): CheckJNI is OFF
D/AndroidRuntime( 2534): --- registering native functions ---
I/Zygote ( 2534): Preloading classes...
D/dalvikvm( 2534): GC freed 800 objects / 44048 bytes in 7ms
D/dalvikvm( 2534): GC freed 240 objects / 13920 bytes in 6ms
D/dalvikvm( 2534): GC freed 228 objects / 14392 bytes in 7ms
Click to expand...
Click to collapse
Thanks.
BR.
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.
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.
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.
I port a bliss pop custom rom from MT6735 to MT6735m.After flashing the ROM,i got Bootloop then i take logcat. i got these error but i dont know how i can fix these error.Can anyone hekp me to fix the errors. E/agps ( 265): [agps] ERR: [CP] band_num is not ready E/MediaPlayerFactory(21174): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(21174): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found I/ServiceManager(21622): Waiting for batterystats. service I/ServiceManager( 231): service 'media.audio_flinger' died thanks in advance..