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
Hi guys,
it's my 1st thread started at xda, so if it's in wrong place or anything, let me know and i'm sorry.
As I'm not a developer myself I just follow up stuff here to see all u guys good work... but when I saw this news and noticed that it's not here... I'm sure some of you can make good use of this info.
HTC release the source code for Hero (and some others) on their developer centre, it seems like a straight download which should help the devs get nicer drivers (Froyo ???) and smoother running ROMs.
news via: http://www.androidcentral.com/htc-developer-site-updated-kernel-sources-evo-4g-and-htc-hero
HTC dev site: http://developer.htc.com/
Optimized HTC Sense UI coming?
Go go devs.
Nothing new though. At least not for Hero benefits anyhow.
We've had hacked together kernel sources for 2.6.29 for a while now, so this isn't as big a deal as the original kernel source release. Hopefully the devs here can still make use of it.
Hi
nothing really new ?
IIRC, "Github for the untouched original kernel source: hxxp://github.com/toastcfh/CdMa-HeRoC-2.6.29" is another device kernel src reverse for the Hero from a forgotten patch file in the archive ?
so this "really" original kernel source may be newer with last correction from htc ?
thx help me understand
Az'
from what I understand (After a bit of toying with toast's kernel sources myself) this is what's done:
(correct me if wrong):
They took a supplied 2.6.29 kernel source as the base. Don't know if it's from Nexus, Desire or Legend, but some anroid-2.6.29 base kernel that was already available.
Already having a 2.6.29 base with most HTC-ish hardware available, the hard part was merging in all the cpu centric files (board files, for the MSM720x platform) from the already released 2.6.27-htc sources.
So starting with a htc-ish 2.6.29 base, and slowly and trial-and-error moving stuff over from the 2.6.27-htc sources (which is harder than it looks. 2.6.27 -> 2.6.29 had quite some changes in the linux world) until it boots and until all hardware worked.
He did this for the CDMA hero. From there it wasn't too long (or did it work directly?) until it worked for the gsm hero. Someone just had to notice his work I believe .
_So_, that means that our 'godmode-2.6.29' sources aren't really 'hacked together' that much. The support files are still from HTC, only they are the same as the 2.6.27 (android 1.5) drivers. _Maybe_ HTC updated or optimized some things and thus the official-2.6.29 might contain newer or better working support for the hardware.
The way to check this is out is to compare the **** in the source files (which people are probably doing already) to see the differences HTC did to toast's version.
The other method is to 'try' and feel what's different. This _never_ works in the XDA community because there is a _huge_ placebo effect in what all the users are feeling. The same as compcache, swap, bfs or not, etc... opinions and preferences are all over the place.
Only if benchmarks or other hard numbers make one version better than the other, it remains something of preferences for the users and creators of the roms.
(Is there already a simple recompile somewhere with overclocking enabled of the HTC 2.6.29 sources? Because then the testing can begin ).
so no current roms are built from the official kernel (the 2.6.29 kernel from HTC)?
As far as I can understand the GoDmOdE kernel sources are based on a leak of 2.6.29 kernel sources for multiple HTC devices, including a CDMA hero kernel source. And the sources for all our 2.6.29 GSM hero kernels are based on this.
The official 2.6.29 are very new, but I am sure that now that they are released we will see kernels based on these sources as well.
Is anyone working on a UVOC kernel for the new HTC 2.2 update??
I'm desperate!!! :-D
I'm actually a Linux developer so if anyone can point me in the right direction I might start myself!
Thanks,
Shyrka
I'm a newbies on Android, but I think dev needs HTC to release new Kernel sources before adding this type of features.
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
On 2012.05.28 ipaq3870 uploaded his last version of i8000 android kenrel. a kernel that is based on M910 (s3c6410) phone, modified for our device.
Two years later and after saw gingerbread running on our phone, even with some problems and lacks i decided to contribute, work and continue this project.
i want to modernize this kernel in order to make our froyo ROM faster and make gingerbread ROM with more features to work.
there are many sources over the internet. we only need some volunteers. no need for advanced linux/programming knowledge. some free time and will to study a little is necessary of course.
volunteers can contribute here
https://github.com/argentinos/o2droid (fork from ipaq's job)
sources can be found here
https://github.com/a.../kernel-s5pc100
https://github.com/a..._samsung_omnia2
https://www.kernel.org/
http://opensource.sa...earchValue=m910
http://opensource.sa...earchValue=5800
https://github.com/a..._samsung_omnia2
http://omnia2droid.g....com/svn/trunk/
my last goal is to see latest version of 2.6 kernel on our phone. i do not think our old phone can ever execute 3.X kernel or run properly android ICS, JB etc
for those dreaming about it can conrtibute on erikcas 3.0 kernel for i8000 here
https://github.com/erikcas/spica-3.0