Related
This kernel uses AOSP camera driver so it's most likely compatible only with Redux 2.0 (tested) and Oxygen (not tested)
Before you do anything- make a backup
It's my lame attempt (I'm a modder, not a dev) to get more battery life without loosing stability of original kernel.
Kernel is based on current thalamus 2.6.35.14 sources
What is changed (mod8):
-Vdd levels sysfs interface is back, this time seems to be stable
-default voltages for CPU clocks <700 MHz are lowered a bit- keep this in mind when playing with UV
-headphone volume boosted a little- needs to be tested
-more optimized compilation- kernel should use CPU in more efficient way (and kernel is 500 bytes smaller )
-big thanks to paul8944 for testing
What is changed (mod7):
-removed sysfs Vdd levels interface- it seems that it was responsible for instability and FC's in mod6
-USB transfer speed is higher (was ~800kB/s, now ~2MB/s for write operations)
What is changed (mod6):
-added sysfs Vdd levels interface- VDD_MIN is set to 800 mV, VDD_MAX to 1300 mV, step is 25 mV (this works fine with IncrediControl)
-available governors: ondemand, powersave, conservative, performance and smartassV2
-conservative governor is tweaked a little (should be a little less conservative)
-USB transfer speed tweak- needs testing
-other fixes
What is changed (mod5)
-lowered minimum cpu clock to 128 MHz
-more clock speeds are available up to 1113 MHz
-added smartass and smartassV2 governors
-tinyRCU replaced with preemtive tinyRCU
-enabled call recording (not tested)
-many other fixes and improvements mainly form ch33kybutt's and elevendroids' sources
Note about smartass governor- after longer period of inactivity you have to press Power button for about 2 seconds to wake up the phone
Installation:
-make a nandroid backup (just in case)
-put zip on SD card and flash in recovery, I suggest also wiping dalvik-cache (just in case)
Download:
thalamus 2.6.35.14 mod8
md5: E526C99D4326F5B11D02DB60FEFA169F
Previous versions:
thalamus 2.6.35.14 mod7 (description above), md5: 7AB623BCC5E28D9BC8A012EDD9E9BBC7
Mod6 is not available due to instability
thalamus 2.6.35.14 mod5 (description above), md5: 7DC3E94E56FD00C49FEB5C713033DE33
thalamus 2.6.35.14 mod4 (128 MHz min cpu clock, default governors set, non-preemptive TinyRCU) md5: E7DD4637D8838A6E1A64E763C8A4D549
Kernel sources available on Github
I'll give it a try, seems good. I have one question and one suggestion:
the question is: what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
and the suggestion is to add the syscf interface for being able to change the voltages. It could save some battery life if our Desire stands it (mine does even at 800 mV )
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
blackhawk_LA said:
what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
Click to expand...
Click to collapse
I was not satisfied with default cpu clock table
-128 MHz uses ~20 mA of current less than 245- it's about 10% saving for iddle not locked phone
-for me 691 MHz max clock is really enough for my needs, it was not available in stock version
-more speeds make governors able to better match cpu speed (and save some juice)
-there are some performance fans so why not enable also 1113?
soronk said:
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
Click to expand...
Click to collapse
Looking what caused this, I'm not sure if it's wlan driver or preemtive tinyRCU (not present in mod4)
Download temporarily removed
EDIT:
It was wlan driver.
Corrected, reuploaded package
gen_scheisskopf said:
EDIT:
It was wlan driver.
Corrected, reuploaded package
Click to expand...
Click to collapse
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
soronk said:
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Me too.....
Sent from my HTC Desire using XDA App
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Tones1971 said:
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Click to expand...
Click to collapse
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
gen_scheisskopf said:
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
Click to expand...
Click to collapse
Yes it work! But without camera. MIUI needs the 720p camera drivers.
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
h_misc said:
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
Click to expand...
Click to collapse
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Click to expand...
Click to collapse
Too bad, with screen off laggy behaviour when raising the CPU-clock is exactly what I want.
With the conservative governor reaction to the power button is instant, smartass was really irritating me when pushing the power button the days I tried it.
I used setcpu with a screen off profile with conservative and ondemand with screen on (on gingervillain) which was just perfect.
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
blackhawk_LA said:
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
Click to expand...
Click to collapse
I use the FTP server with screen off, a script that functions as webserver to name two examples. So I need it to be possible for the CPU to be at more than minimal speed.
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
blackhawk_LA said:
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
Click to expand...
Click to collapse
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
So which governors do you think should be in kernel? I don't want to include all available
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
So which governors do you think should be in kernel? I don't want to include all available
Click to expand...
Click to collapse
The ones I like to use are ondemand and conservative.
You should include what you like off course
h_misc said:
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
Click to expand...
Click to collapse
I couldn't agree more
I think that the most used governors are conservative, ondemand, interactive and smartass (don't know about the new governos: smartass2 and others)
But for me, having ondemand it's enough
blackhawk_LA said:
But for me, having ondemand it's enough
Click to expand...
Click to collapse
Do you want a dedicated build?
So as for now governors will be ondemand, performance, conservative, powersave (even more conservative than conservative ) and smartass- more likely v2.
I plan to release mod6 when I'll implement SVS
As some of the other threads are getting a little bit chaotic, I'm opening this thread 'bout kernels. I'm trying to list all available kernels for the I9001 here in this first post. You may discuss kernel related problems here.
Right now the kernels are included in a bigger package. That's why there are the links to those packages and not to a "single" kernel file.
Available kernels:
FeaCore_Phoenix_OC: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore_Phoenix_nonOC: http://mediafire.com/?5unogie5i58x85r
Cranium Kernel_OC:http://www.multiupload.com/5QC10CJZK6
Is the feacore phoenix non oc is stable? Battery drain???
2.3.6 ZSKP6 | Adrenaline Shot v12
FeaMod 1.2 | Instanet 3G Free
Nice..
Sent from my GT-I9001 using Tapatalk
pyronia said:
Is the feacore phoenix non oc is stable? Battery drain???
2.3.6 ZSKP6 | Adrenaline Shot v12
FeaMod 1.2 | Instanet 3G Free
Click to expand...
Click to collapse
It's less fluid for me ... Back to 1.3.1.
pyronia said:
Is the feacore phoenix non oc is stable? Battery drain???
2.3.6 ZSKP6 | Adrenaline Shot v12
FeaMod 1.2 | Instanet 3G Free
Click to expand...
Click to collapse
I use 1.3.1 non OC.
Its stable and has a good battery use
Sent from my GT-I9001 using XDA App
manveru0,i got confused when i saw ur commit 'revert,re revert blah blah'
what's the current status of jhash3 in phoenix kernel?
sakindia123 said:
manveru0,i got confused when i saw ur commit 'revert,re revert blah blah'
what's the current status of jhash3 in phoenix kernel?
Click to expand...
Click to collapse
Current status is that jhash3 is reverted back to standard jhash in the OC version. Yesterday I had a loss of about 10% battery power over a time period of ~ 8 hours, which is too high. oudbrood has the same issue. Right now I'm testing the latest build. If it turns out that the battery drain is lower, I'm definitely gonna send jhash3 into nirvana
My clone of Manveru0 kernel is still drain battery 2% over night, and i have 3890 points in Antutu without any adrenalin and thunderbolt
pm.sleep.mode=1, I not use full suspend mode in MSM
max CPU freq 1490, all freq undervolted -25mv.
One question why here such options #define DEFAULT_RAMP_UP_STEP 345600 and , #define DEFAULT_RAMP_DOWN_STEP 345600, for them very good productivity but is used only three frequencies
p.s. BFQ slow rather than CFQ, in antutu -200 points with BFQ
vitaliy_y said:
My clone of Manveru0 kernel is still drain battery 2% over night, and i have 3890 points in Antutu without any adrenalin and thunderbolt
pm.sleep.mode=1, I not use full suspend mode in MSM
max CPU freq 1490, all freq undervolted -25mv.
One question why here such options #define DEFAULT_RAMP_UP_STEP 345600 and , #define DEFAULT_RAMP_DOWN_STEP 345600, for them very good productivity but is used only three frequencies
p.s. BFQ slow rather than CFQ, in antutu -200 points with BFQ
Click to expand...
Click to collapse
hey can u post ur kernal. would like to try it out. thanks
Could you upload a non-OC Fly High kernel? Or is Fly high still a test-kernel?
Sent from my GT-I9001 using Tapatalk
vitaliy_y said:
My clone of Manveru0 kernel is still drain battery 2% over night, and i have 3890 points in Antutu without any adrenalin and thunderbolt
pm.sleep.mode=1, I not use full suspend mode in MSM
max CPU freq 1490, all freq undervolted -25mv.
One question why here such options #define DEFAULT_RAMP_UP_STEP 345600 and , #define DEFAULT_RAMP_DOWN_STEP 345600, for them very good productivity but is used only three frequencies
p.s. BFQ slow rather than CFQ, in antutu -200 points with BFQ
Click to expand...
Click to collapse
with or without jhash3? I guess without it, right?
the high default ramp up step value was because i once had stability issues with lower values. But that may have been something else. Anyway, did lower it for a test. Okay, I've now also SIO as I/O scheduler included. Need to test that as well. Thx for your input
Yes, without jhash3
I have included support shed debuggin in kernel, and now testing a little commands sach as echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
I maked temporarily dssconfigure JFS anf CIFS.
Now testing kernel
vitaliy_y said:
Yes, without jhash3
I have included support shed debuggin in kernel, and now testing a little commands sach as echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
I maked temporarily dssconfigure JFS anf CIFS.
Now testing kernel
Click to expand...
Click to collapse
hey man,cud u try adding xz boot compression ,cleancache?i cudnt do it.....compilation errors
EDIT:manver0 added cleancache!
I check the battery expense after that I will search for initial codes for BLN
vitaliy_y said:
I check the battery expense after that I will search for initial codes for BLN
Click to expand...
Click to collapse
there are plenty of codes for bln around. That ain't the problem. But, you need to change the liblights library which means, you need to recompile it and push it onto your phone. Now I don't know what happens if I push the new library with an update package, everyone gets it and after that somebody reverts to an older version without bln. You know what I mean?
https://github.com/neldar/kernel-2.6.35-nexusS-bln
Edit: By the way I've lowered the DEFAULT_RAMP_UP_STEP down to 249600 which leads to shutting off the device every time it goes into sleep mode. Exactly this was the reason why I have 345600 in it. I'm gonna revert the sources again...
Edit2: I had a reply on the german board android hilfe about jhash3. I'm definitely not gonna reimplement it as the battery drain is definitely higher:
He checked the battery drain with and without 3g data connection
2 hours Wlan off (and 3g on) = 11% battery drain
4 hours Wlan on (thus 3g off) =2% battery drain
I used DEFAULT_RAMP_UP_STEP adn down step 128000, and device worked normal,
Ideal sleep speed was 246000 instead of 128000
vitaliy_y said:
I used DEFAULT_RAMP_UP_STEP adn down step 128000, and device worked normal,
Ideal sleep speed was 246000 instead of 128000
Click to expand...
Click to collapse
ok, gonna check it out.
Why would you choose a higher frequency on the ideal sleep speed?
Edit: echoed your values to the ramp up and down node and it immediately killed my device when going into sleep state (aka hit power button)
i used instead a generic concept.............min and max
Envy Kernel
Kernel Purpose
This was previously the Galaxy KOR.
Must there be such a difference in perspective between stock and custom? My objective is to squeeze everything there is to squeeze out of what would be expected of a proper "stock" kernel. There is no required user input, everything is defaulted as it should be. The TouchWiz kernel is built on the VRBMB1 platform for this reason. Think of this kernel as an augmentation of the stock.
Kernel Features and Specifications
Based on VRBMB1 source code.
Patched to the latest linux kernel (v3.0.70).
Used the linaro toolchain built with gcc 4.7 (13.02).
Removed some unnecessary features.
ROW scheduler (v4) defaulted.
Implemented urgent request handling.
Integrated a "stock" 256mhz/1.62ghz cpu freq table (see 2nd post).
Added NTFS r/w support.
InteractiveX V3 governor added (thanks imoseyon).
Updated lowmemorykiller values.
Ondemand governor from CM10.1 defaulted.
Lightened kernel modules and memory resources.
Ramdisk optimizations.
420Mhz GPU OC applied to high frequency.
Imoseyon's USB Fast Charge added.
PegasusQ governor added.
Not Working
Nothing that I'm aware of.
Closing Statements
This is my first kernel. The more I get into it, the more I appreciate and enjoy working on this stuff and I have every intention of making this a priority in my life. Looking around at development, I see I have much to learn (thankfully). I imagine, as time passes, my efforts will change and, with that, so will my kernels. Therefore, I cannot promise the best there is at any time, only the best I can offer at that time. And that, my friends, is where the fun lies.
Anyone is free to add this kernel to their ROM. Just be sure to give credit and let me know so that I can check out your work.
Source.
Special thanks to Yank555 for helping me out on one or two or several occasions.
Thanks to imoseyon for letting me use the InteractiveX governor from his lean kernel.
Thanks to the Cyanogenmod team for their awesome source code.
Thanks to the linaro team for their toolchains and compilers.
Special thanks to remf4i. RIP, my friend.
Cheers,
Rath
PS - Downloads and stuff in post #2.
Downloads
Stock TW LK3 Kernel
Envy Kernel r1 (3/26/2013)
Instructions
Flash kernel in recovery.
Wipe cache.
Wipe Dalvik.
Fix permissions.
Relevant Information
Everything is defaulted
As stated in the OP, this kernel is principled on stock functionality. Like Samsung and Google kernels, there is no necessary user involvement. The proper scheduler (ROW), governor (ondemand), and cpu clocks (1.62Ghz) are defaulted in the kernel. Just flash and enjoy. That said, you can always use a CPU app to get some control if you like. Imoseyon's interactivex governor is in there too.
New "stock" CPU frequency table
The 1.62ghz comes at a much lower power cost with the frequency/voltage tables I have set. All phones (so far) have been able to run 1.62ghz with the same voltage needed for 1.512ghz (stock). I have applied this and adjusted down the rest of the voltages accordingly. I have not added voltage control and will likely not.
There is also an adjustment to the low end frequencies. 384Mhz has been clocked to 256Mhz and voltages have been lowered.
The ROW scheduler
As you may know, the scheduler assigns work to the CPU and hardware. Most schedulers were developed to work on desktop kernels that use hdds and different architectures. Unlike desktops, our phones use flash memory. The ROW scheduler was designed to optimize scheduling on flash memory devices.
USB Fast Charge
To use imoseyon's usb fast charge script, you must have BusyBox installed. See his thread for more details.
To turn it on, type in terminal emulator: ffc. Off is the same command. Remember, to give the terminal root access you need to type: su.
Flashing and settling
Keep in mind, kernels need time to "settle" in place. Especially after you just wiped the cache. After your first boot up on the new kernel, use the phone until it loads 100% (as in no "it's still booting up lag" which would be like 5 minutes) and then reboot. Sometimes you don't get optimum usage until after a battery charge or overnight.
For Those Using 64GB SDcards
Those 64GB sdcards are formatted to exFAT by default. exFAT is owned by Microsoft and licensed for Samsung to use. However, Samsung cannot release the exFAT support in their source codes because they are proprietary. There's nothing I can do about that. All you can do is format the sdcard to a supported file system. Plug your phone into your computer, get all your files off the sdcard, and format it to fat32. I have added NTFS support to the kernel, so that is also an option. Neither does fat32 nor NTFS suffer the performance of the cards. With fat32 however, you are limited to 4gb per file.
Galaxy KOR Changelog
v1.0
Initial release.
v1.1
Rebuilt from the ground up on LK3 source code.
Lots of bad coding fixes on my end (I'm getting better at this; I promise).
Added interactive and conservative governor.
Added BFQ hierarchical support (basically more control for the BFQ scheduler.
v1.2
Implemented the undervolt and overclock table.
Removed KSM support (unneeded).
Enabled the block-io cgroup controller for use with BFQ.
Fixed the stupid naming convention thing on the past kernels (the -00009-asdlkfnasd).
v2.0
Fixes. Fixes everywhere.
Readjusted the slow and nominal PVS clock tables for stability.
Trying out some entropy related things (it won't hurt anything even if it's not effective).
Added NTFS support and experimental exFAT support (I'm going to need to some people with exFAT sdcards to help).
More fixes.
Edited the OPs for relevancy.
v2.2
Reconfigured the toolchain and binaries.
Rebuilt linaro with GCC 4.6 instead of 4.7 for stability reasons.
Some optimizations for less lag and more responsiveness.
v2.3
Added the InteractiveX governor from the lean kernel.
Dove into the ramdisk a little.
Added an init.d script to set the minfree values (I will need feedback on this).
Reconfigured the BFQ scheduler.
v2.6
Merged latest linux kernel v3.0.59.
Reconfigured the linaro toolchain (hopefully for the last time).
Modified the voltage tables.
Removed the minfree tweak (it may have been the cause of some people's battery drains. The stock lmk values will suffice).
Patched up some code.
Changed compression mode to LZMA.
v2.7
Merged linux-v3.0.60.
Allotted more L2 cache to 1.62Ghz.
Finalized some optimizations.
Re-implemented the minfree tweak.
v3.0
Started from scratch (getting my github in proper order).
Patched up branches at a time to Linux 3.0.61.
Merged the ondemand governor from CM10.1.
Defaulted the ondemand governor.
Lightened up the kernel modules.
Freed up unnecessary memory resources.
Decided that kernels aren't the place for minfree tweaks (especially via script).
v3.1
Rebuilt with latest linaro release 13.01.
Minor code changes.
Further kernel memory tweaking.
New naming scheme implemented.
v3.2
Merged Linux 3.0.62.
Added the ROW scheduler; updated it; defaulted it.
Vamped the block layer for urgent request handling.
Removed BFQ and CFQ for now (need to fix coding issues with new block layer).
Optimized the VRBLK3 ramdisk.
Added linaro gcc optimization flags.
v3.3
Flagged more gcc optimizations.
Added imoseyon's USB fast charge script (be sure to thank him!).
Set the "high" GPU freq to 420Mhz instead of 400Mhz.
I kept the slow and nominal GPU freq at stock. There should be no more than standard power draw.
Freed more kernel memory resources.
v3.4
Patched up to Linux 3.0.66.
Further optimizations to building code.
Further memory resource optimizations.
Envy Kernel Changelog
r1
Patched up to Linux 3.0.70.
Updated linaro toolchain 13.02.
Patched VRBMB1 source code and ramdisk.
Added pegasusq governor from international s3.
256Mhz cpu freq edit and undervolt.
Just as I was snooping around here looking for a kernel
Sent from my SCH-I535 using xda app-developers app
Gonna try it now bro thanks for your work
Sent from my SCH-I535 using xda premium
Ruining good so far
Sent from my SCH-I535 using xda premium
epicroot said:
Ruining good so far
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Great! Let me know if anything seems amuck. I've been using it on Rem's Executioner ROM and everything seems good. Be sure to set the BFQ scheduler. It should be defaulted, but there's always other factors.
Sent from my SCH-I535 using Tapatalk 2
Rath1on said:
Great! Let me know if anything seems amuck. I've been using it on Rem's Executioner ROM and everything seems good. Be sure to set the BFQ scheduler. It should be defaulted, but there's always other factors.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
That's exactly what I'm running.. Do you know if I'll have issues with the CPU clock settings sticking? On Executioner 2, I can't get them to stick on a reboot.
I use system tuner pro on cleanrom 5.5.1 I can't find how to check on schedulers should I use a different kernel manager app?
Edit: never mind I think I found it. Mine was set at cfq. What's the difference?
Sent from my SCH-I535 using xda app-developers app
This is awesome to see! Gotta love seeing more and more development for our beloved S3!
Sent from my SCH-I535 using xda premium
isn't Rath spelled with a W? Wrath?
which would make this a Kow Kernel.
I clicked on this thinking this was a Korean Kernel... lol.
나이스!
dbornack said:
That's exactly what I'm running.. Do you know if I'll have issues with the CPU clock settings sticking? On Executioner 2, I can't get them to stick on a reboot.
Click to expand...
Click to collapse
It depends on how I set up the clock table. We'll see.
cell128 said:
I use system tuner pro on cleanrom 5.5.1 I can't find how to check on schedulers should I use a different kernel manager app?
Edit: never mind I think I found it. Mine was set at cfq. What's the difference?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You can look up the differences between schedulers with some Google. BFQ aims at divided workload using hierarchy scheduling. I think I'm going to pair it with a form of the interactive governor.
Stran93r said:
This is awesome to see! Gotta love seeing more and more development for our beloved S3!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
jucytec said:
isn't Rath spelled with a W? Wrath?
which would make this a Kow Kernel.
I clicked on this thinking this was a Korean Kernel... lol.
나이스!
Click to expand...
Click to collapse
It's a play on the word core and a play on my name at the same time. I thought it was clever.
Sent from my SCH-I535 using Tapatalk 2
Rath1on said:
It's a play on the word core and a play on my name at the same time. I thought it was clever.
Click to expand...
Click to collapse
It is... :good:
Issues I've been able to reproduce:
- Reboot when video is initiated within an app like Tango, GChat, etc.
- CPU Control FCs 2-3 times before I can get in to check CPU settings
On Executioner 2.0
What are your using to check the CPU settings with? I use ROM toolbox and have had no issues.
I'm not sure what's going on with the video. I don't use video chat, so I can check. Do any other kernels work for it?
Sent from my SCH-I535 using Tapatalk 2
Rath1on said:
What are your using to check the CPU settings with? I use ROM toolbox and have had no issues.
I'm not sure what's going on with the video. I don't use video chat, so I can check. Do any other kernels work for it?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I've had good luck with CPU Control Lite for a long time on multiple phones. But I can give another one a shot.
I've just uses the stock and IMO kernels so far. Those don't give me any issues.
Sent from my SCH-I535 using xda app-developers app
Phone boots up and runs for a minute or so then resets... boots up and runs for a minute or so then resets again... Just stays in that cycle... Tried doing a clean install... Tried flashing stock kernel then KoR... tried installing with absolutely no CPU apps n the phone... Not sure what else to try... Any thoughts?
Samsung Galaxy SIII powered by CleanROM 5.5.2
o0BlacknesS0o said:
Phone boots up and runs for a minute or so then resets... boots up and runs for a minute or so then resets again... Just stays in that cycle... Tried doing a clean install... Tried flashing stock kernel then KoR... tried installing with absolutely no CPU apps n the phone... Not sure what else to try... Any thoughts?
Samsung Galaxy SIII powered by CleanROM 5.5.2
Click to expand...
Click to collapse
I got the same thing on this. Constant reboots. Doing nothing. I tried.
Sent from my SCH-I535 using Tapatalk 2
o0BlacknesS0o said:
Phone boots up and runs for a minute or so then resets... boots up and runs for a minute or so then resets again... Just stays in that cycle... Tried doing a clean install... Tried flashing stock kernel then KoR... tried installing with absolutely no CPU apps n the phone... Not sure what else to try... Any thoughts?
Samsung Galaxy SIII powered by CleanROM 5.5.2
Click to expand...
Click to collapse
Alright, guys. Thanks for the info. I'm looking into it. Running Clean ROM? I'll flash it and check it out. I've been itching to get back to work on it, but this week is a little here, there, and everywhere.
countryfolk07 said:
I got the same thing on this. Constant reboots. Doing nothing. I tried.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Are you running Clean ROM as well?
Sent from my SCH-I535 using Tapatalk 2
Rath1on said:
Alright, guys. Thanks for the info. I'm looking into it. Running Clean ROM? I'll flash it and check it out. I've been itching to get back to work on it, but this week is a little here, there, and everywhere.
Are you running Clean ROM as well?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
No. I am stock odex at the moment.
Sent from my SCH-I535 using Tapatalk 2
Change log:
Included all inazuma r5
Added many governor, i/o schedulers.
Governor: Interactive, interactive pro, impluse, powersave, performance, conservative, smartmax, intelliactive, lionfish, zzmoove, bioshock, yankactive, bluactive, elementalX, ondemand, userspace
I/o schedulers: noop, deadline, row, fiops, sio, sioplus, tripnadroid, cqf, bqf, zen
Hotplug: IntelliPlug, ClusterPlug, Alucard Hotplug, ThunderPlug
Usb fast charge
Sound controler
Adaptive Low memory killer
Powersuspend
OC cpu 1.8 ghz, GPU 650Mhz
DT2W halfscreen, fullscreen
Many TCP.
And many many optimized...
Download: Please go to downloaad tab
XDA:DevDB Information
Chriszuma Kernel, Kernel for the Moto G 2015
Contributors
nguyenquangduc2000, zeeshanhussain12
Source Code: https://github.com/nguyenquangduc2000/chriszuma-msm8916
Kernel Special Features: Dt2w, OC CPU and GPU, many governors and i/o schedulers...
Version Information
Status: Stable
Current Stable Version: V4
Stable Release Date: 2016-06-17
Created 2016-06-17
Last Updated 2016-06-17
Isn't CPU 1.8 GHz cause damage to device ?
Stock ROM supported?
Thanks for your work
Gpu clock speeds are not showing.. just showing 400 mhz and next 0 max.. min is 100 mhz
Source code?
Sent from my MotoG3 using XDA-Developers mobile app
Rahul1608 said:
Gpu clock speeds are not showing.. just showing 400 mhz and next 0 max.. min is 100 mhz
Click to expand...
Click to collapse
What about the CPU overcook, is it actually working?
arindamghosal said:
What about the CPU overcook, is it actually working?
Click to expand...
Click to collapse
Yes working.. But quickly heats up a lot..
nguyenquangduc2000 said:
Change log:
Included all inazuma r5
Add many governor, i/o schedulers.
OC cpu 1.8 ghz, GPU 650Mhz
DT2W halfscreen, fullscreen
Many other features are waiting you to explore.
Download here or you can go to download tab.
XDA:DevDB Information
Chriszuma Kernel, Kernel for the Moto G 2015
Contributors
nguyenquangduc2000, zeeshanhussain12, nguyenquangduc2000
Kernel Special Features: OC cpu, gpu, Dt2w...
Version Information
Status: Stable
Current Stable Version:V4
Stable Release Date: 2016-06-17
Created 2016-06-17
Last Updated 2016-06-17
Click to expand...
Click to collapse
Oh mate really thanks for this, nice performace. The bury_alem governor still crashing the system, maybe you remove it, the others are ok. The GPU's max frequency is 400 MHz, and when The phone turn on it start as 0 MHz. The rest are OK until now. Thanks again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
arindamghosal said:
What about the CPU overcook, is it actually working?
Click to expand...
Click to collapse
Yes it is at 1785 MHz, but don't enable the bury_allen Governor
---------- Post added at 12:28 PM ---------- Previous post was at 12:18 PM ----------
vicky90 said:
Isn't CPU 1.8 GHz cause damage to device ?
Click to expand...
Click to collapse
As he said for surnia kernel, he has already tested. The overclock in Android isn't like as PC, it's a bit different, if some issues happen, the mobile will heats up a bit, probably freezes, and reboot, then you can flash a more stable kernel. This kernel is working ok, just don't enable the Bury_Allen governor
josfer said:
Source code?
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank all of you. I will remove bary allen. Source code will be released after all the issues are fixed.
Update are available to download. Please try and report me if you have any problems.
Update:
-Removed barry allen
-Reconfiged gpu oc
Johny Cipeli said:
Oh mate really thanks for this, nice performace. The bury_alem governor still crashing the system, maybe you remove it, the others are ok. The GPU's max frequency is 400 MHz, and when The phone turn on it start as 0 MHz. The rest are OK until now. Thanks again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
Yes it is at 1785 MHz, but don't enable the bury_allen Governor
---------- Post added at 12:28 PM ---------- Previous post was at 12:18 PM ----------
As he said for surnia kernel, he has already tested. The overclock in Android isn't like as PC, it's a bit different, if some issues happen, the mobile will heats up a bit, probably freezes, and reboot, then you can flash a more stable kernel. This kernel is working ok, just don't enable the Bury_Allen governor
Click to expand...
Click to collapse
Hi,
Nice to know that the cpu overclocking is working, and probably gpu problem and the governor problem will be fixed in the next version hopefully. will try it out then. Does it support modified stock MM rom....??
Arindam
Amazing works.. OC seems really cooolll!!! Bro plejj fix Hard Disk not connecting issue..
Heres the logcat:
logcat.txt
dmesg.txt
last_kmsg.txt
Also if u want log cats of my Redmi and/or tab in which the HDD work, I can provide you..
vicky90 said:
Isn't CPU 1.8 GHz cause damage to device ?
Click to expand...
Click to collapse
No,it works well
Forever Alone said:
Amazing works.. OC seems really cooolll!!! Bro plejj fix Hard Disk not connecting issue..
Heres the logcat:
logcat.txt
dmesg.txt
last_kmsg.txt
Also if u want log cats of my Redmi and/or tab in which the HDD work, I can provide you..
Click to expand...
Click to collapse
I do not own osprey to test. I made it based on its configs. Therefore, I have released source code for any one want to fix this error.
Man, it's strange, the performance didn't increase, before I flash the kernel I had changed from ext4 to F2fs, Is is can influence in this problem?
can you give direct link to the OC commit of cpu & gpu?
Probably broke some records ;D
HelpMeruth said:
Probably broke some records ;D
Click to expand...
Click to collapse
The results here is the same, as if it had not been overclocked. Maybe Inazuma isn't compatible with Overclock
HelpMeruth said:
Probably broke some records ;D
Click to expand...
Click to collapse
Hi I got higher score than that on Optimus R11 kernel,.
Regards
Arindam
If its only pulling 530/1600 on GB3..... its worthless.
I've written extensively and performed hundreds of tests on GB using a half dozen kernels. I've pulled 570+ on single core and 1700 on multi core. Most well built and tuned kernels will average in the 550/1650 range. This Kernel falls flat on its face. As stock Kernels appear to pull about 525-535 single core, and about 1580-1600 multi-core.
The real question is: Does the GPU OC work.
I need some hard numbers to crunch using some graphic benchmarks. Then we'll see.
This is important to know, because I'm about to announce a community project that will crowdsource, and cherry pick the absolute best of the kernels currently in existence. I've long believed that this chip DOES oc, but not as high as 1.8ghz. As squid has shown, you can make it report higher speeds, but not operate at them. 1.4 is provable. Bluspark did 1.6, but theres debate as to whether it actually operated at it. There is NO debate however that the bluspark kernel scored higher than than the 1.4's have, ESPECIALLY on single core benchmarks. I think I've seen as high as 578 with it. This leads me to believe that it *may* be possible to OC the chip to the 1.5 range, before it just stops. Or it *could* be that above 1.4ghz, into the 1.6ghz range there is a disproportional gain in performance due to a)heat, b)inefficiency, or c)both.
The GPU is seriously lacking and without anyone really trying to push the limits until now, its been a mystery as to what it can do. I've seen 650 on the beserk kernel on redmi, but it was plagued by heat with extreme gaming. But users have reported that the 550ish mhz OC was both efficient and effective. So, lets see some real numbers here from some graphics benchmarks.
And to all those that cry and whine, and cry and whine, and yes... cry and whine about battery and heat and poor potty training as a child: go away. You're too far gone to understand that just because its available, you DONT have to use it. What do you guys do when you get into a car thats got 400 horsepower? or use an air conditioner in your home that goes down to 50 degrees? According to your logic, you floor it, until you crash it. Or you die from hypothermia with the latter.
Now..... on to the good stuff. Post your GPU OC vs 400-465mhz scores.
Hello everyone!
Dan asked for ideas for lspeed.
While govtuner is great, maybe hotplugging can also be more optimized.
Govtuner optimizes zzmoove inbuild hotplug but leaves every other hotplug untouched.
Dan wants to start optimization of hotplugging next month and asked me to open this thread to collect your current settings and values.
So if you are interested in optimization of hotplugging, please share your current setup in this thread.
You can post screenshots from KA or just list your available options for hotplug along with the tuneables.
This will be the starting point for the optimization next month.
Best regards
dr.zook
Here are my options for hotplug
@Paget96 Dan, if I have forgotten anything, please tell me
dr.zook said:
Here are my options for hotplug
@Paget96 Dan, if I have forgotten anything, please tell me
Click to expand...
Click to collapse
Thanks for saving my time, what i need. Soon when i grab some time I'll start with hotplug optimizations.
I can't give an ETA or something, but, expect it soon, till then, share your setups and hotplugs.
Thanks for support
Sent from my Nexus 5 using Tapatalk
@Paget96: intelliplug, redmi note 3 pro, exkm
Two more: lazyplug (1st)
and
msm-hotplug
for redmi note 3 pro
Thunderplug :
Alucard :
I would like to report on Hotplug governor, but I have only HTC Desire S which has only single core. So I could not participate anyway. Thanks for you guys kind contribution. Thank you very much.
Blu-plug from blu_spark kernel
my Device is a Nexus 5
We can start filling up this thread again
Sony Xperia Z5 (SoC: Snapdragon 810)
Stock msm hotplug
Tunables path: /sys/devices/system/cpu/
Today I'll start with profiling hotplugs. I'll add three profiles battery, balanced, performance for next hotplugs:
- IntelliPlug
- Blu_Plug
- MSM Hotplug
- Mako hotplug
- AutoSMP
Device: Nokia X2
godspeed85 said:
Today I'll start with profiling hotplugs. I'll add three profiles battery, balanced, performance for next hotplugs:
- IntelliPlug
- Blu_Plug
- MSM Hotplug
- Mako hotplug
- AutoSMP
Device: Nokia X2
Click to expand...
Click to collapse
That's RR???
Sent from my Nexus 5 using Tapatalk
Paget96 said:
That's RR???
Click to expand...
Click to collapse
Are you asking about the rom?
godspeed85 said:
Are you asking about the rom?
Click to expand...
Click to collapse
Yes, is that Reconstruction Remix?
Paget96 said:
Yes, is that Reconstruction Remix?
Click to expand...
Click to collapse
Yes. Resurrection Remix
Althrough this is not probably the thread to ask it . Do you guys by chance use any hotplug which has a freq limit to turn on the cores? Since it seems most hotplugs turn on the cores when the highest freq hits and I'm not that happy about it.
EvilMegaDroid said:
Althrough this is not probably the thread to ask it . Do you guys by chance use any hotplug which has a freq limit to turn on the cores? Since it seems most hotplugs turn on the cores when the highest freq hits and I'm not that happy about it.
Click to expand...
Click to collapse
Well blu_plug do it based on threshold.
Paget96 said:
Well blu_plug do it based on threshold.
Click to expand...
Click to collapse
Most of them do it based on threshold. Found some which do it based on freq buts it seems thats its a pain to port them. I asked some dev about what do they think of hotplug on newer device and it seems its useless now