yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] show-p1984:
Just compare them...

I did remove the lowmemvalues as well as the values for dirty_ratio and swappiness.

They were "compatible" before, but they overwrote kernel defaults.
[HTC Sensation] show-p1984:
Got the rpcrouter crashes fixed. (mainly surfaced when using the camera)

KGSL should be fixed in a few seconds too, will release a new test then.

Edit: One time I rely on XDA's doublepost melt into one feature and it fails me -.-
[HTC Sensation] show-p1984:
Bricked v1.45-test #495 Openbeta

Changes:

#472

* Removed audio idle wakelocks. (should increase battery life while listening to music)

* fixed two memleaks

* New toolchain gcc 4.6 linaro

-> A newer compiler usually produces more efficient code and detects more code fails

* Fixed tons and tons and tons of code errors. snq- helped a lot.

* Improved CPU sleep states (moar savingz!)

#482 (internal)

* msm: add dimmed capacitive LEDs

* removed notification LED timer

* changed min/max panel brightness

* msm: scm: update from upstream

* msm: cpufreq: set safe default min and max speeds for boot (1536/192)

* msm: kgsl: Don't check for idle while suspended

* msm: xo: Add NULL pointer and error pointer check

* arm: vfp/nwfpe: updates

* arm: vfp: patched fpu calculations to speed things up

#490

* REVERT: arm: vfp: patched fpu calculations to speed things up

---Not stable, needs more work =/

* Deleted useless cpu check.

* xz: Fix missing <linux/kernel.h> include

* updated toolchain

****Due to many requests, here you got it:****

* mm: CLEANCACHE (Backport from linux-3.1)

* drivers: staging: ZCACHE (Backport from linux-3.1)

* drivers: staging: ZRAM (Backport from linux-3.1)

* setup: Bash magic for the install script to let you just install it, without any configuration. Install zip, done!

* script: ZRAM swap size set to 100MB

#495

* re-enabled cpu sleep stats

* changed to noop scheduler

* drivers: staging: zram: prevent null pointer error

* drivers: staging: zcache: prevent null pointer error

* arm: mach-msm: Updated rpcrouter to linux-3.1

---This will (hopefully) fix all rpc crashes.

---Mostly surfacing while using the camera/youtube

* drivers: kgsl: code fixups

* Revert "msm: kgsl: Delay 30ms to make sure GPU is ready during resume time"

---Tests have shown that 30ms are not enough on the pyramid.

---It should only take the GPU 10ms at max, but sometimes the GPU will hang even with 30ms.

---Increasing this to the old value (50ms) seems to solve this problem.

Camfix from 1.4 still valid.

Click me

I ran out of apps I could open and deposit into the (Z)RAM :D

If you want to see the magic happen:

cat /sys/kernel/mm/cleancache/*
cat /sys/kernel/mm/zcache/pool0/*
cat /sys/kernel/mm/zcache/pool1/*
cat /sys/kernel/mm/zcache/pool2/*
cat /sys/kernel/mm/zcache/pool3/*
cat /sys/block/zram0/*
free

No thanks

to a certain developer for cleancache/zram.
[HTC Sensation] deagleone:
moin show... no dl link :mad: :p
[HTC Sensation] show-p1984:
ofc Oo

It even says "click me"
[HTC Sensation] Catpoule:
Show, i noticed that when I switch to 1118 , amaze camera V8 freezes each time i try it ... it does not freeze at 1536 ,neither at 178O but under 1536 it does freeze when taking pic.

and "1.45 test" seems like it's not any longer battery saver !! :eek: lol

As i already told you in antoher post, i had a freeze when moving my apps to sd card, at this time it was also underclocked at 1340.

Each time I underclock, it seems that freeze occures ... :confused:
[HTC Sensation] deagleone:
to many beers :D

@ Catpoule

which ROM?
[HTC Sensation] show-p1984:
Try latest test, many crashes should be solved (if not all).

That said, new page, lets bump the beta:
[HTC Sensation] Catpoule:
lol :D don't drink so much !

i'm on insertcoin actually 3.4.0
[HTC Sensation] deagleone:
use amaze Cam v7 little french girl :p

P.S. goooooooooooooooooooooood morning!
[HTC Sensation] Catpoule:
ok, going back to V7 :p

and trying new bricked test ....

report back
[HTC Sensation] nrvnqsrxk:
Will test new beta for Pyramid 8.2.1

Sent from my HTC Sensation
[HTC Sensation] Catpoule:
Good news !

i test it again and no more freezes or crashes, it is smooth, fast and all working fine for me. even at 1008 it works great ..... very good job !! you did it ;)
[HTC Sensation] show-p1984:
Well I did bork it in the first place, so I need to fix it :p
[HTC Sensation] deagleone:
quick impressions of .495 @ ic3.4.0

(amaze)cam is working (exept burst) , apps starting quick as hell, youtube test... no hang ups...

integer Performance exploded to an awesome level!

and the reaction of the ui is a dream...

for the bench-guys

.495 @ ic3.4.0 @ 182-1538 MHZ ondemand (no tweaks)
[HTC Sensation] rawrfische:
Sorry for the late report back, show. Had to do the Halloween thing with my son. :). I'd talk about my previous reported issue, but...

I've since replaced the init.d scripts with yours and flashed the latest test. The difference is like night and day! Swap space was quickly getting eaten up (seen by typing free command in console) and I have yet to experience any UI lag like before.

Will keep an eye on it and report back tomorrow. Still on Pyramid 3D 8.2.1.
[HTC Sensation] inffy:
Testing the new LeeDroid with the newest test version....

Freaking faaaaaaast :D this thing flies...
[HTC Sensation] mat9v:
Gah! Why doesit not "fly" for me? I did exactly the same - deleted all scripts, used those 2 that Show-p posted and still it crawls.... I think I will try disabling Zcache and test again...
[HTC Sensation] millerman:
Hi show-p1984,

may be it is possible to enable ppp support for async serial ports &

ppp support for sync tty ports in the new kernel.

It seems to be missing PPP support so many VPN tools that use Point-to-Point Protocol do not work.

Any Ideas ?

Regards Millerman

from my HTC Sensation Z710e using XDA App
[HTC Sensation] show-p1984:
Will be included in the next test version which will also include another zcache null pointer fix.

Thanks to dingolino for "finding" this, even though he posted it into the wrong thread :p

And now: gn8! :D
[HTC Sensation] n4sa:
One thing i've noticed is that the whole system slows down when downloading an app from the market. It becomes unusable. Any ideas why?
[HTC Sensation] artymarty:
- - - - - - -

FIRST RUN

- - - - - - -

/ # e2fsck -y -v -f /dev/block/mmcblk0p23
e2fsck -y -v -f /dev/block/mmcblk0p23
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p23: recovering journal
Clearing orphaned inode 60 (uid=1001, gid=1001, mode=0140777, size=0)
Clearing orphaned inode 59 (uid=1001, gid=0, mode=0140777, size=0)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p23: ***** FILE SYSTEM WAS MODIFIED *****

3412 inodes used (4.46%)
692 non-contiguous files (20.3%)
6 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3193/201
124222 blocks used (40.62%)
0 bad blocks
1 large file

2400 regular files
995 directories
0 character device files
0 block device files
0 fifos
0 links
3 symbolic links (3 fast symbolic links)
5 sockets
--------
3403 files

- - - - - - - -

SECOND RUN

- - - - - - - -

/ # e2fsck -y -v -f /dev/block/mmcblk0p23
e2fsck -y -v -f /dev/block/mmcblk0p23
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

3412 inodes used (4.46%)
692 non-contiguous files (20.3%)
6 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3193/201
124222 blocks used (40.62%)
0 bad blocks
1 large file

2400 regular files
995 directories
0 character device files
0 block device files
0 fifos
0 links
3 symbolic links (3 fast symbolic links)
5 sockets
--------
3403 files
/ #

So I guess it worked yes?

Thanks for pointing that out :)

To do a random check to see if it needs to be run, what would I type in?

e2fsck /dev/block/mmcblk0p23 ??
[HTC Sensation] V6-Maniac:
Did the same thing although the kernel flies i can't seems to get those scores.

Your close to what i saw of the pica Show posted on his twitter.

Mine seems to stock at 6000 with the init.d files provided by Show.
[HTC Sensation] McLongDong:
Is this compatible with InsertCoin Sense Android 2.3.4 V2.2.5 SSE? This is an older ROM so I don't if this kernel is suitable.
[HTC Sensation] deagleone:
@ V6-Maniac

Did u use shows init.d scripts?
[HTC Sensation] V6-Maniac:
Yes i did use those files.

Tried several dalvik settings, and running the latest #495

Also tried deleting every of my own init.d scripts and run only those provided by Show.
[HTC Sensation] lamecake:
Sorry for being a noob, but the whole compressing ram stuff sounds unnecessary for me.. :d Any easy way to permanently disable it? Using Insertcoin 3.4.0!

Btw your latest kernel is running like a charm! Had some freezes on youtube before, but as stated in the changelog, all gone on 495.
[HTC Sensation] V6-Maniac:
Compared my Antutu bench with the one from Show on his twitter. (http://twitter.com/#!/showp1984/status/131130675549048832/photo/1)

It's seems that my device hangs on the 2d/3d graphic bench.

While no one tweaked there build.prop i should get higher scores.

What i've done so far:

- Used the init.d scripts provided by Show

- Checked my symlinks

- Played with several dalvik commands like:

dalvik.vm.execution-mode=int:jit

dalvik.vm.stack-trace-file=/data/anr/traces.txt

dalvik.vm.lockprof.threshold=500

dalvik.vm.dexopt-flags=m=y

Maybe someone else got a suggestion?

Edit:

Forgot the pica:

Although Antutu says 1890 i tested @ 1728mhz
[HTC Sensation] nrvnqsrxk:
Not experiencing freezes anymore on Pyramid 3D. Thanks for the fix!

Sent from my HTC Sensation
[HTC Sensation] mat9v:
If you look closely, those benchmark scores are high only in 2D/3D section - you can achieve that by inserting "debug.gr.swapinterval=0" into build.prop file (but it will cause tearing and some artifacts in games/GUI). As far as I know Samsung increased in SGS2 the framelimit (default in Android @60fps) to 120fps. I have somewhere screenshots of even higher scores.

Unless I am completely wrong here and in that case I humbly ask Show-p for info on how he configured his Sensation to get that score :)
[HTC Sensation] V6-Maniac:
I did a search on this also and this "debug.gr.swapinterval=0" can be a pain for some Sensation Gamers.

I want to ask Show if Uncap can be our the solution?

Edit:

debug.gr.swapinterval=0 does increase the FPS from 60 to 75.

But in daily use it cause (non games) in gives my hick ups and the scrolling in the appdrawer isn't smooth

Edit 2:

After disabling dalvik.vm.execution-mode=int:jit it gets a bit better but the scores don't come higher as 6100 in antutu
[HTC Sensation] Gtj94:
gave it a try and it didn't really do much upfront besides make scrolling laggy :/

Edit: ran a test and my 2d fps can reach 160 so it is doing something
[HTC Sensation] mat9v:
It's basically a V-Sync option - so expect tearing and lagging.

Oh, and it's not true that "debug.gr.swapinterval=0" increases the framelimit to 75 - you can test it yourself by running Quadrant - the Earth test should show over 100fps.
[HTC Sensation] V6-Maniac:
Yep, it is and thats why i'm gonna end this command line option.

I rather have a smooth system then a high score which has been forced to.

Edit:

@Show-p1984

Is it possible or placebo: but my Sensation feel snappier at #490
[HTC Sensation] Forceing:
Im on ARHD 4.1.5 with Bricked 1.45-495. Everything is fine, but I have two problems. First I can not use Bluetooth, it cannot connect to the other phone. Second the button backlight is not working. Where comes this bug?
[HTC Sensation] Alex_electro:
Noob Question...

Hi, have a weird question... When I look in Both bricked and stock kernel to compare, most of the difference is a lot of files related to camera in stock one...

So those file are not in custom kernel so is there a way to merge it all,

And if the issue with amaze cam is caused by shared registry entries by cam and tweaked by the kernel (to improve performances)...

So if amaze installed right after kernel before reboot is those registry entries will revert to amaze need instead of kernel need...

Sorry for miss-threading my question...if so

Cheers
[HTC Sensation] rawrfische:
The commands to make and activate the swap file are in /system/etc/init.d/90zram. So I guess in theory you could remove this file before your next reboot. Someone please correct me if I'm wrong because I haven't tried it myself.
[HTC Sensation] dcfowler:
@show - First impressions are that #495 rocks. No force closes, and after 7 hours of fairly typical usage I'm still at 77%....

Great work, many thanks!!!! :-D
[HTC Sensation] sirbilbo:
Agree this is just amazing, speed is superior and my battery last at least 36 hours :D btw. using anker 1900 mA.

(what I use you can see in my sig) Perfect combination :D :D
[HTC Sensation] guyd:
Yes. That's what I am using ;-)
[HTC Sensation] MarlinFF:
What are your guys recommendations for CPU governor and CPU max? Thanks

Sent from my HTC Sensation 4G
[HTC Sensation] undercover:
Search this very thread for more opinions but I recommend ondemand and 1.2ghz
[HTC Sensation] Astug:
Do I have to flash the camera fix for Leedroid's v4 (aka Sense 3.5)? It doesn't include the Amaze camera, or does stock camera require the fix aswell?
[HTC Sensation] show-p1984:
I have quite the opposite experience here. With CC/Zcache the market feels a lot better than before.

Yeah, it's done.

Just check your last_kmsg from time to time. It will warn you if it is needed again ;)

This /\

Remove the 90zram script and do this: swapoff /dev/block/zram0

Then you don't need to reboot ;)

Vsync@off is only useful for an accurate benchmark reading without the fps limit blocking our phone. Same as on the pc this will introduce some lagging/tearing/artifacts, so it's better not to use it for everyday usage.

And I think it's a placebo :P

Capacitive button backlights are working and BT is working too. There must be some other problem @ your end.

(I am not assuming a kernel bug until I see some logs which do prove that)

The mA reading is very inaccurate on our sensation. Some kernels will only give you ~14-80mA and will drain the battery faster than bricked. Just look at your runtime and ofc, after wiping your battery stats let the phone collect new ones for about 2 days.

It may also have something to with my correction of a few very serious coding fails from HTC in our battery driver. So maybe I fixed it and it is now displaying the right value? xD

I don't know tbh, I never gave anything on this reading. For me it is important how long the battery lasts and not what this strange (mostly random) number tells me ;)

Stock 3.5 does require the camfix as well. (the sense 3.5 camera is even newer than amaze, it uses ZSL so the camfix is required to get rid of it)
[HTC Sensation] tinker2000:
I dont know if anyone else has experienced battery death when the phone is off. I went to bed last night at around 1AM and the battery had discharged itself over the course of 6h with the phone powered off. (Was 90% whenb I went, Anker 1900mAh battery)

Its weird and I have no explanation of why this may be., i have not added any more applications and nothing was running before i turned it off.
[HTC Sensation] show-p1984:
If you turn it completely off, nothing will be running.

If you turn it into hibernation (fast(quick) boot enabled) nothing will be running.

BUT:

If you turn it off while connected to a power supply, the recovery will startup and charge your phone.

If you turn it into hibernation while connected to a power supply, the installed ROM will startup and charge your phone.
[HTC Sensation] tinker2000:
Thanks Dude.

I am a little concerned about this latest release at the moment. I dont recall it being plugged in when i turned it off, but am not 100% sure so will check later.

Another thing, I seem to need more processor power with zram running, ie I have had to up my min frequencies to 384MHz instead of 192. This resolved a sluggishness issue I was seeing when it woke up. I'm not sure (IMO) if zram is making the kernel better....but she is smooth when fully woken up and being mollycoddled.
[HTC Sensation] mrg02d:
Im seeing very low standby current guys! 2mA/H with this kernel and ARHD 3.6.4

Dang?

Matt
[HTC Sensation] scm_crash:
On 1.4r1, I'm doing 5 minute averages instead of 1 minute. On standby I've seen as low as -50mA but not often at all. It seems to sit around -110mA to -200mA on standby. But I'm wondering if my phone isn't giving the right numbers because my standby life is ridiculously good. I pulled it off the charger and turned the screen off... 4 hours later I checked and it was still at 100%. I don't have my WiFi on most of the time since my AT&T U-verse sucks the hairiest ones here. T-mo's data plan is actually more reliable and faster most of the time. :rolleyes:

I don't see a need to move on to 1.45 yet. I don't really care about zram or zcache. My phone's underclocked right now since I'm already running fast enough for everything. I feel that running zram and zcache will only slow things down and/or eat more battery.
[HTC Sensation] escalator:
Still got freezes with 1.45 v495. Batteydrain is much higher than 1.2.

Also some lags while using, and my Buttons no more illuminated....

Using IC 3.4.0.
[HTC Sensation] Hereisphilly:
Same here, alot of drain in #495, and my button backlight doesnt work anymore. Not many noticeable lags though
[HTC Sensation] johnkristian:
#495 got my phone really hot (and wifi never sleeps?). Back to 1.41r1 (ARHD 3.6.4). Anyway, great work.
[HTC Sensation] RussianBear:
to people who are having problems with the backlight: put your finger over the light sensor and see if it comes on. mine's working fine on the latest build.
[HTC Sensation] Astug:
Same here, works just fine with 495. No lag (on 1.18 even ;)) or higher battery drain.
[HTC Sensation] -DC-:
what voltage do you guys use @ 1.5? :)
[HTC Sensation] ziggy1001:
I just used echo "-62500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

To give me
[HTC Sensation] tinker2000:
1150000mV using init.d script to set voltages

cheers
[HTC Sensation] immunityx:
For me the latest tests with zram made things laggy and sluggish
[HTC Sensation] Blodia:
Personally I also found the latest beta with zRam slightly more sluggish.

Back on #427 and it's all good
[HTC Sensation] Catpoule:
Show,

well everything was running fine, and things turn quickly in nightmare lol

i went to market and it becomes laggy, as if something was going wrong, and it continue to be more or less laggy, taking a lot time as if it was calculating and it finished by freezing, i had to pull battery out. :confused: don't know what happened suddenly ...
[HTC Sensation] show-p1984:
Bricked v1.45-test #499 Openbeta

Changes:

#472

* Removed audio idle wakelocks. (should increase battery life while listening to music)

* fixed two memleaks

* New toolchain gcc 4.6 linaro

-> A newer compiler usually produces more efficient code and detects more code fails

* Fixed tons and tons and tons of code errors. snq- helped a lot.

* Improved CPU sleep states (moar savingz!)

#482 (internal)

* msm: add dimmed capacitive LEDs

* removed notification LED timer

* changed min/max panel brightness

* msm: scm: update from upstream

* msm: cpufreq: set safe default min and max speeds for boot (1536/192)

* msm: kgsl: Don't check for idle while suspended

* msm: xo: Add NULL pointer and error pointer check

* arm: vfp/nwfpe: updates

* arm: vfp: patched fpu calculations to speed things up

#490

* REVERT: arm: vfp: patched fpu calculations to speed things up

---Not stable, needs more work =/

* Deleted useless cpu check.

* xz: Fix missing <linux/kernel.h> include

* updated toolchain

****Due to many requests, here you got it:****

* mm: CLEANCACHE (Backport from linux-3.1)

* drivers: staging: ZCACHE (Backport from linux-3.1)

* drivers: staging: ZRAM (Backport from linux-3.1)

* setup: Bash magic for the install script to let you just install it, without any configuration. Install zip, done!

* script: ZRAM swap size set to 100MB

#495

* re-enabled cpu sleep stats

* changed to noop scheduler

* drivers: staging: zram: prevent null pointer error

* drivers: staging: zcache: prevent null pointer error

* arm: mach-msm: Updated rpcrouter to linux-3.1

---This will (hopefully) fix all rpc crashes.

---Mostly surfacing while using the camera/youtube

* drivers: kgsl: code fixups

* Revert "msm: kgsl: Delay 30ms to make sure GPU is ready during resume time"

---Tests have shown that 30ms are not enough on the pyramid.

---It should only take the GPU 10ms at max, but sometimes the GPU will hang even with 30ms.

---Increasing this to the old value (50ms) seems to solve this problem.

#499

* drivers: staging: CLEANCACHE updated (Oct 24, 2011)

* drivers: staging: ZCACHE updated (Oct 24, 2011)

---fixed 2 exceptions, causing mpdecision incompatibility

* drivers: staging: ZRAM updated to version 0.7 (Apr 27, 2011)

---fixed ZRAM device conflict once again

* i/o: schedulers: switched back to deadline as default

---noop was causing low sdcard throughput

* built with PPP support for sync tty ports

Camfix from 1.4 still valid.

Click me

I ran out of apps I could open and deposit into the (Z)RAM :D

If you want to see the magic happen:

cat /sys/kernel/mm/cleancache/*
cat /sys/kernel/mm/zcache/pool0/*
cat /sys/kernel/mm/zcache/pool1/*
cat /sys/kernel/mm/zcache/pool2/*
cat /sys/kernel/mm/zcache/pool3/*
cat /sys/block/zram0/*
free

No thanks

to a certain developer for cleancache/zram.[/QUOTE]
[HTC Sensation] show-p1984:
MP decision killed you ;)

Should be fixed in #499
[HTC Sensation] immunityx:
Damn u show i just flashed back to #427 cause it was laggy in #490/#495 now you back with more crack lol

About to try #499 and see if the sluggishness is gone
[HTC Sensation] stevendph:
latest beta #495 works great to me. Using ARHD 4.1.5, every thing is smooth, fast and my battery drain is amazing.... 27 hours on battery with moderate use (display is at 49%) and my battery now still has 55% left. I am betting if it can last 48 hours...
[HTC Sensation] immunityx:
Seems like #499 fix the sluggishness for me will test it more but so far it is better then #490/#495
[HTC Sensation] show-p1984:
EDIT:

Nevermind... missread something in the original error message -.-
[HTC Sensation] GabrielSousa:
the old version cwm 4.x.x.x ?
[HTC Sensation] 3c:
EDIT: Never mind, delete this post.
[HTC Sensation] LittleH79:
Well yes.

Just flashed the RUU, booted, did revolutionary, flashed cwm version 4.0.1.4 as suggested.

And this is the error I get:

E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2

So there's one tiny difference: (I'll copy and paste them next to eachother)

E:format_volume: make_extf4fs failed on /dev/block/mmcblk2p2

E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2

Mine says 1p2 at the end..
[HTC Sensation] mattdub1:
i was stock 2.3.3 and i rooted my phone, then wanted to upgrade to 2.3.4 so flashed melvins stock rooted 2.3.4
[HTC Sensation] LittleH79:
Yes, see above post.

To the step flashed given RUU, did revolutionary, sent CWM 4.0.1.4 with given link, chose wipe data/factory reset and got error in previous post

:confused:
[HTC Sensation] 3c:
Sorry, my bad... Was too quick as you said 'new recovery' again and your signature is still on 5.0.2.0. What are you trying to do when you get that anyhow?

I'm no CWM expert anyway, I use 4.0.1.4 because it's stable as many others do. it looks like a conflict of phone model... What are you actually trying to flash? the kernel I suppose? Not sure I can help much more anyway, it's way out of my league.

But if you explain in more details what you do, you'll save time and make everything less confusing. eg "installed CWM, now i get this error", in between I'm not sure what you did in CWM to get this result? Did you try again the full wipe script, any errors from them?

Why don't you simply: run a full-wipe, then flash a ROM and see what happens?