I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Dark Reality said:
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Click to expand...
Click to collapse
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
tatperson said:
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Click to expand...
Click to collapse
Try not to think of it in terms of Android versions, but rather, Linux Kernel versions. I believe it is because the 2.6.32 kernel is considered near perfect in terms of stability. Many Linux distributions use that kernel when they want to offer an extremely stable experience to their user base. For bleeding edge features but less stability, most distributions will use version 3+ of the Linux kernel. My guess is that since it is a standard of sorts because of being well-tested, it's just easier to rely on until we are provided with a later version. Just my two cents.
And why wait for Google release of Android 5.0? Why won't we do it ourselves.
tatperson said:
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Click to expand...
Click to collapse
Well, that would make sense if we had the GB kernel, 2.6.35. We have the Froyo kernel, and, AFAIK, there's not even a Froyo ROM for the Photon. Why would there be? It's a Gingerbread phone.
Acvice said:
Try not to think of it in terms of Android versions, but rather, Linux Kernel versions. I believe it is because the 2.6.32 kernel is considered near perfect in terms of stability. Many Linux distributions use that kernel when they want to offer an extremely stable experience to their user base. For bleeding edge features but less stability, most distributions will use version 3+ of the Linux kernel. My guess is that since it is a standard of sorts because of being well-tested, it's just easier to rely on until we are provided with a later version. Just my two cents.
Click to expand...
Click to collapse
This makes sense, and I understand what you mean about Linux kernel versions. I understand the kernel is modular. Once when I was trying Ubuntu, I got a kernel update. Didn't affect anything, just had to reboot. Couldn't tell what it changed.
Also, I just noticed that AOKP Build 8 uses kernel 3.0.1, according to the screenshot on the left. Kinda torn on trying AOKP. On one hand, I'm not a "pink unicorns" kind of guy. On the other, the default wallpaper and status bar icons are nice. Another AOKP ROM featured a pretty cool textured status bar. But when I asked what AOKP had over CyanogenMod, the only answer I got was "swagger". In fact... well, that's a completely different topic. New Topic button, here I come. Hopefully the powers that be will see this as valuable conversation, not spamming up the boards...
//edit: AOKP screenshot lies, it uses the same kernel as the rest (screenshot is of another device, to be fair).
Dark Reality said:
Well, that would make sense if we had the GB kernel, 2.6.35. We have the Froyo kernel, and, AFAIK, there's not even a Froyo ROM for the Photon. Why would there be? It's a Gingerbread phone.
This makes sense, and I understand what you mean about Linux kernel versions. I understand the kernel is modular. Once when I was trying Ubuntu, I got a kernel update. Didn't affect anything, just had to reboot. Couldn't tell what it changed.
Also, I just noticed that AOKP Build 8 uses kernel 3.0.1, according to the screenshot on the left. Kinda torn on trying AOKP. On one hand, I'm not a "pink unicorns" kind of guy. On the other, the default wallpaper and status bar icons are nice. Another AOKP ROM featured a pretty cool textured status bar. But when I asked what AOKP had over CyanogenMod, the only answer I got was "swagger". In fact... well, that's a completely different topic. New Topic button, here I come. Hopefully the powers that be will see this as valuable conversation, not spamming up the boards...
Click to expand...
Click to collapse
AOKP has more features than cyanogen, and dont mind the pink unicorn. Its only a boot animation. And the AOKP team changed it here recently so it really doesnt look as obtrusive as it used to. CNA happens to be my personal favorite.
Well, I kept the boot animation from CM10, which I really like, so whatever ROM I stick with will probably just use that, unless I find something better.
Using AOKP now. A little annoying that I can't add lock slider items, but I can live with it. I see what they mean by swagger -- it's a toggle. I think it's like "Awesomeness Detection" in Rockband 2. That is, a toggle option that does nothing but confuses the user or makes them think they're doing something special. A placebo. But in reality there is no code to it. (I'm assuming about AOKP. Harmonix confirmed this about Rockband 2 -- 3 years after the game shipped.) But yeah, boot animation is fine for now (if a little small). And I'm actually using an AOKP wallpaper. It's the one with the shadow of the guy with the swords. Pretty awesome. (Is that what UnicornPorn.apk is? The wallpapers?)
Curious about CNA but I'm going to give AOKP a few days to settle in. Battery is a big thing for me though.
its actually a nvidia thing, i imagine a quick google search between linus and nvidia will tell ya how he feels about them ;P. (if you dont believe me the transformer lineup has 2.6.39 as its ICS kernel)
you can use any kernel version you want so long as it has all the proper stuff in it, the big thing most people overlook tho is not a lot of people look at the linux kernel and see all the commits. which if you are making kernels i highly suggest you do as there was some awesome battery saving stuff in 2.6.38 as well as some overall speedups.
the version number changing is used to signify a stable release. like 3.0 or 3.1, 3.2 etc.
its entirely possible (hell sometimes needed for some kernel sources) to take what the OEM provides take the corresponding linux kernel (in this case 2.6.32) and overlay the oem code. the reason why most dont do it is cuz it takes a long time. once you have the linux tree merged with your device specific files you can then backport patches much easier.. and at that point you could have a 3.x kernel using the same 2.6.32 stuff from the oem. wont help you overall on booting and fixing camera etc in ics but it will give ya plenty of improvements in just the kernel itself
Dark Reality said:
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Click to expand...
Click to collapse
well from a laymen point of view i run and love most of th3bills roms(PORTS) from jokersax.com and considering my mopho(photon) is over a year old and getting almost 7000 antutu and 4000+ quadrant scores(which makes a new GALAXY NEXUS STOCK LOOK SLOW)...i don't care what kernel when im blazing like that.lol If its kicking azz dont fix
Related
Sorry I've been gone for a while, and my old thunderbolt is still running a Senseless version of Gingertheory (gingerbread) Rom, I would like to upgrade to a newer gingerbread rom now...what is the ASOP stuff? please enlighten me on which Rom I should run...I've got a replacement phone from Verizon, my text messages were all screwed up and not coming in properly. Anyways. I guess I should download clockwork mod on my new phone.
I don't need bloatware, just basics and a fast phone with good battery life.
NeoNxz said:
Sorry I've been gone for a while, and my old thunderbolt is still running a Senseless version of Gingertheory (gingerbread) Rom, I would like to upgrade to a newer gingerbread rom now...what is the ASOP stuff? please enlighten me on which Rom I should run...I've got a replacement phone from Verizon, my text messages were all screwed up and not coming in properly. Anyways. I guess I should download clockwork mod on my new phone.
I don't need bloatware, just basics and a fast phone with good battery life.
Click to expand...
Click to collapse
The best GB Rom is whichever one you like.
for sense it would be a theory rom. for aosp either liquid or theory.
I am currently running gingeritis3D and i love it. I have not ran any other GB roms but i dont feel the need to. This rom is kicka$$ and so smooth. Got all the sense 3.0 goodies and the only bug that i know of an issue with voicemail which i fixed by just using google voice. I really highly recommend it
I was also told that the latest version (VIII) i based of the latest GB leak so its very stable
So what is ASOP? Can someone explain to me? Is it Senseless??
NeoNxz said:
So what is ASOP? Can someone explain to me? Is it Senseless??
Click to expand...
Click to collapse
That's pretty clearly explained in my thread. Link in my sig.
NeoNxz said:
So what is ASOP? Can someone explain to me? Is it Senseless??
Click to expand...
Click to collapse
Written by loonatik78
"Sense ROMs: Sense ROMs are built from RUUs, either officially released or leaked. An RUU is the complete update file for a handset; including the bootloader, radio, and ROM. Currently, all Gingerbread Sense ROMs are based on leaked RUUs. Each RUU has a version number, for example 2.10.605.0. The higher the number, the newer it is. Newer is generally better. Devs will usually include the base RUU version number in their OP. I like to think of custom ROMs developed on a common base as a family of sorts. They're going to generally have some similarities. They can have major differences as well. Some things about them won't ever change though.
Sense ROMs come in many flavors; 2.1, 2.1/3.0 hybrid, 3.0. It's really hard to tell what you like until you play with some and get to know them.
AOPS ROMs: AOSP ROMs are not built from leaked or released RUUs. They are built upon code obtained through the Android Open Source Project and are custom built for the devices. HTC, and manufactures in general, don't support AOSP being developed for their device. As a result, AOSP devs basically have to figure it out for themselves which makes the ROMs much more experimental. These ROMs typically come out in 1 or more versions, usually identified by date of release if it's a final release version, or an RC (release candidate) version if it's still in beta testing. Think of the version number and RC/beta number like the RUU number of a Sense ROM. For instance, CM7.0.3 may have several release versions that are only very slightly different. Then you may have several CM7.1.0 Beta or RC candidates that may less stable, but being offered for real world use and user feed back. That's basically the picture for the dInc currently, not the Tbolt, so don't quote me. CM releases are generally going to all look and feel the same and carry the same group of features. OMFGB is going to be making a name for itself with different features and characteristics. You won't know which you like until you try them."
Mig1234 said:
Written by loonatik78
"Sense ROMs: Sense ROMs are built from RUUs, either officially released or leaked. An RUU is the complete update file for a handset; including the bootloader, radio, and ROM. Currently, all Gingerbread Sense ROMs are based on leaked RUUs. Each RUU has a version number, for example 2.10.605.0. The higher the number, the newer it is. Newer is generally better. Devs will usually include the base RUU version number in their OP. I like to think of custom ROMs developed on a common base as a family of sorts. They're going to generally have some similarities. They can have major differences as well. Some things about them won't ever change though.
Sense ROMs come in many flavors; 2.1, 2.1/3.0 hybrid, 3.0. It's really hard to tell what you like until you play with some and get to know them.
AOPS ROMs: AOSP ROMs are not built from leaked or released RUUs. They are built upon code obtained through the Android Open Source Project and are custom built for the devices. HTC, and manufactures in general, don't support AOSP being developed for their device. As a result, AOSP devs basically have to figure it out for themselves which makes the ROMs much more experimental. These ROMs typically come out in 1 or more versions, usually identified by date of release if it's a final release version, or an RC (release candidate) version if it's still in beta testing. Think of the version number and RC/beta number like the RUU number of a Sense ROM. For instance, CM7.0.3 may have several release versions that are only very slightly different. Then you may have several CM7.1.0 Beta or RC candidates that may less stable, but being offered for real world use and user feed back. That's basically the picture for the dInc currently, not the Tbolt, so don't quote me. CM releases are generally going to all look and feel the same and carry the same group of features. OMFGB is going to be making a name for itself with different features and characteristics. You won't know which you like until you try them."
Click to expand...
Click to collapse
Thank you...Given this I will go with an AOSP rom..which do you guys prefer?
NeoNxz said:
Thank you...Given this I will go with an AOSP rom..which do you guys prefer?
Click to expand...
Click to collapse
Highly subjective question, but i like cyanogen mod. The latest version is generally not posted for it on xda though. Have to go to rootzwiki to find it under their thunderbolt forum.
NeoNxz said:
Thank you...Given this I will go with an AOSP rom..which do you guys prefer?
Click to expand...
Click to collapse
Cm7 or omgb/omfgb are good. Can't really go wrong with those
Sent from my ADR6400L using Tapatalk
thunderstick 2.2 is great very smoth find it in rom manager.He also has some great mods to go with it
Im running SHIFTAO5P from DROIDTH3ORY. Its fast and awesome on battery life
Sent from my SHIFTAO5P using XDA App
chefmg said:
thunderstick 2.2 is great very smoth find it in rom manager.He also has some great mods to go with it
Click to expand...
Click to collapse
I went with thunderstick 2.2...read into the AOSP threads and saw the voice mail issue and don't want any problems now...so far so good! thanks guys
NeoNxz said:
I went with thunderstick 2.2...read into the AOSP threads and saw the voice mail issue and don't want any problems now...so far so good! thanks guys
Click to expand...
Click to collapse
The voicemail issues are with Sense ROMS... not AOSP. VM notifications actually work on AOSP.
Sent from my SHIFTAO5P using XDA App
I have tried most sense based ROMs, I keep going back to Gingeritis 3D. BAMF is a close second, all other ROMs I have tried I get FC issues, and other wierd **** where I will just flash back to 3D. Keep in mind, each phone is different, so results will vary. Try them all out, nandroid is your friend!
This is not a thread for "which one is better."
I've not found anywhere in the i777 forums a description of how the two AOSP roms relate in similarities and differences, something I believe would be a common question.
From my googling, it appears that AOKP has all of the same features as CM9, just with a different interface.
Those of you who know best: care to share your wisdom of other differences?
From what I've seen, AOKP is kind of a smaller project than CM in terms of device coverage, but that allows them to implement more features it seems. I found a pretty quick and simple write-up here: http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9
I tried them both, I'm staying with AOKP
tysj said:
From what I've seen, AOKP is kind of a smaller project than CM in terms of device coverage, but that allows them to implement more features it seems. I found a pretty quick and simple write-up here: http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9
Click to expand...
Click to collapse
Great article!
Thanks for the thread, OP. I had been wondering this myself. I would like to use stock ICS (a la Galaxy Nexus) on my gs2, but CM9 and AOKP seem as close as I'm going to get for now (unless it's out there and I'm just not seeing it). Regardless, CM9 was giving me fits with a couple of games that I like to play and I used AOKP for a couple of hours, but that's about it. I'm not sure which is closer to stock ICS, but I'm told that CM9 is.
College kids nowadays, are so smart. Good for them.
Great read. Im leaning more towards AOKP. Been running Tasks rom for a few days and im loving it.
I did use cm9 for a while but now on AOKP and just loving it
It's really very snappy and great battery life
Task did a wonderful job
I've leaned more towards using AOKP, it's speedy, feature packed and more stable in comparison to the CM9 Nightlies. Until there's a stable release, I'm sticking with AOKP.
AOKP is really amazing, it's a great work put by people that care a lot about quality.
CM9 is breakthrough, it's the base pillar of several roms and it has really talented people contributing to it. Without CM support many devices wouldn't have AOSP ICS.
Both are great choices no matter which one you pick.
Fortunately we have great guys like atinm, codeworkx, Entropy and task (among others) that make this happen.
blackplague1347 said:
Thanks for the thread, OP. I had been wondering this myself. I would like to use stock ICS (a la Galaxy Nexus) on my gs2, but CM9 and AOKP seem as close as I'm going to get for now (unless it's out there and I'm just not seeing it). Regardless, CM9 was giving me fits with a couple of games that I like to play and I used AOKP for a couple of hours, but that's about it. I'm not sure which is closer to stock ICS, but I'm told that CM9 is.
Click to expand...
Click to collapse
I also had this need and came across this.
http://forum.xda-developers.com/showthread.php?t=1601518
This was my first flashed ROM so have nothing to compare to other than stock Sammy Touchwiz'd ICS but it is great. Might just be what you're looking for.
tysj said:
From what I've seen, AOKP is kind of a smaller project than CM in terms of device coverage, but that allows them to implement more features it seems. I found a pretty quick and simple write-up here: http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9
Click to expand...
Click to collapse
Excellent report, thanks for sharing bro
skblr said:
I did use cm9 for a while but now on AOKP and just loving it
It's really very snappy and great battery life
Task did a wonderful job
Click to expand...
Click to collapse
x2.
Why isnt i777 supported directly by AOKP? Is it because they are on a much smaller scale compared to CM? Will the i777 ever get AOKP direct support at some point? Not that it matters, Task650's Roms is badass as it is but I still wonder why it isnt supported.
I also have used both and I was a huge supporter of CM. I like AOKP better. As it stands right now I think AOKP is more polished and has more features currently. When CM9 comes more along I'm sure it will be equally as good. I flashed CM9 the day before yesterday just to see what progress has been made. I see they merged the custom lockscreen stuff and some other things, but I still found there were some things in AOKP that I missed so I flashed right back to AOKP. The good thing I must say is that both are AOSP and can usually go between the two without wiping data. I went from AOKP, to CM9, back to AOKP without doing a data wipe (just wiped the caches) and everything worked fine
tysj said:
From what I've seen, AOKP is kind of a smaller project than CM in terms of device coverage, but that allows them to implement more features it seems. I found a pretty quick and simple write-up here: http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9
Click to expand...
Click to collapse
It's a good article but it's quite dated given the number of nightly updates since it was written. CM9 has come a long way in terms of features that have been added:
- Theme manager
- Profiles, which allow you to control features available in the power saver option
- Lock screen shortcut configuration
- Galaxy SII specific advanced features
- Performance options OC, governor, etc.
Right now, other than the weather on the notification bar, you can get pretty much get in CM9 the same features in AOKP.
One thing that AOKP doesn't have is the ability to update to the latest nightly through ROM Manager in a few (4) clicks. That's is a big plus if you are an update junkie.
In any case my recommendation is that you try them both. It's all a matter of personal choice.
projekt1 said:
Why isnt i777 supported directly by AOKP? Is it because they are on a much smaller scale compared to CM? Will the i777 ever get AOKP direct support at some point? Not that it matters, Task650's Roms is badass as it is but I still wonder why it isnt supported.
Click to expand...
Click to collapse
It's all about kernel sources. The ICS kernel sources have not been released for the i777, so the AOKP team won't touch it.
I just bought this phone the other day, after having an HTC Inspire for over a year. I really enjoyed the benefits of it being a sister phone of the Desire HD, such as really phenomenal ROM development.
I know that there aren't any sources released for this phone, but after using LordClockan's Ice Cold Sandwich, I just can't get used to this TouchWiz.
If anyone has started a project, I can help out with anything that I can.
If not, would anyone here like to try & help out?
My ROM building knowledge is non existent, but I'm dedicated to get this going.
Sent from my SAMSUNG-SGH-I717 using xda premium
I sure hope so! I loved existz work on the Inspire!
one7dchevy said:
I sure hope so! I loved existz work on the Inspire!
Click to expand...
Click to collapse
Him, TwistedUmbrella, and LordClockan's teamwork is a testament to the wonderful community her at XDA!
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope it's comming!
Have you tried the ICS roms that we DO have? They're not AOKP; but they run the AOSP stock apps and they've been themed well enough to be pretty damn close -- all while maintaining full s-pen capability, which is something even the CM9 folks can't claim yet (they don't have button functionality)...
Need kernel source first!!
Sent from my SAMSUNG-SGH-I717 using xda premium
paleh0rse said:
Have you tried the ICS roms that we DO have? They're not AOKP; but they run the AOSP stock apps and they've been themed well enough to be pretty damn close -- all while maintaining full s-pen capability, which is something even the CM9 folks can't claim yet (they don't have button functionality)...
Click to expand...
Click to collapse
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
Stock apps will almost always work on ANY rom with little to no modification required, regardless of whether they are from an AOSP rom.
The current roms are heavily based on the leaked ICS rom with only small tweaks universal between nearly all roms, things like themes, lockscreens, sounds, animations, etc. are all pretty simple if you know what you are doing (something admittedly, I have not personally built a rom but Im very familiar with the process).
When Cyanogen (or possibly AOKP, Im not familiar with their roms and how they are developed) is released, we will begin to see true rom development begin to happen. Until there is source code from Samsung, we will continue to see roms with Touchwiz all over them.
To show you how easy this is, here is a link to have a bot build a rom for you for any of the Galaxy 1 or 2 phones.
http://romkitchen.org/
Click your phone choice (Galaxy 1 or 2 currently, the Note is NOT supported yet).
Click Generator in the upper right hand corner.
Use the six tabs across the top of the page to choose your Modem, Kernel, Theme, stock apps, etc.
Of course, this only gives you a base to work with, from there, its pretty easy to swap in or out what you want.
Think about it like this, I can give you a copy of Windows already pre-configured for your PC and them or customize it just by changing some registry entries and including the data files (wallpapers for example). The included drivers would be pre-built meaning that 'I' didnt actually write them, nor did I change much in Windows, all I did was provide the files containing the data and changed a few settings to link to the files.
Dsmforlife92 said:
Need kernel source first!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not entirely true. I know some ICS roms that have been hacked to death to get at least partial functionality.
I'm thankful that some devs have taken their time to do what they have done, but what I am looking for hasn't been done.
AOKP is like AOSP, but more tweaks are added.
[edit] As for myself, I could care less about S Pen support. I haven't even used it, nor do I think I ever will. I got this phone for the monster sized screen.
Sent from my SAMSUNG-SGH-I717 using xda premium
littlewierdo said:
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
Stock apps will almost always work on ANY rom with little to no modification required, regardless of whether they are from an AOSP rom.
The current roms are heavily based on the leaked ICS rom with only small tweaks universal between nearly all roms, things like themes, lockscreens, sounds, animations, etc. are all pretty simple if you know what you are doing (something admittedly, I have not personally built a rom but Im very familiar with the process).
When Cyanogen (or possibly AOKP, Im not familiar with their roms and how they are developed) is released, we will begin to see true rom development begin to happen. Until there is source code from Samsung, we will continue to see roms with Touchwiz all over them.
To show you how easy this is, here is a link to have a bot build a rom for you for any of the Galaxy 1 or 2 phones.
http://romkitchen.org/
Click your phone choice (Galaxy 1 or 2 currently, the Note is NOT supported yet).
Click Generator in the upper right hand corner.
Use the six tabs across the top of the page to choose your Modem, Kernel, Theme, stock apps, etc.
Of course, this only gives you a base to work with, from there, its pretty easy to swap in or out what you want.
Think about it like this, I can give you a copy of Windows already pre-configured for your PC and them or customize it just by changing some registry entries and including the data files (wallpapers for example). The included drivers would be pre-built meaning that 'I' didnt actually write them, nor did I change much in Windows, all I did was provide the files containing the data and changed a few settings to link to the files.
Click to expand...
Click to collapse
I appreciate the explanation, but you're not telling me anything I don't already know. I was just saying that our current roms have been themed/tweaked well enough to look like AOSP, so they're not that bad; and, you don't really have to deal with touchwiz annoyances anymore if you don't want to -- trebuchet, apex, and nova all work well.
CM9 or AOKP they're not, but they're exceptional given the single source-less leak we have right now... and they certainly blow away stock touchwiz GB! lol
littlewierdo said:
I hate to disagree but they arent even close (no offense to current devs, this isnt their fault).
S-pen functionality needs either the source from Samsung or a new driver has to be written from scratch, which isnt worth the time or effort considering that Samsung likely will soon be releasing source for ICS (usually a few weeks after the OS is officially released).And, if he rumors are true, ICS should be official soon (however, to be clear, I dont believe ICS is coming any time soon).
The reason these other roms have S-Pen support is, surprise surprise, they COPIED large sections of code from the stock leaked release, where, conveniently, everything ALREADY WORKS!!
.
Click to expand...
Click to collapse
Pen apparently works in the CM9 build for the international note. Haven't looked at the source myself yet, but it is probably just the standard wacom driver.
zonyl said:
Pen apparently works in the CM9 build for the international note. Haven't looked at the source myself yet, but it is probably just the standard wacom driver.
Click to expand...
Click to collapse
AFAIK, they haven't gotten the button to work yet, but it's promising.
Its going to take a lot kf time and effort and prob a group effort to get aosp or aokp roms for our phone. I believe the reason skyrocket and 989 have it is because they have had a lot of devs working together for long time on it. I can get a booted aosp rom hut no sound no camera no data. So theres a lot of work needed to be done
Sent from my SAMSUNG-SGH-I717 using xda premium
I apologize for my noobish question, but how are the ASOP builds starting to roll out w/o source being released?? I understand you can compile aosp builds on your own, but doesnt the source code provide all the tweaks you need to optimize it on a device to device basis?
There's no ICS source for the Captivate either, but we are officially supported on CM9. Very glad!
Sent from my Captivate using Tapatalk!
if there is good source from another device that is near this one then porting could be possible.
The short answer is a combination of two things based on what I can tell.
They are actually using the existing kernel for the leaked ICS roms and beginning to dissect them. As far as I know, the current AOKP roms being used are using either an unmodified original kernel from ULD3 or 'very slightly' modified/patched kernel from ULD3 with a few tweaks for overclocking support and whatnot.
As far as what is happening with the Captivate, I believe they are taking heavy sections from the Gingerbread source code and splicing it in to their ICS kernel and changing what they need to for ICS compatibility.
Also, similar devices that have ICS source code floating around can also be spliced up.
I am only speculating here since I am not involved in the projects, if someone knows more than I, feel free to speak up.
Good morning or evening to all,
this is my first post on the forum, so please by patient. I am new to the world of custom ROMs and I tried to educate myself by reading the noob guides. However, my questions become more and more widespread, and I am not sure where to try to find the answers.
To be clear: I am NOT asking about 'what ROM is best' and such. I would like to know more about the following:
1) There are CM7 ROMs (Netrino for example), CM9 and CM10 ROMs. As I understand it, because there have been stock files from MOTO, CM& ROMs can have stable kernels, hardware acceleration etc etc. However, if there is no hardware acceleration, how can CM9 ROMs be smoother?
2) In the same vain, how can CM9 and 10 ROMs have kernels? Where they written from scratch? And how can they be faster than stock?
3) Due to my SOD problems, I flashed several ROMs and currently have a CM9 one, which is stable so far. If I go back to a CM7 one, such as Netrino 2.9, what differences would I see? Will the latter be faster or more efficient? Smoother? Or should I just leave it alone, since it works?
4) And to reverse the question, how can a CM10 ROM be smoother, if it does not have hardware acceleration and drivers?
I am sorry about the bombardment. I do not want to waste anybody's time, but some pointers would be helpful. Thanks in advance!
to give you a shorter answer for better understanding:the stock roms are mostly based on android 2.3.6 which is the newest firmware.the roms only differ from the regions and mostly have battery tweaks or connection tweaks etc...
lets go to cm 9 and 10.cm9 is basically android4.0 and cm10 android 4.1.these are faster because they do not have many unnecessary apps like stock roms do.
i hope this explains a bit...
peddarson said:
to give you a shorter answer for better understanding:the stock roms are mostly based on android 2.3.6 which is the newest firmware.the roms only differ from the regions and mostly have battery tweaks or connection tweaks etc...
lets go to cm 9 and 10.cm9 is basically android4.0 and cm10 android 4.1.these are faster because they do not have many unnecessary apps like stock roms do.
i hope this explains a bit...
Click to expand...
Click to collapse
Thanks for the answer, peddarson.
Can it be that the only difference between roms is the absence of apps? Then, netrino should be the fastest of them all. And where does the absence of hardware acceleration and drivers factor in?
A few of your questions could be easily answered just by flashing the roms and seeing for yourself. Or Googling.
For example, you keep asking about hardware acceleration without knowing what it does or what it means. If you did, you'd know it plays a much bigger role with how apps function than the UI. The "smoothness" described in CM10 is with the UI and not the apps themselves (hint), while certain programs like the camera app, Chrome, etc. have a tendency to be unstable (hint.) You might be able to piece together that the UI isn't as ha-dependent as you thought. Maybe the visual experience has more to do with the actual software than hardware.
The answer to a few other of your questions is that these ROMs play off an original source and then tweaked to be optimized to the author's liking. Kernels can be overclocked, memory management can be altered, etc. If you want to know specifics, look into what each specific ROM does. It's right there in black and white.
nh777 said:
A few of your questions could be easily answered just by flashing the roms and seeing for yourself. Or Googling.
For example, you keep asking about hardware acceleration without knowing what it does or what it means. If you did, you'd know it plays a much bigger role with how apps function than the UI. The "smoothness" described in CM10 is with the UI and not the apps themselves (hint), while certain programs like the camera app, Chrome, etc. have a tendency to be unstable (hint.) You might be able to piece together that the UI isn't as ha-dependent as you thought. Maybe the visual experience has more to do with the actual software than hardware.
The answer to a few other of your questions is that these ROMs play off an original source and then tweaked to be optimized to the author's liking. Kernels can be overclocked, memory management can be altered, etc. If you want to know specifics, look into what each specific ROM does. It's right there in black and white.
Click to expand...
Click to collapse
The thing is that, as I said, I do not want to flash the ROMs (again) and see. I am not interested in learning the specific merits or disadvantages of each. I just want some pointers on what hardware acceleration does, how it synergizes with the UI, how different ROMs come about with or withoit drivers etc. And because I don't know, I ask (hint). Your post, for example, clarified some of these things, sarcasm aside. It would clarify even more if you could provide some links for me to pursue.
Haha. Welcome to XDA. People are quite unforgiving and harsh with noobs, I appologize on their behalf. I am still pretty new myself but for the past 4 months, I have read and learned quite a lot and have flashed many roms.
My first love was actually neutrino. I always seem to crawl back to neutrino rom because it is ridiculously smooth and stable for me. I've seen many people have issues here and there but I really have no complaints about neutrino. I have tried CNA, which is a port by Bill based off of CM10. I was quite impressed with how nicely it ran. The battery life wasn't as good as I'd like and I require a camera so I flashed back to neutrino.
There are two new cm7 based roms that have surfaced recently, Atrix MRom and TopSmarts. I tried MRom and it is quite a nice rom. I wasn't a fan of the Holo Launcher that it uses so now I'm on TopSmarts. This rom has been great for me. Like I said, I always end up back with neutrino but this is quite the contender. It's pretty new and only the first version so it will most likely be updated often.
I'd give a couple cm7 roms a go, if I were you. Just make sure you make a Nandroid backup of your current rom so you can always restore. I feel that Cm7 roms have much better battery life and tend to be more stable. The only issue I have with cm7 is there's no webtop option. Other than that, I couldn't be happier with TopSmarts or Neutrino. Both of the devs are also really friendly and quite helpful.
Hope this helps. If you have any questions, you're welcome to PM me.
Sent from my MB860 using xda app-developers app
ProudGrognard said:
The thing is that, as I said, I do not want to flash the ROMs (again) and see. I am not interested in learning the specific merits or disadvantages of each. I just want some pointers on what hardware acceleration does, how it synergizes with the UI, how different ROMs come about with or withoit drivers etc. And because I don't know, I ask (hint). Your post, for example, clarified some of these things, sarcasm aside. It would clarify even more if you could provide some links for me to pursue.
Click to expand...
Click to collapse
Wait, what? Then what's this?
"If I go back to a CM7 one, such as Netrino 2.9, what differences would I see? Will the latter be faster or more efficient? Smoother?"
Come on, guy.
Google hardware acceleration and you might find out that, like I suggested with my previous post, it doesn't necessarily have to do with the UI. Sorry, but I'm not spoon-feeding you links that you could have found in less time than making this post.
I've already explained the different ROMs are based on current software and then ported/tweaked. If you looked at the bugs with each ROM, you'd figure out the holes that drivers would fix.
nw21st (Alphabet district, amirite?) had a great suggestion which was that cm7 roms were easily the most stable. Why? Atrix has drivers up to 2.3.6 so nothing's missing. If you're wondering what differences you'll see in cm7 vs cm9 then you aren't using your phone enough, eg, camcorder. That's fine. Loads of people are on cm9/10 and accept the bugs and limitations. But hands down, cm7 ROMs will remain the most stable.
ProudGrognard said:
Good morning or evening to all,
this is my first post on the forum, so please by patient. I am new to the world of custom ROMs and I tried to educate myself by reading the noob guides. However, my questions become more and more widespread, and I am not sure where to try to find the answers.
To be clear: I am NOT asking about 'what ROM is best' and such. I would like to know more about the following:
1) There are CM7 ROMs (Netrino for example), CM9 and CM10 ROMs. As I understand it, because there have been stock files from MOTO, CM& ROMs can have stable kernels, hardware acceleration etc etc. However, if there is no hardware acceleration, how can CM9 ROMs be smoother?
2) In the same vain, how can CM9 and 10 ROMs have kernels? Where they written from scratch? And how can they be faster than stock?
3) Due to my SOD problems, I flashed several ROMs and currently have a CM9 one, which is stable so far. If I go back to a CM7 one, such as Netrino 2.9, what differences would I see? Will the latter be faster or more efficient? Smoother? Or should I just leave it alone, since it works?
4) And to reverse the question, how can a CM10 ROM be smoother, if it does not have hardware acceleration and drivers?
I am sorry about the bombardment. I do not want to waste anybody's time, but some pointers would be helpful. Thanks in advance!
Click to expand...
Click to collapse
1) Optimization, mainly
2) Motorola released the sources of each Atrix kernel (International, EMEA, ATT etc...). Devs can use it to make tweaked, optimized versions
3) By flashing a CM7, you will go back on Gingerbread (GB). CM9 = ICS and CM10 = Jelly Bean (JB). The main differences you can see are the different interfaces (GB looks ugly to me now...) and some apps like Chrome are missing on GB. Also CM7 is super stable, if you want a stable and customizable ROM then you should try it.
4) CM10 had a lot of optimizations all based around apps preloading/compiling (To be verified), also the animations were changed to make it look smoother. Stuffs like scrolling, animations are smoother on ICS/JB than GB because of optimizations too. If you flash CM7 you'd have the same kind of "smooth feeling" because of a high framerate but the apps won't load as fast as with CM9/10.
Personally I use CM10 even if it's not well supported (Not as well as GB) but ICS/JB is coming soon so I'm trying to get used to it for when it officially comes. I consider GB as a legacy OS, there won't be anything really new/innovative on it since Google doesn't develop any new app on it.