[KERNEL][3.21.2011]EC10 Kernels

adrynalyne

Inactive Recognized Developer
Dec 13, 2008
10,950
6,471
0
Last edited:

bobloblaw1

Senior Member
May 25, 2010
1,334
498
0
Installing now. Hopefully no explosions =P

EDIT: I've played with it for 5 or 10 minutes now. Seems quite nice. I'll test the battery and all that fun stuff tomorrow.

Thanks adrynalyne.
 
Last edited:

chargerfn909

Senior Member
Dec 1, 2010
165
17
0
Curious about this, however my battery is just settling in on EB01 so ill wait and see what everyone thinks...

Sent from my SCH-I500 using XDA App
 

bobloblaw1

Senior Member
May 25, 2010
1,334
498
0
Can we flash EC10 right over the EB16 Kernel?

Hotspot monitoring dummy kernel in both versions?
I wiped both caches (dalvik+ regular) and then flashed right over EB16. No issues here.

I don't know about the monitoring dummy kernel but I'd be surprised if it wasn't in here.
 

chargerfn909

Senior Member
Dec 1, 2010
165
17
0
Same here, but since i'm still getting only 30hrs max on light usage I figure what the heck.... give it a try.
That's excellent! I never go easy, between texting, this place, and the web in general in lucky to get 17 or so hours lol.. I can charge all day at work or whenever I need if I'm not going to be home though..

Sent from my SCH-I500 using XDA App
 

thefunkbot

Senior Member
Oct 9, 2010
513
153
0
Birmingham
What is different from the [KERNEL][3.15.2011]EB16 Kernels?

Can we flash EC10 right over the EB16 Kernel?

Hotspot monitoring dummy kernel in both versions?
You should be fine flashing over eb16 but adrynalyn would have said they have the dummy file if they did. Plus they are very new (ec10 is code for march 10th 2011), so I doubt they have any mods yet.


Sent from my SCH-I500 using XDA Premium App
 

bobloblaw1

Senior Member
May 25, 2010
1,334
498
0
Not that it matters, but for those interested Quadrant scores (voodoo):


1470, 1593, 1659, 1641

So don't use your precious Quadrants as a reason to not install this ;)
 
Last edited:

djp952

Senior Member
Jan 12, 2010
801
987
0
Baltimore
Flashed over SC 2.9.1 w/ stock EB01 kernel ... (non-voodoo here)

> Wifi still works! Already major improvement over the EB16s for me.
> *228/2 PRL update worked
> Still holding a wakelock on Gps Location Provider on boot, don't know if that has anything to do with the Kernel or not. Running a GPS app clears the lock just as it did before.
> Quadrant (non-voodoo): 946

So far so good. Will see how the battery is tomorrow.

cat /proc/version:
Linux version 2.6.32.9 ([email protected]) (gc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #1 Thu Mar 10 12:52:44 KST 2011

Many thanks as always Adrynalyne!!
 
Last edited:

GizmoDroid

Senior Member
May 14, 2010
664
286
0
A description of features would be nice, thanks!
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Description:
It does mostly everything EB16 does, in mostly the same way.

Unfortunately, Verizon isn't nice enough to include a changelog in their leaked beta internal release software.

There seems to be a misunderstanding about what happens when stock beta kernels are leaked. Maybe people are coming from devices that have custom compiled kernels, where the kernel dev actually helped modify the source code. In this case, yes, a dev will know most everything about said kernel.

This is not the case with leaked stock kernels (or any leaked data). The person who posts the leaked data is rarely an active part of development with the pre-compiled source code. They usually can only see exactly what you see: a compiled binary file. They usually install them on their phone, do some general testing to make sure basic functionality is intact, then they give them to the public.


That's where the public comes in. There are virtually infinite amounts of configurations on everyones' phones. The leaker usually only has one phone. If they are thorough, they MAY test it in a few different environments. Everyone has something unique about their set up or something that they really care about and notice about the behavior of their phone. However, no dev or even a small group of beta testers have the time or resources to test every single application/configuration/feature.

On top of this, the public wants immediate leaks ("You've been running something newer than me?! I WANT IT NOW"). They want the bleeding edge, without any of the bleeding edge problems. This creates a conflict between someone sitting on a leak for too long vs. thoroughly testing a kernel.

So if that's too long of a story, or I haven't made myself clear, I offer this summary: You are the beta testers. You are the changelog writers. You find out the description of features. The leaker merely leaks. Someone who actually cares a bit about public safety/performance (like Adryn) will take an additional step and optimize/mod/lightly test. But after that, the public is just one giant test group, and this is the way it is supposed to be.

If that scares anyone, they are welcome to wait a while and read through people's reports of their experiences with the kernel. If that is still too scary, then I hear that Verizon might be releasing this software on the 12th of Never.

And just in case I hurt anyone's feelings, I'm not singling you two out, and I'm not flaming you. This is a general public post aimed at addressing the overall concern behind this issue that comes up in every new dev thread. You both seem genuine and non-confrontational, but there is a wide range of people who come into these types of threads and whine and complain. So it's nearly guaranteed that someone else will enter and be like "OMG guize my phone iz broked how come you didnt say phone is broked???!!!!!" Then, everyone can point to this post. :)
 
Last edited:

redgryphon

Member
Dec 9, 2010
42
1
0
Description:
It does mostly everything EB16 does, in mostly the same way.

Unfortunately, Verizon isn't nice enough to include a changelog in their leaked beta internal release software.

There seems to be a misunderstanding about what happens when stock beta kernels are leaked. Maybe people are coming from devices that have custom compiled kernels, where the kernel dev actually helped modify the source code. In this case, yes, a dev will know most everything about said kernel.

This is not the case with leaked stock kernels (or any leaked data). The person who posts the leaked data is rarely an active part of development with the pre-compiled source code. They usually can only see exactly what you see: a compiled binary file. They usually install them on their phone, do some general testing to make sure basic functionality is intact, then they give them to the public.


That's where the public comes in. There are virtually infinite amounts of configurations on everyones' phones. The leaker usually only has one phone. If they are thorough, they MAY test it in a few different environments. Everyone has something unique about their set up or something that they really care about and notice about the behavior of their phone. However, no dev or even a small group of beta testers have the time or resources to test every single application/configuration/feature.

On top of this, the public wants immediate leaks ("You've been running something newer than me?! I WANT IT NOW"). They want the bleeding edge, without any of the bleeding edge problems. This creates a conflict between someone sitting on a leak for too long vs. thoroughly testing a kernel.

So if that's too long of a story, or I haven't made myself clear, I offer this summary: You are the beta testers. You are the changelog writers. You find out the description of features. The leaker merely leaks. Someone who actually cares a bit about public safety/performance (like Adryn) will take an additional step and optimize/mod/lightly test. But after that, the public is just one giant test group, and this is the way it is supposed to be.

If that scares anyone, they are welcome to wait a while and read through people's reports of their experiences with the kernel. If that is still too scary, then I hear that Verizon might be releasing this software on the 12th of Never.
Very nicely said. But i think most of the time when people ask they are not trying to be rude or annoying. They are just not aware or hoping the person who leaked it might have the changelog as well.

Thanks adrynalyne...
 
Last edited: