yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] BigBoppa:
Due to the missing zsl drivers the phone can only shot one picture.

It will processing this one picture, so it can´t improve it and processes nothing real.
[HTC Sensation] show-p1984:
It will work, but I don't understand what is there to find? I told you the name, one google search would have brought you to the path (/system/etc/) and deleting it is really hard, yeah granted. It's best to let a script mess with the kernel defaults and set it with another app back to defaults again. Sure. From behind through your body right between the eyes.

Don't ***** me if you experience any problems.
[HTC Sensation] tinker2000:
Loving the 1.3.5 with IC3.3.5. Lovely job Mr Kernel Haxxer :)
[HTC Sensation] mattdub1:
Seriously? are you really getting an attitude because I asked you for help? I appreciate you doing all this work for what you've created and I realize you've had to answer what in your eyes are a lot of stupid questions, but you don't need to treat me like I'm so beneath you.
[HTC Sensation] tinker2000:
What (I'm guessing) show means is that its best to leave it alone and let it run itself (like he does).....but if you dont want that, you may not get the support that you want/need... personally I like Faux Clock...it works, but I only use it for the clock speed. I have a script (thanks Show) for the Under volting. If I'm being a twat, feel free to tell me (anyone)
[HTC Sensation] show-p1984:
Where did I get attitude?

I just pointed your nose to sth you could have seen yourself, sure this in inconvenient for you to acknowledge, but this is not my problem.

I wasn't treating you like you are beneath me, I just treated you in line with your question.

(And my conclusion was purely logical, there was no knowledge in there that you didn't have at this time too. Or at least I hope so)

The problem behind all of this is:

You will have any kind of problems, and storm this thread and ask for help because you borked it. And I can look for an error a whole day where none is. To be honest most of the time this kernel is public I spent not on actual development, most of the time I spent here, in the forum, trying to recreate errors, tell ppl what they should or should not do, etc.

Hell, don't get me wrong, I am all for questions. But please let them have a little niveau. I mean: You don't go to your car mechanic and tell him: Hey my gastank has a leak. So I have strapped a basin with a hose beneath it that fills everything back where it belongs. That should work shouldn't it?

Of course it works! You have already made sure of that! The question is: Is that reasonable?
[HTC Sensation] tinker2000:
Hi Show.... Any news on the proper release?

....latest general Beta is superb...had 8000 on CF bench and not a single gremlin in over24h...camera has seen mucho use too.

cheers
[HTC Sensation] mudhi:
v1.35 test ... :D

6 hours idling the phone over nihgt, with some background data usage, consumes only 3% battery :eek:
[HTC Sensation] Gunkk:
[Edit: Just re-ran CF-bench a couple times again, and the Java result is back to where it should be.]

Hmmm... Low java score. This is after full wipe Oct 18 Energy 1.35 test, no cam fix.

Sent from my Bricked Energy Sensation.
[HTC Sensation] show-p1984:
I am testing the final 1.4 overnight / tomorrow a few hours and will release it tomorrow. (only minor changes)

I am too tired now. (2:40am)

gn8 ;)
[HTC Sensation] mattdub1:
Inconvenient to acknowledge? no not at all..I never said I couldn't have googled where the init script was (your right about that), but I asked you a question about app vs script, and I never said anything was your problem. I hardly think that type of question would easily pull up on google. All of what you provided was not stuff I had previous knowledge about so you are incorrect in that assumption, and throwing the line that you "hoped" that I had that knowledge is unreasonable. "Treating me in line with my question" proves that you were treating me like I'm stupid. It proves by what you said that my question was not worthy of asking in your eyes.. I don't believe that it was out of line to ask if the app taking care of min scaling would be just as good as deleting a script, because I'll bet that is not common knowledge here on XDA, and IS something that should be asked of a developer who makes kernels. Using your analogy, do people go and just put any part in their car? No, they refer to the manufacturer's suggestion. I was just trying to do a little preventive maintenance according to the recommendation of the manufacturer.

Regardless, I have deleted the script and appreciate the knowledge that you provided me, I just felt a little disrespected.
[HTC Sensation] mudhi:
I wrote this for my feel on this thread.

kernel developers or any other developers are really helpful, especially show-p, out of my curiousity, I'd pm him with a question on how to compile an android kernel, he point me to a tutorial site, so I did but failed, and ask him again why? he also answered me. Then I started researching, I know I'm a noob, it took me one week just to setup an environment and compiled the first working kernel from source. So... if show-p is that much helpful enough, he may took 3 days and nights inorder to answer my doubts. :D

show-p (and other developers) is already doing incredible work, they consumes most of their life except deep sleep also known as slow-wave sleep (see wiki), not including other stage like dreaming. :D Yet they still spending time for people's doubts. When using custom kernel, that also means you had already having basic knowledge of linux and android SDK, and also responsible for any glitches you may encountered, yet show-p is trying hard with happy attitude to answer doubts. You know how hard is just to debug or finding a line of code in C ? it may took forever in a loop. :D

Also, not all glitches are related to ROM or kernel or apps, it may hardware itself, for instance, this is what I experienced. I had the same stock ROM with same configuration, which I made out of the kitchen, reboots, black screen and crashes found on Bricked v0.91 ~ 1.35 and other kernels, even the stock kernel, but it was healed by itself, it never happened anymore no matter what tweaks I applied. Also seen this happened to a PC, it maybe the chip, some electronic parts or even the battery or power supply.

So... keep on trying or research, not to blame anything, if not, just stay with the stock one with s-on, let htc doing all the work.

This is a bench from using v1.35 test on stock ROM that I made for myself, it must be scored better but because of the optimization that CPU1 would not kick in if not needed.

Uploaded with ImageShack.us
[HTC Sensation] broncogr:
Ok guys, I am the second mod that drops in to clean the thread in one night...

Please stay on topic!!
[HTC Sensation] Gunkk:
Down 2% in 6 hrs... overnight. That's < 0.5% drain/ hr while sleeping with an Anker. Amazing!!!

Show, you're a genius!

Sent from my Bricked Energy Sensation.
[HTC Sensation] mat9v:
Good battery life.

Here is my from past night.

Notice that for 2 hours there were no energy lost (strange thing for me).
[HTC Sensation] mudhi:
For curiousity, I cat the following 2 paths.

cat /sys/devices/platform/kgsl/msm_kgsl/kgsl-3d0/gpuclk

300000000

cat /sys/devices/platform/kgsl/msm_kgsl/kgsl-2d0/gpuclk

228571000

2d and 3d have different clock?
[HTC Sensation] show-p1984:
Yes. Those are two different processing units, hence they have different clocks.

(in fact there are 2 2D cores)
[HTC Sensation] dingolino:
Hi show

could you give a little bit more technical background why:

- the file size from1.35 is fairly smaller than from 1.2final (my guessing is that you got rid of even more unnecessary stuff)

- ondemand in your kernel is better for battery life than smartassv2 (you mentioned this recently)

Best regards

dingolino
[HTC Sensation] show-p1984:
#1 Already answered. I grabbed mdeejays port of the XZ compression from his github, fixed the compile for O2 and tweaked it a bit for speed. That's why. XZ compression is a LOT better in compressing "uncompressable" data. No worries, kernel is still compiled with O2 not Os. (If I would compile it with Os and XZ I bet it would drop below 2megs :D)

#2 I tweaked on demand heavily. And due to the fact that our cpu can change is clocks very fast there is no need to keep it up for a while before dropping down. That's why smartassv2 might consume more battery than ondemand. Soon(tm) there will be another governor to choose from: badass. But it's testing and development was pushed in the background because of the ZSL drivers and other stuff.

KSM info: (Kernel SamePage Merging)

Dalvik does not support KSM out of the box. I recompiled it and got it to work with Sense, but it is very very experimental (works though, around 15% decreased). I think it is best to let ROM cooks decide if they want dalvik to support KSM or not. As long as there are no ROMs capable of using ksm, it makes no sense to include it. (I will only provide KSM in the future. I will not support a hacked Dalvikvm)
[HTC Sensation] mishufac:
hi show-p

First of all i want to thank you for the awesome work you're doing for the sensation kernel. I'm using it since day one and i had a hunch that it'll be awesome when baad started to include in his IC ROMs ( never feeled the need to change either one :D )

I'm using latest test 1.35 and i'm wondering if you can do a little more UV. Now, i am at 1.53Ghz @ 1100 mV (lower voltage it's not stable) but at lower frequencies 192-486 it is at the same 812,5mV. I think that the cpu it supports lower than this. It's just ny idea to save some battery in stand-by.
[HTC Sensation] show-p1984:
The values in the kernel are default values that work for everyone. Due to every CPU is different, everyone may or may not uv further. If you want to max it out use System Tuner and do it. I will not decrease UV further by default, because it is likely that some ppl start having freezes/blackscreens.
[HTC Sensation] mat9v:
Show told me that he uses new compression algorithm for the kernel so the size is smaller.

Ondemand being better is due to (I think) the upclock/downclock curve - it quickly scales up and equally quickly scales down.

I think he meant the minimum voltage of 0.8125 - is it possible to lower it to like 0.750? But I suppose the voltage regulator is unable to go lower?
[HTC Sensation] V6-Maniac:
At this moment i feel like a complete noob, maybe i am.

Or i'm over looking something very small.

But i've got a issue with virtuous OC or any other daemon OC in combination with bricked 1.3.5.

I implanted everything in the right place.

- 83oc init.d script

- Virtuous oc bin file

- Virtuous daemon script

- Virtuous threshold files

- daemon controller

the daemon controller gives me the exect cpu freq which are available.

Only the max freq on wake up is set to 192mhz.

When i set a random speed configuration the daemon controller say it's set.

But checking with "quick System Info" it still logs the 1536Mhz.

But if i use for example setcpu or fauxclock although they haven't any thing to do with virtuous oc they will set the correct speeds.

So the Virtuous oc deamon isn't working properly or doesn't get the right CPUfreq tables

Does anyone have clue why?
[HTC Sensation] mishufac:
I know that every cpu is different, because i can't get it stable @1.89ghz for example, but it handle UV very well. Can you point me in some direction to reduce UV? I have some basic knowledge about linux.
[HTC Sensation] jerrylzy:
Do you mean the voltage value of 192 mhz?

echo "192000 750000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

:)
[HTC Sensation] show-p1984:
No idea and i do only support my kernel. ;)

It is possible but it is not recommended. One of my Sensations runs fine @ 1914Mhz but 12.5mv below the min value will let it reboot instantly. So I do not think that there are much chips out there which could handle this.

I already did. Read my post again, if you still don't see it, read it again.

If you still fail to see it press STRG + A on this page.

System Tuner was the answer I gave you.

___
[HTC Sensation] V6-Maniac:
I know show and your damm right you do:D

But it has to be possible to run your kernel without a CPU profile app and let it run with a daemon instead.
[HTC Sensation] show-p1984:
My kernel provides the interface via sysfs. Settings those with a script yourself, or via shell works wonderful.

That's the only answer I can give you. So it is not my problem ;)

(and I do not know all oc apps out there. I only use 2: SetCPU/System Tuner if I want to test sth. Generally I set all my settings with a script @ boottime and I have no additional memory/CPU usage and no app asking for su permissions all the time :D)
[HTC Sensation] jerrylzy:
The reason for the max freq set to 192mhz is that show's kernel is a little bit different from others,others are 1512mhz but show's is 1536mhz,and you can set it to 1536 and there will be no problem!
[HTC Sensation] V6-Maniac:
I know it's not your problem ;)

And indeed i can run it with a init.d script or something else and it runs my desired speed conf.

But i wanted to let a user with no skill run his own speed without the use of a CPU profile app.

Which does indeed take resources, well i think i have to look for a other way round...

Thx...
[HTC Sensation] artymarty:
Hey show,

I had a crash (happened a few times, but this is the first time I have got to a PC in time to download the files.)

I am running IC 2.2.5SE, fairly standard stuff..

Let me know if you need more
[HTC Sensation] mat9v:
Show - you said that in sleep mode you disable (stop?) GPU core completely?

What is the default sleep frequency of 2d/3d core?
[HTC Sensation] mishufac:
i used System tuner to reduce the voltage, but i cannot go bellow 812,5mV
[HTC Sensation] mattdub1:
apparently I missed some action
[HTC Sensation] mat9v:
Then do it by hand:

echo "192000 812500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "310500 825000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "384000 825000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "432000 837500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "486000 862500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "540000 875000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "594000 887500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "648000 900000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "702000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "756000 950000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "810000 962500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "864000 987500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "918000 987500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "972000 987500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1026000 1000000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1080000 1012500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1188000 1037500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1242000 1050000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1296000 1075000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1350000 1100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1404000 1125000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1458000 1137500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1536000 1150000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1566000 1175000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1620000 1200000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1674000 1225000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1728000 1250000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1782000 1275000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1836000 1287500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1890000 1300000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

It's the same way System Tuner does that if you tell it to set it @ boot and not when System Tuner starts. It creates a file in /etc/init.d with all config variables and voltages are one of them. Play with them to your heart content but remeber they are executed on every boot so you can hose your system that way if you go too low.
[HTC Sensation] mudhi:
V1.35 test knock out my head, I have hard time of draining the battery (calibration purpose), heavily use it for 3 hours yet still have 40%. :D
[HTC Sensation] show-p1984:
Rofl, the content of your last_ksmg:

cat: can't open '/proc/last_kmsg': No such file or directory

:D

It more and more looks like 2.3.4 Sense 3.0 has some libs that are not working nicely with the new mm and kgsl drivers.

I think we can ignore that, new rule:

1.4 = 2.3.5 and 2.3.4 = 0.91 ;)

If someone wants to go ahead and mix some libs of 2.3.5 into 2.3.4 I am not stopping him / her.

At this point it does not seem possible to maintain one Kernel for two versions, and I will not release 2 different Kernels (The Sense 3.0 Kernel would miss several of the key features of upcoming 1.4, which would render that procedure useless).
[HTC Sensation] LKW-Hermes:
Test 1.35

i test it and no problems so far just wait vor 1.4 LOL GREAT WORK SHOW
[HTC Sensation] the_scotsman:
Ah nice...amaze camera working now..will give it a run now (running IC 3.3.7).
[HTC Sensation] mudhi:
v1.35 test, stock sense 3.0 ROM. tested with both UV, UC and original UV and UC. battery below 20%

Hitting a clip on youtube or rotating the screen, the screen frozen, adb shell still working, and so here is the last_kmsg.

http://dl.dropbox.com/u/39118212/last_kmsg.zip

BTW, the first freez, I remove battery and restart device, I can't cat the last_kmsg, and then restart the phone again, and last_kmsg can be cat, but I see many lines that is unusual, something like below, I can't remember the whole phrase.

Restarting Linux version 2.6.35.10 .... htc (gcc version 4.4.0) may xx 2011
[HTC Sensation] KAwAtA:
Haven't had an FC yet using camera or anything else.. been several days and working great! Waiting for 1.4
[HTC Sensation] show-p1984:
Finally a useful kmsg. Thanks.

But sadly I need to confirm my thoughts: It's a lib problem. The kernel is fine. No errors, no problems. It just seems that the old libs are not completely fine with the new kgsl driver functions which will lead to those problems.

Try v0.91 it is 100% stable on 2.3.4 Sense 3.0 (as long as your ROM does not use hacked libs instead of Sense 3.0 stock)

or upgrade to sense 3.5 Android 2.3.5.
[HTC Sensation] mudhi:
Ok, I think I will try to update to 2.3.5, but sadly, I'll lost several applications (specific to TW sensation).

One more question, just to confirm, what I need for 2.3.5 is the stock ROM + amaze camera mod and your camfix + v1.35 kernel? because last night when I tried, I've encounter several application issues.
[HTC Sensation] show-p1984:
You can use whatever rom you want (it must be based on Android 2.3.5 Sense 3.5 though). Installation procedure: Rom -> camfix -> kernel.

If you choose the amaze cam mod:

Rom -> amaze cam -> camfix -> kernel

PS I recommend you to wait for a few minutes.
[HTC Sensation] KAwAtA:
why do you want him to wait .. Im so excited (it was all in caps, I didn't know xda fixed it so it would prevent caps!) Just trying to express my joy, hurry up! please!
[HTC Sensation] ziggy1001:
Thanks for that much appreciated:) I've been using system tuner, fauxclock etc and can't find a list of the screenoff/on governor min/max speeds commands to put in init.d could you or someone else provide a template?
[HTC Sensation] mat9v:
Try these:

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

to set ondemand governor for core0 and substitute cpu0 with cpu1 in above patch to set core1

echo "1728000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

to set max speed for core0 and substitute cpu0 with cpu1 in above patch to set core1

echo "192000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

to set min speed for core0 and substitute cpu0 with cpu1 in above patch to set core1
[HTC Sensation] show-p1984:
[B][U][SIZE="4"]***** v1.4 *****[/SIZE][/U][/B]
[I]/*
* Due to massive changes in the video drivers, this is no longer
* compatible with sense 3.0. If you choose to stay on Sense 3.0
* please use Bricked v0.91.
*
* Flash camfix-for-v1.4 to get full cam support with the new
* sense 3.5 & amaze cam. (Except Burst)
* http://code.google.com/p/bricked/downloads/detail?name=camfix-for-1.4.zip&can=2&q=
*
*/[/I]
[B][U]Simple:[/U][/B]
* Drastically increased UI performance (higher oc)
* Drastically increased battery life (introducing better graphics scaling)
* increased responsiveness
* increased native write speed
* Smaller kernel size (better compression)
* the usual amount of tweaks and fixes
[B][U]Technically:[/U][/B]
msm: kgsl: 8Stages 3D scaling, highest @ 300Mhz (fraction 33)
msm: kgsl: 6stages 2D scaling, highest @ 266,7Mhz, 33,35% Overclocked (fraction 100)
msm: kgsl: GPU off while screen off!
msm: kgsl: improved KGSL suspend
smp: improved CPU hotplug
cpufreq: max OC risen up to 1914Mhz
cpufreq: cleaned ACPU table
mm: adjust vm ratios increase swappiness by 50% decrease dirty_ratio by 50%
mm: increase readahead buffer
msm: scm: Cleanup interruption handling
msm: scm: Mark inline asm as volatile
msm: scm: Fix incorrect cache invalidation
msm: scm: Fix incorrect cache invalidation part 2
msm: scm: Add atomic SCM APIs
arm: Ignore certain memory optimizations on MSM8x60
ARM: Factor out common code from cpu_proc_fin()
proc-v7.S : Fix MMU disabling in cpu_v7_reset
ARM: 6535/1: V6 MPCore v6_dma_inv_range and v6_dma_flush_range RWFO fix
ARM: 6398/1: add proc info for ARM11MPCore/Cortex-A9 from ARM
ARM: 6380/1: Introduce __sync_icache_dcache() for VIPT caches
ARM: 6528/1: Use CTR for the I-cache line size on ARMv7
ARM: Improve the L2 cache performance when PL310 is used
msm: kgsl: Use the correct virtual address for pmem regions
msm: kgsl: Delay 30ms to make sure GPU is ready during resume time
msm: kgsl: Update pwrlevel_change
msm: kgsl: Add sysfs attribute to turn GPU DCVS off/on
kernel: Add XZ compression (orig: mdeejay, fixed for O2)
decompress: removed deprecated error function
rcu: priority boosting for TINY_PREEMPT_RCU
hash: The new jhash implementation
ext2: speed up file creates by optimizing rec_len functions
ext3: speed up file creates by optimizing rec_len functions
ext3: Add batched discard support for ext3
dm io: remove BIO_RW_SYNCIO flag from kcopyd
dm kcopyd: delay unplugging
compile & compatibility fixes
[HTC Sensation] sindresv:
O'joy! :D Flashing now :D
[HTC Sensation] mat9v:
Out of curiosity, will there be GPU320 version?
[HTC Sensation] emanon:
thanks for the update...
[HTC Sensation] sindresv:
First impressions of 1.4: Smoooooooooth, FAST and stable! :D Loving it!

Will report if I get any problems. Insertcoin 3.3.7 with beats and amaze.
[HTC Sensation] show-p1984:
If I can find the motivation to do so, and if it is demanded, yes. But I think that the kernel is fast enough @300 and the additional heat and power usage makes no sense.
[HTC Sensation] mat9v:
Ok, count me in as one demand :) Seriously, I'm just asking very nicely.

The kernel is so smooth I won't use butter from now on :)
[HTC Sensation] kayroccs:
hey just a quick ques but y did u exclude 1.2 clocks on 1.4 ?
[HTC Sensation] show-p1984:
I cleaned the whole ACPU table and threw out a few steps.

use 1188Mhz = 1.2ghz. (It's the sensations default)
[HTC Sensation] knickscity:
Show does this work good on Amaze camera?

Just the burst is inop right?
[HTC Sensation] show-p1984:
Yes. You will need the camfix.
[HTC Sensation] kayroccs:
smart that makes sense thanks
[HTC Sensation] mudhi:
I'll joined v1.4 by tomorrow, and try hacking some sense 3.0 apps to 3.5. need some sleep zzz....
[HTC Sensation] Lakeshow423:
Thanks show, I've been waiting for this! You are the man, bro!
[HTC Sensation] knickscity:
Thanks man, I'll give it a try in a few.