yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Sultanxda:
It was probably a fluke in the soft swap, a one-time error.
[HTC Sensation] barepe:
I has disabling soft swap, and reboot are persists, *reboot 20minutes after start up

Last_kgsm and my 99z_kernel setting http://db.tt/8klA9D1O
[HTC Sensation] Sultanxda:
VERY IMPORTANT: R7.5 released

I have released r7.5 AND IT IS EXTREMELY IMPORTANT THAT YOU INSTALL IT AS SOON AS POSSIBLE. R7.5 FIXES REBOOTS, IT FIXES SETTINGS FROM AROMA NOT BEING APPLIED (EX: CPU GOVERNOR SETTINGS), AND IT FIXES PROBLEMS WITH MPDECISION. Thank you for finding this very nasty bug, Dohclude :good:
[HTC Sensation] barepe:
Downloading and trying new versions, i will report back
[HTC Sensation] barepe:
No reboot after flashing last version, my sensa runing smooth with elegancia 3.3.0 rom and your last kernel 7.5

Great job and thanks :)
[HTC Sensation] StuifzandNL:
I was wondering...

If you use KSM will it drain your battery more??

Got a funny feeling that it does..

And witch's better: hardswap ore zram?

If you use hardswap does it also use the Google's snappy?
[HTC Sensation] Sultanxda:
Hard swap doesn't use Google's snappy because it doesn't need to be compressed. Zram, on the other hand, obviously has to be compressed. Zram is definitely faster than hard swap because it uses RAM, and RAM is much faster than any SD card, so I recommend the use of zRam. As for KSM, I don't know how much CPU usage that takes up so I don't know about battery life.
[HTC Sensation] Harbir:
Hard swap is better as does not let the app to close and swap it to vertual ram SD card and saves little battery and increases the speed of the phone
[HTC Sensation] StuifzandNL:
Thank you guy's!!!

I will enable zram and leave hardswap on

And look what is does to the phone!
[HTC Sensation] Harbir:
Do I mean both inside the phone :confused: then that would be useless use only one of them as they both are replacement to each other
[HTC Sensation] StuifzandNL:
Okay then I try the zram only.

Always used the hardswap.

I will report back on this
[HTC Sensation] ahsan64:
bug in kernel i think....

HI

your kernel RC 7 is very fast and stable but sometime back capicitive button vibrate but with greater amount.....

so i changed the kernel....

i dont know its a kernel problem or not but i changed kernel and now problem is gone...
[HTC Sensation] tcnineteen:
Hi android1234567, trying your r7.5 kernel now, and the time travel issue didn't happen for now after clearing cache and dalvik-cache, nice;)

However, I encountered another random reboot when screen off... I'm running Elegancia Blitz 3.8.0 with Intellidemand, Max 1566, Min 192, Inactive 1134, 2nd-phase 918, screen-off 594, sio, and the only culprit I suspected was UV -9%. But I didn't get random reboot with PYD-X 4.1.9 (for 1 day.) Oh, in addition, I used light minfree settings with hardswap by yank. Trying the same settings without UV now, and I grabbed the last_kmsg as well for your further investigation. (It seems that there was another kernel panic...) Hope it'll help, and thanks for your hard work!:good:
[HTC Sensation] Harbir:
Problem report

STILL cant set the governor and the max screen in for badass selected in aroma .:confused:

can u please upload the non aroma v and i will configure it with AIO mod if it is possible

EDIT- sultan removed from AIO MOD so u have to fix it lol
[HTC Sensation] kamilmirza:
testing r7.5, so far so good :good:

haven't faced any reboots and shutdowns yet (zRAM enabled, no UV)

was facing shutdowns on r7 with

no zRAM
[HTC Sensation] Sultanxda:
Remove the UV and see if you still get reboots.
[HTC Sensation] Sultanxda:
R12 and r12.5 use the same kernel but I'm forcing everyone to use Aroma for r12.5 in order to remove bad files that originally came with AIO. I also checked to make sure that I could set the governor from the Aroma installer and it worked :confused:
[HTC Sensation] szymko1995:
Now reflashed latest cm10 bruce and his gpuoc kernel. Now everything is fast and smoooth.

Sorry to say, that on yours I had problems. Hope you will fix them soon.
[HTC Sensation] Harbir:
dont know why i have that problem only in your kernel please fix :confused: any thing i can do.....to fix it
[HTC Sensation] Sultanxda:
Wrong thread. I tested mpdecision many times on my phone and it worked so the problem is coming from the user side. Perhaps the files causing these problems were somehow not deleted. Now that you've reflashed, everything should be working perfectly, including mpdecision...
[HTC Sensation] Sultanxda:
If for some reason you can't select the governor in the Aroma then just use an app like No-Frills. The main reason why the governors are in the Aroma is so that you can choose the settings you want for the governor you're going to be using (ex: change Badass to power save mode).
[HTC Sensation] Sultanxda:
TO EVERYONE HAVING ISSUES:

MAKE SURE THAT THESE FILES DO NOT EXIST AND IF THEY DO EXIST THEN DELETE THEM IMMEDIATELY AND REBOOT:

/system/bin/mpdecision

/system/bin/thermald

/system/etc/thermald.conf

/system/etc/init.post_boot.sh

/system/etc/init.qcom.post_boot.sh

R7.5 is supposed to delete those files automatically but there's always a chance that it didn't work for some reason. Those files cause many problems and are not needed.
[HTC Sensation] tcnineteen:
Hi android1234567, I checked and they all existed.:p Have renamed them all, rebooted, and now observing how it goes.:fingers-crossed:
[HTC Sensation] axetilen:
You made a serious mistake, I say

/system/etc/init.post_boot.sh
/system/etc/init.qcom.post_boot.sh

you have to read what is inside these scripts before removing it, especially init.qcom.post_boot.sh - sense-rom must-have file

you can edit them and mix them together but never remove both of them

without these files, in some ROMs, all the aroma or init.d scripts become useless

# Execute /system/etc/init.d scripts on boot
sysrw
chgrp -R 2000 /system/etc/init.d
chmod -R 777 /system/etc/init.d
sysro
/system/xbin/busybox run-parts /system/etc/init.d

p/s: most of my aroma scripts are designed for sense-based roms -> not for AOSP

msm_mpdecision automatically disables CPU1 while deep sleep -> do you know that?

suggestion -> remove chmod 444 in the script
[HTC Sensation] Sultanxda:
Thanks, I'll create a new .sh script with only the lines relating to init.d.
[HTC Sensation] axetilen:
no no no

these lines must be in init.qcom.post_boot.sh or at least any .sh file in system/etc

init.d folder scripts are controlled by .sh files outside the folder

if you create a script in init.d -> wont work

copy init.qcom.post_boot.sh from Bricked kernel and copy to your kernel

also write these lines into that init.qcom file too
[HTC Sensation] Sultanxda:
I know that. That's why I said that I would make a new .sh script, not a regular script.
[HTC Sensation] kamilmirza:
r7.5 is running smooth with the following:

UV (192MHz at 725mV, and so on)

intellidemand (maxfreq = 1350)

zRAM

mpdecision

no GPU OC

uptime= 3h

deepsleep= 1h

no reboots and shutdowns, yet
[HTC Sensation] ali_l67:
so we must not delet .sh script ?
[HTC Sensation] Sultanxda:
R8 released

Okay everybody, r8 has been released and I finally got the scripts to be automatically removed by themselves AND added a script to execute your init.d folder, so everything should be working. I finally figured out how to do this correctly and the way I fixed this is completely different from what I was doing before, so give r8 a try. I apologize for all the problems you guys were having :(
[HTC Sensation] StuifzandNL:
Witch is the best governor to play graphic games??
[HTC Sensation] Sultanxda:
Lagfree. The only governor in my kernel with better performance than lagfree is obviously Performance.
[HTC Sensation] axetilen:
lagfree is good but it may cause lag while watching movie

lagfree is so-called a battery-friendly of ondemand and it works like between ondemand & conservative

ondemand with performance preset is faster than lagfree

the faster one is interactive but you kernel doesnot have -> I don't like this gov because it is not battery-friendly

I also like lagfree. I'm not sure it is batter-friendly or not because it scales down quite slowly :confused: but it should save some
[HTC Sensation] Sultanxda:
There's a misconception about how lagfree works (at least in my kernel). Lagfree goes to the CPU's max freq when the power is needed. Then, Lagfree SCALES DOWN step by step. Note that it only SCALES DOWN step by step; it DOES NOT SCALE UP STEP BY STEP, IT GOES TO THE MAX FREQUENCY. That makes Lagfree the fastest governor available in my kernel (aside from Performance, of course). There's a reason why it's called "Lagfree"...
[HTC Sensation] StuifzandNL:
It will be nice if there was a special governor for heavy gaming..

Not overheating phone less battery drain and smooth gaming (:
[HTC Sensation] Sultanxda:
Maybe smartassV2? I can add it if you think it's good for gaming while saving battery.
[HTC Sensation] axetilen:
quite similar to interactive, huh?

but it scales down much slower than interactive, same as conservative

heavy gaming ---> ondemand set at 972mhz for both cores

done

smooth + cool + play longer

smartassv2 = ondemand with battery friendly + screen-off setting

your kernel ondemand has screen-off profile -> no need smartassV2
[HTC Sensation] XeloOw:
I used Smartass on my N1 and it was the Best

Envoyé depuis mon HTC Sensation Z710e avec Tapatalk
[HTC Sensation] StuifzandNL:
Thanks buttons are pushed (:
[HTC Sensation] seandk:
Don't worry about this.

Nothing is perfect, and even less at the beggining.

But you have the merit of providing a good and fast support, and it's the most important after all.

Envoyé depuis mon HTC Sensation XE with Beats Audio Z715e avec Tapatalk
[HTC Sensation] kamilmirza:
+1

true that! :victory:

---------- Post added at 04:22 AM ---------- Previous post was at 03:57 AM ----------

what about GPU rates?
[HTC Sensation] aliko007:
Update to 3.0.58 maybe ??
[HTC Sensation] axetilen:
I leave it at 267mhz
[HTC Sensation] AsmirGT:
Hello everybody,

thanks android 1-7 for great job :good:.i tried your kernels since r6 but i cant notice any big difference as good as "remove mod kernel(origin)" on viper 1.6.2.

i tried faux 123 10b kernel and it seems for me to be smoother and better benchmark with antutu .

sultan and origin both about 8200-8450 without sd card test and faux 10b about 8800 both intellidemand and same frequencies.

sorry for my bad english,my native language is german

So long
[HTC Sensation] Sultanxda:
R9 beta 1 released

Okay everybody, I'm releasing a beta version of r9 for testing. In r9b1 I have changed the GCC optimization flag from -Os to -Ofast, making the kernel 10% bigger but optimized for speed. I'm going to need feedback on the performance of r9b1. Beta releases do not install an init.d script nor do they include an Aroma installer. You can download beta releases under Betas in the Download section of the OP. Have fun!
[HTC Sensation] almostthere:
Meh...antutu is always inaccurate about benching anything. Kernel's are subjective but am experiencing fairly smooth game play on NFS Most Wanted which before this was laggy as hell on other kernels. So as long your happy with whatever you're using, stick with it

And by the way, on R8
[HTC Sensation] almostthere:
Did a quick flash and bench and everything seems fine and smooth, abit smoother but Antutu spazzed out again for the I/O and SD Card test so that was discarded. Noticed reboot to recovery was very fast though when I wanted to flash back on R8
[HTC Sensation] AsmirGT:
over 9000 thats nice, my score with faux 10b 8800 is with NO GPU OC and CPU at default 1566MHz without SD Card benchmark.

hier is the antutu result with only OC CPU and SD Card Bencmark:
[HTC Sensation] reddvilzz:
Eh.. after flashing this kernel, looks like my statusbar dissappeared for a moment and every apps are fc'ing in the first opening after reboot. This happens after every reboot. But after that it works fine.

Anyone know this problem?

I flashed it not from freshly installed viper rom. I flashed it after 5 days using venom rom with the bricked kernel and i wipe cache + dalvik and then flash.

Did i do somethig wrong in the flashing process or it isn't compatible with the viper? Because when i see the kernel section in venom hub there are no sultan kernel here. Help please anyone?

Sent From Viperized Sensation
[HTC Sensation] sepsep 21:
I flashed r9b1 with no problem. No fc happened. No problem with statusbar. Everything is completely stable and my phone is working smoothly
[HTC Sensation] Sultanxda:
That's weird. I'm on ViperS and that doesn't happen to me. The process to flash my kernel is the same as all other kernels.
[HTC Sensation] remcoros:
Hey android1-7

I would advice against compiling the kernel with -Ofast.

See this for some discusssion about compiling linux kernels with -O3/-Ofast:

http://unix.stackexchange.com/questions/1597/compiling-gnu-linux-with-o3-optimization

I would go with -O2, which enables most safe optimizations.

Here's a list of all possible parameters and good explanations: http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#Optimize-Options

Also, the difference between -O2/3 is probably not noticeable for normal users. They will probably just swipe trough menu's, try some games and give "wrong" feedback, based on the current state of the phone. Where they 'think' it will be faster or slower due to the new kernel. Where in fact it is due to caching, multi tasking, syncing or other background processes.

just my2c.
[HTC Sensation] reddvilzz:
Hmm weird. Can you tell me the steps to flash it?

Does it affect from what options i enabled when i flash the kernel or something? And btw i'm using the sensation xe does that matter?

And 1 more sometimes it freezes after around 10 minuter or so i don't know maybe because the spiking cpu usage and then after 10 seconds freeze it reboot by itself

Sent From Viperized Sensation
[HTC Sensation] Sultanxda:
That's why I put it as a beta. So far all the releases besides r9b1 have been compiled with the -Os flag for the reasons that you gave; I just wanted to see if -Ofast/-O3 offered any significant benefits because Bricked is compiled with -O3. Would you recommend that I keep building with -Os or switch to -O2?
[HTC Sensation] Sultanxda:
You are flashing it correctly. Are you undervolted? If so, then try removing the undervolt.
[HTC Sensation] paranull:
is there any aroma version for r9 r1 beta?
[HTC Sensation] sepsep 21:
No. Not yet.
[HTC Sensation] mani1999:
Come on....:rolleyes:
[HTC Sensation] Sultanxda:
Install the newest aroma version then install the beta and all your Aroma settings will still be there. Betas won't really have Aromas unless I'm adding features to the Aroma. It is like this because I want the kernel to be tested, not really the Aroma.
[HTC Sensation] oran3e1:
Good benchmark results but slow when using it compated to the latest bricked kernel, sorry but this needs to more updates and less options in the aroma launcher because and im guessing alot of people dont know what most of them are.

thanks anyway :)
[HTC Sensation] Sultanxda:
It shouldn't be running slower than Bricked (unless you're using different settings)... Is your second CPU core coming online properly?
[HTC Sensation] Imaginexist:
can someone put up good choices to make then for the options in the aroma installer, ? i kinda rushed through it since i didnt know many myself, but im sure theres a good setup thats universal.
[HTC Sensation] 69gm:
Just curious...will you be upgrading to 3.0.58?

Thanks!
[HTC Sensation] Sultanxda:
Eventually. I don't know how to modify the official 3.0.58 patch to make it work with ARM kernel source, so I'll wait for DK to upload his 3.0.58 changes and I'll add them to my source.

EDIT: DK uploaded 3.0.58 source so I'll try patching my kernel now.

EDIT2: I tried patching my AOSP kernel with DK's new 3.0.58 source and it didn't boot up. Guess you'll have to wait a little bit for 3.0.58 (I'll try doing different things to patch it up later). Also, I looked at what was patched and the things that were patched were really minor and won't really have a massive effect for us.
[HTC Sensation] reddvilzz:
Yes i use the -9% + undervolting. Okay will try to change the undervolt.

Sent From Viperized Sensation
[HTC Sensation] Sultanxda:
Alright everybody, we WILL be getting 3.0.58. Just realized what I was doing wrong :)
[HTC Sensation] Harbir:
Nice man r9b1 is blazing fast and my bench mark are also increased keep up the good work but the battery drain is also high in beta v don't know why will u be including the fast v as there is no bootloops
[HTC Sensation] Sultanxda:
I think I'll leave the -Ofast optimization on if people think it is fast. The 3.0.58 version will come tomorrow because I've run out of time for today (I have school tomorrow).
[HTC Sensation] remcoros:
Just take my words as c developer or do some research yourself. With -O3 you disable C standard compliance. Kernels are complex code and you don't want to run into weird issues because you think you can squeeze that last 0.5% performance out of it.

Do some research yourself please before sticking with it. Or ask faux as he have a good understanding of the code in android Linux kernel.

Edit: I was just reading your other thread and you already found the issues :)

Note that playing with compilers is not an easy thing and you should really have good understanding of what the implications are. Just because they named it -O'fast' doesn't make things go magically faster. Read the documentation of your compiler and do some background checking on Google when cooking on this stuff.

You will actually learn a lot by doing so. And it will avoid issues for other people.

Btw. Very nice job you're doing here on the kernel cooking. Also considering your age and going to school etc. You're very active and helpful to people. Keep up the good work.

Also, I'm running your kernel too ;)
[HTC Sensation] Sultanxda:
I posted that before I made an unbootable AOSP kernel when I switched it to -Ofast. Switching this kernel over to -O2 should help performance a little bit considering that I've been compiling with -Os for all my releases. Rest assured that I won't be using -Ofast or -O3. Tomorrow's beta will include -O2 optimization, GPU underclocking, Linux 3.0.58, and smartassV2.

I am also well aware of the funky stuff -O3 and -Ofast can create (including slower code, and, more recently, bootloops), which is why I've been playing it safe with -Os for all my releases (except for the beta). I just thought it would be a fun/interesting test to try out -Ofast.
[HTC Sensation] remcoros:
Ok cool. I just wanted to emphasise it a bit because as you say it. It's funky stuff :)
[HTC Sensation] Harbir:
canj u please tell whats the problem in ofast as i am not facing any not even a bootloop or reboot?
[HTC Sensation] remcoros:
If you're a developer. Google it. If not. It's unexplainable.

Programming code can be a complex thing. Especially kernels as that is one of the layers closest to the hardware.

The links I posted earlier (the gcc manual page) will explain a bit.

Also 'I do not get bootloop' doesn't make sense. No offense Btw.

I can give you a PC program which makes your computer not reboot or crash but will cause GPU rendering issues when you play your favorite game.
[HTC Sensation] Sultanxda:
-Ofast enables -O3 optimizations and adds other optimizations that disregard strict standards compliance and can cause problems in the compiled code or even make it slower. Also, if -Ofast increased performance then the difference in performance between -Ofast and -O2 would be so small that you wouldn't be able to notice it. -Ofast can also create programming loops and increase the size of the compiled code (there are a ton more potential problems to using -Ofast/-O3 but I'm not going to put them here). For all my releases, I've been using -Os, but I'll switch to -O2. -O2 adds more optimizations than -Os and the optimizations that -O2 adds are perfectly safe. In all honesty, -Ofast/-O3 isn't really worth the risk.
[HTC Sensation] kamilmirza:
dear android1234567,

can you fix the battery temperature? it's always on 11.5 C

[silly suggestion] can you put the CPU temperature on battery temperature :D
[HTC Sensation] sepsep 21:
My battery life is good with r9b1.
[HTC Sensation] kamilmirza:
after upgrading to ViperS 1.6.2

my toast notification background color + all the windows has become gray :( it was black before

i think it has something to do with the 'color depth'

i have change it 32bit (as well as 24bit) and restarted my device but no gain :(

please check the attachments :(

any suggestions?
[HTC Sensation] ivicask:
This has nothing to do with kernel, it was compiler error which deleted some parts from framework while we where fixing some other bug, we fixed it and testing it for now..

Cant believe how much trouble this gives you..grey or black..lol :)
[HTC Sensation] kamilmirza:
lol thanks :D

didnt knew that it has nothing with the kernel :silly:

you can't imagine how much trouble it is giving me :p
[HTC Sensation] paranull:
waiting for the new 3.0.58 release, cant wait to test the new features! love the kernel btw no more reboots or lag ;) thanks
[HTC Sensation] Balikesirli:
I found an issue:

Transition animation will get disabled.

I don´t knot why.

I activate it manually in developer options, but after some time it will disable.

I active it again, but after some time it will disable again!

It happened 4 times so far.

ps. I don´t install any new stuff, only this kernel.. i am comming from latest faux kernel v10b8
[HTC Sensation] Sultanxda:
What the heck... lag, in my kernel? I'm not letting any lag survive. Might be because the default I/O scheduler is set to BFQ or it might be something else. Rest assured that the lag will not live in my kernel for long as there is no place for it. This is still only the first release; thanks for your feedback, everyone :) I think I'll change bases to Bricked for now as it seems a lot of people find Bricked to be the fastest. Time to make it faster :D Expect another release some time today

EDIT: Forgot to add this: XxXPachaXxX and I discussed this and it turns out the source I built from has a bug that hurts performance a lot, so I'll be changing bases.
[HTC Sensation] chickenz88:
Yea, ur default I/O is bfq, but I changed it to cfq before back to Brick, but it's really not better than bfq. Btw, Brick is not fastest kernel, I think almost peope use it for battery life, The fastest is Faux kernel...

We always remember your effort and credit, keep ur works up. Thanks!
[HTC Sensation] tichyline:
The kernel is running fine only its get lagy if we change default cpu settings.

Now on vipers 1.6.0 running and i report battery live! For now everything is stable normal fast...

But for me also after opening some app also very lag :'(

Need update...
[HTC Sensation] Sultanxda:
I wasn't able to get Faux to boot up when I compiled with Linaro, so I'll just try using the normal NDK toolchain. I'll take your word for it that Faux is the fastest :). If everything works when I build with Faux then I will rebase my kernel to that.
[HTC Sensation] XeloOw:
We want a good battery life too , not only performance :D !!

Good luck Android123456789
[HTC Sensation] Sultanxda:
You can enable kernel based mpdecision, use different CPU governors, etc. Most of the balance between performance and battery life is decided by the user :)
[HTC Sensation] axetilen:
have you tried to changed something like up_threshold, two_phase_freq,...?

changing these things can give different results in battery life and performance

I think your kernels sometimes too focus on performance? :confused:
[HTC Sensation] Sultanxda:
There are settings like that in the menu configuration for Lagfree, Badass, and Intellidemand (my kernel has the 3-phase algorithm for Badass). I won't be modifying the CPU governor files themselves nor will I be modifying the thresholds for Badass, Lagfree, and Intellidemand because right now they're working like they're supposed to and I don't want to mess something up :)
[HTC Sensation] dollyaja:
How to make a good set for undervolt,mpdecission etc to make good batt life, not so lame on performance