• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [KERNEL][4.0.4] LeanKernel 3.10.0 (7/2)

Where can I get this notrim? And what is smartreflex?

Ok. Here is MY explanation based on MY understanding (as remedial as it may be).

First, the notrim versions are on his site, just follow the link. The earlier notrim versions had issues but v5 is a winner for most, including me.

Smartreflex is a code written in that will automatically determine your voltage settings based on your phone. If you type in "checkv" after su of course, it will give you current voltages along with what your phone will run supposedly. I have found that it is quite accurate. Now, smartreflex does NOT exist in the notrim versions because the throttling happens at a certain temperature. The notrim versions raise that temperature limit to a level that Imo has deemed higher (for benchmark people) but still safe. Type in "checkt" and you will see temperatures and how many times you have been throttled. Generally, the throttling will only happen if you have been running benchmarks. In order to implement this, smartreflex had to be eliminated. THIS IS ONLY FOR THE NOTRIM VERSIONS. Smartreflex only exists in the latest experimental versions.
 
Ok. Here is MY explanation based on MY understanding (as remedial as it may be).

First, the notrim versions are on his site, just follow the link. The earlier notrim versions had issues but v5 is a winner for most, including me.

Smartreflex is a code written in that will automatically determine your voltage settings based on your phone. If you type in "checkv" after su of course, it will give you current voltages along with what your phone will run supposedly. I have found that it is quite accurate. Now, smartreflex does NOT exist in the notrim versions because the throttling happens at a certain temperature. The notrim versions raise that temperature limit to a level that Imo has deemed higher (for benchmark people) but still safe. Type in "checkt" and you will see temperatures and how many times you have been throttled. Generally, the throttling will only happen if you have been running benchmarks. In order to implement this, smartreflex had to be eliminated. THIS IS ONLY FOR THE NOTRIM VERSIONS. Smartreflex only exists in the latest experimental versions.

Fantastic explanation! Downloading right now...as jbdan nods and winks!
 
Really thinking about trying 2.3 after seeing the potential battery boosts. Interested to hear your results!
 
Just flashed 2.3. Interesting to see what OMAP mods he implemented to improve battery life. Seeing as the display and cell radios are the largest power draws though, I don't think a LV kernel will play that big of a role in battery usage, at least with heavy usage. Still, I keep flashing the newest ones whenever I see them hoping it will help out somehow. I figure it certainly can't hurt battery life :p.
 
Does anyone know if this kernel has support for init.d? And if yes, how would I get in "activated," if you will? I don't see init.d at the root of my device like I thought in had with other kernels. Any help would be greatly appreciated.

jmar
 
Really thinking about trying 2.3 after seeing the potential battery boosts. Interested to hear your results!

So far, not looking good at all. 42 minutes on battery, only 12 seconds of on-screen time and I'm at 94% already. :confused:

I think I'm going back to 2.0.1. 2.2.0 was ok, but 2.0.1 was better for me and so far 2.3.0 looks horrid. I'll give it another hour to see if it's still draining so quickly.
 
I have done lots of beta testing over the years, and I may be missing something here but testing a ROM or Kernel for an hour doesn't seem like a credible method.

I would think at least 72 hours with a few reboots would be more like it.
 
I have done lots of beta testing over the years, and I may be missing something here but testing a ROM or Kernel for an hour doesn't seem like a credible method.

The first discharge cycle on 1.10.0, 2.0.1 and 2.2.0 were nowhere near this bad. There is nothing of note in the battery usage nor in better battery stats. Obviously 1 hour isn't a long time, but 42 minutes of basically idleness on wifi with 12 seconds of screen on time should not eat 6% of a battery. :cool:

Time will tell, I'm not saying I am going to abandon it after 2 hours, just that I will check back in after another hour to see if the discharge is happening at the same rate.

I flashed this kernel before I left work and in the battery graph it was obvious where I flashed it. The slope of the battery discharge curve steepened significantly. I figured I would charge it up fully to give it a full discharge cycle, but that same fast discharge trend appears to have continued. But, like I said I'll check it again in an hour.
 
I hear you. I seem to notice improvement over time.

This is what a lot of peoples say!

I am never happy with a kernel right away, most of the time.

Ask jbdan;)

I'm not a benchmark junky but I like this!

E7sAO.jpg


Zu1zZ.jpg


Just having fun with my Nexus Prime!

Quick story: So I was at work today changing a trash at the condiment bar (in my line of work even a manager is on the sales floor 85% of the time). This lady is talking to two gentlemen at a table and I notice she has a bag with Andy embroidered on the flap. We get to talking about Android and she says, "Next time I come in I will bring you some "Android Swagger." This loosely translates to: she is going to bring me some Android accessory. Her husband works for Google as a dev. I work in Cupertino, CA, land of the iXxxxx/iXxx. The guys she had been speaking to had iXxxxx'x and seem perturbed at our fluid geek conversation. She had a Nexus S (T-Mobile, Android's birthplace). I had a Nexus Prime; her words...I totally agreed.

:D
 
I hear you. I seem to notice improvement over time.

I think perhaps I wasn't fully charged, despite the 100% indicator. After the 6% quick "drain", it definitely stabilized as you were anticipating. I still haven't seen that behavior before with other kernels on the first boot with them. So I think it was somehow related to the charge.

Anyway, went to bed last night at 11:45pm with 90% battery and at 8:45am it was at 86%.

4% over 9 hours is quite good. Not as good as the 2-3% over 7.5 hours I saw on 2.0.1, but still very good. I'll see how it goes today while at work.
 
On 2.0.1 my battery stayed at 30% for around 9 hours. I thought it was just the indicator not refreshed but it only dropped to 29 after playing with the phone for a few minutes and stayed stable until I plugged it in later that day!

I think I have a screen shot of it....
 
Just been reading through a little, is 2.0.1 the favorite so far? I'm currently on Franco, looking to try lean. What has been the best(from overall preference) for battery life? I know it can vary by phone, but I'm just curious which version most people have preferred.
 
Just been reading through a little, is 2.0.1 the favorite so far? I'm currently on Franco, looking to try lean. What has been the best(from overall preference) for battery life? I know it can vary by phone, but I'm just curious which version most people have preferred.

1.6.6, 1.10, and 2.0.1 have been the consensus favorites so far.
 
I just reverted back to lean kernel 2.0.1 to review. Anything above that has not been as good in my findings.
 
Yeah, 2.3 was pretty bad for battery life today. I took it off my car charger at 100% when I got to work. Walked to my office, sat down, looked at it again.. 94%?! By after lunch it was at around 65% and I hadn't really touched it. Pretty disheartening :(.
 
Yeah, 2.3 was pretty bad for battery life today. I took it off my car charger at 100% when I got to work. Walked to my office, sat down, looked at it again.. 94%?! By after lunch it was at around 65% and I hadn't really touched it. Pretty disheartening :(.

Interesting. I had the same 100 -> 94 drop after less than an hour of pretty much nothing (like 12 seconds display on). It's been decent since, but I think I'm going to go back to 2.0.1 for tonight's charge.
 
Keep in mind, guys, that these types of batteries will often be charged to roughly 95%, then very slowly charged the rest of the way to 100%. Depending on the software they will sometimes report 100% even if they haven't gotten there yet. It's quite possible that 6% jump was actually just a 1% jump as the reporting became accurate.
 
Keep in mind, guys, that these types of batteries will often be charged to roughly 95%, then very slowly charged the rest of the way to 100%. Depending on the software they will sometimes report 100% even if they haven't gotten there yet. It's quite possible that 6% jump was actually just a 1% jump as the reporting became accurate.

Yep, well aware of that behavior as it was typical on my dinc. In my case with the quick 100 -> 94 drain, I had plugged it in at about 96% because I had to unplug it and re-plug it in. So I dunno, perhaps it screwed with the trickle charging. On second thought I think I'll give 2.3.0 another go and charge over night as I normally do (even though I'm only at 48% heh). 2.3.0 deserves at least one more day and perhaps you're right and it was just a "100%" charge, not a 100% charge.

You hear my 2.3.0?! :p You have one...more...day...before I get the kernel flash itch! :D
 
Interesting. I had the same 100 -> 94 drop after less than an hour of pretty much nothing (like 12 seconds display on). It's been decent since, but I think I'm going to go back to 2.0.1 for tonight's charge.

I'm on 2.2 no trim 5 getting great battery life 63 percent battery; 2 hours screen time and 11 hours up time!
 
2.3.0 stable has been stellar. I may have finally found a replacement for franco 13.1 as it is finally feeling a bit long in the tooth. What a run though I'll keep it on hand indefinitely!
 
Back
Top Bottom