yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] DragunKorr:
Running 1152 latest very smooth and responsive on my stuff good job!

Lagfree my fave
[HTC Sensation] jaysun3000:
Would this work on JB MIUI?
[HTC Sensation] Sultanxda:
Yep. My kernel works on any JB ROM :)
[HTC Sensation] Sultanxda:
Beta testers

Hey, I need some beta testers for r2 of my kernel. The only testers I need are users of the 1.728GHz kernel; if your Sensation can't overclock to 1.728GHz then beta testing r2 won't serve much use. In r2 I have increased the maximum L2 cache frequency from 1.566GHz to 1.728GHz (for some reason ALL the other Sensation kernels, including ICS kernels, don't have the L2 cache frequency higher than 1.566GHz and I have no idea why). I have tested this on my Sensation personally and it boots up and works fine, but because nobody else has the L2 cache frequency past 1.566GHz, I'd like some people to test it. Send me a PM if you're interested.
[HTC Sensation] adame09:
I can test for you
[HTC Sensation] Sultanxda:
Check your PM.
[HTC Sensation] ptlsajan:
Hey bro I will test for you... pm me
[HTC Sensation] Jiggs82:
Loving the kernel man keep up there good work....can't wait for r.2 version, fast and smooth:)
[HTC Sensation] lavier:
by flashing this will both the cpu work..........???

am on stock cm10 n after installing kernel tuner only one is working other is offline
[HTC Sensation] Sultanxda:
Force the other CPU online using an app called Android Tuner (both cores work for me). Also, the other core should be coming online automatically when you need the power; if it isn't then there's something wrong.

EDIT: Ah you haven't flashed my kernel yet. Anyway, I just tried Kernel Tuner and it seems glitchy (it turned off my other CPU core :confused:) so if I were you I'd uninstall it, reboot, and see if anything changes.
[HTC Sensation] lavier:
ohk gonna try your kernal

how can i enable second cpu with android tuner
[HTC Sensation] Sultanxda:
In Android Tuner go to settings, active tweaks, boot settings, choose Force all CPUs online, select init.d script, and then reboot your phone.
[HTC Sensation] Sultanxda:
r2 released

R2 has been released with the maximum L2 cache frequency increased to 1.728GHz. Feedback is very important for this release; for example, if you can't overclock your CPU to a frequency you had it running at before then I need to know so I can adjust the max L2 cache frequency. The changes in r2 do not matter to those who have their max CPU frequency at or under 1.566GHz. Have fun!
[HTC Sensation] ninjabadger:
R2 froze my phone when running 384-1728 lag free. This was during antutu.

Edit:

1674 OK but results lower than 1.5r at 1728.

Edit2:

Went back to r1 and ran antutu at 1782 without issue so L2 frequency likely culprit. Perhaps try at 1620 or 1674?

Sent from my HTC Sensation
[HTC Sensation] haifish9999:
In R2 (1512 version) haven't s2w or I miss something?

P/s: sorry,I've got this in init.d. Thanks
[HTC Sensation] allenfoxtc:
cpu1 still offline-badass, whatever the rest of aroma settings are. But if you'r lucky (with all of your system build-in's tuners turnned off), cpu1 will be online for about 3 mins after boot complete.
[HTC Sensation] chassy_8o9:
is exactly the behavior I see on my device, I am using paranoid android official v24 by DK with sultan r13 build... I could only enjoy the power of this kernel, for a few minutes, only if the device just rebooted...
[HTC Sensation] MS Gray Man:
Made it 5 mins 4 secs before cpu1 went dark.

Toggled prevent changes from other apps and reboot...cpu1 went dark at around the 1 min mark.

remove prevent changes and reboot - dark 1min again.

OK made it to the 5 min mark again by making sure that settings\performance\memory mirrored Aroma settings..

Unlike processor and i/o scheduler which you can toggle to not restore on boot... Memory management has no such setting... zram and KSM are either disabled or set ... Set zram to 18% (default) and making sure KSM was unchecked (as it was not enabled in Aroma) - I hit 5 mins again.

Unchecking allow purging of assests puts me back to a 1.5min failure...

So for now I am out of ideas.
[HTC Sensation] allenfoxtc:
Well done! You just break the records... :)

I still can't figure out why cpu1 gets offline after a few minuts.
[HTC Sensation] TAGTRAUM:
Same here....I have heavy lags on switching homescreens for every 30secs, another 30secs it's a quite smooth :cyclops:
[HTC Sensation] Sultanxda:
I'm downloading AOKP as I type. I'd really like to keep my hair :p
[HTC Sensation] MS Gray Man:
So here's a bit of an oddity... Did a dirty flash of Tamcore and rebooted.. No other changes were made so...

Kernel Tuner set to not restore changes on boot... No frills not restore on boot... \settings\performance no restore for proc or IO and memory set to zram 18% 0- fliush disabled, KSM disabled.

Both cores functioning as expected with 11m of uptime and 2.5m of deep sleep.

However the original settings from the Aroma install of Sultan seem to be in place...

1566 810/972 (2nd/3rd phase) sio - badass...

While some of those are defaults for Tamcore I don't believe the frequencies are...
[HTC Sensation] Sultanxda:
The original settings of the Aroma install should be in place as r13 was meant to fix that. AOKP is booting up right now. You had the screen on for 5 minutes, correct? Also, can you post your last_kmsg file from right after the second CPU core stays offline forever? The last_kmsg file can be found in the /system/etc folder.
[HTC Sensation] MS Gray Man:
yes -- unlocking at boot up and then just watching for the core to shut down from kernel tuner main screen, then seeing if kernel tunner cpu tweaks would force it awake as it tried to enable both cores for a settings mod.

last_kmsg -- would be happy to looking at \system\etc though it goes from init.sultan.sh to media_codecs.xml... no last_kmsg file anywhere in \system via root explorer... would the dirty flash and coming up on tamcore have removed it?

by the way if it helps both cores have now been up under the dirty flash for 26.5m with 8:48 of deep sleep.
[HTC Sensation] Sultanxda:
Also, is this with mpdecision enabled?

UPDATE: I'm at 4 minutes with mpdecision enabled and your CPU settings (Badass, max freq @ 1566MHz, etc.), so far the second core is turning off and on like it's supposed to. Also, the Aroma's CPU settings were applied successfully. I'm on a clean install of AOKP.

UPDATE2: I'm at 13 minutes and the second core is still coming online like it's supposed to... wtf?
[HTC Sensation] MS Gray Man:
Yes last I checked if mdprecision is disabled and you dont run Kernel tuner or anything that tries to reenable it both cores will stay active... at least this is how I remember it :silly:

Problem seems to only happen with mdprecision running -- kind of why I'm counter checking with tamcore as it runs on kernel md as well...

This particular set of efforts was not done on a clean install... previously however it has been... I've seen this behavior on both jellybam and franks clean installs... However if it will help you I will run a backup real quick and then install either version of AOKP you want and r13 and see what happens... that way I can send you whatever files if it happens..

---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------

by the way with regard to the Aroma settings, I believe those were being applied correctly. The strange behavior with the flipped governor WAS coming from the \settings\performance in the ROM trying to force ondemand vs. badass...

---------- Post added at 04:34 PM ---------- Previous post was at 04:28 PM ----------

Crazy and I don't have an answer... running a backup now..

Want me to install Franks or Jellybam?
[HTC Sensation] Sultanxda:
This is what I did: factory reset/wiped cache/wiped dalvik cache/wiped system, installed AOKP, installed google apps for 4.1.x, installed CWM.99, rebooted, installed my kernel, rebooted again. Also, I'm at 27 minutes and core1 is still coming online like it is supposed to. All kernel functions are operating correctly. As I said before, the kernel was fixed and there is something else causing the problem. I have KSM enabled and LogCat disabled. Mpdecision is enabled.
[HTC Sensation] MS Gray Man:
OK so here's what I did.. After backup using 4ext rc9 - wipe all but sd card - flash aokp_pyramid_unofficial_Jan-08-13- flash sultan r13 - reboot - reboot recovery flash gapps jb 20121011 frankinstine - reboot - install kernel tuner from playstore - showing cpu1 already dead - entering cpu tweaks does not bring it back...

I don't know how to get the install any cleaner than this and cpu1 dies...

there appears to be no last_kmsg file in system\etc but I'll send you whatever you want...only difference I see is I did not disable logcat.

Reflashing Sultan to disable log cat.. Here are screen by screen selections:

sultan - yes mdp - s2w no - badass - performance - same freq both cpu - 1566 - 192 - 810 - 972 - 594 - 200 - 267 - no zram - sio - medium - yes disable logcat - default - yes vsync - yes fsync - no fast charge - yes ksm - -9%-

reboot

pink unicorns

cpu1 online less than 56secs and now offline..

cpu tweaks showing cpu0 - 192/1566 badass cpu1 - null/null (offline) badass
[HTC Sensation] Sultanxda:
Don't use Kernel Tuner; uninstall it and reboot. I used Android Tuner Free. Also, I don't know if this is relevant, but I am S-OFF and using TWRP.
[HTC Sensation] ianoob:
Have you tried system panel lite instead of kernel tuner to check the cores? Mine is still working perfectly

Sent from my phone on an app
[HTC Sensation] Sultanxda:
I disabled fsync, but fsync shouldn't be the source of your problem.
[HTC Sensation] MS Gray Man:
Only variation here is TWRP vs 4ext.

Uninstall KT - reboot - using either Android Tuner free or System Panel...

AT - Shows CPU1 offiline

SP - Shows CPU1 sleep
[HTC Sensation] ianoob:
In Sp, open the cpu info, leave it open and start a high process app, switch back to SP and see if both are active. Mine shuts down very quickly

Sent from my phone on an app
[HTC Sensation] MS Gray Man:
Nope that cpu is nighty night...

Now to complete the circle - dirty flash tamcore zip over this install and reboot.. both cores function as expected once again.

Reflash sultan r13 over tamcore to match your fsync setting -- cpu1 goes dead again in AT

---------- Post added at 06:18 PM ---------- Previous post was at 05:26 PM ----------

So before I restore anything you want me to try and capture from this phone?
[HTC Sensation] Sultanxda:
Are you S-OFF? Maybe try TWRP, do factory reset/wipe cache/wipe dalvik/wipe system and reinstall. TWRP is the only difference between our phones left. I'll try using 4EXT to see if I can replicate the problem.

EDIT: Flash the newest available NO-AROMA version and see if it works. Delete 99z_kernel from /system/etc/init.d before you do that.

EDIT2: I'd also like you to retrieve your last_kmsg after Core1 goes offline. Use this app to retrieve it: https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack

I'd really like to find out what's causing my kernel to not play nicely with your phone and quite a few other people's phones.
[HTC Sensation] dohclude:
MS Gray Man - Are you absolutely certain that cpu1 is staying offline? I know on mine, it appears to be offline most of the time, but does actually kick in when there is enough load. The way I test is by running Antutu benchmark. If I get a score above 7000 then I know cpu1 is coming back online. If the score is around 4000-5000 however, it's pretty clear that it's not. With this method you can test without having kernel tuner installed (or any other tuning apps that may be causing issues for that matter.)
[HTC Sensation] Sultanxda:
+1 (I would thank you but I ran out of thank you's for today)

The kernel based mpdecision that TamCore's kernel uses is different from the kernel based mpdecision that my kernel uses, so it's possible that the mpdecision I'm using has better power management.
[HTC Sensation] MS Gray Man:
OK so just for the novelty - I switched to TWRP and as we thought no change there. Clean install in fact I even skipped gapps, locally loaded an apk for AT vs using the play store. cpu1 still dies. I even removed the OC and UV just in case...

Working on lumberjacking now.
[HTC Sensation] Sultanxda:
Did you run Antutu as per Dohclude's suggestion?
[HTC Sensation] Sultanxda:
R14 Beta 1

I decided to release a beta for r14 in order to see if there is a speed difference between the -Os optimization flag and the -Ofast optimization flag. R14 beta 1 has been compiled using the -Ofast optimization flag instead of -Os, resulting in a kernel that is 10% bigger but optimized for performance. I'll need feedback on the performance of r14b1. For those who don't know, -Ofast is -O3 optimization but with a few more things for more performance. As a comparison, Bricked uses -O3. Betas will not include the Aroma installer nor do they come with init.d scripts. Read the changelog in the second post for all the details on what else changed in r14 beta 1. You can download beta releases under Betas in the Download section in the OP. Have fun!
[HTC Sensation] MS Gray Man:
Since Android Tuner is clearly only tracking and increasing times for CPU0 - I'd say it's a safe bet that CPU1 is offline.
[HTC Sensation] Sultanxda:
It'd be an even safer bet if you ran Antutu. When I let my phone sit for an hour, the second core would go offline and I would have to open an app or a game to make it come online.
[HTC Sensation] MS Gray Man:
Link to your logs is in PM... Going to go restore now.

Well I induced an app fault to hang tanks and turrets at 70-80% cpu @ 1566 for about 3 mins without that core kicking on. If that is working as expected then your power management is too good...
[HTC Sensation] Sultanxda:
I looked at your last_kmsg file and here's what it says:

CPU1: shutdown
CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[MPDEC]: CPU[1] on->off | Mask=[10] | time online: 42545
call alarm, type 2, func alarm_triggered+0x0/0x9c, 43581000000 (s 43581000000)
CPU1: Booted secondary processor
saw_set_voltage: 8901_s1: msm_spm_set_vdd failed -5
increase_vdd: vdd_sc (cpu1) increase failed (-5)
[MPDEC]: CPU[1] off->on | Mask=[11]
CPU1: shutdown
CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[MPDEC]: CPU[1] on->off | Mask=[10] | time online: 508
TSENS: Current CPU Temperature is: 31
rmnet0: no IPv6 routers present
CPU1: Booted secondary processor
saw_set_voltage: 8901_s1: msm_spm_set_vdd failed -5
increase_vdd: vdd_sc (cpu1) increase failed (-5)
[MPDEC]: CPU[1] off->on | Mask=[11]
CPU1: shutdown
CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[MPDEC]: CPU[1] on->off | Mask=[10] | time online: 504

Note that it says stuff like CPU1: shutdown and [MPDEC]: CPU[1] on->off

AND

CPU1: Booted secondary processor and [MPDEC]: CPU[1] off->on.

This turning off and on/on and off of CPU1 comes up throughout the ENTIRE last_kmsg file, meaning that mpdecision is working correctly.

Mpdecision is working correctly because it is shutting CPU1 down and booting CPU1 up, and it is doing this throughout the entire last_kmsg file. When you played that game, the mpdecision probably turned the other core off before you could see that it was on. If you don't believe the last_kmsg file and think that mpdecision is not working correctly then please run Antutu and tell me what score you get. At this point, Antutu is the most accurate way to tell whether or not mpdecision is working correctly.
[HTC Sensation] MS Gray Man:
Well OK I guess it's working. However you asked for the file from when it quit working... Well that's where it quit working. It was cycling.. during boot and then shuts down shortly after. Having a process running at 80% core consumption and max freq and the second core doesn't wake up, is not desirable behavior.

So yes that file shows it cycling right up until it stops. Either way, I dunno what to tell you. This was really about me trying to help. I really don'ty have a dog in the race. That core is not running after awhile. It's that simple. Cpu1 NEVER lights back up after a point. Not even briefly regardless of CPU load. When Android tuner isn't even showing or tracking CPU1 times the core is not going active after that.

and yes I do mean single column for cpu0 -- NO column for cpu1 in times --- so no, it isn't working properly.

But like I said, I'm OK with it.
[HTC Sensation] Sultanxda:
If you could run Antutu and give me your score then I would be extremely grateful. If you score around 4,000 with Lagfree and the max CPU frequency set at 1566MHz then I will look into this more. However, if I have no proof that mpdecision really isn't working after a certain period of time, then I won't waste time trying to solve a problem that may not even exist, and right now mpdecision is working perfectly for me and according to your last_kmsg file it is working perfectly. Were games laggy after core1 went offline? Was your UI laggy after CPU1 went offline? Also, CPU0 is never allowed to go offline (for obvious reasons). If CPU0 went offline then the kernel would panic and the system would crash.
[HTC Sensation] MS Gray Man:
OK did a wipe and clean install again of frank's AOKP. Installed Android Tuner and Antutu..

Stock kernel running stock speed (1188) Antutu @ 7877

AT shows both cores running as expected and time shows CPU0 and CPU1

Reboot run Sultan r13 AROMA (set as badass - performance but left at stock 1188)

AT again shows the core active for a brief period after boot then it shuts down. Times shows only CPU0

Antutu benchmarks @ 4792

Ran Antutu again for kicks after a reboot. No settings were changed. This time I went into CPU times quickly (while core was still active so that it kept columns for cpu0 and cpu1)

then ran Antutu @ 4343 -- returned to AT CPU times (CPU1 timer had increased for the time Antutu run and never gone out of offline) -- switched view and abck again, column dropped to only CPU0 indicating that AT sees that core as completely offline..

So yes, that cpu core is going down for some reason and not coming back.

---------- Post added at 10:29 PM ---------- Previous post was at 10:06 PM ----------

Sent you new logs via PM taken after this.
[HTC Sensation] Sultanxda:
According to the kmsg log, CPU1 was turned back online right before you sent the reboot command (the reboot command then turned it off after that because it was rebooting, so that's normal), which makes no sense because you scored ~4,000 in Antutu :confused:. I'm looking at the last_kmsg right now to see if there is any significant gap between turning the CPU on/off, so I can try and pinpoint what's causing the problem. It'll be easy to see what turned CPU1 off because it probably won't have an [MPDEC] flag near it.

UPDATE: I've rebuilt the kernel three times with different things changed each time and attached them at the bottom of this post. Please tell me if any of them work. Also, none of them use Aroma, so switching kernels won't take long.
[HTC Sensation] allenfoxtc:
I can't boot using any version of r14, does r14 can't flash over r13?

Accroding to Zarboz (http://xdaforums.com/showpost.php?p=33623251), i can't find idle_freq in my device, should it be the reason why cpu1 turn off then never get online?

Disable mpdecision doesn't work for me, so i add a line "chmod 444 /sys/kernel/msm_mpdecision/conf/enabled" to lock it. Finally mpdecision never get start anymore, but cpu1 still be offline in a few mins (possiblly because of Kernel Tunner runs "chmod 777 .../cpu1/online" after reenable both core), and then cpu1 with fully controllable will be offline by a unknow process which i can't find out.

Update- cpu1 will recover when you unlock the screen.
[HTC Sensation] MS Gray Man:
I'll test them if I have extra time at work or when I get home...

Cheers.
[HTC Sensation] dhman06:
So I'm new to this kernel flashing thing. I'm running AOKP JB. Can I flash this kernel on my phone? Do I just install the latest version and flash it from recovery? Do I need to wipe anything?
[HTC Sensation] MS Gray Man:
So I only went as far as the beta and the first special file... Both cause boot loops (never makes it to boot animation - loops HTC)

That was flashed over r13 installed and booting (but cpu1 shutting down)
[HTC Sensation] Sultanxda:
Thanks. I know how to fix that (GPU underclocking isn't working as expected). I'll release r14b2 when I get home in about 6hrs
[HTC Sensation] Sultanxda:
r14b2

Can someone flash r14b2 and tell me if it's booting? I tried updating the kernel to 3.0.58 by patching my kernel from DragunKorr's source. All I need to know is whether or not it's booting. A quick response would be very much appreciated :). Thanks in advance.

EDIT: It isn't booting. Guess you'll have to wait a little longer for 3.0.58 (I'll try patching it differently some other time; maybe the weekend). BTW, the update to 3.0.58 only includes really minor changes for us, and it only really changes drivers.
[HTC Sensation] erraggy:
It only bootloops without even getting to the point where I can grab a logcat. Sorry.

EDIT: whoops... I didn't see your update stating it doesn't boot LOL.
[HTC Sensation] Sultanxda:
The effort is appreciated :)
[HTC Sensation] Sultanxda:
Sorry everybody, we WILL be getting 3.0.58. I just found out that the -Ofast and -O3 optimization flags cause bootloops with my kernel (only my AOSP kernel, not the Sense one). I'll be uploading r14b2 in about 15 minutes (I'm testing the GPU underclock now).
[HTC Sensation] erraggy:
Issues on r13 (from Aroma)

@Android1234567: Since my move from DragunKorr's to bruce's CM10, I don't think I have been able to get your kernel to install and perform well. I've been busy for the past few weeks, but got the itch to give it another go tonight and I wanted to report my findings.

Performance is very laggy and my gut tells me dual-core functionality are not behaving well. On first boot after install, I grabbed a logcat:

View attachment firstboot.txt

I found some issues with the 40ext4tweaks script as well as the fact that bruce's init.d script was still present, so I decided to give some edits a try as well as remove 89bruce since it applies to his kernel and is not intended for yours:

View attachment 40ext4tweaks.txt

Doing so gave me a second boot with the captured logcat:

View attachment afterMyEdits.txt

Things still felt pretty slow, but I gave AT benchmark a try with the following result: 3671 (screen shots below):

View attachment 1646041

View attachment 1646040

I'm not sure if any of the other files that were included in bruce's CM10 init.d could be causing issues, but the other 2 looked innocuous enough (00banner, 90userinit).

Any help getting your kernel fully operational again on CM10 would be awesome!
[HTC Sensation] Sultanxda:
I'll make test kernels for people with mpdecision problems tomorrow. I'll barely be able to release r14b2 today (out of time). Sorry
[HTC Sensation] erraggy:
No worries. I've got work and I assume you have school ;)

Your efforts are appreciated :D
[HTC Sensation] Sultanxda:
r14b2 released

Yeah I have school tomorrow :mad:

Anyway, r14b2 has been released. The kernel has been updated to 3.0.58 (thanks to DragunKorr) and it boots up. I figured out that changing the GCC optimization level to anything but -Os yielded an unbootable kernel, so I was forced to switch the optimization level back to -Os. Also, GPU underclocking is not included in this beta. GPU underclocking will be included in tomorrow's beta. SmartassV2 is also in the beta. Have fun :)