HTC opened source code of kernel 3.0.16 for One V. It's the same hardware based as our DHD. So I hope now devs can use it to make our custom roms to be fully functional with ICS 4.0.
Who is the first?
http://htcdev.com/devcenter/downloads
FireBlast said:
HTC opened source code of kernel 3.0.16 for One V. It's the same hardware based as our DHD. So I hope now devs can use it to make our custom roms to be fully functional with ICS 4.0.
Who is the first?
http://htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
good news
Sent from my Desire HD using XDA
cool wonder how long before we get a full working ics rom a day or two at most.....
It's not that simple.
While they share the same SoC, they do not have the same board, hence board config files.
The jump from linux 2.6.x to 3.0.x is huge and u can't simply bring in those missing board-spade*.c .h files from the old kernel and expect them to compile. You're going to get a whole lot of compile errors because the underlying linux kernel has gone through so much changes. It's a daunting and massive undertaking.
My money is on devs waiting for HTC to release DHD kernel source for ICS.
Related
I'm just curious what's usually involved. I know cyanogen mod does some custom things but ignoring those customizations, what is involved exactly in porting it to a device?
I would assume the major hurdle is driver support. As in the linux kernel compiled/used has hardware support for device x. But other than that, what else?
For ex, with the nook color, what is needed to port it? We can't expect a recent kernel for the nook color from barnes and nobles, but what about the existing kernel used in cm7?
Or if it's not just a kernel issue what are the issues/hurdles. I'm not a developer but just curious from a layman's point of view.
I would think if a working kernel is ready, wouldn't it be just a matter of compiling? I guess I'm curious as to why some say it takes a month or so.
First we need an upgraded kernel to even think about ICS. Then there will also need to be drivers written/rewritten for hardware acceleration and such. Also many other things that will need to be put together to compile even a semi-working rom.
---------------------------------
Sent from my LG Optimus V using Tapatalk
I hope by Xmas, CM team will prevail new ROM running ICS.
I don't care it called CM8 or CM9, as long as it's ICS supporting NC, I'm happy
Slight thread-jacking here, but somewhat related:
Kernel wise, what's the difference between an SDK port vs an AOSP port?
dormido said:
Slight thread-jacking here, but somewhat related:
Kernel wise, what's the difference between an SDK port vs an AOSP port?
Click to expand...
Click to collapse
The SDK is used by devs to create apps so only code relevant to having a semi- working simulator is present. AOSP is the full source code, witch includes everything but it is only built for one device, the galaxy nexus, so there is still much work involved in porting.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it
It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170
Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App
Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)
You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.
You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.
Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App
Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827
not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together
Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.
I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App
I've just seen the news about onskreen going multitasking,,,,,,went to download,,,,,,,,,,,but really I don't know what to download and how to use it on my TF101G
As far as i know:
Cornerstone is no app as you understand it. It is something like a "launcher".
The problem is that cornerstone has to be integrated into the os by the manufacturer himself because it has to be integrated deeply into the os.
So you won't see cornerstone on tablets unless a manufacturer decides to implement it.
Or someone takes the AOSP code from google and releases a complete rom. But i think that would be a lot of work. I don't think that someone would do this. It would be awesome to see this im cyanogenmod^^. I mean both are open source now.
Sent from my GT-I9000 using XDA App
I think I saw someone with a Xoom that has it.. (from Reddit). It would be awesome if we got it too.. I need to learn to make roms in my spare time.
it has to be baked into the rom its not a apk u run
I would love to try this too !
The "simple" way would be to get source from a rom, to integrate it and build the rom. But the integration step is unfortunatly not simply I think :/
Integrating difficulties is just one of the problems... for example Cornerstone requires ICS.. which we don't have.
asdfuogh said:
Integrating difficulties is just one of the problems... for example Cornerstone requires ICS.. which we don't have.
Click to expand...
Click to collapse
First ICS has to come out. Then we will gather our forces, go on our knees and humbly ask any dev to face the challenge and coock rom with Onskreen integrated. It will not be soon, but someday ... Hope never dies...
Since it's under the ASL, I hope that it's included into the official CM9 for the Transformer. If it is not, I'm sure that there will be unofficial CM9 roms with it. Now, Asus, release the ICS update for the Transformer we need the kernel sources and drivers...
Vyrlokar said:
Since it's under the ASL, I hope that it's included into the official CM9 for the Transformer. If it is not, I'm sure that there will be unofficial CM9 roms with it. Now, Asus, release the ICS update for the Transformer we need the kernel sources and drivers...
Click to expand...
Click to collapse
Steve Kondid stated he will work to get it into CM9 (that's if it come to the TF).
He has it running on his 10.1
"fat__tire: Just for fun... http://t.co/gLBPGYMW Sorta buggy but sorta cool. #nookcolor #cm9 #cornerstone"
--http://twitter.com/fat__tire/status/169628187347783681
well we got ICS. Anyone working on getting cornerstone working?
cmarticus said:
well we got ICS. Anyone working on getting cornerstone working?
Click to expand...
Click to collapse
First we need a stable custom rom then we need a normal version and a cornerstone version patience is a virtue
Sent from my Transformer TF101 using xda premium
^^ what he said but the expand on that we need a rom that is fully deodexed or one that has a full source code available so that it can be baked in without signature errors + we need a apk dev and a rom dev (Or one that can do both) to put it all together
GOOD NEWS !!
Ok, so i spent a few bucks and increased my RAM, which is enabling me to at least make complete builds of source, and i also got my usb repaired.
I made the first build of AOKP.
It DOES NOT boot (x10) as of now.
I just merged freexperia's device trees (of CM9) into the aokp source tree and made a build.
here is the first build for x10
http://bit.ly/x10aokp1
also the first build for arc (lt18/lt15) {i do not know if it boots, as i don't have an arc to test}
http://bit.ly/arcaokp1
if any good rom cook is interested, you can try PORTING using files from these builds onto CM9 builds. {with credits}
(the apps will defiinitely work, the framework might or might not, port libs and bins intelligently, i have not much idea about porting aosp based roms)
i am very very new to the scene, and have extremely nominal programming knowledge, and i do not know where this project will take me, but i will not give up without a fight
more builds will come up soon
debugging is a pain in the a$$ because the android gadget is broken in kernel (that's for x10, for arc, i do not even have the device) and thus i cannot do the good old "adb logcat" to find errors.
once i get the arc build up, i might think or other devices too, but for now i ca nconcentrate only on arc and x10
Why create another thread? http://forum.xda-developers.com/showthread.php?t=1677853
for the thanks?
xPlayGunZ said:
Why create another thread? http://forum.xda-developers.com/showthread.php?t=1677853
for the thanks?
Click to expand...
Click to collapse
that was for cm9
and maybe yes for the thanks... you can think that way if you want
Sent from my X10i using XDA
Well done dude
The Alpha build works fine for me and for me its faster and better than CM9.
AOKP for X10!!!!!!
Wow! Finally! AOKP for X10! Go for it Champ!
--------
Google is releasing 4.1 goodness... what does it mean for our tablet who just got creamed
buzzmcfly said:
Google is releasing 4.1 goodness... what does it mean for our tablet who just got creamed
Click to expand...
Click to collapse
It means nothing yet, as we still dont have ICS Source and with out it no proper wifi or screen and a few other things, I can build a JB rom but it will be full of bugs at best.
I am talking a build with a fresh kernel. Using the current one might work and then it might not. I would like to be able to do a full rom not just an Install stock ICS and flash over tht as that may also cause problems.
Bottom line we need source.