Related
Hey, new to the forums, recently purchased a GSM Hero.
I have done some development for free software (think freedom, not price) projects, and have become accustomed to git repositories and structured development.
Upon entering the world of custom Android ROMs (at least Hero ROMs) I have been sorely disappointed with the development practices going on, releases on file sharing sites and the like.
On top of this, none of the ROMs available suit my needs.
This is all fine, as I'm not developing those ROMs.
I have decided that I need to start working on my own custom ROM, however guides and documentation regarding this process are in short supply.
It would be much appreciated if someone could link me to some guides to starting my own custom ROM.
I intend it to be a light vanilla ROM, with none of the bloat that seems to perpetuate other ROMs, I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC
naivemonarch said:
I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC
Click to expand...
Click to collapse
Have you tried this one ? >[2.1] aychteesees-vanilla-cupcake< NOT the [3.0.1]verison ..this is still @dev
http://android.modaco.com/content/h...96/3-0-1-aychteesees-vanilla-cupcake-rom-gsm/
Give it a try [2.1] ! and tell us how it went ...
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.
I'm downloading 3.0.1 as we speak, however I'd still like some resources on making my own ROM.
I'm interested on this documentation too....thanks
naivemonarch said:
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.
Click to expand...
Click to collapse
That's weird , I have used almost everything ( apps ) with that ROM [2.1] ... and never get FC's
Did you flashed from Zero .. I mean with all he possible wiping . inlcuding SD ext partition wipe
???
That is a MUST ..!
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
FunkTrooper said:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
Click to expand...
Click to collapse
There's Paul's (modaco) online kitchen, but if you want to compile by yourself, there's a plethora of gits on github (cyanogen, lokx, kiall to mention just a few).
Good question. Yeah it would be nice if there was a 'Cooking Class' thread on this forum like in some of the other forums. There is a decent tutorial however at HTCpedia.com under the HTC Hero ROM Development section, it's in the stickies there. However, I still have questions and that forum is not visited as much as xda.
Link to cooking thread:
http://htcpedia.com/forum/showthread.php?t=1404
FunkTrooper said:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
Click to expand...
Click to collapse
As a start, I would read that thread I just linked above. Once you can dump the contents inside the system.img and then combine it with the boot.img to build an update.zip, then you are already halfway there - that's actually fairly easy. But knowing how to add custom kernels to the update.zip, making the custom ROM rooted, etc. are all stuff that I'm still working on. There's supposed to be a lot of info in the Dream/Magic forums, so I'll keep reading.
Android is still fairly new and very few people know how to use Linux, thus there's less support and less interest in wanting to cook for one's own Android device.
BTW, that thread I linked above is also found here.. Doh!
http://forum.xda-developers.com/showthread.php?t=551711
Thanks for the link, a good read.
Anyone know what the process is for using a custom kernel? There are a few things I'l like to enable that aren't in the HTC kernel (like FUSE).
naivemonarch said:
Thanks for the link, a good read.
Anyone know what the process is for using a custom kernel? There are a few things I'l like to enable that aren't in the HTC kernel (like FUSE).
Click to expand...
Click to collapse
If I eventually manage to find out I will post it here. My most important concern is making a rooted ROM from those shipped ROMs, as some people have been doing here.
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
You could start with building ROMs from Oxygen or CM source. That way you can familiarize yourself with the AOSP project without worrying about drivers etc. (DevNull source is completely stock AOSP with drivers for the Desire etc.)
Later on, when you know how everything works, you can start your own project.
If you want to start building AOSP from Google source, you might want to read the tutorials over at Google for a couple of times + checking the wiki's over at CM. They pretty much explain everything that there's to it.
If you're looking for a guide specific for the HTC Desire, then I think you're out of luck. Most dev's over here start off with the tutorials over at android.com and even with tutorials etc. at CM.
Is DevNull definitely 100% AOSP + drivers? If so, then it would be pointless compiling from source anyway.
I already ran that through dsixda, but the options there are quite limited.
What I had hoped I could do was make a tiny tiny AOSP. DevNull is pretty small though, so maybe it can't get much smaller.
rootSU said:
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
Click to expand...
Click to collapse
Hi Dan, for a start, the best place to start would be building a Cyanogen Rom from source as per Cyanogen's guide here. This guide is specific for the Desire
My suggestion is to build/modify this source first, since it's actively supported by a community. Once you get a fair idea, you could move on to the vanilla source..
Btw..Linux knowledge isnt crucial for building it, and you can easily follow the guide
Edit: Oops, just reallized that I just mirrored Pyr0wl's advice
Hello Guys,
I am a developer of windows apps and I also do some web development stuff. I have also for the last couple of weeks been playing around with the android SDK and building apps for my phone. I have wanted to get into kernel development for my device, but I have had trouble finding a good place to start. I know I can follow the google directions and build a kernel, but that may not be specific to my device.
I was first wondering is there a kernel (Perferably AOSP like Cyanogenmod) that i can compile just get used to the build process. I belive I have already found that, it being this kernel right here:
https://github.com/CyanogenMod/android_kernel_samsung_smdk4412"]https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
(Sorry, Im under ten posts.)
But this is where the confusion starts for me. I see this as a base of a lot of kernels for the note 2, but I notice the kernel is for the Galaxy S3. So in short, is there a good way to start learning how to build and modify android kernels for my Note 2? If so, do you have any recommendations on what kernel to base of of, or any tips or tricks, or etc?
PS: I am a "Newbie" by the forum standards so i can't post in the dev section.
R3liant said:
Hello Guys,
I am a developer of windows apps and I also do some web development stuff. I have also for the last couple of weeks been playing around with the android SDK and building apps for my phone. I have wanted to get into kernel development for my device, but I have had trouble finding a good place to start. I know I can follow the google directions and build a kernel, but that may not be specific to my device.
I was first wondering is there a kernel (Perferably AOSP like Cyanogenmod) that i can compile just get used to the build process. I belive I have already found that, it being this kernel right here:
https://github.com/CyanogenMod/android_kernel_samsung_smdk4412"]https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
(Sorry, Im under ten posts.)
But this is where the confusion starts for me. I see this as a base of a lot of kernels for the note 2, but I notice the kernel is for the Galaxy S3. So in short, is there a good way to start learning how to build and modify android kernels for my Note 2? If so, do you have any recommendations on what kernel to base of of, or any tips or tricks, or etc?
PS: I am a "Newbie" by the forum standards so i can't post in the dev section.
Click to expand...
Click to collapse
You might want to start here http://forum.xda-developers.com/forumdisplay.php?f=1896
Check the Matrix thread, devil kernel and Garwyn's experimental kernel thread. These might give you some ideas
davidh59 said:
You might want to start here http://forum.xda-developers.com/forumdisplay.php?f=1896
Check the Matrix thread, devil kernel and Garwyn's experimental kernel thread. These might give you some ideas
Click to expand...
Click to collapse
Thanks! I have been testing around, but two problems have come up,
I have searched multiple threads and got as many dependencies as I could, but I still needed the toolchain. I got the android NDK, and used this guide:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
I used the arm-linux-androideabi- toolchain, is that ok? Even if it is, is there a better or recommended tool chain?
Another problem I had is when compiling the source I got a "error unknown pseudo-op .arch_extension" when it was compiling the devices section of the kernel.
Any thoughts and help would be appreciated.
Cheers,
R3liant
Hi guys- I have seen a website or page on how to build your own rom.
how difficult is it on 1 to 10?- 10 being very difficult.
what tools do I need?
many thanks
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
building your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
creating your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
htc_desire_luke said:
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
Click to expand...
Click to collapse
any software needed ??
htc_desire_luke said:
any software needed ??
Click to expand...
Click to collapse
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
There is an entire section dedicated to this subject, found in
creating your own rom
paolo-red1 said:
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
Click to expand...
Click to collapse
sound very difficult-
my laptop is running linux and i think 64bits- I am running opensuse 12.1 KDE
but thats all i know
will have to do some more reading on this, I dont think I will be able to just pick it up and go.....
You are kiddin' me
Enviado desde mi HTC Desire
creating your own rom
Jack4L_ said:
You are kiddin' me
Enviado desde mi HTC Desire
Click to expand...
Click to collapse
what do you mean Im kiddin you?
Good morning,
as per thread title I'm trying to build my first custom ROM.
As it is my first time ever trying this, instead of starting from scratch I decided to port an existing ROM to our device.
I decided to go for Paranoid Android (AOSPA) ROM, for two reasons: I previously used and liked very much the KitKat version, and there is currently no port of this ROM.
I read a lot of guides on how to do this, and while I learnt a lot, I'm still not quite sure on how to properly do this. So I thought I might ask for some help.
What I learnt so far is this:
1) Fork Paranoid Android's manifest and add compatible device and kernel repositories (I chose @MWisBest's device repo)
2) Fork Paranoid Android's vendor_pa project and add device support
3) Fork device tree and adapt some makefiles
What I still don't quite get is:
1) Apart for device-specific fixes, is this enough to TRY a build?
2) Regarding device, are there some specific fixes to make a working ROM? (e.g. I knew something about block-based OTAs so I disabled them following ParanoidAndroid's change #68 on Gerrit)
You can see my work on GitHub, search for my username Bruno3589 (I'm not allowed to insert URLs right now, I need to make >10 posts).
I'll try a build ASAP, but it might take a while since I'm limited in terms of internet connection and time.
Any help or suggestion is really appreciated!
Thanks in advance and have a good day
P.S. I know MWisBest's device unifies all variants (tuna) instead of making separate ones (maguro,toro,toroplus), I thought it would be useful to have a single build.