Hello all,
I would like to build a 2.2 rom for the edge, but given my limited understanding of kernels and source codes, i have come here to ask for assistance!
What I have:
full copy of my current edge safely burned onto a disk for safe keepings
a computer running the latest ubuntu with:
android sdk (all)
JDE and JDK 5 and 6
eclipse
a copy of the Dingo source code which was posted yesterday
finally, my Edge (universal android rooted edge with Dingo and the SuperUser posted by androidpolice)
What I want:
2.2 android for
flash support (NPR.org is my must-have flash site ><)
Speed increase
better battery life
What I was planning:
I have been reading around, and see a couple options:
1. create my own update.zip
2. flash over the system and data with custom files
The problems I see:
1. Update.zip - the update folder is a compilation of many little folders, including 2 system folders. I assume system1 is the eink system and system2 is the android, but from my edge's file structure it looks like they both combine into one system structure during update. My problem, I don't have a complete grasp of the update.sh file. But my guess is change system2 to contain framework and core of 2.2 and then change update.sh to make sure all the components are part of the update(that is, 2.2 and ee UI eink programming) Am i anywhere close on this?
2. Flashing- From what I have read, this seems the easiest way to brick a system. But potentially this could also be the easiest to update the folders and files required for 2.2. Possibly as easy as entering debug password, hooking up usb, and entering "./adb sync" (if i set up the proper android source on my workstation). I worry that because of the "gimped" adb bridge (jcase mrspaceman and robot speak of this) flashing this way wont be possible either. again, is this a workable understanding?
This project has kind of become all-consuming for me, so i'll probably start testing these methods soon and hope for no brick. But before i take the jump, I decided to look for input here
thanks all!