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
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
What is a kang?
A kang is a rom who uses its source from another project and build upon it. Most the time to personalize it (only add to the original code) and other times to eventually improve (go back and change code) on the original work like CyanogenMod does.
Example.
Google made Android Open Source Project.
CyanogenMod is a Kang of Original Android.
MIUI is a Kang of CyanogenMod.
Thanks.
So how do I kang? (Without knowledge of android development)
setup build env
get a coffee
pull source by syncing with sbloods tree
make ur changes to the source
get a coffee, build. enjoy coffee
read sbloods rom/source thread.
Sent from my HTC Glacier using xda premium
smirkis said:
setup build env
get a coffee
pull source by syncing with sbloods tree
make ur changes to the source
get a coffee, build. enjoy coffee
read sbloods rom/source thread.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
But doing all of that requires knowledge of Android Development... (except the coffee part)
you need at least basic knowledge.
well another option is downloading the Rom and just removing and adding files. read so you don't delete something important though
--sent from my glacier.
Or just use Cyanogen Compiler...
Easy way to make a CM Kang
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.
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
Herewith I have enclosed the link of kernel source file of h60 device from the emui website http://emui.huawei.com/en/plugin/hwdownload/detail?modelld=70 (opens in desktop only)
http://emuirom123.dbankcloud.com/H60_kernel.tar.gz
Alternate link for the file: https://uptobox.com/udvb2m1mujxr
Is that enough to build the AOSP based custom rom or cyanogen rom ?????? @codeworkx
codeworkx wont be providing development too much hassle for him as he has little spare time and the phone is 2 years old now. there is a unstable aosp rom
https://forum.xda-developers.com/honor-6/development/h60-mm-emui4-source-t3447862
jkccl9 said:
codeworkx wont be providing development too much hassle for him as he has little spare time and the phone is 2 years old now. there is a unstable aosp rom
https://forum.xda-developers.com/honor-6/development/h60-mm-emui4-source-t3447862
Click to expand...
Click to collapse
I am not forcing codeworkx...I am asking someone to build cm or aosp rom..Above file is the correct kernel source file or not ????
enba.kpm said:
I am not forcing codeworkx...I am asking someone to build cm or aosp rom..Above file is the correct kernel source file or not ????
Click to expand...
Click to collapse
dont have a clue, supports pretty dead and there is an unstable aosp ^^