yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halodos:
Running the d2spr version (would you want to start a thread there too?) on slim beta 3 and it's amazing.

Applied the settings swiftks recommended with the gov tweaks and undervolting, and it's still running smoothly and efficiently, sometimes getting an estimated 2 days run time!

The prodigal son returns! Thanks imoseyon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Please don't do that ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Ah yeah every time I merge in CM kernel code, some of my changes get reverted - sigh. exp3 should fix that - check it out. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm excited to see you back and working on this ROM. I've never given it much of a chance cause I heard it didn't work well with Quantum what are your guys' experiences with it though? Currently I'm flashing BMS 8/17 on top of Quantum 1.19 because I've heard good things, but I want to give this kernel a shot if people like it as much as it seems!

Do you guys tweak it to your liking or do you leave it as is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Anyone else not going into deep sleep? Just noticed it. Running exp3 on latest Slim beta 3.

Only thing of significance that BBS is showing is PowerManagerService.WakeLocks

**Edit**

Weird... took a phone call, and now my phone is going into deep sleep.

Power manager service wake lock still increasing in time though too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hey OP, any updates for the 10.1 since the RC1 is out for 10.1.3? There have been changes since v7.2 which may brake couple of things
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] agentfusion:
So, is anyone else having issues with this (and pretty much every other kernel) eating your IMEI? Basically, on cm10.2 if I flash any kernel, my apn settings are blank and so is my IMEI.

I'm asking here because this is my favorite kernel by far and I'd really like to use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Reflash the ROM, GAPPS and Kernel which will resolve this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
I checked the CM repo and there aren't any kernel changes for 10.1.3 so you guys should be good with v7.2. :cyclops:

Speaking of... I really want to go back to 10.1. 10.2 just isn't stable enough - I'm kinda stuck with 10.2 for a while though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you please share the exp version of 7.2. It seems after the server change old exp kernel for is missing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Woody:
I am glad to hear this and I agree. There are still some things that need to be ironed out ROM-wise before we can move forward Kernel-wise.

If you can wait until I get home later tonight, I can uplaod it for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
The new leankernel stable is up! (;
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Can you guys test v8.0.5?

http://androtransfer.com/get.php?p=imoseyon/d2att/test/lk_s3att_aosp_mr2-v8.0.5.zip

I think i fixed CM-10.2's memory leak but the changes were so drastic I'm afraid there may be other things broken. It's no longer based on cm-10.2 kernel source.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxf250:
8.0.5 broke wifi. Reflashed 8.0.3 & wifi is back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I disabled data and enables Wifi. Seems OK for me. I'm writing this on Wifi.

Phone doesn't seem as responsive though.

Update: rebooted again.. Seems back to normal speeds.. Still on Wifi only. Will continue to use this and report back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I was using cm 10.2 default kernel for the last couples of days... And it was fine.

I flashed your test version... And it's also fine for everything... 3G and wifi are fine too.

What was the problem exactly for this memory leak that you fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Flash stock kernel (or stock ROM which includes stock kernel). Try playing Candy Crush (or 1000000) for about 30min straight. Your phone runs out of memory and pretty much dies. I'm sure there a are other apps that you can try but those two do it for me every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Is this related to games only or maybe apps that are using the gpu?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
only the apps that use the gpu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] j3hans:
Is this compatible with note n700
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you post the v7.2 exp please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Let me know if you're unable to find it. It will take me some time but I can switch branch and compile/build one for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v8.1 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog (Android 4.3 only)

I think I managed to fix the gpu memory leak without having to completely deviate from cm's kernel source.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks, sorry where to find the exp brain of 8.1? Unable to find in the usual link

Edit: found it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Woody:
Check your PM.

I'll post a public link a little later on this evening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
thanks for you excellent work.

by the way, I was running 8.0.5... and since yesterday night, I've got two complete freezes. I pressed the home button to wake it, but for those two freezes, it did not work. It rebooted by itself one time when trying to wake it with the power button... and the other time, I had to hold the power button and hold it again to force a reboot.

I just installed 8.1... and I will post a last_kmsg file if I'm still getting this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
I heard sometimes increasing your voltages might solve the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
maybe... but I don't think it has anything to do with the problem I have. I'm running with the default voltage... nothing modified. Default voltage are already high enough.

In the past, I've been running with lower voltage... 900mv for 384MHz without any problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
I don't think you'll see that problem on 8.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monfro:
8.1 is running really well on Slim B4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
I flashed v8.1

It booted once before rebooting. but now it won't go past the Samsung Galaxy S III logo (the one with Cid)

Flashing other roms\kernels does nothing

Restoring old backups does nothing

I checked /system with the file explorer in twrp recovery...

There are no files there, no matter what I do

Help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Did you mount it before checking with the file manager?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] exodus454:
I had this problem recently too. Only solution was to flash my phone back to stock and then reflash what you want over that. I have no idea what the problem was, but i couldn't restore backups or flash anything new either even after formatting over and over. Now everything is working just as it should.

I also wanted to stop in and say this kernel is AMAZING. I've been using kt747 since I got my S3 and was really happy with it. I flashed leankernel the other day out of curiosity and it's absolutely incredible. Out of the box the performance and smoothness exceeds anything I've seen from other kernels in a long time! Not to mention my battery life thus far has been better than I ever believed the stock battery was capable of. I always swore by using ktoonservative with mild overclocking and this is absolutely smooth as butter on Pac 4.3 at stock clocking. Browser scrolling is smoother than I've ever seen.

Well done sir! :good::good:

Not to mention video and focal actually work - and well at that! For an experimental build, 8.1 is working flawlessly. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nazo:
I'm getting tearing on the latest 10.1 (release candidate 1.) Has anyone ever found any solution to it? I really like the idea of this kernel, but the tearing is horrifyingly annoying.

It almost feels like what happens on a PC when framerates exceed the screen refresh rates and vsync is disabled.

EDIT: If I select the option "disable HW overlays" which says "always use GPU for screen compositing" (which to me sounds like the opposite, but whatever) it stops tearing all over the place, but I have no clue what the long term effects of doing this are... (Namely, would it affect compatibility or battery usage?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Compatibility, no. Battery usage, sort of. It's a complicated discussion not warranting the time.

Know that I have been disabling HW overlay for a damn while already because of that CM bug (which I don't think has been looked over). Believe me when I say you won't encounter issues, the downside being that you need to enable this option every time you reboot.

I have myself set an action using Tasker and Secure Settings that runs at boot to disable HW overlay so I don't have to do it manually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nazo:
Well, PowerAMP freaked out and wouldn't load any music, plus my battery life was HORRIBLE, so I'm going to revert back to BMS for now. I was hoping for a simpler kernel with undervolting, but I'm guessing because this one lacks the powersave governer or something maybe I've been getting FAR worse battery life. FAR FAR worse... (Normally at the end of a day of work it's around 79% or so, but today it was around 53% when I checked in my first break with the screen off the entire time and only minimal apps running, so I quickly reverted to BMS and it only went down another 10% from there throughout the remainder of the considerable remaining time, so I'm going to consider this one to not mix well, lol.) That's with undervolting and profiles that lower the clock rates from stock (I even have it set to lower almost to the minimum only when the screen is off.)

Actually, the PowerAMP issue has me a bit stymied. It was acting like it couldn't access any of the files on the MicroSDHC card... Yet if I access them via a file manager, I could read text files and etc. It was also loading album art. I couldn't play audio through the file manager's built in player either though, so I'm guessing it's some kind of sound system thing? I didn't see any mention of it using Voodoo or anything like that since it's supposed to be more minimal, so I'm not sure what it could be, but it did work when I played games and such, just not in any music player.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -oH-mr_rogers:
Cannot send SMS

hey i just flashed Leankernel v8.1 on top of Quantum v1.20 and now i cannot send SMS at all. i can still receive them however.

i went into recovery mode (TWRP 2.5.0.0), flashed Leankernel, wiped cache/dalvik, reboot..

did i do anything wrong, usually when flashing a kernel its just flash then wipe cache/dalvik?

thoughts, suggestions?

i went back and factory reset and reflashed Quantum and GApps and it works again but i have heard a lot of good things about this kernel and i really wanted to try it out :D

thanks for any and all help

-RoGeRs

Edit: somehow Voice+ was enabled on my phone... Problem solved haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
no GTFO!!"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Screen flickers on CM 10.1.3 RC2 with v7.2 build. Any plans to update the kernel for the latest fixes in the CM 10.1 Branch? Don't think after this any major changes would be required in CM 10.1 branch as 10.1.3 stable will be the last build.

I have gone back to 10.1 as per your suggestion couple of pages back due to memory issues in 10.2 nighties. Thought to stay on 10.1 until the memory issue is fixed by CM in 10.2. Happy with the 10.1.3 RC2 performance, running for the past 2 days now, but it would be great with Lean kernel only
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rokius:
No flickering issues on CM 10.1.3 RC2 with v7.2 here. Is it while on a particular app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
All the apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rokius:
Strange.. I ran Odin to stock, and started from scratch with no TiBu either. No issues thus far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Hmm try v7.1: http://goo.im/devs/imoseyon/d2att/lk_s3att_aosp_43-v7.1.zip

Also, I fixed memory leak in cm-10.2 but you'd need to flash my v8.1 kernel for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abc123pro:
I'm very sorry if this was asked before but is USB otg not supported? I'm actually on the latest 4.2 leankernel. Or is that just due to my rom? Liquidsmooth d2tmo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Been going back some and don't really see many talk about settings. Any suggested schedulers or voltages?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] exodus454:
Honestly, unlike a lot of other kernels I've been leaving lean pretty much at the default settings. Row/interactiveX, default voltages. I bumped the min speed to 189, occasionally I'll run 1600 or 1700mhz but there's not a huge difference from the default. I've also been playing with the gpu over clock.

I'm currently on 8.1 with aokp 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r_scotter:
I use to love tweaking KT747, but now I'm very happy with the simplicity and stability of Lean. I run it with Slim Bean 4.3 and only change a few things.

I overclock to 1728 w/ row and interactiveX. Under interactiveX I change the max screen off freq to 594. I don't undervolt anymore because I didn't notice any difference from stock. Multicore power saving is set to 1 and gpumax freq is 480.

These settings give me very good performance and, on average, 16 to 20 hours and 4 to 4.5 hours screen on time with 2100 mAh batteries.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halodos:
I see deadline recommended over row for in flash memory devices - is this not the case for this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
For some reason trickster won't keep settings after I check start at boot. Running PAC 9-11 nightly

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Make sure to set frequency lock and disable any boot scripts that could change your frequency.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you please share 7.1 exp, if possible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
7.1 is working with cm 10.1.3 rc2, looking for 7.1 exp if anyone can share
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Could be wrong, but doesn't appear to be one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
What could be wrong? didnt get you

I asked if someone can share the 7.1 exp version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
I mean I don't seem to be able to find a 7.1 experimental version anywhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
I'm still using 4.2.2. Can I use 8.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Nope, you'll have to use 7.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
Problems with root...

I am using PA 3.99 RC1.

I started using Leankernel today. For some reason, after a few normal user initiated reboots, now root apps are not able to get root privileges. The ROM by default denies them, and the Apps (like titanium) think that ROM is not rooted. I have checked the superuser settings in ROM, and everything is as it should be, default action is PROMPT and timeout is 30 seconds.

I have now flashed the ROM over again, and Root is not behaving weird anymore.

Not sure if this was a Rom issue or a Kernel issue. Want to be back on this kernel...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Root does not have anything to do with the kernel... So it's probably a rom issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
Upon further investigation, I have found that the problem happens after running lkconfig. Immediately after that, superuser denies all requests, and titanium thinks that the phone is not rooted. Rebooting fixes it, but the moment I run lkconfig again, I lose root functionality, as Superuser denies all requests.

So it seems to be a kernel/lkconfig bug.

Edit- reporting now that the problem doesn't happen with BMS kernel and its setcolor command. [MENTION=3357040]Imoseyon[/MENTION] please look into it, as I find LK to be a better kernel for d2att-PA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akaleshnikov:
What's the latest version of this kernel I can run with AOKP MR1 milestone 2 4.2.2 release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
7.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
7.2, you will have screen flickering issues with 7.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v8.2 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Like a kid in a candy store
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halodos:
I changed off lean kernel for a hot second yesterday, and hit lag spikes everywhere on my launcher. The update was all I needed to get lk again

Runs great on Sprint gs3. My modifications:

Read ahead to 2048

Deadline

Mp core saving to 1

Undervolted across the board -50
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Thanks for the update.... Guessing you may have fogot to merge your CM fix for the deep sleep/Screen On bug in the experimental build? :D

Yeah, it's happening in 8.2 exp.

As always, good work though.

Hope you'll be getting the new Nexus so I can continue your kernel on it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
darn it again lol. Try this build? http://www.box.com/shared/uj9mj6z102v2rw7ss635
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
I lost 7% battery in 2 hours (idle) with 8.2 stable, whereas on 8.1 it was under 2% per hour. Is that because of what you stated above? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Which ROM are you on? If you want to flash v8.2 I recommend the latest nightly ROM builds. Otherwise I'd stay on v8.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
pa_d2att-BETA-3.99-RC2-20130922.zip

edit: looks like there might be some issue in the ROM, as WiFi always stays-On, no matter what setting I choose for WiFi sleep policy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hi op, can we have last kernel release for 4.2.2 considering 10.1.3 is out.. There have been couple of kernel changes since 7.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlkaliV2:
I needed to take a second and say I recently discovered your kernel and started using the d2spr 8.2 with the latest 4.3 (build 1) of Slimbean. It is an absolutely incredible rom as far as battery life is concerned and this kernel made it that much better as I compared stock to your build. I've noticed a few hiccups, but for the most part 8.2 has been solid and does not cause any undue battery drain. My overall experience has been very positive. Great work and thank you for this kernel. I like keeping it simple :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v8.3 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog

I don't know anyone who wants exfat support on AOSP but I added support for it anyway. The module is not loaded by default - you will need to use the "loadexfat" command.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
just tested it out on d2att, everything else is good, but I still temporarily lose root (until next reboot) after running lkconfig. What happens is that after running lkconfig, Superuser in PA-3.99-RC2, be default denies all su permissions to all root apps. This behaviour doesn't happen with any other root app, just lkconfig, and no Superuser settings help. Everything is normal on next reboot, but my lkconfig color setting doesn't stick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Try SuperSu. There are all kinds of problems with the built in Superuser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
tried that as well, same results as with Superuser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadezero:
Haven't used LK in a while.

Finally made the switch from Rootbox to Carbon Nightly.

Quick Q - does this kernel modify any of the bootscreens? KT747 has that ugly 1337g4m3r thing going on. BMS has 'booped'. Etc.

I'm looking for something clean.

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
No, stock boot screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Any changes to above settings for 10.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Why would you turn mpdecision off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Nope... Still have amazing battery life when combined with Slim ROM, Greenify & Autostarts.

Because.... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
With the autostarts that hasn't been updated in two years?

I use the xposed version. Works beautifully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Are you still running the latest experimental or stable build?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Yes & No... One on Play store is v1.7.5. A newer version v1.7.7 was released/built early this year (Google). Regardless, both with no problems, so there really is no need to update... Just helps limit all the background processes.

Running latest exp build always... Currently v8.3 I believe; no issues. Battery easily last all day from 7:00 am to 1:00 am.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you share your autostart settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
That would take forever, and pretty much be dependant on what apps you have installed. You more or less want to disable anything that is not essential for starting your system up, and leave apps enabled you want to on in the background; i.e. you can disable maps, YouTube, Facebook, etc. From starting after boot, as you don't really need their system processes running in the background, only downside being they may take a extra second to open. But leave things like gmail, messages, contacts sysnc, etc. Alone so you still get notifications when you get new messages. Then you can go through all the other menus and disable any apps you choose you don't want opening in the background for that particular operation (like the power plugged in batch... Why the hell do I want chrome running any background processes when I plug in my phone???).

This app works great in conjunction with greenify.... As in Autostarts will prevent the app from pre-loading it's processes, and once you choose to open and then close said app, Greenify will (upon your configuration) stop the background processes that the app keeps open, even after closing it.

Hope that helps a bit.

p.s. you also don't want widgets that update on your home screen(s). This is a sure fire battery killer. All those weather and Facebook/twitter widgets you have refreshing every time you turn on your phone, goes like this to your battery....... Well I don't know how to type a SUCKING sound, but that's what it does. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
How do you run lkconfig? Do you launch Terminal Emulator first and then su?