Related
Going to try to find all the roms I can and get them in one place before it gets real messy, Please let me know if I missed your rom or if you added a new one so I can add it even if im not at my computer you can do this by e-mail to [email protected] or to my phone! 906-430-1564 please dont call me for no reason, that will just make me mad but if you have a sweet forward that Id like to send to my friends. Send it, Im paying for unlimited messaging might as well use it, I have a sick and twisted and sarcastic sense of humor and that should help.
READ THIS FIRST!!!!!
SAVE THE POOR PEOPLE WORKING ALL OF THE QUESTIONS THAT ARE ANSWERED HERE!!!!!
thanks goes to seraph1024 for making this. http://forum.xda-developers.com/showthread.php?t=619153
Stock-Leaked Roms
Leaked:
EPE76 image format download MD5: 31a7944d2af0ecdaa06f4bf8f1558a10
http://www.mediafire.com/file/ynznmyxkiiz/EPE76-stock-images.zip
Leaked:
EPE54B update zip download MD5: 0cfa033d58509b9bdf5d9ae09d976a38
http://www.mediafire.com/file/amrjmuzj1ho/Leaked-EPE54B-stock-image-update.zip
Second Update:
ERE27 update zip download MD5: 90700607c04279716b505aa203e9c684
http://www.mediafire.com/file/vomqomnwndi/2nd Update-ERE27-stock-image-update.zip
ERE36B update zip download MD5: MD5 070e47f96d7c14e682232155e86a8f4b
http://www.mediafire.com/file/ntztctz20ly/Leaked-ERE36B-stock-image-update.zip
Original Stock:
ERD79 update zip download MD5: 5e17b0351024c8fb1a2020f1fd55210e
http://www.mediafire.com/file/2mjozawirom/Original-ERD79-stock-image-update.zip
http://www.mediafire.com/?sharekey=a1e428ed720bdf41ab1eab3e9fa335ca03f7573b24953fcd Here are some files thankfully posted by Moderator Mikey1022 for general use until there is another repository for stock roms
ROMS
Ok Rom list starting with the newest:
Cyanogen
CyanogenMod-5: Kang Central Station (STABLE) [03/23/2010 / 5.0.5.3]
http://n0rp.chemlab.org/android/nexus/update-cm-5.0.5.3-N1-signed.zip
Cyanogenmod:
http://forum.xda-developers.com/showthread.php?t=623496
Chef: cyanogen
GrimmsMod based on CyanogenMod 5.0.5.3(All in one) Advanced overclock and undercurrent cooked in use if you know what this means or read about it and understand it! :
http://forum.xda-developers.com/showthread.php?t=654958
Chef: Grimms
[CyanogenMod-5 based] Core CM w/Exchange Apps:
http://forum.xda-developers.com/showthread.php?t=651448
Chef: lpasq
CyanogenMOD BakedGoods 1.1:
http://forum.xda-developers.com/showthread.php?t=639637
Chef: Herver
MoDaCo
21/Jan 1.3 - MoDaCo Custom ROM:
http://forum.xda-developers.com/showthread.php?t=614186
23/Mar 2.1 - MoDaCo Custom ROM for Nexus One with online kitchen:
http://forum.xda-developers.com/showthread.php?t=630529
01/Apr Alpha r21 - MoDaCo Custom ROM Desire Port with Online Kitchen (+HTC_CIME!):
http://forum.xda-developers.com/showthread.php?t=636048
Chef: paulobrien
TheOfficial Nexus1
Enomther's TheOfficial Nexus1:
http://forum.xda-developers.com/showthread.php?t=614427
Chef:enomther
NexDESIRE
NexDESIRE_v1.2_REMIX!!! Looking Better:
http://forum.xda-developers.com/showthread.php?t=637325
Chef: manup456
Snack Pack
SnackPack v0.2.1 [CM5+Extra Snacks] - New A2SD Method:
http://forum.xda-developers.com/showthread.php?t=638301
Chef: ctso
Passion Google
[ROM]Passion_Google_WWE_1.09.1700.1_EPE54B:
http://forum.xda-developers.com/showthread.php?t=642811
Chef: Football
OK I think that covers them if I made a mistake please let me know I will come back and update as much as I possibly can, and fix any errors. Nexus one will be here soon!!!
Ok did Roms and now Im gonna do Kernels Hopefully people find this usefull, Again if you add one please pm me or message me here or at [email protected] or use the device in your hand 906-430-1564
Kernels
Diet Kernel for Nexus One (based on CM 5.0.5.3), incl. undervolting and overclocking!:
http://forum.xda-developers.com/showthread.php?t=654416
Coder: Ivan Dimkovic
Direct Link: Attachments on first post of thread.
:
[Kernel - .32 & .33]Conservative Power Governor Kernel (with several tweaks): http://forum.xda-developers.com/showthread.php?t=653598
Coder: intersectRaven
Direct Links:
20100329_2221:
http://www.mediafire.com/?ya2tdzbdjiz
http://www.mediafire.com/?wqtigvyg0du
20100329_0835:
http://www.mediafire.com/?njjnjjqwltz <= 2.6.32
http://www.mediafire.com/?ttdz0cj0z0m <= 2.6.33
:
[Kernel-.33.2!] OCed - UVed: -1.113Ghz Stable - 4/05 -8MB extra ram!: http://forum.xda-developers.com/showthread.php?t=633238
Direct Link:
boot-cm_2633.2-oc-uv-ram.zip
http://droidbasement.com/nexus/kernels/ram/boot-cm_2633.2-oc-uv-ram.zip
boot-cm_2633.2-oc-uv-xtra-ram.zip
http://droidbasement.com/nexus/kernels/ram/boot-cm_2633.2-oc-uv-xtra-ram.zip
<><><>
zImage-cm_2633.2-oc-uv-ram
http://droidbasement.com/nexus/kernels/ram/zImage-cm_2633.2-oc-uv-ram
zImage-cm_2633.2-oc-uv-xtra-ram
http://droidbasement.com/nexus/kernels/ram/zImage-cm_2633.2-oc-uv-xtra-ram
lib-2633.2.tar.gz
http://droidbasement.com/nexus/kernels/ram/lib-2633.2.tar.gz
.
[Kernel-.33.2!] Undervolted @ Stock Speeds-4/04 - CM5.0.6src - #teamdouche:http://forum.xda-developers.com/showthread.php?t=634587
Coder: persiansown
Dircet Link:
http://kmobs.scepterr.info/kernels/zImage33UV.zip
:
[KERNEL] [CM-Source] [BFS-315] KiNgxKxernel 2.6.33 1.113Ghz Capable!: http://forum.xda-developers.com/showthread.php?t=635806
Coder: kingklick
Direct Link:
http://www.4shared.com/file/233881708/2a7fa596/KiNgxKxernel-2633-5.html
Radios
Stock
32.24.00.22U_4.03.00.21_2 download MD5: 28a6aabf2f756806c5eb5e99a9626ca4
Direct link:
http://www.androidspin.com/download...Official_Nexus1_Radio_Update_4.03.00.21_2.zip
32.26.00.24U_4.04.00.03_2 download MD5: c55116d119e9e30cffc86875dce1a560
Uploader: enomther
Direct Link:
http://www.androidspin.com/download...Official_Nexus1_Radio_Update_4.04.00.03_2.zip
Original (older) Radio image 4.02.02.14 (from ERD79) in an update.zip.
http://www.androidspin.com/download...heOfficial_Nexus1_Radio_Update_4.02.02.14.zip
If anyone wants to be helpful point me in the direction of radios that are not listed here, if you upload on please notify me.
reserved111111111111111
good effort!
Please everyone keep the chatter to a minimum so we can maximize the usefulness of this thread. If you have a rom or kernel that needs to be added to the list let the OP know.
This a very good idea! a one stop shop for all of us. especially to all newbie user. keep up the good work thanks..
Good job Justin. I actually thought bout doing this as well, makes people's lives much easier.
Thanks man Someone still need to go do themes in the other thread so it doesnt get so cluttered we cant find anything I wont be able to keep up with all three when more people get the device.
Well for now there aren't many themes available, no need for a sticky at the moment.
Good sticky. Maybe a post linking to all the different radios? When I first rooted my phone I found it harder to find info, and links, to the different radios and whether they were just for US users.
In one of the two reserved spots, would it be a good idea to link to all the versions of radios and RILs? I've been trying to find some older ones, but this could make it nice and simple.
Will get on it as soon as the little one goes to sleep, Shes dancing around to spongebob right now, not good for me concentrating on anything.
Check Enomthers rom link for radio links
Any chance at getting links to stock roms?
Sure will do my best to get them up. Daughter is kinda freakin' She is teething like crazy.....
Here is a mediafire link...except roms and kernels
http://www.mediafire.com/?sharekey=a1e428ed720bdf41ab1eab3e9fa335ca03f7573b24953fcd
This is not a Q&A section, only post here if you have a rom, radio or kernal to contribute to the list.
Nexus One 1.11 ROM, Maybe you can get some use out of it.
Also the 1.10 is uploades has well.
http://conflipper.com/shipped/Passion (Nexus One)/
hi justin.
please don't post direct dload links from droidbasement on to this thread (please link to the actual blog post). i want people to fully read what is written prior to downloading.
thx
Without the inclusion of proper documentation included with an Android Rom or an Android Build users will start filling up the HD2 Android Development Forum with why this wont work when it does on someone elses Rom. To stop this from happening there will be a requirement when creating a Thread for a Rom with Android included, or an Android Build.
------------------------------------------
------------------------------------------
If you are making a Rom with Android built in or an Android Build that is run from haret then please INCLUDE with your file a readme.txt file in the ROOT of your release archive with the following information:
*What BUILD version?
An internal version # that can be used to identify the authors exact release (e.g. my-rom-v0.5.zip) for easier reference for the users and fellow developers benefiting from the release.
*Which kernel image and kernel modules are used?
Where are zImage and modules.ko originally downloaded (in case the chef didn't compile on their own) and where is the kernel source code for the kernel and modules.
In case the chef did not compile on his own, he should still be able find out where the source code is.
(The license under which the Linux kernel is released requires the distribution of the source code that was used when distributing builds.)
*What rootfilesystems are used?
Where was it taken from, what does it include (android version it's based on etc) and in case of self compilation, where is the source code.
(In case of most windows mobile shipped devices that's often some rootfs file e.g. named android.ext2 and an initial ram filesystem often named initrd.cpio.gz).
*ChangeLog*
A ChangeLog is really an essential addition in every build as it informs the end user what modifications have been made from the last build. This will save you ALOT of questions as to what has been added, deleted or modified and therefore is a requirement for everyones benefit.
*WindowsMobile version your Android Build was tested on*
Please include your WinMo Build version, HTC OemDrivers (if known), XIP (if known) and Radio version so that users know what the Android Build was tested on and can replicate if neccessary for fault finding purposes.
------------------------------------------
------------------------------------------
If you are unable to obtain any of this information and thus can't make it available through an included readme.txt you should not distribute your rom and keep it for personal use only.
If you are using an exact copy of a present release (e.g. in case of a WinCE rom that has an android 'dual boot' option) you must include the readme.txt from the original rom chef.
If you release a Rom and do not have the required information then you will be asked to either create and include a readme.txt file with your Rom or ask for the thread to be deleted.
If you have any comments or questions on this please feel free to post.
Mark.
** reserved **
Thanks a lot for the quick action, Mark. I am glad to see a first positive response.
If this will establish I hope that
*users are informed about what they get
=>less unneeded questions and thus more room for constructive feedback
*developers have an easier time to benefit from present releases
*new developers must try to get an understanding of what they are doing
=>more quality releases
The original post can be found here.
I think it would be nice to hammer out the readme.txt requirements together with chefs so we can get some convention that satisfies everybody.
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
dcordes said:
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
Click to expand...
Click to collapse
Edited the 1st post to include this
Mark.
Will be following this convention for any future releases
DarkStone1337 said:
Will be following this convention for any future releases
Click to expand...
Click to collapse
Thank you
Future releases soon I hope lol
Mark.
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Excellent rules! We need to improve stability of ports and eliminate all unnecessary questions !
P.S. Hope there won't be any "bogus", or "copy-paste-claim" ROM-s.
dcordes an mskip +1
ahbad said:
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
Click to expand...
Click to collapse
Very good idea. I think we should at least add the rom release date to minimum required readme.txt information.
For the rootfs release date I think we should leave it up to the chefs because I think it will be hard to find out in many cases. Reason is rootfilesystems get passed on 20 times...
In case of the kernel release date it might be a good idea to add it. should be easy to find out. When you grab the kernel e.g. from the two sources I link to in the thread
http://oe.netripper.com/files/htcleo_autobuild/
http://cotulla.pp.ru/leo/Android/
you can just copy paste the date from filename or information on the site. This would be very useful assuming the kernel images will be removed at some point.
On a side note: For both kernel examples the source code repository to add in readme.txt is
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
So currently in every leo rom readme.txt this must be linked to as kernel source reference. netripper autobuild zImages using this exact source code and cotulla zImages share same codebase (although currently the latest changes are unavailable but will be added in git soon)
shufflez said:
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Click to expand...
Click to collapse
To me that seems over exaggerated. Rom version in file name should be enough. Rest can be looked up in readme.txt
So what does everybody think? If we add the release date of kernel and completed rom, do we have an agreement ? In that case we should compile an example and add it in the first post.
best regards
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
David Balfour said:
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
Click to expand...
Click to collapse
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Install to folder
May be a good idea install all files to appropriate folder, not directly root of SDcard as in last darkstone FROYO. Greatly simplify process of testing and changes between several images and don't messy root. Switching between different versions is than as easy as renaming directory.
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
dcordes said:
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Click to expand...
Click to collapse
I agree with you on this theres no need to make things more complicated than they need to be. Although there does need to be some sort of standard for the thread title.
And no I cant think of anything else right now that needs to go in.
dcordes said:
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
Click to expand...
Click to collapse
Also agree that its upto the chef how they want their files set up as long as its clearly stated in the readme.txt what to do to get it working.
Everything sounds fine What needs adding to the first post to make it complete?
Sorry I have been working on my Loader but its all finished now (I hope).
Mark.
HD2 Android Image & Instructions
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
youdaler said:
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
Click to expand...
Click to collapse
I will just give you a friendly warning this time as it is your first post. This thread is for the discussion of information to be included by Android builders.
If you look in the Android forum then you will see working builds by DarkStone and by Dan1j3l. Look at their threads for how to load Android. to answer your question yes Android does work (95%) on the HD2.
Please confirm you have read this so I can delete these posts and keep the thread clean. In futured please only post in the correct thread and if you arent sure then post in the Q&A thread at the top of the Android forum.
Mark.
Understand. Thanks for clarifying.
I think we should extend the readme.txt items with some section like 'expected issues' or 'known problems' .
And in the readme.txt , could help too:
Tested with:
-WinMo rom x.xx.xx
-Radio rom 2.xx.xx
Sent from my HTC Desire using XDA App
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
shadowrelic said:
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
Click to expand...
Click to collapse
You are correct about the ROM, but ROMs also include the kernel (if it didn't, or no kernel was flashed separately, the device would not boot). Yes, other kernels can be flashed on your existing ROM, but it's not necessarily going to be compatible.
Sort of, but there's a lot more than that. See here and here. Later versions of Android will require newer drivers,etc. which the existing kernel won't provide (they'll be outdated). Back porting and additional coding is theoretically possible, but insanely difficult (many times). Even after this some things may still not work.
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
shadowrelic said:
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
Click to expand...
Click to collapse
For both your questions, the Nexus-line devices would be the way to go. They usually have everything working on new Android versions the soonest, and Google always releases their code, etc.
Hi
i can use linux kernel (zimage) to update android kernel if yes ,how ?
thnx
OK, so here's the thing... I'm kind of new in the Android acknowledgement, so I hope that here will be the place where I will get my answers. So here's what I know...
At first I didn't know that Android was Java-based, using a modified Linux kernel which we all know it's C-based (entirely). After a while, I found that there were different firmwares (ROMs) from the original ones, called Stock ones and also different kernels. After reading lots of info about how things actually are, I've decided to root my stock and then I moved to a custom MIUI for my SGSII with a JB implementation. At first it was great, but I had some issues which left me disappointed. Then I moved on to the official MIUI (China - English one). Things got better after I got used to it. The major bugs disappeared, only small ones left and a few crashes, but in time most of them got fixed. Later it crossed my mind, "Why are there so many different kernels and which is the best one for my phone or ROM to be precise?" Well this is where I need your help. I've read some topics that siyah kernel is probably the best kernel, which fits the MIUI rom. The pointing of concrete kernels isn't the kind of answer I was actually searching for. To be honest, I need answers to questions like:
How many kernels are there ?
Which ones are safe ? (I've read that there are badly written ones, so yeah, it needs to be asked)
Statistically, which is the best kernel and is it for the MIUI rom ?
How can I tell that it's suitable for the MIUI rom ? (Since I've read that not all are)
What are the risks of changing the kernel?
How can you test the kernel's behaviour, an app which makes statistics in time or some other methods ?
Believe me, as annoying this topic might seem, lots of us (the newbie users) are burning up the google servers, just to find these answers. I'm really hoping for a reply spam with answers (if possible , spare the trolling ones). Thanks for reading my annoying topic, anyway
Since most of the source is available, basically anyone can build their own kernel at home, so it is hard to tell how many kernels are there.
what isn`t available as open source are most of the OEM-specific drivers. Samsung, for one, doesn`t make most of the drivers' source publicly available, so kernel developers have to make a binary kernel around the binary drivers and literally pray their work well together.
Siyah is safe, but I prefer the stock kernel (I like the stock ROM... go figure). The stock kernel is the only one that is sure to work properly with all the hardware in the phone, because it is the only built from sources for the drivers as well (read my previous paragraph).
Which ones are safe (other than stock and Siyah): you gotta try them for yourself, read other users' remarks and feedbacks, and so on.
Risks:
Very low. As long as the bootloader is good, if the kernel totally malfunctions, just reboot in download mode and flash something else.
Some app may work very well in one kernel and bomb in another. It may crash in some kernels. It is very empyrical.
The problem is that custom kernels don't undergo the same type of quality testing as stock kernels. Developers have very limited resources to do that, and some developers are more interested in having a short time-to-market than a quality product (well, many large corporations act like that as well). At the end of the day we - power users - are the beta testing and quality assurance teams for the kernel developers.
Hi! This is maybe a general dev question, but I'd like to get an answer anyway:
what is exactly the link between an Android release and the kernel it works upon?
I noticed most recent releases use 3.0+ Linux kernels, and others (like the DSCs) use the Phoenix Universal Kernel, which is based on a 2.6.35... So I wonder: is ICS/JB in any way dependant on "newer" kernels?
I understand the answer must be closer to "no", since the pre-alpha build also uses a fork of the PUK, but the fact that it uses a *different version* makes me wonder how much work does it take to get a kernel ready for a newer release, and most importantly... why?
Thanks a lot! Total n00b here, but eager to know more.
Newer kernel not required at least for ICS.
All GB/ICS kernels are based on this kernel (and it's a Dell's lie about using same sources for 407 release as SoD was fixed there without switching timer source):
http://opensource.dell.com/releases/streak/4.05_and_4.07/
kibuuka successfully applied kgsl/genlock patch and it's the only thing actually needed for ICS.
List (a bit old) of changes in Phoenix kernel and later derivatives:
http://forum.xda-developers.com/showpost.php?p=25291276&postcount=3812