[Hero, G2 Touch Android Development] polariscon:
1.4 nonOC full wipe

App2sd not working IMO.

Got this in logcat:

05-25 22:38:59.553: INFO//system/xbin/busybox(44): +++ "Pleased to meet you, we came to drop bombs on you!"

05-25 22:38:59.613: INFO//system/xbin/busybox(44): +++ Welcome to Android 2.1 / CronosDroid_1.4

05-25 22:38:59.643: INFO//system/xbin/busybox(44): sysctl: /etc/sysctl.conf: No such file or directory

05-25 22:38:59.673: INFO//system/xbin/busybox(44): --- Checking filesystems

05-25 22:38:59.723: INFO//system/xbin/busybox(44): e2fsck 1.40.8 (13-Mar-2008)

05-25 22:38:59.733: INFO//system/xbin/busybox(44): /dev/block/mmcblk0p2: clean, 11/249856 files, 31395/499214 blocks

05-25 22:38:59.763: INFO//system/xbin/busybox(44): mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory

05-25 22:38:59.773: INFO//system/xbin/busybox(44): *** Unable to mount filesystem for a2sd!

And then :

05-25 22:38:59.813: INFO//system/xbin/busybox(44): --- Checking filesystems

05-25 22:38:59.833: INFO//system/xbin/busybox(44): e2fsck 1.40.8 (13-Mar-2008)

05-25 22:38:59.833: INFO//system/xbin/busybox(44): e2fsck: Superblock invalid, trying backup blocks...

05-25 22:38:59.853: INFO//system/xbin/busybox(44): e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p1

05-25 22:38:59.853: INFO//system/xbin/busybox(44): The superblock could not be read or does not describe a correct ext2

05-25 22:38:59.863: INFO//system/xbin/busybox(44): filesystem. If the device is valid and it really contains an ext2

05-25 22:38:59.863: INFO//system/xbin/busybox(44): filesystem (and not swap or ufs or something else), then the superblock

05-25 22:38:59.863: INFO//system/xbin/busybox(44): is corrupt, and you might try running e2fsck with an alternate superblock:

05-25 22:38:59.863: INFO//system/xbin/busybox(44): e2fsck -b 8193 <device>

05-25 22:38:59.883: INFO//system/xbin/busybox(44): mount: mounting /dev/block/mmcblk0p1 on /system/sd failed: No such file or directory

05-25 22:38:59.893: INFO//system/xbin/busybox(44): *** Unable to mount filesystem for a2sd!

05-25 22:39:00.053: INFO/logwrapper(44): /system/xbin/busybox terminated by exit(0)

05-25 22:39:00.193: INFO/DEBUG(99): debuggerd: Apr 15 2010 14:07:48

And strange thing here:

looks like Daemon starts here after app2sd script.

05-25 22:39:00.203: INFO/vold(98): Android Volume Daemon version 2.0

05-25 22:39:00.263: INFO/vold(98): New MMC card 'SU08G' (serial 1076027447) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:c913

05-25 22:39:00.273: INFO/vold(98): Disk (blkdev 179:0), 15954944 secs (7790 MB) 2 partitions

05-25 22:39:00.283: INFO/vold(98): New blkdev 179.0 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:c913, Dpp 2

05-25 22:39:00.293: INFO/vold(98): Partition (blkdev 179:1), 14956452 secs (7302 MB) type 0xc

05-25 22:39:00.293: INFO/vold(98): New blkdev 179.1 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:c913, Dpp 1

05-25 22:39:00.313: INFO/vold(98): Partition (blkdev 179:2), 998429 secs (487 MB) type 0x83

05-25 22:39:00.313: INFO/vold(98): New blkdev 179.2 on media SU08G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:c913, Dpp 0

05-25 22:39:00.313: INFO/vold(98): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:c913/block/mmcblk0' for mountable filesystems for '/sdcard'

05-25 22:39:00.313: INFO/vold(98): Aborting start of /sdcard (bootstrap = 1)

05-25 22:39:00.313: INFO/vold(98): Volmgr not ready to handle device

05-25 22:39:01.433: INFO/AndroidRuntime(101): JNI options: '-Xjniopts:warnonly'

also no bootscreen:

05-25 22:39:15.173: WARN/zipro(131): Unable to open zip '/data/local/bootanimation.zip': No such file or directory

lightsensor error:

05-25 22:39:38.063: ERROR/lights(122): write_int failed to open /sys/class/leds/lcd-backlight/auto

and finally wifi:

05-25 22:39:40.675: ERROR/WifiService(122): Failed to load Wi-Fi driver.

I think, going back to previous release. :confused: