Database Info

System Tuner

Hi all,
I've got a problem with System Tuner. On every ICS ROM I try the CPU clock and voltage settings won't stick. After I reboot the phone they go back to their defaults. Hence, I've got 3 questions:
1. Does everyone have these problems? Did I not check a setting or something?
2. What alternatives to System Tuner don't turn the second CPU core permanetly on?
And 3. Is there an init.d script which lets you set the clock speeds/voltage settings? Because I would rather not use an app at all to do that.

Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.

ccs16rocks said:
Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.
Click to expand...
Click to collapse
Yes I did that, but the minimum frequency doesn't stick.

Nobody?
I'm using No-frills atm, but does that turn CPU1 permanently on?

-editedpost-

V1k70r said:
Yes I did that, but the minimum frequency doesn't stick.
Click to expand...
Click to collapse
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?

yasobaso said:
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?
Click to expand...
Click to collapse
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny

boroboy69r said:
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny
Click to expand...
Click to collapse
Could you be more detailed Do you mean " Re-Apply CPU settings" if so yes I had it enabled. I will reflash stock o any other kernel and check if it's going to solve this.

I also have this problem with system tuner pro, now i'm using setcpu and the settings stick.
using vipers 1.1.0, tried anthrax/bricked/faux123 all didn't stick.

You know you.could ask the dev of super tuner. He's always very responsive anytime I've had issues. Also having different versions backed up in Ti helps as well cause a new update fixes one thing from a slew of phones but might just break yours. Having a backup versions means you can go back restore and test.
Casperi.
Sent from my SGH-T989 using xda premium

In relation to your second question, what kernel are you using? Faux's kernel has the second core on by default. System tuner doesn't have the ability to turn it off. If you want it offline until it's needed, try seb's or bricked kernels instead.

System Tuner 3.0
Just to let you know System Tuner 3.0 was released some time ago and provides improved CPU handling, new GPU, Gamma, MP, thermal controls on many custom kernels and a lot of other new or improved features (entropy, fstrim to name a few).
This is now a spawn of Android Tuner, and benefits from a larger user-base, improved stability and performance.
It now has the ability to turn on/off CPU cores, with a dedicated screen-off option. Only if custom kernel allows it though.

NSTools and SetCPU Set on Boot

If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2

why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor

Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.

i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"

qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.

I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.

[ROM] CyanogenMod 10 (qwerty)

Here is where I'll post my CM10 builds.
qwerty was the name I gave to the kernel I used to post here before I started to post entire ROM builds.
This is based on the amazing dhiru1602's work, big thanks to him.
Dowloads:
Google Drive
You can't resume downloads with GDrive. If you prefer other hosting websites, you can use the direct link of my builds to remotely upload them somewhere else. Dev-Host allows you to do that and allows you to resume downloads. Feel free to mirror my files.
Sources:
Device, kernel, vendor
Misc changes/instruction to build this ROM. The patches not available on Github are here.
Please, read carefully the whole post.
There are two different versions of the ROM. One is using the kernel 3.0, the other the kernel 2.6.35. Read the known bugs and flash the one you prefer.
I did some changes to this CM-10, I updated it and added some extra features such as inbuilt SD swap (Settings > Storage > Use external storage), possibility to show the navbar without rebooting (System > Power menu > navbar and enable it from the power menu. It doesn't work perfectly, keyboards and notification panel can go behind it) possibility to limit the number of background apps and other handy options.
I also backported some performance patches and misc fixes from CM-10.1 and some apps: Trebuchet, Apollo, Gallery (camera), Clock, CM File Manager and Superuser.
CyanogenMod 10 - kernel 3.0
Click to expand...
Click to collapse
Known bugs:
Backlight issues for some users: the screen backlight will automatically turn on when it's supposed to stay off.
Audio/video sync issues while recording videos at 720p, along with frames and fps drops.
Rare reboots. If they happen, post the content of /proc/last_kmsg.
CyanogenMod 10 - kernel 2.6.35
Click to expand...
Click to collapse
Known bugs:
Missing HW composer.
WiFi doesn't work perfectly. Some users report continuous disconnections or problems connecting to netowroks. Try to use a static IP in case you have problems.
Native USB tethering doesn't work. Use a third party app (tested: android-wired-tether).
The inbuilt Wi-Fi hotspot can be used only once, sometimes more, and after that a reboot is required to use it again. You can though use this modified version of android-wifi-tether, reboots are not required.
HD video playback suffer low framerate issues.
The 720p preview framerate is intentionally limited, especially while recording. The recorded video is (almost) fine.
There are sometimes lags in the preview while video calling with the front facing camera
Poor bluetooth headset sound quality. (I don't own a bluetooth headset, hence it's very hard for me to find the problem) - flash libaudio-BT-NR-fix.zip.
Release changes:
Code:
Look for the name of the zip in this thread to find its changes. This is no more updated.
...
20130425: Camera HAL updates. Removed background apps limit. Use the modified dev settings to choose the number of background apps.
20130416: Camera HAL: experimental changes
20130407: Partially working WiFi tethering (perfect with [I]android-wifi-tether[/I])
20130402: Several kernel changes, UMS regression fixed
20130329: Video pillarbox. Regression: UMS requires adb
20130326: Optimized build
20130320: SSID fetch fixed
20130319: Better wpa_supplicant support: WiFi scan and disconnecting bug fixed. Missing WiFi signal intensity fixed.
Instructions
Click to expand...
Click to collapse
Stock ROM / CM7 / CM9 / CM10 Alpha3 (or older):
dhiru1602 said:
IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Click to expand...
Click to collapse
Stock ROMs only: Make sure you have CWM. Flash a custom kernel otherwise
Download the zip of the ROM and save it into the internal SD or the external one (*)
Reboot to recovery
Flash the downloaded zip
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
optional: Flash Google Apps (for Android 4.1.2, many things will break otherwise)
Reboot
(*) While flashing, the device will reboot and you'll see a different recovery after that.
If the zip is inside the internal SD, the flash will re-start automatically after the reboot.
If the zip is inside the external SD, you have to re-start the flash manually re-flashing the zip. If you don't do that, only recovery will work until you flash the zip.
CyanogenMod 10:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps (if you have already flashed them once, you can skip this step)
Reboot
Data wipes are mandatory only if you are not using CM10, it's not required otherwise.
It doesn't matter if you are going to flash the version with the 3.0 kernel and you are using the other, it should work.
CyanogenMod 10.1/10.2:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
Wipe data/factory reset
Reboot
Downgrades are probably not expected, that's why you need to do a data wipe.
Important note:
The modem is always replaced with XXLE4 modem when this ROM is flashed over a stock ROM, CM9 or CM10 Alpha 3 (or older).
You can easly replace it. Take modem.bin from the tar of a stock ROM, place it in /radio overwriting the existing one and reboot. This is required only once, modem.bin is never replaced while updating the ROM. I9003L must do this, I9003 users can use the included modem, but it's better to use the modem made for your region.
Useful informations
Click to expand...
Click to collapse
The latest versions of Instagram are not working due to a problem with related to the GPU binary blob. Instagram 3.4.0 is the latest working version. Probably every device using the same binary blob is affected (Optimus Black for example). You can download a modified version from here that will allow you to login.
The latest versions of Skype do not work properly, the preview is stretched and wrongly rotated. Use Skype 2.9.0.315 or see this post.
LEDs are not supposed to blink when a new notifcation arrives. They'll light up, but they won't blink. Making them blink would prevent the device from entering deep sleep.
(3.0 kernel) Once the battery is fully charged, it will start discharging and it won't be recharged automatically if at least 90 minutes have passed. You can forcefully charge it by unpluggin and re-pluggin the cable. This is an intended behaviour, charging the battery continuosly to keep it at 100% can shortnmyself toer its life.
This ROM allows you to force two apps to stay in memory. See this post for more info.
I made possible to toggle the navbar state directly from the powermenu modifying the existing expanded desktop feature, however it's not working perfectly. The navbar can go over the notification panel and the keyboard while in landscape. However it works as expected if you enable the navbar by setting qemu.hw.mainkeys or modding framework-res.apk. I have no intention to "fix" this as I can't see the utility of the navbar on our device.
(3.0 kernel) For some reason when the screen is turned off during a call by the proximity sensor, if enough time has passed it won't be turned on automatically. You can wake the screen immediately by pressing the home button or the power button or you can increase the backlight timeout from the settings. That will make the proximity sensor work for longer (I'm not sure, but I think the proximity sensor stops working exactly after this timer has expired). this problem is maybe solved.
FM radio is available through third party apps, such as Spirit FM
"Native" 3G video calls are not supported and most likely never will, flash a stock ROM if you need them. GTalk, Skype and all the other apps works though.
(3.0 kernel) if you lost your IMEI, WiFi will probably not work. See this for more info and instructions to fix the problem. No more required.
(3.0 kernel) part of the RAM is reserved. You'll see that we have 442MB 454MB of RAM, that's fine, the missing RAM is not really lost, it's still used.
If the keyboard keeps crashing, you probably flash the wrong gapps.
The magnetic sensor sometimes reports wrong values. When it happens, the field intensity is very high. This was observed with the 3.0 kernel, but probably the same thing happens with a 2.6.35 kernel.
(3.0 kernel) my SD card (it's probably a cheap SD card) is not working properly and I often have corrupted files. It worked fine with the kernel 2.6.35, so if you often have corrupted files, try a different SD card or use the old kernel.
Weird activity in standby? Read this.
(3.0 kernel) 1.2GHz is not stable on every device. I had to disable SmartReflex because it was causing crashes on my device. This means that the voltage of the OPP5 is locked the value I chose is not universally good. I'd prefer not to increase it more, if you have too many reboots, don't overclock. WARNING: don't tick "Set on boot" unless you are sure your device can handle OC. f you are stuck in a bootloop, flash disable_opp5.zip.
In case the max frequency is 1.1GHz, then SmartReflex is enabled and the option in DeviceParts has no effect.
If you find a bug not listed, please report.
Post as many informations as possible, ways to reproduce it and logs.
You can easily grab (almost) all the logs I need by pressing vol down, vol up and power at the same time ("recent" builds only). LEDs will blink and /storage/sdcard0/logs_qwerty/log_DATE.txt will be created. In case the memory is not ready, you'll find the files in /data/logs_qwerty/log_DATE.txt.
The standalone kernel is no more mantained. Flash the ROM instead.
Click to expand...
Click to collapse
Kernel - 2.6.35
Click to expand...
Click to collapse
After months of use, I decided to publicly release my kernel.
This is for CyanogenMod 10 Alpha 4.
It's based on the GB kernel sources released by Samsung (GT-I9003_GB_Opensource_Update2.zip), modified (mostly by dhiru1602) to work with CyanogenMod.
Because of my lack of fantasy I named it "qwerty". It sucks, but at least it's easy to remember.
Main features:
XDA_Bam's code and fixes:
◦ 5 OPPs
◦ Booting at stock speed (1000MHz)
◦ Slight undervolt (3%) on all OPPs
◦ Home button double presses fix
◦ Lowered processor transition latency
◦ Stable Bluetooth connections
Modified light sensor driver: [1]
◦ Disabled hardcoded filter. CyanogenMod has its own filters, enable it from the settings.
◦ Dynamic polling interval
◦ Code cleanup
Modified battery driver [2]
CPU Governors:
◦ Ondemand (default)
◦ SmartassV2
◦ Conservative
◦ Performance
I/O schedulers:
◦ Deadline (default)
◦ Noop
◦ CFQ
◦ SIO
Toggable FSync
Fixed always ON LEDs bug when used for notifications only
VPN networks support (not tested)
Slightly increased touchkeys sensitivity (from 45 to 35)
Other minor changes and optimizations
Downloads:
version 4.0: kernel-qwerty-cm-10-galaxysl-v4.0.zip: kernel with custom DeviceParts.apk [3], hostap and tiap_drv.ko [5]
clean-qwerty-cm-10-galaxysl.zip: restore zip with dhiru1602's kernel
UPDATE: USB composite is still a bit messed up. Windows can't recognize the phone when RNDIS (USB tethering) is enabled (working fine with Linux).
If you need RNDIS, flash this kernel release or the previous one.
Additional zips:
powerHAL-cm-10-galaxysl.zip: power HAL for boosting the CPU when ondemand is used [4]
libsensor-cm-10-galaxysl.zip: custom libsensor. Read note [1]
Changelog:
Code:
22/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.1...v4.0"]v4.0[/URL]
02/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.0...v3.1"]v3.1[/URL]
01/03/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.1...v3.0"]v3.0[/URL]
12/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.0...v2.1"]v2.1[/URL]
09/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v1.0...v2.0"]v2.0[/URL]
08/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commits/v1.0"]v1.0[/URL] - Initial release
Notes:
[1] I made it compatible with the prebuilt libsensor included in CyanogenMod, but I'm using my own libsensor and maybe I didn't test this kernel with the stock one for long enough. I hence added my libsensor, just in case. If you want to restore the original libsensor, simply remove /system/lib/hw/sensors.latona.so.
[2] You can modify "samsung-battery" wakelock length through DeviceParts. By default it behaves like the original module. If you see "Android System" or anything else eating your battery with no reasons, increase the delay or restore the default one.
[3] DeviceParts.apk (System Settings > Advanced) is included because of some additional settings useful when this kernel is used. I'm not a Java dev, so it's probably not perfect, but it works quite well. I took pieces of code from other devices (mostly Crespo, Aries and S2). The source code is available, suggestions are more than welcome.
[4] Power HAL will make the CPU jump to a certain frequency (I set 800MHz) whenever Android requires it (when the screen is touched for example). Power HAL will also limit the max freq to 800MHz (my choice, not too fast, not too slow) when the screen is off. You can change the boosting freq from my custom DeviceParts. CPU frequencies changes (See XDA_Bam's thread for more info about variable overclocking) are not expected. If you don't like it, simply remove /system/lib/hw/power.latona.so. Few more lines about power HAL here.
[5] hostap and tiap_drv.ko make WiFi tethering possible using this modified version of android-wifi-tether.
Special thanks to dhiru1602 and XDA_Bam for their awesome work.

Wow. I'll flash it for sure.
Thanks for sharing.
Update:
Flashed and it works just fine. Just changed max freq to 1200.
Deviceparts looks very professional as well.

Hats off to u buddy. Also kernel name is really good buddy. Dont worry about that
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.

Re: [KERNEL][CM10] qwerty [08/02/13]
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app

Re: [KERNEL][CM10] qwerty [08/02/13]
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003

imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Works fine for me. Try wiping cache+dalvik cache.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
Click to expand...
Click to collapse
Are you using SIRI kernel?

Hetalk said:
Works fine for me. Try wiping cache+dalvik cache.
Are you using SIRI kernel?
Click to expand...
Click to collapse
I am just using the signal fix kernel by loSconosciuto before ...........

^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.

Re: [KERNEL][CM10] qwerty [08/02/13]
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Sent from my GT-I9003 using xda premium

Re: [KERNEL][CM10] qwerty [08/02/13]
Hetalk said:
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Click to expand...
Click to collapse
i post here becoz i wanna flash this kernel will try what u say later, thx
Sent from my U9GT2 from moage.com using xda premium

^ You'll need to wait for users to get thru a battery cycle to report battery drain. I did charge my phone to 100% after flashing qwerty .. so will report my experience tomorrow.

Re: [KERNEL][CM10] qwerty [08/02/13]
just flashed this kernel.. on top of my cracker that i am using previously.. no problem on boot.. upgrading apps as usual.. ive noticed the speed, scrolling and such.. its faster than cracker .. the speed of gb is there..gonna test for some time.. thanks.. via slimbean 3.1 A4..
Sent from my GT-I9003 using xda app-developers app

I am pleased thank you very much !!!
Governor smartassV2 and IO Scheduler deadline (reputable boost daily)
Mini CPU 300/1000 is an exellent choice (I guess the hotboot fix)
it's just what I need ^^
Thank you for taking us solicitous

Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?

just added a tab (specific options) available in the parameter menu

vishal24387 said:
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Click to expand...
Click to collapse
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decisions mostly depend on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
vishal24387 said:
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Click to expand...
Click to collapse
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Click to expand...
Click to collapse
All our kernels based on the sources released by Samsung use a prebuilt module for WiFi. Dhiru tried to use the opensource driver, but it didn't work.
This prebuilt module, taken from our stock ROMs, requires a prebuilt and modified wpa_supplicant which is not completely compatible with Android 4.0+ (Samsung didn't give us the changes required to make the opensource one work). To make things worse there's dhcpcd, we have to use an old version because of the old wpa_supplicant.
In other words: it sucks.
With some access point there are no issues, with others WiFi works, but not so well and with some others nothing works.
EDIT:
Now that I think of that, there are maybe some differences when this kernel is used. I took the prebuilt module from XXLE4 instead of taking it from EDIT2: XXKPM
The warning message I get the first time I turn WiFi (maybe it happens even with the other module, I didn't try it) on suggests me that something was changed in XXLE4, but I don't know if this is a good thing or not.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Click to expand...
Click to collapse
I'm starting to think the problem is CWM. For now only you and spacebar2011 had issues. I will PM you something when I'll have some free time to find the problem. If nothing works, I'll just give you the tars to flash the kernel with ODIN as I did with my signal fix kernel.
@Hetalk
Thanks for trying to help, but he is a peculiar situation. The problem is not the updated blob or a wrong flash, he (and spacebar2011) tried to flash my signal fix kernel several times over a clean CM10 with no success.
rodero95 said:
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Click to expand...
Click to collapse
Dunno, battery life had never been exceptional for me. If you use your phone a lot, any kernel will give you a bad battery life. You can see differences only if you keep your phone most of the time in idle, with mobile data disabled.
wee2wee said:
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
Click to expand...
Click to collapse
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.

loSconosciuto said:
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
Click to expand...
Click to collapse
Thanks...found it...

loSconosciuto said:
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decision mostly depends on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
Click to expand...
Click to collapse
Thanks for ur simplified explaination This means in order to bring smoothness ondemand will keep most of the time freq at 800 mhz (as per ur settings). But definitely its going to affect battery life as just for a simple touch freq will raise to 800 mhz directly. Anyway overall it depends on user who want battery life or smoothness
I have used ur fixed signal kernel for longer time. That kernel really works very well when we use phone (even with 2g net). But surprisingly in deep sleep mode (means with gsm network on on and 2g net off) then there is very heavy battery drain For me its 25% battery drain in 9hr deep sleep mode. But if we keep our phone phone offline in deep sleep mode then it will drain battery just 4% in 9hr. Strange...!!!
I will monitor tonight also with that signal fix kernel. and final tomorrow I will flash this kernel on clean cm10a4 so that I can compare both ur kernels
EDIT : My doubt was right. Your previous signal fix kernel works really good. Yesterday night tested and I found that lost 3% battery in 8 hrs standby. Means my previous 25% battery loss was not a correct observation. Anyway now I will flash this kernel and tell u the results

Re: [KERNEL][CM10] qwerty [08/02/13]
Well, its obvious that keeping a continuous connection with the network costs battery and that when we are connected with mobile network it will eventually change between signal modes (2g, HSDPA, edge, etc) and that also costs battery.
That's why mobile network use to consume more battery than WiFi or offline.
Sent from my GT-I9003 using xda premium

Really nice Kernel with good combination of battery and performance and many good tweaks
Thank you very much Sir :laugh:

MTK6577 CPU Governor Switcher

V18.1 Available
Share to all of You my little program
Features:
- CPU governor switch on the fly
- Fix for MTK6577 bug when 2nd core keep sleeping after screen unlock
Available governors:
- hybrid (default) - 2nd core starts then 1st is 100% loaded, max freq=1001Mhz
- ondemand - both cores work together, more time on freqs between 250-1001Mhz
- powersave - both cores work on 250Mhz
- super powersave - only one core, works on 250Mhz
- perfomance - both cores always run on 1001Mhz
- userspace fixed - fixed freq for both cores, no scaling
- userspace scaling- upper scaling freq thresholds is calculating on CPU load - in this mode, app runs 01processor.sh script from bumbon4ik
- visualization - upper line - cpu frequency, 1001mhz = full screen width, 250mhz = 25% etc. below - both cores, 100% load = current frequency line width. for ex. - fixed 500mhz and 100% both cores load will show three lines on half a screen
:good:
IMPORTANT.
On some phones & ROMs v18.1 may freeze the phone.
To delete app install this update from recovery - v18.1_recovery_uninstall.zip.
Its code:
Code:
mount("ext4", "EMMC", "data", "/data");
delete("/data/app/MTK6577_governor_switcher_v18.1.apk");
unmount("/data");
So it delete only apk in data partition, to remove apps data You have remove folder data/data/MTK6577_governor_switcher_v18.1 and the same MTK6577_governor_switcher_v18.1.odex from dalvik-cache manually.

michfood said:
Share to all of You my little program
Features:
- CPU governor switch on the fly
- Fix for MTK6577 bug when 2nd core keep sleeping after screen unlock in ondemand mode
Available governors:
- hybrid (default) - 2nd core starts then 1st is 100% loaded, max freq=1001Mhz
- ondemand - both cores work together, more time on freqs between 250-1001Mhz
- powersave - both cores work on 250Mhz
- perfomance - both cores always run on 1001Mhz
- userspace - don`t know
Click to expand...
Click to collapse
Thanks michfood :good:
I will give this a try on my zopo zp300+ because the power drain on the phone is very bad so I hope this can sort out those cpu's :fingers-crossed:
Do we have to reboot to switch between the different mode's ie: switching from hybrid to on demand will this require a reboot?
Also I assume I must disable/un-install any other cpu controllers such as set-cpu

no need to reboot.
you can see current governor and cpu freq in such programs as CpuSpy, SystemPanel, CoolTool and others.
about other CPU controlling soft - yes, it`s better to use only one thing.
so AFAIK setcpu do not work properly because of that ondemand bag - after screenunlock only one core works.
it can be shown for ex. in SystemPanel or MicroCpuMonitor

michfood said:
no need to reboot.
you can see current governor and cpu freq in such programs as CpuSpy, SystemPanel, CoolTool and others.
about other CPU controlling soft - yes, it`s better to use only one thing.
so AFAIK setcpu do not work properly because of that ondemand bag - after screenunlock only one core works.
it can be shown for ex. in SystemPanel or MicroCpuMonitor
Click to expand...
Click to collapse
Thanks for the advice michfood :highfive:
You are correct about setcpu I made changes with setcpu but did not see any big improvements only slight improvements :crying:
I am installing your APK now and I will report back after a couple of days use :good:
Keep up the great work michfood it's really appreciated buddy

Thanks for this app! I will give it a try and see what it can do

michfood said:
Share to all of You my little program
Features:
- CPU governor switch on the fly
- Fix for MTK6577 bug when 2nd core keep sleeping after screen unlock in ondemand mode
Available governors:
- hybrid (default) - 2nd core starts then 1st is 100% loaded, max freq=1001Mhz
- ondemand - both cores work together, more time on freqs between 250-1001Mhz
- powersave - both cores work on 250Mhz
- perfomance - both cores always run on 1001Mhz
- userspace - don`t know
ATTENTION!! - found an interesting bug:
- after performance governor CPU keeps running on 1001Mhz, solved in v2 - there is ALWAYS NEEDED to switch hybrid and after that - to other governor.
please - reload
Click to expand...
Click to collapse
I installed this on my Micromax A89, after keypad unlock, governor is changing back to hybrid automatically.

hafeezluqman said:
I installed this on my Micromax A89, after keypad unlock, governor is changing back to hybrid automatically.
Click to expand...
Click to collapse
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running

AW: MTK6577 CPU Governor Switcher
hafeezluqman said:
I installed this on my Micromax A89, after keypad unlock, governor is changing back to hybrid automatically.
Click to expand...
Click to collapse
Same issue here!

michfood said:
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
Click to expand...
Click to collapse
Ya it's changing back to hybrid after screen locks. If possible please correct this problem.

michfood said:
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
Click to expand...
Click to collapse
I also tried CPU Sleeper Dual Core from play market. But heating problem still exist. Is it the problem of kernel ?

without checked "2nd core activation" it stays on "ondemand"....
try it!

kra_ppo said:
without checked "2nd core activation" it stays on "ondemand"....
try it!
Click to expand...
Click to collapse
We want 2nd core activation. Unticking it, is waste.

michfood said:
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
Click to expand...
Click to collapse
Hi michfood,
No Problems on the zopo zp350+ mtk6577 michfood it work's great at the moment. :victory:
I did have a little problem at first I think caused by installing cpu spy after I installed your app.
Try to Install cpu spy first then install your app it worked for me. My setting's now hold no problem. :good:
Hope this helps:fingers-crossed:
Regards bigrammy

V3 issued - tried to fix bugs.
Please reload.
Seems works fine, please test it.
PS - with Fix_on option, after screen unlock 2nd core ALWAYS awakes from sleeping, in ALL governors. It is really needed only for "ondemand", but I think it`s not bad for others. And may be we should asleep 2core in "powersave" mode to achieve min battery drain?

michfood said:
V3 issued - tried to fix bugs.
Please reload.
Seems works fine, please test it.
PS - with Fix_on option, after screen unlock 2nd core ALWAYS awakes from sleeping, in ALL governors. It is really needed only for "ondemand", but I think it`s not bad for others. And may be we should asleep 2core in "powersave" mode to achieve min battery drain?
Click to expand...
Click to collapse
Bug fixed : Governor is not reverting back to hybrid after screen unlock or reboot. I will reply after 2-3 hours about overheating.

I am using it on Ondemand governor. After 1 hour of temple run 2 gameplay with mp3 playing in background, Heat is 20% less on my device. Battery came down from 50% to 24%. It means 26% drained in 1hour gameplay.

is it good?
Sent from my JY-G3 using xda app-developers app

It is good. Without this app, the 2nd core will sleep after screen unlock. So this app is a must have. Is there any app, which shows the load of 2 core seperately, like task manager of windows 7.

yes it's Micro Cpu Monitor.
it doesn't show frequency, but only load
Sent from my JY-G3 using xda app-developers app

guys - have a good news, SetCPU 3.0.9 seems to work properly with our ondemand mode and 2nd core! :good:
so I guess there is no need to go on with my app - SetCPU is quit enough

(8hours) Maximum Battery with NoteIII(Exynos) with Dr.Ketan,Pekaka Kernel and SetCPU.

This is the complete guide for the maximum battery even with power usages.
First of all i am really sorry for my bad English
ROM
Dr. Ketan ROM l21 http://forum.xda-developers.com/showthread.php?t=2519897
Applications
TW Launcher frozen with titanium backup both TW Home and TW easy mode.
Using Nova Laucher as my primary laucher.''
Usning SnapLock instead of Built in Lockscreen. (set Built in Locksreen to none from the setting).
Uninstall the useless or bloatware apps like group play, google now, g+ samsung store etc.
Greenify
Added all apps to greenify except WhatsApp, viber and Sayhi.
Setting
All air and motion functions are off.
Power saving mode on for 24 hr.
Brightness auto -5
Kernel
This is the important and main part to save more battery recently i found Pekaka kernel for my Note III. Their are many comments about drain and getting device too HOT.
So i decided to play with kernel setting. And install setcpu setting thats work for me like a charms.
So after flashing the kernel do worry about getting device too HOT even with Playing Heavy Games also i have attached the setting for the SetCpu... Match your setting below and let me know if this setting also work for you.
The first three setting are to cool down the device if the device gets to hot, it will automatically scale the processor down to allow it to cool.
The other four are to save battery while the screen is off. This will lock the CPU between these lower frequencies when the screen is off, using less mv, resulting in less battery usage.
Thanks to Dr.Ketan for such a wonderful ROM
Thanks to Pekaka for the Great Kernel for Lollipop
Thabks to the developer of SetCPU app.
Give it try and let me know by your comments if this setting work with you or not.

samymarboy said:
This is the complete guide for the maximum battery even with power usages.
First of all i am really sorry for my bad English
ROM
Dr. Ketan ROM l21 http://forum.xda-developers.com/showthread.php?t=2519897
Applications
TW Launcher frozen with titanium backup both TW Home and TW easy mode.
Using Nova Laucher as my primary laucher.''
Usning SnapLock instead of Built in Lockscreen. (set Built in Locksreen to none from the setting).
Uninstall the useless or bloatware apps like group play, google now, g+ samsung store etc.
Greenify
Added all apps to greenify except WhatsApp, viber and Sayhi.
Setting
All air and motion functions are off.
Power saving mode on for 24 hr.
Brightness auto -5
Kernel
This is the important and main part to save more battery recently i found Pekaka kernel for my Note III. Their are many comments about drain and getting device too HOT.
So i decided to play with kernel setting. And install setcpu setting thats work for me like a charms.
So after flashing the kernel do worry about getting device too HOT even with Playing Heavy Games also i have attached the setting for the SetCpu... Match your setting below and let me know if this setting also work for you.
The first three setting are to cool down the device if the device gets to hot, it will automatically scale the processor down to allow it to cool.
The other four are to save battery while the screen is off. This will lock the CPU between these lower frequencies when the screen is off, using less mv, resulting in less battery usage.
Thanks to Dr.Ketan for such a wonderful ROM
Thanks to Pekaka for the Great Kernel for Lollipop
Thabks to the developer of SetCPU app.
Give it try and let me know by your comments if this setting work with you or not.
Click to expand...
Click to collapse
What version of pekaka kernel you use? Could you share screenshots of battery usage?

satslu said:
What version of pekaka kernel you use? Could you share screenshots of battery usage?
Click to expand...
Click to collapse
the latest one 3.2 and screen has been attached above.

samymarboy said:
the latest one 3.2 and screen has been attached above.
Click to expand...
Click to collapse
I can see it now. According to ur ss, usage all over wifi or 3G?

@satslu Usage over WiFi.
WiFi remain always ON in my device I'm mostly indoor user so never OFF the WiFi even not in Use.

Here. Is New Results according to which you can use Almost 8hours with screen On.
Because this result are estimated from 92% battery not from 100%.

Your screen on time is quite impressive. I was on L21 up until the last few weeks. It was much better than stock TW, but still not what I wanted. I was thinking about switching kernels, but ended up on cm12.1 and couldn't be happier. djmax81 is finishing up a kernel for it that should improve battery, and it is incredibly smooth, even compared to Dr. Ketan's rom.

@mwbuss8 can you post the screens with djmax8 kernel ?"

samymarboy said:
@mwbuss8 can you post the screens with djmax8 kernel ?"
Click to expand...
Click to collapse
I don't have his new one. he said it should be done pretty soon