yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
Great! :) I've been busy lately and haven't been able to look through the code for potential issues. Once I do, I'll shoot you a PM to try and track down the issue.

Again, thanks for the feedback. Getting in-depth bug reports tells me that it's worth putting some effort into dkp, which is high praise as far as I'm concerned. :)
[Verizon Samsung Galaxy S III] vmancini3:
I'd really like to use this kernel...it was AMAZING on AOSP...but I heavily rely on my phone everyday and would love to use the stable build once its ready! Maybe on the weekends when I'm home I'll try running the test build and see if I can be of some help...
[Verizon Samsung Galaxy S III] decimalman:
Pfft. Using your phone is for chumps. :p

I have tomorrow off, so I'll be able to poke around and try to figure out what the issue is. Details about issues are always appreciated, so if you do decide to flash it this weekend, please let me know how it goes. I'd really like to get a stable TW build out, and any details you can provide would help out. :good:
[Verizon Samsung Galaxy S III] thelangosta:
I understand, most of us have lives outside xda. I am happy help. I did download the tuner pack that has the diagnostic zip in it(2nd post I think) and will be flashing that after the kids are in bed. Would a random snapshot of what is going on help? I had a lockup last night but realized that the home key was still functional(power button has been unaffected) so just the screen and capacitive buttons were unresponsive. Battery life is great at 48% after 11+ hours and 2+ hours screen on so far.
[Verizon Samsung Galaxy S III] decimalman:
That's pretty bizarre. If your phone is still marginally functional after it freezes, then it may be possible to get some very useful debug information. I'll make a test build with lots of extra debug stuff compiled in and something to save it all. I'll let you know when I get it all put together.

In the meantime, if you can figure out a way to get a logcat or dmesg from your phone without having a working screen, it would be a huge help. A last_kmsg would help too, assuming that it gets saved properly after a freeze.
[Verizon Samsung Galaxy S III] thelangosta:
I will definitely try the test builds. The only issue I have is that we are leaving on a 9 day camping trip tomorrow. Is there a way to use adb on my transformer to debug the phone? Not sure I have ever heard of that use for an android tablet before.
[Verizon Samsung Galaxy S III] decimalman:
I'm sure it's technically possible, but I have no idea how you'd actually do it. The ROM on your Transformer might include adb, so you might be able to use it with a USB-OTG cable or ad hoc WiFi. It would be pretty impressive if you managed to pull it off. :) If not, enjoy your vacation and don't worry too much about dkp. I'll get it sorted out one way or another.
[Verizon Samsung Galaxy S III] thelangosta:
I will definitely be looking into it. Gonna ask the dev of the Rom I am on if he has done it or heard of anyone doing it. Maybe adb via Bluetooth! It is cm10.1 so at least there is a large user base to query. I am not worried about dkp. There is a good dev working on it. LOL, I couldn't even type that straight faced. Sounded pretty corny in my head. Thanks
[Verizon Samsung Galaxy S III] decimalman:
A good dev? Who? LOL :p

It has to be possible, but you might need some serious nerd skills to pull it off. I think as long as you can do some kind of networking between the two devices, there's probably a way. "adb connect <IP>" should be able to manage, assuming that the adb binary on your ROM is fancy enough to manage it. I think CM will probably have a decent binary, so it's worth a try.
[Verizon Samsung Galaxy S III] dave_k605:
Thanks for the kernel.
[Verizon Samsung Galaxy S III] Droid316:
So the 6/14--3.4 kernel will work on liquid 2.7 official?
[Verizon Samsung Galaxy S III] kimber45:
https://github.com/kosborn/p2p-adb

Someone has definaltly been working on android to android adb. Will update with more links if I find anything else.
[Verizon Samsung Galaxy S III] thelangosta:
So I posted the question over there in the thread and one of the users replied that I should try the Bootlog Uptime app. It pulls a last_kmsg and logcat when it detects a crash. I am hoping the problem will trigger this app even though it does not seem like a full on system crash since I have to reboot it. I will post up if it notifies me of a "crash".

Edit: There are also some wifi adb/adb wifi apps that you put on the phone and run in the background. You can then view the output in the browser of another device on the same network. I am not sure that this would be a good idea on an open campground wifi network.
[Verizon Samsung Galaxy S III] omair2005:
is it possible to add usb otg support?!
[Verizon Samsung Galaxy S III] decimalman:
I don't have an OTG cable handy, so I have no idea what's preventing OTG from working. I might have to go buy myself some new toys. :D

It should. It works for me, but I've seen several reports that it won't boot. YMMV.
[Verizon Samsung Galaxy S III] dpaine88:
Searched but no luck.

Can anyone tell me the difference between "freelunch" and "nanolunch"?

Thanks
[Verizon Samsung Galaxy S III] decimalman:
It probably didn't get mentioned on this thread. nanolunch is basically the same as freelunch, except that it uses more precise (but less accurate) CPU load statistics. By default, nanolunch also has a few tweaks that might make it a bit smoother at the expense of a small amount of battery. Personally, I run nanolunch most of the time, and and it seems to get basically the same battery life as freelunch but feels a bit smoother to me.
[Verizon Samsung Galaxy S III] Droid316:
So how stable are the TouchWiz kernel?

Any problems or can it be used for daily use.
[Verizon Samsung Galaxy S III] decimalman:
There are still some issues, especially on VZW/USC. thelangosta has been providing lots of excellent feedback on the subject, and it sounds like it's pretty stable except an occasional freeze after calls. I'm in the process of reworking some code that I know is causing issues, but it sounds like there's probably another bug that I haven't been able to track down yet.

There might be a new test build coming out later today (I'm working on two projects on AOSP and one on TW, so there's no telling what I'll get done today). If you're feeling adventurous, I'd love to hear whether it's any more stable.
[Verizon Samsung Galaxy S III] thelangosta:
Today I have not had a single lockup. That's with texting, using navigation, email, calls,etc. Seems like it is sorting itself out. I have that Bootlog Uptime app running just in case it does lock. Still on row/nanolunch combo without any further tweaks.

Edit: Err, spoke too soon. It really is just the touch input that freezes. Screen rotates, volume buttons work, home button works. If I long press the power button that brings up the reboot as normal but of course I can't select reboot. If I just turn the screen off it stays off. Now I have to figure out where the loss from Bootlog Uptime went.
[Verizon Samsung Galaxy S III] vmancini3:
OK....took the otter box case off of my phone...ready to do some testing!!! Just have one question....what is the best way for me to provide useful information? I know I did insert my own custom line into the build.prop file that disables logcat for added ROM speed....so should I remove that line? And I've never done a logcat before (really my first time testing anything), so if I need to do one what's the proper procedure??? I'd really like to assist in making this fully stable TouchWiz kernel a reality!!!

Edit: You could tell me how to do the logcat....but I'm gonna do the "right" thing and Google it!

Edit 2: So it turns out there are a couple of ways to get a logcat...either with an app or using manual commands....which would you prefer? Is one any better than the other???
[Verizon Samsung Galaxy S III] vmancini3:
One thing I'm noticing right away that seems to be strange is the voltage table appears to be reversed...the higher the MHz the lower the mV...its been the other way around with every other kernel I've ever flashed...is this normal?
[Verizon Samsung Galaxy S III] decimalman:
Sorry, I got thoroughly distracted.

From what I can tell, the peculiar nature of the freezes will make it hard to get good debug info. Ordinarily, when you hit a catastrophic kernel bug, a bunch of debug info gets saved and your phone reboots automatically. Unfortunately, it sounds like what's happening instead is that the kernel keeps hobbling along without saving any debug info, but isn't functional enough to easily save the debug info yourself.

I suspect that the only way to get good debug info requires access to a computer with adb installed and configured. If you've rooted your phone, you probably have all the drivers you need installed, but adb is another matter. I'm working on saving you the trouble of installing the Android SDK just to get adb, but I haven't gotten there yet. Once I have something set up, I'll PM you with details. Thanks for testing. :good:

What app are you using? That's definitely not right, and it'll probably crash your phone if you apply a voltage table like that. I hadn't noticed any misbehavior, but then I occasionally miss obvious problems like that. :laugh:
[Verizon Samsung Galaxy S III] vmancini3:
I'm using setcpu....and ....here....just look...and my phone's running fine...lol...I'm telling you...I'm able to do like anything to this phone and it just takes it!
[Verizon Samsung Galaxy S III] decimalman:
I could have sworn I fixed SetCPU like 3 months ago! It's caused by a silly bug in SetCPU, but it's easy to fix in the kernel instead. I can't believe your phone can tolerate voltages that low.
[Verizon Samsung Galaxy S III] vmancini3:
Actually....I just had to do a battery pull.....I put the frequency up to about 1782 MHz and....yeah my phone crashed and crashed HARD!!!!!

I believe the reason its still working.....is because I cleared the data for SetCPU so now its back at the default settings of 1026 MHz min and 1512 MHz Max....and at those settings...its actually running just fine....also keep in mind I'm using my phone while its plugged in and it won't even get up to 90°F......forget that....now its at 95°…but still stable from what I can tell...

I'm gonna try a different tuning app...
[Verizon Samsung Galaxy S III] decimalman:
I'm impressed it was running at all. :)

I haven't tracked the 1026 MHz bug down yet, but I'd strongly recommend setting the minimum back to 384 if you notice it set to 1026. I had no idea how hot these phones could get until I left mine charging, rescanning 20 GB of music, and running a 1026 MHz minimum.

YGPM.
[Verizon Samsung Galaxy S III] vmancini3:
AntuTu CPU master seems to be working with this kernel nicely...I'm running right now with a min of 594 and a max of 1296 using the freelunch governor with the row scheduler and man this thing has turned my phone into greased lightning!!! I've also been on my phone with the screen on non-stop for about 30 minutes already and I'm only at 96% battery!!! So far so good! The min and max settings that I've put into place also seem to be sticking I should add!
[Verizon Samsung Galaxy S III] vmancini3:
Except for the CPU min and max speeds bouncing around to wherever they feel like....I have yet to encounter any issues.
[Verizon Samsung Galaxy S III] david_hume:
Just change the governor to fix that issue.

sent from my GS3 from the infected army
[Verizon Samsung Galaxy S III] vmancini3:
Doesn't matter what governor I use...does the same thing....
[Verizon Samsung Galaxy S III] PaulG1488:
Use a better app
[Verizon Samsung Galaxy S III] vmancini3:
Which one do you suggest....I've tried at least three...all with the same result...although I know there might be like 20 more apps that all do the same thing to some extent...
[Verizon Samsung Galaxy S III] vmancini3:
Currently testing every single app I can find to control/tune the CPU and governors/schedulers! Will report my findings later...
[Verizon Samsung Galaxy S III] decimalman:
It has nothing to do with the app, and probably very little to do with the governor. TW has several services that change the settings. Some apps (Trickster, Kernel Tuner, maybe others) have an option to lock the frequencies, but it may or may not work reliably.

I'm in the process of fixing a few bugs (and potential bugs). I've set up a blacklist that can prevent certain services from changing frequency settings, which should should fix the 1026 MHz bug and help settings stick. I also cleaned up the code that tracks user interaction, which I think is (possibly) causing freezes. I'm testing now. If all goes well, I'll finally upload the test builds I've been hinting at.

EDIT: I should really test before I announce new builds. :p PC hardware issues and a new bug or two are holding up new builds.
[Verizon Samsung Galaxy S III] vmancini3:
Sweet....looking forward to it! Even as it stands right now...this kernel is giving me better results than all the other ones I've tried....and I really do think I've tried them all!

P.S. - haven't had my phone freeze yet...

EDIT - Too bad I'm not there to help you out...lol... I'm A+ certified...
[Verizon Samsung Galaxy S III] decimalman:
It looks like I might have some faulty hardware in my computer. Needless to say, test builds will be delayed until I get it worked out. Anyone have a beastly computer that I can SSH into? :p

I'll update once I'm up and running again.
[Verizon Samsung Galaxy S III] vmancini3:
what exactly are the requirements for you to consider a computer "beastly"? I have a computer not being used at the moment...but I'm gonna take a guess that you're using Linux....? And if you are...what distro?
[Verizon Samsung Galaxy S III] decimalman:
I was mostly just joking. I don't especially want to do development over SSH. :)

I think I just have a wonky memory module, so hopefully I can just run a few tests and pull the DIMM. If not, I'll have to track the issue down and hold a donation drive to replace whatever is fried (joking!--it's my computer and I'll buy my own parts :)). I might be able to hobble along and get a new build out, but it'll be a pain since builds fail so much that it takes about an hour to build for a single device. :(

Assuming I'm the only person using the computer, my requirements for dev work would be 4+ cores at 4 GHz or so (Intel preferred, since I'm a fanboy :p), 8+ GB RAM, at least 10 GB unused disk space, and a reasonably fast internet connection. And Linux, of course. Personally, I run Gentoo, but any ol' distro would work. And as long as I'm listing off everything I need for development, vim. I can't live without vim. :D
[Verizon Samsung Galaxy S III] vmancini3:
Wow.....yeah....I definitely don't have anything close to the caliber you're speaking of....:( And hey....you do what you can when you can...we know how it is...this type of stuff isn't easy by any long shot and I for one really appreciate the work you've put in already....like I said...I've flashed EVERY (no exaggeration) kernel there is to flash...and on a TouchWiz ROM, no other kernel has given me the results that your kernel has! I've been running it since Friday night and I still have yet for my phone to lock up or freeze or anything...the only issue I see is I can't get the min and max speeds to stay put.. .that's it...if you need anything that I can actually help with..just ask...I'm on here like there's no tomorrow:D
[Verizon Samsung Galaxy S III] decimalman:
I'm working on getting everything running again. I think I have a wonky memory module, so I'm in the process of tracking it down. Unfortunately, memtest86+ isn't doing its job very well, so this might take a while.

The requirements I listed are basically the computer I build on, and thanks to the absurd optimization flags, it already takes something like 20 minutes to rebuild a single device's kernel. I'll be the first to admit that THAT'S FRIGGIN' RIDICULOUS.

The min/max thing should be pretty easy to resolve once I can cripple whatever is responsible for it. I'll let you know when I get a bootable kernel put together. :thumbup:
[Verizon Samsung Galaxy S III] countryfolk07:
Anyone running this on SlimROM with new firmware? I really want to try this kernel. Currently using BMS. I get 24 to 30 hours with 4-6 hours screen time, depending on phone usage, maps, etc. all on network. I'm just a fan of if it ain't broke don't fix it. LOL. Thanks for any info.

Fine print..... I have the Samsung 3000mah battery.
[Verizon Samsung Galaxy S III] PaulG1488:
I just went on slim rom with this kernel today everything is smooth sailing so far.
[Verizon Samsung Galaxy S III] Cruiserdude:
Those specs aren't too much beyond my box, tho I only have 4gb ram (bad dimms, just like you, and have my memory timed at 6-8-6 @1.5v and can't find 2 more dimms that'll hold that without adding voltage) and I tend to run my i7 860 only to 3.6 ghz, as I don't like having to add voltage. Started out at 2.8 and I've still got a mild undervolt going on, so I'm happy. It's responsive, cool, and efficient, so no complaints here.

Never been able to bring myself to try Gentoo, I honestly prefer plain old Kubuntu these days, as the Ubuntu base is really stable and it's easy to troubleshoot, plus most of what people seem to hate about Shuttleworth OS these days seems to be based around Unity, which ain't a problem for a KDE fan like myself. I like to play around with other distros and got an Arch partition I'm playing with atm, but that's about it.

If I knew my way around a computer a bit more I'd love to try a more in depth distro, or maybe finally learn some code so I could contribute to what awesome folks like yourself do. The farthest I've ever gotten is building a LAMP stack on an old computer for the hell of it, but maybe someday!

Anyway, I'm rambling now, but I must say I'm quite thankful for folks such as yourself who know their way around this code and are willing to put in some quality work while being respectful of other devs and users, expecting only the same respect as payment. Considering some of the stuff that goes on around here, it really gives me hope to see that kind of attitude. So thanks man.

:thumbup:
[Verizon Samsung Galaxy S III] pocii29:
If you check back. I pushed mine on carbon rom with almost 5 days use and 10 hours on screen

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] juancaperez2000:
Stock battery?
[Verizon Samsung Galaxy S III] vmancini3:
No...I'm sorry...but there is absolutely NO way ANYBODY is getting anything close to 10 hrs. screen on time with a stock battery....
[Verizon Samsung Galaxy S III] TheDriller:
I got 6... And screens to prove it :P... Then I bought a lemon
[Verizon Samsung Galaxy S III] vmancini3:
yeah....but you're different....you have some sort of demon magic...lmao!!! I do know that when everything is right in the world and all the planets are aligned just right then a person can always get more battery life then the next guy...plus....for me I don't think it helps that the original s3 I had didn't like it here on earth and wanted to take a trip to the underworld when I decided to plug a flash drive into it via an OTG cable...the darn thing never turned back on and when following advice from the Verizon "tech" over the phone just to do what I had to do to get a replacement...the phone got so hot I almost burned myself...no joke... So in a nutshell, I think I dramatically shortened the life of my battery...and btw the new phone (one I'm using right now and have been using since) has absolutely no issues with an OTG cable and flash drive! I'm lucky that I've been getting roughly 4 hrs. screen on time as it is....because I've been reading everything there is to read here at XDA and trying every tweak and/or app you can imagine!!! I really think I'd be able to get close to 5 hrs. of screen on time if my battery hadn't already been accidentally abused...
[Verizon Samsung Galaxy S III] pocii29:
No way haha. I can push like 28 hours on stock. This was a lemon

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)

---------- Post added at 04:47 PM ---------- Previous post was at 04:36 PM ----------

Hehe. I'm sure I could push 6 days on stock battery if I was,

A. Running tw.

B. severely under volted and Underclocked.

C. A very conservative governor

D. Left it absolutely alone and it never left deep sleep from the moment it was unplugged.

****, now you got me thinking.. Yeah right. Not using a phone for 6 days is like disconnecting yourself from the time continuum lol.

I guess that's what's fun about all this. Trying everything to push it to a new level...

Have you tried nanolunch on your tw roms yet RErick?

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] countryfolk07:
I'd like a little more realistic every day use. 4g only, I don't have Wi-Fi anywhere. I don't want to cripple my phone, or not use it, for sake of battery. So I guess I was asking for an everyday comparison between this kernel and BMS. Thanks again.
[Verizon Samsung Galaxy S III] decimalman:
Good(?) news! I finally got a freeze and got a bunch of debug information. It looks like I was totally off-base, and there's an issue in the video drivers. If all goes well, there might even be a surprise in store for TW users. :)

Assuming you're strictly interested in AOSP (dkp on TW isn't exactly stable yet), there shouldn't be any earth-shattering differences. It's just a kernel, after all. ;) It can't reduce the power needed by your modem, but I've gone out of my way to improve battery life in areas the kernel can touch. Fun fact: Sprint used to have a battery life thread, but nobody has posted in it since I posted an unusually good run with an early build of dkp.

Intel processors are a pleasure to work with. I haven't played with an AMD since my 2004 AMD64, and I don't want to switch back. I use an i7 950 overclocked from 3.0 to 3.8 GHz without any signs of instability (recent memory issue aside). I never actually expected to need 12 GB of RAM, but dat triple-channel speed. :p Turns out that building kernels with LTO takes a staggering amount of RAM, so I'm glad I invested in an excessively large kit.

I love Gentoo. I cut my teeth on Slackware, so I'm used to building from source and occasionally putting together duct-tape-and-bubblegum fixes when stuff won't build. I can't honestly recommend Gentoo to anyone (compile times and low-level maintenance :(), but for me personally, the package management makes sense and it's nice to have source tarballs sitting around when I need to fix what ain't broke. :)

I used to keep an extra partition handy for when I wanted to experiment with another distro or a BSD, but I haven't tried anything new in ages and I needed more space in /home (~/android is up to 143 GB! :D) so I repurposed the partition.
[Verizon Samsung Galaxy S III] vmancini3:
How do I thank more than once...lol

And any chance you can remember what you were doing when it froze??? If I could actually get my phone to freeze or lock up I think I'd also be able to provide a decent amount of info... seems like I might have to go out of my way to make that happen.

EDIT : Btw...if I may add....I know you said these issues had nothing to do with any of the tuner apps....however...something you just said goes along with something I have been noticing....

You said it turns out it's an issue with the video drivers right? Well..strangely enough, AnTuTu CPU Master seems to be the only app that works somewhat well controlling the kernel...and I have noticed that any time I open that app after I've cleared away all open apps...the screen gets dim for a split second as the app is opening...just thought any info would be better than less info...
[Verizon Samsung Galaxy S III] joshua5683:
I'm getting weird graphical issues, is it kernel related? An odd thing happened: http://xdaforums.com/showpost.php?p=42920939