Database Users

[Kernel][CM7][July 12]Le kernel du jour Build #6

DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY HARD OR SOFTWARE BASED DAMAGE. IF YOUR PHONE BRICKS, YOU LOSE IMPORTANT DATA, OR OTHERWISE INCUR LOSSES AS A RESULT OF RUNNING THIS KERNEL, ITS NOT MY FAULT.
THE LATEST NIGHTLIES HAVE BEEN REMOVING VOLTAGE CONTROL STATS, SO PLEASE REMOVE ALL OVERCLOCKING BEFORE FLASHING A NIGHTLY OR AN UPDATE FROM HERE.
This is a CM7 based kernel with a 1.6 Ghz overclock, Voodoo sound and color fixes, uv support, and BLN. See the changelog for all the updates and features.
Informations (THESE CHANGE ON A REGULAR BASIS):
1. Max clock is set to 1GHz on the first boot, set the max clock in CM settings or voltage control or setCPU.
2. I cannot possibly stress this enough. IF YOU EXPERIENCE BUGS WHILE ON THIS KERNEL, POST HERE. Do NOT submit bug reports to the CM team, until you have flashed back to stock CM, and can verify the bug exists there too.
3. To undervolt, use either Voltage Control, SetCPU, or Control Freak.
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to have feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/android_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not an error. Don't freak out. Let it boot.
Thanks to Netarchy for his Nexus S oc code, coolhbo for setCPU, the CMSGS team for their work, Supercurio for Voodoo, raspdeep for his oc/uv patches(showed me how to create a sysfs interface for uv), Xan for the uv app, neldar for BLN, and cyanogen for his amazing rom.

CHANGELOG:
V1:
Initial release
V2:
Voodoo Sound v4 added!
v2.2
Fixed the OC bug from v2
Fixed the OC bug from (the unreleased) v2.1
Added some initial testing code for UV!
Removed v2 from the downloads
Added a stock kernel to downloads
v2.3
Added wifi sleep workaround from coolya
v2.4
Updated to be in sync with the official releases
Removed some debug code (coolya)
Added compatibility with the cpusettings in CMparts(coolya & atinm) (Only works under updates after march 04 update, as it requires code in the actual rom.)
v3.0
Added compatibility with Xan's uv app!
v3.1
Added the new wifi sleep fix
Fixed the uv bug (hopefully)
Removed v3
v3.2
updated to stay in sync with the 03122011 nightly
yas259 fixes(don't ask me about these, this driver is way over my head)
radio fixes(not ril polling)
config edits
v3.3
updated to keep in sync with the 20111303 nightly
Lots of little tweaks
-kernel hz = user hz =100
-update timings (Thanks Kang)
-enabled Tiny RCU
Removed the returntostock kernel
v3.4
Updated Voodoo sound to v5
Implemented voodoo color v2
v3.5
Updated Voodoo sound driver number to v5 (now the control app says 5)
Added 600mhz and 1.3Ghz steps
Added interactive and smartass cpu frequency governors
Some initial work on BLN (disabled)
Added frequency_voltage_table for compatibility with custom frequencies in the uv app (disabled due to bugs)
v4.0 - (BUGGY, BETA RELEASE)
Increased voltage on 600mhz and 1.3ghz steps (let me know how this affects stabilty, guys)
Implemented BLN (VERY EXPERIMENTAL AND BUGGY)
Added states table to Voltage Control app that doesn't actually do anything.
Added Atimn/eifert's fix for the bad block issue.
v4.1
Fixed the stability issue on 1300mhz (Big thanks to kang for his help)
Added in the cardock fixes from xcaliburinhand (grab the "DockSound Redirector" app from the market)
fixed the ?mv bug in voltage control
Fixed bln (thanks to neldar)
Added 1000hz version of the kernel
Did a few tweaks to smartass, it's still kinda sketchy though
Updated voodoo sound to v6
There's probably more, I just can't remember them.
v4.2
More stability tweaks on 1300mhz
-The voltage for 1300mhz is now the same as 1200mhz, so you won't be able to undervolt it as much in the app, but it seems to help with stability.
Latest bln from neldar (fixes the touchkey disabled bug, and the touchkey on during sleep bug)
Enabled the microphone presets for voodoo sound
v4.3
Added 1400, 1500, and 1600mhz steps
Updated voodoo sound v7 (very little feature changes though)
Unlocked FPS cap
Built on latest upstream code (pulls in all fixes in recovery, etc. If people are still having bad block issues, let me know)
v4.4
Disabled some debug code
Fixed the ?mv bug on 400, 200, and 100mhz steps in voltage control
Fixed up smartass
Integrated the sdcard r/w cache fix (Thanks to Existz for pointing it out)
v4.5
Upstream fixes:
-New wifi driver
-New kernel flashing method, which should help bad block people
-Dual sd card sharing
Added a time that a frequency must stay at before scaling up in smartass
- You can tweak it same way as you can tweak all the other settings, its ramp_up_rate_ns
v4.6
Upstream fixes:
- Lots of random JVB merges, code clean up, etc.
Fixed the notification bug crash on the first v4.6
v5.0[May 3]
- Extend battery polling to 15s
- Sched_autogroup patch (increases smoothness under heavy load)
- New bootlogo
- Fix setCPU crashing on screen off
-Unified HZ (256) (should increase battery life, and has no adverse effect on performance)
- Reunlock fps cap
-Switch to the Codesourcery toolchain (should result in faster/smoother code)
-Full compatibility with 2.3.4
v5.0b[May 4]
-Fixed touchkeys for real this time
-Temporarily enabled debugging (will be disabled in the next update)
-Fixed the crazy battery stats
-Reenable smartass governor
v5.1[May6]
-Lots of upstream gpio changes
-Camera drivers kanged from JVB (REQUIRE THE LATEST NIGHTLY TO WORK)
- -03 optimizations
- Switched to hardware based floating point calculations (seems to increase performace under certain loads)
- Dropped 1.6ghz to 1.55ghz (Something for you to shoot for, Shaolin. )
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-Upsteam changes to modem_ctl
-Upstream tvout drivers (Totally untested on my end, so i dunno if they work)
-fsa usb switch suspend
-Overvolting cap
-add the kernel version (v5.2) to the kernel name.
v5.3[May 16]
-Upstream changes to initial flash/initramfs
-Upstream changes to battery calculation percentage
-Some other stuff, nothing really important. Its all upstream changes anyway.

NIGHTLIES/WHENEVERS:
#1[May 25]
+Working ril (data + service)
+working gps
+switched to mfloat=softfp as it gives slightly higher linpack scores
+Voodoo sound v9
+LZO compression for a faster boot up time.
Known bugs:
Rild crashes in areas with no service, causing a hard reboot. (Can anyone tell me if this happens on the stock kernel?)
#2[May 27]
+Actually working ril (no more reboots)
+Optimized for size
+Updated to 2.6.35.13 kernel (No, I dont have a changelog. There is one on the internet somewhere. Needless to say, its huge.)
+Probably some other stuff.
Known bugs:
Bln is finicky on this build, try reflashing/rebooting if it doesn't work at first.
#3 [May 29]
+States table in voltage control kinda works, but is buggy.
+disabled ext2
+re-added 1.6Ghz with a higher voltage (be careful guys).
+upped 1.55ghz by a few Mhz so it should be one or two above rather than below.
#4 [June 4]
+Disabled the states_enabled_table again, cause voltage control was really sketchy about keeping the states properly enabled. Hopefully the new rewrite will help.
+Fascinate support
#5[June 28] UNTESTED
+All upstream merges
+GPU bus clock speed modifiable using Control Freak
+Other stuff that I can't remember or have time for
#6[July 12]
+Upstream changes
+Fixed BLN (For whatever reason, it won't work after booting into recovery. Do a normal reboot, and it'll work).
+Reenabled the debugging, cause it was causing issues

This is nice!! Waiting for Voodoo fixes!

So can we flash back to original cm7 kernel after this using odin?
Sent from my SGH-I897 using XDA App

chipsa964 said:
So can we flash back to original cm7 kernel after this using odin?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe you need to use the cm7-update.zip file to install the original cm7 kernel - unless there is a .tar cm7 kernel?

born_fisherman said:
I believe you need to use the cm7-update.zip file to install the original cm7 kernel - unless there is a .tar cm7 kernel?
Click to expand...
Click to collapse
There is, but it doesn't fix everything g that is necessary. You need the update zip.
Sent from my CM7 powered captivate

It'd be great if you can integrate BLN into the kernel as well!! Running kang's voodoo color/sound right now, but who ever comes out with a BLN kernel will have my full attention(and of many other people I imagine judging by the posts on the CM forum)!!

boardsportsrule said:
It'd be great if you can integrate BLN into the kernel as well!! Running kang's voodoo color/sound right now, but who ever comes out with a BLN kernel will have my full attention(and of many other people I imagine judging by the posts on the CM forum)!!
Click to expand...
Click to collapse
yes please 1+ for BLN.
That being said with Voodoo fixes soon to be intergrated, and hopefully UVing Im watching this thread closely.
And when we do flash this would we have to do anything differently? Or just flash it over the current set up via CWM like any other ROM.
Thanks and great work so far.

Would these recent captivate cm7 voodoo kernel be helpful to integrating voodoo into your oc kernel?
http://kang.project-voodoo.org/

Voodoo sound is almost done, either tonight or tomorrow. Then, ill look at making this compatible with xan's UV app. Bln is probably going to be last, as it looks like the most work. There is currently no bln for any nexus s kernel, so ill have to see if it'll work.
Sent from my SGH-I897 using XDA App

Dlev7 said:
yes please 1+ for BLN.
That being said with Voodoo fixes soon to be intergrated, and hopefully UVing Im watching this thread closely.
And when we do flash this would we have to do anything differently? Or just flash it over the current set up via CWM like any other ROM.
Thanks and great work so far.
Click to expand...
Click to collapse
Yeah, just flash it over top.
Sent from my SGH-I897 using XDA App

This might seem like a pretty hefty request, but what are the chances that you can implement MKV splitting into the kernel? I wouldn't expect the kernel to be the route to getting MKV support on a device, but apparently developers for the Advent Vega Android Tablet have done exactly that. H.264 acceleration on a device that supports the stream should work no matter the container as long as something else in the chain parses the container first.
I'm not sure about licensing issues though, but it seems that a device that came with support for the MKV container (pretty much all Samsung devices, even their TV's and Bluray players) shouldn't be in violation of anything if it's running a custom ROM that contains the same functionality. Or maybe we'll have to wait for a Samsung Gingerbread source and create a Samsung-CM7 Frankenstein project?
Not being able to play my library of 720p MKV's with embedded softsubs without remuxing (and remuxing to mp4 still doesn't support embedded softsubs) on my Captivate is a dealbreaker keeping me away from CM7, but the other features and the possibility of syncing a Wiimote to control the new N64oid emulator is still very appealing

GGXtreme said:
This might seem like a pretty hefty request, but what are the chances that you can implement MKV splitting into the kernel? I wouldn't expect the kernel to be the route to getting MKV support on a device, but apparently developers for the Advent Vega Android Tablet have done exactly that. H.264 acceleration on a device that supports the stream should work no matter the container as long as something else in the chain parses the container first.
I'm not sure about licensing issues though, but it seems that a device that came with support for the MKV container (pretty much all Samsung devices, even their TV's and Bluray players) shouldn't be in violation of anything if it's running a custom ROM that contains the same functionality. Or maybe we'll have to wait for a Samsung Gingerbread source and create a Samsung-CM7 Frankenstein project?
Not being able to play my library of 720p MKV's with embedded softsubs without remuxing (and remuxing to mp4 still doesn't support embedded softsubs) on my Captivate is a dealbreaker keeping me away from CM7, but the other features and the possibility of syncing a Wiimote to control the new N64oid emulator is still very appealing
Click to expand...
Click to collapse
Well, I'll keep an eye out for anything that might factor into that, but between having other, more crucial features that need to go in first, and knowing next to nothing about video codecs, I can't promise anything. Sorry.
Also, I'm pretty sure I've got voodoo sound in there, but the cm build system is messed, so I haven't been able to build a working kernel or rom all day. Once builds are working again, do people want me to start posting "nightly" builds in here too?
Sent from my SGH-I897 using XDA App

merging voodoo sound and color is fairly simple. you just have to "git pull git://github.com/project-voodoo/linux_samsung.git nexus-s-voodoo" and compile. the pull command automatically changes the content of each file that's different between your local files and supercurio's branch files. i hope this makes it easier for you.
Sent from a phone, playing a phone, disguised as another phone.

slifer315 said:
merging voodoo sound and color is fairly simple. you just have to "git pull git://github.com/project-voodoo/linux_samsung.git nexus-s-voodoo" and compile. the pull command automatically changes the content of each file that's different between your local files and supercurio's branch files. i hope this makes it easier for you.
Sent from a phone, playing a phone, disguised as another phone.
Click to expand...
Click to collapse
Sadly, no. the cm kernel isn't a stock nexus kernel, theres a lot changed. Even if I could some how merge in just sound and color, there would probably still be issues.
I was actually planning on implementing voodoo color last, because theres still so much work bring done on it. I figured once I got everything else in there, it would be further along.
Also, this is partly a fun learning project for me, manually patching files is my kind of fun.
Sent from my SGH-I897 using XDA App

TheEscapist said:
Sadly, no. the cm kernel isn't a stock nexus kernel, theres a lot changed. Even if I could some how merge in just sound and color, there would probably still be issues.
I was actually planning on implementing voodoo color last, because theres still so much work bring done on it. I figured once I got everything else in there, it would be further along.
Also, this is partly a fun learning project for me, manually patching files is my kind of fun.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
actually there aren't any issues. I've been using a kernel I built after the pull for several days now.
Sent from a phone, playing a phone, disguised as another phone.

TheEscapist said:
Well, I'll keep an eye out for anything that might factor into that, but between having other, more crucial features that need to go in first, and knowing next to nothing about video codecs, I can't promise anything. Sorry.
Also, I'm pretty sure I've got voodoo sound in there, but the cm build system is messed, so I haven't been able to build a working kernel or rom all day. Once builds are working again, do people want me to start posting "nightly" builds in here too?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Of course. MKV support is definitely not a primary feature of a kernel, but it sure would be nice. Also, I'm not talking about a codec, I'm talking more of a demuxer that simply streams the H.264 and audio streams as if they weren't inside the MKV so the hardware could play them like any MP4 (kind of like an Android equivalent of Haali Media Splitter).

I'm giving this a try...i really like the fact that I can choose how my cpu scales....hoping it helps battery life a little...also looking forward to you adding uv...
Sent from my Captivate using XDA App

Testing now. While I'm not particularly interested in the OC, the fact that you're using SetCPU and it's working makes me want to see if I can UC this. The default kernel doesn't play too well with this.

[KERNEL] [AOSP] leanKernel: minimalistic kernel (v5.1.0, 11/16/11)

This is a minimalistic Thunderbolt kernel based on the official gingerbread kernel source, patched to 2.6.35.14, and then a bunch of lean mods added (look at feature list below).
DOWNLOADS:
1) lean (normal lean version), 1) 184Mhz (184Mhz can be unlocked via st - note for many people 184Mhz is unstable and cause issues, also supports outgoing call recording)
speedtweak.sh
This script will allow you to "transform" your kernel into normal, extreme, 1.92, 1.92X and battsaver versions (ie. it allows you to control speed, voltage, and slots to a certain degree). Once you run the script, everything will be self-explanatory. To run the script:
1) Open Terminal Emulator (install it from market if you don't have it).
2) Type "su" (without quotes) and hit enter.
3) Type "speedtweak.sh" (without quotes) and hit enter.
leanKernel kernel speed tweaker
------------------------------_
1) normal: undervolted, overclocked to 1.41Ghz
2) extreme: extremely undervolted, overclocked to 1.41Ghz
3) 1.92: undervolted, overclocked to 1.92Ghz
4) 1.92X: extremely undervolted, overclocked to 1.92Ghz
5) battsaver: extremely undervolted, not overclocked
6) Unlock 184Mhz
7) Lock 184Mhz
8) View current settings
Please type 1, 2, 3, 4, 5, 6, 7, or 8:
Click to expand...
Click to collapse
speedtweak.sh and SetCPU
The risk of running setcpu is that it can inadvertently override the min and the max that were set by the speedtweak script. (oh it can also override the governor setting but that's not as bad). Other than that it's pretty harmless - it can't mess with the voltage settings. So if you're going to use SetCPU, keep this in mind. One way to make this work is to use SetCPU to configure governor and min/max, and use speedtweak.sh to configure voltage settings. Or just don't use SetCPU.
FEATURES
Includes lots of goodies from kernel source (2.6.36.x & 3.x from kernel.org) newer than stock.
speedtweak.sh script to adjust clock frequencies and voltages.
SVS - manual voltage tweaking via /etc/init.d/01vdd_levels
InteractiveX and ondemandX governors! Added my own suspend code to interactive and ondemand code to make the phone lock at low clock speed when screen is off. No need for sleep setcpu profile anymore.
For 1.92Ghz builds, interactiveX and smartass governors were modified to minimize unnecessary spikes above 1.8Ghz to keep phone stable.
vm, minfree, memory, buffers readahead buffer tweaks
All unnecessary kernel components removed to make kernel lean and fast!
low # (5-10) of cpufreq slots for simple management and less governer transitions.
Undervolted for longer battery life.
SWAP and EXT4 enabled.
Filesystems mounted via EXT4, and tweaked for performance.
init.d enabled in ramdisk
TUN, CIFS, NSIO (netspector) module support
zram (from linux 3.1) module support (to enable, go into Terminal, type su, and then type "zram enable" without quotes). What is zram?
TINY_PREEMPT_RCU.
CHANGELOGS
4.2.0 (10/28/11) - last "stable" kernel based on cm7 source.
5.0.0 (10/29/11) - based on official kernel source from HTC.
5.0.3 (11/1/11) - bluetooth, video playback, scaling frequencies sysfs all fixed. audio levels tweaked. netspector(nsio) module upgraded to 2.0.
5.0.4 (11/13/11) - 5.0.3 with audio levels reverted stock for better compatibility with MIUI (no need to upgrade from 5.0.3)
5.1.0 (11/16/11) - cpufreq and cpuidle updated to linux v3.2rc1, suspend support for LTE, 184mhz version supports in-call recording now (outgoing only).
DIRECTIONS
Uh.... flash the zip in clockworkmod. You may need to wipe Dalvik cache and/or delete /data/misc/dhcp, /data/misc/wifi.
Donate to your favorite charity, or donate to me.

GOVERNORS
First, my take on the governors that are out there: http://forum.xda-developers.com/showpost.php?p=13020648&postcount=617
I offer three governors: interactiveX, ondemandX, and smartass. What are they?
interactiveX - it's the interactive governor from CM, but I added suspend/wake logic so when the phone screen is off it runs at below 400Mhz. Also, I modified its code some more to minimize unnecessary cpu spikes above 1.8Ghz if you happen to be running one of my 1.92 kernels. Most tbolts are unstable above 1.8Ghz, and it's the quick jump above 1.8Ghz that usually locks up the phone. It will hit 1.92Ghz only when it makes sense (ie. sustained high load). This is my favorite governor - perfect combination of speed and power efficiency.
ondemandX - ondemand governor code from latest linux source *plus* the suspend/wake logic described above, except it has the ability to ramp to 369Mhz while screen is off. No additional code was added for stabilizing above 1.8Ghz.
smartass - smartass code from erasmux, but I wasn't happy with its performance so I tuned it for quicker ramp up in speed. It has the same suspend/wake logic as ondemandX, and the same >1.8Ghz stabilizing mod as interactiveX.
Source code
AOSP: https://github.com/imoseyon/leanKernel-tbolt-gingerbread/tree/aosp
AOSP FAQ
Wifi is not working - 1) first make sure you flash kernel via CWR, not kernel manager or rom manager, 3) clear dalvik cache, 2) delete all files in /data/misc/wifi and /data/misc/dhcp, and reboot.

Imoseyon said:
Thread split into GB and Froyo. "
Click to expand...
Click to collapse
finally took my advice huh???? lol
good work, flashing now!

Whats the change log on 2.5.3test2 ?
Will that work on cm7?

Great work as always! Very impressed!
Sent from my ADR6400L using Tapatalk

well we need to run scripts to over clock gbtest kernel like the previous ones for froyo and cm7

psicrest said:
Whats the change log on 2.5.3test2 ?
Will that work on cm7?
Click to expand...
Click to collapse
he's working on changelog and the 2.5.3 test 2 kernel is only for the "gingersense" leak...for cm7 flash the AOSP kernel
by default the 2.5.3 kernel will run at 1408mhz in "normal" mode

Awesomeness...finally able to boot all the way up...running battsaver...and confirmed camera is working...thank you imoseyon!!!

Saweeeet!!!!
I'll check back later with my experiences running

This may have fixed the slow charge issues inadvertantly. its not in your change log but either this (test2) or 1.3 on jcases build fixed it.
Sent from my ADR6400L using XDA Premium App

arcanexvi said:
This may have fixed the slow charge issues inadvertantly. its not in your change log but either this (test2) or 1.3 on jcases build fixed it.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
This new kernel fixed the slow charge for you or updated jcase gbread rom? I did both and my phone refuses to charge.
Sent from my ADR6400L using XDA Premium App

I don't know if this was posted before, so i apologize if it has;
Here are my questions;
How can having the 184 slot unlocked be worse? (I saw this posted with no explanation in the old thread)
I've used all governors on batt saver and all run smooth as butter, so which will give me best battery life? I understand interactiveX is for performance and efficiency, smartassx and ondemandx are both kinda similar.....
I adjusted the voltage to the lowest values that my phone could handle but my battery life was worse than before.....
Excuse my noobishness

Ok full change logs for v2.5.2test2 sense:
v2.5.3test2 (5/19/11) - fixed BT, backported usb stuff from ace kernel including otg, changed overclock/undervolt to safer values.
gonna work on wifi tethering today.

nerogold said:
This new kernel fixed the slow charge for you or updated jcase gbread rom? I did both and my phone refuses to charge.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
That is weird, mine charges fine. I'll try to look at this today.
Derrtydozen said:
I don't know if this was posted before, so i apologize if it has;
Here are my questions;
How can having the 184 slot unlocked be worse? (I saw this posted with no explanation in the old thread)
I've used all governors on batt saver and all run smooth as butter, so which will give me best battery life? I understand interactiveX is for performance and efficiency, smartassx and ondemandx are both kinda similar.....
I adjusted the voltage to the lowest values that my phone could handle but my battery life was worse than before.....
Excuse my noobishness
Click to expand...
Click to collapse
Sometimes extreme undervolting can do more harm than good. If your phone is not getting enough juice then it can have unpredictable results. Try bumping up voltage to see if it helps.

Imoseyon said:
Ok full change logs for v2.5.2test2 sense:
v2.5.3test2 (5/19/11) - fixed BT, backported usb stuff from ace kernel including otg, changed overclock/undervolt to safer values.
gonna work on wifi tethering today.
Click to expand...
Click to collapse
I've been waiting to flash this until the camera and USB issues were sorted out.
The GingerJane thread says "PSCII.apk (chingy) - fixes usb mounting with custom kernels"
...does this mean that I need to flash that file to fix USB mounting or is it already fixed on YOUR v2.5.2test2?

Natef53 said:
I've been waiting to flash this until the camera and USB issues were sorted out.
The GingerJane thread says "PSCII.apk (chingy) - fixes usb mounting with custom kernels"
...does this mean that I need to flash that file to fix USB mounting or is it already fixed on YOUR v2.5.2test2?
Click to expand...
Click to collapse
So turns out USB mounting wasn't really broken with the kernel. There's some compatibility issues with the leak connect to pc app. You'll need the new PSCII app for usb mounting to work. Both jane and gingeritis should have the new apk now.

How many are experiencing.lockups and random reboots with his kernel? I hope I'm not alone...
I thought it was just the radio but once I switched to the stock.kernel everything was fine and dandy
Sent from my ADR6400L using XDA Premium App

Imoseyon said:
So turns out USB mounting wasn't really broken with the kernel. There's some compatibility issues with the leak connect to pc app. You'll need the new PSCII app for usb mounting to work. Both jane and gingeritis should have the new apk now.
Click to expand...
Click to collapse
Nice. So install the APK and then reboot and flash the kernal and everything should be good?
How close is the kernal to the stock one in the GB leak? I have been getting decent performance and great battery life, hoping that doesn't change with the new one.

How about the wifi tethering issues?

Will the swap enabler work properly with the GB Sense Test Kernel??
Sent from my ADR6400L using XDA App

[Q] cpufreq parameters without using 3rd party apps

Hello.
I've got a stock Android 3.2.1 (A501 4.066.29 COM GEN1) rooted with Stock/HV/Taboonay V3.7 for HC 3.2 16-10 - 1.64Ghz/UV control kernel.
The question is:
how to set cpufreq parameters (governor, max_freq,..) WITHOUT using 3rd party apps so that the parameters were restored after reboot.
Thank you for reading this.

Either the kernel needs to support init.d scripts or a service needs to execute on boot.
That kernel doesn't support init.d and Voltage Control has a startup service.

CuriousTech said:
Either the kernel needs to support init.d scripts or a service needs to execute on boot.
That kernel doesn't support init.d and Voltage Control has a startup service.
Click to expand...
Click to collapse
Forgive my ignorance but I can't put to use your answer.
I don't get where is Voltage Control and what I have to do.

Get Voltage Control from the market, make adjustments, save as boot. You'll be given the option to save as init.d script or startup service.

Well.. I tested it. Odd app.
First of all it can see only one core. It's funny. After reboot cpu0 works in conservative mode, max_freq 1.4 GHz and cpu1 in ondemand mode, 1.0 GHz.
I tried to edit init.d script and add the 2nd core but after reboot cpu worked with the default kernel values - script didn't work at all.
Moreover Voltage Control shows voltages turned upside down - the less cpu frequency the bigger voltage values. I fear to use this app

Download setcpu or antutu cpu master it recognizes dualcore , has the boot option

More education would be advised To you PLEASE DONT BREAK YOUR TABLET
Please do not take this the wrong way..
it does sound like you do not know what your doing.. I suggest you read more about over clocking./under voltage of a TEGRA 2 DEVICE.. That will get you more understanding about what you need to do. And maybe even help you decide if you really want to do this or not.. There is alot of resources online about this subject. I have tried custom kernel with set cpu.. I use it on my 650 mhz phone. clock it to 768. but it has a huge battry issue when running at that speed.Not to mention It would be dangerous to leave it on my purse with something running might be a fire bug.. GOOD LUCK .

Basically lower voltage at higher frequencies keeps the CPU stable. Leaving it linear would increase temperature exponentially.
Script Manager can run scripts on startup but I don't know how you could disable them if they keep it from starting up.
I didn't know about VC and dual core though. My bad.

ef1x said:
Download setcpu or antutu cpu master it recognizes dualcore , has the boot option
Click to expand...
Click to collapse
Thank you.
I tried all cpu related apps from the Market that I was able to try. Now I want to try to get along without them.

erica_renee said:
Please do not take this the wrong way..
it does sound like you do not know what your doing.. I suggest you read more about over clocking./under voltage of a TEGRA 2 DEVICE.. That will get you more understanding about what you need to do. And maybe even help you decide if you really want to do this or not.. There is alot of resources online about this subject. I have tried custom kernel with set cpu.. I use it on my 650 mhz phone. clock it to 768. but it has a huge battry issue when running at that speed.Not to mention It would be dangerous to leave it on my purse with something running might be a fire bug.. GOOD LUCK .
Click to expand...
Click to collapse
Thank you Erica

I don't understand? You want something that does the same thing but you don't want to know it's there?
I found one app called System Tuner that lets you adjust CPU frequencies individually. I don't know why though.

CuriousTech said:
Script Manager can run scripts on startup but I don't know how you could disable them if they keep it from starting up.
Click to expand...
Click to collapse
Thank you but it looks too bulky for such a small task. And I still don't want to use 3rd party apps

CuriousTech said:
I don't understand? You want something that does the same thing but you don't want to know it's there?
I found one app called System Tuner that lets you adjust CPU frequencies individually. I don't know why though.
Click to expand...
Click to collapse
Actually I don't like how these apps work. And I thought that setting up a few parameters would't be difficult. It seems I was wrong.

Yep. Code has to execute to do stuff, otherwise that stuff doesn't get done.

System Tuner Pro allows voltage adjustments on overclock settings. If you're interested. Also, has a lot of packages integrated into one (task manager, app freezer, etc). They have a free version in the Market if you're interested. It's nice to have several apps, in one nice package.

Moscow Desire
Thank you but I actually don't need it anymore
I have rolled back to the stock kernel because of constant "sleep of death" issue.

huck_d said:
Moscow Desire
Thank you but I actually don't need it anymore
I have rolled back to the stock kernel because of constant "sleep of death" issue.
Click to expand...
Click to collapse
It's because the 3.7 kernel you used, is really not compatible with the a501. The ultra-low voltage causes "screen freeze" and the "sleep of death" when under 3g only. It's a known issue with the 501 and 3.6 and 3.7 kernels also. I would reccommend RTrips 3.4+. Probably his best for for a501.
I ship it with my own Alexandra II and III rom. No issues with it, and none ever reported.
Had I noticed when I woke this morning, you had an a501, I could have given this advice. Sorry, didn't have enough coffee
---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------
Moscow Desire said:
It's because the 3.7 kernel you used, is really not compatible with the a501. The ultra-low voltage causes "screen freeze" and the "sleep of death" when under 3g only. It's a known issue with the 501 and 3.6 and 3.7 kernels also. I would reccommend RTrips 3.4+. Probably his best for for a501.
I ship it with my own Alexandra II and III rom. No issues with it, and none ever reported.
Had I noticed when I woke this morning, you had an a501, I could have given this advice. Sorry, didn't have enough coffee
Click to expand...
Click to collapse
The problem, is that a lot of dev's, don't have a501's, only a500's. So they really can't test a lot on it. And sometimes, the issue doesn't happen for 2 or 3 days. Sometimes less. I'm going to experiment a little this weekend, with some of the newer kernels, and mess with the voltage's and see if I can get it stabilized where it doesn't freeze on 3g only.

Moscow Desire ,
Thanks for clearing it up and the advise. I'll try either 3.4 kernel or your ROM.

huck_d said:
Moscow Desire ,
Thanks for clearing it up and the advise. I'll try either 3.4 kernel or your ROM.
Click to expand...
Click to collapse
If you go to RichardTrips kernel thread, you will see a link to his older kernels.
You will find the 3.4 listed on his server. I think you just need to flash it, although I usually dump Dalvak cache.
Alex II is an easy install. Alex III (3.2.1) is a little more ... interesting to install, but not difficult. If you run into an issue, post it in my thread. Everybody else has got it installed, so I think you'll have no issues either.
It's the only "certified" 3.2.1 for the Acer a501 that I know if. Not that the other roms are bad, because they really are good, but, the 3.2.1 they advertise, are from system dumps after running an update, or adding missing files to a 500 rom. The TMPL is an Acer release.

Phone slow after root

I rooted and am running tek s ROM. The phone has been super laggy and slow since I flashed that ROM. Any advice.

Have you switched the governor to interactive or on-demand? That's the most important piece. The below link has a bunch of tips (universal to qualcomm/US S7 and S7e) to improve performance.
http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039

pitbullmommy45245 said:
I rooted and am running tek s ROM. The phone has been super laggy and slow since I flashed that ROM. Any advice.
Click to expand...
Click to collapse
Check the thread under Guides about common problems and fixes.

I did but I didn't see a fix for this. I did what another member told me to do and it worked.

pitbullmommy45245 said:
I did but I didn't see a fix for this. I did what another member told me to do and it worked.
Click to expand...
Click to collapse
Bug #1: Phone is laggy after rooting the phone/Battery is down the tank.
Fix: The phone is (partially) lagging because the ENG bootloader automatically sets the CPU governor to "Performance." While this is supposed to lock the CPU frequency at the maximum values, it does cause a lot of heat and possibly throttling. Additionally, the max core clocks are set to 1.593Ghz instead of their actual maximums. Not every CPU Tuner will allow you to set the big cores separately, so look around for one that does if you don't want to use Kernel Toolkit.
First, use Flashify to flash one of two zips provided by psouza4 on our sister Verizon Galaxy S7 (Edge) threads.
1. Kernel fixes & tweaks V15
2. Kernel fixes, tweaks, & Debloater
You need only flash one of these two zips. One additionally debloats the system, one does not. Choose whichever suits your needs.
What the zips do:
CLICK TO SHOW CONTENT
Next, install a CPU Tuner utility like Kernel Toolkit, then change the governor from "Performance" to "Interactive." Also change the max CPU frequency of the little cores to 1.593Ghz and the big cores to 2.150Ghz while you're at it. Leave the cores at their default minimum frequency. This will go a long way to improving the speed of the phone. Also make sure you that have the new settings to apply on boot. Every kernel manager should have this option somewhere.
Note: Although the max frequency in the settings screen will drop to some number, as long as you can see the CPU ramp up to the new settings in the information screen, then everything is fine. You can test the max frequency by turning the screen off and then back on.
Then, install sEFix and set entropy to "Ultra."
Lastly, install L Speed and:
Code:
-Main Tweaks: Turn on
-Battery Improvement
-OOM Killer
-Kernel Tweaks - "Light"
-CPU Tuner: Turn on
-CPU Optimizer
-LNET Optimizer: Turn on
-Google DNS
-Faster Streaming
-Faster Dormancy
-IO Tweaks: Turn on
-IO Boost
-Partition Remount
-RAM Manager
-Balanced
-Seeder
-Moderate
Literally the first bug and fix on the guide.

[Kernel][3.0.101] Chrono Kernel Refresh R4.6.2

Custom kernel for Samsung Galaxy S Advance
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
​Hi there!
Because of numerous issues found in 3.4.113 kernel, I'm temporarily moving to development on 3.0.101 base.
What is difference between chrono kernel (CK) and CK refresh build? CK was mostly tested on MM-based ROMs, but appeared not to work stably on Android 4.4.x. Aim of this build is to properly enable support for older ROMs (like kitkat), and when done, merge these changes to 3.4.113 kernel.
This build is based upon chrono kernel r4.1 build, so to avoid versions confusion, I'm creating a separate topic.
Features:
CPU, GPU and DDR OC support
more governors and I/O schedulers
Lite kernel - some kernel features moved as modules
F2FS support
ABB-charger tweaks
many others features and tweaks...
Credits:
@dh.harald and @hafidzduddin for contribution on U8500 platform sources
@ Team Canjica for a base for this kernel
@ Nova Fusion for F2FS implementation
@zwliew for contribution on TC kernel
@cocafe for LiveOPP, GPU OC, abbamp and abb-charger tweaks and many cool patches which I've used from his kernel
@faux123 for dynamic Fsync implementation
@Christopher83 for dynamic management of dirty page writebacks implementation
@KINGbabasula for contribution on TC kernel sources
@boype for SIOPlus tweaks and OndemandPlus governor
@Adi_Pat for abbamp, kernel tweaks
@PolishVodka for initramfs scripts for 4.2.x and 5.0.x
@Rox for help in fixing initramfs scripts for 4.1.2
@ace2nutzer for optimization CPU OC and for whatever scripts which I have used in my kernel
@Meticulus for BLN, Sweep2wake and Doubletap2wake
@mkaluza for huge LiveOPP/Mali improvements and Dynamic governor
@yanpol199 for help with F2FS support in TWRP
@ all users who tests this kernel and directs the development along the right path
@ all those users, who I forgot to mention (PM me if so)
Team Win for TWRP recovery
Samsung for opening kernel source
Linus Torvalds for Linux sources
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
Source Code:
LK 3.0.y based releases
Installation:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Notice: this kernel is not compatible with NovathorSettings app, be sure to remove it before installing a kernel!
Download:
FTP
XDA:DevDB Information
Chrono Kernel Refresh, Kernel for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, cocafe, faux123, zwliew, mkaluza, Meticulus, KINGbabasula, ace2nutzer, TeamCanjica
Source Code: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/refresh-3.0.101
Kernel Special Features:
Version Information
Status: Testing
Stable Release Date: 1974-11-11
Beta Release Date: 1974-11-11
Created 2018-03-22
Last Updated 2018-03-23

Changelogs
Changelog
R4.6.2
rebased to CM14.1 branch (added support for 6.0.1 and 7.1.2 ROMs)
R4.6.1
fixed CPU OC instabilities
LCDCLK is adjusted to fix tearing issues *
adjusted Dynamic CPU governor tunables for a better battery live
adjusted PowerHAL profiles **
genfstab: storages swap is disabled by default (remove /ramdisk/fstab_specs.txt before flashing to take this change in an effect)
updated temporary kernel zip
* tested with apps like Impossible Game, a display tearings are mostly resolved here. Apps like Youtube, though, might still causing tearings when playing video.
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage, so unless you're undervolting the CPU, there won't be any significant difference in a battery drain.
R4.6
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
R4.1
Initial build for janice (kernel sources based on Chrono Kernel r4.1)
LiveOPP: updated to r5.7.1 kernel version
Exfat: test fixes for Stock 4.1.2 ROM (not tested)
Enabled CONFIG_STE_TRACE_MODEM (test fix for Stock ROM incoming / outgoing calls)
Kexec: added janice support

Misc
Storages switch
By default, this kernel comes with internal and external storages switched. You can revert this behavior, by changing the line
Code:
use_swap=1
to
Code:
use_swap=0
in file /ramdisk/fstab_specs.txt and flashing the kernel package. This setting will remain until you format /ramdisk partition.

Thank you Chrono again.
So far I am still having issues with calls on 4.1.2 stock, I took another logcat in case would help you, and seems like phone can't enter deepsleep mode, but I will investigate further this issue with some days of usage.
I couldn't get exfat working, I took the exfat-fuse binary from /sbin in TWRP, then ran "exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard", tryed also with "mount.exfat-fuse etc etc", the fact is the card is correctly mounted and usable from recovery, but this does not matter after all.
The nice thing is I find multitasking working far better, phone seems to be more responsive in situations where more apps are running at the same time, this is very good to me!.
Another big point is installation went fine and recovery is working perfectly, so problems with possible bootloops are solved (and after some more usage I will go further to your more updated roms )
If there is something more to provide you, test or informations missing, please ask me Chrono

I tested chrono kernel r4.1 on Lineage OS 11.
-Compared to the previous chrono_kernel_r5.7.1, this is considerably slow, especially during the opening of apps like Settings, Contacts, Google News, Play store.
-If I set 1000 Mhz as maximum clock of the dynamic governor, the phone becomes slower and a bit hot on the back.
Multitasking is severely affected by that clock. Multitasking is more stable at 800 Mhz, despite it's still slow.
-If I reboot the phone, the maximum clock of 1000 Mhz is automatically resetted at 800 Mhz.
-If I attempt to reboot the phone in recovery mode from Lineage Os 11 ROM with the PC USB charging cable on, phone will shutdown instead. Disconnecting the charging cable before rebooting the phone in recovery mode is the only workaround. It doesn't happen with the Epirex Kernel, so I think it's related to your kernel.
In my attachment there is a meminfo that I took while the phone was under load.
If it isn't enough, I attached a full logcat. There are some errors and crashes.

@Pdevo, @isaak, thanks for testing!
I tested chrono kernel r4.1 on Lineage OS 11.
-Compared to the previous chrono_kernel_r5.7.1, this is considerably slow, especially during the opening of apps like Settings, Contacts, Google News, Play store.
Click to expand...
Click to collapse
Probably I've rushed things, or sort of. I had a hard time trying to find a considerably stable kernel 3.0.101 base (this one appeared to work stably, though not best, in terms of the performance). Nevertheless, the multitasking should already be better (at least better than in r5.7.1, as in this one LowMemoryKiller appeared not to work at all). I'm updating the sources to a new kernel base, r4.6 which should be even better in multitasking term.
-If I reboot the phone, the maximum clock of 1000 Mhz is automatically resetted at 800 Mhz.
Click to expand...
Click to collapse
Should be fixed in upcoming release.
-If I attempt to reboot the phone in recovery mode from Lineage Os 11 ROM with the PC USB charging cable on, phone will shutdown instead. Disconnecting the charging cable before rebooting the phone in recovery mode is the only workaround. It doesn't happen with the Epirex Kernel, so I think it's related to your kernel.
Click to expand...
Click to collapse
It's a bug in CM11 ramdisk, I've took another one from Codina, and now this issue should be resolved as well.
Pdevo said:
So far I am still having issues with calls on 4.1.2 stock, I took another logcat in case would help you, and seems like phone can't enter deepsleep mode, but I will investigate further this issue with some days of usage.
I couldn't get exfat working, I took the exfat-fuse binary from /sbin in TWRP, then ran "exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard", tryed also with "mount.exfat-fuse etc etc", the fact is the card is correctly mounted and usable from recovery, but this does not matter after all.
Click to expand...
Click to collapse
I'm afraid that exfat driver built in the kernel is not compatible with this userspace mount.exfat-fuse utility. I won't be able to fix it, until I find a time to return to stock & rebuild either mount.exfat-fuse or kernel driver in order to make them compatible each with other.
As for the deepsleep issue, I can say that at least 4.4.4 is not affected by this bug. Try making sure that no apps are preventing deep sleep (Better battery stats or Wakelock detector can help in that).

New build r4.6 is up!
Changelog
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.

ChronoMonochrome said:
Changelog
updated to r4.6 LowMemoryKiller implementation - best so far!
Disabled HighMem
removed some CPUfreq steps *
Dynamic governor: parameters are tuned for the better performance (credits: @ace2nutzer)
Added performance profiles (the corresponding parameters can be found in /ramdisk/perf.profiles.rc)
Other updates from r4.6 (various updates from LK 3.4, tweaks etc)
* Avalable CPU frequency steps are: 200, 800, 1000, 1100, 1200, 1215 Mhz. I've decided just to give it a try - this is a necessary part of tuning the CPU governor. If anyone doesn't like that frequencies between 200 and 800 MHz were removed I can add them back, but until performance-related issues are not resolved I'd suggest just leave as it is.
Click to expand...
Click to collapse
Tested on Lineage Os 11 without CCleaner.
After flashing this new kernel I had to force a Media scan with Fx File Explorer (that detected over 300 changed files) because the phone was really slow. That was sufficient to speed up the multitasking that now it's much better than previous 4.1 build.
Additional observations:
- Do you think it's possible to improve Media scanner reactivity via kernel?
- Fx File Explorer detects my external sd card as Main storage and Media card as internal storage. This doesn't happen on Epirex kernel.
- Battery usage is higher than previous kernel. If I stay on a webpage in idle, after 30 seconds my battery decreases of one percentage point (i.e. from 70% to 69%). I noticed that a simple swipe on the screen jumps the current clock directly to the maximum frequency, this could be one of the reasons.
- There is only FIOPS as I/O Scheduler and I miss all the other schedulers.
I think you're on the right track!

isaak said:
- Do you think it's possible to improve Media scanner reactivity via kernel?
Click to expand...
Click to collapse
I don't think it's possible. The only possible way is to overclock CPU, though it won't help much.
- Fx File Explorer detects my external sd card as Main storage and Media card as internal storage. This doesn't happen on Epirex kernel.
Click to expand...
Click to collapse
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
- Battery usage is higher than previous kernel. If I stay on a webpage in idle, after 30 seconds my battery decreases of one percentage point (i.e. from 70% to 69%). I noticed that a simple swipe on the screen jumps the current clock directly to the maximum frequency, this could be one of the reasons.
Click to expand...
Click to collapse
Ok, I'll consider of tuning CPU governor in order to provide more battery friendly setup. I was afraid that the battery usage might be too high, but that was a necessary evil, I guess. In the meantime, as a temporary workaround, the maximum CPU frequency can even be lowered to 800 MHz, it should be still fast enough.
- There is only FIOPS as I/O Scheduler and I miss all the other schedulers.
I think you're on the right track!
Click to expand...
Click to collapse
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?

ChronoMonochrome said:
I don't think it's possible. The only possible way is to overclock CPU, though it won't help much.
Click to expand...
Click to collapse
Nevermind.
ChronoMonochrome said:
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
Click to expand...
Click to collapse
I'd like to revert the behavior, so I would appreciate If you could provide the same instructions here and in the other kernel thread..
ChronoMonochrome said:
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
Click to expand...
Click to collapse
I would suggest deadline, noop, sioplus, zen (plus the existent FIOPS).

ChronoMonochrome said:
This is a default behaviour in Chrono Kernel. Because on codina we have only 4 Gb of available space, it makes sense just to remove internal storage partition and use the external one as primary. If anyone wants, I can revert this behavior. It's possible to switch storages back by editing file /ramdisk/fstab_specs.txt (set use_swap value to 0) and flashing a kernel package.
To load more I/O schedulers, you can copy (or symlink) a module file to /system/lib/modules/autoload, then reboot the phone. This doesn't seem to work, a script that loads modules, is broken.
Because usually I don't change I/O scheduler, by default, no more I/O scheds are loaded. Do you have any preferred I/O scheds?
Click to expand...
Click to collapse
Personally I really appreciate and find useful the external sdcard storage as primary one, should be the default behaviour for me, it makes sense and also I never liked to have some files on one unit and some files on another one (download, pictures, recordings on extsdcard, apps folders, screens, other apps downloads etc on internal), I really like the idea of sdcard as main, like the old times of galaxy mini
Fiops to me is a fair good scheduler, maybe also noop would be useful, but I guess having as much things as modules as possible can help load only the strictly necessary, but I say this without dev knowledge.
I will test this build and especially the deepsleep issues, to see if there are apps causing phone not to sleep, the problem is I didn't add any app, just using the same enviroment that with cocore was going to deepsleep. I will report soon, anyway, good job chrono, keep it up

Pdevo said:
Fiops to me is a fair good scheduler, maybe also noop would be useful, but I guess having as much things as modules as possible can help load only the strictly necessary, but I say this without dev knowledge.
Click to expand...
Click to collapse
Yes, FIOPS is good. I just think that having 2 or 3 additional schedulers to select would be better for different uses.
In my previous post I replaced sioplus with zen, according to the conclusions of this guide. There is an useful (up to date) list of recommended IO schedulers, ordered for everyday usage, battery life, heavy multitasking, etc.

New build r4.6.1 is up!
Hey guys and sorry for having to wait that long for a new releases!
I'm still working on 3.4.x kernel - no great news here, but at least I've found a more less stable sources base, so the only what needed now, is a time to bring up some stability fixes and feature changes.
For now releasing a 3.0.101 kernel with some minor changes:
R4.6.1
fixed CPU OC instabilities
LCDCLK is adjusted to fix tearing issues *
adjusted Dynamic CPU governor tunables for a better battery live
adjusted PowerHAL profiles **
genfstab: storages swap is disabled by default (remove /ramdisk/fstab_specs.txt before flashing to take this change in an effect)
updated temporary kernel zip
* tested with apps like Impossible Game, a display tearings are mostly resolved here. Apps like Youtube, though, might still causing tearings when playing video.
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage, so unless you're undervolting the CPU, there won't be any significant difference in a battery drain.

ChronoMonochrome said:
** the minimum CPU freq is set to 400 MHz. I've decided to use it as a default since 200 and 400 MHz CPUfreq steps are anyway using the same voltage
Click to expand...
Click to collapse
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs:
1) Minimum CPU freq here is still set at 200 MHz after I flashed chrono kernel 4.6.1.. but this time I forgot to flash the temporary kernel before your kernel.
Anyway chrono kernel 4.6.1 was flashed without issue using TWRP 2.8.7.0.
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
5) On the Performance UI, performance profile results automatically set on Balanced after any reboot, even if I set Power save as default (it may be reproducible with "Performance" option too, I didn't check).
UPDATE: I've reinstalled chrono kernel again and these behaviors still happen.

For me the minimum freq was correctly 400 mhz as expected, as always running on stock 4.1.2.
After two days of use I can say you are following the right path.
This time I wanted to remove every possible source of doubts and I went for a clean installation, so doing a complete reset and flashing your kernel, of course after the temporary one. I still have the phone not going to deepsleep and the call issues (basically it is impossible to do and receive phone calls on stock rom).
A part from these I can say I didn't noticed any other issue at all, finding memory management a little improved compared to previous release and battery life still good, considering the phone isn't going to sleep mode.
I think this will continue to improve and soon all these glitches will just be gone away, thank you so much chrono also hoping to settle for a bit on your ultimateROM, only waiting for the vibration working, because that is basically the only notification for me

isaak said:
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs:
1) Minimum CPU freq here is still set at 200 MHz after I flashed chrono kernel 4.6.1.. but this time I forgot to flash the temporary kernel before your kernel.
Anyway chrono kernel 4.6.1 was flashed without issue using TWRP 2.8.7.0.
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
5) On the Performance UI, performance profile results automatically set on Balanced after any reboot, even if I set Power save as default (it may be reproducible with "Performance" option too, I didn't check).
UPDATE: I've reinstalled chrono kernel again and these behaviors still happen.
Click to expand...
Click to collapse
1) Isn't an issue here, the showed CPU frequency is 200 MHz, but the actual CPU pll clock set at 400 MHz. Might be confusing, but yet that is better for a battery life.
2) These aren't really bugs, it's how LOS 11.0 performance profiles works. To change min / max CPU freq, you either need to edit /ramdisk/perf.profiles.rc (and set a custom values) or disable perf profiles. Actually there is one more way - to remove CPUfreq adjusting lines completely from that script - would anyone like this change introduced in a new release?
3-4) I've checked it right now - no issues for me... Have you set "apply on boot" checkbox?
5) It's a known bug of CM11 perf profiles. AFAIK, @ace2nutzer fixed this bug in his CM11 builds. @ace2nutzer, can you please remind how this could be worked around?

ChronoMonochrome said:
2) Maximum CPU freq is automatically restored at 1000 Mhz after any reboot, even if I set 1200 Mhz (with any governor).
Click to expand...
Click to collapse
2) These aren't really bugs, it's how LOS 11.0 performance profiles works. To change min / max CPU freq, you either need to edit /ramdisk/perf.profiles.rc (and set a custom values) or disable perf profiles. Actually there is one more way - to remove CPUfreq adjusting lines completely from that script - would anyone like this change introduced in a new release?
Click to expand...
Click to collapse
Honestly I don't know how to disable perf profiles. If it's a simple thing to do (like a command or two to execute), please tell me how to do it because it's enough for me, otherwise I'd like to try the third way and see.
ChronoMonochrome said:
3) Deadline scheduler is automatically set after any reboot, even if I set FIOPS as default scheduler.
4) Dynamic governor is automatically set after any reboot, even if I set Zenx as default governor.
Click to expand...
Click to collapse
3-4) I've checked it right now - no issues for me... Have you set "apply on boot" checkbox?
Click to expand...
Click to collapse
Yes, "Set on boot" options are correctly set for both Processor and I/O Scheduler.
And I keep "Enable per-app profiles" option turned off.
@ChronoMonochrome
UPDATE 1: It occurs only randomly and with particular combinations. The best way to reproduce is to set these, one at a time:
1) Zenx as governor, min. 200 max 800, Noops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Fiops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Sioplus scheduler. Reboot.
After the first, the second or the third reboot, some of these values you've set will change spontaneously on their own.
UPDATE 2: I've got a screen flicker issue while I was browsing in Naked Browser with the new LCDCLK frequency.
Tried to set echo 1 > /sys/kernel/mcde/lcdclk, it's ok now, but I've noticed that this value is not kept after a reboot.
Do you need a specific log?
In case please write me any command and I'll give you the output.

isaak said:
On Lineage OS 11:
Using more accurately the Performance function in Lineage Os Settings (an example here), there are different bugs: .....
Click to expand...
Click to collapse
I suggest to keep it unchecked, otherwise it'll change the profile randomly, and that's probably not what u want.
ChronoMonochrome said:
....
5) It's a known bug of CM11 perf profiles. AFAIK, @ace2nutzer fixed this bug in his CM11 builds. @ace2nutzer, can you please remind how this could be worked around?
Click to expand...
Click to collapse
There's still no fix ! But what i did is to add the perf. profile in my control app ... that works fully independently.
But that's probably not what u guys want.
My last try was to do that over build.prop .. this works only for around 15 seconds (after wiping dalvik cache it's around 30 sec.) and then it sets back to "balanced" .. so i use it anyway just for speeding up the boot sequence:
Code:
# CM Performance Profiles (only during boot)
# 0= powersave; 1= balanced; 2= performance - default
sys.perf.profile=2
IMO the best way is to add the perf. profiles button to the quick settings, then it's very easy to switch between the 3 profiles.
Using the same profile for everything is for sure not the best option if u want performance + powersave at the same time.
Personally i use performance, and when i read an pdf or watch a YouTube Video then i switch to powersave.
Using powersave or even balanced for normal usage isn't recommended as it can drain even more battery than using performance, because it's slower and the CPU will stay too long on max. freq and the LCD also will stay longer ON, which leads both to increase power consumption.
So the faster the cpu is, the quicker it'll go on idle (min cpu 200) which is powersaving freq and the faster u'll turn OFF the screen, and logical bigger time on suspend --> deep sleep :highfive:

ace2nutzer said:
I suggest to keep it unchecked, otherwise it'll change the profile randomly, and that's probably not what u want.
There's still no fix ! But what i did is to add the perf. profile in my control app ... that works fully independently.
But that's probably not what u guys want.
My last try was to do that over build.prop .. this works only for around 15 seconds (after wiping dalvik cache it's around 30 sec.) and then it sets back to "balanced" .. so i use it anyway just for speeding up the boot sequence:
Code:
# CM Performance Profiles (only during boot)
# 0= powersave; 1= balanced; 2= performance - default
sys.perf.profile=2
IMO the best way is to add the perf. profiles button to the quick settings, then it's very easy to switch between the 3 profiles.
Using the same profile for everything is for sure not the best option if u want performance + powersave at the same time.
Personally i use performance, and when i read an pdf or watch a YouTube Video then i switch to powersave.
Using powersave or even balanced for normal usage isn't recommended as it can drain even more battery than using performance, because it's slower and the CPU will stay too long on max. freq and the LCD also will stay longer ON, which leads both to increase power consumption.
So the faster the cpu is, the quicker it'll go on idle (min cpu 200) which is powersaving freq and the faster u'll turn OFF the screen, and logical bigger time on suspend --> deep sleep :highfive:
Click to expand...
Click to collapse
Sorry for so late response, I had to take a break in a development because suddenly got sick with a flu (I'm fine now, btw) :silly:
I think I've found a temporary solution to this bug, take a look if you're interested:
https://github.com/ChronoMonochrome...mmit/bd0dcce403633543f1bf11e5f8b476a3e88322cb

New build is up!
Changelog
R4.6.2
rebased to CM14.1 branch (added support for 6.0.1 and 7.1.2 ROMs) *
Hey there! I've been testing 6.0.1 / 7.1.2 ROMs and I've recently got some issues with camera on 3.4.x kernel build, so I've decided to release a new refresh build (based on 3.0.101 sources).
I've rebased the most of recent changes to CM14.1 branch in order to support these ROMs (so if you're using older ROMs like stock 4.1.2 then better to use previous release cause some patches might be missing here).