Database Info

[Answered] Troubleshooting SD card issue with adb logcat

I am trying to troubleshoot an issue I am having with SD cards on my HTC Evo 4G.
I'm trying to reproduce the issue while monitoring logcat filtering with grep for the following strings: mnt card /dev storage
What should I be grepping for while troubleshooting the SD card?
Thanks in advance!

I've just reproduced the issue, but I did not see any error indicating what went wrong.
To reproduce, I installed a couple of apps from Amazon Appstore, moved them to the SD card, and rebooted. During the boot up, I saw the SD card go through all of the phases to get mounted and scanned, but none of the typical permissions messages from SD apps were being displayed indicating that the issue had reoccurred.
Still, I must not be grepping for the right term, because no error messages were displayed. I can try again without the grep, but it will be a lot more difficult to find the information in the loads of unrelated log messages.
Again, any ideas on what I should be grepping (filtering) for in the logcat output?
10 minutes later, and I am still unable to run any apps that are on the SD card, and I am unable to unmount the SD card from the settings menu. I get the following exception when trying to unmount:
Code:
E/ActivityManager( 108): Error running process
E/ActivityManager( 108): java.io.IOException: Error running exec(). Command: [/system/xbin/procrank] Working Directory: null Environment: [ANDROID_SOCKET_zygote=11, ANDROID_BOOTLOGO=1, EXTERNAL_STORAGE=/mnt/sdcard, ANDROID_ASSETS=/system/app, ASEC_MOUNTPOINT=/mnt/asec, PATH=/sbin:/system/sbin:/system/bin:/system/xbin, ANDROID_DATA=/data, BOOTCLASSPATH=/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar, ANDROID_PROPERTY_WORKSPACE=10,65536, ANDROID_ROOT=/system, LD_LIBRARY_PATH=/system/lib]
E/ActivityManager( 108): at java.lang.ProcessManager.exec(ProcessManager.java:226)
E/ActivityManager( 108): at java.lang.ProcessBuilder.start(ProcessBuilder.java:201)
E/ActivityManager( 108): at com.android.server.am.ActivityManagerService.logProcessResult(ActivityManagerService.java:9437)
E/ActivityManager( 108): at com.android.server.am.ActivityManagerService.access$900(ActivityManagerService.java:155)
E/ActivityManager( 108): at com.android.server.am.ActivityManagerService$9.run(ActivityManagerService.java:9614)
E/ActivityManager( 108): Caused by: java.io.IOException: No such file or directory
E/ActivityManager( 108): at java.lang.ProcessManager.exec(Native Method)
E/ActivityManager( 108): at java.lang.ProcessManager.exec(ProcessManager.java:224)
E/ActivityManager( 108): ... 4 more

I think I solved my SD card issue. I decided to just capture the full verbose log and then analyze it in Notepad++. Eventually I found that I should have been filtering for 'Vold' as this appears to be the volume manager daemon.
Here is a log with a filter for 'Vold' after reproducing the problem:
Code:
I/Vold ( 59): Vold 2.1 (the revenge) firing up
D/Vold ( 59): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 59): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 59): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/VoldCmdListener( 59): volume list
D/VoldCmdListener( 59): share status ums
D/VoldCmdListener( 59): share status ums
D/VoldCmdListener( 59): volume mount /mnt/sdcard
I/Vold ( 59): /dev/block/vold/179:1 being considered for volume sdcard
D/Vold ( 59): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)
W/Vold ( 59): Skipping fs checks
I/Vold ( 59): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging
D/Vold ( 59): Volume sdcard state changing 3 (Checking) -> 4 (Mounted)
D/VoldCmdListener( 59): asec list
W/VoldConnector( 108): Bad msg (alRecorder-1)
What should normally come after the "D/VoldCmdListener( 59): asec list" line is a listing of all the asec files for the apps that have been moved to the SD card.
I found that "alRecorder-1" was actually just a truncated name for the Virtual Recorder app. I put the SD card into my computer slot, deleted the ix.com.android.VirtualRecorder-1.asec file from .android_secure, and then the phone would boot up fine with all of the remaining SD card apps available and operational.
I could then reproduce the problem by installing some more apps to the SD card. I checked the log again, and this time it was a different app triggering the "W/VoldConnector( 108): Bad msg (...)" message. Hmmm...
I also noticed that the SD card's filesystem was not being checked ("W/Vold ( 59): Skipping fs checks"). That prompted me to again insert the card into my PC's reader slot, and then I ran a check disk against the volume including a scan and recovery attempt for bad sectors.
Lo' and behold! It found and fixed a problem - even recovering a file - and it seems I am back to normal now! After nearly a week of troubleshooting, it all makes sense that this was caused by a bad sector, as the card would work fine until I hit those bad sectors for a write operation and then FAIL.
I hope this information will help someone else in the future.

I eventually found out that my problem was due to Froyo's 123 app on SD card limit. I just got the Gingerbread update for my Evo last night, and now the issue is gone. Glorious!
Sent from my PC36100 using XDA Premium App

who wants a sony arc rom ???

Im starting to port the sony ericsson arc rom to our desire s and i just wanted to know who would be intrested in my rom ????? let me know what u think of the sony ericsson arc and what new things you would like to see in this port. like timescape and other things. its going to be good porting and i hope your all intrested and i aint doing this for nothing lol

paul.robo said:
Im starting to port the sony ericsson arc rom to our desire s and i just wanted to know who would be intrested in my rom ????? let me know what u think of the sony ericsson arc and what new things you would like to see in this port. like timescape and other things. its going to be good porting and i hope your all intrested and i aint doing this for nothing lol
Click to expand...
Click to collapse
Yup. More choice is always a good thing!!
I vote for a port. Do your thing!

LOG CAT
Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Users\paul\Desktop\DOWNGRADE.SAGA.AND.GUIDE
C:\Users\paul\Desktop\DOWNGRADE.SAGA.AND.GUIDE>adb logcat
* daemon not running. starting it now *
* daemon started successfully *
--------- beginning of /dev/log/main
I/DEBUG ( 1175): debuggerd: Nov 29 2011 12:52:30
--------- beginning of /dev/log/system
I/Vold ( 1173): Vold 2.1 (the revenge) firing up
D/AK8975 ( 1182): AK8975 daemon 1.0.8 Start
D/AK8975 ( 1182): (Library version : 1.2.1.1125)
I/rmt_storage( 1183): rmt_storage user app start
I/rmt_storage( 1183): rmt_storage open success
I/rmt_storage( 1183): rmt_storage shared memory ioctl success
I/rmt_storage( 1183): rmt_storage mmap addr = 40009000
D/Vold ( 1173): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1173): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1173): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted
)
THIS SHOWS ERRORS SO NOW IM GOING TO CHANGE MY APPROACH AND GET A DIFF SONY ROM AND FROM THE X10 NOW THAT WAS FROM ARC S WHICH IS GOING TO BE MUCH MUCH HARDER SO ILL STICK WITH THE X10 FOR NOW.

[Q] Device encryption not starting

Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
I/MountService( 872): encrypting storage...
I/power ( 872): *** release_dvfs_lock : lockType : 1
D/SSRMv2:CustomFrequencyManagerService( 872): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1188000 uid : 1000 pid : 872 tag : [email protected]
D/lights ( 872): button : 0 +
D/lights ( 872): button : 0 -
D/qdutils ( 321): getuiClearRegion:70 wormRect( l = 0 t = 0 r = 720 b = 50)
D/qdutils ( 321): getuiClearRegion:76 FinalwormRect( l = 0 t = 0 r = 720 b = 50)
E/SMD ( 346): DCD ON
I/SecureStorage(12345): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(12345): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
E/SecureStorage(12345): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(12345): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(12345): [ERROR]:Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Any ideas?

ccoager said:
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
Any ideas?
Click to expand...
Click to collapse
My recommendation? DON'T DO ENCRYPTION!! you may get your phone in a lockmode and unable to recover data..

Is there anything else that could be causing this?
I have not chosen device encryption and I am also seeing these messages in logcat..
I/SecureStorage(15360): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(15360): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_stor.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
E/SecureStorage(15360): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(15360): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(15360): [ERROR]:Error cannot connect to TA/driver!
E/SMD ( 213): DCD ON

Same Problem
I am getting the same thing and when I rooted my SCH-r530u I disabled the Knox thing
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon is preparing to run
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon successfully binded a socket
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_stor.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_storage.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Loading app sec_stor and sec_storage failed
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Fail to open session with qualcomm
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Error cannot connect to TA/driver!
02-20 22:57:12.161: V/AlarmManager(411): waitForAlarm result :8
Click to expand...
Click to collapse
What does it mean? I keep getting it every few seconds while the screen is on
* I was going to edit out the sad faces but its too funny cause it fits the situation perfectly*

[SOLVED][Q] WiFi won't turn on

All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.

I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.

_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.

[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!

lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.

CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.

I can't boot into my ROM, I keep running into dex problems.

I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
Code:
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/DEBUG ( 1389): tid 15467 does not exist in pid 15467. ignoring debug request
I/ServiceManager( 1385): service 'media.audio_flinger' died
I/ServiceManager( 1385): service 'media.player' died
I/ServiceManager( 1385): service 'media.camera' died
I/ServiceManager( 1385): service 'media.audio_policy' died
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/mediaserver(15513): ServiceManager: 0x2a00b448
I/AudioFlinger(15513): Using default 3000 mSec as standby time.
E/MediaPlayerFactory(15513): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15513): calling dlsym on pFactoryLib for FACTORY_CREATE_FN
E/MediaPlayerFactory(15513): registering DASH Player factory...
I/CameraService(15513): CameraService started (pid=15513)
I/CameraService(15513): Loaded "BCM21553 Camera HAL" camera module
D/BcmCamera(15513): HAL_get_number_of_cameras: numCameras:1
I/AudioPolicyManagerBase(15513): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/AudioFlinger(15513): loadHwModule() Loaded primary audio interface from Samsung BCM21553 audio HW HAL (audio) handle 1
I/AudioFlinger(15513): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(15513): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger(15513): Using module 1 has the primary audio interface
D/AudioPolicyManagerBase(15513): setOutputDevice() changing device from (2) to (2) force (1) delayMs (0) on Output (2)
I/AudioFlinger(15513): AudioFlinger's thread 0x40f53008 ready to run
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
D/audio_hw_primary(15513): call=n, earpiece=n hp=n speaker=y sco=n a2dp=n out_device=2
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
I/audio_a2dp_hw(15513): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(15513): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(15513): loadHwModule() Loaded usb audio interface from USB audio HW HAL (audio) handle 4
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger(15513): no wake lock to update!
I/r_submix(15513): adev_open(name=audio_hw_if)
I/r_submix(15513): adev_init_check()
I/AudioFlinger(15513): loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 5
I/AudioPolicyService(15513): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/AndroidRuntime(15512):
D/AndroidRuntime(15512): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(15512): CheckJNI is OFF
D/dalvikvm(15512): Unable to stat classpath element '/system/framework/core.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm(15512): DexOpt: --- BEGIN 'conscrypt.jar' (bootstrap=1) ---
E/dalvikvm(15640): Fatal error: java/lang/Object
E/dalvikvm(15640): VM aborting
F/libc (15640): Fatal signal 6 (SIGABRT) at 0x00003d18 (code=-6), thread 15640 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
I/DEBUG ( 1389): Revision: '0'
I/DEBUG ( 1389): pid: 15640, tid: 15640, name: dexopt >>> /system/bin/dexopt <<<
[A bunch of seemingly random (at least for such a noob like me) numbers]
W/dalvikvm(15512): DexOpt: --- END 'conscrypt.jar' --- status=0x0006, process failed
E/dalvikvm(15512): Unable to extract+optimize DEX from '/system/framework/conscrypt.jar'
D/dalvikvm(15512): Unable to process classpath element '/system/framework/conscrypt.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/dalvikvm(15512): DexOpt: --- BEGIN 'okhttp.jar' (bootstrap=1) ---
E/dalvikvm(15692): Fatal error: java/lang/Object
E/dalvikvm(15692): VM aborting
F/libc (15692): Fatal signal 6 (SIGABRT) at 0x00003d4c (code=-6), thread 15692 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?

knuxfanwin8 said:
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
Click to expand...
Click to collapse
Yeah. You need to Deodex both ROM BASE and PORT BEFORE you build. That is the reason you keep getting dex errors. Use ASSAYYED Kitchen or @superR's Kitchen or similar to accomplish this ?