yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
So I'd go in and disable data over mobile network right? And I can still receive calls and SMS and MMS? Just I'd need to use WiFi for anything more than that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Your really clogging this thread up with basic cell phone knowledge questions. I'm scared that your even flashing kernels if your this green.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
I'm on miui right now giving it a try and there's is all weird to me the menus are totally different from tasks rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is a kernel development thread. Please take all your questions that are unrelated to this kernels development to a more appropriate thread. *hint* Q & A or the General section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Oh. Poop. I'm on aokp most recent and I lose all semblance of stability if I UV really at all, which super sucks. I thought I had it good this am, but apparently it freaked out Tasker and made it wake lock the phone for 2 hours. The only stable setting that doesn't absolutely drink battery for me is sio / pegasus or abyss. Any other governor or scheduler drinks me down and any uv beyond about 25 shuts me down. Fail is me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
Hey there... I got the AOKP you and Task put together ... it's fantastic. I am really enjoying and going to stick with it for a while, however every time I try to get your kernel flashed over, it doesn't boot. Boot loops Samsung logo and then flashes to black, i've triple checked everything, all the right files (10/16 rom and kernel) and procedures I can come up with... any idea? It's great right now but I would like to try the complete package.

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
As long as you have done a full wipe and let the ROM fully boot once before flashing my kernel there is not much you can do. Some phones just dont agree with it due to every phone being so radically different. Ill post more if i can think of something, but nothing is coming to mind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
yea, I let it reboot. setup a few things, got accounts synced, rebooted to make sure everything sticks and then rebooted into recovery to perform the kernel flash. Is there a kernel cleaning script or something maybe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, if you search this thread though, there is a SUPER wipe version that some have got it working with. Its got something like 15 steps and it has worked for many, or maybe someone will see this post and have the steps. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
don't forget to wipre cache + wipe dalvik + fix permissions AFTER you flashed the kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Post #2 http://xdaforums.com/showthread.php?t=1781242
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
thanks!! Will try and report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
swipe2wake

Wooooooohoooooooo, Looks like I finally got swipe2wake working :highfive: :good:. Its really only good for while your plugged in since it has to maintain a wakelock but is neat if your sitting around plugged in :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
sweet..great work dude:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
One last thing I have all mobile data disabled and still shows 100% use age under battery stats.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its all going to be you fault soon. ;) :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phat_cow:
I must have done something to mess up my wifi and bluetooth drivers because both of them are not working. I tried flashing back to stock with root with no success. Also tried flashing back to stock with no root using odin and that didn't work either.

Anyone have any suggestions at all before I send this phone in for repair?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Check the OP (right at the top - the part about wifi and bluetooth drivers) - did you flash as recommended to get the drivers back?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Reflash the kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phat_cow:
Yes, I flashed back to stock then flashed the kernel he provided. Sounds like a hardware issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Two options (well, three, but returning should be last resort :)) - tell us what you flashed, in what order (i.e. ROMs, kernels, Odins, anything odd) and we could try to figure it out - or zap the phone down to zero (copy everything off and format completely), and Odin or ADB push back to completely stock. If that doesn't work, then take that and flash up to Task's ROM (the cleanest I'm aware of), no other kernel, and see if THAT works. After that, you're down to option 3 :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phat_cow:
OK So this is what I did:

1. boot to recovery

2. Wipe Data \ Factory Reset\Wipe Cache\Wipe Dalvik Cache

-Mounts and Storage => format /system

-Mounts and Storage => format /data

-Mounts and Storage => format /cache

3. Reboot to recovery

4. Wipe Data \ Factory Reset\Wipe Cache\Wipe Dalvik Cache

5. Mounts and Storage => Mount /system

6. Flash ROM

7. Flash Gapps

8. Advanced => Fix Permissions

Reboot system

And it did not work :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Yep - and that's not what I said - pull the external card and format the internal card, then push a clean recovery image and start over. I would do this with caution, since I've never had to go that far - I'd do some looking around (i.e. the stickies for "returning to stock") and make sure I'm not sending you down a bad path. Or just flash back to stock and return it if you're not comfortable digging that deep...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
I think like you mentioned about completely formatting the internal card and using Odin to go back to stock is the best option.

I highly disagree with people returning their phones to Samsung for warranty because they messed up their phone flashing stuff though. This practice is a large reason why the phones are be coming more expensive and the warranty process for legitimate claims is so horrendous.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Ok, so after 2 days of rather exhaustive testing, I appear to have finally found settings that work for me, so I thought I'd share. This handset does NOT appear to like undervolting or overclocking, although all it appears to on OC is rapidly overheat. Any UV on OC steps prompts an immediate reboot.

I am on pegasususq and sio, stock settings for both. All other scheduler and governor combinations drink battery at a rate of 5-10%/hour.

Screen off frequency at 96, touch boosters at default, vibration at 80 but I'm considering 60.

I spent hours and hours testing UV settings, and have settled on a meager - 25mv on each step. This was the only way I stayed stable.

As of right now, I'm at 76 percent battery on relatively heavy use over weak signal, which always drinks extra juice. Time since unplug is right at 7.5 hours. Idle consumption appears to be about 1.5%/hour.

Gps stays on always, wifi on when I remember it when I'm home. I also use something like 12 Tasker profiles, including one that runs sync every 30 minutes and one that shuts off BT after 3 minutes of no connection. Mobile data stays on 100 percent of the time. I don't let anything other than the messaging app and Gmail push notifications because they bother me. (Ok, and alarms and reminders, but those don't count.)

Totally random question... Is anyone able to rip the default "whistle" notification sound from a stock s3 for me? I hate all the s3 on board tones and haven't had time to make new ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lokesh1699:
http://www.mediafire.com/?o7tc5p6q4vqez1z..this one has all the media ripped from stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
It's also available on zedge(check play store)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phat_cow:
So, I removed my memory card, booted to recovery and formarted /sdcard and wiped everything. restarted in download mode and used Odin to install stock firmware without root.

Here's what I found out. Wifi works and everything...BUT the weird thing is if I turn bluetooth on. It screws up my wifi. Wifi won't turn back on unless I restart the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Well you're getting closer! Do it again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You may think he's kidding, but he's not...it really could help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
I'm not trying to be a **** here, but this is kinda getting off topic of ktoonsez kernel. Regardless I hope you get it worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Wurd

---------- Post added at 01:24 AM ---------- Previous post was at 01:20 AM ----------

Its crazy to hear all the things people have done and they can't understand why they are not getting their desired results
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Update

New governors added for next release:

Sleepy and

wheatley :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
QFT. The amount of people in this thread completely uneducated about undervolting is mind blowing.

Under almost all circumstances the voltage should be left as-is. You probably shouldn't be undervolting. The maximum amount of battery that can be saved is 2%. Which even then is if you undergo extreme undervolting, which can often lead to an unstable system completely negating the point of doing it to save battery since one random reboot uses much more power than you'd save.

Please, people, for your own good educate yourself on the actual benefits and myths of undervolting. I recommend anybody consult the undervolting link in my signature if anything I've said in this post sounds strange or new to you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
I know this might be a stupid question, but how do we update so we can try the new governor? I'm already on the most recent kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, just a little. You can test it when I release :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
It better be better than ktoonservative! I've just gotten to the point where I understand 2/3 of the ktoonservative tweaks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Just saw your edit :p. Now it makes way more sense.

Really looking forward to it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL. Too new to tell so Im not sure yet and I added 1 move called wheatley :good: :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Hate to sound like a fanboi, but you've been with me through 5 roms... At this point I trust you man. Although I have a lot of questions, expect a PM this week :)

Its all operator noobiness, nothing to do with your kernel, I just can't find the data I need no matter what I search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yotorogo:
I flashed the touchwiz JB kerenel, wiped cache, dalvik, and fixed permissions. I'm currently running the frosty JB rom. The problem is that whenever I try to open ktweaker it vibrates and after like 5 seconds it closes.should I try reflashing the kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
So agreed. In most cases pushing a cpu beyond its set speed requires higher voltages. I've overclocked everything for years and usually upping voltage is needed to be stable but that can cause cpu damage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Question about kernels for TW JB.

I want to test a tw jb on one of (my 3) Galaxy S3's but as with all my rom's I gotta use Kt's kernels.

I saw the note that states none of them work on the LI7 leaks or greater but im not sure for which roms that applies.

I installed DrewGaren's JellyBean 747 Milestone 6 Firefly (Liberate) Edition but after installing the latest Kt kernel for it the boot up shows black kernel screen but oddly still has sound and even appears to boot with sound but no video...so either wrong or incompatible kernel?

Is this an incompatible rom? If so what tw jb roms are suggested I could test that u know Kt's kernel will work?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Wouldn't that be a good question to ask in the ROM thread? Not about the kernel, just read the OP and search the thread, and if nothing shows up, ask if it's based on LI7 or greater leak.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I agree with your point but you can save a hell of a lot more than 2% by undervolting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
So I was wondering what the theory behind the feature for setting the max mhz while the screen is off. Does keeping it at a low step provide better battery life, or does a higher step work better seeing as it would complete tasks quicker? I currently have mine set to 384mhz @ 850mV, however if you guys tell me lower is better then I will set it to 192mhz which is my min and @ 825mV. I have seen some people post they have it set around 1134mhz, so I'm kinda confused.

I'm currently losing about 1%/hr which isn't terrible, but on previous releases I've seen as low as 5% over a 10 hour period, so now I'm trying to tweak and learn how this stuff works as I've never had to tweak anything before it's always been spot on ;)

Sent from my Tablet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
There are lots of variable that go into the decision to UC while the screen off. I choose 486. Most governors over-react to load to get a smooth user experience. While the screen is off, you dont care about it cus you are not using it. After stating that, people can say, then it will take longer to finish the task, yes that is true, but you might have consumed more power while executing a simple task like recieving an email of 2 sentences or a text that says LOL. It is all a balance and how you use your phone, for some it will workgood and for others it will not, its all takes experimenting :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
That's what I'm learning. I haven't even gotten to messing with governor settings yet, I'm slowly trying to figure out how different UV configurations affect my phone. Ktweaker is a nice app for beginners as its not too overwhelming like extweaks was for siyah on the s2 sooo many options I just looked for the governor and io scheduler and ignored the rest lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya, I just gave them a huuuuuuuuuuuuge update a few days ago on the S2, its got like 400 options in it now, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Yep, I'm still gonne do it though... We can all monitor relative draw with a couple flat probes and a 10$ radio Shack multimeter if we wanted as well. It's not really the point. Unless you're into that and want to do it as part of YOUR adventures with the kernel. I've never gone long enough between flashes to quantify a real-world improvement, and didn't care enough to meter out the draw.

It's my phone, I'm not hurting anything. Even if I was, it's still my phone. I can set it on fire and dance naked around it (in the privacy of my own home, of course) if I want. Since that would be fairly destructive, I opted for tinkering with UV. If I get 2% or half a percent battery, then cool. If I lose battery life, not so cool, but I'm still having fun tinkering with it.

That's the lovely thing about sandboxes, we get to build what we want, how we want, when we want.

A huge chunk of the FUN in this thread is comparing notes, tweaking the kernel and seeing how far we can take it. Unless I missed something, that's a huge part of "the point" of this kernel. Otherwise we would just run the stock kernel.

Please don't tell us what we SHOULD do with our devices, if I wanted that I would have bought an iPhone and let Apple dictate my choices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
No, you can't. The post in my signature goes through all the math. If you have other math that proves otherwise I'd definitely be interested in seeing it, but it's common sense really.

Considering lowering the voltage doesn't affect deep sleep, screen or radio drain, and you're lowering the voltage levels by ~5% (or less) for most frequencies, without even going over the numbers in depth, it's just not possible.

Again, though, read the post linked for yourself, don't just take my word for it. I'm also not associated with the author in any way, I'm just tired of seeing people arbitrarily lowering their frequencies and reporting issues without any knowledge of what they're doing or understanding of the real gains from their changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
will the aosp kernel work with rootbox? glad to see you here ktoonsez!! also noticed some others here from s2 att threads. glad to see you guys here. going to pick up my s3 in couple hours and wanting to prepare my rom and kernel for flashing!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
I'd also point out that several people in this thread have reported a stable UV as high as 20% in the lower frequencies (925mv down to 740mv) and apparently higher in the upper frequencies. In this instance when I say "stable" I'm implying that they are reporting no reboots or app issues, since I have no knowledge of the scope of their stability tests. I believe it was Quazimodem that was apparently running stabilitytest on each freq though. However, if it's holding up under daily use and everything functions properly... I call that a win.

So while the study itself is certainly valid, if unnecessarily complicated, it isn't factoring in variables from device to device, kernel to kernel, user to user, or governor applications. Simply observing that the assumption of a max uv of 5% is now skewed in some instances by a factor of 4; makes the assumption of a max battery savings of 2% fairly arbitrary.

At this point though, my interest in the study somewhat wanes; since to update the math for the results obtained by users in this thread, we'd have to go through and rework all of the original equations with updated information.

In short, while I totally agree that the net effect is not going to be what some people are hoping for, the gains you are projecting are also a bit pessimistic in several cases. And frankly if I can get 1% improvement and have this much fun doing it, I'll take it. I'd take the fun even if I got no gains at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Hey ktoonsez good to see you here!! Trading my s2 shortly for s3. Will the aosp kernel work for rootbox 2.9? Does the kernel need new mali drivers like the s2 did?

JB 4.1.2 Rootbox Nightlies

Ktuned Siyah kernel Sooo Smoooose

I777 SGS2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Again, that's for the lower frequencies, but that said, the post itself never states that the reduced UV frequency is 5%, it's as "extreme" as stability allows, which I assume is 20% (or close) edit: The spreadsheet has tests reducing the lower frequencies from 950 to 750 (21%). I just used 5% as an example, since I was factoring in the higher frequencies too. I just re-read the post and the author equates the frequency differences to real-world mA savings, which can then be calculated to estimate total battery savings under a variety of screen/radio conditions.

You're right though in that it depends on the device, and the math from users in this thread. But that's my point, really, in that no math is being done, no real tests are being done, people are seemingly posting frequency levels without any quantifiable proof or accurately measured power savings.

What it boils down to is that because there's proof of real world savings, it gets concerning (as somebody who values facts & real information) when people are posting about issues they're having with their changed frequencies. People are always going to do this, because placebos combined with ignorance is a very powerful thing. I just think it's good to show that there is math out there to show that the common thought of

undervolting=huge battery savings

is a myth and that it doesn't hurt to educate yourself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Good to see you here too. Dont know anything about rootbox. Use mine and tasks AOKP, best out there :D :good: :highfive: :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
My guess would be that unless people are as interested in the math as you are, they're not going to do it. Frankly I don't care enough to take the otterbox off my phone to measure drain.

The people reporting issues after they apply someone else's voltage table will probably always do so.

On my device, as long as I'm not running OC, my upper frequencies are actually more tolerant to UV than the sub-stock ultra low frequencies.

I latched on to your statement of 5%, because "extreme" is purely subjective, and in most cases with the current iteration of this kernel, 5% is a great place to start. In fact I don't think I've seen anyone mention since before September that they had to increase voltage to get the kernel to work. KT has her pretty dialed. My device will actually tolerate a - 22% UV at sub stock frequencies and higher on stock frequencies. However I like it to run indefinitely on scaling tests so I don't push it that hard.

Imo, demonstration of the math, as it pertains to this kernel, with a specific governor would have been awesome.

Telling us we shouldn't UV, then promoting another thread... Not so much.

Just flash the kernel, start tweaking and join the fun dude. At the end of the day, who really gives a damn, right? It's all about the fun, if I just wanted to rock it stock I wouldn't be running an android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fizzer82:
I read through the link and the study, lots of horrible assumptions so it is no way a proof that under voting isn't worth it. True it won't help you're idle time much, and it won't help a lot of you're running around at max brightness. But that's not why most under volt... It's to get more usage time and to aid that, many run min brightness and dark colors.

Making a blanket statement that the best you'll get is 2% is quite misleading. I've gotten better than 20% more screen on time through mild stable undervolting.

P=CV^2f is the math you're missing. Voltage affects cpu power consumption exponentially. There's no doubt in my mind that undervolting has benefits. If it were such a minor effect, why would scaling CPUs adjust voltage at all?

Stock voltages are set so there's about a zero percent chance of voltage-related errors across all batches of processors. Not all CPUs come out of the fab equal, so stock settings are a lowest common demoninator - there's tons of safety margin. Lots of people can make significant gains purely on the luck of the draw.

It's the same reason a tuning shop can reprogram the ecu in your car for more power. They lower the safety margin based on the type of gas you want to use, your particular engine's characteristics, altitude range you'll be driving in, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
I knew I'd seen that equation before in this thread but I couldn't find it to save my life, thanks man, well stated