Related
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
Hi,
Is there any ICS rom for Vibrant which is open source?
I have looked the passion and other ROM, I dont' think they are open source.
Is there one which I can download and built the ROM myself?
Thank you.
Not sure but all of them should be open source. just give credit where it's due and that should be good
Sent from my SGH-T959 using xda premium
When CM9 is out, it will all be on github, so you can pull and build it.
ICSSGS and Passion both (I think) claim to be open, but the proof is in looking for their sources and trying to build.
test.im.09 said:
Hi,
Is there any ICS rom for Vibrant which is open source?
I have looked the passion and other ROM, I dont' think they are open source.
Is there one which I can download and built the ROM myself?
Thank you.
Click to expand...
Click to collapse
Code Name Android is open source and currently has device trees for the Galaxy Nexus and Nexus S. There is no Vibrant device tree yet. Whenever I can get back to civilization my goal is to build one then to compile all from CNA source.
Onecosmics is open in the sense that they give you all the files that you need to build from the aosp device tree, AOKP and cm9 are also open.
Any of Neo's roms are not open source, nor does he even bother to respond to a PM about the device tree
Hi
I am trying to put together a really good 2.6.35 kernel so we can have a stable CyanogenMod 7.2. I am using TomGiordanos source here:
https://github.com/TomGiordano/kernel_huawei.git
and building off the 2.6.35-ICS branch using the .config from the b5xx kernel here:
http://forum.xda-developers.com/showthread.php?t=1653699
I got the source to compile and it all seems to work quite smoothly. It has a couple of issues though. Biggest is that the wifi just gives an error when trying to turn it on. Next is that the key brightness does not work, but I think I know where the problem is with that. Any help to get the wifi going would be awesome for a start though.
PaulMilbank said:
Hi
I am trying to put together a really good 2.6.35 kernel so we can have a stable CyanogenMod 7.2. I am using TomGiordanos source here:
https://github.com/TomGiordano/kernel_huawei.git
and building off the 2.6.35-ICS branch using the .config from the b5xx kernel here:
http://forum.xda-developers.com/showthread.php?t=1653699
I got the source to compile and it all seems to work quite smoothly. It has a couple of issues though. Biggest is that the wifi just gives an error when trying to turn it on. Next is that the key brightness does not work, but I think I know where the problem is with that. Any help to get the wifi going would be awesome for a start though.
Click to expand...
Click to collapse
Here you can find some changes from Bukington. Has the same base from TomG.
demolition23 said:
Here you can find some changes from Bukington. Has the same base from TomG.
Click to expand...
Click to collapse
Buckington is pushing to the TomG source repo. Wireless is fixed if I build against their cyanogenmod_u8800_defconfig instead of the config from forumbers kernel he found. HDCRJacob had made a commit which forced the wifi to enable in the cyanogenmod defconfig and another file.
Now we have other problems like camera, light sensors and maybe some other stuff if I use their defconfig. Kernel building is fun...
See here:
http://forum.xda-developers.com/showthread.php?t=1891281
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei
My Kernel Source:
https://github.com/PaulMilbank/kernel_huawei/tree/cm7-u8800-35
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
PaulMilbank said:
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei.git
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
Click to expand...
Click to collapse
Camera issue??? Please, any issues but camera
»»Sent From My U8800««
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
PaulMilbank said:
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
Click to expand...
Click to collapse
You can use VictorTeam's source.
forumber2 said:
You can use VictorTeam's source.
Click to expand...
Click to collapse
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
They have github group https://github.com/Victor-android
.35 kernel based CM7.2 would be pretty dope to me, especially if tethering works
PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
here:https://github.com/Victor-android/kernel_huawei/tree/2.6.35-cm-u8800
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Nice to hear that someone's still working on U8800's .35 kernel. Good job so far!
PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Do you use your vendor files for compiling CM7?
forumber2 said:
Do you use your vendor files for compiling CM7?
Click to expand...
Click to collapse
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
PaulMilbank said:
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
Click to expand...
Click to collapse
But you could compile kernel?
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Will you try your luck with cm9/10?
PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
if you send vendor files to me,i can compile in my free time
forumber2 said:
if you send vendor files to me,i can compile in my free time
Click to expand...
Click to collapse
Maybe Ezets here:
https://github.com/ezeteze/android_device_huawei_u8800.
Not sure otherwise. I don't have any vendor files sorry.
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Unrealized said:
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Click to expand...
Click to collapse
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
forumber2 said:
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
Click to expand...
Click to collapse
Guess it has something to with the "new" Adreno drivers. Might do some benchmarking later with the older ones. I haven't really experienced lagging myself though. it's kinda the same as w/ .32 based CM7 (especially when using ADWLauncher)
I am about to build a kernel for N8000. But my problem is I can not download from samsung open source site (Very Slow Connection).
Can someone please mirror the update7(MD1) for me on a fast server like dev-host, android file host, mediafire or etc...?
Here's the Samsung open source site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8000
Thanks in advance.
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
kcrudup said:
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
Click to expand...
Click to collapse
Thanks.
I have two questions if you don't mind.
1. Merge-to-ss-jb is the latest source (MD1)? Is it a good to go for a kernel to be based upon?
2. Is it alright with you that I base my kernel on your own kernel?
I appreciate it if you can help me with some kernel stuff as I am new to this.
Sent from my HTC One X using Tapatalk 4 Beta
csec said:
"merge-to-ss-jb" is the latest source (MD1)?
Click to expand...
Click to collapse
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Is it alright with you that I base my kernel on your own kernel?
Click to expand...
Click to collapse
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
kcrudup said:
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
Click to expand...
Click to collapse
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
csec said:
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Heard that the published sources have different wi-fi drivers than preinstalled stock kernel.
This is the main reason of allshare cast not working with custom kernels (on the contrary, some s3 custom kernels DO SUPPORT allshare cast), even if status=official and flash counter=0.
Anyone can confirm?
Anyone has the proper ones or know which one (i.e. from a different samsung device) to use?
gitHub link dead