yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] ungraph:
Question!

Is the kernel for ICS compatible with Virtuous Insquisiton v4.0.1?

Thanks!
[HTC Sensation] krohme:
this kernel gives me fantastic battery life, CPU temperature is always low even when playing power hungry games like FIFA or shadowgun..

but then I keep getting random freeze once in a blue moon where the screen goes black & the phone becomes unresponsive, requiring a battery pull :confused:

can't work out what the cause is.
[HTC Sensation] framir:
Same issue here with no mod and latest beta!
[HTC Sensation] faux123:
Me 4 :( I had a random reboot as well... still trying to figure out what caused it.. I am suspecting 3.0.28 patches... mainline patches sometimes break more things than they supposedly fix... :( Still waiting for more logs :p
[HTC Sensation] joaquinf:
005b1 feedback

Hi! i'm testing v.005b1 and it's time i give some feedback. First of all i don't run any cpu apps, no OC, no UV. Just the kernel as is, sheer intellidemand @1,5 GHz max. freq.. More info about my setup is in my signature. Also, i do not run benchmarks, i find them useless.

In terms of performance, the phone feels responsive and fast, ui is fluid and cpu temperature is below average (~40°C for me). Although i've noticed some lag while "clicking" or selecting some options in the settings menu. When I select the option it become highlighted and slowly (about 1 or 2 seconds) fades to finally open what i've selected. This is very noticeable in settings>apps even after loading all the storage data per app.

Games are smooth, but i feel that they were smoother in v003 when both cores were online all the time, like it takes 2 minutes or so to "trigger" the second core online and up to 1.5GHz. After first 5 minutes the game run smooth. Temperature while playing is fairly low, as always with faux versions <60°C.

Battery life is great, this is the strongest feature at this moment in my opinion. As you can see in the screenshots attached this graph shows my phone batt under HEAVY usage. I did it on purpose to test the batt life and the result speak by itself. Those peaks you can see were reboots i did on purpose while trying to test intellidemand tweaks posted by faux using SetCPU. I decided not to keep it for now.

+25 hours of juice

~4,5 hours of screen on with auto brightness

45 mins of GTA (heavy GPU game)

it doesn't appear but, i played shadowgun, mc3, Draw Some, Radiant defense. All together for around 1,5 hours more. Meaning +2 hours of heavy gaming usage.

Other apps i've used: Whatsapp, gmail, browser, xda premium, facebook, twitter, camera, Speed test, Google+.

+2 hours of music (mostly screen off of course)

am i missing something? .. ooh! phone calls :D i use it for calling too: +1 hour.

Auto sync activated in: Gmail, facebook and weather.

Lucky last screenshot is the amazing kernel batt life while idle. 7 hours 41 mins and is a flat line. of course this was overnight, no more than 5 mins of screen on, wifi and data turned off (also testing OTA fix :D, which works :D) but you get an idea of both scenarios. Heavy and near-to-no usage.

EDIT: no random reboots or sd card issues for me ... no issues whatsoever :D

Thanks for your work faux. This kernel is amazing, and eagerly waiting for moar performance tweaks, specially for UI improvement.
[HTC Sensation] Astug:
This. Any idea as to why this is faux? This lag isn't present when using the bricked kernel.
[HTC Sensation] ifti_a:
I'm using the kernel in my sig but for some reason it's not showing the CPU temp in system tuner ?

Anyone else have same issue ?
[HTC Sensation] dublinz:
I am on Pyramid-ICSFAUX-sense-005b2 for the past 2 hours, so far no problem, but i have to admit that i didnt had any problem with 005b1. Now i did tried to recreate problem that you lads had with 005b1 (on charger with 100% full battery) so far for last 45 min no reboot. I am using Elegancia rom 3.6.1

Edit: I DO have lag in settings, as described by joaquinf ...., ?
[HTC Sensation] ImHuge07:
My phone rebooted the other day and got caught in bootloop while using v4 and android revolution hd 6.0.0.

It just rebooted again today when I received a text message. I was browsing the web and heard the start of my text message notification then it restarted. Here is the last kmsg

Failed to open the file (java.io.IOExceptioat com.estrongs.android.pop.app.h.run(Unknown Source)

at java.lang.Thread.run(Thread.java:864)

( Did I grab the right message?)
[HTC Sensation] faux123:
the file is located in /proc folder so you will need to grab /proc/last_kmsg it's just a plain old text file.
[HTC Sensation] ImHuge07:
I see a kmsg but I don't see a last_kmsgn the proc folder. I used two different file explorer apps with both in root mode. Am I doing something wrong?
[HTC Sensation] dublinz:
This command might be handy " adb pull /proc/last_kmsg"
[HTC Sensation] MuertoKo:
I'm installing your 005b2 as a final try to get those little bugs solved :P

I'm out for a week to Mexico so won't be able to share my results though... :( Hope you have 006u final build version out or something like, with your actual actualization rythm everything is posible!

See ya soon!
[HTC Sensation] ImHuge07:
Okay ill do this when I get home. Anything I can do in terminal to get it?

---------- Post added at 10:55 PM ---------- Previous post was at 10:30 PM ----------

Tried to do that but says it does not exist.

My phone has restarted two more times since my first post btw.

Am I doing something wrong or do I not have a kmsg for some reason?
[HTC Sensation] dublinz:
did you used command that i send you? if you did you should have last_kmsg on your hdd (in same folder where you have adb....e.g. c:/adb)
[HTC Sensation] ImHuge07:
Yes and it says remote object does not exist.
[HTC Sensation] faux123:
Not all reboots would produce /proc/last_kmsg esp if you pulled the battery.
[HTC Sensation] ImHuge07:
Ah okay. Just had 3 reboots and all happened when dealing with text messages. First was when I received one, second was when I was writing one, third was when I was scrolling through past texts. I didn't pull the battery or anything. I'm using the stock text app.
[HTC Sensation] baste07:
did you UV?
[HTC Sensation] ImHuge07:
If your asking me... no. Not using any CPU apps either.
[HTC Sensation] pnut22r:
Hate to beat a dead horse, but is it likely that USB otg will ever work for this phone?

Just curious. Nothing more.
[HTC Sensation] rickyiswhite:
hmm this kernel seems to make my phone overheat badly. took a picture then put phone back in my pocket but noticed a hot sensation on my leg I took out the phone the camera app was still open and the phone was at 150 F°

also seems like it forces both cores to run and I never enabled that option... see screenshot

was this temp just from talking then charging

Sent from my Primed Sensation 4G with Beats Audio
[HTC Sensation] faux123:
sigh...
[HTC Sensation] PaulGiz:
I feel for you buddy.
[HTC Sensation] rickyiswhite:
?

Sent from my Primed Sensation 4G with Beats Audio
[HTC Sensation] faux123:
Everyone, please get the highlighted concept removed, forgotten, erased from memory. My kernel DOES NOT FORCE 2nd CORE ONLINE after boot. MPDECISION was the one forcing 2nd Core Online/Offline. By default, in a DUAL CORE system, both CPUs are ONLINE AFTER BOOT PERIOD.

Because of many complaints about my kernel "FORCING 2nd CORE ON" (which is a TOTALLY WRONG concept), I have made my intellidemend governor to be smarter by adding capabilities to OFFLINE 2nd core after careful load calculations while screen is ON.
[HTC Sensation] rickyiswhite:
I only said that because it hasn't happened with a different kernel....

but I flashed bricks kernel and it seems I'm still having the overheat problem I'm causually browsing web twitter and Facebook and its at 130 degrees Fahrenheit and its usually not... any ideas?

Sent from my Primed Sensation 4G with Beats Audio
[HTC Sensation] faux123:
Isn't inquisition ROM based on a Leaked Sense 4.0 dump? When you load leaked ROM or pre-release software, you are bound to encounter bugs and such. Most users of my kernel have claimed the opposite regarding temperature... most said my kernel is cool even when under heavy load.... So I am not sure why you are experiencing such high temperature. It seemed that you may have a rogue app or bad system service that's constantly running thus heating your phone...
[HTC Sensation] PaulGiz:
I tried VI myself for a laugh and found it did run pretty hot.

Besides possible issues with ported (not leaked) ROM, when you went back to Bricked you need to re-enable thermald and mp decision. The lack of thermald with bricked may be cooking your phone.

Faux properly installed and running on a compatible ROM runs very cool under all conditions.

P.
[HTC Sensation] jordin1128:
I'm using 005b1 with CD5.1 but running 1188/384...phone operates well @ 1.5 but just saving some extra battery :D ..Anyway, battery monitor widgets indicates the highest temp I've reached is 53.0(f)...20 hrs+ with 46% left :D ..screen time is 2.5hrs.

I would have to agree with Paul and Faux..look here -> http://xdaforums.com/showthread.php?p=16534005 <- this might help!
[HTC Sensation] rickyiswhite:
no I'm running Prime 5 now, and it must be an app cause it does it only sometimes

Sent from my Primed Sensation 4G with Beats Audio
[HTC Sensation] HunnyBearLewis:
I couldn't believe it when I read 53degrees F, then I noticed you checked with Battery Monitor Widget and that only checks the batt temp...use System Tuner and you'll see ridiculously high CPU temps (which I see on any kernel when I game so I'm not having a go at anyones work here...)
[HTC Sensation] jordin1128:
That's right! Thanks bro!
[HTC Sensation] show-p1984:
Erm woot?

My kernel cooks nothing. thermald and mpdecision are automagically found and renamed back to their defaults by my install zip. (which enables both of them)
[HTC Sensation] HunnyBearLewis:
This is completely off topic in regards to thread but had to point out how awesome the word "automagically" is. I will be incorporating that into everyday use. Thanks ;)
[HTC Sensation] BioTecK:
Me 5! ;)

I just had a black screen when I received a call. I couldn't answer or see who called me and I had to take out the battery.

Right after restart I went to /proc/ and took the last_kmsg file which you can find here.
[HTC Sensation] PaulGiz:
Sorry, Show-p. I gave obsolete info. It is almost impossible to keep up with all relevant threads all the time.

I also like automagically. It really is a descriptive, colorful and just happy word.

P.
[HTC Sensation] japinder:
+1

Thanks for making it my word of the day. :)

My first thought was that he meant 'automatically' ;)
[HTC Sensation] baste07:
Is the latest still beta 1?
[HTC Sensation] Hawke84:
yes i think so, ive not seen any other betas released by faux..
[HTC Sensation] sjh4:
http://faux.androidro.ms/

beta 2 avaialble
[HTC Sensation] Hawke84:
no been released by faux yet no idea what changes are, if its stable, or even if its safe to flash...
[HTC Sensation] PaulGiz:
I think it's proper protocol to allow dev to release each version, not just grab it.

1. Has it been tested?

2. What is changelog? Do you eat things from the floor? I like to know what is going onto my phone.

3. If it isn't released, it isn't supported. Hope it works, but if something breaks, you're on your own.

4. Betas are for testing. If you don't know what you have, and it isn't supported, what exactly are you testing?

A little consideration is in order for the people who give us these great advances.

IMO

P.
[HTC Sensation] sjh4:
agreed, however all i did was repost the same link already given earlier in the thread by another forum member to access beta1 prior to release

regarding beta 2 , have done an nandroid backup and installed it, so far no issues compared to beta 1
[HTC Sensation] Hawke84:
thanks paul, id like to add to this that kernels do have the ability to brick a phone as its editing the boot.img...
[HTC Sensation] Pikaraph:
I just got a shutdown after a phone call, but no /proc/last_kmsg after reboot...

I'm on ARHD 6.6.1 and faux 5b1
[HTC Sensation] faux123:
Open Beta may not be stable and may cause issues with your phone!

By loading open beta you have agreed to:

1. To report all random reboots with associated /proc/last_kmsg

2. To provide feedback on errors or bugs with detail phone information such as ROM, kernel version, and apps

3. Participate in Forum discussions for the beta software with others without FLAMING each other or post useless information such as:

a) Phone doesn't boot (without providing any additional information, ROM versions etc)

B) phone is too hot (without providing any additional information, ie OC freq, UV etc)

The Open Beta system is designed to have the community help each other and the developers. This way, all potential bugs are flushed out so the final released version will be stable and error free. The more actively you participate in Beta Testing the better the final product will be (you are really helping yourself to create a better community software).

If you do NOT agree with the statements above, DO NOT load my Open Beta software.

Kernel 005 Open Beta Build 2 (build #9)

https://twitter.com/#!/faux123/status/192317464149901314 (BETA is always Ultimate Edition with everything turned on unless stated otherwise!)

[ build 2 ]

Add cpufreq driver patches

Update KGSL drivers to CAF latest

Update Bluetooth drivers to CAF latest

Add ARM TrustZone debugging

patched Thermal Driver to CAF latest

Add mutex protection for Intellidemand (this should eliminate random reboots :p )

[ build 1 ]

Minor overclocking code clean up :P

patched latest CAF HDMI bug fixes

patched latest CAF BT bug fixes

patched latest CAF KGSL bug fixes

Add more debugging for USB OTG :P

Create more intellidemand tunable parameters via sysfs interface

Fixed minor thermal monitor issues

Applied latest Google's interactive governor patches

Patched OnDemand and Intellidemand's rate sampling transition issue

further tuned intellidemand to be more intelligent ;)

patched to 3.0.28 from kernel.org

Intellidemand Governor tweak:

Introducing Smart Core Management :D

Automatic offlining of 2nd CPU core while Screen is ON.

Scenarios:

1- While Screen is ON > 3 min, and average load of the CPU is < 35%, then CPU1 will be taken offline.

2- While Screen is On, if average CPU load > 35%, CPU1 will be Online and both CPUs max frequencies will be limited to 1.13 GHz Max

3- While Screen is On, After both CPUs' Max is limited to 1.13 GHz, when the average CPU load has dropped down to less than < 25%, then both CPUs Max freq will be restored to 1.51 GHz Max (then go back to scenario 1).

-- for 3D Games or GPU intensive apps (GPU in Turbo Mode and Load is >= 50%), both CPUs's max frequencies will be restored to 1.51 GHz and both CPUs will be online.

NOTE: DO NOT use BENCHMARK APPS to compare my kernels to others. All those are ARTIFICIAL benchmarks and mostly measures CPU raw performance. If you insist to use those to compare kernels then set to performance governor before comparing for Apple to Apple comparison.
[HTC Sensation] ximocko:
Awesome Faux! I'm running your 005 b1 and it was just great. Ah I was wondering that whether should I wipe the battery status every time I flash kernel?! Thank you very much Faux.
[HTC Sensation] BioTecK:
Awesome.. Thanks! I will flash this right away and report back if I notice something odd!
[HTC Sensation] joaquinf:
Wiping Battery stats does nothing .. this is a myth. Check here for the explanation given by one of the google engineers. Just wipe dalvik+cache and should be ok
[HTC Sensation] stuart0001:
True. It's amazing the myth still gets so often perpetuated. What always make me smile is when people state their battery life has improved after doing it. Ahh, the power of placebo.

On a related note, I don't think its necessary to wipe dalvik, just cache as there are no changes to apks with kernel flashes. However, I'm happy to be corrected as I'm often wrong.
[HTC Sensation] PaulGiz:
If an apk accesses a service controlled by kernel, there is an eensy weensy chance that something may get screwy. It's just good insurance, but may or may not be needed every time.

P.
[HTC Sensation] henrylar:
USB host?

Hi Faux

I am writing here because this is a very good kernel. However, the thing that could make my sensation to an even more interesting thing would be if USB host could be enabled. I have seen this working for some kernels used in certain devices running CM7. The reason for it is to get digital sound out. I have seen that several hifi nerds have bought amplifiers with DA converters. I have a FIIO E17, which sounds wonderful on my computer. I have no clue about the work to do, so this is just a humble question.
[HTC Sensation] overthinkingme:
I'm pretty sure that's a WIP. I've seen him state it a few times in this thread.
[HTC Sensation] faux123:
:rolleyes: OTG is WIP. Love them TLA!
[HTC Sensation] joaquinf:
This will give you an idea of USB OTG ...

http://xdaforums.com/showthread.php?p=24003612&highlight=usb+otg#post24003612

http://xdaforums.com/showthread.php?p=24886760&highlight=usb+otg#post24886760

http://xdaforums.com/showthread.php?p=24411071&highlight=usb+otg#post24411071
[HTC Sensation] zimphishmonger:
Lmao, another otg usb question?!

If it's not on the changelog, it probably isn't working yet

Sent from my HTC Sensation 4G XE with Beats Audio
[HTC Sensation] baste07:
just flashed 005beta2

will check it out how it goes
[HTC Sensation] bstylz911:
Link please :)
[HTC Sensation] joaquinf:
Sigh..

Posted in the previous page ....
[HTC Sensation] baste07:
heheh i can feel your sigh
[HTC Sensation] baste07:
Got a bit faster drain on 5b2 but usage has been heavy
[HTC Sensation] malybru:
Hi,

Your link to 005b3 does not seem to go anywhere.

:confused:
[HTC Sensation] GideonX:
Sure it does, look a little harder.
[HTC Sensation] BioTecK:
Cool! I'll flash it when I get home! ;)

Hi,

Use this link: http://faux.androidro.ms/Pyramid-ICS-sense-005b3.zip
[HTC Sensation] TheUntouchable:
Faux, thanks for your great work! But why always linking to twitter AND rootzwiki? :(
[HTC Sensation] bstylz911:
Is the new beta for faux stable ?
[HTC Sensation] asesino:
Can we get at least 24hrs to test drive a beta kernel before releasing a new beta :p thank you sir for all the work.
[HTC Sensation] Arie-:
Phone crash v005b1

I do not know whether you are still interested in bug reports for v005b1 but here it goes.

What happened: My telephone was hooked to my charger which was hooked to a power socket, not in the computer. When I pressed the power button, the screen remained black, before that I had not used my phone for a few minutes. How many minutes I cannot remember but this can be anything between one and ten minutes. I disconnected the charger, pressed the power button but still my telephone would not respond. All this time the Orange charge indicator kept burning.

Now I removed and plugged in again the battery, pressed the power button and my phone started immediately. When my phone was booted I immediately opened ES, went for /proc/last_kmsg but this file did not exist. In stead of this file I therefore copied kmsg, maybe this is of any use for you. I estimate that between starting the phone and the copying of the kmsg file is a maximum of 4 minutes, I really immediately when I could operate my phone copied the file as soon as I had located it.

My phone:

Model: HTC Sensation

ROM: HyperNonSense 2.2 - http://xdaforums.com/showthread.php?t=1581619

Kernel: Faux v005b1

Possible related apps:

SetCPU (although I have not used it to change settings)

System Tuner:(I use it to take a look at CPU Times and Voltage Table)

Script Manager Adds: I use it to set the CPU speeds and Voltage table on boot. This script was last modified April 16th 19:30 or so. Therefore I do not think this is a crash caused by under volting.

V6 Supercharger: I don't know to what extend this script changes stuff to the kernel or ROM or whatever, but I try to list everything which might be related.

Edit: The attached files are kmsg.zip, this _is_ a zip file which contains the kmsg file. The voltage.zip file contains my script to set CPU speeds and voltages.
[HTC Sensation] GideonX:
It was just released, stability data is probably not there yet from the folks who flashed it.

Why not try it yourself and see?
[HTC Sensation] baadnewz:
system\etc\thermald.conf

content

sampling 1000

[tsens_tz_sensor0]

sampling 3000

thresholds 55 65 75 85 95

thresholds_clr 52 60 70 80 90

actions cpu cpu cpu cpu shutdown

action_info 1134000 972000 648000 384000 6000

so either delete that file or edit it to reflect ur frequencies, but can overheat ur cpu
[HTC Sensation] smint86:
but that can't be the final solution. there must be some error in the kernel itself, because even with stock kernel the performance seems better when cpu is under heavy load, or am i misguessing?

i will return to stock kernel as long as this isn't fixed properly, anyway thanks to faux123 at this point and of course also to baadnewz! using IC 2.4.1 with stock for now...
[HTC Sensation] baadnewz:
i was never afraid to admit that my kernel knowledge is very limited. (you can see i never made my own kernel, always used stock or snq-'s as default in my roms)

it might not even be a problem with faux kernel at all, the problem might lie in the incompatibility between 2.3.3 build from htc sources kernels (htc only released sources for 2.3.3 kernel ) and 2.3.4/5 roms (or just my rom ) - so let's not point fingers just yet.
[HTC Sensation] 3c:
Agreed, no finger pointing... The fact is that something gets misconfigured somehow... Don't want to blow my device or CPU by deleting a needed file...

This file is from 2.3.4 or from the kernel? Just wondering? It would seem users on 2.3.4 get better results on stock kernel, just trying to understand how to modify this file safely.
[HTC Sensation] baadnewz:
that is a configuration file present in all roms but the values differ from one base to another . it basically measures cpu temp, and if it beyond some values it reduces cpu speed to prevent overheating (and reboots or device behaving strange)
[HTC Sensation] BigBoppa:
... and it looks like in 2.3.3 kernel with 2.3.4 libs that the reading of the sensor is different. My sensation throotles cpu[1] speed even if cold...
[HTC Sensation] 3c:
Not my question, the file is self explanatory.

If this file is part of 2.3.3 and 2.3.4 and is the same for all... It can't be a ROM issue, only the kernel is misbehaving in some ways, overheating the CPU obviously!

IMO, if file is in all versions, the daemon checking CPU temp is doing its job the same way. The daemon is part of the ROM, not the kernel, right?

Then something is obviously going past the 60° when we have a 2.3.3 kernel + a 2.3.4 ROMs, something that does not happen when both kernel and ROM are 2.3.3 or both 2.3.4.

Does this sound correct?

Then there's no way to solve this but get a 2.3.4 kernel or raise the temperature values in that particular file? Do you know what temp values where set in 2.3.3? Maybe those were higher in the first place?

So until it's "fixed", any 2.3.4 custom ROM will have lower performance than a stock 2.3.4! Right?

EDIT:

Wow, so the 2.3.4 libs are messing the reading? Providing values in different units? Though the config file is the same on 2.3.3 and 2.3.4, or is it different too?

So we might be able to check the reading?

Faux123, can you modify your kernel to report the CPU temp in /cpu0/cpu_freq/cpu_temp or some other files so we can compare?
[HTC Sensation] Joshhedge:
I'm just using SetCPU as Daemon isn't working great for me with ARHD 3.0.4 and Faux 0.1.0. With Daemon It was smooth, but performance in games and benchmarks was poor whilst with SetCPU It is smoother and performance overall is amazing...
[HTC Sensation] baadnewz:
ok, got to the bottom of this.

in 2.3.5 leaked (my rom)

file reads

sampling 1000

[tsens_tz_sensor0]

sampling 3000

thresholds 55 65 75 85 95

thresholds_clr 52 60 70 80 90

actions cpu cpu cpu cpu shutdown

action_info 1134000 972000 648000 384000 6000

in 2.3.3 (1.35 official ruu)

file reads:

[tsens_tz_sensor0]

sampling 5000

thresholds 60 75 85

thresholds_clr 57 70 80

actions cpu cpu cpu

action_info 972000 648000 384000