Quote:
Originally Posted by spectheintro
ACL can you explain what this means? Are there multiple Android ports for the TP2? I know that neopeek is a mod of Cyanogen (a separately developed project), but I thought all TP2-related things were universal. Does neopeek use drivers/code that you guys don't?
|
Before i answer this.. i finally got that beotch to run. Had to run it on my old sense ui build. Runs a lil slow and the background is not displaying properly (just white background). but its playable and i actually did well ..lol.. it is using hardware 3d
Logs dont show why the background is not working but i will need to find out if the Hero/Eris have no issues with it. If they dont, then we have to look further into our gralloc code.
hmm now to answer your question. Before i dive in you need to understand that there is 2 big components to get android to run. First is the kernel of course. Without it nothing is possible, its the underlying system that deals with the hardware. Kernel's have their modules that we also control that handle things like wifi and other devices. Then comes the big gorilla android itself. Android comes almost ready to run with a few exceptions that are missing so the vendors can customise it to their needs.
Ok now that we straightened that out i can tell you for a fact that we "htc-linux.org" group are the only ones that i know who develop for the rhod/topaz and other msm7k devices. You can search all the web and i assure you that our kernel is 100% homegrown our of our home pcs. So does neopeek use our kernel, yes he does because no one else makes one. Cyanogen repo last we checked had no info about any of the devices we work on and why would they? they are busy making android for devices that already have kernels made. Sure a few tweaks here and there but nothing like reading assembly all day and reverse engineering bits and pieces the kernel. I know they have a big dev team so it would be great if we could work with them but i doubt it since they have other devices to support.
xdandroid is our version of android straight from google. Stinebd and gang handle all that good stuff for our devices because once again, no one else does. Neopeek uses some of the xdandroid drivers like the essentials "libhardware legacy", gralloc and the RIL and there are a few others that have to be custom made by the vendors. But the android build itself is different. It can have different setting enabled or have customized ui
hope that answers it.. now back to some angry birds with no background