I'm tired of CyanogenMod, it there always seems to be something wrong with it, this there a custom Gingerbread Rom out there does work 100%? I am no expect on modding Roms but I am guessing CM team strips the original OS down and rebuild it, any that keep the working OS and just have some nice mods for it?
No, because there is no official Gingerbread rom for the Wildfire, ALL ROM's for it are built from source. (Or based on other ROMs, which themselves are built from source) (Except SFM, obviously, which is build from the Salsa ROM - But its not really complete for daily use as you know)
3xeno said:
No, because there is no official Gingerbread rom for the Wildfire, ALL ROM's for it are built from source. (Or based on other ROMs, which themselves are built from source) (Except SFM, obviously, which is build from the Salsa ROM - But its not really complete for daily use as you know)
Click to expand...
Click to collapse
Thanks, so let me get this straight in my mind, 2.3.3 mod like Cm7 are built for other android phones who got Gingerbread officially? so they only way to get the kind of ROM I am looking for would be to look for a 2.2 ROM?
No, CM7 is built from the source code of the Android OS. Its not based on any phone's ROM.
I was assuming from your query you were looking for a GB ROM based on the official ROM, which is why I posted that.
Related
Hi,
I'm playing with ROM building recently and I when building 2.1 ROM, everyone say "We can't fix X issue because we don't have kernel sources".
I was shocked seeing all great hardware support is on the Eris leak based ROMs.
Why thoses ROMs have better hardware support ? I thought when we port a ROM, we take a working boot.img (kernel + drivers) and the new system.img together. So if I'm not wrong, what make thoses ROMs better ?
I'm probably missing some key understanding. If you can help me, I'll really appreciate.
Regards,
mik
Eris is basically Verizons Wireless's re-branded version of Hero.
The hardware and everything is same, just the physical appearance.
So our new kernel base is now this one ?
I'm asking because I'm building AOSP (cyanogenmod) ROMs so if this new kernel+drivers is the way to go, I'll start wirking with this as base and not the old HERO2.1 one
mik- said:
So our new kernel base is now this one ?
I'm asking because I'm building AOSP (cyanogenmod) ROMs so if this new kernel+drivers is the way to go, I'll start wirking with this as base and not the old HERO2.1 one
Click to expand...
Click to collapse
The kernel of the Eris is different to the Hero, they are still using the old kernel on the Eris port
l0st.prophet said:
The kernel of the Eris is different to the Hero, they are still using the old kernel on the Eris port
Click to expand...
Click to collapse
So why the hardware support is so good ?
hardware driver...
Isn't all of this supposed to be open source anyway? Like, if the official kernel has better hardware support, why isn't it in the Android Open Source Project (AOSP), if Android is GPL-licensed Free Software? Is there a violation of the GPL going on here?
FunkTrooper said:
Isn't all of this supposed to be open source anyway? Like, if the official kernel has better hardware support, why isn't it in the Android Open Source Project (AOSP), if Android is GPL-licensed Free Software? Is there a violation of the GPL going on here?
Click to expand...
Click to collapse
Because the official kernel isn't officially available, it's still technically in development. They are under no obligation to release it until they release it to the public, by which point we will have it anyway
FunkTrooper said:
Isn't all of this supposed to be open source anyway? Like, if the official kernel has better hardware support, why isn't it in the Android Open Source Project (AOSP), if Android is GPL-licensed Free Software? Is there a violation of the GPL going on here?
Click to expand...
Click to collapse
Common misconception number 1 - Android is *not* licensed under the GPL, it is licensed under the Apache Software License (ASL). This license is not a copy left license so OEMs who modify the Android source are under absolutely no obligation to make their modified source code available.
However, the Linux kernel upon which Android runs is licensed under the GPL, so HTC must provide the source for any *shipping* software that uses said kernel. Since HTC have not officially released their version of Android 2.1, again they are under no obligation to supply kernel source. The second that they official ship the update, this changes and they are obliged under the terms of the GPL to make the kernel source available.
Regards,
Dave
And I hate to be a complete noob, but are these drivers that provide the nice hardware support part of the kernel?
If not, what difference would it even make if we didn't have the official kernel sources?
Since the Eris has the exact same hardware as the Hero, why can't we use the same kernel as the Eris rom ?
Latoc said:
Since the Eris has the exact same hardware as the Hero, why can't we use the same kernel as the Eris rom ?
Click to expand...
Click to collapse
Because it isn't the same hardware.
The Eris is close, but not identical to the Hero. The major difference is it's CDMA, not GSM. And, it uses touch buttons instead of physical buttons.
Other than those two, I'm not sure if there are any other significant differences. Point being that those differences are enough to warrant a different kernel.
e.japonica said:
hardware driver...
Click to expand...
Click to collapse
So if I understand correctly, the Eris leak based ROM use the old kernel (2.6.29) but newer hardware drivers so my question is correct ... Should we use any Eris based ROM as base to make new AOSP ROMs ?
This way, we will keep the old kernel but new drivers ...
Please correct me if I'm wrong.
mik- said:
So if I understand correctly, the Eris leak based ROM use the old kernel (2.6.29) but newer hardware drivers so my question is correct ... Should we use any Eris based ROM as base to make new AOSP ROMs ?
This way, we will keep the old kernel but new drivers ...
Please correct me if I'm wrong.
Click to expand...
Click to collapse
Really, it's all going to change when we get to official Hero 2.1 ROM (and kernel,) because that's what we'll be using very soon (if we're to believe the hype about 2.1 finally coming this month.)
As for right now, it's up to you. If I were to start working on a ROM, I would use the Eris dump, although you'll have to change to the official kernel in a couple weeks anyway.
I'm not really sure what to say about using "the old kernel but new drivers. I'm not into kernel dev myself, but what's "old" and what's "new" is going to change soon anyway, so I don't think it matters too much at this point.
EDIT: Let me correct myself: If you're going to make an AOSP ROM, you won't use the Eris *ROM* as the base, you'd just use the kernel and drivers. The rest of the system would not have any HTC-ness attached to it (no Sense/HTC Mail/etc), so you'd actually use an AOSP image instead of an Eris/Hero image.
craig0r said:
Really, it's all going to change when we get to official Hero 2.1 ROM (and kernel,) because that's what we'll be using very soon (if we're to believe the hype about 2.1 finally coming this month.)
As for right now, it's up to you. If I were to start working on a ROM, I would use the Eris dump, although you'll have to change to the official kernel in a couple weeks anyway.
I'm not really sure what to say about using "the old kernel but new drivers. I'm not into kernel dev myself, but what's "old" and what's "new" is going to change soon anyway, so I don't think it matters too much at this point.
EDIT: Let me correct myself: If you're going to make an AOSP ROM, you won't use the Eris *ROM* as the base, you'd just use the kernel and drivers. The rest of the system would not have any HTC-ness attached to it (no Sense/HTC Mail/etc), so you'd actually use an AOSP image instead of an Eris/Hero image.
Click to expand...
Click to collapse
Yeah, I know. Sorry to not being clear enough. When we build AOSP build, we take an existing ROM to extract kernel and drivers to make the AOSP code working. When I say take Eris leak based Roms as base, I mean just the kernel/drivers part. I know the whole system will not be taken into account.
Eris and AOSP 2.1 roms
After looking at the previous 2.1 roms that were being used to cook and the Eris now being used by everyone, although both being 2.1 they do appear to be different versions of the same product
The Eris appears to be a cut down version of the ASOP 2.1 version, the mail app is still based around the 1.5 version HTC mail, rather than the mail app that is on ASOP which gives you global address list search etc on exchange, and new features on incoming mail for normal mail accounts.
Are features like this built into the kernel themselves ? or things like mail, dialers just apk files
A few forums are now reporting that the new official version of 2.1 for the hero will be a basic version compared to the versions running on desire and nexus. Which would be a disappointment
About to flash CM7. Seen some mention of 'kernal' in various threads. What does it do? and do I need to update it?
Cheers.
same question
The Kernel controls things like battery drain and CPU levels for overclocking etc... its not a must do but recommended for best performance. there is probably not a "best" one but more like the best that suits you. If you are running CM7 i would recomend Vork Kernel's or ManU kernels
Richardtrip's kernels are also very good: overcklocking, manual voltage level, Two-way call recording.
plohoi said:
Richardtrip's kernels are also very good: overcklocking, manual voltage level, Two-way call recording.
Click to expand...
Click to collapse
Have you used the call recording? If so how do you "activate" it or listen to the calls afterwards?
CdTDroiD said:
Have you used the call recording?
Click to expand...
Click to collapse
Yes call recording is working fine.
CdTDroiD said:
If so how do you "activate" it or listen to the calls afterwards?
Click to expand...
Click to collapse
There are several apps in http://forum.xda-developers.com/showthread.php?t=993793 thread, I used app by skvalex.
Since I'm new to Desire and HTC- what is the difference between Sense and AOSP kernels?
(before you ask- I know what AOSP is)
Do Sense firmwares require some extra drivers/modules/settings in kernel?
gen_scheisskopf said:
Since I'm new to Desire and HTC- what is the difference between Sense and AOSP kernels?
(before you ask- I know what AOSP is)
Do Sense firmwares require some extra drivers/modules/settings in kernel?
Click to expand...
Click to collapse
Hi there!
Sense is HTC proprietary software built over the top of Android. This code is not open source and is what HTC use to set themselves apart from other manufacturers like Samsung etc. Sense is what they sell as their user experience.
AOSP stands for Android Open Source Project. Since Android is an open source operating system, Google publish all the code and necessary tools to develop Android. Companies like HTC get the code and then write Sense over the top. Devs in this community like Cyanogen take the AOSP code and build their ROMS from scratch.
When you see ROMS that are for Sense 2.1 on Gingerbread for example this means that someone has been able to port software running on other phone models like the Desire HD or Incredible etc to your phone model (Desire)
As for the kernels you will need to make sure that the kernel you run is supported on the device and that's about it. The Kernel has to have some key components or the phone won't work so the ROM you use just uses them.
Having said that, ROM developers usually optimise around one or two particular Kernels. They are usually included in the ROM or the Dev will tell you which one they recommend for certain purposes.
You do have to have apps in the system that can access settings if customising the performance beyond what the dev has already done is what you want to do.
Thanks for the answer but it's not exactly what I'd like to know
Thing is- what makes Sense kernel incompatible with AOSP firmware (and vice versa)
Sorry for not answering what you were looking for. I'll try again.
The Kernels for Sense would have specific code that enables features in the phone that HTC build. LED control, light sensor etc. I assume Sense is quite strict about what it will work on and what it won't.
The AOSP Kernels are built without knowing the exact hardware maps of the internal components and as such won't work with Sense because they simply don't know how due to HTC keeping a lid on all source work for Sense and the handset itself.
The best developers can figure most of it out (certainly I am not a dev, just a geek ) and teams like CyanogenMod have it mostly discovered and configurable.
Is that more helpful?
Isn't Sense a HTC's android framework "mod"? I mean does it "just" provide more/different functionality than AOSP?
AFAIK all kernels must be built knowing exact hardware map, otherwise some devices will not work or kernel will not boot. The only autodetect I'm aware of is display panel type and filesystems (I did mess with kernels @samdroid.net)
i have a question about kernels an such from what i understand is you don't need to update the kernel but its a good idea too do so. couple questions i have.
1. how do you know what kernel you have installed currently.
2. How do you flash or get a new one installed if you need or want it.
3. scene i am using core droid 6.3 gb2.3.3 what kernel would be the most compatible or effective?
I have had my inspire phone for 3 months an finally rooted it 3weeks ago sence then i have used the rom manager too play with different roms an make backups of the 2 i have found i like the most. After reading i have seen it stated too get the most out of these roms though you should install a different kernel.
To know your currently version, you have to go in parametres and then logiciel version and look at build. Sorry for my bad English.
Sent from my HTC Desire using XDA Premium App
I don't want open a new thread, so I will ask here.
Now I have
kernel
2.6.32.15-gf5a401c
baseband
32.49.00.32U_5.11.05.27
Click to expand...
Click to collapse
on stock pre rooted 2.2 Froyo.
I want put this ROM. Can I put this ROM with my kernel and radio or I musst put latest kernel and radio?
GTRSkyR34 said:
I don't want open a new thread, so I will ask here.
Now I have
on stock pre rooted 2.2 Froyo.
I want put this ROM. Can I put this ROM with my kernel and radio or I musst put latest kernel and radio?
Click to expand...
Click to collapse
You will find that many roms contain a kernel in the zip file, so it will often change when you flash a rom. If not, the developer may recommend one.
Radio is independent of rom flash, and unless you start getting connectivity problems there is normally no need to change it. Again, some developers will recommend a radio (and maybe a RIL if they know a particular combination works well with their rom.
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
There are a few (or more) ICS/JB roms that are fully running without any problems on DHD. Why CM doesn't make one officially? I'm using CM7 and I saw many ICS roms running smoothly on DHD but I'm not going to try it because I don't want to loose my stuff on current CM7. So I'm waiting for CM to build an official one. Why don't they build it?
And I found out CM only build an official one when the manufacturer release a official new stock rom. Right?
...
yes. Its correct and CM's you are talking about are custom roms and that's why they are diffeerent. Release of official CM is unknown becouse kernel for dhd is not released
dato_ts said:
yes. Its correct and CM's you are talking about are custom roms and that's why they are diffeerent. Release of official CM is unknown becouse kernel for dhd is not released
Click to expand...
Click to collapse
Right now I'm using official cm. If I wanted to change to an unofficial cm, do I need to wipe data off?
I guess you mean cm7. I would always do a full wipe before flashing a new rom. It might be ok if you don't wipe but it's not worth chancing it because you could get problems later. Backup your apps if you need to first if that's what you're concerned about.
Hello Developers
is someone able to create an AOSP (KitKat 4.4) ROM for our Samsung Galaxy S4 Mini? It would be great if we have a "vanilla" Android version for our Smartphone and this can be used as base for other ROMs. Would be great if someone could build it
Greetings
Cilenco
Cilenco said:
Hello Developers
is someone able to create an AOSP (KitKat 4.4) ROM for our Samsung Galaxy S4 Mini? It would be great if we have a "vanilla" Android version for our Smartphone and this can be used as base for other ROMs. Would be great if someone could build it
Greetings
Cilenco
Click to expand...
Click to collapse
Most ROM are based on AOSP or CM (which CM is based on AOSP) :/
And if you want a minimum ROM, there's few ROMs are even less 'bloat' and more 'vanilla' than AOSP itself.
I think he meant that he wanted an actual aosp rom, not just an aosp based rom. While we don't have a pure "aosp" rom for our phones, cyanogenmod is pretty close, slimkat is also pretty bare if you're into that. I'm sure a lot of people could port it, it just remains to be seen if any developer is interested enough to actually do it.
Yes a pure AOSP ROM would be great. The whole ROMs which are aviable for our device are based on AOSP so I think it wouldn't be so difficult to build one from AOSP isn't it?
bluespoon4 said:
I think he meant that he wanted an actual aosp rom, not just an aosp based rom. While we don't have a pure "aosp" rom for our phones, cyanogenmod is pretty close, slimkat is also pretty bare if you're into that. I'm sure a lot of people could port it, it just remains to be seen if any developer is interested enough to actually do it.
Click to expand...
Click to collapse
Slim kat is equal to Slim ROM? In that case there is already a port to the S4 mini in the developer section of this forum