ramdisk needs to be edited:
u can extract boot.img
extract the ramdisk
and study it
then create ur own ramdisk
and test it (from DooMLoRD)
the files are in the zip posted by doomlord
Kernel folder is for splboot modules and ramdisk for dualbooting - we don't have splboot yet (and probably never will).
system/system.ext2 is our system image.
The only problem i see with this, DooM, is that we will have to half our data partition if we want to use two ROM's (as in, two data images) meaning we will have much less app space, same goes for /system too...
but i am currently busy with lots of work, so anyway once the kernel is released for PLAY (shortly), i will push sources to git... i am sure u will soon find the changes percolating thru to other kernels
I guess I do since you've been fairly quiet about it. Thanks for the git source pushes. I may have to learn how to compile Android kernels myself. Being that I know how to do it with Linux kernels makes me curious as to this process.
Are you sure it isn't just your phone (if it is then I feel really bad for you)
Suggestion, although might seem stupid: try reflashing baseband
Its not just data it is the the complete gsm conection. No service at all, no SMS, no calls, no data. I tried reflashing the full 62 ftf with baseband and all but that changed nothing. I am not sure if it is becouse of the kernel but it happened shortly after i flashed it...
No matter how much we try to hide it, we all have some creative juices flowing somewhere … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?