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
I'm a new one for G1,recently,I want to compile a ROM for G1.i want to know the step that compile the ROM for G1. thank you.
This should help you get started... http://source.android.com/source/initializing.html
thank you,I will try it
Also, these can help:
forum.xda-developers.com/showthread.php?t=969266
wiki.cyanogenmod.com/wiki/HTC_Dream_%26_Magic:_Compile_CyanogenMod_(Linux)
I'm pretty sure cyanogenmod 6 source is broken
Sent from my HTC Dream using Tapatalk
OK, so so here is a thought. Since the stock ROM for the I9500 and the Korean SHV-E300 has all of the lib files necessary for creation of a ROM, why doesn't someone just use those to try to port a ROM over to see how it would actually work? I just came from the Exhibit 4G and that is pretty much how our device tree was created. Using other phones and our own libs. I know it would take a dedicated dev to do this or attempt it. But in the end it should be very rewarding. Tell me what you guys think.
Sent from my SHV-E300K using Tapatalk 2
lunerceli said:
OK, so so here is a thought. Since the stock ROM for the I9500 and the Korean SHV-E300 has all of the lib files necessary for creation of a ROM, why doesn't someone just use those to try to port a ROM over to see how it would actually work? I just came from the Exhibit 4G and that is pretty much how our device tree was created. Using other phones and our own libs. I know it would take a dedicated dev to do this or attempt it. But in the end it should be very rewarding. Tell me what you guys think.
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
+1
any dev that can verify this ? possible or not ? any port rom would do Ex. MIUI Rom
It is kind of like porting but not really. It would be using all of our already made drivers that are in .so format and then using partial or full frameworks from the custom ROM sources to build. Just look at it like taking Ubuntu 13.10 and running Gnome 3.8 on top of it as the shell. Neither one of them get along with each other but there are ways to make them coexist and work well together.
Sent from my SHV-E300K using Tapatalk 2
CLOSED
reserved
reserved #1
Quick Porting
reserved
reserved
Reserved #2
Reserved for OP
Reserved for OP
All questions are allowed! :good:
I'll give it a try when I get home
Edit : @arDroid.99 can you also use 7zip on windows or just winrar ?
Sent from my Galaxy Nexus using Tapatalk
gamerman123x said:
I'll give it a try when I get home
Edit : @arDroid.99 can you also use 7zip on windows or just winrar ?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
yeah, 7zip will work too My instructions for ziping and unziping are based on winrar.
updated:highfive:
Thanks this worked like a charm for porting 4.4 Roms :thumbup:
Sent from my Galaxy Nexus using Tapatalk
gamerman123x said:
Thanks this worked like a charm for porting 4.4 Roms :thumbup:
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yep, Its the ultimate guide:laugh:
Hey man =) firstly i really like to say thanks a lot for the guide. but I have an issue. I tried to port GS3 CM10.2 4.4 rom to HTC one x CM 10.2 RC1 rom. Even i tried your 2nd section I'm still stuck at boot loop. the closest phone is one x+ and it has only aosp 4.4 so i can't use that. by displays GS3 sounded much better and i tried that. I'm still stuck. Was i supposed to use something else instead of another CM kitkat rom? Thanks!
can someone do this to SU760 i had a hard time doing this bunch of our PRO dev just leave
Sent from my SU-760
Lg Su760
Rom: AOKP JB
Alcatel OT-995
Rom: CM 10
ereneren564 said:
Hey man =) firstly i really like to say thanks a lot for the guide. but I have an issue. I tried to port GS3 CM10.2 4.4 rom to HTC one x CM 10.2 RC1 rom. Even i tried your 2nd section I'm still stuck at boot loop. the closest phone is one x+ and it has only aosp 4.4 so i can't use that. by displays GS3 sounded much better and i tried that. I'm still stuck. Was i supposed to use something else instead of another CM kitkat rom? Thanks!
Click to expand...
Click to collapse
Yeah, this guide will work on 4.3 cm10.2 and any 4.0+ rom( only difference is the priv-app folder). The reason of your issue may be because the device your porting from. I here alot of people port gs3 roms using the nexus 4. Try using the nexus 4.
And remember to use stable roms. Roms that are like in alpha stage my not be able to port saying some apps, permission,etc still relies on unneeded libs.
thank you.I will be try.You are maked a very good work.Thanks again.
arDroid.99 said:
Yeah, this guide will work on 4.3 cm10.2 and any 4.0+ rom( only difference is the priv-app folder). The reason of your issue may be because the device your porting from. I here alot of people port gs3 roms using the nexus 4. Try using the nexus 4.
And remember to use stable roms. Roms that are like in alpha stage my not be able to port saying some apps, permission,etc still relies on unneeded libs.
Click to expand...
Click to collapse
hey man. I tried stable rom this time. I used CM 10.1.3 as base (device is endeavoru) and I used crdroid CM11 rom from mako (nexus4) but with or without the fix it doesn't boot I'm always stuck on boot logo. can you give a link for porting which would be best? Thanks a lot!
ereneren564 said:
hey man. I tried stable rom this time. I used CM 10.1.3 as base (device is endeavoru) and I used crdroid CM11 rom from mako (nexus4) but with or without the fix it doesn't boot I'm always stuck on boot logo. can you give a link for porting which would be best? Thanks a lot!
Click to expand...
Click to collapse
Your base isn't the same android version as your port ROM.
Cm10.1 is 4.2
Cm11 is 4.4
Sent from my GS3 on 4.4 KitKat using Tapatalk 4
ebildude123 said:
Your base isn't the same android version as your port ROM.
Cm10.1 is 4.2
Cm11 is 4.4
Sent from my GS3 on 4.4 KitKat using Tapatalk 4
Click to expand...
Click to collapse
yeah, you right!:laugh: I didn't read that response correctly, I must have been distracted:silly:
After doing this which the rom I ported boot normally and everything seen to work exceptfor the settings app. I get a Unfortunately, Settings Has Stopped error once I hit settings. What can it be?
SVLAN said:
After doing this which the rom I ported boot normally and everything seen to work exceptfor the settings app. I get a Unfortunately, Settings Has Stopped error once I hit settings. What can it be?
Click to expand...
Click to collapse
This isn't a cause of the guide and congratulations. First, what rom did you port and what did you use as base? Like the devices
Hey guys,
I've set up an organization on github und uploaded my config there.
Could you please provide me your github usernames via PN so I can add you to the team?
Thanks,
Daniel
Doublepranks. But I just wanna join for learning if you would let me in....
Sent from my XT1033 using Tapatalk
swordrune10, don't have a moto g yet but most likely getting one for xmas
Sent from my Galaxy Nexus using Tapatalk
Josalaito, i'm working in cm 10.2 now, and i think we need a hard work because msm8x26 is not fully supported by cyanogen and we need to use 8960(The same happened in my old y300 cm doesnt support 8x25 and we use msm7x27a)
Hi, my username is debaj, I hope I can help anything as a geneal Android developer since I have no experience in ROM development except building Cyanogenmod for my old Nexus S
My Username on github is: denizkoekden
Regards,
Deniz
Still don't have a Moto G but wanna buy one for christmas...
My username on GitHub is: Lopicl
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
immortal_yash said:
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
Click to expand...
Click to collapse
I think it's best to begin with msm8226 from the outset rather than trying to kang a different board
I'm seapoint on Git by the way. https://github.com/seapoint
My Moto G arrives Tomorrow
too bad I won't have time to do anything
I am Scrizz on github
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8926 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
7alvi reporting for call of booty..jk
Count me in. Will be getting mine by January (most likely) and for my work I have built Carbon, Mokee, Slim, AOKP, baked, anir, etc etc for HTC Pico..!
kaliberx said:
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8626 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
Click to expand...
Click to collapse
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
immortal_yash said:
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
Click to expand...
Click to collapse
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
kaliberx said:
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
Click to expand...
Click to collapse
try using mine or alpha or any pre started device tree willl save you some time
BTW any knows which audio blob is being used in Motog?
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
a1Pha said:
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
don't worry, I got u
Sent from my Nexus 7 using Tapatalk
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Lopicl.00 said:
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Click to expand...
Click to collapse
we really do need a kernel tree and if someone could pull the prop files that would be great
Sent from my Nexus 7 using Tapatalk
If you want, you can fork my kernel project.