[Q] [REQ] Gsiff_Daemon Runaway causing severe battery drain, possible fixes? - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

This is a formal request for any developer capable of doing so, to take a look at this problem.
There is a growing number of users noticing a severe battery drain and hot phone at times, caused by the runaway process; (gsiff_daemon)
The threads discussing this as of now are scattered and unorganized, and with the number of users experiencing this problem, it would be excellent to have one central thread for everyone to work together on this.
Here's what we know so far:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
It is not carrier specific, At&t, Tmobile, and Verizon users have all confirmed this problem.
The only reliable way to rid of this at this time, is a reboot, although some have had luck ending the gsiff_daemon process, or renaming the file, although this requires further testing.
Here are a few threads that have been started on the issue, with some good reading:
http://forum.xda-developers.com/showthread.php?p=30074303#post30074303
http://forum.xda-developers.com/showthread.php?t=1800812&page=3
Anyone capable of looking into this, and know what they are looking at enough to determine the cause, will be eternally thanked, and i will personally donate a case of beer(or soda) to whoever fixes it.
Thanks!

is this Gsiff_Daemon issue only for rooted users? I just got it too...after rooting...I never had this issue since june 30, since I've had the phone

I just renamed the file.. problem went away. it doesn't run anymore.. and haven't had any negative effects that I can tell....

do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?

Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app

tjb433 said:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
Click to expand...
Click to collapse
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.

themadproducer said:
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.
Click to expand...
Click to collapse
isn'ttthere a period before bak?

eyecon82 said:
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).

78c10 said:
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).
Click to expand...
Click to collapse
I am using rooted stock rom
This is only an issue with touchwiz, so you won't see it on cm10
Sent from my SPH-L710 using xda app-developers app

eyecon82 said:
isn'ttthere a period before bak?
Click to expand...
Click to collapse
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.

themadproducer said:
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.
Click to expand...
Click to collapse
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though

eyecon82 said:
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though
Click to expand...
Click to collapse
Eyecon82...really...don't worry about the period. It's irrelevant.
So long is the file is renamed, it wont be triggered/found by whatever normally triggers/finds it.

http://pastebin.com/siAGdxp4
It looks like it's sending gyroscope and accelerometer data to the locapi, (location application interface) and there's some reference to sns there as well.
So, why would a location app need accelerometer data? Or maybe the question is why would someone who's getting my location data need my accelerometer data, too? What's in it for Samsung that they would bother developing it and roll it out? Why wasn't it there in June?
Ok, having a little fun speculating, but perhaps blackboxing for car accidents? Your phone log is the first thing they check and see if you were texting, or whatever, right before impact. Oh, wait, if they have a location-accessing app, they don't need your locally stored log. Nah, probably something technical with the compass....

Janis;34345281It looks like it's sending gyroscope and accelerometer data to the locapi said:
Yes, I don't have any evidence to support this other than what just happened on my phone. I was out for about a 15 minute walk and I got back. Phone was hot and i noticed a severe drop in battery. I remember reading that Goog Now tabulates how far you walked/jogged monthly or something. Maybe this process is capturing that motion/data for it? Just my speculation. No evidence. I think I'll try renaming the file as I dont really GAF about how far Goog thinks I've walked.
Click to expand...
Click to collapse

I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file

harryshepard said:
I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file
Click to expand...
Click to collapse
You sure it's gsiff_daemon that's causing the issue? Have you renaming qosmgr in system/bin?
Sent from my SGH-I747 using Tapatalk 2

Sorry, didn't have reply notification. Yes I am sure. I Google'd it after seeing it using 30% of my battery with about 50s use. I will try renaming qosmgr but how do you diagnose which process is actually doing it? This time battery doesn't specifically say gsiff_daemon but not sure if that's where I saw it before.
I have attached my battery use screenshot. Game and screen a the top, fair enough. But 13 hours on battery and 75% drained, 6% of which is 7 seconds of the gpsd process. It's a little odd
Sent from my GT-I9300 using xda app-developers app

fix yet ? mines doing same

gsiff_daemon
Mine has been doing the same ever since the kitkat update.
I am running an unrooted EE note 3 (n9005) in the UK.
Gsiff_daemon is constantly my top battery drainer according to the battery app (35% - 47%).
I have not been able to find any consistent method to either activate this rogue app or to get rid of it.
Is there any solution without rooting it as I understand that renaming it should do the trick?

+1 from me about this problem.
Uprooted, up to date Note 3.
No solution so far, will try turning off WiFi when screen off and auto rotation... Let's see...
Hopefully it'll be fixed soon or in next version. It's a shame, though, my Windows phone pals are teasing me!
Best regards,
Doncho

Related

How to Speed up your Hero - My Way

Well i already tried speeding up my HERO by following the steps from another thread here in the forum and it just didn't work for me.
So Heres what i Tried and it just seems to work out for me! And its very simple too.​
THIS IS VERY IMPORTANT: DOWNLOAD "OVERCLOCKWIDGET" FROM THE MARKET AND SET THE MIN MHZ TO (128000) AND MAX TO (528000) MHZ. THIS SHOULD HELP KEEP THINGS RUNNING SMOOTH.
^^^^Also from the settings of "OverClock Widget" you can set the MHZ Frequencies while the screen if off to the a low but not so low Frequencies in order to save battery!
So if your like me and like to have a lot of widgets on your phone then Using Task manager to kill certain apps might just do the trick....
First of all never end applications such as
com.htc.socialnetwork.provider
com.htc.provder.weather
HTC media uploader
Touch input
HTC Location Service​
and more! They do not have an icon if your using "advance task Manager" All other apps are good to end such as music,peep,market, Messages,Mail, Google Mail, and of course Browser which uses a lot of memory.
Give it a try and let me know how it goes...​
Heres the link to a video i made to show the performance of my HTC Hero!
Not the best quality.
http://www.youtube.com/watch?v=R3BrCmWXwhQ
Click to expand...
Click to collapse
Thats the way i do it to.
But i also noticed, that some widgets uses more battery than others. After i removed quick calender and digital clock, i got better battery performance. That might also have some effects on the processing power
I tried this...
This afternoon and so far this morning the Hero is far more responsive after I wake it up (which was when it was at its most laggy).
I can now immediately slide around the home screens. Before I had to wait a few seconds or suffer ignored screen swipes.
I was not using the Stocks app or widget but it was set to auto update so set it to never update.
Maybe its a process that runs regardless of whether you use the app or widget ??
Know what I think might work? An app that reboots the phone.
User selects frequency of reboot (daily? every 2 days? every week?)
User selects time of reboot (12 midnight? 3 am?)
User defines Countdown period (15 seconds? 30 seconds? 1 minute?)
At the user-defined time, the app will run itself, and prompt the user "Reboot Now?". A countdown timer will start.
User can select 'Later', 'In 10 minutes', or if there is no interaction/input, when countdown reaches 0, the app will reboot the phone automatically.
This way, users will always wake up to a 'fresh' phone. What do you guys think?
Rebooting the device won't make it faster. On the contrary you have to start every apps for the first time so it takes more time.
You'd better leave it on and turn to airplane mode when you don't need it.
piflechien said:
Rebooting the device won't make it faster. On the contrary you have to start every apps for the first time so it takes more time.
You'd better leave it on and turn to airplane mode when you don't need it.
Click to expand...
Click to collapse
Tell that to my phone. It's back to it's zippy self after a reboot, and only slows down after I run Maps, Browser, Google Talk, Market and HTC Mail
joemax said:
I tried this...
This afternoon and so far this morning the Hero is far more responsive after I wake it up (which was when it was at its most laggy).
I can now immediately slide around the home screens. Before I had to wait a few seconds or suffer ignored screen swipes.
I was not using the Stocks app or widget but it was set to auto update so set it to never update.
Maybe its a process that runs regardless of whether you use the app or widget ??
Click to expand...
Click to collapse
Well im glad to know it works not only for me but for other people Too!
minogue said:
Well i already tried speeding up my HERO by following the steps from another thread here in the forum and it just didn't work for me.
So Heres what i Tried and it just seems to work out for me! And its very simple too.
So if your like me and like to have a lot of widgets on your phone then Using Task manager to kill certain apps might just do the trick....
First of all never end applications such as
com.htc.socialnetworl.provider
com.htc.provder.weather
HTC media uploader
Touch input and more! They do not have an icon if your using "advance task Manager" All other apps are good to end such as music,peep, market and of course Browser which uses a lot of ram.....
Give it a try and let me know how it goes...
Click to expand...
Click to collapse
Could you be more detailed about what process must be excluded from closing?
com.htc.socialnetworl.provider
com.htc.provder.weather
HTC media uploader
Touch input
...
...
THX!
@Asci
Thread updated with latest Info!
I think clock should also be spared of killing, as if I recall correctly, something bad could happen to set alarms (not setting off, volume too low etc.)!
Hi guys, need some help.
i've just rooted my Hero thanks to this article http://forum.xda-developers.com/showthread.php?t=543571 and Quick Boot (which needs root) now works perfectly.
After i've installed overclockwidget i cannot start it as it gives me an error "Star-up error - cannot start Overclockwidget (need Root)".
Any ideas?
thanks in advance.
Surely increasing the CPU speed will also increase battery drain ?
Its also likely to lead to instability and additional heat (Hero gets hot enough when working hard).
Personally I would be wary of doing this.
I have no real issues with battery drainage after tweaking the processor speed; lasts about the same as it would w/out the tweaks.
I do see some minor performance improvements, but on the flip-side, the phone can also get sluggish at times upon waking it up from sleep.
I'm confused, my hero runs at 528 stock o_o
seshmaru said:
I'm confused, my hero runs at 528 stock o_o
Click to expand...
Click to collapse
wrong.. the proccesor was underclocked just like with the HTC Magic and the T-mobile G1
minogue said:
wrong.. the proccesor was underclocked just like with the HTC Magic and the T-mobile G1
Click to expand...
Click to collapse
wrong, mine runs at 528 MHz, and I haven't overclocked it
I can confirm that mine shows 526 (the widget number) as well out of the box. And changing the settings doesn't appear to do anything. It's always returning to 480Mhz - 528Mhz when I restart the app / widget. I've tried this both with SetCPU and OverClock Widget.
The Hero (at least some Heroes) seems to be immune to fiddling with the cpu. And I am sure I'm rooted, because I enabled paid apps in Android Market with MarketEnabler and that's working.
MarketEnabler didn't work out of the box tho - because it had a script that relied on Grep and Grep isn't installed, so I had to empty the AndroidMarket cache by hand from the terminal... Maybe there's something similar preventing fiddling with the cpu speeds?

mssmison did it!: CyanogenMod 5.07 test 3. for kaiser!

wifi working with patch.
http://forum.xda-developers.com/attachment.php?attachmentid=325161&d=1273647492
http://forum.xda-developers.com/showthread.php?t=679680
could someone resize it to 240x320 please? cant wait to try this
Heads up! New Kaiser Wifi update: http://forum.xda-developers.com/showpost.php?p=6456191&postcount=33
Old one replaced build.prop with wrong version. Reinstall and use the new Wifi update.
Also to get rid of android-rebooting-problems with GPS Test application do the following:
1. Start terminal emulator
2. su
3. cd system/lib/hw
4. rwsystem
5. rm sensors.msm7k.so
6. rosystem
7. exit
8. exit
9. restart phone
So how is it? I'm too lazy to install it.
Dukenukemx said:
So how is it? I'm too lazy to install it.
Click to expand...
Click to collapse
Seems like a really nice build. I'm using 320x428 with 144 dpi. A bit slow because I'm currently not running in NAND but I would expect it to perform quite well once I go back to running NAND again.
I haven't tested it very much yet as I'm doing some experiments in WinMO at the moment.
just tried
hey
i just downloaded this and i have to say im impressed about this.
as i love the eclair design and everything and the donut speed i have to say this is impressing because it is FAST! not as fast as donut but pretty much the same. that could be due to the 500 mHz OC but i just like that build.
just needs to be optimized a bit, maybe a few apps like astro and others
and as the developer has a new phone we need a new one.
But i have to say its awesome!
i love it already and just tried it for 9 min.
just the OC needs to be removed i noticed right now and is there any way to set another value for the screen sensebility because quiet often it does not react on a touch.
so keep updating this!
nick
nice rom but it chews through battery like crazy. With a full charge battery will drop from 99 to 75(battery fix removed OC and set 1400 value) with just a 10min phone call and a couple txts. I think what we need is a new kernel highly optimized for battery life using the latest patches. Judging from the name alone of the kernel its running right now 2.6.25-01051-gc362ac-dirty and the fact that 2.6.25 was released in jul 2008 i think theres room for tons for improvement.
Does anyone know how to adjust the microphone gain? my friends complain they cant hear me..
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
kallt_kaffe said:
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
Click to expand...
Click to collapse
Thanks to update.
It working good on Polaris.
Also i change interval to 180 and density to 120 in .prop
Here's an update that changes the wifi scan delay to 120 seconds and also (not tested yet) changes the model name from Vogue to Kaiser.
i'm still trying to figure out if it's possible, somehow, to flash an update.zip file (to be able to use the cyanogenmod skins) with the nomorootfs we're using, instead of converting the skins to metamorph format
does anyone know if it's possible or how to do it?
Can't get wifi to work with updates, which one should I need?
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Dukenukemx said:
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Click to expand...
Click to collapse
edit: how stupid can I be? I've bought another phone and forgot to add the mac adress.
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
mssmison didn't say he was going to put any more effort into it either. Hopefully, someone will pick it up.
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power.
Click to expand...
Click to collapse
Try deleting /data/system/batterystats.bin. That usually helps when the batterymeter has gone bad.
A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
kallt_kaffe how do you do it?
I'm new to the androidinstall.tar method. I'm tyring to run from haret but it seems impossible.
You said you where experimenting with something in winmo, so that implies you're using haret? Are you running from haret?
When I try, Polymod, and Mssmission they don't show an install option, when I try myn and incubus I get it installed but I get no sound. It was actually your gps kernel that let me get things installed all other kernels i tried had non-functional dpads within the installer environment. Also, trying another kernel once installed didn't fix the sound issue.
Anyhow just let me know if you're using Haret. I wonder whats up with the sound and missing install option. I tried the install two different ways one with a 2gb fat32 partition, and then another attempt using three primary partitions 1.3gb fat32, 300mb ext, 300mb ext. All installers then would give me options beside's fat, but not all intallers would have an install option.. I'm using radio 1.71.09.01.eMo, model: kais100, os: wm6.5 (shifu v.3)
kallt_kaffe said:
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
Click to expand...
Click to collapse
I try start Skyforce game, but it forceclose.
It can work after i added "sensors.sapphire.so" into /lib/modules/hw/
I've installed the cyanogenMod updater from the marketplace, but it can only find older versions, no experimental versions, whatever option I set in the program.Anyone?
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
battery life has been fantastic for me on this build...
although I reverted back to 400mhz and got rid of compcache.
I am sure that OCing to 500 by default is draining the battery faster.
I would rather a usable phone than a fast one...(although it still seems very fast to me)

[Q] Phone performance

I wanted to investigate the sporadic freezing in my Galaxy S2. So, I turned on, show CPU usage under the developer's options in ICS. For reference I'm currently running Jedi Knight's latest rom.
I have attached a picture of my cpu usage while at my home screen. The number I've read to be average loads, and anything over 1.00 means trouble. I'm consistently over 10 for my one, five, and fifteen minutes averages. Also, my red bar which apparently measures time in kernel, sometimes spikes and correlates with a brief moment of unresponsiveness.
I've only seen two other screenshots and both users were under two. I was curious what everyone else's loads were. Also, let me know how frequent you have brief freezes, what kind of background apps you usually run. Include info like how many activities do you allow to run in background, do you force gpu rendering, etc. I can't wait to see other's results.
Sent from my SGH-T989
I got like 9/10/11 on mine. I always suspected that I have unusually bad battery life no matter what ROM I'm on, now I wonder if this has anything to do with it...
I'm on Eugene's Plain Jane ROM, which is an AOSP ICS ROM. The Manage Apps menu shows about 10 processes running. Force GPU is on.
ToastMan12 said:
I got like 9/10/11 on mine. I always suspected that I have unusually bad battery life no matter what ROM I'm on, now I wonder if this has anything to do with it...
I'm on Eugene's Plain Jane ROM, which is an AOSP ICS ROM. The Manage Apps menu shows about 10 processes running. Force GPU is on.
Click to expand...
Click to collapse
Thanks, for the response. Do you ever experience temporary freezes? My goal is to figure out if my mini-freezes are caused my memory or CPU.
Sorry for the bad picture quality. I posted through the android app. Anyway, I've left my phone alone for 15 minutes, and I got 8.7/8.7/8.7. I wonder if this uses a different scale than the Unix scale.
rsromano said:
Thanks, for the response. Do you ever experience temporary freezes? My goal is to figure out if my mini-freezes are caused my memory or CPU.
Sorry for the bad picture quality. I posted through the android app. Anyway, I've left my phone alone for 15 minutes, and I got 8.7/8.7/8.7. I wonder if this uses a different scale than the Unix scale.
Click to expand...
Click to collapse
Well, I wouldn't call them freezes, but sometimes performance seem to degrade for a fraction of a second and I experience like a small stutter. Doesn't seem to be unusual, but I'm not sure...
ToastMan12 said:
Well, I wouldn't call them freezes, but sometimes performance seem to degrade for a fraction of a second and I experience like a small stutter. Doesn't seem to be unusual, but I'm not sure...
Click to expand...
Click to collapse
That's normal. The only roms I know that work 100% smooth are Jelly Bean Roms on OFFICIALLY supported devices like the Nexus S and Galaxy Nexus. (Yes the Nexus S runs smoother than this phone. Not faster, smoother) but what OP is stating isn't normal in the least bit. My advice? Ditch that rom. I've never experienced such high CPU activity on any rom and its bad news. Your phone will eventually overheat and shut down. Never a good thing when the SoC gets no form of cooling.
Sent from my SGH-T989 using xda premium
RushAOZ said:
That's normal. The only roms I know that work 100% smooth are Jelly Bean Roms on OFFICIALLY supported devices like the Nexus S and Galaxy Nexus. (Yes the Nexus S runs smoother than this phone. Not faster, smoother) but what OP is stating isn't normal in the least bit. My advice? Ditch that rom. I've never experienced such high CPU activity on any rom and its bad news. Your phone will eventually overheat and shut down. Never a good thing when the SoC gets no form of cooling.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
ToastMan12 said:
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
Click to expand...
Click to collapse
Whoa.. if changing software doesn't help then you for yourself a hardware issue. If you experience lag and heat issues no matter what call tmo and get that handset replace.
Sent from my SGH-T989 using xda premium
That's the thing. I don't experience any lag and the phone is perfectly cool. It gets hot on intensive use, though.
Sent from my SAMSUNG-SGH-T989 using xda premium
I experience the exact same thing as ToastMan. My device always runs cool except when have multiple, heavy-use apps open for an extended period of time. My cpu usage percentages and used memory is always reasonable. Could it be something like an incompatible kernel? What are some debugging steps we could take? What kind of information would be valuable to you that we could provide?
Sent from my SGH-T989
rsromano said:
I experience the exact same thing as ToastMan. My device always runs cool except when have multiple, heavy-use apps open for an extended period of time. My cpu usage percentages and used memory is always reasonable. Could it be something like an incompatible kernel? What are some debugging steps we could take? What kind of information would be valuable to you that we could provide?
Sent from my SGH-T989
Click to expand...
Click to collapse
Is there a chance that maybe the reading is just wrong? Or maybe normal values on Android are different?
If several other people could just check their results and post them here it will be very helpful.
ToastMan12 said:
Is there a chance that maybe the reading is just wrong? Or maybe normal values on Android are different?
If several other people could just check their results and post them here it will be very helpful.
Click to expand...
Click to collapse
I was also thinking that it could be calibrated differently somehow. Like, if it was off by a factor of ten. My values would be much more reasonable. But I have seem several screenshots in the 1.0 range.
ToastMan12 said:
So what do you do when CPU activity is still showing well over 1.0 (5-9) even after installing a fresh ROM? I just flashed the latest official CM10 nightly and have not installed anything other then gapps, and cpu usage is showing 9/8/5.
Click to expand...
Click to collapse
Min has always been in the area of 9/9/10ish. My screen has never stuttered not even on GB, no rrs or sods on official cm10 so far either. My battery life is an entire day (16hrs) of listening to music/playing emulators nonstop.
Make sure you have the 2 idle processes in your battery. If you don't then your phone doesn't idle which will kill your battery life.
If you are using cwm non-touch make sure you use dark side tools or upgrade to touch recovery (cwm 6.x.x.x or TWRP... my favorite). Reinstall your ROM with a complete wipe, install gapps, boot it up then wait 10 mins before doing any setup.
If you are idling then look at your batt stats again... screen is probably waaaay up there... play with your brightness settings.
Hope this helped
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Relsig said:
Min has always been in the area of 9/9/10ish. My screen has never stuttered not even on GB, no rrs or sods on official cm10 so far either. My battery life is an entire day (16hrs) of listening to music/playing emulators nonstop.
Make sure you have the 2 idle processes in your battery. If you don't then your phone doesn't idle which will kill your battery life.
If you are using cwm non-touch make sure you use dark side tools or upgrade to touch recovery (cwm 6.x.x.x or TWRP... my favorite). Reinstall your ROM with a complete wipe, install gapps, boot it up then wait 10 mins before doing any setup.
Click to expand...
Click to collapse
Can you post a screenshot of your idle processes, please?
rsromano said:
Can you post a screenshot of your idle processes, please?
Click to expand...
Click to collapse
Cell standby, phone idle. They should be higher but I had my screen on several hours more than normal today (hence screen being 55%). Top reads 18 hours on, 21% battery life remaining.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

[Q] KT747 Kernel Help

Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah I read your post earlier in that thread and was using your settings. I've come across a newer problem, my phone randomly reboots. I don't know what was causing this so I restored default settings.
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
DarthDerron said:
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
Click to expand...
Click to collapse
I doubt locking the frequencies has anything to do with your reboot problems, this simply dissallows any apps that are capable to override the voltage settings for any particular frequency step. In fact, unchecking this may actually give you a false positive of it 'fixing' the problem when it is actually just using the default (or higher) voltages, burning up more battery in the process. As mentioned by jethro and liltitiz its more likely your UV settings, keep playing with them until you find the happy spot (works on other things too....:silly.
jethro650 said:
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
Click to expand...
Click to collapse
Or just move the ktweaker apk from the /system/app directory from a recovery based file manager. This will keep it from launching on startup and then can either be moved back or ran to reinstall. This way you dont have to cleark the dalvik cache, which should be done any time a kernel is installed, eliminating the extra long boot time when this is done. Either the built in TWRP explorer or the Aroma File Manager which can be 'flashed' in recovery. It doesn't actually flash anything, just unpacks, runs, and then is dumped from memory on reboot...very handy if you dont have TWRP or can't get into android.
liltitiz said:
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I was wondering what was going on. I restored stock Voltage and realized that it was the problem.

Governor issue (??)

Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
It's mpdecision bug - needs root to fix
This issue should be affecting all stock ROM users of TAB Pro 8.4.
I noticed it a while ago and recently had some free time. The issue was narrowed down to Samsung's buggy mpdecision binary in /system/bin and you need root access to fix it. There are two ways to do it (you'll need terminal and file manager with root access rights):
1. Open terminal, type "su" and then "stop mpdecision". Open Root Explorer, navigate to /system/bin and rename "mpdecision" file to something like "00mpdecision". Reboot. All cores will be running at 300 mhz when idle and tablet will feel noticeably smoother and faster. I did not see any serious impact on battery while running this way for 2 weeks already.
2. Download attached mpdecision file from CM11 modrianwifi ROM, unrar it and transfer it to your tablet. Open terminal, type "su" and then "stop mpdecision". Open Root Explorer, navigate to /system/bin and rename "mpdecision" file to something like "00mpdecision". Copy new mpdecision file into /system/bin, change ownership to root:root and access rights to rwxr-xr-x.
Reboot. The issue will be resolved for good and unused cores will be shutdown properly. Tablet will feel the same way it was before file replacement.
Hope it helped.
favero_ said:
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
Click to expand...
Click to collapse
Hm I'm not seeing this issue on my tablet running the NK1 firmware, though I think I do remember it happening on the AND3 Firmware (saw it under Android Tuner) , I wonder if it was fixed under NK1, I'm curious too - do you know a easy way to reproduce it?
Here is a screenshot of CPU-Z, my tablet has been running for at least 1 day without a reboot, and had some 3D games run on it etc, CPU cores always seem to fallback to offline and 300mhz under my test
On a side note:
I don't run the Samsung Touch Wiz Launcher I am using "TSF Shell" as my Launcher, and have disabled some Samsung apps like "My Magazine" and a few Knox things that run in the background. also I don't use too many widgets since I found out they can hog CPU esp on poorly written apps. ,
mpdecision
I saw this issue on NA1, ND3, NG1 and NK1 firmware. Initially I thought it was fixed in NK1, but it came back in 3 days after last reboot. I'm running heavily de-bloated rooted stock f/w (Knox is at 0x0).
As for reproduction - I was suspecting Flipboard, but the issue came back after its uninstall as well. Seems to be uptime-related. 1 day uptime is not enough for NK1 - please check after 2 more days.
I'm running TouchWiz, but used "MyAndroidTools" to disable several services and startups for few remaining stock widgets and apps. Now I'm totally happy with my Tab Pro - best tablet I've ever had.
otyg said:
Hm I'm not seeing this issue on my tablet running the NK1 firmware, though I think I do remember it happening on the AND3 Firmware (saw it under Android Tuner) , I wonder if it was fixed under NK1, I'm curious too - do you know a easy way to reproduce it?
Here is a screenshot of CPU-Z, my tablet has been running for at least 1 day without a reboot, and had some 3D games run on it etc, CPU cores always seem to fallback to offline and 300mhz under my test
On a side note:
I don't run the Samsung Touch Wiz Launcher I am using "TSF Shell" as my Launcher, and have disabled some Samsung apps like "My Magazine" and a few Knox things that run in the background. also I don't use too many widgets since I found out they can hog CPU esp on poorly written apps. ,
Click to expand...
Click to collapse
NetFluke said:
This issue should be affecting all stock ROM users of TAB Pro 8.4.
Click to expand...
Click to collapse
Thank you! I've replaced my /system/bin/mpdecision file with yours and so far the tablet is working properly.
I'll know in a few days if it sticks. But, I definitely had this problem with the governor with T320XAR1ANK1. FYI, for what ever it's worth, I've noticed this governor is slightly slower to ramp up. I don't really care, as the tablet is still super responsive, but some may also notice that Antutu and CF-Bench scores are slightly lower with this governor.
Yeah I can confirm its still present in K1, I tried to limit it down to a few things that could be causing it but have been unsuccessful sine it occurs at random it seems
but my thinking its either something to do with
1. video decoding (I watched a few videos) .
2. charging the tablet (I noticed on my ampere cable it was drawing 0~70 - 120 mA idle )- but this could be because cpu was already drawing more power then needed, usually it's 0 ~ with an occasional 30 mA when plugged in with screen off.
3. possibly game / 3d
...anyways I switched the mpdecision file and it seems to work fine now, except for a slower rampup speed like the others said - not really a big deal i'm sure this will help battery life too.
favero_ said:
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
Click to expand...
Click to collapse
WOW! Finally someone on this forum other than me noticed this issue
I think I posted about this issue in September or so, and nobody else here said they noticed anything. Then I stopped checking this forum regularly... I'm glad to see others have now noticed this problem and have even figured out the root cause too!

Categories

Resources