zslzsl999 发表于 2014-3-18 14:28 已经解决了 差点忘了这个帖子了 大致说一下我得过程这个问题要在串口行输入logcat查看android的log信息 然 ...

谢谢你的回复。我看了一下我的logcat，好像没看到invensense的信息啊。 能加个Q不，我还没解决，愁死了啊。我的Q 271891857，感谢！！

zslzsl999 发表于 2014-3-5 10:51 握手。。。 那个BOARD_SDMMC_BSP是干啥的？

就是编译后的文件跑在emmc上，文件系统格式是EXT4，要是设置为False的话就编译的Yaffs格式。你的问题解决了吗？

gooogleman 发表于 2014-2-20 22:37 呵呵，这个楼上问题还没解决吗？

这个问题是2.3系统的，还没解决。现在弄4.0 的系统，有了新问题。 就是35楼的问题。我的Android是4.0的，在BoardConfig.mk里面没发现有BOARD_SDMMC_BSP这个变量，我就直接编译出来后，使用make_ext4fs制作的system.img镜像，制作成EXT4格式的了。我的u-boot也是1.3.4版本，利用带的工具ext3format格式化的system分区，系统第一次启动之后就出现下面的错误： Freeing init memory: 176K init: cannot open '/initlogo.rle' EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null) EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 32237 in gd Aborting journal on device mmcblk0p3-8. EXT4-fs (mmcblk0p3): Remounting filesystem read-only EXT4-fs error (device mmcblk0p3) in ext4_reserve_inode_write:5641: Journal has aborted EXT4-fs error (device mmcblk0p3) in ext4_evict_inode:215: Journal has aborted rtusb init rt2870 ---> usbcore: registered new interface driver rt2870 EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 26728 in gd Aborting journal on device mmcblk0p2-8. EXT4-fs (mmcblk0p2): Remounting filesystem read-only EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:5641: Journal has aborted EXT4-fs error (device mmcblk0p2) in ext4_evict_inode:215: Journal has aborted init: Unable to open persistent property directory /data/property errno: 2 我用ls查看了一下，发现也挂载上了。但是一直打印下面的信息，停留在ANDROID字样的界面，进入不了系统。 request_suspend_state: wakeup (3->0) at 5335262707 (2014-03-02 08:59:42.414075023 UTC) init: untracked pid 2179 exited init: untracked pid 2184 exited request_suspend_state: wakeup (0->0) at 9111824947 (2014-03-02 08:59:46.190638013 UTC) init: untracked pid 2230 exited init: untracked pid 2229 exited request_suspend_state: wakeup (0->0) at 13894569232 (2014-03-02 08:59:50.973382464 UTC) init: untracked pid 2290 exited init: untracked pid 2289 exited …… 要是再次启动的话，错误就会变成： Freeing init memory: 176K init: cannot open '/initlogo.rle' EXT4-fs warning (device mmcblk0p2): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure EXT4-fs warning (device mmcblk0p2): ext4_clear_journal_err:4155: Marking fs in need of filesystem check. EXT4-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended EXT4-fs (mmcblk0p2): recovery complete EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) EXT4-fs warning (device mmcblk0p3): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure EXT4-fs warning (device mmcblk0p3): ext4_clear_journal_err:4155: Marking fs in need of filesystem check. EXT4-fs (mmcblk0p3): warning: mounting fs with errors, running e2fsck is recommended EXT4-fs (mmcblk0p3): recovery complete EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended EXT4-fs (mmcblk0p4): recovery complete EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null) EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 32237 in gd Aborting journal on device mmcblk0p3-8. EXT4-fs (mmcblk0p3): Remounting filesystem read-only EXT4-fs error (device mmcblk0p3) in ext4_reserve_inode_write:5641: Journal has aborted EXT4-fs error (device mmcblk0p3) in ext4_evict_inode:215: Journal has aborted rtusb init rt2870 ---> usbcore: registered new interface driver rt2870 EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 26728 in gd Aborting journal on device mmcblk0p2-8. EXT4-fs (mmcblk0p2): Remounting filesystem read-only EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:5641: Journal has aborted EXT4-fs error (device mmcblk0p2) in ext4_evict_inode:215: Journal has aborted 一样是进入不了Android系统。

我做了个板子，VDD_ARM和VDD_INT没处理好，跑不了高频

标题看起来行，可别是幌子

gooogleman 发表于 2013-5-29 23:16 ./make_ext4fs  -l 120M -a system system.img out/target/product/smdkv210/system 经过这么压缩 再用fi ...

你好，我用make_ext4fs制作的system镜像可以挂载上，并且也启动到了Android界面。但是很多应用程序不能使用了，比如不能放歌曲、不能看视频，不能安装应用程序。安装应用程序就会导致Android界面重启，终端提示： binder: 465:465 transaction failed 29189, size 64-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 465:508 transaction failed 29189, size 60-0 binder: 407:407 transaction failed 29189, size 64-0 alarm_release: clear alarm, pending 0 alarm_release: clear alarm, pending 0 alarm_release: clear alarm, pending 0 request_suspend_state: wakeup (0->0) at 249555247379 (1970-01-02 19:22:47.319828253 UTC) init: untracked pid 72 exited init: untracked pid 556 exited init: untracked pid 223 exited init: untracked pid 583 exited init: untracked pid 199 exited init: untracked pid 572 exited init: untracked pid 218 exited init: untracked pid 209 exited init: untracked pid 301 exited init: untracked pid 352 exited init: untracked pid 407 exited init: untracked pid 386 exited init: untracked pid 317 exited init: untracked pid 398 exited init: untracked pid 378 exited init: untracked pid 367 exited init: untracked pid 416 exited init: untracked pid 287 exited init: untracked pid 438 exited init: untracked pid 267 exited init: untracked pid 465 exited init: untracked pid 304 exited init: untracked pid 339 exited init: untracked pid 427 exited init: untracked pid 212 exited