Hi I've got a SGS2 and today I've installed ICS I rooted the phone with Chainfire's kernel and I got some problems with Set CPU. The app starts quite normally, it reqests root it gets it etc. Problem starts when I set different frequency and exit the app. After I start it again it freezes thr phone but the hard keys are responsive to the touch but nothing else happens.
If the app is gathering some logs I'll be happy to help if you tell me how btw great app you've already got a beer from me
Cheers
Everytime I try to change the Max frequency to 800 my phone I9100 freezes. When I try to create profiles it freezes too.
I am using stock samsung Rom XWLP2 rooted through mobile odin.
---------- Post added at 04:53 PM ---------- Previous post was at 04:26 PM ----------
That's exactly what I was trying to say!
I've been looking into this on the kernel side of things.
For whatever reason, I can't figure out what, and this is specific to I9100 ICS:
I9100 ICS seems to be patched against the classic "SoD with cpufreq limits less than 800 MHz) to begin with, if you manually set /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq to 500 MHz in an ADB shell, things work OK (well, if your kernel is not patched, it may hit 800 MHz occasionally)
However, if you use a SetCPU screen off profile, even if the max frequency includes 800 MHz (which was safe on Gingerbread kernels), the moment the profile kicks in, the device will freeze.
This includes even if a wakelock is held preventing complete suspend - the device is, instead, hanging the moment the profile is applied. It doesn't happen if /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq is manually changed.
Edit: Hmm... ICS kernels currently don't have scaling_available_frequencies... how the heck does SetCPU know which frequencies are valid? (Doesn't matter, adding them doesn't help.)
So SetCPU is worthless in ICS kernels? Or just the Samsung stock ICS kernels?
Right now:
Using a profile with any Samsung I9100 ICS kernel (that includes my I777 ports), whether stock or custom, is an almost guaranteed hang. Not just screen-off profiles, any profile seems to be likely to cause a crash. Even profiles with a limit of 800 MHz will crash (these have traditionally been safe on Samsungs.)
Setting the frequency in the main screen seems fine - I just set a 500 MHz limit and turned the screen on and off multiple times with no problems.
There's something janky in the kernel (no userspace utility should be able to cause a crash), but so far no one knows what.
Hopefully in a week or two the kernel problem will be found. It'll likely never work with stock kernels, but it's always been that way with SetCPU thanks to the classic Samsung 800 MHz resume limitation. (Every Samsung kernel has needed patching to allow screen-off profiles with limits <800 MHz to work.)
I Will sure buy this app when the problem is solved with ICS Kernels.
It worked great with gingerbread, but now it makes my device freeze or it crashes.
Can't wait for the moment the problem is solved
There's a problem? Paid version works perfectly well on my XE with ICS (and thusly ICS Kernels)
Sent from my HTC Sensation with Beats Audio using xda premium
From what I've experienced and been reading in the siyah 3.0 thread there are bugs in all ICS kernels from Samsung which will cause the freezing you are getting.
Looks like the devs have worked it out and should be fixed pretty soon. Check out that thread for more info.
----------------------
GTI9100 XWLP3
There's a problem? Paid version works perfectly well on my XE with ICS (and thusly ICS Kernels)
Sent from my HTC Sensation with Beats Audio using xda premium
thanks dude, that was a fast update!
I wonder if it is possible to add some more freq. between the range of 384 and 528 for the next udpate, e.g. like 500 or 480 for the non 1.5 cupcake build.
I've tried just about everything
Yeah the first thing I did was clear the market cache after uninstalling before going to the market. I expected to see the price for it after doing that but only saw install. No price and got the same error. I even used titanium backup to disconnect it from the market after an uninstall. Same issue. I'm sure it's not an Amazon issue with me since I've never dealt with it in Amazon except search for it to see the price, but all suggestions are welcome.
This did just make me think of something to try. So of to try something. Thanks...
It has issues with Shake Awake app, everytime single time all day long shake awake forces close when I use SetCPU. Im I the only one with this issue?