We have the source for the T-Mobile & Telus variants so we should have the tools needed to build it. Is there a dev out there that was planning to put together a plain AOSP build?
These have always been my favourite because they're generally problem free and quick, but also easy to build on or modify to your liking with the UOT Kitchen.
Pretty please? =)
Related
How do i make a custom rom ?
being that most of the android cooking began with the G1 and the Magic, have a look through the forums for those devices.
I'm betting you'll find shedloads of stuff on building ROMs in those areas, as most of the cooks started in there.
Another good place would be ...
http://github.com/kiall/android_vendor_community
http://github.com/jnwhiteh/android_vendor_community
http://github.com/loxK/android_vendor_community
You can get a stock AOSP 2.1 ROM built with ... 1 xml file... and about 6 commands Between the 3 of us, we've got hero support in AOSP nearly solid!
There are quite a few ROMs available, but one thing is not entirely clear to me. Why aren't there any clean AOSP ROMs for the Wildfire? I can understand it would be difficult to develop newer Android versions like Gingerbread that were never officially released for the Wildfire, but wouldn't it be relativly easy to compile a working ROM from the 2.2/2.2.1 source code? Or am I completely missing the point here?
It seems to me all the materials are available to pull this off without too much effort, right? The Kernel source is available from HTC and the Froyo source from our friends at Google.
From what I understand there are also some vendor specific issues that need to be solved, but the Cyanogen developers apparently have this solved already.
That pretty much covers everything right?
So my question would be, is it possible to easily build a clean version of Froyo for the Wildfire by doing the following:
1. Grab the kernel source from HTC and compile it (or just fuse a pre-compiled one seeing as there are quite a few available).
2. Compile the Android 2.2/2.2.1 source
3. Apply vendor specific fixes (assuming they don't have to be incorperated in the code directly).
4. Flash kernel + ROM, thereafter Gapps
5. win?
Basically something like Openfire without bugs. Which reminds me, wouldn't the video recording/SIM card issues be fixed with the official HTC kernel? In which case, I see little reason to try and compile the stuff by myself.
Ah well, I really really hope someone can enlighten me on this subject.
TL;DR: I want to create a basic a clean AOSP Froyo 2.2/2.2.1 ROM which should be easy right because we already have the required materials (proper HTC kernel -- or third party one, 2.2/2.2.1 source, cyanogen vendor fixes), so compile = good to go?
there are
- Wildmix http://forum.xda-developers.com/showthread.php?t=1155032
- CM6 http://forum.xda-developers.com/showthread.php?t=822132
- Utmost http://forum.xda-developers.com/showthread.php?t=862561
- Openfire - http://forum.xda-developers.com/showthread.php?t=783024
more here (scroll down) http://forum.xda-developers.com/showthread.php?t=1029318
There is always CM7
Remember you use these at your own risk
Thank you for your reply, but it doesn't really address my questions. I am aware of the custrom ROMs available, none of them really meet my demands.
Cyanogenmod is an excellent ROM, but CM6 has some issues and CM7 is based of Gingerbread.
Utmost and Wildmix are both based on Openfire. The problem with Openfire is that it has a lot of internal stuff I don't really like. Seeing as Utmost and Wildmix are based on it those don't really float my boat either.
My eventual goal would be to create a clean AOSP like this one:
http://forum.xda-developers.com/showthread.php?t=1162656
Unfortunately it's based on Gingerbread and not fully functional (yet!).
That is why I asked the questions that I asked. I'd rather do it myself from scratch, but in order to do any work I could really use an answer to my questions
Thanks anyways.
Trademark225 said:
Thank you for your reply, but it doesn't really address my questions. I am aware of the custrom ROMs available, none of them really meet my demands.
Cyanogenmod is an excellent ROM, but CM6 has some issues and CM7 is based of Gingerbread.
Utmost and Wildmix are both based on Openfire. The problem with Openfire is that it has a lot of internal stuff I don't really like. Seeing as Utmost and Wildmix are based on it those don't really float my boat either.
My eventual goal would be to create a clean AOSP like this one:
http://forum.xda-developers.com/showthread.php?t=1162656
Unfortunately it's based on Gingerbread and not fully functional (yet!).
That is why I asked the questions that I asked. I'd rather do it myself from scratch, but in order to do any work I could really use an answer to my questions
Thanks anyways.
Click to expand...
Click to collapse
Have news for you
We are currently working on a ROM with the aosp ROM you linked as base ...
Stay tuned
Sent from my HD2 using XDA Premium App
He meant a AOSP Froyo, no Gingerbread ;D
nejc121 said:
He meant a AOSP Froyo, no Gingerbread ;D
Click to expand...
Click to collapse
Got that after posting that
But gingerbread is much better than froyo and compatible to nearly all apps you can have
Sent from my HD2 using XDA Premium App
Anyway what's wrong with gingerbread??
I figured since 2.2.1 is the last available official version released it would be easier to get all hardware functioning properly. But if those new ginger AOSP projects fix the video recording bugs and get everything else fixed, ill gladly switch to it. Maybe ill use xdbg's (spelling?) ginger aosp as a base as soon ss the bugs are fixed.
Sent from my HTC Wildfire using XDA App
Hi guys,
I am confused with all those fancy looking ROMs.
You are good in coding, building, cooking but still not sure about themeing...
I have an idea and I wish to ask you to try to make ROMs that way:
1. cook the ROMs in classic look and easy to see and understand (white text on black menu or something) just the basic theming and give an option to update for another look...
2. when you are building sense ROM please make it the way sense look like not with some orange icons or percents with transparent menu upon a light wallpaper where you cant see anything without hardening you eyes.
3. building Cyan is the same, make it stock and give an option to theme it.
4. do not put some extra software in the ROMs, that way you just got where everybody wanna go away from (HTC way) We all want to remove the bloatware with the stock ROMs but stock ROMs instead of giving us basic option to install what we need give us more and diferent other bloatware
========================================
anyway, I am posting this because I am looking on all those Sense3.5 threads. I don't have enough time ATM to build one miself the way I like it to be, so I am searching for stock stable kernel, basic clasic sense3.5 look with sense3.5 functionality, stock icons and stock boot animation and etc. but I couldn't find such. every sense 3.5 rom is moded somehow, why you are using sense3.5 in the ROMs name when you use just few setings from sens and everything else is moded?!?
I do not want to be rude at all!!! you all have my possitive feelings, thats a wonderful forum with more wonderful members...just...please listen to me and when you build please add an option for the members to choose whether to update through a custom recovery the look of the ROM, give us basic look sense, ADW or MIUI ROMs!
Best Regards
http://forum.xda-developers.com/showthread.php?t=1503426
Most basic 3.5 for WFS, use UOT Kitchen to change the battery to stock, its clearier than clear
This is a development thread, not a request line. Keep this place uncluttered by posting stuff like this in general, a rom post or a pm.
Sent from my HTC_A510c using Tapatalk
I can build you one, one day.
m1ndh4x8r said:
I can build you one, one day.
Click to expand...
Click to collapse
It would be nice to have one with the new european RUU but I think that's a lot of work...
Hi,
I would like to learn how to create my own custom ROM. Any reference you have on the topic would be great. I have successfully built my own kernel from source and have made a guide here: http://forum.xda-developers.com/showthread.php?t=1516051
Now I would like to build my own custom ROM. I noticed that when I downloaded the kernel source code from Samsung it also included the platform source code. I have read somewhere that I wouldn't be able to compile the Stock ROM just because a lot of the stuff is proprietary (like touchwiz). If this is the case, how are developers including the proprietary stuff?
Is it possible to build stock ROM from source?
Are custom ROMs more about tweaking existing configurations and apps, as oppose to compiling from scratch?
Thanks for helping a noob. I really want to learn the stuff.
I can make update.zips through android kitchen. I was really wanting to make a CM10 unofficial port but can't because of sources.
I did mess around with stock a little bit but i really didn't like it because of all the bloatware and stock features.
MIUI doesn't work for me either.
If you guys could help me find a good Base to work with that would be awesome. And also i don't want anyone to think i am stealing their work or anything so I need permission to use it as a base.
I do plan on uploading it in the future.