Quote:
Originally Posted by natemcnutty
OK, I removed those two files then. I still don't get why data isn't working, but that is what I'm looking into right now.
Also, for some reason, when booting we only see 3 of the mtdparts. I did an ls of /dev/block and /dev/mtd/ during the install script to find that the mtd4 was not being created until we get into Android. That means I can't format or reference our cache partition, and when I do it, Android will not boot since there is no /cache mount point. Any idea why this might be?
As for cyanogen, I don't know what all would be needed to get it running, but I'd be willing to look into it 
Edit: You sure we don't need/want ueventd? I was just looking at our sysinit.rc and has this:
Code:
service ueventd /sbin/ueventd
critical
Without it, it throws an error that it couldn't find it and is disabling the daemon. I think it is required by our init.android but not the other one that the vogue used originally. I'm leaving it in since we are only going up to gingerbread from here, and it appears Froyo is happy with it being there. |
another thing stine said make sure we grab the correct init.android. They arent the same from froyo and gingerbread so we need to make sure we get them from the correct git.
cyanogen is easy .. had 5.0 running before but im interested in the later one. So in time i will upload those tars as well.
anyways i wont be back till later tonight so keep attacking it
Edit: i saw you issue. I'm fixing it in my commit tonight. Our initrd wasnt creating the directories for all the new nandparts thats all. We are all set now.