Database Users

Weird problem with lag on hero with MCK 2.2, setcpu, (compcache not enabled)

so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?

dmc971989 said:
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
Click to expand...
Click to collapse
What gov. are you using on setcpu?

theoottesen said:
What gov. are you using on setcpu?
Click to expand...
Click to collapse
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day

Similar problem...
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.

im just curious if this is the original problem or a new one cause by this rom setup... because I dont ever recall reading anything about the CPU getting stuck at 245mhz from sleep mode being the source the slow downs....

Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?

x99percent said:
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
Click to expand...
Click to collapse
yes, i keep them disabled...

jamesthomas128 said:
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
Click to expand...
Click to collapse
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).

tkirton said:
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
Click to expand...
Click to collapse
im fairly positive that the CPU is getting stuck in the sleep mode while the rest of the phone is not, causing me these issues... the problem is i dont know how to fix them

dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
Ok, modaco rom sets the governor to "performance" on boot. This essentially "sticks" your CPU to max throttle.
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Will tell you where you are, governor wise..
I'm not entirely sure what setCPU does, I've never used it, but I assume it just tweaks your top and bottom Mhz and maybe changes governor to performance when the screen is on? If it's configured properly? Maybe not, who knows?
If you want the best battery life, put the governor back to msm7k, it's a custom governor modified by HTC to make your battery last longer.
I changed the following line in modaco.sh:
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
to:
echo "msm7k" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_govern
and haven't noticed any slowdown from it.. my battery is lasting longer than it did on Stock or Fresh 1.1...

Problems with TouchControl?

if you are having problems with TouchControl or wanted it to be more responsive than try using the Faux kernel and enable s2w while also having the module enabled with TouchControl. I personally like the double tap awake but found it unreliable until I accidentally noticed it became much more responsive when I enabled s2w in the faux control app. Not really sure if it matters but I only enabled the double tap module on the TouchControl app and enabled the s2w option in the faux control app.
Now the only drawback I found is that you can't swipe to turn on even though it is enabled in the Faux App but it doesn't matter to me since I much prefer the double tap awake which works much better when the s2w is enabled in the Faux App. Whats interesting is that swipe to lock does still work even if the module is off in the TouchControl app it must be working because it is enabled in the Faux app.
The setup I mentioned above has worked for me using the latest Xylon rom and prior to that the Xenon rom both using Faux 5m and what I am using now 6B01 (Does not work with 6B04_r2, it appears the TouchControl app does not have that module yet). I have not tried any other kernel is I only use Faux.
Would have posted this in the main TouchControl thread but I don't have access yet. Anyone can feel free to post this there f it helps anyone especially since I keep reading people having issues with the screen becoming unresponsive. If that happens simply hold the power button until it reboots (That has happened to me usually the first time I setup everything after I flash a new rom but then it works like a charm after the reboot). Let me know if you have any questions for me. Good Luck

[Q] [CPU/GPU Governor] Best fitting for my needs? well described

Hello
I am on a quest to find the best governor or kernel for me.
Firstly heres my ''specs'':
I am using I9505, on GE JFLTE-GPE 5.0.1 rom. Right now i have Hulk Kernel, but i have also tried Alucard/Goggy_Max.
I do not care if i have to flash kernels, etc. but i do not wish to change rom
I use my phone for Facebook, Snapchat, Messenger, Chrome, Gmail and loads of music. My music is on my MicroSD (64GB 95MB/s reads). i do NOT game on my phone.
My wish is for the most smooth performance of the above-mentioned, but it is also VERY important for me to have good battery life. Therefore i use Greenify and Amplify. I have limited many alarms/wakelocks, and greenified alot (not Messenger/Snapchat, because it stops notifications)
I do NOT own SetCPU, but i am using STweaks on Hulk Kernel right now.
I have usually used Ondemand governor, but found out yesterday that governors can do alot of difference, so i have shortly tried Badass, and trying SmartassH3 right now. I have been very satisfied with Ondemand governor, but i would be happy if i could get better battery life, with the same performance. For my GPU im trying 'Simple'' governor.
Furthermore ive considered the following governors; DanceDance, Badass, Ondemand, Yankactive, Smartmax, Impulse, SmartassH3 but i am not limiting myself to these, if you have other suggestions.
Thanks in advance
Links to my used Rom/Kernels
Goggy_max : http://forum.xda-developers.com/showthread.php?t=2741181
Hulk_Kernel : http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
GE Rom : http://forum.xda-developers.com/showthread.php?t=2557353
Alucard Kernel : Included as default in rom.

Here's a thread with explanation on pretty much all CPU governors and I/O schedulers.
Based on what you're saying, Intellidemand should be ok for you. It scales CPU based on the GPU load. So that means if your GPU is not working hard (gaming) your CPU should sit in lower frequencies.
SmartassH3 is more of a conservative governor.
You can even try the conservative governor. It was designed with battery in mind. Meaning that this governor prefers the lower CPU frequency. This also means less smoothness.
Another option is to activate one of the Intelli-Plug profiles from Hulk.
Eco performance is what I would suggest. It will turn your phone into a dual core phone but with some performance tweaks.
You could also try the other profiles and see what works best. But you get more battery savings by turning cores off or disabling them.

GDReaper said:
Here's a thread with explanation on pretty much all CPU governors and I/O schedulers.
Based on what you're saying, Intellidemand should be ok for you. It scales CPU based on the GPU load. So that means if your GPU is not working hard (gaming) your CPU should sit in lower frequencies.
SmartassH3 is more of a conservative governor.
You can even try the conservative governor. It was designed with battery in mind. Meaning that this governor prefers the lower CPU frequency. This also means less smoothness.
Another option is to activate one of the Intelli-Plug profiles from Hulk.
Eco performance is what I would suggest. It will turn your phone into a dual core phone but with some performance tweaks.
You could also try the other profiles and see what works best. But you get more battery savings by turning cores off or disabling them.
Click to expand...
Click to collapse
Hi
I tried the SmartassH3, but it seems it keeps rather high freqs? atleast it made my phone warmer than usual, so i am back to Ondemand until further. I activated the intelliplug and limited the cores to 2, and ive felt no performance loss yet. Which is great, so thanks for that tip
BTW, after ive begun with the governor tweaks, ive noticed my Poweramp decides to turn off when my screen is off? :/ It is not hibernated by Greenify, and Amplify has not limited either, so i do not understand why it stops. If i choose ''use wakelocks'' in Poweramp, it stays active. But this ofc. drains battery very quickly . Do you have any idea, what could be the problem here?

Check with an app to see how many cores you have active. Some said those settings don't work. For me they seem to work. But just to make sure.
When using poweramp the device will be awake anyway.
Governors should not have any effect on apps and how they run, except performance-wise. Governors can't put apps to sleep.
Poweramp requires the media service to run. Make sure you did not block that.

GDReaper said:
Check with an app to see how many cores you have active. Some said those settings don't work. For me they seem to work. But just to make sure
When using poweramp the device will be awake anyway.
Governors should not have any effect on apps and how they run, except performance-wise. Governors can't put apps to sleep.
Poweramp requires the media service to run. Make sure you did not block that.
Click to expand...
Click to collapse
I've already checked with Trickster MOD kernel settings, and verified it works
Ill check up on the media service. Do you know its exact name in Amplify?

amd62 said:
I've already checked with Trickster MOD kernel settings, and verified it works
Ill check up on the media service. Do you know its exact name in Amplify?
Click to expand...
Click to collapse
No, as I don't use Amplify.

after ALOT of tests, i think ive found out what happend. I limited the screen off max freq to 384MHz, and i think this was the problem. I will report back if it is NOT the problem. Else consider it solved
EDIT: Seems it was not. The search continues :I

LG G2 VS980 [RRv5.5.8] Llama Sweet Kernel DT2W Feature GONE

So I had recently flashed the latest Resurrection Remix 5.5.8 Lollipop onto my LG G2 VS980 and then continued on to installing the Llama Sweet Kernel R3 and had changed the settings to what the OP said to in his post:
Personal setting (soon as i know how to do i'll make them as default) :
CPU MAX FREQ 1497 MHz
CPU MULTICORE POWER SAVING aggressive
CPU GOV Nightmare
ENABLE Intellithermal (IMPORTANT)
CPU VOLT -20
IO Read-Ahead size 2048 KB and Scheduler ZEN
GPU GOV simple_ondemand
Sound +3 for Headset boost and +2 for Speaker boost
POWER SUSPEND kernel mode
FAST CHARGE enable
WIFI SCAN interval 150 sec
http://forum.xda-developers.com/showpost.php?p=61078624&postcount=2
Click to expand...
Click to collapse
I did that and it worked out perfectly fine and my phone has no issues at the moment, but for some odd reason the double tap to wake feature has been removed/doesn't work anymore. I have gone under Settings and through all the options but there is no option to "Double-tap to wake up" anymore. Is there a solution to this?
------------------------------------------------------------------------------------------
I have found out that it is a problem with the kernel. But is there a way to get around and enable the double tap to wake feature on this kernel? I want to try out the kernel but want the feature on my phone as well. If there is no way of that, then can someone link me to the stock kernel for this rom?
http://forum.xda-developers.com/showpost.php?p=62738195&postcount=7092

Overheating problem on Stock ROM

Hi guys!!
I am running Stock ROM on my GT-I9301, with @sev3n1985 kernel. I have overheating problems! Sometimes it's very hard to hold my phone. How can I solve it? Btw, I'll leave my Kernel Settings down bellow
Regards :*
Settings (I use Kernel Adiutor):
- CPU Max Freq: 1401Mhz
- CPU Min Freq: 300Mhz
- CPU Governor: smartmax
- Multicore Power Saving: Disabled
- CPU Hotplug: MSM Hotplug (MPDecision desactivates)
- CPU Boosted: 1
- Max Cores Screen Off: 1
- Thermal: Temperature Throttle
Sent from my S3 Neo+ (GT-I9301I) running Custom Made StockROM with @sev3n1985 kernel

Have you already done a factory reset?
Perhaps it's just a bad app.

Jhnsn said:
Have you already done a factory reset?
Perhaps it's just a bad app.
Click to expand...
Click to collapse
I use Greenify even on some system apps, so no background apps. And my ROM is deodexed. So I think that's not the problem. But thank you
Sent from my S3 Neo+ (GT-I9301I) running Custom Made StockROM with @sev3n1985 kernel

S3 Neo is familiar with overheating problems even on stock, but I'm trying to understand, do you have that problem even if you are not using your phone that much?

Sometimes hot plug & governors (more tied to the interactive than ondemand) logic simply bricks hot plug & then you have all cores running all the time. Their is also a conflict tied to additional bust frequency logic. All this is actually cased by Samsung & it's never been corrected in this kernel (it is corrected only in official CM12.1 repo). Simple reset resolve this until it happens again.
Regarding Smart max try like this:
Also go with mpdecision hot plug & use simple on demand GPU governor.
It should save some juice keep consumption under control & device cooler.

Zola III said:
Sometimes hot plug & governors (more tied to the interactive than ondemand) logic simply bricks hot plug & then you have all cores running all the time. Their is also a conflict tied to additional bust frequency logic. All this is actually cased by Samsung & it's never been corrected in this kernel (it is corrected only in official CM12.1 repo). Simple reset resolve this until it happens again.
Regarding Smart max try like this:
Also go with mpdecision hot plug & use simple on demand GPU governor.
It should save some juice keep consumption under control & device cooler.
Click to expand...
Click to collapse
Thanks for your time, dude

You can also try like this to keep it more in green line frequency range even more during the light tasks, performance for the light tasks is not stellar but it's more than good enough this way.
Note: Ideal awake frequency (targeted one) for this SoC should actually be 600MHz considering power voltage and DRAM frequency dependencies but on Samsung firmware this is not fast enough so it actually produces contra effects; jumps to higher frequencies more often along with waking up additional cores so 787 is advised minimum. On the other hand peple who love & use Smart max on other light wait roms such as CM's (without of heap load Samsung bull****s) can actually try with 600MHz. Still interactive governor is possible to be tuned better.
Best regards.