Hi all,
I was wondering how people creates custom ROMs. Does it work (more or less) like unnattented install of Win xp (with nlite software for example), or like custom Ubuntu CD images?
I would like to create my own rom (with a bunch of friend), but I don't know where to start, and what skills are required (programming, or just good computer / software knowledge?), etc.
If anyone can help me, and give me some hints / tutos, I would be very happy!
Thanks in advance.
Nesousx said:
Hi all,
I was wondering how people creates custom ROMs. Does it work (more or less) like unnattented install of Win xp (with nlite software for example), or like custom Ubuntu CD images?
I would like to create my own rom (with a bunch of friend), but I don't know where to start, and what skills are required (programming, or just good computer / software knowledge?), etc.
If anyone can help me, and give me some hints / tutos, I would be very happy!
Thanks in advance.
Click to expand...
Click to collapse
Since HTC hasn't released the Hero kernel source, creating custom rom's will be quite difficult. But if you want to try on porting rom's from sapphire 32a roms or make a quick dirty rom check these threads:
http://forum.xda-developers.com/showthread.php?p=4391033#post4391033
http://forum.xda-developers.com/showthread.php?t=541522
Related
Android is a new open source mobile operating system that Google developed and an SDK has just been made available.
It would be great to see this ported to the Universal if its possible.
I don't see why it would not run since the Universal can already run Linux (to some extent) and Android is just based on that. Whether and to what extent the hardware can be supported is another question that only our programmers can answer. As we can surely count HTC out on supporting their legacy devices it might not be worth anybodies time in the end.
SDK for Android would not help at all. It is just a set of headers and import libraries. To port something to a device you need complete source codes of its kernel, software, etc. Even more - we don't know hardware requirements for Android. It may require the NOR flash to run from it - and we don't have it on our device at all.
mamaich said:
Even more - we don't know hardware requirements for Android. It may require the NOR flash to run from it - and we don't have it on our device at all.
Click to expand...
Click to collapse
Nobody uses NOR these days, it's too expensive and provides no real
benefit over NAND. The XIP days are over.
I hate java with passion, but i don't see any reason why Android software
will not be running on the universal.
Any news? I mean: can Universal run an Android ROM?
I saw something on tytnII, is there an hope?
can anyone confirm if android requires a customised hardware or minimum requirements....
By The Looks Of It I Shouldnt See Why Not...
I Saw That Video Of It On The Tytn And It Looks Like Its Just A Linux Based Kernel Booting Though Haret.
Theirs Already Some Pretty Good Progress With Linux On The UNI And I Dont See Why It Shouldnt Be Possible To Patch This Up. (Wish I Could But Im Not A Linux Coder )
maybe something like this
(click on the emote)
could be done for univ.
Getting A Replacement
I Get My Replacement XDA Exec On Monday Hopefully So Ill See If I Can Do Anything. No Promises Though
Regards,
OllieD
It looks promising but I am also awaiting the Ubuntu Mobile edition for PCC: it looks awesome!
if it has to run java bytecode
hi a .CAB solution should be possible. tis my prefered choice at present. KVM with class jar anyone??
any news ?
Kaiser can run Android, any ROM for Uni?
In this thread we have Android ported in to a Kaiser, hope someone is working on an Android ROM for UNI!!
It looks very nice the interface
Does anyone knows more info about this?
Thanks
Gracias
Any news on Android for Uni?
I've been trying to get it to work on my ELFin too, but i gave up when i only managed to get the Linwizard running without startx... (i dont know how to telnet and startx -.-)
Any news on this?
I'm thinking of getting a universal but i'm gathering info on it atm!
Has anyone been able to get some real progress on this matter?
I installed this onto my main memory, but when I run it I get a blank screen and the phone vibrates continuously, what am I doing wrong? I think this version is supposed to work on the Universal.
hye !
i also tried to install android on my universal, but it didn't work at all, i only had a black sreen and it vibrate without stopping. if someone has an idea, or a new thread were we can find out a running android os for uni... i take it !
Very keen on this
Is there a project? .. I'm a developer and would be willing to assist, but i haven't got enough experience with these devices to start the project off myself...
Count me in as a beta tester
It would be great to have Android on Uni!!
So this news means that very soon developers can start working on android to be ported on other devices!!!
http://android-developers.blogspot.com/
Hi everyone. I'm a long time observer on xda (from win mo) but am very new to android. While I'm familiar with my device and the basics, I'm very unfamiliar with android terminology. For example, I'm eager to try some of the themes I see here but don't know which files to download as they are all labeled for cm6 only, etc. and then I see they need to be "flashed".
Can someone explain the language of the elites pertaining to android please? I'm assuming they are all codes for different roms, etc.
Fyi, I have an evo running froyo, not root or anything. Everything up to date as supplied from htc/sprint
Thanks in advance
cm6 is for this ROM:
http://forum.xda-developers.com/showthread.php?t=735596
the "zip" files will work with most any ROM as long as you stay with in the OS version. Much like WM 6.1 themes would not work in 6.5. SO Android 2.1 themes will not work Android 2.2 (aka FroYo). Of course some things like Kernels are designed for certain ROMs. Like a kernel for Freshs ROM vs. a general population.
PPCUserT said:
Hi everyone. I'm a long time observer on xda (from win mo) but am very new to android. While I'm familiar with my device and the basics, I'm very unfamiliar with android terminology. For example, I'm eager to try some of the themes I see here but don't know which files to download as they are all labeled for cm6 only, etc. and then I see they need to be "flashed".
Can someone explain the language of the elites pertaining to android please? I'm assuming they are all codes for different roms, etc.
Fyi, I have an evo running froyo, not root or anything. Everything up to date as supplied from htc/sprint
Thanks in advance
Click to expand...
Click to collapse
you need to be rooted to apply themes and ROMs. Currently though, there is no way to root if you already have Froyo.
Flashing a new ROM, theme, or anything with the same regards simply means to wipe away what exists and replace it with something new.
So when you are flashing a new ROM, you are taking away the old one (with a data wipe aka factory reset) and then installing the saved zip file (contains the ROM) onto the computer.
Unfortunitly themes can't just be installed like they could on WM they need to be "flashed". These means you need to enter the phones bootloader. If you don't know what all that means then you have some more reading before you can get into themes. Much of which was said in the post above this.
Thanks everyone. And thanks for not flaming me, lol
Hi.
I have question about Android Porting.
I wanna port android from HTC Hero to my HTC Diamond.
So, what programming language should I know ?
And what i must to do, to port android to my HTC Diamond.
Thanks.
It would help you knew JAVA and basic linux commands (best to compile under linux).
You could do it the "quick and dirty way" by just dumping the /system/ files from a HTC Hero build and then sqsh'ing or making it into a .ext2 file. Otherwise, you could actually port to an ext2 partition. To make it work, try replacing the dumped system files with one from another working build.
Good luck
it would be nice to have a step by step tutorial
I will do a step-by-step tutorial once I have "some" days free. This will be very detailled including screenshots / videos. Of course cross-plattform compatible so you can use it for almost every device. As free time is really rare atm you may see this in some weeks - maybe to come in Jan 2011
vatoloco said:
i will do a step-by-step tutorial once i have "some" days free. This will be very detailled including screenshots / videos. Of course cross-plattform compatible so you can use it for almost every device. As free time is really rare atm you may see this in some weeks - maybe to come in jan 2011
Click to expand...
Click to collapse
awesome ! ! !
See this guide for a start: http://forum.xda-developers.com/showthread.php?p=5626300#post5626300
(it's on building android, but not porting)
Cool! Ill try to do my very best to port a 2.2 sense build from HTC Hero. If I manage to succeed so to say
I'd like to try my hand at building a custom rom. I have an Ubuntu Laptop and an Evo and I really don't know where to start. I read that there was a Rom Kitchen that I could use, but I don't know where to get it or how to get it installed on UBuntu.
Additional Options
Thanks.
Hey, I'll help you out I was once in the same position and 20,00 pages and forums later that I came to conclusion that if you really want to use Android Kitchen by dsixda I recommend you use Cygwin for Windows, which is like a modified DOS with Linux Coding which works flawlesslly. Yes you could use Ubuntu but I tried doing so and I get many errors during cooking my roms. But its up to you, I'll provide the links to help you where to find guides on how to Install appropriate drivers, software to cook up some Roms.
http://forum.xda-developers.com/showthread.php?t=633246 Android Kitchen <------
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/ < ------ Video on how to set up Android Kitchen on Linux Ubuntu.
Good luck
I'm going to second the kitchen thing but only to a point. It does handle some of the more annoying bits of putting a ROM together but I recommend you grab a stock rom, pull it apart, and try adding the changes that you want. Then flash, tweak, flash, etc.
I did this the other day with a stock HTC release. I learned a lot just about the general workings of the rom and all I was doing was basically dropping other people's tweaked frameworks and apps into it. After flashing about 15 times, I had a rom close to what I wanted with nothing I didn't.
That gets you started. Where you go from there is up to you. I hope to move from cut and paste rom assembling to doing some actual real development soon.
Hello XDA,
I've been following you for years. I started following you with my first Android phone, an HTC Hero. I've been very happy to be able to use a community ROM that made a far better experience than the stock ROM.
I recently got a brand new HTC One V PrimoU, and I'd like to make it my new polyvalent tool.
I'm not a noob in computers, kernel/linux related stuff, electronics, networking. I already tried some ROMs. In fact, I started with KangBang 3.0 (the same version as now I think), but both WiFi and BlueTooth were not working. Android could not even detected the WiFi MAC address, so I guess it was a driver or wireless chip firmware related problem. I think I was the only one affected, so it was maybe a bad flash or I used the wrong kernel. I did'nt investigate more at the time, but if it happens again to me, I'll send some system/kernel logs.
I then tried AOKP, had a great (really) experience with it, except that the Jack plug sound quality was awful. No bass, only mid/high tones. I even thought my speakers were dead at first, but then tried with headphones. Now, I want to try KangBang again, because that ROM was good, and fast, just missing WiFi.
TL;DR
I'd like to ask some precise questions about KangBang and the HTC One V.
I initially wanted to ask in the ROM dev thread, but can't since I'm a new user, so I ask here. Sorry if the questions are stupid/simple/answered, but let's make a clear base, with precise interrogations and answers, so that they will never be asked again
The kernel is included in the .zip file. Still, do we need to flash manually ? Or will the Aroma installer handle that ?
What about ROM Manager ? Is it recommended to use or is it a good way to brick a phone as I heard ?
Does this ROM change the base Android system and file structure ? Would it be compatible with a side-by-side installation of a Linux system such as Debian ? (To see what I mean by side by side installation of Linux, search Debian Kit for Android on Google, as I can't post links)
Also, I'd like to tell ROM makers these advices (don't take them bad, I you think I'm wrong about them there's no problem, just tell me why) :
It would not be a bad idea to give a simple statistic about the ROM : the load average with the ROM installed on an idle and clean phone. That would give a good indication of idle power consumption and ressource wasting.
I see that users reporting problems with their devices NEVER include any kind of debug information. Maybe you should ask for them, just because by searching for this debug information they might solve the problem themselves. Most Android systems and kernels report a LOT of information, that we can access with simple commands such as dmesg.
Last but not least, I would like to thank you, ROM developers and XDA users for allowing me to play this way with my phone, and to make it work exactly the way I want.
Hugo G.,
ummm this device has kangbang?? (btw questions go into q&a )
so i'll move onto the TL;DR which i was grateful for
1) The rom thread should say what kernel but yes, we don't have s-off so flashed manually
2) Ignore rom manager don't touch it
3) think of it as the differences say with debian vs ubuntu vs mint all basically debian but all with they're own differences (pros and cons)
also about the "suggestions" to the devs, that will NEVER go down well, why should YOU suggest to use what to put in the threads also i know in my threads i ASK for logcats time and time again...
hope this helps
if you need more info i'll be welcome to add more, but 1st i need sleep BADLY