what is the different between kernel 2.6 and 3.0 - Nexus S Q&A, Help & Troubleshooting

as the title, on ics rom. what is the different between kernel 2.6 and 3.0?
who can tell me?

its the kernel of linux in general lol
they stopped at 2.6.something now they are on 3.0
see http://www.phoronix.com/scan.php?page=news_item&px=OTUwMg
Yay! Let the bikeshed painting discussions about version numbering begin (or at least re-start).
I decided to just bite the bullet, and call the next version 3.0. It will get released close enough to the 20-year mark, which is excuse enough for me, although honestly, the real reason is just that I can no longer comfortably count as high as 40.
The whole renumbering was discussed at last years Kernel Summit, and there was a plan to take it up this year too. But let's face it - what's the point of being in charge if you can't pick the bike shed color without holding a referendum on it? So I'm just going all alpha-male, and just renumbering it. You'll like it.
Now, my alpha-maleness sadly does not actually extend to all the scripts and Makefile rules, so the kernel is fighting back, and is calling itself 3.0.0-rc1. We'll have the usual 6-7 weeks to wrestle it into submission, and get scripts etc cleaned up, and the final release should be just "3.0". The -stable team can use the third number for their versioning.
So what are the big changes?
NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver changes, and a lot of random fixes, but the point is that 3.0 is *just* about renumbering, we are very much *not* doing a KDE-4 or a Gnome-3 here. No breakage, no special scary new features, nothing at all like that. We've been doing time-based releases for many years now, this is in no way about features. If you want an excuse for the renumbering, you really should look at the time-based one ("20 years") instead.
So no ABI changes, no API changes, no magical new features - just steady plodding progress. In addition to the driver changes (and the bulk really is driver updates), we've had some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!) and in general this is supposed to be a fairly normal release cycle. The merge window was a few days shorter than usual, but if that ends up meaning a smaller release and a nice stable 3.0 release, that is all
good. There's absolutely no reason to aim for the traditional ".0" problems that so many projects have.
In fact, I think that in addition to the shorter merge window, I'm also considering make this one of my "Linus is being a difficult ^&^hole" releases, where I really want to be pretty strict about what I pull during the stabilization window. Part of that is that I'm going to be travelling next week with a slow atom laptop, so you had better convince me I *really* want to pull from you, because that thing really is not the most impressive piece of hardware ever built. It does the "git" workflow quite well, but let's just say that compiling the kernel is not quite the user experience I've gotten used to.
So be nice to me, and send me only really important fixes. And let's make sure we really make the next release not just an all new shiny number, but a good kernel too.
Ok?
Go forth and test,
Linus
Click to expand...
Click to collapse

just for commemoration

same question.why brainmaster's ics version's kernal is also 2.6x as Gingersnap,but official ics is 3.0.
how about future's OTA for NS?

Singnal said:
same question.why brainmaster's ics version's kernal is also 2.6x as Gingersnap,but official ics is 3.0.
how about future's OTA for NS?
Click to expand...
Click to collapse
Because its probably a moded rom to look like its ics.
if i'm not mistaken, ics is based on the latest linux kernal - which is 3.0 (or 3.2 by now not sure )

the biggest differents are?

Have you read anything that I just posted yet? >_<
Read what i posted earlier.. and if you want follow the link.
Read under:
So what are the big changes? in my previous post!

Brainmaster's ROM isn't pretend ICS, it's the real thing. The new kernel 3.whatever won't be available until the sources are released, and there's not a huge gulf between those kernel versions anyway, it's more cosmetic
Sent from my SNES

Related

Developers of ROMs

Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.
Agreed! (This text is just to pass 10 char limit)
Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.
but arnt all these builds just different attempts at getting a working 1.5 build?
Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.
well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!
Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.
momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?
Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave
I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.
Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.
As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.
momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave
I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.
Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.

New Faster HTC Sense UI out today!

http://www.engadget.com/2009/09/14/htc-hero-firmware-update-peps-up-the-sense-experience-to-somethi/
Good news for HTC Hero early adopters: HTC has a new firmware update out now for the device that considerably speeds up the interface, if the multitude of reports to be found on the internet can be believed. Seeing as this was the number one gripe with the overall excellent UI, we're incredibly glad HTC has gotten work on this, and we'll be spending some more time with the device to return our newly tinted impressions. There's a video after the break demonstrating changes, and most actions seems quite a bit quicker and smoother, all the way down to opening and closing the apps menu, and sliding between home screens.
Click to expand...
Click to collapse
I hope the devs are able to snatch up a copy of that and get it into our already awesome roms! I vote for MyHero 0.1.1 myself
Wow. WRONG SECTION.
Okay, you do realize that it's the KERNEL that provides an increase in speed for the Hero ported builds, right?
Well, if you didn't...now you do. The build number does not matter. As for that OTA update that HTC is delivering, that comes standard with the HTC kernel that XDA had ages ago...and is NO LONGER in use. Most developers are using 2.6.29.6 - not 2.6.27! You do the math and figure out which would be more recent. JAC and CC's latest is based on the 2.83 build. While Drizzy's latest is based on the 2.86 build.
That HTC update is only the 2.73 build packaged in-full.
Reignzone said:
Okay, you do realize that it's the KERNEL that provides an increase in speed for the Hero ported builds, right?
Well, if you didn't...now you do. The build number does not matter. As for that OTA update that HTC is delivering, that comes standard with the HTC kernel that XDA had ages ago...and is NO LONGER in use. Most developers are using 2.6.29.6 - not 2.6.27! You do the math and figure out which would be more recent. JAC and CC's latest is based on the 2.83 build. While Drizzy's latest is based on the 2.86 build.
That HTC update is only the 2.73 build packaged in-full.
Click to expand...
Click to collapse
Hmm... That's not quite correct. That's like saying MS Word is slow because of the Windows kernel. MS Word is most of the problem...
Yes, the devs here have done some great stuff squeezing more speed out of the kernels with swap partitions and BFS - but that is only half the equation. Sense UI is an APP that run on top of the kernel, so it stands to reason that HTC could have optimized the code in Sense UI (and other apps) to improve performance.
-V
Reignzone said:
Okay, you do realize that it's the KERNEL that provides an increase in speed for the Hero ported builds, right?
Well, if you didn't...now you do. The build number does not matter. As for that OTA update that HTC is delivering, that comes standard with the HTC kernel that XDA had ages ago...and is NO LONGER in use. Most developers are using 2.6.29.6 - not 2.6.27! You do the math and figure out which would be more recent. JAC and CC's latest is based on the 2.83 build. While Drizzy's latest is based on the 2.86 build.
That HTC update is only the 2.73 build packaged in-full.
Click to expand...
Click to collapse
Yea, this is really not accurate at all. The patched kernels help with things like compcache, bfs, etc but the app/ui itself is what has been optimized in this release and is SIGNIFICANTLY faster than the 1.73.xxx version, even using the same HTC kernel.
Also, WRONG FORUM!
what i am looking forward to is the sense ui they said will come native to htc magics. we wont need to port the hero one anymore when that comes. hopefully soon, october was the month rumored.
vro25 said:
Hmm... That's not quite correct. That's like saying MS Word is slow because of the Windows kernel. MS Word is most of the problem...
Yes, the devs here have done some great stuff squeezing more speed out of the kernels with swap partitions and BFS - but that is only half the equation. Sense UI is an APP that run on top of the kernel, so it stands to reason that HTC could have optimized the code in Sense UI (and other apps) to improve performance.
-V
Click to expand...
Click to collapse
Hate to correct you here when trying to prove me wrong but;
ROSIE is the APK that runs over SENSE, not the other way around. The userinterface integrates itself with the OS.
And yes, I am more correct than not. Microsoft has nothing to do with Android. That's an entirely different ballpark, regardless of whether or not they are both operating systems. That comparison is irrelevant...considering "BFS" is not packaged with Microsoft kernels. The End.
Again.
hakeem9 said:
Yea, this is really not accurate at all. The patched kernels help with things like compcache, bfs, etc but the app/ui itself is what has been optimized in this release and is SIGNIFICANTLY faster than the 1.73.xxx version, even using the same HTC kernel.
Click to expand...
Click to collapse
The official build is not optimized. It's an official release, therefore it's a feature-rich build. HTC does not cut-down the applications list, widgets, etc. because the company has standards based on increasing speed and reliability whilst not having to sacrifice any adds-on. The optimization you speak of is only relevant HERE...at XDA, because the Hero ported ROM developers OPTIMIZE them by removing applications, widgets, and various other things packaged BY HTC within their official build to increase responsiveness on OUR devices that do not necessarily have the abilities to operate at a caliber comparable to the HTC Hero. (Run-on sentence, I know, I know.)
Reignzone said:
The official build is not optimized. It's an official release, therefore it's a feature-rich build. HTC does not cut-down the applications list, widgets, etc. because the company has standards based on increasing speed and reliability whilst not having to sacrifice any adds-on. The optimization you speak of is only relevant HERE...at XDA, because the Hero ported ROM developers OPTIMIZE them by removing applications, widgets, and various other things packaged BY HTC within their official build to increase responsiveness on OUR devices that do not necessarily have the abilities to operate at a caliber comparable to the HTC Hero. (Run-on sentence, I know, I know.)
Click to expand...
Click to collapse
You obviously do not like being wrong and obviously have no programming experience either. If they have optimised sense ui ofcourse its not just the kernel. When programming there's plenty of different ways you can get the software to produce a result to end user. if they tidy up the code and compact it down ofcourse you can make it more speedy and efficient.
replies
Reignzone said:
Hate to correct you here when trying to prove me wrong but;
ROSIE is the APK that runs over SENSE, not the other way around. The userinterface integrates itself with the OS.
And yes, I am more correct than not. Microsoft has nothing to do with Android. That's an entirely different ballpark, regardless of whether or not they are both operating systems. That comparison is irrelevant...considering "BFS" is not packaged with Microsoft kernels. The End.
Click to expand...
Click to collapse
Ok, seriously, the biggest problem with the Hero rom performance is the shell called touchflo. If you take a hero rom and use the regular home instead of touchflo the performance is night and day better. This is obviously not because of any change in the kernel (since the only change was the home shell). Based on that, I would say that HTC could improve what they collectively call Sense UI very easily by improving the shell portion of the equation.
Since my question was pointed towards the new HTC release and merging it with the current roms, that to me would seem like a DEVELOPMENT question. I also got many great answers on here that all seem like DEVELOPMENT type answers.
Right Forum. Thanks for the replies so far everyone. Hopefully we can determine if HTC released changes to the Sense UI application that the devs already had or if these are new changes (not Kernel).
If Im not wrong most of the Hero builds around here are already based on 2.73, including myhero.
Also, the increase in speed is more than just the kernel. Although a scheduler like BFS can increase the performance, the 1.7x Hero builds are much slower than the 2.73. I remember one of the Hero devs saying that the 2.73 Rosie.apk is way smaller than the 1.7x one.
Anyway, just take any 1.7 Hero build and compare it to a 2.7 build, hopefully both without BFS. I'm sure you will find that Rosie is generally more responsive.
If Im not wrong most of the Hero builds around here are already based on 2.73, including myhero.
Also, the increase in speed is more than just the kernel. Although a scheduler like BFS can increase the performance, the 1.7x Hero builds are much slower than the 2.73. I remember one of the Hero devs saying that the 2.73 Rosie.apk is way smaller than the 1.7x one.
Anyway, just take any 1.7 Hero build and compare it to a 2.7 build, hopefully both without BFS. I'm sure you will find that Rosie is generally more responsive.
Reignzone said:
Hate to correct you here when trying to prove me wrong but;
ROSIE is the APK that runs over SENSE, not the other way around. The userinterface integrates itself with the OS.
And yes, I am more correct than not. Microsoft has nothing to do with Android. That's an entirely different ballpark, regardless of whether or not they are both operating systems. That comparison is irrelevant...considering "BFS" is not packaged with Microsoft kernels. The End.
Click to expand...
Click to collapse
Wow. Where to start...
Yes, you're right - Microsoft has nothing to do with Android - I was stating an example of an App vs. an OS Kernel. You clearly missed what was a fairly obvious comparison. That make me wonder the type of person we're debating with - as it seems it's everyone against, well, you. But go ahead and stick to your guns.
My point was, kernel enhancements being done here are - for the most part - to optimize the build so it runs on inferior hardware (Dream, Magic 32B). BFS is a different beast altogether and a welcome add-on.
HTC managed to speed up Hero without resorting to BFS, this is because most speed improvements in the UI come from improvements in the Rosie.apk - hence the devs here "slimming" it down to use less memory and run better on non-Hero hardware.
Of course, that's not to say that some of the latest Hero builds aren't already using parts of this official Hero build - they all come from official Hero builds (leaked or otherwise).
The point is you are absolutely wrong in your argument that performance gains only come from kernel version increments. So you can either get over it and learn something - or you can keep arguing with everybody. Frankly I've already spent enough time on you and if you don't get it by now you probably never will so there is no point in continuing any further... But I'm sure others will probably want to have some fun at your expense if you still refuse to see the light.
I have a feeling this isn't the first time you've been corrected and I'm positive it won't be your last. As such, you shouldn't be so quick to jump on others.
Do you know the saying, "a little bit of knowledge is dangerous..."
;-)
You know, for a really good example of how it's not the kernel that determines the speed of everything, just think of how your market apps get updated all the time and how some will say *speed improvements*. The app gets updated to utilize the hardware and performance available and in turn improves its own speed better. Now the kernel does determine a great deal, but the apps are just as important with how they're coded. I would say these leaked kernel's are probably better than the new Rosie update, however there may be optimizations in the rosie ui, or other apps, that I'm sure the devs will rip or have already ripped that will continue to make our lives interesting in the coming days!
This forum is freaking amazing and you all are what make the experience here so enjoyable! Thank you all, especially you devs for making this such a great community!
~*Apollo*~

[Q] Differences - Prime and Revolver

What is the difference between the 2 ROMS?
When I do a search all I see are comments like "I'm using X and it's great!"
If there's a list of ROMS with notes about what makes one so great over the other that would be appreciative.
I would like to know this as well.
robojerk said:
What is the difference between the 2 ROMS?
When I do a search all I see are comments like "I'm using X and it's great!"
If there's a list of ROMS with notes about what makes one so great over the other that would be appreciative.
Click to expand...
Click to collapse
I think an even better question is "What is the difference between STOCK, Revolver and Prime?"
Revolver 2.5's changelog contains "Improved battery life". Compared to what? Stock 3.2 (8.6.5.9)? Prior Stock 3.2? Prime? Revolver 2.1?
Similarly, PRIME 1.8.2 changelog shows "Choice of Touchpad Circles or Mouse Arrow" and "Lots of bugs fixed (Rotate, Compass, Wifi disconnects)", etc. Are these not in the STOCK 8.6.5.9 as well? (yes, they are)
Disclosure: I've run all versions and don't see much difference between any of them, but I'm currently on PRIME 1.8.4
jhanford,
Good point. That's what I do not understand about these "custom" roms. Seems like they offer the same functions/features as the stock rom so I do not know what exactly is the advantage of using them.
Install them and test them yourself, the proof of wether or not they are better can only be judged by your own user experience and not by what others proclaim.
I noticed a significant performance improvement after flashing Revolver compared to stock.
My browser also no longer randomly locks up and quits when going to sites with flash advertisements. YMMV, of course.
There's not really much difference between the three of them since the source code isn't released and not a lot can be changes. The latter two "custom" roms just have a few tweaks included that make it slightly faster and they usually include special kernel modules such as tunneling, governors, and sound improvements/fixes.
I've ran all three and the difference is minimal as of the current firmware since a lot of stuff is now fixed. Before 3.2 Prime and Clemsyn/Revolver were a lot more useful since IMO they were a lot faster than the official version of 3.1.
I am currently on latest version of Prime but very tempted to give Revoler a try. The only thing stopping is that I do not want to waste the countless hours that I put in to create the "Hubs"
I don't think you'll see significant customizations until Ice Cream Sandwich and the next generation of tablets come out. If you look at the overall history of custom ROMs on Android, they've basically fallen into two camps:
1. Taking something from a newer device that's not officially available for given older device and porting it. That can be new versions of the OS itself, or it could be vendor customizations like newer versions of Sense in the HTC world. Right now, all Honeycomb tablets are getting fast updates to the latest version. As for vendor customizations, there aren't heavy customizations to begin with. Vendors are mostly competing on hardware design right now, throwing in a few widgets and apps that may or may not be useful. But usually customization ports stay within a brand (i.e., an older HTC Sense device gets a newer HTC Sense version). That can be for both technical and legal reasons (even within vendors it might be a legal gray area, but it's generally tolerated). But we're still in the first generation of Honeycomb tablets for all vendors, so even the small customizations that vendors are doing are already on the devices in question.
2. Building a customized ROM from the OS source, aka Cyanogen. Since Honeycomb isn't open source, no dice there. ICS is supposed to return to an open source license.
I don't mean to trivialize what the authors of the custom ROMs that do exist have accomplished. I haven't even tried them yet. There even may be significant improvements they have been able to do within the limits of what they have. But overall, it's going to be nothing like what exists on the phone side, where vendors are improving their custom skins from one generation to the next, there are 3+ major generations to work with, and the source is available. Tablets will get there in a generation or two.
Also remembr that the custom roms are deodexed. The hulu flash mod only plays well with the deodexed roms. But really there isnt much differences bc there is no source so that limits the dev capabilities for now
Sent from my Samsung Epic
ajamils said:
I am currently on latest version of Prime but very tempted to give Revoler a try. The only thing stopping is that I do not want to waste the countless hours that I put in to create the "Hubs"
Click to expand...
Click to collapse
What hubs do you speak of?
Rackers said:
What hubs do you speak of?
Click to expand...
Click to collapse
Check the thread here.
Back to topic: I took the plunge and installed latest Revolver. So far, I have not found any difference between Revolver and Prime or maybe I just haven't tested it enough yet.
Have you noticed any difference in battery life between the two?
Rackers said:
Have you noticed any difference in battery life between the two?
Click to expand...
Click to collapse
Not really. Then again, I haven't used it much since I flashed revolver.

ICS: What are we missing?

What goes into a fully functional ROM for an android phone like our beloved TB's? ICS for us has been an evolution of sorts. From what I understand, first we had woefully buggy ICS because we were missing something that only the manufacturer can provide (the RIL, whatever that is?). Sounded to me like the OS would work, more or less, but it was the calling and data that was missing.
Then we got our leak. The leak provided some critical component, but we still have imperfect ROMs. What did we get, and what do we still need?
I know our devs are leaner and meaner coders than the guys at HTC, and that there have been ROMs which are much improved over the initial BAMF one. But, have we gotten ICS to a sweet spot that can't be improved by an official HTC update? Or can we still benefit from it whenever the hell it comes out?
Duely blundered from my thunderdolt.
If I have to guess, you're seeing them hang back until something a little more refined than that leak comes out. The kernel source will be very helpful in getting some kinks ironed out related to the battery life problem of the leak. Also, I believe there are camera and camcorder issues that are kernel related. Kernel source never gets released until after the official update goes public.
Some of the devs may also be preparing Jelly Bean ROMs and not even paying attention to ICS anymore. I'm hoping for this, as we're still going to be one revision behind when HTC releases Ice Cream Sandwich for Thunderbolt. I've seen at least one dev state that ICS to JB is a snap, relatively speaking, so we should get some sweet 4.1 action fairly quickly one the OTA drops.
The ril was one component we were lacking but jester stumbled across something in his build that gave us 1x data and liquid figured out some of the rest. The main thing we are missing now is official ics kernel. The leak we got was a crappy test build and I think that was among their first test builds but that is just my opinion. Once we get kernel source for ics things will be much better. We also need a kernel dev too because imoseyon has moved on to other devices and won't have time for the thunderbolt.
Sent from my Thunderbolt using Tapatalk 2
Yes, I am currently being a coward. Normally I could live without a camera and camcorder, but I just had a kid. Don't want to miss those moments because daddy hacks his phone.
So we got the RIL and need the kernel. After the real release comes out (probably by the time yet another version of Android will be out), we wait a few months, and bam we have the new htc stock ICS kernel. Is the only way to get it is from them intentionally releasing it? There's no way to reverse engineer it eh?
Guess we wont see another "lean kernel" then if Imo's out of the equation. Hopefully he's not the only show in town.
Duely blundered from my thunderdolt
Kernels can be hacked and changed to your liking but I think you can get into trouble if you publish it.
Sent from my Thunderbolt using Tapatalk 2
Liquid's current ICS ROM is pretty damn good, if only with a few hiccups that can be fixed without the new kernel. I can't even imagine how good it could be with a new official ICS kernel.
Kernels can be hacked and changed to your liking but I think you can get into trouble if you publish it.
Click to expand...
Click to collapse
Wouldn't imoseyon have gotten in trouble for all the great kernels he's released if that were true?
The Linux kernel is free for anyone to modify. If you improve it, you're expected to share your work. That's the beauty of open-source software.
If HTC doesn't release their source for the kernel but you hack it is what I mean.
Sent from my Thunderbolt using Tapatalk 2
If HTC doesn't release kernel source, they will be in violation of the GPL. The only source they can legally withhold is their own software, like Sense, or proprietary driver files. They don't own the kernel, so they must release the source after they release an official ICS build, and they can't go after anyone for hacking it and publishing the source. Of course, if they never release ICS, the wouldn't have to release the kernel source, and some brave dev would have to figure it out. I hope that doesn't happen.
I suspect we're splitting hairs on this one.
Technically, HTC isnt allowed to withhold the kernel source at all. But they do. So reverse engineering / decompiling the kernel is completely legal.
I'm super excited for ICS/JB/BBQ/whatever. I'm running liquid's rom on my bolt right now. It isn't perfect, but I love the overall user experience. It's a shame these things take so long to move through the pipe, but I'm very appreciative of the efforts folks are putting in to make this happen. :good:

Marshmallow

Hi All,
I just had a very general question. I am wondering since the release of Marshmallow on some other devices, does anyone have any plans on making a release for the TF700?
I am only asking out of curiosity as I am perfectly happy playing around with all the great roms here. Currently using Zombie-pop.
Thank you
I am in no way a developer, but I can say that from my interactions on this site, the answer is probably a no. There are just too many new options out there with better hardware to customize. Although, all it takes is a small group of talented individuals to love this device enough to port or make a new ROM! Which I am sure all current tf700 users would be totally psyched for.
I think the days of chasing the latest and greatest are over for this tablet.
@hardslog has Omni 6.0 booting on this device but he says it's an ugly hack: http://forum.xda-developers.com/showpost.php?p=63895936&postcount=3355
Focus for the devs is elsewhere by now which is understandable. I think they tickled the best performance possible out of this hardware quite a while ago..
For people who still love this tablet (and I do) and plan to use until it dies a natural death it is time to settle on your favorite rom, set it up to your liking and maintain it.
For me that is CROMi-X. Yep, not very sexy since the last version is JB, but heck - it works very very well.
I am currently working with @LetMeKnow to incorporate his latest tweaks into CROMi-X 5.4, keep your eyes peeled if you're interested, we'll start a new thread once it is done
I have been running this version for a couple of weeks now and I do not miss Lollipop one bit....
berndblb said:
I think the days of chasing the latest and greatest are over for this tablet.
@hardslog has Omni 6.0 booting on this device but he says it's an ugly hack: http://forum.xda-developers.com/showpost.php?p=63895936&postcount=3355
Focus for the devs is elsewhere by now which is understandable. I think they tickled the best performance possible out of this hardware quite a while ago..
For people who still love this tablet (and I do) and plan to use until it dies a natural death it is time to settle on your favorite rom, set it up to your liking and maintain it.
For me that is CROMi-X. Yep, not very sexy since the last version is JB, but heck - it works very very well.
I am currently working with @LetMeKnow to incorporate his latest tweaks into CROMi-X 5.4, keep your eyes peeled if you're interested, we'll start a new thread once it is done
I have been running this version for a couple of weeks now and I do not miss Lollipop one bit....
Click to expand...
Click to collapse
Better than Zombi-Pop? It's pretty buttery. Not perfect, but faster than Crombi-KK. Hmm. I may have to think about flashing it once/if I tire from Zombi-Pop.
Okum4 said:
Better than Zombi-Pop? It's pretty buttery. Not perfect, but faster than Crombi-KK. Hmm. I may have to think about flashing it once/if I tire from Zombi-Pop.
Click to expand...
Click to collapse
I never said "better"
"Just as well - maybe even better" is as far as I am willing to go :cyclops:
Going back I just realized: I really liked the JB Asus UI! And some of the tweaks we lost with KK and LP. Like remapping the power button to forward delete, Keyboard manager which lets you assign different keyboards for landscape, portrait, hardware kb, the choice to go back to the 4.1 UI with the home buttons on the left...
It could be just nostalgia... After all it's that time of the year where you look back and reflect, don't ya? :angel:
Dont belive the nay-sayers...
bigbasshb said:
Hi All,
I just had a very general question. I am wondering since the release of Marshmallow on some other devices, does anyone have any plans on making a release for the TF700?
I am only asking out of curiosity as I am perfectly happy playing around with all the great roms here. Currently using Zombie-pop.
Thank you
Click to expand...
Click to collapse
Im not sure why some of the above people posted that this tablet has reached its limit. I just downloaded the KatKiss 5.1.1. Not Marshmellow but has built in SPLIT SCREEN! That is the magic for me to use this tablet as a front like productivity device for my job.
http://forum.xda-developers.com/transformer-tf700/development/katkiss-5-1-1-tf700-t3166232
As much as I loved the Crombi line and still revere Josh and SDbags for their work, I jumped the shark and switched to this ROM.
I benchmark well on this and my I/O memory hasnt missed a beat...
I thought they were designing newer versions of Android to run on devices with less hardware requirements? To help minimize the "fragmentation" of the os and hopefully bring manufacturers to update the devices faster etc. I'm aware our device is hindered unless Nvidia updates the Tegra3 drivers. Someone will probably find a way to port it over. May not be a top priority of developers but as a hobby, the challenge may be taken up.
Well I guess we have our answer. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166 [ROM][MM 6.0.1] [ KatKiss - KatshMallow #012]
Thank you for all the replies.
Awesome. timduru is an excellent rom builder for the Transformer series.
Flash KatKiss 6.0. You won't be sorry. Great ROM. It's up to version 18

Categories

Resources