• 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)

2.4.0 is out now.

leanKernel v2.4.0


- Linux 3.0.22
- Linux 3.0.23
- lkflash: added the notrim option
- OPP table and smartreflex tweaks
- fast USB charging by chat0989, and ffc toggle script by me (open terminal, type "ffc" without quotes and then enter).
- omap-serial fixes
- nfc wakelock reduced
- reverted c4 state patch due to instability
- fixed some opp/sr initialization bugs, a couple introduced with 2.0.0
 
Ty! Looks nice please post experiences when tested thoroughly.

That means you too jmar! :D

Oh you know it!

Using 2.4 exp1 notrim on 4.0.4 stock rooted...charging up now! Oh, all usage will be with the extended battery :) and display at ~20 percent. Report Tuesday @ 9pm PST.

Been reading up on kernel flashing and may revisit my seemingly dead, most likely forgotten, and self admittedly abandoned kernel flashing guide. :)
 
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

Bump for help...TIA :)
 
Oh you know it!

Using 2.4 exp1 notrim on 4.0.4 stock rooted...charging up now! Oh, all usage will be with the extended battery :) and display at ~20 percent. Report Tuesday @ 9pm PST.

Been reading up on kernel flashing and may revisit my seemingly dead, most likely forgotten, and self admittedly abandoned kernel flashing guide. :)

20% brightness?!? I use 40% to reduce battery suckage, but wow, either a) your display is much better than mine or b) your tolerance for samoled/pentile effects are much higher than mine :)

I am currently running franco 18.6, purely to fiddle (again) with color control. While I have no real fix at the moment for the video playback stuff, I figured I would spend more time with the gamma and offsets and see if I couldn't make stuff watchable (for me). No real (consistent) luck for me there, but...

Long story short - flashed franco 18.6 about 3 hours ago and holy crap. I thought my battery % was stuck. So far so good with it, but I'll post details later (after a full charge and day at work) in the franco kernel thread.
 
Has anyone tried this yet with lean??
Color control update in init.d:
Custom kernel brings improved screen performance to the Samsung Galaxy Nexus

Yes, I fiddled with it, but I had to flash one of the franco kernels (18.6) to do this. Other kernels support color control, but afaik LK does not.

While you can fiddle with the color tinting on your particular screen (because, yes, it does vary screen-to-screen), it's not an end all be all "fix" for the gamma issues on the device. I believe the gradient issues in videos and color banding, etc are fundamental to the display or the RGB->samoled processing that is happening to display what you see on the screen. I'm not entirely sure what Samsung is doing is even fixable/flashable - it may be a driver/internal-software issue that only Samsung can provide a tweak for (if they choose to do so).

The color control features do provide a very usable feature - tuning your screen to your taste/eye. Not everyone sees things the same way, so this allows you to tune the gamma on R(ed)/G(reen)/B(lue) and tune it to your liking.

Honestly, the default gamma/etc on the stock kernel (and LeanKernel) were more to my taste (or perhaps what I was use to) than the defaults in the francokernel with its color control. That said, with franco you can tune this back to the defaults or to your own preference, whereas (currently), with LeanKernel you cannot. If you like this feature, I urge you to vote in the rootzwiki thread I posted earlier. :)
 
2.4.0 is out now.

I've been on 2.4.0 notrim for about 24 hours and I really can't see a difference from 2.3.0 notrim4 (which I find to be the best of the notrims). Ultimately, I gage the kernel based on idle and/or wifi usage because at work I get horrible reception and therefore the battery life comes and goes.

I have yet to find a notrim version (I run at max clock speed) that drains more than 5% over night on wifi. I'll take that all day long.
 
I am running the same and found the same. Plus I find it much smoother for high CPU intensive activities with no lag or lockups, and have not had a single reboot since finding the notrims. I know every phone is different, but my phone refuses the 1420 speeds that are available on the exp....so being able to go to 1650....works great for me. Even apps like maps and nav make the phone hot, but no hotter than running at 1350....
I am liking this 2.4 notrim a lot...will test it through today though.
 
I am hoping someone will post a link for us to a step by step on the terminal emulator so we can enable the fast charging.

Never heard of the terminal emulator .


EDIT, OK,

I got terminal emulator now. Rootwikli is very slow to load. Anyone have the commands?
 
I am hoping someone will post a link for us to a step by step on the terminal emulator so we can enable the fast charging.

Never heard of the terminal emulator .


EDIT, OK,

I got terminal emulator now. Rootwikli is very slow to load. Anyone have the commands?

Well, I can't remember the toggle. Due to the fact that rootz is down atm, I can give you an alternate. Just go to root explorer (or similar), mount r/w, go to /sys/kernel/fast_charge and change the number from 0 to 1. Zero being off, 1 being on.

FYI: Fast charge is only for USB. If fast charge is on, you will not be able to mount to your computer, hence the need for a toggle. I do know that chad is working on a widget for a toggle.
 
Well, I can't remember the toggle. Due to the fact that rootz is down atm, I can give you an alternate. Just go to root explorer (or similar), mount r/w, go to /sys/kernel/fast_charge and change the number from 0 to 1. Zero being off, 1 being on.

FYI: Fast charge is only for USB. If fast charge is on, you will not be able to mount to your computer, hence the need for a toggle. I do know that chad is working on a widget for a toggle.


what does "fast charge" do exactly?
 
Well, I can't remember the toggle. Due to the fact that rootz is down atm, I can give you an alternate. Just go to root explorer (or similar), mount r/w, go to /sys/kernel/fast_charge and change the number from 0 to 1. Zero being off, 1 being on.

FYI: Fast charge is only for USB. If fast charge is on, you will not be able to mount to your computer, hence the need for a toggle. I do know that chad is working on a widget for a toggle.

Thanks, it worked. Like you said no mount, but the learning and experience is appreciated.
I did it before I read the no-mount part and when I seen the new drivers being loaded I knew something was up.:)
 
Found it out there on a german site. Type ffc and enter but it still blocks mount. I seen the one on Rootz but did not note it down. Its more than ffc.
 
what does "fast charge" do exactly?

USB connectors generally only charge at a rate of 500mAh so that you can pass data at the same time. Fast charge forces the connection to charge at a higher rate but at the cost of losing your data connection. 500mAh is roughly half of what your wall charger would use. I personally only connect to my computer in order to pass data so I keep the toggle off.
 
Terminal Emulator Fast Charging For any Future Noobs,
  • Get Android Terminal Emulator from the Market.
  • Type in ffc and hit enter and it will tell you Fast Charging On
  • Type it in and hit enter again and it will tell you its off.
No file transferring and the like while its on. It lifts the 5.0A input current limiter.
 
Any ideas on if that could possibly fry any circuitry inside? Or would it just end up being the same overall current as if you were charging and copying a file to the SD card at the same time.
 
Any ideas on if that could possibly fry any circuitry inside? Or would it just end up being the same overall current as if you were charging and copying a file to the SD card at the same time.


I use a 2A power source in the vehicle that shows charging on AC and its still alive. Since it ships with a 1A charger it may have a protection circuit that only allows 1A to enter. I dunno.
 
Any ideas on if that could possibly fry any circuitry inside? Or would it just end up being the same overall current as if you were charging and copying a file to the SD card at the same time.

It shouldn't damage your phone.

I'm not sure what it "could" do to your computer though. Your MB should have limiters built into its circuitry to prevent over current drawing, but I'd still be leery.
 
2.3.0 blew any franco kernel I've tried out of the water

consistently getting 2+ hours screen time, a day or more battery, no keep awake, and basically zero drain when the screen is off
 
2.4.0 is showing me a noticeable increase in responsiveness. Not doing any battery tests right now. 4G just hit my area and I'm all over it.
 
Terminal Emulator Fast Charging For any Future Noobs,
  • Get Android Terminal Emulator from the Market.
  • Type in ffc and hit enter and it will tell you Fast Charging On
  • Type it in and hit enter again and it will tell you its off.
No file transferring and the like while its on. It lifts the 5.0A input current limiter.


So am I to understand that FFC is on by default?
 
Hmm, I wonder if the fast charge feature will fix some chargers that, despite being rated 1-2 Amps, cause the phone to charge at USB/550mAh speeds. Then forcing you to buy special charging cables or soldering the data pins together on the charger to force it to AC speeds.

2.4.0 has yeilded me no more performance or battery life than previous kernels that I can notice. I might start trying out those Notrim experimentals or whatever they are.
 
(Removed the Link because it did not answer the question...)

Good luck.

Edit: little more research and yes..lean has init.d support: go to the root in es file explorer or whatever file system app, and its under etc/init.d

I have it in mine.

Thanks, found it. Now I know where to place scripts. I thought, for some odd reason, that it was in sdcard/. :p
 
Back
Top Bottom