yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Just question. I tried several variations of Kitkat ROMs, all except slimkat have problem with Camera.

When I go to video mode, record small clip and try to go back to Camera. it just hangs. Only way to get camera back working, is by rebooting

Is it known, or any fix available ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It doesn't?? I'm pretty sure when I used BMS with thalamus hotplug it did. I might wrong though.

As for spc...

http://review.cyanogenmod.org/#/c/55625/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LiquidT:
Hey Man.

That looks pretty good on the battery life. As of now if I'm running 3.5 hours my battery life would be at like 40%. Would you share any settings "CPU or anything" so I try setting mine at that setting for better battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Check his signature, and take into account his phone is not connected 24/7 anymore. Things such as sync every 2 hours are applied to keep battery in his case, and that changes quite a lot in the long term.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This is the same hotplug that BMS uses. All kernels on here used auto_hotplug after I switched from our own MP-decision. (minus leankernel).

I know about them disabling it, but it could be a great battery life saver.

I've spent over 7 hours on this next kernel update in the last day alone. There are a LOT of things in here that should fix tons of bugs, battery life issues, speed issues, and GPU issues. Check my github for all that information and more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
core 1 goes offline for me but it comes back on every few seconds (with screen on and a live wallpaper enabled). <--no brainer I guess...

I always run with Multicore power savings set to 0.

When I hit 80% battery at 1 day 12 hours on 3.25 it was with a normal photo background. Making my background a normal stock jpeg allows core1 to stay offline now right up until screen time out or I touch the screen.

I guess my live wallpaper (wave) sucks up a lot more battery than I thought but gpu is still compensating for core 1 being offline I think.

Bare minimum on everything. You can see my voltages etc as mentioned by polobunny. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes I'm aware about it. thalamus made some great work on the Nexus S (used to own one) before ragequitting. Great dev nonetheless.

Also aware about SPC. The d2 suffers from a lot of little annoying issues regarding cpu hotplugging as well as switching different power states. Not sure if it's d2 specific or MSM8960 related though. Guess if I was curious enough I could go and give a look at the few moto phones and sony's that use one. :p

One thing is certain though, mp-decision is a pain in the butt to deal with IMHO, bit of a constraint to running your own settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I had the same thing occur with SlimKat. If it's turning off LTE, try adding LTE to quick settings and turning it on there. You may find that it stays on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah I know about that too, it's sad.

The variation of CPU's have SPC failing to come back alive after collapse. That's what causes the reboots.

You didn't like the old in kernel MP-Decision we used to use? I'm still wondering if there's a way to get both hotplugging methods into the kernel...

Ok got a kernel out and I'm running it through the usual paces. I'll also be testing a kernel with BOTH auto_hotplug and in kernel mpdecision as well. If it works then that will be the version released
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
So Pwn,

I am trying to formulate a pros and cons for MP-decision vs your newer hotplugging.

What i understand so far is that the old mp was causing too many reboots while it was better on battery. The new hotplug method is more stable but worse on battery.

Is that right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I noticed my camera was using battery. I used it once yesterday. I have never seen it appear in the list of items using the battery before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah thanks for the details.

It's not that I didn't like it, but could you actually ever get cpu1 governor to change and stick?

From all my testing, it seems it would always get brought pack to userspace/ondemand (was it interactive when off, I don't recall exactly TBH, maybe it was).

So anything that played with cpu1 at boot would get messed with upon screen off, the only ways being to modify mpdecision files, disable it completely or custom built power.msm8960.so I believe.

Disabling it completely also breaks hotplugging, modifying mpdecision or powerhal is a PITA.

That said, mpdecision works and works really well. I think it does a better job at hotplugging than others such as thalamus/franco's/faux. It also manages the GPU if I'm not mistaken with thermald. So yeah our homeboys at Qualcomm did a pretty decent job coding that thing, no matter what people think. It's just annoying to deal with if you want to change anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
You're mixing up in kernel mpdecision with qualcomm mpdecision :) It's disabled essentially completely in the new kernel.

I seemed to have found a way to get these to coexist with eachother. It seems to work pretty well so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm not sure what you mean by "in the new kernel". If you mean in the thalamus auto-hotplug one, then yeah it is, but in the past it wasn't (was it?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yes it was :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Oh interesting then. :) I might go from TW4.3 to CM11 if/when bluetooth and camera issues keep coming back and forth, so I'll look up the rom and the kernel soon enough hehe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This version now includes both auto_hotplug and In Kernel MP-Decision. In Kernel is set as default, you can DISABLE it by going to the menu in trickster and turning it off. This will enable auto_hotplug again. It's fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Blaze420916:
Can I flash new kernel with 3.2? Or is it for 3.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Thanks for the new kernel, Pwn. I'm gonna keep an eye on the thread for a day or two before I install it, just to see how well it goes down first. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Sorry to be a bother, but just to clarify, switching off MP Decision turns on auto_hotplug, and keeping on MP Decision disables auto_hotplug? Just wanted to be sure before I do anything :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yes. But only the mpdecision next to sound and led setting in trickster
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Okay then, thanks for this update, hopefully this helps with the GPU gov quirk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Just installed the new kernel and am experiencing a huge improvement in smoothness. Good job pwn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Feels great, cpu/gpu working as they should. Just disabled MP-Decision I always have since 2.3

gpu idle is niceee

Edit: question asked already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Thank you so much! Flashing soon! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bonnatron:
Never left lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'm talking about the MP-Decision that is underneath the gpu settings, not the switch at the top.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Also just realized you commented on the SPC issues in December. Guess you really did see it hahaha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Thanks for the update!!

For some reason, all my MPU voltages are now set to 1150. Could anyone please share the stock voltages?

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
Same here. Adding LTE to quick settings and toggling it there doesn't seem to work either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
That's what I was aiming for. Glad you can notice how fast everything is now. It's essentially optimized for speed at the highest level, barring -O4 optimizations. It was a pain finding out what worked and what didn't.

If you had better luck with auto_hotplug make sure you disable the in kernel mp-decision!

LOL

Yes I did I've been following that issue for a while. I love anything that can save battery while still keeping the speed I love :)

You can go check in the leankernel thread and it'll be there. If anyone else gets this issue I'll push out an update that will hopefully work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Blaze420916:
You can go check in the leankernel thread and it'll be there. If anyone else gets this issue I'll push out an update that will hopefully work.[/QUOTE]

Mine did the same thing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Agreed. Rock solid SPC would be great.

Enjoy the beer anyway :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sirdizzle415:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Just wondering..

Does the MP-Decision under "Force Fast Charge" need to be disabled along with the MP-Decision under "LED Control"? What about "scroff_single_core"?

Thanks again for your work. I think this rom is the main reason why I have kept my GS3 til now..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Blaze420916:
The issue with the mpu voltages I can't find anything over in the lean kernel thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
I think you may be refering to the voltages on page 93. Correct me if im wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'll adjust the voltage issue in a little while. Ugh.

READ THE THREAD FOR ANY MPDECISION QUESTIONS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Pretty sure I may have seem this in this very thread, but I'll throw it out again just in case.

By recommendation, I downloaded Snap Camera from the play store. I went ahead and paid the whopping $1.99 for the full version. I think it does a fine job and is much more customizable than stock CM app. No issues so far. Just FYI. :):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ffwd4490:
I know this is not very helpful except to inform but, I installed the new kernel on top of 3.3 and now when I plug in the phone to charge (usb to pc cable) it locks up to the point where a battery pull is required. I have already clean wiped and am now booting into a fresh 3.3 install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Hmm... i'll have to try that tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
And that is why I wait a little while before flashing anything new. ;) :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
quick charge on? you wiped cache and dalvik after kernel install?

Can't hurt to try.. Just raise the voltages if its buggy. Here's stock voltages if you want and just tweak till you find the sweet spot, this has always been the method of over/underclocking etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ffwd4490:
I'd say yes to clearing cache, as it's something I always do. As far as the quick charge, if it was a default setting then yes as I don't tweak anything ever. If not then no....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I mean I'm pretty sure most of are on the same version, but I haven't noticed anything like that with ANY of the tests I've had out!

I'll adjust it to how it should be. It'll take literally one minute. It'll replace the old 2.12 links, no changelog, no new update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Sorry just listing info for people. I have not changed my voltages since January (finally found the sweet spot lol) yes 700mV at lowest! I save the profile and load it up with every new kernel install, trickster aided since 2012!

Edit: the new kernel is GREAT!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
installed the latest quantum goodness clean, super user, vol blaster, gapps

set up, installed the dialer ran it for a bit and backed it up. rebooted, enabled ART and it is stuck on the boot logo.

any thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Hate to ask what might be a stupid question.... but how will we know when it's been changed/updated? Gonna make a post or are should we be able to tell some other way? :):D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No ART on this version. GCC 4.8 broke it so it'll be fixed in the update I post tomorrow!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheToiletSpaula:
What happened? Hmm...

I flashed 3.3 from 3.27, as well as the kernel and a new boatloader in the correct order and now my SIM card is not being detected, even on the 3.27 ROM.

Anyone know what may have happened?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
thanks. guess I was just a little over zealous. Gave me some serious time to enjoy he new boot image. LMAO
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Only one other person mentioned it here, I guess people stopped using ART. I have as Dalvik is still so very buttery smooth now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Personally, I'm staying far away from ART until it's actually ready for prime time. As it stands right now, it's just way too far out on the bleeding edge for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
You should check the last few pages. Quite a few people have been asking about ART. Fix ART and I'm sure people will start using it again.. otherwise we don't have much of a choice, do we?

And ART has been rock solid for me... Haven't had any compatibility issues either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] |flyte|:
I had to update my modem to match boot loader to get my SIM to recognize
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Regardless ART is still a WIP and it's the last feature I have on my list to get working. Now that I have everything on the kernel sorted out I can update the ROM, which I've already fixed ART for. It's just waiting for a good old fashioned update.

Battery life has been MUCH better for me on auto_hotplug now than it ever was before. Can anyone agree or disagree?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Surprisingly with MP Decision off in both spots in Trickster, standby has been not as good as with before :( For the moment, I'm probably going to go back to 3.3's stock kernel until a future update is made and is tested further. From what I've seen, everyone else seems to love the kernel, so just keep up the good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Check your wi-fi. My internet at my school causes my phone to keep a wakelock unless I connect to the right network. Just my 2 cents, battery has been incredible for me so far and I'm draining 3.9% after 2.5 hours at 90% with 25 minutes of screen on!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Oh! Thanks. :facepalm: I'm an idiot :eek: I was looking at the previous pages and checked Trickster and turns out all voltages were set to 1150, which explains the drain. Thanks though, its a good thing to keep in mind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
I was using ART, just for kicks, a couple of versions ago... maybe 3.2? It seemed fine and nothing I did caused any problems (I opened every app I could on the phone and all worked fine). Phone ran great with either art or dalvik but I have no benchmarks to prove anything. Only wierdness is the inital 15 minute boot time - which doesn't happen unless you do something like wipe dalvik in twrp / TiBu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Like I said I'll either fix that in the morning or when the next update comes out. It's only one line of code that has to be changed.

In Kernel MP-Decision seems to give me much better standby as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Thanks for all this overtime! I reverted to 2.8 for now, but now I'm worried about hardware damage after being at these voltages for about 3 hours :( I hope I'm just uninformed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Your voltage was fine, it's literally the same exact voltage table that CM uses :) It's just not reading your tables correctly and setting 1150 mV as your minimum. Unless your phone was severely undervolted then you shouldn't worry!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I will be traveling abroad (next 3 weeks), and I would like to use my S3 over there. Looking for solid/stable ROM to use during the trip.

Need better battery/no FC/ fully working camera. Any recommendations ? Noticed all KitKat ROMS have camera issue except slimkat (freezes, when i switch from camcorder to camera)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Phew, that's good to know, my phone got pretty hot which worried me a little, but since it was 1150 across the board, undervolt is not a concern. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
Honestly if you want a near-guaranteed 0 problem you'd probably want to just go back to stock or try CM on 4.3. No matter how "stable" we say these recent Kitkat builds are they do manage to have the occasionally random reboot or freeze or camera hiccup that could be problematic on a long trip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Thx for ur reply. Unfortunately, both the suggestions wont help me.

I upgraded to MJB bootloader, so cant go back to stock.

As I also was thinking CM4.3, I flashed it this morning, and it seemed ok so far. just last hr or so, it is FC'ing on camera 'Unfortuantely Gallery closed' :)

Last week, I was on dandroid 5.4 for 2-3 days, absolutely no issue, Camera/battery rock solid (Infact, I got 4 hrs screen time in one charge)

Only reason, i constantly keep away from TW ROM, their fonts/appearance and some of swipe features (like on phone in CM to switch between dialer/contacts missing) otherwise, it is great ROM

Any recommendation of balance of both worlds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Go back to STOCK 4.3. You can go back. Just don't use Odin or go back to 4.1.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I am currently on CM 4.3 stable (Feb 4th buiild)

From here, how do i go back to Stock 4.3 without Odin. link/details plz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's 2 AM and I have class in a few hours. Go into the other forum and look around!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmcneil:
http://xdaforums.com/showthread.php?t=2363882

[ROM/RESTORE] [AT&T/ROGERS/TELUS/BELL]Return to UNROOTED STOCK WITH FLASH COUNT RESET
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cehf:
from the beginning of that thread:

the person is already on a 4.3 bootloader. even though it looks like the person has the leaked bootloader rather than the OTA one (I'm not too sure which is which), no one in the thread has responded to inquiries about using this with the leaked bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
He says he's on the MJB boot loader, which is the official one so he definitely has to be careful about messing with that. That being said, I think he should be able to go here: http://xdaforums.com/showthread.php?t=2498233

Download just the ROM. DON'T MESS WITH THE BOOTLOADERS! That SHOULD work fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
So far, 3.3 with 2.12 kernel is great. Smith and quick. The weird LTE issue seems to be something other CM based kitkat derivatives have, but I was able to get the right seeing to stick on others. Also, camera force closed on me last night. Overall, though, Bluetooth is very important to me and that is working great. Thank you for the hard work you've put in to this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LiquidT:
Ok. Last night I updated 3.3 to the latest kernel build 2/12. I did enable the auto-hotplug, “not sure what it is or what it does” but enabled it anyway. Charged my phone to 100% and set it down for the night “not plugged in”. Looked at it this morning and battery was at 43% from just setting all night, just a little over 7 hours of idle time. I’m using JuiceDefender Ultimate enabled with profile on balanced. I’m also using Android Tweaker Pro enabled with auto Tweaker set on battery saver.

The question is: :confused:

Do I need to use apps like JuiceDefender & Android Tweaker?

What is auto-hotplug & what does it do?

Can I get better battery life than this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Like everyone said - read, don't mess around. You're flashing roms, no time to screw around, and if you're asking those questions, you need to proceed fearfully. Go to Dandroid if you liked it - it's stable and has the TW camera and you should be safe flashing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't use those sort of apps. They're usually more a burden than anything else in my opinion.

Your battery could be much better. You have something most likely holding a wakelock that shouldn't be. In idle I usually lose around 1% per hour with everything enabled (sync, wifi etc but obviously no screen on time).

I would use BetterBatteyStats to find the issue, you can post a BBS log if you're unsure how to analyze what you see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
I was curious, I use the free version of Trickster Mod, what does LED control do? Hoping there is way to make the LED brighter as it seems a bit dim on this rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Yay! Finally got 10 posts on the forum, so I can post here ;) Sorry for my English, it's not my primary language

With the 3.3 release, battery life is not bad at all so far for me. Maybe a tad less impressive than what I got with 3.27 but really nothing to complain about.

Every morning I go to work and I listen to the same 128kpbps TuneIn feed (4G/LTE, some areas on 3G) in my car with Bluetooth paired, for exactly one hour.

With the 3.27 release + old Kernel MP-Decision + ART runtime + Deadline/Intellidemand, I would usually arrive at work with ~85-86% battery left (Screen off during all the trip).

This morning, with 3.3 + Auto-Hotplug + Dalvik + Deadline/Intellidemand, I had 82% battery left. Not a big deal.

I'm very pleased with 3.3 + 2/12 so far and I'm impressed by how smooth everything is, even with Dalvik. ART was still smoother and faster for me, particularly noticeable when I scrolled heavy web pages and in Falcon Pro, and I got to admit I miss it, but I've never been more happy with a Custom Rom before I used Quantum.

Thanks a lot Pwn for your hard work. Honestly you're probably the reason why I still use my good old GS3 and decided to not buy a Nexus 5. The GS3 flies with Quantum!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Ever since I installed the latest kernel, my phone has been lagging. Clean wiped, installed again and still slow. It's almost unusable.

Anyone else experiencing the same? I'm on 3.3 with latest kernel and 2/7/14 PA gapps.

Edit: nvmd. Disabling both MP-Decision fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
Hey Pwn any chance you could integrate Active Displays?