Develop Bugs

Little game: Guess the failed experiment...

I had some time to spare this afternoon and decided to try a little something.
Which, due to the lilliputian amounts of space available on this device, I'm afraid will never go any further.
I'll leave a logcat below to see if some of you can guess what that experiment was, shouldn't be too hard.
I'll post the answer sometime soon.
Darkshado
Code:
--------- beginning of /dev/log/main
D/dalvikvm( 4679): VFY: dead code 0x0026-002d in Lcom/android/server/am/ActivityManagerService;.saveSkinLocked (Ljava/lang/String;Z)V
I/dalvikvm( 4679): Could not find method com.htc.util.skin.HtcSkinUtil.getSkinVersionCode, referenced from method com.android.server.PackageManagerService.checkSkinAfterFota
W/dalvikvm( 4679): VFY: unable to resolve static method 8094: Lcom/htc/util/skin/HtcSkinUtil;.getSkinVersionCode ()I
D/dalvikvm( 4679): VFY: replacing opcode 0x71 at 0x000b
I/dalvikvm( 4679): Could not find method com.htc.util.skin.HtcSkinUtil.getSkinVersionCode, referenced from method com.android.server.PackageManagerService.checkSkinAfterFota
W/dalvikvm( 4679): VFY: unable to resolve static method 8094: Lcom/htc/util/skin/HtcSkinUtil;.getSkinVersionCode ()I
D/dalvikvm( 4679): VFY: replacing opcode 0x71 at 0x001c
D/dalvikvm( 4679): VFY: dead code 0x000e-0019 in Lcom/android/server/PackageManagerService;.checkSkinAfterFota ()V
D/dalvikvm( 4679): VFY: dead code 0x001f-002e in Lcom/android/server/PackageManagerService;.checkSkinAfterFota ()V
I/installd( 113): new connection
D/dalvikvm( 4679): GC_CONCURRENT freed 185K, 9% free 2278K/2503K, external 0K/0K, paused 3ms+3ms
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
D/szipinf ( 4679): Initializing inflate state
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
D/szipinf ( 4679): Initializing inflate state
W/ResourceType( 4679): Failure getting entry for 0x7f020006 (t=1 e=6) in package 0 (error -75)
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
W/ResourceType( 4679): Failure getting entry for 0x7f020010 (t=1 e=16) in package 0 (error -75)
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
D/szipinf ( 4679): Initializing inflate state
W/PackageParser( 4679): Unknown element under <manifest>: support-screens at /system/app/com.htc.ringtonetrimmer.apk Binary XML file line #19
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
W/PackageParser( 4679): Unknown element under <application>: intent-filter at /system/app/com.htc.MusicWidget.apk Binary XML file line #9
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
D/szipinf ( 4679): Initializing inflate state
W/PackageParser( 4679): Unknown element under <application>: intent-filter at /system/app/com.htc.FriendStreamWidget.apk Binary XML file line #7
I/keystore( 114): uid: 1000 action: g -> 6 state: 3 -> 3 retry: 4
E/installd( 113): unsupported command 'unmount'
D/szipinf ( 4679): Initializing inflate state

I dunno man!
I can't read this poop lol
I'm guessing:
AOSP Rom?
A new A2SD?

Its htc sense
Can you give me link to sources then i can see howbto help
herpderp ©copy+paste

Can sense work in non-htc phone??
Sent from my GT-S5660 using XDA Premium App

Cool. Though this is weird. Just before this post I was thinking about how I could put HTC on my phone
Then I found this thread. lol

I quickly tried porting this Wildfire S custom ROM. Mixed in some stock Gio files, with the Phiexz stock ROM kernel.
http://forum.xda-developers.com/showthread.php?t=1503162
But the problem is that the thing is just too big for our /system partition.
As it stands I'm not going to push this any further.

Darkshado said:
But the problem is that the things is just too big for our /system partition.
As it stands I'm not going to push this any further.
Click to expand...
Click to collapse
Lol nice try though!

[Q] FC issues (sometimes reproducible) with all ROMs

Let me try to explain my FC issues.
I rooted my Desire Z around october last year and installed CM 7.1 which worked great. I rarely encountered any FCs and was quite happy with it.
Curious as I am I tried CM9 about 2 months ago but had some annoying FCs in various apps, which were not really reproducible. It seemed totally random to me.
I blamed CM9, since ICS was not officially released for the Desire Z.
After 2 weeks of happy FCing from my phone I performed a complete wipe and flashed Andromadus Audacity and still encountered several FCs in various apps.
Same with Virtuous ROM and any other ROM I tried.
Being tired of the issues I had, I went back to CM 7.1 about 2 weeks ago, remembering how well it performed.
And guess what, I still have a lot of FCs.
I can reproduce some of them now.
The fist time I start any audio app, like the standard music player, I get a
DSP FC. This is 100% reproducable, it will happen every time I rebooted and start a music player. But only once.
Rom Manager crashes immediately after a reboot. Every time.
I suspected that it had to do with having overclocked my phone and set it back to factory speed but it didn't help either.
The phone app keeps crashing when I initiate a call, not everytime but every now and then. This never happened when I used CM7 last time.
I wiped Dalvik cache, performed a full wipe, heck I even formatted my SD on my machine.
I just performed another full wipe a few minutes ago and flashed CM7.1 again. When I tried to download the google apps, the sync wizzard, which comes up on first boot, crashed during download of gmail app.
Ideas anyone? I'm short to throw this incooperative piece of engineering out of my window.
I use this phone for my workcalls and constant phone app crashes render the whole thing unusable.
baseband
12.28b.60.140eU_26.03.02.26_M
kernel
2.6.35.14-cyanogenmod-g9e5cdf1
[email protected]#1
Mod-Version
CyanogenMod-7.1.0-vision
build
GWK74

Hmmmm,..... V-odd!!!
Have you tried the superwipe before reflashing a new rom?

just a thought but when you were using ics did you format your system to ext4, now reverting back to gingerbread some roms will only work well with ext3. but I do belive cm7 works fine with ext4, I'm running elitemod cm7 based and am formated to ext4 but maybe the offical one has some issues with it. try a fastboot wipe, this is the cleanest, next best would be a superwipe. check the md5sums of the new rom your flashing. I am doubtfull this is hardware related
Sent from my HTC Vision using xda premium

Yes, I use ext4 FS but I'm sure I used it before ICS too and never had a problem with it.
Trying to perform a fastboot wipe and another reflash right now.
Stay tuned for results.

DaFunkShun said:
Yes, I use ext4 FS but I'm sure I used it before ICS too and never had a problem with it.
Trying to perform a fastboot wipe and another reflash right now.
Stay tuned for results.
Click to expand...
Click to collapse
Though some older roms if you try to go back to GB and such might not support the ext4 partitions (i.e.: normally you have to convert /data /cache etc after the fact with something like 4EXT Recovery), something to note. Also *some* newer ICS roms need the new radio as opposed to the old radio (note my signature as I used to have your radio).
I mean only other thing I can think of is possibly hardware failure like the ram or emmc.
What does your dmesg and logcat output look like after a few crashes? can you plug up your phone and use adb to get the output of both of those?

I can't check logcat now since I'm in the office at the moment.
I try to post the logs here when I'm back home.
fastboot wipe and superwipe didn't solve the issue.

I updated the baseband but I'm not sure if it really helped. The phone still crashes tho less than before.
Code:
07-23 17:59:27.439 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 181K, 47% free 3254K/6087K, external 508K/587K, paused 34ms
07-23 17:59:27.530 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 30K, 46% free 3299K/6087K, external 1153K/1164K, paused 30ms
07-23 17:59:27.590 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 15K, 46% free 3317K/6087K, external 1556K/1692K, paused 31ms
07-23 17:59:27.650 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 36K, 46% free 3298K/6087K, external 2200K/2236K, paused 34ms
07-23 17:59:27.650 W/ResourceType( 1496): getEntry failing because entryIndex 65 is beyond type entryCount 1
07-23 17:59:27.700 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 4K, 46% free 3308K/6087K, external 2753K/2804K, paused 28ms
07-23 17:59:27.800 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 3K, 46% free 3324K/6087K, external 3942K/3943K, paused 31ms
07-23 17:59:27.900 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 24K, 45% free 3397K/6087K, external 4815K/4950K, paused 25ms
07-23 17:59:27.940 I/AudioService( 1352): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
07-23 17:59:27.950 I/HeadsetService( 1798): After phone call off-hook: disable DSP.
07-23 17:59:27.960 D/AudioHardwareInterface( 1248): setMode(IN_CALL)
07-23 17:59:27.960 D/AudioFlinger( 1248): setParameters(): io 1, keyvalue routing=1, tid 1341, calling tid 1248
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): doRouting()
07-23 17:59:27.960 I/AudioHardwareMSM7X30( 1248): Routing audio to Handset
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): new_rx = 0
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): new_tx = 1
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): Starting voice on Rx 0 and Tx 1 device
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): updateACDB: (1, 0, 105, 205)
07-23 17:59:27.960 I/HTC Acoustic( 1248): update ACDB id: (tx, rx, tx_acdb, rx_acdb) = (1, 0, 105, 205)
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): value of device and enable is 6 0
07-23 17:59:27.960 D/AudioHardwareMSM7X30( 1248): value of device and enable is 0 1
07-23 17:59:27.960 D/AndroidRuntime( 1798): Shutting down VM
07-23 17:59:27.960 W/dalvikvm( 1798): threadid=1: thread exiting with uncaught exception (group=0x40015560)
07-23 17:59:28.000 E/AndroidRuntime( 1798): FATAL EXCEPTION: main
07-23 17:59:28.000 E/AndroidRuntime( 1798): java.lang.UnsupportedOperationException: AudioEffect: invalid parameter operation
07-23 17:59:28.000 E/AndroidRuntime( 1798): at android.media.audiofx.AudioEffect.checkStatus(AudioEffect.java:1205)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at android.media.audiofx.BassBoost.setStrength(BassBoost.java:133)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at com.bel.android.dspmanager.HeadsetService.updateDsp(HeadsetService.java:211)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at com.bel.android.dspmanager.HeadsetService$4.onCallStateChanged(HeadsetService.java:129)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at android.telephony.PhoneStateListener$2.handleMessage(PhoneStateListener.java:319)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at android.os.Handler.dispatchMessage(Handler.java:99)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at android.os.Looper.loop(Looper.java:130)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at android.app.ActivityThread.main(ActivityThread.java:3835)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at java.lang.reflect.Method.invokeNative(Native Method)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at java.lang.reflect.Method.invoke(Method.java:507)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:864)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:622)
07-23 17:59:28.000 E/AndroidRuntime( 1798): at dalvik.system.NativeStart.main(Native Method)
07-23 17:59:28.010 D/AudioHardwareMSM7X30( 1248): value of device and enable is 11 0
07-23 17:59:28.010 D/AudioHardwareMSM7X30( 1248): value of device and enable is 1 1
07-23 17:59:28.050 D/AudioHardwareMSM7X30( 1248): Starting voice call and UnMuting the call
07-23 17:59:28.050 D/AudioHardwareMSM7X30( 1248): addToTable (dec_id 0, dev_rx 0, dev_tx 1, type 4, active 1)
07-23 17:59:28.050 D/AudioHardwareMSM7X30( 1248): updateDeviceInfo: E rx_device 0 and tx_device 1
07-23 17:59:28.050 D/AudioHardwareMSM7X30( 1248): case VOICE_CALL
07-23 17:59:28.050 D/AudioHardwareMSM7X30( 1248): updateDeviceInfo: X cur_rx 0 cur_tx 1
07-23 17:59:28.050 D/AudioHardwareMSM7X30( 1248): setVoiceVolume(0.800000)
07-23 17:59:28.050 I/AudioHardwareMSM7X30( 1248): Setting in-call volume to 80 (available range is 0 to 100)
07-23 17:59:28.050 I/HTC Acoustic( 1248): update voice ACDB id: (tx_acdb, rx_acdb) = (0, 0)
07-23 17:59:28.060 I/HTC Acoustic( 1248): update voice ACDB id (0, 0) success
07-23 17:59:28.060 I/AudioHardwareMSM7X30( 1248): update_voice_acdb(0, 0) succeeded
07-23 17:59:28.460 W/BluetoothHeadset( 1496): Proxy not attached to service
07-23 17:59:28.481 W/BluetoothHeadset( 1496): Proxy not attached to service
07-23 17:59:28.491 I/power ( 1352): *** set_screen_state 1
07-23 17:59:28.551 D/AccelerometerListener( 1496): enable(true)
07-23 17:59:28.571 D/szipinf ( 1432): Initializing inflate state
07-23 17:59:28.571 I/ActivityManager( 1352): Start proc com.cyanogenmod.cmparts for broadcast com.cyanogenmod.cmparts/.intents.LEDNotificationReceiver: pid=2538 uid=1000 gids={3002, 3001, 3003, 1015}
07-23 17:59:28.581 D/AudioHardwareMSM7X30( 1248): setMicMute_nosync calling voice mute with the mMicMute 0
07-23 17:59:28.581 D/AudioHardwareMSM7X30( 1248): setMicMute_nosync:voice_mute
07-23 17:59:28.771 D/szipinf ( 2538): Initializing inflate state
07-23 17:59:28.791 I/ActivityManager( 1352): Displayed com.android.phone/.InCallScreen: +1s442ms (total +1s572ms)
07-23 17:59:28.851 D/szipinf ( 2538): Initializing inflate state
07-23 17:59:28.861 I/ActivityThread( 2538): Pub com.cyanogenmod.cmparts.provider.Settings: com.cyanogenmod.cmparts.provider.SettingsProvider
07-23 17:59:28.901 I/ActivityManager( 1352): No longer want com.cyanogenmod.android.fotakill (pid 2316): hidden #16
07-23 17:59:28.931 D/dalvikvm( 1432): GC_CONCURRENT freed 382K, 49% free 3093K/6023K, external 888K/990K, paused 1ms+2ms
07-23 17:59:29.291 D/AccelerometerListener( 1496): orientation: horizontal
07-23 17:59:30.613 I/Process ( 1798): Sending signal. PID: 1798 SIG: 9
07-23 17:59:30.623 I/ActivityManager( 1352): Process com.bel.android.dspmanager (pid 1798) has died.
07-23 17:59:30.623 W/ActivityManager( 1352): Scheduling restart of crashed service com.bel.android.dspmanager/.HeadsetService in 5000ms
07-23 17:59:30.643 W/IInputConnectionWrapper( 2358): showStatusIcon on inactive InputConnection
07-23 17:59:33.515 D/dalvikvm( 1496): GC_EXTERNAL_ALLOC freed 111K, 43% free 3476K/6087K, external 5921K/6183K, paused 38ms
07-23 17:59:33.656 I/AudioService( 1352): AudioFocus abandonAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
07-23 17:59:33.676 I/PowerManagerService( 1352): clearUserActivity for 10000ms from now
07-23 17:59:33.686 D/AudioHardwareMSM7X30( 1248): setVoiceVolume(0.800000)
07-23 17:59:33.686 I/AudioHardwareMSM7X30( 1248): Setting in-call volume to 80 (available range is 0 to 100)
07-23 17:59:33.696 I/HTC Acoustic( 1248): update voice ACDB id: (tx_acdb, rx_acdb) = (105, 205)
07-23 17:59:33.696 I/HTC Acoustic( 1248): update voice ACDB id (105, 205) success
07-23 17:59:33.696 I/AudioHardwareMSM7X30( 1248): update_voice_acdb(105, 205) succeeded
07-23 17:59:33.706 D/AudioHardwareMSM7X30( 1248): value of device and enable is 0 1
07-23 17:59:33.706 D/AudioHardwareMSM7X30( 1248): updateACDB: (1, 0, 0, 0)
07-23 17:59:33.716 I/HTC Acoustic( 1248): update ACDB id: (tx, rx, tx_acdb, rx_acdb) = (1, 0, 0, 0)
07-23 17:59:33.716 D/AudioHardwareMSM7X30( 1248): msm_route_stream(PCM_PLAY, 5, 0, 1)
07-23 17:59:33.716 D/AudioHardwareMSM7X30( 1248): addToTable (dec_id 5, dev_rx 0, dev_tx 65535, type 1, active 1)
07-23 17:59:33.806 D/dalvikvm( 1925): GC_CONCURRENT freed 531K, 47% free 3520K/6599K, external 0K/0K, paused 31ms+3ms
07-23 17:59:33.896 I/ActivityManager( 1352): moveTaskToBack: 8
07-23 17:59:33.926 D/AccelerometerListener( 1496): enable(false)
07-23 17:59:33.936 D/AudioHardwareInterface( 1248): setMode(NORMAL)
07-23 17:59:33.936 D/AudioFlinger( 1248): setParameters(): io 1, keyvalue routing=1, tid 1341, calling tid 1248
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): doRouting()
07-23 17:59:33.946 I/AudioHardwareMSM7X30( 1248): Routing audio to Handset
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): new_rx = 0
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): new_tx = 1
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): Ending Voice call
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): deleteFromTable, type 4
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): updateDeviceInfo: E rx_device 0 and tx_device 1
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): No active voicecall/recording, disabling cur_tx 1
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): value of device and enable is 1 0
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): The node type is 1 and cur device 0 new device 0
07-23 17:59:33.946 D/AudioHardwareMSM7X30( 1248): updateDeviceInfo: X cur_rx 0 cur_tx 1
07-23 17:59:35.627 I/ActivityManager( 1352): Start proc com.bel.android.dspmanager for service com.bel.android.dspmanager/.HeadsetService: pid=2554 uid=10031 gids={3002}
07-23 17:59:35.668 D/szipinf ( 2554): Initializing inflate state
07-23 17:59:35.668 I/HeadsetService( 2554): Starting service.
07-23 17:59:35.678 I/Effect-Equalizer( 1248): EQ_PARAM_NUM_BANDS OK
07-23 17:59:35.688 I/HeadsetService( 2554): Phone status idle: enable DSP.
07-23 17:59:35.688 I/Effect-BassBoost( 1248): New strength: 0
07-23 17:59:35.688 I/Effect-Equalizer( 1248): Setting band 2 to 0
07-23 17:59:35.688 I/Effect-Equalizer( 1248): Setting band 2 to 1
07-23 17:59:35.688 I/Effect-Equalizer( 1248): Setting band 2 to 2
07-23 17:59:35.698 I/Effect-Equalizer( 1248): Setting band 2 to 3
07-23 17:59:35.698 I/Effect-Equalizer( 1248): Setting band 2 to 4
07-23 17:59:35.698 I/Effect-Equalizer( 1248): Setting loudness correction reference to 100.000000 dB
07-23 17:59:36.889 D/AudioHardwareMSM7X30( 1248): AudioStreamOutMSM72xx::standby()
07-23 17:59:36.889 D/AudioHardwareMSM7X30( 1248): Deroute pcm out stream
07-23 17:59:36.889 D/AudioHardwareMSM7X30( 1248): deleteFromTable, type 1
07-23 17:59:36.889 D/AudioHardwareMSM7X30( 1248): updateDeviceInfo: E rx_device 0 and tx_device 1
07-23 17:59:36.889 D/AudioHardwareMSM7X30( 1248): No active voicecall/playback, disabling cur_rx 0
07-23 17:59:36.889 D/AudioHardwareMSM7X30( 1248): value of device and enable is 0 0
07-23 17:59:36.899 D/AudioHardwareMSM7X30( 1248): No active voicecall/recording, disabling cur_tx 1
07-23 17:59:36.899 D/AudioHardwareMSM7X30( 1248): value of device and enable is 1 0
07-23 17:59:36.899 D/AudioHardwareMSM7X30( 1248): updateDeviceInfo: X cur_rx 0 cur_tx 1
07-23 17:59:41.804 D/dalvikvm( 2358): GC_EXPLICIT freed 366K, 47% free 3374K/6279K, external 1951K/2080K, paused 43ms
07-23 18:00:00.892 D/Vold ( 1243): USB disconnected
07-23 18:00:00.892 D/Vold ( 1243): Share method ums now unavailable
07-23 18:00:00.892 I/StorageNotification( 1432): UMS connection changed to false (media state mounted)
07-23 18:00:00.902 W/Vold ( 1243): Ignoring unknown switch 'msm72k_udc'
07-23 18:00:00.922 D/Vold ( 1243): USB disconnected
07-23 18:00:00.972 I/ActivityManager( 1352): Start proc com.android.settings for broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=2569 uid=1000 gids={3002, 3001, 3003, 1015}
07-23 18:00:01.052 D/szipinf ( 2569): Initializing inflate state
07-23 18:00:01.122 D/szipinf ( 2569): Initializing inflate state

I went back to ext3 FS today and flashed Andromadus Audacity 5. Everything
seems to work fine again.
I think this can be marked solved now.
Thanks for your help.

GNex Toro Unable to Boot JB ROMS

Galaxy Nexus CDMA (Toro)
Hardware version 11.11
Basedband: I515.09 V.FC04 / I515.FC05
Run ICS ROMs without issue
Unable to boot any Jellybean based roms. Have tried 3 different releases all with the same results.
Tried LA03 and LC03 boot loaders
Tried both CWMR and TWRP recoverys
Tried superwipe
Tried odin image to stock
Tried GalNex ToolKit
Tried adb fastboot image commands
Tried manual wipes from recovery
Tried locking and then unlocking the boot loader
The commonality between them all are the following lines from logcat during power on. These indicate that the system is unable to mount the partitions. Full logcat output.
Code:
I/Vold ( 106): Vold 2.1 (the revenge) firing up
D/Vold ( 106): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 3, PARTN 3
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 4, PARTN 4
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 5, PARTN 5
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 6, PARTN 6
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 7, PARTN 7
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 0, PARTN 8
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 1, PARTN 9
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 2, PARTN 10
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 3, PARTN 11
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 4, PARTN 12
E/DirectVolume( 106): Invalid 'PARTN' value
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> MAJOR 259, MINOR 5, PARTN 13
E/DirectVolume( 106): Invalid 'PARTN' value
D/Vold ( 106): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
adb shell to show mounts:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
[email protected]:/ #
This issue is not limited to me. Others are having the same problem.

Bump
Sent from my Galaxy Nexus using Tapatalk 2

Mr.Jester said:
Bump
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1778555
Not sure if a solution was found but might give you some ideas where to start

NYYFan325 said:
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1778555
Not sure if a solution was found but might give you some ideas where to start
Click to expand...
Click to collapse
I am posting in that thread too. The technical details are buried down in the pages, so I started this thread to bring them to the top.
And with that said, bump too!

[Q] Stock Email and Contact application crash

Hi,
I'm using the stock Android email client application on a non rooted, stock rom Galaxy S3. Almost every 2 or 3 hours while using the stock email application I got an error message: Email closed or Contacts closed. The stock Android email client is using only 1 profile connected to Microsoft Exchange server. Here's some part of the log file that could be related:
09-17 18:39:59.068 W/WindowManager( 652): Rebuild removed 6 windows but added 5
09-17 18:39:59.078 D/lights ( 652): write_int /sys/class/leds/lcd-backlight/brightness = 24
09-17 18:39:59.088 D/lights ( 652): write_int /sys/class/leds/lcd-backlight/brightness = 28
09-17 18:39:59.088 W/WindowManager( 652): This window was lost: Window{420189f8 com.android.email/com.android.email.activity.MessageListXL paused=false}
09-17 18:40:01.270 I/ActivityManager( 652): Process com.android.email (pid 16962) has died.
09-17 18:40:01.270 I/WindowManager( 652): WIN DEATH: Window{420189f8 XXX.XXXXXXX.XXXXX/XXX.XXXXXXX.XXXXX.XXXXXXXX.XXXXXXXXXXXXX paused=false}
09-17 18:40:01.270 E/MotionRecognitionService( 652): Failed motionCallback
09-17 18:40:01.270 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 18:40:01.270 E/MotionRecognitionService( 652): Failed motionCallback
09-17 18:40:01.270 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 18:40:01.270 E/MotionRecognitionService( 652): Failed motionCallback
09-17 18:40:01.270 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 18:40:01.270 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 18:40:01.280 D/KeyguardViewMediator( 652): setHidden false
09-17 18:40:01.280 D/memalloc( 342): ion: Freeing buffer base:0x43b07000 size:3768320 fd:42
09-17 18:40:01.280 E/MotionRecognitionService( 652): Failed motionCallback
09-17 18:40:01.280 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 18:40:01.280 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 18:40:01.280 D/MotionRecognitionService( 652): .binderDied : 3
09-17 18:40:01.280 D/MotionRecognitionService( 652): .binderDied : 2
09-17 18:40:01.280 D/MotionRecognitionService( 652): .binderDied : 1
09-17 17:11:16.418 D/KeyguardViewMediator( 652): setHidden false
09-17 17:11:16.418 W/InputDispatcher( 652): channel ~ Consumer closed input channel or an error occurred. events=0x8
09-17 17:11:16.418 E/InputDispatcher( 652): channel ~ Channel is unrecoverably broken and will be disposed!
09-17 17:11:16.418 I/ActivityManager( 652): Process com.android.contacts (pid 1517) has died.
09-17 17:11:16.418 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.418 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.418 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.418 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.418 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.428 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.428 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.428 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.428 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.428 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.428 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.428 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.438 I/SensorManager( 652): Set min delay = 200000
09-17 17:11:16.438 I/SensorManager( 652): Set min delay = 200000
09-17 17:11:16.438 I/SensorManager( 652): Set min delay = 200000
09-17 17:11:16.438 I/SensorManager( 652): Before sending... delay = 200000
09-17 17:11:16.438 I/Sensors ( 652): sendDelay --- 200000000
09-17 17:11:16.438 V/Sensors ( 652): setDelay - sensor Accelerometer (handle 4), rate 200 ms (5.00 Hz)
09-17 17:11:16.438 D/SensorManager( 652): JNI - sendDelay
09-17 17:11:16.438 I/SensorManager( 652): send_delay :: return = true
09-17 17:11:16.438 D/SensorManager( 652): unregisterListener:: disable all sensors for this listener, name = MPL accel listener = [email protected]
09-17 17:11:16.438 V/Sensors ( 652): enable - sensor Gyro (handle 3) en -> dis
09-17 17:11:16.438 E/Sensors ( 652): mEnabled = 10
09-17 17:11:16.438 V/Sensors ( 652): setDelay - sensor Gyro (handle 3), rate 20 ms (50.00 Hz)
09-17 17:11:16.438 D/SensorManager( 652): unregisterListener:: disable all sensors for this listener, name = MPL Gyro listener = [email protected]
09-17 17:11:16.438 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.438 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.438 E/MotionRecognitionService( 652): Failed motionCallback
09-17 17:11:16.438 E/MotionRecognitionService( 652): android.os.DeadObjectException
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.BinderProxy.transact(Native Method)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.hardware.motion.IMotionRecognitionCallback$Stub$Proxy.motionCallback(IMotionRecognitionCallback.java:98)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$Listener.callback(MotionRecognitionService.java:1197)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.hardware.motion.MotionRecognitionService$ServiceHandler.handleMessage(MotionRecognitionService.java:1215)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.Handler.dispatchMessage(Handler.java:99)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.Looper.loop(Looper.java:137)
09-17 17:11:16.438 E/MotionRecognitionService( 652): at android.os.HandlerThread.run(HandlerThread.java:60)
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 6
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 5
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 4
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 3
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 2
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 1
09-17 17:11:16.438 D/MotionRecognitionService( 652): .binderDied : 0

vold, using ext3 on SD, USB drives

vold is the volume daemon which is responsible for mounting removable (and sometimes non-removable) volumes.
It's the daemon that mounts your SD card so that you can use it.
It also mounts /media and is responsible for switching to USB mode when you plug the Nook into a desktop.
It's also what should be mounting your USB flash drives when you plug them in.
While working on my adbsync.exe I kept on running into bugs related to the vfat file system on the SD card.
Using the adage of "It's better to fix someone else's bugs than your own bugs", I set to work on vold.
The vold that ships with the Nook is non-standard.
I don't know if it was snarfed by B&N from somewhere.
It won't mount ext3 volumes or USB flash drives.
I built vold from the Eclair sources and it works even worse than the B&N stock.
A bunch of hacking later, I got it to mount an ext3 partition on an SD card.
I'm still working on USB drives and multiple partitions on an SD card.
So my adbsync.exe works marvelously now that it has real UTC timestamps to go on (courtesy of ext3).
As soon as I get things a bit more stabilized I'll post vold.

Code:
# mount
[color=gray]rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0[/color]
/dev/block/vold/179:6 [b]/media vfat[/b] rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 [b]/sdcard ext3[/b] rw,sync,nosuid,nodev,noexec,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/vold/179:18 [b]/audio ext3[/b] rw,sync,nosuid,nodev,noexec,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/vold/180:1 [b]/usb vfat[/b] rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
This still has a few wrinkles, but it's getting there.

Thank you for continuing to develop for the NST! Just wanted to let you know.
:good:Also, thank you for your Library app (it's the best for me).

Ok, for the adventurous we have a beta release of vold.
The first thing is to decide your mount points.
You may like them in the root, like /sdcard or higher up like /mnt/usb
You will have to establish these mount points in init.rc (in uRamdisk).
You can just put them after the one for /sdcard.
All my examples are based upon using the original /media, having two partitions on the removable SD card and one partition on a USB flash drive.
You may use more or less of this stuff depending on your needs.
Code:
mkdir /media 0777 system system
mkdir /sdcard 0777 system system
mkdir /audio 0777 system system
mkdir /usb 0777 system system
Edit vold.conf to suit your setup.
Then replace /system/bin/vold and /system/etc/vold.conf
Be sure to chmod 755 vold
There are a few small wrinkles now.
One is that upon booting it will give you a notification that a drive has been removed.
This is due to a strangeness in the Android code, but for right now it's not worth patching that.
The other wrinkle is that it will complain when you disconnect a USB drive.
Things that do work nicely.
Mounting of vfat or ext3 partitions
Mounting of multiple partitions on a single device
Automatic mounting of USB drives
The UMS still works for /media and one other partition (presumably /sdcard).
Download in the signature.
If you run into strangeness, please post your /system/etc/vold.conf & /data/voldlog

Many many thanks! I had messed up the partitions on my ST. Even after fixing it, I couldn't get /media to mount via USB, and couldn't understand why. Your new version fixed my problems. Thanks again!

Hi Renate NST,
Unfortunately, i was unable to make USB automount work
I have replaced /system/bin/vold (set perm to 755), added the following lines to /system/etc/vold.conf:
Code:
volume_usb
{
media_path /devices/platform/musb_hdrc/usb1
media_type mmc
partition 1
mount_point /usb
}
... and edited /init.rc with:
Code:
mkdir /usb 0777 system system
It seems that something wrong happens with vold when I plug usb flash drive and press "HOST" button. Here is the logcat output:
Code:
I/DEBUG ( 972): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 972): Build fingerprint: 'generic/zoom2/zoom2/zoom2:2.1/ERD79/1.1.2:user/test-keys'
I/DEBUG ( 972): pid: 971, tid: 971 >>> /system/bin/vold <<<
I/DEBUG ( 972): signal 11 (SIGSEGV), fault addr 0ccccccc
I/DEBUG ( 972): r0 0ccccccc r1 00000000 r2 80808080 r3 00000000
I/DEBUG ( 972): r4 0ccccccc r5 00000002 r6 00000000 r7 bec6622c
I/DEBUG ( 972): r8 00000000 r9 00000000 10 00000000 fp bec66a2c
I/DEBUG ( 972): ip ffffffff sp bec661a8 lr afe162bb pc afe0e530 cpsr 60000010
I/DEBUG ( 972): #00 pc 0000e530 /system/lib/libc.so
I/DEBUG ( 972): #01 pc 000162b8 /system/lib/libc.so
I/DEBUG ( 972):
I/DEBUG ( 972): code around pc:
I/DEBUG ( 972): afe0e520 1afffff6 e1a00002 e3082080 e3482080
I/DEBUG ( 972): afe0e530 e490c004 e0433000 f5d0f040 e04c13a2
I/DEBUG ( 972): afe0e540 e0011002 e1d1100c 0490c004 1a000022
I/DEBUG ( 972):
I/DEBUG ( 972): code around lr:
I/DEBUG ( 972): afe162a8 1b039c09 bfa84563 e0034663 f7f89809
I/DEBUG ( 972): afe162b8 4603e90a 7e88f50d 0c00f04f 46629c06
I/DEBUG ( 972): afe162c8 cc01f80e c018f8cd 970ee140 0610f046
I/DEBUG ( 972):
I/DEBUG ( 972): stack:
I/DEBUG ( 972): bec66168 00000000
I/DEBUG ( 972): bec6616c 00000000
I/DEBUG ( 972): bec66170 00000000
I/DEBUG ( 972): bec66174 00000000
I/DEBUG ( 972): bec66178 00000000
I/DEBUG ( 972): bec6617c 00000000
I/DEBUG ( 972): bec66180 00000000
I/DEBUG ( 972): bec66184 00000000
I/DEBUG ( 972): bec66188 00000000
I/DEBUG ( 972): bec6618c 00000000
I/DEBUG ( 972): bec66190 00000000
I/DEBUG ( 972): bec66194 00000000
I/DEBUG ( 972): bec66198 00000000
I/DEBUG ( 972): bec6619c 00000000
I/DEBUG ( 972): bec661a0 df002777
I/DEBUG ( 972): bec661a4 e3a070ad
I/DEBUG ( 972): #00 bec661a8 00000000
I/DEBUG ( 972): bec661ac 0ccccccc
I/DEBUG ( 972): #01 bec661b0 00000000
I/DEBUG ( 972): bec661b4 00000000
I/DEBUG ( 972): bec661b8 00000000
I/DEBUG ( 972): bec661bc 00000000
I/DEBUG ( 972): bec661c0 00000000
I/DEBUG ( 972): bec661c4 00000000
I/DEBUG ( 972): bec661c8 bec668d8 [stack]
I/DEBUG ( 972): bec661cc 00000000
I/DEBUG ( 972): bec661d0 00000000
I/DEBUG ( 972): bec661d4 0ccccccc
I/DEBUG ( 972): bec661d8 bec66444 [stack]
I/DEBUG ( 972): bec661dc 00000073
I/DEBUG ( 972): bec661e0 afe3ae08 /system/lib/libc.so
I/DEBUG ( 972): bec661e4 bec662bf [stack]
I/DEBUG ( 972): bec661e8 000176dc /system/bin/vold
I/DEBUG ( 972): bec661ec 00000000
I/DEBUG ( 972): bec661f0 00000000
I/DEBUG ( 972): bec661f4 00000006
E/MountListener( 1051): Failed to connect to vold
E/MountListener( 1051): java.lang.IllegalStateException
E/MountListener( 1051): at com.android.server.MountListener.listenToSocket(MountListener.java:269)
E/MountListener( 1051): at com.android.server.MountListener.run(MountListener.java:289)
E/MountListener( 1051): at java.lang.Thread.run(Thread.java:1096)
I/vold ( 4450): Android Volume Daemon version 2.0
D/vold ( 4450): Partition not specified, defaulting to 1
W/vold ( 4450): Volume '/media' already mounted at startup
W/vold ( 4450): Volume '/sdcard' already mounted at startup
I/vold ( 4450): Name: 002G00, Serial: 0x090fe044
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:0' (File exists)
I/vold ( 4450): New blkdev 179.0 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 0
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:1' (File exists)
I/vold ( 4450): New blkdev 179.1 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p1
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 1
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:2' (File exists)
I/vold ( 4450): New blkdev 179.2 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p2
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 2
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:3' (File exists)
I/vold ( 4450): New blkdev 179.3 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p3
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 3
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:4' (File exists)
I/vold ( 4450): New blkdev 179.4 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p4
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 4
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:5' (File exists)
I/vold ( 4450): New blkdev 179.5 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p5
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 5
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:6' (File exists)
I/vold ( 4450): New blkdev 179.6 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p6
E/vold ( 4450): Volume /media already mounted (did we just crash?)
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:7' (File exists)
I/vold ( 4450): New blkdev 179.7 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p7
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 7
E/vold ( 4450): Error making device nodes for '/dev/block/vold/179:8' (File exists)
I/vold ( 4450): New blkdev 179.8 on media 002G00, media path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8
E/vold ( 4450): Could not find volume by /devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0 and 8
D/vold ( 4450): send_msg(ums_disabled):
D/vold ( 4450): send_msg(ums_disconnected):
D/vold ( 4450): Bootstrapping complete
D/dalvikvm( 4071): GC freed 3242 objects / 522848 bytes in 36ms
D/vold ( 4450): Accepted connection from framework
D/vold ( 4450): send_msg(volume_mounted:/media):
D/MountListener( 1051): handleEvent volume_mounted:/media
D/vold ( 4450): send_msg(volume_mounted:/sdcard):
D/vold ( 4450): send_msg(volume_nomedia:/usb):
D/vold ( 4450): dispatch_cmd(send_ums_status):
D/vold ( 4450): send_msg(ums_disabled):
D/vold ( 4450): send_msg(ums_disconnected):
D/vold ( 4450): dispatch_cmd(mount_volume:/sdcard):
E/vold ( 4450): Cannot start volume '/sdcard' (volume is not bound)
D/vold ( 4450): dispatch_cmd(mount_volume:/media):
E/vold ( 4450): Cannot consider volume '/media' because it is in state '4
E/vold ( 4450): volmgr failed to start volume '/media'
D/MountListener( 1051): handleEvent volume_mounted:/sdcard
I/ActivityManager( 1051): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.internal.app.ExternalMediaStatusActivity (has extras) }
D/MountListener( 1051): handleEvent volume_nomedia:/usb
D/MediaScannerService( 1152): start scanning volume external
I/ActivityManager( 1051): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.internal.app.ExternalMediaStatusActivity (has extras) }
D/MountListener( 1051): handleEvent ums_disabled
D/MountListener( 1051): handleEvent ums_disconnected
Here is the /data/voldlog:
Code:
12:49:55.406 Starting vold
12:49:55.610 <= volume_checking:/media
12:49:55.612 <= ums_disabled
12:49:55.612 <= ums_disconnected
12:49:56.487 <= volume_mounted:/media
12:50:08.605 Framework connected
12:50:08.605 <= volume_mounted:/media
12:50:08.605 <= volume_nomedia:/sdcard
12:50:08.605 <= volume_nomedia:/usb
12:50:08.606 <= ums_disabled
12:50:08.606 <= ums_disconnected
12:50:08.606 => send_ums_status
12:50:08.606 => mount_volume:/sdcard
12:50:08.606 => mount_volume:/media
12:50:14.008 Starting vold
12:50:14.012 <= ums_disabled
12:50:14.012 <= ums_disconnected
12:50:16.003 Framework connected
12:50:16.003 <= volume_mounted:/media
12:50:16.011 <= volume_mounted:/sdcard
12:50:16.012 <= volume_nomedia:/usb
12:50:16.012 <= ums_disabled
12:50:16.012 <= ums_disconnected
12:50:16.012 => send_ums_status
12:50:16.012 => mount_volume:/sdcard
12:50:16.012 => mount_volume:/media
USB host mode seems to work correctly, since i'm able to mount the drive manually:
Code:
mount -t vfat /dev/block/uba1 /usb

Alright, so I was confused and in a hurry when I last responded.
You are connecting the USB flash drive, then hitting the Host button on UsbMode?
It could be related to the USB going in and out.
Are you trying to use a flash drive without a hub?
That's problematic depending on how much current it takes.
Use a hub.
Put it in host mode.
Connect a keyboard and see that it sees it.
Then plug in the flash drive.

Renate NST said:
You are connecting the USB flash drive, then hitting the Host button on UsbMode?
Click to expand...
Click to collapse
Excatly. When i hitting the button, there pops up the icon with SD card at the top of the screen (just like when you inserting a microSD), but no new mounts appears. However, it creates the new block device (/dev/block/uba1) and i can mount it by hands: mount -t vfat /dev/block/uba1 /usb.
Concering the USB hub: yes, i found that the most of my flash drives are refusing to work via direct plugging in. However, i found an ancient 256 MB usb flash drive that work perfectly So i'm playing with it since I have no a powered usb hub at this moment.

The vold I mixed up is just a stock (not B&N) version with a few modifications for multiple partitions and ext3 support.
Trying to run a flash drive without a hub is too much on the edge.
The Nook can really only supply about 70 mA to the USB.
Most older flashes take more than that.
I would only rely on keyboards and other things that take less than 10 mA.

Hi everyone. Sorry to dig up an old thread.
I just attempted to install this on my Nook Touch Glow with firmware 1.2.1. Unfortunately, it only seems to activate the little boot-up bug where it says that your SD card has been removed, the aforementioned (somewhere on this forum) screensaver bug (see spoiler below), and it doesn't seem to do much else. It doesn't auto-mount my USB drives, but that could be because I haven't been able to get the cpio applet to work for extracting and editing the uramdisk file.
All around, I'd rather have the old vold and vold.conf back. Can anyone please post the original vold (found in /system/bin) and vold.conf (found in /system/etc) for me? That'd be great!
Or, Renate, would you be up for trying to fix the screensaver bug and mounting bug and making a new vold?
Thanks,
3N
For some reason, when I installed the vold file found in this thread, it immediately (after a reboot) caused the Settings > Screen > Screensavers option to only show the screensaver folders located in /system/media/screensaver, and not show any of the ones in /media/screensavers. So I thought Okay, I'll just move my screensaver folders to /system/media/screensaver. I tried that, and what I found was that if I selected a folder other than Authors or Nature for use as the screensaver, it just automatically selected Authors again.
My temporary fix is to put my screensavers in Authors and put the original authors files in a backup folder, but I'd love to be able to fix this or just get rid of this new vold altogether.
EDIT - Thanks to OverByter for giving me these files! Sorry that your vold doesn't seem to work so well, though, Renate.

All the original B&N files are available in the original B&N update, just unzip them.
I use my bootutil.exe (in signature) for modifying ramdisks.
Although vold was working fine, I've largely given up on it.
Mounting USB drives on the Nook was really not too practical.
Both USB host mode and USB drives take a lot of current.
You'd be better off just copying it to the SD card.
Isn't 32 G enough?
I use mntsdcard these days.
The thread is here: http://forum.xda-developers.com/showthread.php?t=2609223
It works fine and I haven't thought about it for a while.

Renate NST said:
All the original B&N files are available in the original B&N update, just unzip them.
I use my bootutil.exe (in signature) for modifying ramdisks.
Although vold was working fine, I've largely given up on it.
Mounting USB drives on the Nook was really not too practical.
Both USB host mode and USB drives take a lot of current.
You'd be better off just copying it to the SD card.
Isn't 32 G enough?
I use mntsdcard these days.
The thread is here: http://forum.xda-developers.com/showthread.php?t=2609223
It works fine and I haven't thought about it for a while.
Click to expand...
Click to collapse
32 gigs is certainly plenty, but I'd mainly be using it to auto-mount my keyboard, camera, and MP3 player (to save the extra time required with manual mounting), not for memory drives.
And thanks for bootutil! :good: