yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Bort76:
I really appreciate you looking at it.

That explains it. Held power last time.

The voltage table is default for the kernel and no overclocking. Does you kernel undervolt compared to stock? I've been trying to find the stock voltage table to compare, but I didn't have much luck. I may try bumping voltage up in steps to see if it helps. Right now, I've tried disabling MPDecision to see if that does anything.

Again, thanks for the help.

----------------------------------

Update:

I don't think the problem is the kernel (or, not specific to this kernel, at least). I spent the weekend flipping switches in Kernel Adiutor to see if anything would help, but no luck. I ended up trying a different kernel and still had the freezes. Finally, I tried to be smart and wiped system, reflashed CM (Nightly 4/26 this time), and reflashed dkp. It has been a day or so with no freeze, so I'm optimistic. [knocks on wood]

----------------------------------

Update:

Spoke too soon. Froze up again. Maybe it's just dying of old age. Oh well, I'll either figure it out soon or move on. C'est la vie.
[Verizon Samsung Galaxy S III] AyUaxe:
Might try a wipe and update to CM 12.1 5/23 or 25. Those builds seem very good for a few folks. I've been using dkp steady for about a month and latest has been more stable. I also flash vmin1100, but otherwise don't change any voltage. Running CPU 1782 Max, 54 min, tierservative or freelunch govs. Earlier kernel build gave me freezes on freelunch and any change to GPU. Those would be my bets for your culprits. Also, be sure your firm ware and radio are up to date. Lots of gremlins related to outdated firmware.
[Verizon Samsung Galaxy S III] decimalman:
dkp has fallen pretty far behind CM, so it's time for a new build. Unfortunately, I still haven't tracked down the battery drain issue that's been affecting some people. :( Since nothing has changed for 4.4, I'm only doing a 5.1 build.

Changelog:

Synced with CM: lots of cleanups, fixes and optimizations.

dkp uses the stock voltages unless you flash the vmin zip, disable "Override Minimum Voltage" in KA/Trickster, or (obviously) change the voltage table. If you've flashed the vmin zip since the last time you flashed your ROM, you can remove /system/etc/init.d/00dkp-vmin and reboot to undo it, or just re-enable "Override Minimum Voltage."

It looks to me like you're seeing some kind of hardware instability, but I'm not sure which hardware to blame for it. It looks like memory is being corrupted, but I'd expect apps to force close frequently if the memory itself were to blame. I'm not sure what to suggest, sorry. :(
[Verizon Samsung Galaxy S III] Deliquified:
The CM boot screen had an issue for awhile where there was a memory leak that caused instability.. No idea if that ever got fixed. Perhaps something to look into
[Verizon Samsung Galaxy S III] decimalman:
This looks like a considerably more sinister issue, unfortunately. :( The last_kmsg Bort76 posted suggests that the memory where the kernel itself is stored was being overwritten or corrupted. That memory is protected from software trying to change it, which is why I'm thinking it's a hardware issue.
[Verizon Samsung Galaxy S III] decimalman:
A lightbulb just went off. I'll send you a PM in a bit. :)

EDIT: Both last_kmsgs point to the same section of code. I thought I spotted what was happening, but it turns out to be nothing. I'll PM if I find anything.
[Verizon Samsung Galaxy S III] :
[MENTION=4932679]decimalman[/MENTION]: You're getting power collapse reboots? ;p Some men really do want to watch the world burn
[Verizon Samsung Galaxy S III] decimalman:
You just had to ruin my fun, didn't you? I was happily deluding myself into thinking SPC was working. :p

Is this how SPC crashes usually look? I expected a little more fanfare than trapping an invalid instruction after a returning to an incorrect address, hundreds of cycles after (apparently) successfully resuming.
[Verizon Samsung Galaxy S III] Bort76:
The power collapse reboots are probably a red herring. Of the 10 last_kmsgs I've been able to pull (even with a long press on power, most don't save ¯\_(ツ)_/¯ ), only two have involved the power collapse. Mostly, they are read/write errors (usually in mmcblk0p15-8, which I think is the app data partition), plus just miscellaneous other panics. Leads me to think I have corrupt memory or corrupt storage or a gypsy curse.

I put together a 'greatest hits' of kernel panic messages for my own use, to look for any common issues. I didn't see a pattern. But, if you want to torture yourself, feel free to have a look (I've attached a txt file). @decimalman, you've been incredibly helpful, but don't kill yourself on this. I've pretty much come to terms with it being a lost cause. :good:
[Verizon Samsung Galaxy S III] :
I was just busting your balls, it does look like this error is isolated to this user. I think he even said it didn't matter which kernel he used.
[Verizon Samsung Galaxy S III] decimalman:
New builds are up. I was playing with the toolchain I use for dkp, and discovered a handful of interesting optimization possibilities. Everything seems stable, but it's possible that some new issues will pop up with the new optimizations.

Changelog:

Synced 5.1 with CM

Updated to BFQ v7r8

Reworked some hotplug infrastructure in preparation for a project I'm planning

Overhauled auto-hotplug: it's now more efficient and much more aggressive

Enabled -ftoplevel-reorder, allowing LTO to do a better job optimizing

Specialized some LTO behavior to further improve optimization

Added a few smaller optimizations: inlined spinlocks, improved optimization for CPU hotplug, etc.

Normally, I'd just describe optimizations as "...and I optimized some stuff," but I'm pretty excited about the new optimizations in this build. The benchmarks I usually use to evaluate changes are all showing 5-10% improvements, and battery life over the past 24 hours has been noticeably better. Not too bad, considering how little I actually changed. :D

You've got a weird and sort of fascinating bug on your hands. I don't think I'll come up with a solution, but it's still interesting to explore. :)

Meanie. :p
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=4932679]decimalman[/MENTION], I'm trying to download your kernel for d2vzw but I keel getting a failed download as soon as it starts, it doesn't matter which build I try they all fail, any ideas, I've tried several times.
[Verizon Samsung Galaxy S III] decimalman:
Well, we were overdue for some MediaFire issues. It's been whole weeks since anyone mentioned not being able to download. :mad:

The usual advice is to try a different browser, or download on a computer and push to your phone. I have no idea how well either option works (I don't download my own builds :p).
[Verizon Samsung Galaxy S III] Jeremy.Stewart85:
First off I want to say thanks for the kernel, seems to be the only one in such active development for this old workhorse on AOSP. The battery life has been awesome while running and it generally feels like a snappy new device as opposed to a 3 year old slug.

Unfortunately for me, I'm getting similar symptoms to Bort. Sometimes the phone locks up with a black screen, even as a notification light continues to blink. Other times it will fully reboot. I've collected a couple of kmesg for each scenario and will try to collect more as they come in. Unfortunately I've changed a bunch of variables in between the two logs as I was trying to get things to work, but the device still fails in similar ways so I think whatever is causing it has remained constant throughout.

Some theories:

It seems loosely related to times when I move outside of wifi signal range or move between WAPs. That isn't 100% but it has happened most frequently right when I leave the house or after I leave work which I have steady signal at.

It does not appear to have to do with idle/peak CPU usage. My phone will sit completely idle all night without a lock or reboot, I've run benchmarks and those are also stable.

My setup:

Hardware- Verizon Samsung S3 16GB pebble blue from the original batch to make it to the US.

Kernel- both the 5/29 and 6/08 dkp build.

OS- CM12.1nightly 5/28 and 6/12

CPU- 1512MHz max, 54MHz min. Voltages are all -50mV except for the lowest 9 slots which I kept at 875 for stability. Tried both tierservative and freelunch governors.

I/O- Tried both zen and row internal storage schedulers.

Attached the relevant parts of kmesg.

Not expecting miracles but would love to get this working! The default CM kernel manages to burn through my battery quicker than I would like so I want to avoid going back. Let me know if I can help. I don't have a ton of spare time to throw at this but I'll do what I can.
[Verizon Samsung Galaxy S III] decimalman:
#pebblebluemasterrace :D

The S3 is still my main device, so I plan to continue development for the foreseeable future.

You're right, that looks exactly the same as one of the issues Bort was seeing. I'm starting to suspect that standalone power collapse isn't as fixed as I had hoped. Your logs and Bort's both show the same thing: a while (measured in CPU time, anyway :p) after returning from SPC, your CPUs go off the rails and start trying to run non-code from a bogus area of memory. I have a very vague hunch about why, but I'd like to know if SPC is really to blame before I try to fix an issue that might not exist.

Once I figure out something else I'm working on, I'll send out a test build with a number of changes to help track down a few bugs that have been reported recently. Among other things, I'll add a switch to disable SPC. Hopefully it'll help.

The notification light will continue to blink, regardless of what the CPU is doing. It has its own hardware to cycle through its animation. That's not relevant or anything, I just think it's neat. :)

CM12.1's battery life is terrible for a reason: the CM kernel currently has almost all CPU power saving features disabled. Since cores won't be powered off, and they can't enter a deep idle state, they just waste power and accomplish nothing. The end result is better performance, but (IMO) the cost to battery life is way, way too high.
[Verizon Samsung Galaxy S III] AyUaxe:
If you want something like a control to try that test build, please count me in. I'm not having any of the problems noted above. Dkp is butter for me. 54-1782mhz-phone died lock on any higher frequency. Minimal voltage changes. Don't feel i have enough knowledge to fool with those. Deadline for internal, sio external. Illinois for TCP conflicts works great.
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=4932679]decimalman[/MENTION] can I get a good link to your d2vzw kernel?
[Verizon Samsung Galaxy S III] :
Hi, I was wondering if you have plans to give support to the Sweep2Wake and/or DoubleTap2Wake features again or I shouldn't count on it?
[Verizon Samsung Galaxy S III] decimalman:
As much as I'd like to get it working, I don't think it's going to happen. :( Our hardware really can't support it very well--it takes too long for the CPU to wake up to process the touchscreen data, which makes it impossible to detect gestures well. The only solutions I can think of are to write a custom touchscreen firmware that processes the gestures on the touchscreen itself (this is how devices that natively support S/DT2W do it) or to completely disable deep sleep while S/DT2W are enabled. Neither option appeals to me.
[Verizon Samsung Galaxy S III] :
CM has proximity wake, keeping the sensor on all the time doesn't eat too much battery...
[Verizon Samsung Galaxy S III] griz.droidx:
Great kernel for me dkp so thanks for your continued support. Really. Thanks good sir.
[Verizon Samsung Galaxy S III] Krystalmyth:
Got people jealous of a phone from 2012 because of people like you. I wish I could pay the money ive saved on upgrades to you. I'm at a point in my life I've lost so much I have very little, but I have a phone that refuses to die reminding me I shouldn't give up yet. This phone isn't anything like it was back then. It has grown with me. So I just want to say thank you, for not giving up on people like me who struggle in this world; so a girl can feel like they're still relevant. This is why XDA has done something incredible in the superficial world of tech. Somewhere in these little slates of metal and glass, you put a piece of yourself. Never going to see this phone on Craigslist. Thank you again.
[Verizon Samsung Galaxy S III] griz.droidx:
Krystal, very well said. Totally agree especially after seeing a lack of ROMs and kernels for other newer devices. And this one still does everything I need it to. I'm in the same boat. Decimal and other devs make my day a little brighter at times.
[Verizon Samsung Galaxy S III] AyUaxe:
This kernel with cm12.1 has been and continues to be da bomba. Some of us have been hawking dkp on the d2vzw cm12.1 xda forum started by [MENTION=6629594]mastercylinder[/MENTION], continuation of [MENTION=2963287]mastamoon[/MENTION]'s, [MENTION=2385005]invisiblek[/MENTION]'s, [MENTION=4131011]amf66[/MENTION]'s, and [MENTION=3124924]timedroid[/MENTION]'s work keeping development alive until it became evident there was sufficient interest/devotion for cm and his honor, [MENTION=2044079]Nardholio[/MENTION], Ball Buster and Maintainer, to pick us up. We are individually not worthy, but as a community--we're still not worthy, but dayum, this is what Android is really about. Thanks to you all!

Now could someone explain a bit about the voltage tables, like how to determine optimal settings?

Update edit:

Searched around but didn't find any clear info or app to assess actual voltage requirements for any given cpu frequency-seems it's trial and error. Flashed dkp-vmin-800.zip. Used Adiutor to set lowest speed tier at 815mv (min 54mhz, no signif lag coming out of deep sleep, etc.). Current stable Max is 1782mhz/1200mv. Tried 1890/1230--snappy and initially stable, but saw some weirdness with BT and ui transitions that I haven't seen before or since. If anyone else has tips to fine tune or segments of the tables that should be given more attention, that would be appreciated.
[Verizon Samsung Galaxy S III] bryank29:
Ok, just flashed the 5.1 aosp for my S3 running CM 12.1. Running it out of the box...what are the recommended tweaks, or is it best to just run as is? Right now

Frequency Lock is off. Frequency Profile is untitled, min is 384000, max is 1512000. Governor is tierservative. I am using Trickster.

Looking at the main page, 1512MHz is at 33%, next nearest is 702 at 1%, 648 at 26%.
[Verizon Samsung Galaxy S III] AyUaxe:
Look at my comment above, read the op on this forum, then search this and master cylinder's forum for further details. It's mostly trial and error, since different phones, though the same model, can behave differently, due in part to variations in chip supplies and other manufacturing variances. Just don't set new tweaks to apply at boot, until you've run them a while to confirm they work.
[Verizon Samsung Galaxy S III] bryank29:
can't find delete, so edited...didn't realize Voltage app was similar to Kernel Adiutor. So that is the one I am using.

Made tweaks, and MFLOPS went from avg 580 down to 450-470. But need to give it a full day of doing stuff to make sure performance hasn't suffered.
[Verizon Samsung Galaxy S III] bryank29:
Is there an MFLOPS score that is "too" low?

So I just noticed, running StabilityTest...it FORCES the userspace governor on it's entire 10 minute test. So even though I set freelunch in Kernel Adiutor. I kept noticing my freelunch option would switch back to userspace AFTER the stability test was complete.

EDIT - Just read on the screen it says a different governor may be selected, and my governor "freelunch" will be restored IF stability test has no crashes. So I guess if I go back to Kernel Adiutor and see userspace selected again, that means freelunch did not work out well? Or does that mean I should consider changing my frequencies?
[Verizon Samsung Galaxy S III] bryank29:
there is not a ton of information it seems when setting an I/O scheduler with internal vs external storage. I did SIO for internal, and FIOPS for external since it seems fiops is closer aligned to performance.

The stability test kept kicking me back to userspace, so I just set it to freelunch and left it.
[Verizon Samsung Galaxy S III] AyUaxe:
Give deadline a try for internal and sio for external SD. I'll be interested to know if you see any performance difference.
[Verizon Samsung Galaxy S III] bryank29:
Right now, my battery won't charge past 64%...it's very odd and I have no clue if it has to do with kernel tweaks or if the nightly I flashed today had a change. I saw a new changeset that mentioned power consumption in tonights nightly, so going to flash that first before blaming the kernel tweaking.

I will try your changes.

I noticed after doing the SIO for internal and FIOPS for external, my battery felt like it was draining QUICKER. They changed power from 20 to 0.75. No clue what that means and no clue if connected.

static struct sensor_desc sharp_gp2 = {
.sensor = {
.name = "GP2 Proximity",
.vendor = "Sharp",
.version = sizeof(sensors_event_t),
.handle = SENSOR_PROXIMITY_HANDLE,
.type = SENSOR_TYPE_PROXIMITY,
.maxRange = 1.0,
.resolution = 1.0,
.power = 0.75
},

---------- Post added at 05:05 AM ---------- Previous post was at 04:16 AM ----------

well I flashed the July 17th nightly and it's charged past 66% now...but it reverted the kernel, so I may flash the kernel and just see.

---------- Post added at 05:28 AM ---------- Previous post was at 05:05 AM ----------

When I look at the frequency table, my uptime has been 4 min 21 seconds (after reboot) and 1512 Mhz holds 23%, then nothing till 1242Mhz (which is my max setting). Should that tell me anything?
[Verizon Samsung Galaxy S III] AyUaxe:
I think you need to go through the better part of a day of normal use before those frequency tables can tell you much. Obviously, if you're getting high frequencies and little or no deep sleep, then something is running hard more than it probably needs to. Battery stats may show what it is. Others probably have some additional, better suggestions.
[Verizon Samsung Galaxy S III] bryank29:
Do you guys typically run in "Battery Balanced" mode?

So should I be keeping an eye on Battery Stats as well as the Running Apps section? My typically always running apps are Settings (since I am actively looking at it), weatherbug, instagram, google services, google play, google app, google keyboard, and themes).

I cleared my battery stats to get a fresh look.
[Verizon Samsung Galaxy S III] AyUaxe:
I have been in balanced battery without even thinking about it. Since getting a set up I generally like with cm12.1 and dkp, I stopped looking at those settings. I doubt the mode or profile setting means much, when we're tweaking things as much as we are directly. Just to test, I switched to power saver, and don't notice any significant change yet.
[Verizon Samsung Galaxy S III] bryank29:
Saw this quote elsewhere regarding the S3, they mentioned using Clean Rom but said

I did increase my Read Ahead buffer for both internal and external to 2048kB (from 512). Was worried of setting it too high.
[Verizon Samsung Galaxy S III] AyUaxe:
The clean rom suggestions seem unduly conservative, but perhaps good for them. Mine has been very stable and smooth/quick @ 54mhz, max 1782mhz for months. Played with voltages a little but ultimately went back to what dkp and kernel audiutor defaults (which I believe are slightly under volted) with a vmin 800mV. Don't see why we'd want to forego benefits of these tweaks. As to read ahead, I've never seen a benefit to more than 640kb. Try different values and see how it effects load time for maps and your largest gallery. Deadline is arguably the simplest, most efficient scheduler for fast internal memory. Sio appears to me to be best for external. It's trial and error though and YMMV. Happy weekend to all!
[Verizon Samsung Galaxy S III] bryank29:
Believe it or not....my phone struggles to charge with I/O SIO selected....I don't know why. When I set it to FIOPS, it charges better.

I also have had a few instances where running an app freezes, and I can do nothing, and have to reboot. Is this a case of being too under volted? I was min 384 and max 1242. I changed max to 1350 to see how it does. I was hoping to revert to default because I don't remember my S3 (Verizon) original settings. If I flashed the CM nightly, which any of these kernel settings be ignored and it would let me see what my phone's natural settings are? I had read if you are too under volted, it can have the opposite effect and your battery will drain more. I use a ZeroLemon 7000mah battery, and have noticed quick discharges when in the 90-100% range, but when it gets into high 80's...it seems to stabilize and not drop as quick. Charged to 100% last night, within 1 hour with minimal use was at 92%. Left it uncharged over night and it only dropped to 89%, which I was happy about.

I think my phone charges faster on 1350 as well.
[Verizon Samsung Galaxy S III] AyUaxe:
Sounds to me like you're in a correlation=/=causation situation. The scheduler and Max frequency shouldn't effect charging. Your probs sound like there are apps throwing wake locks or unduly ramping up the processor. If anyone more knowledgeable could chime in, I think info about how to diagnose such probs could be helpful to many.
[Verizon Samsung Galaxy S III] bryank29:
Yea I am definitely open to other opinions. All I know is, I don't use the phone any differently from 100 to 90, than I do 90 to 90, yet the % drops MUCH slower between 90 and 80.

I installed my stock S3 battery last night (2100mah) and obviously its going to die out quicker than my 7000mah, but noticed that 100-90 correlation as well on the 2100 mah. Once I take off my charger while it's been sitting at 100%, I am to 98% within 10 minutes, 95% within 25-30 minutes, and 90% within the hour. Whereas I might hang at 87% for 10-15 min of continued use.

---------- Post added at 10:57 PM ---------- Previous post was at 10:46 PM ----------

All I know is...the charging when my kernel was set to DKP / Freelunch and the I/O was set to SIO, my phone was charging like a turtle...raising 1% every 5-10 minutes. Since switching to Zen (internal) and FIOPS (external) , I simply see my phone charging faster.

Now is it possible something was in the nightly builds that affected this? I don't know. Is it possible there is anything in the OS or nightly builds causing that 100 to 90% discharge so rapidly? t first I thought it was just the 7000mah battery having a bad sector or something, but it dropped fast on my stock 2100 mah as well.
[Verizon Samsung Galaxy S III] ZipAddict:
Check your charging voltage using an app first. Also It could be that current kernel settings have such high cpu usage that its affecting charge. I look at my cpu usage with trickstermod. But could be charger wire or some other weird coincidence.

4 min and 21 seconds after reboot still probably involved some boot processes and usually cpu freq will be at highest then so thats normal and not telling you anything. You are just using a couple frequencies at boot and as time goes on u will use the others.

Wait...maybe i misunderstood your question... How is your max setting 1242 but its going up to 1512?

Yes to balanced mode. Forget about all the app stats when you use greenify. You cant help the power they use when you need them. But when you are not using them hibernate them! Also use built in advanced settings on privacy guard or install amplify to save more battrry by limiting wakelocks, alarms, auto starts, etc.

Download stability test app to check stability. It could be that. If you flash a new nightly then you have to reflash kernel too if you want same kernel settings as now otherwise it installs new nightly kernel instead. The battery drain you speak of is explained in this xda thread...

http://xdaforums.com/showthread.php?t=871051