Database Info

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*~

Google Maps Navigation for CDMA Hero???

Has anybody gotten this to work on CDMA Hero's???
http://www.gadgetvenue.com/google-maps-navigation-works-usa-11233152/

1.6 only....we are on 1.5. Not going to happen.

As noted, requires 1.6+.
We will be getting 2.0 eventually, probably a few months from now. Keep your fingers crossed.

Why are we waiting?
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.

5tr4t4 said:
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
Click to expand...
Click to collapse
I can't agree with you more. When I transfered to the android platform I was under the assumption that what u said supposed to happen was the case.
However I hear it's very difficult to build a 2.0 for hero.
You see the "drivers" that are in the hero right now will not work on 2.0. If you build the provided open source 2.0 rom, you will get an OS with no tie to the hardware. a map with gps a phone with no radio and a browser with no wifi. which will be useless to any one.

sm_x said:
You see the "drivers" that are in the hero right now will not work on 2.0. If you build the provided open source 2.0 rom, you will get an OS with no tie to the hardware. a map with gps a phone with no radio and a browser with no wifi. which will be useless to any one.
Click to expand...
Click to collapse
Uha, I know. The Linux guys warned us years ago about allowing proprietary drivers in Linux (see the old NVIDIA debate, for instance). So you have a kernel that can't talk to the hardware until manufacturer X says it can.
And so we wait for HTC or Qualcomm or whomever to release their drivers.
Sorry for the rant (and thanks for the solidarity, sm-x), this Google Nav thing just set me off. The hack-a-day progress on XDA is really wonderful but we should have real access to the code so we can make it better, not just reverse engineering...I can do that on my iPhone/iPod.

2.0 is out of the question without the binaries from HTC, but 1.6 should be doable with the 1.5 bits. It'd take someone with a lot of time and dedication, though.

kRutOn said:
2.0 is out of the question without the binaries from HTC, but 1.6 should be doable with the 1.5 bits. It'd take someone with a lot of time and dedication, though.
Click to expand...
Click to collapse
How about tricking the rom into showing itself as 1.6? Not sure what all that would entail tho

5tr4t4 said:
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
Click to expand...
Click to collapse
I also agree with this. I wrote up a little article about it:
http://www.thesearethedroids.com/2009/11/24/a-look-into-custom-ui/

well said gents

Will Froyo be available for polaris someday?

As you know, Google has published Froyo sources. And there is a froyo on SF already. I tried it on my POLA100. It installed and launched well. No wifi, bt, camera, external sound, gps, 3g... Nothing except phone—can receive and send calls. For my humble opinion it runs as fast as current speeded eclairs, even dialer runs almost immediately. Will it see future on polarises, or it's time to think about some native android device? =)

..................deleted

I dont know what you expect from our devs here.
As far as i know the source is only a few days old (23.june).
At this moment eclair is about to get fully functional camera, stable builds, battery life and a good competition between the roms.
So if you neeeed it that much it would be the best to buy a native android device that gets the latest versions first.
---------
So there will be a delay, it depends on how much changes must be done.
I hope that android will become more and more a real alternative for our device.
Since im using android on my polaris i think its like i bought a totally new device and im really happy about it.
Another thx to all devs, modders here ;D

dertester123 said:
I dont know what you expect from our devs here.
As far as i know the source is only a few days old (23.june).
At this moment eclair is about to get fully functional camera, stable builds, battery life and a good competition between the roms.
So if you neeeed it that much it would be the best to buy a native android device that gets the latest versions first.
---------
Click to expand...
Click to collapse
off topic, we're on enthusiastic dev forum

dertester123 said:
I dont know what you expect from our devs here.
As far as i know the source is only a few days old (23.june).
At this moment eclair is about to get fully functional camera, stable builds, battery life and a good competition between the roms.
So if you neeeed it that much it would be the best to buy a native android device that gets the latest versions first.
Click to expand...
Click to collapse
Sorry for possible intonation and meaning misunderstanding. Actually I didn't complain or tried make somebody do something. I appreciate all the devs for their work, It is really great challenge for them to port and adapt builds and eclair gets almost perfect lately. My question was actually just a question about possible future. There could be some hardware restrictions, incompatible drivers, who knows what else, right? So it could be no future for Froyo on polaris at all, that was my question about actually. But dzo has already answered it with uploaded froyo build which installed and launched on my polaris, so I am glad that there is possible oportunity for Froyo and polaris. And of course I am not agitating to get native android phones, and not laughing on enthusiasts here, forgive me my english. =)
iD

ah sorry too, got you wrong^^
sometimes hard if everybody is translating ;D
In the vogue thread they started the froyo development by incubus.
First build is on with bug, but he tries to get a build with most things working this night ^^
Faster than thought

[Q] android 2.3 for G1

Can 2.3 rom be used on my old G1 ??????

maliamalia said:
Can 2.3 rom be used on my old G1 ??????
Click to expand...
Click to collapse
Probably.
But not yet. Trust that Cyanogen and his army of coders will crack the secrets and port the ROM.
But not yet.
On a related note, hooray for the 6.1 Stable release!
That is all.

which is more stable and fast, CM6.1 or MTtest3 ??

maliamalia said:
which is more stable and fast, CM6.1 or MTtest3 ??
Click to expand...
Click to collapse
Think they're about the same. The MTTest3 is good but I prefer CM6.1 for all the extra goodies that come it it. CMParts etc.

Okey, I will try CM6.1.

I don't think android 2.3 will run fast as 2.2:
2.2 is a port of official froyo from mytouch3G, so it's very optimized.
I hope in android 2.3 on G1, I would try to develop something to port 2.3 but I don't know how can I do.. I think by the official sdk but.. mmh
(I'm a programmer but I never developed roms for phones)

Cyanogen said on Twitter that he currently has no plan to port 2.3, as the OS will most likely be GPU-driven.
Honestly, his 6.1.0 release is pretty great.

XBrav said:
Cyanogen said on Twitter that he currently has no plan to port 2.3, as the OS will most likely be GPU-driven.
Honestly, his 6.1.0 release is pretty great.
Click to expand...
Click to collapse
yeah but now our device is really going to be out of date. :/

Well I think it's about time to upgrade to G2 or Nexus S. There's lot of great phones out there. G1 is rocking long enough I think, it stopped to be fast and responsive from Donut update or so...
Sent from my T-Mobile myTouch 3G using Tapatalk

failed to flash CM6.1,
my G1 with the 2708 kernel and 1.33.0013 SPL.
help me!!

maliamalia said:
failed to flash CM6.1,
my G1 with the 2708 kernel and 1.33.0013 SPL.
help me!!
Click to expand...
Click to collapse
congratz. wrong thread and wrong section.
flash cm6.1
flash gapps
flash latest pershoot kernel
next time go to the right section and provide logs etc

I think we must try to port android 2.3 to our g1!
BTW if 2.3 is too slow for our phones, I'll stay on 2.2, no problems!
I'm waiting for a perfect phone:
slide qwerty
800x480px amoled/superAmoled/superLCD
ram>512
rom>1gb
slot SDXC rolleyes: )
cpu>1ghz (and good performance.. the number isn't sufficient )
possible cpu with dual core
excellent gpu
5mpx camera with flash and 720p 60fps recording (also 1080p 30fps would be perfect ) with good optic and NO HTC PINK HALO
google experience or sense
I ask too much?
Do you think I'll keep G1 for the rest of my life?

It can probably be adapted from the AOSP source, but since it has some new gui thingy w/e that is, it will never be the same on our devices, whats the point in downgrading from something that works quite well atm, 2.2.1

Cyanogen's cm6 isn't one of those roms which have the myTouch base of T-mobile. It's pretty much coded from the Nexus Rom and ASOP.
Sent from my Plain Biff Dream using XDA App

Point of updating to 2.3
Well, for me there's one big reason why I'd like to upgrade to 2.3 - Native SIP.
What I don't understand is why Native SIP hasn't been built-in from 1.0! Now there's a flood of poor and mediocre SIP apps on the market, none of which are very good.
I sure hope 2.3 comes to the G1!

hernick said:
Well, for me there's one big reason why I'd like to
I sure hope 2.3 comes to the G1!
Click to expand...
Click to collapse
But for now I can't see any developer works on 2.3..
When froyo and other old android upgrade has been released a lot of people began to develop test roms (in the beginning unusable roms )
Now I can't see nothing

Kishtsang said:
Cyanogen's cm6 isn't one of those roms which have the myTouch base of T-mobile. It's pretty much coded from the Nexus Rom and ASOP.
Sent from my Plain Biff Dream using XDA App
Click to expand...
Click to collapse
yea, but there are divers from the mytouch, would have been foolish to keep using hacks when was real drivers out there.

maliamalia said:
which is more stable and fast, CM6.1 or MTtest3 ??
Click to expand...
Click to collapse
Having just switched from MT3G-test3 to Cyanogen 6.1, I would have to say they're pretty comparable. If you put my feet to the fire, I'd say MT3g-test3 is slightly faster, especially in regards to installing apps from the market. But the goodies available in Cyanogen are so good that...
Aargh, it's hard to decide. I have a nandroid+ext of both, so I can swap back and forth at will. I might spend a few days with each to see which one I enjoy using more, and report back. One thing making it harder... I have a white G1, which historically has had problems with Cyanogen. But the latest seems to be working a lot better than previous releases.

nagash91 said:
But for now I can't see any developer works on 2.3..
When froyo and other old android upgrade has been released a lot of people began to develop test roms (in the beginning unusable roms )
Now I can't see nothing
Click to expand...
Click to collapse
Don't worry, Google has only released Android 2.3 yesterday. Give the developers some time!

GoodDamon said:
Having just switched from MT3G-test3 to Cyanogen 6.1, I would have to say they're pretty comparable. If you put my feet to the fire, I'd say MT3g-test3 is slightly faster, especially in regards to installing apps from the market. But the goodies available in Cyanogen are so good that...
Aargh, it's hard to decide. I have a nandroid+ext of both, so I can swap back and forth at will. I might spend a few days with each to see which one I enjoy using more, and report back. One thing making it harder... I have a white G1, which historically has had problems with Cyanogen. But the latest seems to be working a lot better than previous releases.
Click to expand...
Click to collapse
SuperBler is really fast too. You should Check it.

what is the different between kernel 2.6 and 3.0

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