Hi all,
I work in a cell phone chipset company and I was trying to run CM10.1 on our device.
It looks like the kernel is working and adb is working as well.
But it just can't boot into idle screen. Attachment is the logcat.
Looks like dalvik thing or lot more other things...
Hoping someone give us a hand and provide some clues or hints. Thanks in advance!!
========================================================================
After check the permisson, logs look better but still stuck. Thanks to Kangie.
Any further ideas?
I'm not a CM Porting expert, but looking at the log it does seem to be choking when trying to initialise the dalvik cache.
I'd start with checking the perms on /cache/dalvik-cache.
01-04 18:54:05.310 E/dalvikvm( 824): Could not stat dex cache directory '/cache/dalvik-cache': Permission denied
01-04 18:54:05.310 I/dalvikvm( 824): Unable to open or create cache for /system/framework/core.jar (/cache/dalvik-cache/[email protected]@[email protected])
...
01-04 18:54:05.310 E/dalvikvm( 824): VM aborting
01-04 18:54:05.310 F/libc ( 824): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1), thread 824 (dexopt)
Anyway - Looks mostly like a perms issue. Check that, go from there.
Kangie said:
I'm not a CM Porting expert, but looking at the log it does seem to be choking when trying to initialise the dalvik cache.
I'd start with checking the perms on /cache/dalvik-cache.
Anyway - Looks mostly like a perms issue. Check that, go from there.
Click to expand...
Click to collapse
hi Kangie,
Thanks!! The log seems different when I modified the permissions.
And now the log is attached again. this is logcat_v2.
Any help woul;d be much appreciated~~:good:
On second thoughts: It does look like Vold (Volume Daemon) is crashing then..
01-06 17:49:22.140 W/MountService( 713): Thread android.server.ServerThread still waiting for MountService ready...
This happens over and over. My guess is that the android boot is being held up by this - It just keeps waiting for something that never happens. That's a good starting point. I'm not sure where to go from there and don't have a device - Back over to you for observations.
Related
Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
EDIT: maybe it was related to Maps since I installed maps 7.x I don't see that process anymore!
moly82 said:
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
Click to expand...
Click to collapse
Maybe you have some program/app installed which uses the download manager? Some app trying to download an update outside of the regular mechanism? I don't see DownloadService running on my phone unless I instructed it to download something. Do you notice anything downloadmanager/media related in logcat? If in doubt, attach the phone to a PC, run the following commands and attach the resulting file ('attach_me.txt') here:
Code:
adb shell 'ps; echo -----------;logcat -v time -b main -b system -b events -d;echo -----------;dumpsys;' > attach_me.txt
Use the full path to adb if you need to.
This shows the currently running processes (ps), the contents of the main, system and event logs (logcat) and a snapshot of the current state of your phone (dumpsys). If there is anything there you don't want to show to the whole world edit the resulting file before attaching it here.
thanks a lot for the reply my friend
tonight at home I think I will be able to run the adb command you suggested me (in my home computer I have sdk installed)
so far I checked logcat in terminal ("logcat |grep edia" and "logcat |grep ownload") and this is what I got:
$ su
# logcat |grep edia
D/Vold ( 1197): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1197): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageParser( 1626): No actions in intent filter at /data/app/org.wikipedia-1.apk Binary XML file line #39
I/ActivityManager( 1626): Start proc android.process.media for broadcast com.android.providers.media/.MtpReceiver: pid=1765 uid=10011 gids={50011, 1015, 1023, 1024, 1028, 2001, 3003, 3007}
V/ActivityThread( 1765): android.process.media white listed for hwui
D/SystemUIService( 1701): loading: class com.android.systemui.media.RingtonePlayer
D/SystemUIService( 1701): running: [email protected]
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothHeadset.:273 android.bluetooth.BluetoothAdapter.getProfileProxy:1155 android.media.AudioService.getBluetoothHeadset:2198 android.media.AudioService.access$2800:104
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothA2dp.:160 android.bluetooth.BluetoothAdapter.getProfileProxy:1158 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4087 android.app.LoadedApk$ReceiverDispatcher$Args.run:758
$ su
# logcat|grep ownload
I/ActivityManager( 1624): Start proc com.google.android.youtube for broadcast com.google.android.youtube/.core.transfer.DownloadService$BootReceiver: pid=2305 uid=10050 gids={50050, 3003, 1015, 1006, 1028}
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
I'm attaching also screenshots of the process I'm talking about
EDIT: I reinstalled everyting from scratch as a new build by quarx came out.. it seems that installing only cm build + minimal gapps, that process doesn't show up. Later after I installed back all my apps (via app2zip flashable zip) the process showed up again.. so probably you are right and there is a certain app using that process.. but how can I understand which one has relation with that service? maybe YouTube as i see it mentioned in logcat?
delete
i could generate the logs you asked without using the pc but using the phone terminal and multiple commands.. i'm uploading them to my dropbox links are below thanks in advance..
http://db.tt/gJLBYeT7
http://db.tt/OahQ8Zf7
http://db.tt/KPUTy4et
YAFU what happened to you?
it seems to me after I installed latest maps 7.x the media > download process is not appearing anymore in running processes.. maybe it was related to sh*tty maps??? :fingers-crossed:
Hello, currently, one of our Galaxy 4.0 Players is stuck in a boot loop. I have been searching this site and a few others for over a month now for solutions and am stumped.
I have tried flashing several different US YP-G1 stock ROMs using both Heimdall and Odin, Terrasilent kernel, Steve's kernel, Icyfusion ROM, factory reset, wiping cache/dalvik.
Over a month ago, the device started randomly rebooting and showing the first time startup screen each time it rebooted like this. When it would have a random reboot however, it would get stuck in a boot loop and have to be restarted by holding the power button or pulling battery. Then after a couple weeks of that, it has since been stuck in a boot loop.
Interesting "dmesg" information that may or may not have anything to do with this are:
7.347889] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.352046] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
7.362574] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.368081] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
8.585066] mmc0: error -110 whilst initialising MMC card
8.655510] mmc1: new high speed SDHC card at address b368
I believe that the internal sdcard has died and have formatted the external one with the vfat and rfs partitions to act as the internal sdcard. But according to dmesg, it appears that perhaps mmcblk0p2 is trying to be mounted in the boot procedure before MMC1 is detected?
Any help is greatly appreciated and I will provide any more information as needed.
-Tony
"FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread"
update
Between flashing the international verions's bootloader, reflashing recovery rom, Terrasilent kernel and restoring a Nandroid backup from our other YP-G1, the mounting problems seem to be gone now.
However, there is still a bootloop problem which I believe has something to do with these logcat entries:
D/NativeDaemonConnector( 246): NativeDaemonConnector ::
D/NetdConnector( 246): run ::
D/NetdConnector( 246): listenToSocket ::
I/SystemServer( 246): Connectivity Service
W/dalvikvm( 246): threadid=17: thread exiting with uncaught exception (group=0x
40015578)
E/ ( 246): Dumpstate > /data/log/dumpstate_sys_error
V/ConnectivityService( 246): ConnectivityService starting up
E/ActivityThread( 246): Failed to find provider info for settings
E/AndroidRuntime( 246): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 246): java.lang.NullPointerException
E/AndroidRuntime( 246): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:664)
E/AndroidRuntime( 246): at android.provider.Settings$Secure.getString(Se
ttings.java:2209)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:264)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:61)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:229)
I/dumpstate( 277): begin
E/dumpstate( 277): Cannot get free space size. So, skip dumpstate.
When the problems first started before all the flashing, logcat also showed this fatal exception in ConnectivityThread
Hello everyone
I've managed to unlock and root my SGP312 (pollux_windy). Because I always liked AOKP, I tried to install this custom ROM. Here's what I did:
1) Flashed Little Kernel into /boot while in Sony's Fastboot Mode
2) Flashed extracted boot.img of AOKP into "boot" and newest TWRP recovery (v2.6.3) into "recovery" while in LK's Fastboot Mode
3) Rebooted into TWRP recovery, wiped data, cache and dalvik cache
4) Flashed newest AOKP version (jb-mr2 milestone #1 for pollux_windy)
5) Flashed gapps (gapps-jb-20130813-signed.zip)
And tada, the custom ROM booted and everything was fine... No force closes / crashes, no problems, everything worked like a charm.. except the god damn Play Store! Whenever I open the Play Store, it only says "No connection". Pressing retry doesn't help at all. Ofcourse I always search through some forums before posting an issue, so here's what I've already tried:
- Other custom ROM (CM 10.2 stable for pollux_windy)
- Other gapps package (pa_gapps-full-4.3-20131102-signed.zip)
- Force Google Play Store and Google Play Services to stop and delete their data
- Wiped cache and dalvik cache
- Tried a connection without native IPv6 (WLAN hotspot of my HTC One, going over mobile internet which is clearly IPv4 only)
- Checked /etc/hosts (only contains 127.0.0.1 localhost)
- Executed Shark for Root -> There is clearly some data activity going on, my tablet seems to send some data to the google servers but they return an empty response as it seems (see logcat down below)? Unfortunately I am not able to analyze the packets, thanks to SSL/HTTPS...
- Changed some build.prop settings to match an original installation (model=SGP312, device=SGP312 and so on...)
And none of these methods worked. I am totally clueless what else I could try? Here's a logcat snippet:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
My build.prop is now reverted to the original AOKP build.prop, which can be found here: dl.snapserv.net/build.prop.txt (Sorry, I am not allowed to post links yet...) Have you guys any idea? XDA is basically my last hope, otherwise it seems like I am doomed to use the stock ROM :/ Or did I do something wrong?
Thanks for reading and have a nice day!
Regards
NeoXiD
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
[/QUOTE]
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
bondcheg said:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. (How I found that problem? I just went so far that I've intercepted the traffic to the google servers with a fake root certificate and Fiddler...) Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
NeoXiD said:
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD[/QUOTE]
I`m novice user and never conneced my device with adb and dont know how to do it.
bondcheg said:
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
I`m novice user and never conneced my device with adb and dont know how to do it.
Click to expand...
Click to collapse
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
bondcheg said:
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
Click to expand...
Click to collapse
That might be the fault then, because it might get interpreted as serial number '0', which might get rejected by Google. Did you flash any custom bootloader? Normally this should not occur... You can also drop me a PM so we do not spam this thread with a 4-eye-conversation.
Regards
NeoXiD
Hello all
I am having some trouble with SDK installing apps to my Android. I've tried to find many forums about my issue, but I've hit a brick wall every time. My rooted device is an LG Optimus C running Android 2.2 (ancient lol). My issue is that I'm getting the error: Failure [INSTALL_FAILED_DEXOPT] for every app I try to install. I've wiped the device twice and then found out that this error happens every time after I've installed a good amount of apps...which I read somewhere that this will happen because of not having enough space in Dalvik..or in the data area and won't allow the install to write anything else..correct me if I'm wrong on this I've also cleared all caches multiple times, including Dalvik.
I've also tried the work around where you try and skip that all together and put the app straight into /system /app. That came up with no resolution, even with the correct properties selected (read/write/execute etc). So now, I really have no other avenues left but to come here and ask.
Here is the Logcat results I get using adb install -r app.apk no matter what app it is. I will use tumblog.apk (compatible with device) for this example:
D/AndroidRuntime( 4201):
D/AndroidRuntime( 4201): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
I/AndroidRuntime( 4201): Heap size: -Xmx32m
D/AndroidRuntime( 4201): CheckJNI is OFF
D/AndroidRuntime( 4201): Calling main entry com.android.commands.pm.Pm
W/ActivityManager( 1356): No content provider found for:
W/ActivityManager( 1356): No content provider found for:
D/PackageParser( 1356): Scanning package: /data/app/vmdl-166230949.tmp
D/PackageManager( 1356): Scanning package com.luckydroid.tumblelog
E/PackageManager( 1356): Package com.luckydroid.tumblelog has mismatched uid: 10
060 on disk, 10061 in settings
I/PackageManager( 1356): Linking native library dir for /data/app/com.luckydroid
.tumblelog-1.apk
D/installd( 1256): DexInv: --- BEGIN '/data/app/com.luckydroid.tumblelog-1.apk'
---
D/dalvikvm( 4211): Zip inflate: partial write (will retry): (24536 of 32768)
E/dalvikvm( 4211): Zip inflate: write failed: No space left on device
W/dalvikvm( 4211): DexOptZ: extraction of classes.dex from /data/app/com.luckydr
oid.tumblelog-1.apk failed
W/installd( 1256): DexInv: --- END '/data/app/com.luckydroid.tumblelog-1.apk' --
- status=0xff00, process failed
E/installd( 1256): dexopt failed on '/data/dalvik-cache/[email protected]@com.luckydroid.
[email protected]' res = 65280
W/PackageManager( 1356): Package couldn't be installed in /data/app/com.luckydro
id.tumblelog-1.apk
D/AndroidRuntime( 4201): Shutting down VM
I/AndroidRuntime( 4201): NOTE: attach of thread 'Binder Thread #3' failed
D/jdwp ( 4201): adbd disconnected
I really have no clue what any of this means lol...pretty new to logcat. I am aware of the file name not matching the original name of the apk..shouldn't matter considering I've installed many apps with shortened names. Any help would be greatly appreciated! Thanks
EDIT: Looks like "E/dalvikvm( 4211): Zip inflate: write failed: No space left on device" is the problem. Not enough space in Dalvik. Still have no idea how to work around.
Bump
Is this not posted in the correct forum? I'm just guessing no one knows of a solution?
Çözüme Yakın
Sizin sorununuz apk~classes.dex~.smali dosyalarının içinde gereksiz kodları siliniz. "Ayrıca Facebook klasörünü bulup siliniz (her clasess.dex'te bulunmaz)" ayrıca kimi classes.dex boyutu 9MB iken yükleniyor bazı clasess.dex dosyaları ise 7,8*MB olunca yüklenmiyor. Tabikide kodlar içinde dexOpt= dex options ayarı vardır ama ben bulamadım sadece bunları biliyorum. Umarım çözüm bulan çıkar. TR