yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
I too have had a reboot, and others have said they too have had them so I am working at it. Unfortunately I haven't been able to pull a logcat myself since it was just the once
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahagersr:
Yep old buddy, I'm getting reboots too. I've had three. Haven't had time to try and logcat.

Man this things snappy!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
I can't seem to get a logcat. It only happens when I'm at work and busy and I can't seem to reproduce when I have time :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
I have that same issue, unfortunately I changed so much since the last build I don't know what the issue is
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Update: reboots maybe fixed, send me a logcat or any specifics about reboots if you are getting them, its been a pain in the ass to catch it for me since it has only happened once or twice at random times when I wasn't pulling a logcat.

Deadline has been update to have 0ms latency (faster write speeds) credits to Imoseyon. I still get better performance with deadline but its battery friendliness has been critiqued so its up to you.

GPU overclocking: I have been hesitant to add this since any kernel that has it immediately has a debate of the effectiveness of it. I added it and tested it by benchmarking it several times on both clocks and averaging. I understand that benchmarks are not the best indicators, but it gives me a numerical comparison of the two. I got better performance consistently at 480mHz. If you do not like it for any reason, feel free to lower the max clock to 400. Any comments on it are welcome just consider what I have just said first.

I labeled the build as experimental since it has a lot of new changes and I haven't gotten much testing on it. I wanted to get a build out there right away that hopefully fixes reboots because those suck. Feedback improves the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
Just flashed got 2 SOD's in less than 30 minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Yeah, I did too, it appears the OC on the GPU is draining voltage, either increase voltage or lower max clock of gpu. I am fixing this as we speak

EDIT: its up, hopefully fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahagersr:
Fast support there.

I'll flash as soon as I get done with this road trip and give it a good days worth of trial.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
Got SOD again :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
info on what you do, govenor,OC speed, if you undervolt. or if you have stock values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Alright guys, SOD is a SOB. Trying to get voltages right, but it is all experimental. The most stable build is the build before the RC1 (since that one gets no reboots).

Feel free to send any voltages that improve stability

EVERYONE!! I AM AN IDIOT!! I MADE SOME VERY STUPID STUPID GIT MISTAKES AND MIXED CODE THAT SHOULD NOT HAVE BEEN MIXED AND THAT WHY THERE ARE SOD ISSUES! I AM WORKING ON IT, BUT LIKE I SAID, I AM AN IDIOT

EDIT: I seem to have found the mistake and fixed it. I am going to test this one a bit longer before releasing though ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
take your time bro! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
No reboots so far! Great battery so far! Thanks!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Final results no reboots or SOD plus over 4 hours screen time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Thanks for the feedback guys! After way too much work on this kernel I am posting RC2. It has all the changes from the previous changelogs without the bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
sweet man!!!! thank you!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahagersr:
RC2 is working great here. Zero issues thus far. Been running it for a few hours straight, no reboots.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unh1nged:
Wait, so.. who's an idiot?

Haha kidding man, no worries

You made a mistake, that's all. Your contributions are massively appreciated. Still my fave kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Hahaha it was straight up painful after I saw my mistake. Glad you like it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
There one one kernel that has been able to do this. Unfortunately this kernel is not able to be discussed on xda. PM me and I'll help you with G+ community to join for further help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephhi:
I'm hoping to include this kernel in my upcoming rom but RC2 is constantly rebooting for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Are you sure it is kernel specific? I have had 1 report of a reboot on RC2 and it wasn't reproducible. Can you give me some information on the context of the reboot? Also give me a heads up before packaging the kernel in the rom please if you decide to go down that route.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
I will see what I can do based on how hard it is. I can't work on it til Thursday however so don't hold your breath
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I have a S3 running BamRom 1.0 rc3 based on 4.3.1. I tried to install the 4.3 kernel but go hang ups w/ a weird screen.

Sent from BamRom S3 with Viper4Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Everyone, sorry to disappoint but this kernel is now dead. Due to a serious serious issue with the git client, me trying to delete 1 repo caused the deletion of my kernels repo instead. There will be no builds anymore, I would have to start from scratch and I do not remember every line of code I have changed for the past 4 months.

My sincerest apologies to you guys, I am still shocked myself right now, I can't believe it did that.

I will keep downloads up for now but I doubt the kernel will work bug free into the future without keeping up with driver updates and such. If there are any GPL concerns from any mods here on xda, please let me know and I will take the links down. I had source up until it got deleted. Thanks for the help, experience, and the times guys. You made this kernel a wonderful learning experience for me. Look out for my app in the next few months guys, its my new project if git doesn't screw me on that too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jazztrmpter:
RIP. That sucks man, that was a hell of a lot of work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Wow sorry man. REALLY appreciate everything you've done for this community with some top notch kernels.

Thank you sir. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cameronmx9:
Ouch man that sucks, I was just reading through this thread and was about to install. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Based on your sig you are on android 4.2.2. The 4.2.2 kernel is really going to be fine to use since it has the latest cm changes in it and most 4.2.2 roms aren't going to update so it won't be behind
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cameronmx9:
Yeah I may upgrade to the nightlies soon, but the last few days have been my first experience on a non-stock rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wtfdusk:
This kernel was great. I'll miss it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Thanks! Can't wait to have that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hungmung:
There are links to the needed changes fir it on the play store here

https://play.google.com/store/apps/details?id=com.teamkang.fauxsound&hl=en

Sent via carrier pigeon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Curse you, I was gonna play battlefield 3 tonight, now my impulses are gonna make me boot to ubuntu and try it out :P thanks man, this helps a lot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
YOOO I play bf3 too! well (used to) what do you play it on? PC? ps3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
both but mainly pc now

edit: I am the worst op, all other ops complain about off topic discussion, hell I embrace it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
On a more serious note, it says there's user custom under volting but I don't see it on trickster mod at all :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Yeah, just noticed I must have broken it at one point. Will look into and fix for next build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Build 3 has the fix for user custom voltages :)

ask and you shall receive - build 3 has the latest 2.1 faux sound support
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hungmung:
Thanks a lot running this now been looking for a aosp kernel that had faux sound and intellidemand support. Appreciate the hard work.

Sent via carrier pigeon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
Glad to see you got it up and running! Did you get the UV and default governor figured out?

Oh and btw my name has an extra "ta" in it. :p Just for the record.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Ooops gonna fix that right now. I figured out the UV issue, but still have no idea why its defaulting to interactive on first boot :/ it has no reason to do that. Until i do figure it out, it looks like I have to just leave it as is. In terms of funtunality, people just have to switch it to their designated governor and then its fine. Feel free to try it out and let me know what you think
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Just a FYI, the init post boot script in your rom likely defaults to interactive ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
something tells me I need to have a boot image and all to edit this :( still haven't figured that one out. I posted a detailed description of my dilemma here http://xdaforums.com/showthread.php?t=2390356. I am going to keep reading til I figure it out. Thanks for narrowing down the location
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Good news guys, just synced latest cm10.2 sources and successfully built a kernel for android 4.3! Going to make all the changes that are currently on the 4.2.2 build and get them into the 4.3 build. Expect a release later tonight at like 10 EST!

For those wondering, the only 4.3 build so far that I found was the unofficial cm10.2 found here -----> http://xdaforums.com/showthread.php?t=2390147
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobchef:
If you need a tester I am running that ROM right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Thanks man, I generally try to make sure that everything works before releasing to you wonderful folk, but I can miss stuff so feedback once you install is much much appreciated. Check it out tonight, perhaps sooner if I can find time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Huge fan following you have op
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Quite the sarcasm on this one :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
No seriously, excellent work man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Will definitely flash this once it's done
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Please read OP and give me feedback!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
Step 1 completed on testing of new 4.3 kernel. Kernel downloaded, flashed, and booted. Initial impression: smooth and snappy. Will edit once I'm able to conduct some further testing. Most of my testing will occur on the 08/05 release once it is out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
BTW: should be coming out with a bigger 4.2.2 update tonight
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
While you're at it, so you think it's possible to UC it to 192? I've only found one kernel that did it and I can't find it again. It saves so much battery life during deep sleep it's unreal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
I'm sorry but I don't think I am going to take this request. UC that low tends to give a lot of people sleep of death problems where the device won't wake up. I can however test it, but don't hold your breath 270 is pretty low as is.

Here is the kernel that goes that low btw ;) http://xdaforums.com/showthread.php?t=1756776

even the maker of that kernel keeps his standby on his phone at 486 instead of 192
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
Well, thank you for taking time to test. I never had any problems, but all phones are not created equal and whatnot. Excellent job. I love seeing new devs. I want to get into it so bad it's unreal. I used to make mods on my old iPhone all the time, but this OS is so different. And I only have a mac. It's hard to find good programs to work with. Hell, I even had to go to a friend's to root because I couldn't get casual to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
On one kernel "unnamed", I was running my phone at 81. I agree that every phone is different, but if the kernel is tuned correctly, there should be no issues running it at 192.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Well I already had a report on this thread with someone getting SOD at 270. If you would like super underclock there are other kernels that support it, but respectfully I try to get my kernel to be as stable as possible. You have to keep in mind that not only are phone created unequally, but so are ROMS. It is all dependent on what you do. Like I said, I would be more than happy to test it at a lower clock but don't hold your breath.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
No worries, man. Just keep up the good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Thanks! If you ever want a start in some kernel dev PM me. It really is rewarding if you are driven to do it. I knew next to nothing before I started.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Looking forward to it man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Just gonna chime real quick. Running 4.3 with Pwncakes 10.2 8/5 release and so far(it's only been an hour) all is good.

Using TricksterMod running 384/1512 Row/Ondemand. Will report if I run into any issues.

Thank you sir, so happy to have Faux Sound back!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
No problem, glad you enjoy it, hopefully bringing more tweaks to you soon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Sorry to disappoint guys but no new build tonight. I have spent the past 5 hours and I can't get it to flash. Need to figure out what went wrong. I will update the OP the moment I get it to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stratatak7:
Do not get discouraged. I know it is very difficult and frustrating. When I started modding, I must have spent hours doing the same things over and over to no avail. You can do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
No disrespect was meant by my post about lowering to 81. I truly hope none was taken. It fantastic to have a custom kernel out for Unofficial CM 10.2. Keep up the great work!!!!! Your work is greatly appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
None taken man just trying to explain why I am ambivalent about it. ktoonsez kernel can go pretty low and he is good with kernels! Glad you like the 10.2 kernel, I will keep working on it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hey op, can we have fifo as additional I/o. I remember on ix kernel, I used to get excellent battery with Fifo.

Edit: link to the post through which I used to get best battery

http://xdaforums.com/showthread.php?p=43613816
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
No problem! Currently working on figuring out what's wrong with the 4.2.2 build and when I get that to work I will add it to the 4.3 kernel and the 4.2.2 after that

EDIT: its a slower process since I constantly have to switch between two ROMs for testing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Hey if u need a 4.3 tester I'd be glad to help out. Still running Pwncakes 8/5.

Also if your taking requests, freelunch Scheduler ran fantastic for me. :) Kinda a joke, I know we're waayyy early in the land of 4.3.

Like I said tho, hit me up if u need testing done for 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Few screenies on how things are progressing for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Hahaha yeah 4.3 is an adventure. Getting the build out yesterday was hard enough. If I try over clocking at all, it makes the phone perform worse than some single core processors. The same with under clocking. Its honestly terrible, that's why it has such few tweaks. More will come though, don't worry :). I will try alternating between updating the two kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Muchos gracias for the feedback. A few notes, I notice your 384 had more time than deep sleep, were you texting periodically or doing something that woke the phone up often? Or did you have periods of nothing?

Also the data manager seems to be taking A LOT of battery, nothing should be pulling that much battery in my opinion, you might want to look into that or get back to me if that only happens on my kernel.

Lastly, your 3000 read ahead on your sd card is a bit unnecessary, I tried benchmarking it and improvements really stopped after 1000-2000 read ahead, so you could lower that value if you wanted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
THANK U sir also for your feedback.

Yep, this is the first I've seen My Data Manager pull this much battery. I've been using the app for a cpl yrs with obviously a lot of different kernels. Still tho, I can't say it's kernel related BUT I will keep an eye on it and get back to u if it continues.

Throughout today I've been using the phone on my two breaks and an hour lunch while at work. Mostly XDA, PowerAmp in the car, a few texts and just general surfing the net. I'll keep on eye on the 384.

I've had read ahead buffer at 3072 for yrs. My devices are usually packed with pics, tunes, videos, apps and such. I can't remember reading anywhere that having this at 3072 could have some adverse effects on battery or performance BUT I DEFINITELY could be wrong on this. I'm going to go ahead now and take it back down to between 1000-2000. You would know more about this then I so I'll take your word on it.

Really appreciate the feedback brother!! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
Good evening, aeppacher! Finally got around to flashing your kernel. I've been having issues with my phone lately so I didn't think it was worth it, but I got it all fixed. I'm at 53% battery right now, with 11 hours left on my shift tonight. I'll tinker with the settings and let my battery die, charge it up and post post battery life after it drains again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
What issues were you experiencing? Also what did you do to fix it? I am assuming you mean issues with the kernel. Also please specify what kernel you are running (4.2.2 or 4.3)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
I was running iX kernel and while it's a good kernel, when I updated my modem and bootloader it broke my camera and Torch. Took me a few days to make the connection, so now it's all fixed and my Bionic Sheep are kicking some wolf ass.

Edit: Charging back up now. Can't wait to see battery life. I'm a very heavy user and one of my games eats a lot of battery in a very short time. It's not even a "3d" game. Oh well. Will be posting pics of battery life when it gets back down to about 20% later tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Yeah man, My Data Manager is still suckin on some battery with stock kernel on Pwncakes 8/6 build he posted about an hour ago.

So definitely not kernel related. I think we kinda already knew this tho but just wanted to let you know it's not your kernel.

Weird, never seen this till today. I'll dig around and see what the deal is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Thanks! Um try clearing data on it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
UPDATE RELEASE 4

So unfortunately the latest build was uploaded just as I left the house to go out and when I was out I realized I gave the wrong link. It is now fixed and the latest link is the right one with the latest features:

-fifo

-cpu hotplugging (yay battery)

-easter egg on boot (this took too much of my time to get to work)

Next 4.3 Build should come in the next few days so keep checking!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update. Hope the latest release do the same magic which Iconic iX kernel use to do
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Thanks yeah it was the first thing I thought to do but need to wait till my billing cycle ends. Lol.

FWIW I don't get hung up on battery life. I have two batteries and run my device full bore. IMO takes the fun out of all this getting to hung up on battery life.

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Can any testers confirm if their CPU settings are sticking through a reboot (4.2.2 Build 4)? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
If no one else responds I'll load it up later today. I'm using your 4.3 kernel with great success ;) :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes they are sticking after reboot, using trickster mod app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Mine are sticking too with Trickster Mod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Lol guess trickster is being silly for me. Thanks guys. Keep the requests coming and any feedback
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
When you approach the 4.3 kernel again, what do you plan on adding first? Governors? or do you plan on making it as stable as possible and then add stuff in?

If I could suggest, perhaps a more stable governor like intellidemand and interativeX (although I'm sure they'll both need a porting of their own to 4.3). Both are nice and offer some good features. And maybe the IO sched I suggested and was added to the 4.2.2 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
As of now it is relatively stable. I plan on adding governors and IO schedulers as well as thalamus' hot plugging. Once I get that to work I will be working with OC, UC, and UV which seems to be the biggest hold backs as of now om the 4.3 kernel because they destroy performance on all the builds I have tried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Understood. When I said more stable governor I didn't mean to imply interactive wasn't. I simply meant, in my experience, intellidemand and interactiveX are more stable and easily ported than SmartAssH3, asswax etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Love the Easter Egg!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeppacher:
Its cool. I figured that. Yeah I hate giving dates and times because I feel bad when I miss them but look for the next 4.3 build tomorrow