yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] hayzooos:
Agree 100%. I ran the new TW kernel for a day or two after giving it a chance realized battery just wasn't the same. Flashed back to 10/31 last night and already noticed an improvement today.

Do you use Google Music at all? The only reason I ask is because there is a known issue with it. From what I've experienced, it'll play about three songs and then it'll stop playing altogether. However, the app still constantly runs in the background and will not let your phone go into Deep Sleep.

I only noticed this specific issue with GMusic last night so the worse battery wasn't a direct result of this, although it would play a more significant role if you weren't aware.

I'm sticking with the 10/31 kernel for the time being.
[Sprint Samsung Galaxy S III] freecharlesmanson:
You know complaining about the battery life when you have no clue what's doing it just proves you did not read the previous post. If you can't diagnose your system to improve battery maybe you should just go back to stock?

---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------

I only use google music. Yet again before smearing the good name of a kernel or application people need to produce proof logcat,time in state, partial wake locks, kernel alarms.

---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------

See op here if he reads back will see two roms are to blame
[Sprint Samsung Galaxy S III] shinesthru:
Maybe take out down a notch.
[Sprint Samsung Galaxy S III] slickdaddy96:
Typical for xda blame the ROM when nothing has changed on the ROM and the only thing that has changed is the kernel. Then I will go into the ROM thread and they will blame the kernel.

I didn't mention the ROM i was using because nothing has changed. I am using Stock TW LJ7 odexed. Nothing custom at all except for this kernel. I am not complaining about battery life, I am trying to get to the bottom of it so it can be fixed. Giving the new kernel 2 days to settle in, I can tell there is a difference with NO change to the ROM at all. I'm not a newb, I know how to troubleshoot my phone. Nothing in logcats or battery stats jump out at me. I was not having the qosmr problems a lot of TW users were having. I was getting 15-18 hours (even more sometimes) with anywhere from 1-6 hours of screen time with the 10/31 kernel. I was just pointing out with nothing else changed I am not getting that anymore. So something in the kernel changed to cause my phone to do this. It is the only logical conclusion.

I know people want to shove things off as someone else's fault or the fact that user is an idiot, but I am not. I am coming here to a kernel thread to ask what changed in the kernel that might have caused the decrease battery life and work with the developer to troubleshoot it. I can post logcats if need be. I will have to reflash the new kernel and let it run for a day or two and then I will post logcats, meanwhile I will capture a logcat of the 10/31 kernel running and compare the two, but just at a glance they didn't look different.
[Sprint Samsung Galaxy S III] jamcar:
Have a link for 10/31?

Generating random authentication keys
[Sprint Samsung Galaxy S III] ktoonsez:
For the ROM type you are talking about, the changes from 10/31 to the newest were:

1. Fix bluetooth minimum typo for when screen is off

2. cpufreq: BLOCK screen off profile MHZ while in a phone call

3. cpufreq: Added down_threshold_hotplug tunable to ktoonservative gov

4. cpufreq: ktoonservative adjustments

Hopefully that helps you. :good:
[Sprint Samsung Galaxy S III] freecharlesmanson:
Ok first off if you are using a more recent rom you should use the newer kernel but actually... ...QOSMGR it's most likely your problem but like I said you should be able to diagnose alittle you empirically have either a CPU scaling issue, radio,application issue it is one or more of those three so... in basic battery stats you either see a radio WiFi, cell, Bluetooth, GPS in use or at a high percentage. Or you have something waking or wake locking, using excessive CPU. Or your time in state shows your scaling is bad. But battery just doesn't disappear unless you had a bizarre issue I doubt a logcat would help
[Sprint Samsung Galaxy S III] slickdaddy96:
Here you go. Ktoonsez if you don't want this old version linked please tell me and I will delete the link.

http://www.mediafire.com/?qokfwsskwtwr8r2
[Sprint Samsung Galaxy S III] ktoonsez:
I dont care. And you guys should read the post I made on the previous page, there really is nothing changed that would effect battery and is probably the qosmgr screwage as freecharlesmanson states below my post.
[Sprint Samsung Galaxy S III] slickdaddy96:
I will play around with qosmgr and see. I am just worried renaming it may cause other unintended issues with the phone/ROM. I have seen a few people state that was a possibility although I take all user reports with a grain of salt because it might have nothing to do with the renaming.

Its just funny to me that one kernel works great and doesn't get qosmgr all worked up so to speak but the other one makes it go crazy. Just a oddity I guess if that is what is causing it.

Thanks Ktoonsez for the kernel though. I am getting battery life that I could have only dreamed of. Keep showing my wife (who wants to keep unrooted and stock) how much battery life I am getting while she is having to plug her phone in on the way home from work, and I think I am close to convincing her to let me have her phone to root and put this kernel on! :D
[Sprint Samsung Galaxy S III] ktoonsez:
Excellent :D. It is awesome when you have 2 phones to test side by side like that to see whos is doing the best :good: :highfive:
[Sprint Samsung Galaxy S III] hayzooos:
I don't have much to add here, but I wanted to quote it for truth. Charlesmason, step back a bit hoss, who crapped in your cereal bowl this morning?

I clearly stated in my post I noticed the battery was worse before I realized something was awry with GMusic. Two separate issues, maybe it was my mistake for posting them in the same post.

And what you would want a logcat of? Me using my phone on and off for 8 hours, usually no more than about five minutes at a time? I'm sure that would be real helpful.

I have never understood what is so wrong with people stating they have issues with a ROM or kernel. If no one posted any issues about anything, we'd still be running Android Cupcake, amirite?

Nothing in the ROM (FreeGS3 JB v1.0.0) changed...nothing. No new apps, no new settings, I still work at the same place and live at the same place. I still have LTE while I'm sitting here at my desk. Nope, the only thing that changed was the kernel. Modem is still the same, literally EVERYTHING. gsiffdaemon and qosmgr both reside in /system/bin, right? Flashing a kernel doesn't touch that does it? I renamed them both while I was on 10/31 the first time, and since nothing else changed, if I look in /system/bin right now, will they still have ".bak" right behind them?

*checking* Yup, both still have .bak at the end.

I'm normally a pretty cool, calm, collected guy, but this is twice in the last 24 hours where someone has jumped on me for stating I was having an issue with something. How can we expect things to get better if we don't state what problems we're experiencing? The other was over in (Heaven forbid) the CM10 thread.

OP, I have a lot of respect for your kernel, I've used both the TW version and the AOSP version and both were fantastic for my phone. I noticed battery life wasn't on par with the 11/13 TW version and I wanted to make it known for a few reasons. One, if it's just me and no one else is having an issue, then it's my problem and I'll provide whatever information I can to see if someone could help me fix it. Secondly, if it's not just me, then there's something not quite right, and I'd like to help in anyway possible so whatever it is can be fixed. Maybe it's just me and slick...maybe it's not, but with responses like Charlesmason gave, they're not going to say boo anyway. Which is a shame, IMO.
[Sprint Samsung Galaxy S III] freecharlesmanson:
It's because sprint /Sammy based source uses qos most likely as a way to report/manage/regulate the client end of the network..... it's not a good thing qosservices are things like packet filtering

Although for a big network it's a god send to regulate with and even throttle troubleshoot but it also let's them have the client end (your phone) tcp stack by the big and hairys

---------- Post added at 03:48 PM ---------- Previous post was at 03:44 PM ----------

Based on fcc regulations it's by a very narrow definition qos is legal to use

Things like throttling or filtering services

Are constantly being fought legally and should be
[Sprint Samsung Galaxy S III] freeza:
For the record, the qosmgr is not related to Quality of Service (networking) but is related to mostly the controlling of the CPU governor MSM-DCVS and a few power related items.

Take a look at "/system/etc/qosmgr_rules.xml" for a bit of information on what the binary qosmgr does. It took a while for me to figure out exactly what this was responsible for, as I once thought it was related to QoS as well.

At any rate, what this has to do with battery drainage for some people is baffling. I can only come to the conclusion that something you're doing is tweaking one of the values related to that XML file.

Hope this helps. I, myself, have had no problems with qosmgr (maybe because I do use the msm-dcvs governor, or because I don't mess with any values related to that XML file).

Good luck getting to the bottom of this, guys!
[Sprint Samsung Galaxy S III] hayzooos:
With the ktoonservative governor, I don't think many people use the MSM-DCVS governor anymore, do they? I think the majority of people who use this kernel use the kt governor as well. Although isn't the MSM-DCVS the default governor for our phones?

Thanks for the insight, always good to know what some of these things do, especially when we're changing the values based on others' recommendations!
[Sprint Samsung Galaxy S III] ktoonsez:
Very interesting, thanks for that info, I have been traveling like crazy and have not had time to verify that it was/wasn't networking QOS. Can someone post up the xml file since I dont have a ROM downloaded on my phone to look at it????

Thanks guys
[Sprint Samsung Galaxy S III] freecharlesmanson:
No see I just want it to stay scientific, it's not any one having a issue that I mind it's people don't maintain factual and useful posting. I didn't say logcat I simply meant that if people need help trouble shooting or think a app is causing issues let's try to make it tangible. And better yet if you actually did have an issue with play music then you would be on a short list of people so. Maybe you'd want to help figure why exactly
[Sprint Samsung Galaxy S III] JAG50:
Realize the frustrations with battery life. But for the record, my battery life has improved significantly with the 13 Nov kernel.. S3, LJ7, no additional mods. Please note that any kernel has a break-in period to settle in and produce results. Photo attached.
[Sprint Samsung Galaxy S III] hayzooos:
I read ya. For the record, that's my favorite battery mod, I dig the white. What ROM are you running now? And I grabbed the pre-11/12 GMusic apk from an older nandroid I had, so I'm not having that problem anymore.

The issue I was having with GMusic was I would play a CD, and it would play through about three tracks then the sound would stop. The app would still be running, and you could see it was pushing out audio based on the animations within the app, but there was no sound. Couldn't skip tracks, stop it, nothing. I would even Force Close it, and the phone wouldn't go into Deep Sleep at all, it would continuously run at the lowest frequency. Eventually a reboot would fix it, but after about three tracks again, the same thing would happen.
[Sprint Samsung Galaxy S III] freecharlesmanson:
I'm running cm10 the theme is black infinitium

---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------

A no dude you have problem. Not sure what's going on but you should get some sort of monitoring app to see what service in system is racking up that usage
[Sprint Samsung Galaxy S III] slickdaddy96:
Is it TW or AOSP you are running?
[Sprint Samsung Galaxy S III] freecharlesmanson:
He is running tw lookslike
[Sprint Samsung Galaxy S III] freeza:
Here it is :)
[Sprint Samsung Galaxy S III] mw86:
Thanks for the info Freeza. I like you dont understand why it happens either. I use AOSP but used Freegs3 (Jb TW) to update prl and my modem etc. I tried the two first kernels Ktoonsez made for that and i did get the qosmgr issue. For those who don't know battery stats or even OS Monitor are apps that can show it. In OS monitor tell it to show system processes like those that start with the com. Name.

Since Freeza it never happened to you what I see is only one core gets pegged from 50-100% usage despite any frequency running. How a simple process can actually use that much is beyond me. So for me it pegged at 2106mhz since thats the max I use.

Its seen on any Jelly Bean Touchwiz rom and paired with a custom kernel (any). No rom or kernel drops 25% battery in less than an hour. Those having extreme battery drain please realize QOSMGR is disguised as Android System as many other processes so you will need to monitor.

Easiest way is just use Develop option in Settings to display "show cpu usage" as qosmgr shows up as that there. All our roms have this option so no additional monitoring apps needed.

I know if i have my screen up just a bit on brightness i definitely can lose as much battery an hour that QOSMGR has been doing.

The issue is not on a specific rom its any Jelly Bean Touchwiz version with a custom kernel like for example Agat and Kt747.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] ktoonsez:
Thanks man, it appears that the binary is probably populating those tunables based on CPU needs. What sucks is that it is doing it unnecessarily since we dont even have that gov selected. I will diggin into the kernel code to see what I can do :good: :highfive:
[Sprint Samsung Galaxy S III] freeza:
Not a problem. Hopefully you don't have to make any changes to the governor. I actually use it a lot lol
[Sprint Samsung Galaxy S III] Compusmurf:
I put qosmgr back into system\bin rebooted, used ktweaker to set ktoonservative, uv -50, no overclock, SIO and I can get the cpu to peg at 100% each time.

This is using the stock JB LJ7 Touchwiz rom with init.d enabled.

Any other combos would it be helpful to try?

I'm going to reset everything to plain stock and try that combo next. Ondemand, CFG, no UV.
[Sprint Samsung Galaxy S III] ktoonsez:
Nothing will be useful, I believe I know the problem and probably will not be able to fix it unless I remove all the manual hotplugging but would kill the uniqueness of my gov and not willing to do. I now think that the qosmgr is a "rider" binary that assists and or drives smp. Those of you that have used the AOSP version of my kernel know that you cant use the "Performance" app in Settings and this is also due to smp.
[Sprint Samsung Galaxy S III] Compusmurf:
Ok, I can't get it to misbehave on ondemand.

So, what's the expert opinion? block the qosmgr app itself?

I've run 2 days without it and no issues that I've been able to detect. :)
[Sprint Samsung Galaxy S III] ktoonsez:
Knowing what we know now thanks to "freeza", it will have no ill effects to remove/rename qosmgr since 99% of the items it is accessing are tunables for the msm governor.

Again, big thanks to freeza for finding out what QOS actually was, awesome find :highfive: :good:
[Sprint Samsung Galaxy S III] Compusmurf:
Awesome. reblocking it and resetting my gov's back to what I like. :)

No sense testing any further. Might want to comment that in your first post for TW users.
[Sprint Samsung Galaxy S III] ktoonsez:
DONE! :good:

OP Updated with this:

***** IMPORTANT *****

If you are using my ktoonservative governor with the Touchwiz JELLYBEAN version, you should rename /system/bin/qosmgr to /system/bin/qosmgr.bak to prevent battery drain
[Sprint Samsung Galaxy S III] freecharlesmanson:
Strange name for a file doing what it does and explains allot about msm gov
[Sprint Samsung Galaxy S III] ktoonsez:
I know, I couldnt even come up with what the letters might stand for
[Sprint Samsung Galaxy S III] hayzooos:
So if someone were to use the MSM gov, would it not work at all if we don't rename the qosmgr back to normal? Or would there be no battery drain only with that governor?

Not really important as I have zero intention on using that governor, but just curious I guess.
[Sprint Samsung Galaxy S III] ktoonsez:
I do not have the source for the qosmgr binary so I don't know for sure. My guess is that the MSM gov would be less optimized as intended by qcom. With qosmgr disabled, no battery drain should be present no matter what the governor.
[Sprint Samsung Galaxy S III] r.suchil2:
Every time I use this kernel I only experience one small glitch. When I'm scrolling and using the ktoonservative governor I occasionally experience a little resistance... if that make sense. Like I would be scrolling down but all of a sudden my phone seems to want to scroll upward..even when I know I've scrolled down. Same thing for opening up the multitasking menu. When I swipe to end something in the background, sometimes it shows I swipe the opposite way I swiped..does all this make sense or do I sound insane haha
[Sprint Samsung Galaxy S III] freecharlesmanson:
I have that happen but it's probably not the governor for it to go up instead of down it seems to be a input malfunction
[Sprint Samsung Galaxy S III] r.suchil2:
It only happens when I use the ktoonservative governor
[Sprint Samsung Galaxy S III] galaxys3man30:
After you rename it u have to reboot right?

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] Xalky:
Yes, you probably should, just in case it's already in process. Rebooting will shut it down.
[Sprint Samsung Galaxy S III] mw86:
Okay maybe its just simply Qualcomm Operating System Manager QOSMGR? No matter its solved. Nice work Freeza! Maybe Qualcomm Operating Scale Manager. Haha who knows.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
It's possible to lag but I'm not gonna even try to argue how flawed the logic is that a governor makes your scrolling reverse
[Sprint Samsung Galaxy S III] r.suchil2:
I was just saying it only happens when I use the ktoonservative governor. I never said the governor was the cause. You simply assumed thats what I was saying. And since the ktoonservative gonernor is only available with this kernel and since the problem is only present when I use the ktoonservative governor, I decided to post it on this thread to hopefully find a solution.
[Sprint Samsung Galaxy S III] freecharlesmanson:
You try aleteringkernel tunables to see if it's affected?
[Sprint Samsung Galaxy S III] Xalky:
Actually , ktoonservative is also on the Agat kernel.
[Sprint Samsung Galaxy S III] shinesthru:
Would a "mediaserver" wakelock be kernel related? I searched the thread and found a couple mentions of this wakelock, but no fixes. Any ideas?
[Sprint Samsung Galaxy S III] ktoonsez:
Nothing to do with kernel. Its the ROM and usually only persists after a cache/dalvik wipe then goes away. If it doesnt you probably have some corrupt media/media data causing it to flip out.
[Sprint Samsung Galaxy S III] shinesthru:
Thanks.
[Sprint Samsung Galaxy S III] DerIdiot:
I'm getting a lot of random reboots with the phone at kt747 stock voltages. Not sure, for example, I just got a text message, after it stopped buzzing it showed the CM10 boot animation. Any ideas? I was previously running undervolted with no issues..

Settings:

CFQ

Ktoonservative

Min: 144

Max: 810

Stock voltages

594 1st touch booster

486 2nd touch booster

486 screen off profile
[Sprint Samsung Galaxy S III] freecharlesmanson:
The kernel settings aren't important. What build are you running
[Sprint Samsung Galaxy S III] Circaflex:
what is the terminal command to enable fast charge with this rom? i tried ffc with no luck.
[Sprint Samsung Galaxy S III] NYCHitman1:
You should be able to do it from KTweaker in Extras.
[Sprint Samsung Galaxy S III] Circaflex:
i removed it while testing a few different programs was just curious if there is a command i can use to enable fast charge
[Sprint Samsung Galaxy S III] decimalman:
su
echo 1 >/sys/kernel/fast_charge/force_fast_charge

Seems to do the trick. I don't see any other obvious ways to enable it besides KTweaker.
[Sprint Samsung Galaxy S III] dmchssc:
I'd been having problems with reboots when I enabled frequencies below 384 MHz. I did stress tests using SetCPU with the phone locked to 192, and the phone would reboot within half an hour every time. I set minimum frequency to 384 MHz, and I haven't had a random reboot since.
[Sprint Samsung Galaxy S III] hayzooos:
What exactly does fast charge do? If a charger only outputs so much, what enables the phone to accept more than that? Or does it remove some sort of limit to what our phones will take? What kind of repercussions does it have if you do it all the time?

The only thing I could find was regarding something like a USB charger (or car charger) that would be recognized as AC instead. What if you plug your phone into the wall every night anyway, would it do anything of benefit then?
[Sprint Samsung Galaxy S III] Circaflex:
you are correct its so the phone recognizes the usb from a computer as ac, i dont think it helps at all if you are charging from the wall
[Sprint Samsung Galaxy S III] cfusion:
I had similar soft reboots a couple of weeks ago,fixed after removing 192. More recently, I added 192 back and increased the voltage to 900 on 192 and 384.... Not 100% sure of cause and effect but had only one soft boot in the week after doing so.
[Sprint Samsung Galaxy S III] hayzooos:
Cool, thanks for the response. So I'm assuming it'll accept more amperage from the car charger (for example) than it normally would? I guess I always assumed it would take as much as the car charger can put out, but it must limit it to something specific regardless of the output the charger provides if it detects it as USB.

---------- Post added at 11:57 PM ---------- Previous post was at 11:53 PM ----------

Are you running the TW version or the AOSP version of the kernel? I ask because I'm running the 10/31 TW version and I just checked the voltages and I see it as 925mV for the 192 step which I have as my min as well. I haven't touched them at all, so this is what they were set to stock.
[Sprint Samsung Galaxy S III] r.suchil2:
Hey Ktoonsez...not sure if this has been addressed or talked about but I always have an issue connecting back to wifi once I reboot my phone. Im using your aosp kernel on the 11/19 CM nightly. I noticed this problem on 11/19 nightly without your kernel, but it seems to be harder to reconnect after a reboot. Love this kernel. Thanks for everything.
[Sprint Samsung Galaxy S III] ktoonsez:
You probably need to do a clean flash, I had same issue 1 month ago, after I did a clean flash and did NOT restore any data, all has been perfect. :good:
[Sprint Samsung Galaxy S III] beserker15:
Is anyone else getting the static snap crackle pop sound during music with regular headphones using the TW kernel? I know it is normally associated with underclocking and listening to music via bluetooth but for some reason I am hearing the sound on regular headphones for any speeds lower than 486mhz. On CM10 and the AOSP kernel, I can listen to music via headphones at 96mhz without any crackling. Just thought that was weird. Have tried several different TW roms.
[Sprint Samsung Galaxy S III] G U C C I:
Ktoonsez, I'm using the same configuration I always do and am getting pretty bad battery life. I noticed I had bad battery life with the nightlies pretty much all last week. Did this happen to you too?