yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It was pegged due to a run away process in your ROM. Probably should inventory your apps. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Just notice my sample rate in governor settings was at 10000 not sure how that happened. I cleared data and set it all the way I like it just to be safe. Ill look into my apps aswell. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
Really? 04-09cm10.1 nightly drained my battery bad. Trying 04-10 now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cowhow:
I'm not OCing or UVing...KToonz pure stock.. I can't really give a fair assessment on battery life because I'm using a hi-capicity battery. This kernel is definitely more stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Ktoonzes hey man this it not kernel related but i hope you can help me trying to cmpile CM10.1 here first try I could but no boot now I get this

make: *** No hay ninguna regla para construir el objetivo «vendor/samsung/d2-common/proprietary/bin/rild», necesario para «/home/maxrdlf95/android/out/target/product/d2att/system/bin/rild». Alto.

Theres no rule to build the object rild need for rild stop that the translation any help would be appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Okay, I've finally given up on linux 3.4. No matter what I do I get reboots and I'm pulling my hair out. Can anyone confirm that the last 3.0 version of the kernel is 3/14? If so, does anyone know where I can get it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
The 4.2.2 JB 3.0 Kernel in the OP is from 3/27..Not sure if one newer than that has been dropped as I have been absent from this thread for about the last week.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
What was he min? And ur screen off profile?

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I appreciate the help, but I've tried everything. I tried min values from 189 to 486, various screen off profiles, disabling profiles altogether, etc. Finally I just did a fresh install of task's AOKP and used his Underwear kernel with all default values and still got reboots. I've been fighting this since 3.4 came out and I'm just sick of messing with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its telling you the problem. You just gotta read and navigate to where the error is pointing.

You don't have the proprietary (rild) in vendor/Samsung/d2-common/proprietary/bin/

Also. You can go to one of the CM IRCs if you need help with this stuff. That way you're not coming into a thread that doesn't have anything to do with it. ;)

http://wiki.cyanogenmod.org/w/CM_IRC_channels
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Thanks you-re the best man :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
Its okay.... I myself am using an extended battery. Im aware of how fast my battery should drain. Losing 11% over a night is alot(4200mah). Its not kt kernal either. I know its the rom. Because it didnt drain that badly till i installed cm10.1 04-09nightly.

But good for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bstylz911:
Are there new updates for tw ROMs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
3/17 is the latest one with 3.0 kernel. If you need a copy let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] garymachete:
Negative... 3/27 is the latest 3.0 build.

http://xdaforums.com/showthread.php?p=39645578

Xone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I miss read his post, i thought he was wondering which one was the latest CM nightly with 3.0 kernel. my bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
I'm having issues with the phone waking up at times I had it happen 3times yesterday. Rom is cm 4/2 any version after that will give me the issue with in one hour of updating. I can run cm for 24hrs no problem then I install the newest kt and it will work for about a day before the phone will not wake up.

BY not waking up I mean message led will be on and touch buttons will light up but the screen will not turn on and today my alarm did not go off. To fix I hold the power button till it restarts.I never had reboot ussues

like some users with 3.4

Is there some log that I can pull to figure the issue out?

Also I will run stock cm for 3 days to see if I get the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
This killed my lag. Thanks. Ktoonservative/row

Edit: Not completely but it does help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Side effect of lowering these thresholds is a slight decrease in batt life. Just keep that in mind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
n/m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 4.11.2013

1. Optimizations for ROW scheduler

2. Optimizations for CFQ scheduler

3. Optimizations for DEADLINE scheduler

4. Some backgound scheduler optimizations and entropy stuff

5. Merge in codeaurora JB_2.5.04.02.02.40.236

6. Fix composition issues when framework rebooted in suspend

7. REVERT regulator fix up that was causing high power drain and instability

8. Merge in codeaurora JB_2.5.04.02.02.40.242

9. 100% synced with CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Already booting up from kernel flash. I love you toons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ppluissz:
Hello ktoonzes i am having problems with the new SmartassH3 governor , i dont know why but it always stays tucks at the highest frequency I stablished for my cellphone , in my case 1512mhz. It is acting like Performance, it just lowers the frequency when the screen is turned off. Hope you can help me and Thanks a lot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Hmm, I am experiencing bootloops on today's build. My last_kmsg vanished some time ago so I can't help much in that regard. It isn't an immediate reboot but usually within 1-2 minutes. Should I be clearing ktweaker data/cache?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This has been covered, its not cooperating with 3.4 and I asked people to tweak on it with the tunables to see if they had any luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
Sorry to be dumb on this one but does this mean:

Disabled or Enabled? :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Sorry for ask again, I Know that it was already asked 1,000 times.

Can you post the recommended settings for the new kernel.

I ask because I came from TW, and I see different options that the one that I had in TW.

Thanks and great work. You're the best.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Enabled
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Post #3 ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Now that the schedulers have been updated which do you recommend? If ROW then just ignore this post :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I see that I can turn off touch boosters. Is there a way to have touch boosters turned off but still take advantage of booster when pushing a button to wake the phone from sleep?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidFiend76:
Deleted. My issued was resolved. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Does 3.4 4/11 build have issues with cm10.1? I'm still using the 3.4 4/6 build???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I would update, lots of Cm updates and lots of optimizations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Just had a spontaneous reboot with todays kernel. Haven't had one of these in a while. Settings are from post 3. Tasks latest ROM.

KT any chance you can have a glance at lastkms?

http://db.tt/LcAAS6vu.

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Hey Ktoons!

Running CM 4/10 nightly, and I get reboots every hour or so (seems random afaik). Tried your kernel and got reboots about every 5 minutes. My phone also doesn't like the newer (3.4 kernel) AOKP builds... But CM is using 3.4 too. Any ideas for me to try or anything I can pull that would help? I also tried copying your settings from post 3 (Yes I know those won't neccesarily work best for me ;) ) Thank you!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here is the important part:

[ 798.533129] SMSM: Modem SMSM state changed to SMSM_RESET.

[ 798.539783] Notify: start reset

[ 798.542835] Probable fatal error on the modem.

[ 798.547138] modem subsystem failure reason: (unknown, smem_get_entry failed).

[ 798.559438] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

Are you on an old modem or a new experimental one? Sure seems like that could be the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im assuming you are NOT OCing or UVing, just stock Mhz settings and stock voltage? If so, add 25mv to all steps, keep everything else stock, no changes at all so that it can use stock interactive governor and cfq scheduler. Just a thought, might want to change to "noop" for scheduler though since that one basically has 10 lines of code with no complications.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
You got it, all stock voltages, I didn't adjust the -25 to all like you do. I'll try upping it up and use the noop :) I actually have noticed that noop seems to agree better with my phone. I got the very first shipment, so maybe they changed something in the hardware? Thanks dude! I'll let ya know if it works :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They did go thru a few iterations so maybe you got unlucky on CPU. Now that I got the the current temp in KTweaker, take a look at that screen here and there to see what temps are when you are using it and NOT using it too just to see what temps hover at.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Well so far I've made it longer than usual :) Temp is at ~45* right now for CPU temp. I'll keep an eye on it. I love the options you have in this kernel!!! If this works on my phone (even with an occasional reboot as to be expected), donation headed your way :) Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man. Is the 45 with use or just sitting there idle with screen on. 45 is pretty high for AOSP (only TW usually runs at 45 idle with no use due to the 1.1gb size, 73 background process/services and no free RAM), mine sits at 29-32 at idle with screen on, gets to 45 only if I am doing XDA or web browsing, anything with high GPU usage. Your reboots might be due to excessive heat and the CPU doing a over-heated panic boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
odd...i just tried your steps and still it seems to overclock to 1890 whenever stress is put on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwburns32:
I have always used SetCPU but since every one here is saying to ditch and use voltage control, I did so. It seems my settings are sticking but I like the idea of having screen off and charging profiles. As far as I can tell there are no settings to do this? Can anyone confirm?

I am currently running at 384/1350 with ondemand and noop... anyone else use these settings to compare battery usage/life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I dont have those exact settings but Im running 384/1674 cfq/ondemand. Phone is fast and smooth. I am not a heavy user but I usually go about 2 days with 2-3 hours screen on. All depends if Im at work or not. Bad signal at work. Right now Im at 2 days 7min 1.5 screen on with 44% battery. Like I said I am not a heavy user.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
I believe the paid version of voltage control has the profiles option. Everything I have seen shows screen off profiles are a waste of time and don't save battery over just leaving the governor alone. So YMMV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
I assume you are on the i747 version of this phone? If so, check the following:

1. Check Version: Do not use same version as me, 7-10b, unless you are on Samsung firmware.

2. Uninstall set cpu or any other clocking apps you have and reboot.

3. Make sure to save as boot settings on Voltage control (setting is a menu option).

4. As Ktoonsez has stated, you will have 6 seconds at 1890 at boot no matter what, then it will adjust.

5. If all else doesn't work, try a full wipe, including data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
So I'm not crazy :D alright well thanks buddy like always task to let rescue :D

im on my phone. expect terrible typos.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
thanks for the reply, but no...still nothing; I get pushed up to 1890 when a stressful app runs even though i have it set to stock clocks. I'm not yet ready for a full wipe yet either lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwburns32:
cfq/ondemand over noop/ondemand? I believe KT suggests noop/ondemand but hey if it aint broke... why fix it?

My battery life has been pretty solid today since switching to Voltage control. I am 6 hours off charger, 49 mins of screen on time, 31 mins of voice calls, about 50 sent/received messages, some XDA and web browsing, WiFi on and I've only lost 80%. I'd say pretty good so far.

I indeed have the paid version, but where is profile setting? And where did you hear that screen off profiles are waste of time?? And if you don't mind me asking what scheduler and governor do you use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
This is from the dev/creator of SysTune:

http://xdaforums.com/showpost.php?p=16102061&postcount=5577

There are many more posts of this nature elsewhere, but this was one of the first I found... I personally am using noop/ondemand right now. I may switch to deadline tomorrow and compare to what I have been seeing with noop so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
+1 on this. Also, Deadline and Ondemand give me the best battery I have seen so far, getting 2 full days with normal use... just my 2 cents.:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwburns32:
Good to know. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mentalmuso:
Make sure you're selecting the apply at boot or init.d script option thingimeeejig.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:


Yeah even with his kernel on GS2 I had better luck with cfq. I haven't tried noop yet but like you said if it aint broke..lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Thanks for the suggestion. I appreciate it.

However, I am certain that I did do that. The interesting thing, this was my path of events:

Delete all CPU apps (I had 3 on the phone)

Reboot

Install Voltage Control

Make Settings, including, set on reboot

Exit App

Re-enter app to check. First attempt failed...still shows 1350.

Exited app/re-entered app.

Set at 1512 again.

Exited app/re-entered, and it appeared to stick.

Exit/Re-enter/Check again. Still stuck

2-3 hours later checked again (no reboots). Back to 1350

Just now rebooted and checked again. Still at 1350.

The interesting thing I'm referring to is it appeared to stick, then later no go.

But the phone is running great :good:

I am tempted to apply the G1 kernel and see what it shows for CPU. But I'm not scared to do any other flashing at all until the IMEI issues are resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
anyone using the elite version of voltage control... is there an option to kill the annoying 'applying default profile in 10, 9, 8.....' or will I have to use the init.d method of settings sticking on boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
On stock rom, with the 7-10b kernel and SetCPU to ondemand/noop 1026/384, I'm at 6% after 30 hours with 6hrs screen time, 5.5hrs music at full volume through the speaker (while driving, ipod cable died), 1.75hrs voice calls, 1.25hrs Maps + GPS, and tons of surfing + texting in the mountains of Ouray/Telluride, Colorado (not great signal, if at all). I had no issues at all while on this 4day trip.

I'm very, very impressed. Thanks for the work, guys! Looking forward to your ICS and Jellybean ROMs when they stabilize with full functionality!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
i've actually just noticed something similar, namely that the kernel wanted to default the max clock to 11xx. this happened only after a cold restart (shutdown and restart). it would later sometimes go back to 1890, but never what i set it at which was 1512.

using the phone for a bit i saw that the usage was almost always in the 11xx and 1890 regardless of what i set the max clock to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwburns32:
I also am trying to get my settings to stick and it seems no matter what I do they won't stick... getting rather frustrated at the moment lol. I'm going to keep trying...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
I"m thinking we just need to give it a bit of time. Kernel hasn't been out long. I'm stopping trying until I see the next 'fix'. Performance is fine for me for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
I feel like ktnz and task are up to something lmao sneaky devs its unlike them to not be jumping at the bit btw I'm running flaxi123 tmo kernel it runs much smoother for now til of course ktnz unleashes the cracken lol try it out..

Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Same modem as usual,didn't know there was any experimental one around...UCDLK3

I'm guessing recommendation if it continues to reflash modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Ktoonsez I was just wondering about this error when you go into the settings for the Interactive governor under boostpulse what does that really mean? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ive been meaning to remove that, its just saying its not readable or writable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats the modem I am running, thought you might have been running original from June 2012 or something. Not sure what caused that modem panic then, never seen that one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Thanks dude. I'll keep an eye out if it does it again. Might have been a fluke.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
OK got ya once again thanks KT!! The 4-11-13 update is running great!! LOVE IT!! :D:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I don't know if its just me but it seems phantom scrolling is gone with today's update :thumbup::thumbup::thumbup::thumbup::thumbup::D:D:thumbup::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I thought I released that fix for you guys on the last one, maybe not. It was the auto_hotplug module that was causing it and fixed it on the 7th build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Last one still had a lot of it.... This one so far is awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Great release KT but still having trouble getting rid of the animation lag. Anyone have suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Read books instead? :D (Sorry, just couldn't help it!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
If you go to Developer options and you pick .5x for Window, Transition and Animator the animation should be much quicker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 4/11/2013

1. Upgraded to newest Linaro compiler

2. Fixed multiplier problems in some of the schedulers

3. Updates to KTweaker for some error handling

4. Scheduler/Entropy optimizations

ENJOY!!!!!!!! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaysmi32:
Ktoonz, I noticed on the tw version of your kernel there's a lot of crackling when play music through Bluetooth headphones.... I even notice on my regular Bluetooth headset, when running your aosp kernel on task rom for instance it works perfectly no crackles, just wondering if u can check on that, appreciate the work u do for us ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No prob. I never mess with bluetooth drivers on AOSP or TW so you'll have to do some tweaking to get TW to behave. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paganfx4:
Thanks Ktoonsez! Running your latest aosp kernel undervolted and my device runs much cooler and with better battery life. Thanks for putting the time into Linux 3.4 and making it work so well. Keep up the good work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Dare I?

I think I do :). Pretty happy with your last test build though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
I'm getting constant force close's as soon as I adjust frequency. I've tried to stop the app and clear data and it doesn't fix it. Also tried a fresh install of ROM and kernel and it still does it. Has anyone had this happen and how did you fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Did you wipe caches, fix permissions?

What version of the the kernel, what ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
I have no idea what's going on but essentially all 3.4 kernels don't work on my phone except kts April 3rd build. Everything else I'll get a reboot approx 30 seconds after the phone boots up.

Ive done everything from wiping cache and dalvik to doing full wipes

Any ideas ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MorphiousGX:
Clear your cache, delete all ktweaker data (under app management), don't use old settings (don't restore), fix permissions, and for sake of stability, restore defaults (the button within ktweaker). If it stays stable, then it must be one of your settings. Introduce them one at a time to find out which one is causing it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
No problems with the newest tj build :) Thanks ktoonsez!

:cool::beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Gave it a try and its a no go :/ but it lasted a bit longer than usual though haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IAmReflex:
Are you on a ROM that supports the 3.4 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I'm getting bootloops also, but only from the latest release. You just gotta stick with the one that works unfortunately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
Anyone try changing the io scheduler settings, and have them not stick when you turn the screen off and back on?

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
My battery life was incredible overnight last night idling. But when the screen is off and i'm using pandora to stream music the drain seems excessive, 5% in 30~ minutes. Could this be affected by the screen off sampling time being at 90000? I'm wondering if adjusting that down would make the batt drain slower when streaming with the screen off.

If so, could a script be made by a user to change this value on the fly when opening streaming apps? using tasker to change the rate and not ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Chances are that it's cause of the constant data streaming. And is worse if you have bad signal or low connection.