[WIP][On hold indefinitely] CM7.2 Port from Nexus One - Dell Venue

Disclaimer: I'm a noob. This is my first attempt ever and even it doesn't sound that difficult, don't keep your hope high.
So what I intended to do right now is to use the CM7.2 RC0 KANG for Nexus One (which is currently my main daily use) as a base, which can be found here:
http://www.mediafire.com/?qac2glyh0egscb2
(Rationale: Dell Venue and Nexus One share the same chipset and GPU, and furthermore, I have assessed that build and found it stable enough to be ported)
Proprietary files and driver data from a working ROM of Dell Venue will then be transferred to replace the files in the base (which originally belong to Nexus One). What I have transferred includes:
Modules:
/system/lib/modules
Hardware
/system/lib/hw
Keyboard
/system/usr/keylayout
/system/usr/keychars
Mount points & wifi
/system/etc/vold.fstab
/system/etc/wifi
/system/etc/ppp
(My source for these: http://www.freeyourandroid.com/guide/porting-android)
I have also replace the boot.img
and delete the first line of the script in updater-script,
which removes the phone model identification process:
Code:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
The package is then zipped and signed, but so far, it doesn't even boot. It doesn't even make it to the boot animation.
I haven't involved the boot.img and kernel yet. And I don't think it's necessary for a boot.
I repeat: I'm a total noob and totally inexperienced in the process of ROM development. I would be grateful and appreciate if you can point me to an useful guide or have any suggestion that could make some progress.
The catlog is attached below. It looks like alien language to me and I need someone experienced to help me diagnose it. My priority is to make it boot now, then we'll see what we can do next. Thank you in advance.
Last logcat update: 2012-02-23, 1700 GMT+8
PS: I'll upload the zip file if someone requests, for now I prefer to focus on the logcat
UPDATE 12.02.25: Well, first attempt with Kitchen, it did boot actually, but ended up with a blackscreen after 10 secs or so. Logcat says it's VertexArray or some OpenGL sort. Asides from that, nothing else works except for the touchscreen and SDCard. Logcat is in attachment below.
UPDATE 12.02.27: I halt the project from now on. This is due to lack of time, skills, direction and motivation. I have other commitments in life as well. I might come back when I know more, but don't hold your hope.

---

You need the venue's kernel and ramdisk (which is implied as it's a major part of the kern).
If it is the stock kern that you're using, your system tree is missing other binaries.
Some devices are ported in exactly this manner, just inserting binary-only drivers into a generic/minimally modified CWM.
Your logcat is stating that the device is panicing as critical components are missing/cant mount all partitions
Code:
E/PrintK ( 1): <3>init: cannot find '/system/bin/lfinit', disabling 'lfinit'
E/PrintK ( 1): <3>init: cannot find '/system/bin/qmuxd', disabling 'qmuxd'
E/PrintK ( 1): <3>init: cannot find '/system/bin/DrmHost', disabling 'DrmHost'
E/PrintK ( 1): <3>init: cannot find '/system/bin/logd2', disabling 'logd2'
...
etc
anything marked as E/ is an error level message, as in 'serious error'
Some of the W/ and D/ level ones might be important too, but even in the stock rom there's plenty of warning messages that can be safely ignored.

---

Your logcat is stating that the device is panicing as critical components are missing/cant mount all partitions
Code:
E/PrintK ( 1): <3>init: cannot find '/system/bin/lfinit', disabling 'lfinit'
E/PrintK ( 1): <3>init: cannot find '/system/bin/qmuxd', disabling 'qmuxd'
E/PrintK ( 1): <3>init: cannot find '/system/bin/DrmHost', disabling 'DrmHost'
E/PrintK ( 1): <3>init: cannot find '/system/bin/logd2', disabling 'logd2'
...
etc
Click to expand...
Click to collapse
Well, I am aware of these missing files. I did get some of them back later, though, they still logged it as an error despite having found the files.
e,g,.
Code:
E/PrintK ( 1): <3>init: '/system/bin/logd2'
Something like that, I lost the log so I can't quote.
----------------------------------
You need the venue's kernel and ramdisk (which is implied as it's a major part of the kern).
If it is the stock kern that you're using, your system tree is missing other binaries.
Click to expand...
Click to collapse
I did screw this up a few times, but that one I used a boot.img that belongs to Venue itself, not the stock cm7.
---------------------
After some additional transfer, I ended up not being able to dump the logcat
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
reloc_library[1311]: 160 cannot locate 'android_log_setColoredOutput'...
CANNOT LINK EXECUTABLE
Well, guess I screwed up again. Probably will try again from scratch.

---

really appreciate your work, it would be awesome if cyanogen get ported for our venue

---

Tried Kitchen and it booted but did not last long enough for me to check around that much. Huge driver problems. Refer to update in the first post.

---

SwordLaker said:
Disclaimer: I'm a noob. This is my first attempt ever and even it doesn't sound that difficult, don't keep your hope high.
So what I intended to do right now is to use the CM7.2 RC0 KANG for Nexus One (which is currently my main daily use) as a base, which can be found here:
http://www.mediafire.com/?qac2glyh0egscb2
(Rationale: Dell Venue and Nexus One share the same chipset and GPU, and furthermore, I have assessed that build and found it stable enough to be ported)
Proprietary files and driver data from a working ROM of Dell Venue will then be transferred to replace the files in the base (which originally belong to Nexus One). What I have transferred includes:
---cut--
Click to expand...
Click to collapse
Hi Swordlaker,
I search many internet site how to build kernel & rom for dell venue. But so far no lucks. Build based on cm7 > passion > when running extract-files.sh (to pull neccessary file from live device -I flashed with many streakdroid4-250) I got this
Code:
[email protected]:~/cm7/system/device/htc/passion$ ./extract-files.sh
remote object '/system/bin/akmd' does not exist
chmod: cannot access `../../../vendor/htc/passion/proprietary/akmd': No such file or directory
remote object '/system/bin/parse_radio_log' does not exist
chmod: cannot access `../../../vendor/htc/passion/proprietary/parse_radio_log': No such file or directory
remote object '/system/etc/AdieHWCodecSetting.csv' does not exist
3 KB/s (255 bytes in 0.072s)
remote object '/system/etc/firmware/bcm4329.hcd' does not exist
remote object '/system/etc/firmware/default.acdb' does not exist
remote object '/system/etc/firmware/default_att.acdb' does not exist
remote object '/system/etc/firmware/default_france.acdb' does not exist
16 KB/s (1156 bytes in 0.069s)
130 KB/s (9220 bytes in 0.069s)
remote object '/system/etc/vpimg' does not exist
917 KB/s (84096 bytes in 0.089s)
2287 KB/s (162992 bytes in 0.069s)
5800 KB/s (1793168 bytes in 0.301s)
1732 KB/s (206768 bytes in 0.116s)
1072 KB/s (98264 bytes in 0.089s)
579 KB/s (42764 bytes in 0.072s)
remote object '/system/lib/libhtc_acoustic.so' does not exist
remote object '/system/lib/libhtc_ril.so' does not exist
3282 KB/s (468788 bytes in 0.139s)
1010 KB/s (102848 bytes in 0.099s)
[email protected]:~/cm7/system/device/htc/passion$
My understanding ... there are huge different on proprietary drivers between venue and passion [which is normal between dell & htc]. I think many of filename[DOT]mk need to be modified for successful build. Let us see the "wifi". Is venue using broadcom chipset? How to know what wifi chipset in the venue. I'm noob too in this android space.
after running extract-files.sh, here are the file extracted
Code:
[email protected]:~/cm7/system$ ls vendor/htc/passion/proprietary
AudioBTID.csv libEGL_adreno200.so libGLESv2_adreno200.so liboemcamera.so libq3dtools_adreno200.so yamato_pm4.fw
libcamera.so libGLESv1_CM_adreno200.so libgsl.so libOmxVdec.so yamato_pfp.fw