yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] katdog75:
Hi there!

First a big thank you to Show for all your work on bricked. I have tried both bricked and faux kernels and 1.4r has been my go to kernel because it was rock solid for me with the best battery. I love that the cam doesn't jam up my phone too! Fingers crossed for 1.6b3. So far this rom seems very snappy for me.. will report on battery after trying it out for a few days.

When show was referring to the kernel working in the new continuous mode.... Was he referring to the fast burst scene that does not work on the sense 3.5 roms? I tried loading the kernel on my husbands phone with ARHD 4.1.8 and the app was still crashing. (So I figure I just have misunderstood) I have the Amaze cam mod for my sense 3.0 and it works wonderfully except the fastburst and panaramic and had hoped that luck would have those work with this kernel... But it doesn't appear that the kernels affect theses functions.

Thanks again Show and enjoy the beer I sent you! :-)

Kate
[HTC Sensation] :
Show-p, Ive had a look at your kernel and sensation people are reaalllly lucky I have to say, its more difficult for 7x30 devices as they have a really old kernel, I posted some libs in dhd thread such as hwcomposer, genlock, libmemalloc, lib overlay and they all work perfectly fine, even showed a dumpstate of hwcomposer running and enabled, you should create ICS for sensation people :p, are you talking about real hw acceleration or hacks?? cuz im talking about real hw acceleration and no longer continuing with it on dhd, goodluck! :D
[HTC Sensation] plun:
Wiped Dalvik-cache and flashed 1.6b3.......

"Nema Problema", great work !

;)

(running LeeDroid 4.2.1)
[HTC Sensation] guyd:
wake-up call screen bug

@show-p

I did some more testing and I verified two different work-arounds for the wake-up call screen bug that still exists in v1.6 Beta 3 for my phone.

#1 - Turn off auto brightness (already known)

#2 - Set scaling_min_freq to 384000 (384 MHz)

Either one of these two methods work. When I tested these methods, I found that you must give the phone enough time to go into deep sleep after you place it into standby. I waited 60 seconds after pressing the power button to be sure the phone was full asleep before I called the phone to verify if the screen would wake-up.

My sig is upto date with rom, versions, etc.

UPDATE: After a full day of use, the bug showed up again using method #2
[HTC Sensation] katdog75:
Anybody experiencing issues with the htc browser crashing when using the back arrow button on the phone to navigate backwards? Whenever my browser opens a link in a new window and I then try to use back arrow it often crashes. When I reload the browser I am then back to my Google home screen. Already cleared cache and dalvik. Any comments or suggestions?
[HTC Sensation] guyd:
No problem here with back button in browser in ARHD v4.1.8 and Bricked v1.6 b3
[HTC Sensation] voltaje:
The new Bricked v1.6 b3 is working great in Coredroid 2.7. No problems so far in 14 hours since flashing it.
[HTC Sensation] marvelspires:
I will try here to see if decreased or eliminated the freeze ... and come back to post my opinion.

TANKS SHOW!
[HTC Sensation] xdviper:
Whoaaa beta 3 is much better than 2. I hope its not an placebo effect and actually faster but its smooth. No lag, nothing! Thanks for another release dude. Goggles also works perfectly as expected. Thanks man. I got you with a beer Thursday when checks cashed.
[HTC Sensation] mattdub1:
Neither of these fixes

Have worked for me and several others there is something else going on
[HTC Sensation] birel3107:
Using 1.6b3 with energy 6-12 and faux-clock. (Wake: 0,384-1,536, sleep: 0,192-0,432, UV: -50, smartassV2 governer)

No wake issues so far after 6 hours.

Edit: Auto brightness turned on
[HTC Sensation] arachnid1970:
Downloaded beta3 yesterday and everything works perfect...thanks@showp :)
[HTC Sensation] StuartTheFish:
I just tried it too, but the exit camera crash is still there for me, after only 5 minutes. Any chance of you 100% fixing this any time show? I like your kernel otherwise.
[HTC Sensation] Pavelol:
totally agree with you on this one.

my phone went to deep sleep (maybe 2 hours of sleep) and i couldn't wake it up.

didn't have even adb access to strip some kernel log :|

had to pull battery out :(
[HTC Sensation] Jonny:
Hi showp1984

I am just curious about the current progress of ZSL drivers as I saw in a fairly old post somewhere that ones you made crashed after 1 or 2 goes and I would just like to know if any dither progress has been made?

Kind regards
[HTC Sensation] marvelspires:
I installed today in the morning and I had two freeze, watching a video, pushed back and freeze, and the other went into the game "uno" and freeze
[HTC Sensation] guyd:
The issue you describe is different than the one I've been having. I've never had a problem with pressing the power button and having the phone wake-up. That has always worked fine for me with Bricked. The issue I've been having is related to the screen not waking up (turning on) when you receive a phone call when the phone is asleep.

Did you try the three finger reboot method prior to pulling the battery?
[HTC Sensation] masondoctorjt:
No screen wake issues for me so far. Ive Been using beta 3 since this morning and the issue usually shows up by now. I did have it reboot on me twice, but I wanted t-mobile's update so I installed ruu from t-mobile, got update, and redid root, reinstalled recovery then put beta 3 on again. Haven't had a reboot yet:) I'll keep u updated.
[HTC Sensation] V6-Maniac:
What kind of video format did you watched?

I tested my rom today to see how the Bravia engine runs.

Watched two episodes of the Iron Man and had no problems.

Back, home and powerbutton it did had any issues.

I must admit it took a couple of seconds after pushing the button and the reaction.

But thats it so no freezes for me...
[HTC Sensation] tibere86:
I wonder if this wake issue is CPU batch related. I have never had any wake issues with any version of either faux kernel or bricked kernel regardless of the ROM I'm running.

On a side note, how's the battery life with Smartass V2? I've always used ondemand as I read someplace it was the only governor which properly made use of our aSMP CPUs.
[HTC Sensation] Jonny:
That's funny I was just about to ask the same question as well!!

Also can I add, what are the differences between ondemand and smartassv2?
[HTC Sensation] masondoctorjt:
I thought it seemed related to running stock rom with custom kernel, but maybe your right, Although I do not have wake issues anymore, I did have my phone reboot itself again since doing a total reinstall including a freshly formatte sd card. I'll give it more time though as like has been pointed out, sometime time fixes weird issues. At least it wakes, I can deal with a random reboot here and there for now. Hopefully I can pull the log and see what happened if it does it again.
[HTC Sensation] ijob:
Hi there,

I have been experiencing an issue with the latest beta and with Fauxs latest Kernel too.

My location for my weather doesn't work, it always displays me as 'United Kingdom' not my actual location.

I dont know if this is an issue with recent code or whatever but with earlier kernels, there is no problem.

ROM: ARHD 3.6.8
[HTC Sensation] papete:
2 way call recording

Hi, I just have a small request:

the Kernel supports call recording (and it does), but the voice from the other party is recorded too low, and my voice is too loud. I'm coming from a HTC Desire that had the 2WC recording patch and sound level was (about) the same for both parties. Is it possible to fix this?

I'm using SKAVALEX's recording app on a sensation with the ARDH 3.6.8 and your V1.5 Kernel.

Thanks
[HTC Sensation] banesi:
Hey Show,

I've noticed that flashing Bricked-v1.5r1-beta1-528-ondmnd-1536-192.show-p1984.zip works fine for me but flashing Bricked-v1.5r1-beta2-535-ondmnd-1536-192.show-p1984.zip gives me wake up error and CPU may be pegged warnings:

D/PowerManagerService( 289): setTimeoutLocked: now=198580, timeoutOverride=-1,

nextState=0, when=205580, mDimDelay=32000, mScreenOffDelay=7000

W/SharedBufferStack( 749): waitForCondition(LockCondition) timed out (identity=

4, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 683): waitForCondition(LockCondition) timed out (identity=

3, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 289): waitForCondition(LockCondition) timed out (identity=

2, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 749): waitForCondition(LockCondition) timed out (identity=

4, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 683): waitForCondition(LockCondition) timed out (identity=

3, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 289): waitForCondition(LockCondition) timed out (identity=

2, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 749): waitForCondition(LockCondition) timed out (identity=

4, status=0). CPU may be pegged. trying again.

W/SharedBufferStack( 683): waitForCondition(LockCondition) timed out (identity=

3, status=0). CPU may be pegged. trying again.

Maybe something you introduced since this beta2 just make problems with my CPU and possibly others also, hope this helps somehow...
[HTC Sensation] Jonny:
Well if 1.5 betas give you errors, flash 1.6 beta 3
[HTC Sensation] mv0hra:
I too had this issue with most of the free ones, including TotalRecall & Recordmycall.

I started using CallRecorder by skvalex and I no longer experience these problems, the only problem I have is the quality of my recorded voice, it has a slight/medium crackle.

The kernel developer, show-p 1984, is well aware of the situation and is planning to resolve this soon, probably in the next release.

I have used the faux kernel and there are no problems relating to this. However, you do loose the amaze camera functionality.
[HTC Sensation] :
Show-p. for your current kernel you can improve 3d performance by 50% :p
[HTC Sensation] sszz:
Proposals for a stable version

Same here. I tested all the proposed solutions with 1.6 beta3 as well as my own observations (not able to wake up after deep sleep is more frequent when the phone temp is high, so I set a temperature profile in SetCPU that does not let the min frequency to drop below 576MHz till the phone is hotter than 37 Celsius), but none of them worked. Okay, I must admit, the frequnecy of the freezes did decrease but still far from 1.5 beta1 that NEVER had these issues.

Using European stock 1.50 ROM.

So here are my proposals @show:

1. Is there any chance that you can find out why 1.5 beta1 is special in terms of stability and interpret this in your new kernels?

2. if not, can you please re-compile 1.5 b1 with GPU @320Mhz? That is confirmed to be rock solid for most of us so that might be one kernel to stick with.

Thank you.
[HTC Sensation] guyd:
Have you tried going into the weather app and changing your location manually?

And are you certain that the wireless location is enabled in settings?
[HTC Sensation] papete:
2WCR

Thanks a lot mv0hra for your response. I do use skvalex and I keep my recordings from my old Desire on my new Sensation and when I hear the recordings of both the difference is quite noticeable. This Kernel has the cracking voice issue that you mention, but also there is a noticeable difference in the volume level of both parties, I didn't have this issue with my Desire.

The fact that the dev is aware of it and working on it is actually what I wanted to know, I didn't want to keep a kernel from a dev that does not pay attention to this feature.

Regards
[HTC Sensation] masondoctorjt:
+1.. I tried beta 3 all day and night. No more reboots through the night, but the nasty no wake showed up. Not as frequent as before, Maybe once every 6 hours, but it never happens with 1.5 beta 1. Here is my last_kmsg if it helps show. If you need more of it, I will have it saved so I can give it to you.

(do_exit+0x0/0x730)

[33962.645224] r6:c00dc75c r5:c00f6ab0 r4:cfc35d30

[33962.645743] msm_watchdog_resume

[33965.638448] keyreset::deferred_restart in

[33965.650686] [BATT][tps65200] TPS65200 shutdown

[33965.651388] events/0(parent:kthreadd): Restarting system.

[33965.651479] GLaDOS: Oh Joy... Another reboot. Have you nothing else to do?

[33965.651601] GLaDOS: Maybe loosing those extra 20 pounds would be a nice idea.

[33965.651662] arch_reset: mode 104

[33965.651784] arch_reset: no command restart.

[33965.651845] from arch_reset

[33966.287099] rmt_storage_event_write_iovec_cb: write iovec callback received

[33967.018880] rmt_storage_ioctl: send status ioctl

[33967.021688] rmt_storage_ioctl:rmc->msm_final_call=0, rmc->mdm_final_call=0

[33967.022115] wait_rmt_final_call_back: Wait for final MSM efs_sync: OK (rc=863)

[33967.022328] back arch_reset

[33967.022664]

[33967.022878] Restarting Linux version 2.6.35.14-Bricked_XE-1.6.beta3-ondmnd-1536-192.show-p1984 (showp1984@jarvis) (gcc version 4.6.3 20111201 (prerelease) [gcc-linaro/4.6 revision 106852] (Linaro GCC 4.6-2011.12-1~dev) ) #44 SMP PREEMPT Sat Dec 10 01:02:17 CET 2011

[33967.022908]

No errors detected
[HTC Sensation] abs_rio:
I've got the same problem. However, mine is intermittent, mostly it does show the correct location but I get the occasional United Kingdom. I'm using SENSEaY ROM.

When the problem occurs refreshing doesn't help. I do have wireless location enabled as well.
[HTC Sensation] ziggy1001:
Not too sure this is kernel or rom related i have just started getting this and multiple roms with stock and bricked are all doing the same, in the past i never got (the almost useless) United Kingdom as my location, 95% of the time i would get an accurate GPS location for my district in London

Methinks AccuWeather is to blame:(
[HTC Sensation] mv0hra:
I thought the quality of the recording was pretty good, but then I do not have a desire device to compare too. Maybe try v1.6b3 of this kernel.
[HTC Sensation] sjappie:
Beta 3 is great. Low drain. Approx 20ma when standby with BT on. Only downside i notice is some grafic lagg on smartassv2 gourvener. With ondemand no issues.
[HTC Sensation] blahbl4hblah:
Just curious. Not sure if it was brought up before. How come when I use this I only have 561mb of ram. While when I use fauxs it shows 562mb. Not a big deal just curious is all
[HTC Sensation] Ace42:
They may allocate RAM differently for drives, maybe showp puts more RAM towards something. I'm certain the difference wouldn't be zRAM, but don't worry about it.
[HTC Sensation] sszz:
last: kmsg

Another screen freeze with beta3. Hope this helps. If you need more of this last:_kmsg, please see attachment.

[13278.341599] r6:c00dc75c r5:c00f6ab0 r4:cfc35d30

[13278.342576] msm_watchdog_resume

[13278.858048] pm8058_drvx_led_brightness_set: bank 6 brightness 255 +

[13278.859330] pm8058_drvx_led_brightness_set: bank 6 brightness 255 -

[13281.326918] keyreset::deferred_restart in

[13281.351454] [BATT][tps65200] TPS65200 shutdown

[13281.352888] events/1(parent:kthreadd): Restarting system.

[13281.353254] GLaDOS: Oh Joy... Another reboot. Have you nothing else to do?

[13281.353438] GLaDOS: Maybe loosing those extra 20 pounds would be a nice idea.

[13281.353804] arch_reset: mode 104

[13281.353987] arch_reset: no command restart.

[13281.354323] from arch_reset

[13282.119916] rmt_storage_event_write_iovec_cb: write iovec callback received

[13282.790173] rmt_storage_ioctl: send status ioctl

[13282.795331] rmt_storage_ioctl:rmc->msm_final_call=0, rmc->mdm_final_call=0

[13282.795697] wait_rmt_final_call_back: Wait for final MSM efs_sync: OK (rc=856)

[13282.795911] back arch_reset

[13282.796094]

[13282.796429] Restarting Linux version 2.6.35.14-Bricked_XE-1.6.beta3-ondmnd-1536-192.show-p1984 (showp1984@jarvis) (gcc version 4.6.3 20111201 (prerelease) [gcc-linaro/4.6 revision 106852] (Linaro GCC 4.6-2011.12-1~dev) ) #44 SMP PREEMPT Sat Dec 10 01:02:17 CET 2011

[13282.796490]

No errors detected
[HTC Sensation] show-p1984:
Thank you two very much! And I was talking about the new goggles search mode ;) (Someone reported it would freeze on him, which I could not reproduce)

ZSL drivers are in the following state of progress:

First opening of the cam app works wonderfully, the second will work for some time and then freeze your whole phone.

I am currently trying to debug this issue to find out what is not being reset on camera close/open and fix it.

I would rather compile a stable 1.6 than go back to 1.5r1b1 ;)

Thanks.
[HTC Sensation] sszz:
Thank you, this would be fantastic. Looking forward to (stress) test it... :)

One observation since my last post. Going to sleep after using CPU / GPU heavy stuff, like games (NFS Hot Pursuit in my case) increase the probability of freezes.
[HTC Sensation] show-p1984:
2 kernel test to get a grasp on the black screen on call wakeup issue (seems only to be present on Android 2.3.4 Sense3.0):

(Both kernel magic versions are the same as latest b3, so you can still use the modules of that version and just fastboot boot / flash the zImage, or copy it inside the zip and override the old or whatever ;))

Linux localhost 2.6.35.14-Bricked_XE-1.6.beta3-ondmnd-1536-192.show-p1984

#45

SMP PREEMPT Sat Dec 10 04:09:23 CET 2011 armv7l GNU/Linux

Click Me

Linux localhost 2.6.35.14-Bricked_XE-1.6.beta3-ondmnd-1536-192.show-p1984

#46

SMP PREEMPT Sat Dec 10 04:18:48 CET 2011 armv7l GNU/Linux

Click Me

Kgsl problems will be solved by #46. Cpu sleep code issues will be fixed by #45.

Please be aware that #46 will use more power, since I removed the gpu scaling and the gpu shutdown while display is off.

If you have no problems, stay on b3, these kernel versions are only for ppl that do get problems, so I can fix this annoying issue only some ppl seem to get ;)
[HTC Sensation] tinker2000:
Hi Show-p,

Whats the difference between the two test kernels? I have no issue with the original beta3..... Have had no lockups and the battery is fooking marvellous :)

cheers
[HTC Sensation] show-p1984:
Two different ways for a possible fix of the call screen bug on Android 2.3.4, Sense 3.0, which is hard to fix when I don't get it :/ (and neither am I getting a useful error report from the logs :()

If you have no problems, stay on b3, those kernel versions are only for ppl that do get problems. ;)
[HTC Sensation] blahbl4hblah:
Thanks for the quick answer
[HTC Sensation] tinker2000:
Sorry Show-p...

Is zram working on the beta 3 kernel. I noticed the zram init.d script, but my swap file shows zero use?

ta
[HTC Sensation] show-p1984:
I have increased the gpu memory as well as the vmalloc reserve. I don't know what faux did, and which values he has set, so that might be the difference.

I just saw that it is still in there... =/

well it will do nothing because it is not activated in the kernel (yet).

(Internal tests with ZRAM are running and so far I seem to got rid of the memory problems it was producing, expect it back soon!)
[HTC Sensation] wifesabitch:
I'm also still getting freeze ups with beta 3. Did it when I was using Go Weather.

Using the Pyramid3D ROM.
[HTC Sensation] tinker2000:
Just had a freeze in an embedded you tube video in market. You tube itself seems fine :(

last kmsg attached...dont know if its of use :)
[HTC Sensation] banesi:
Just tested #45, stil same wakeup issue as before, test ruu, 2.3.5, sense 3.5
[HTC Sensation] faux123:
@show-p1984

A one line mention would be appreciated for L2 bandwidth boost ;)
[HTC Sensation] GabrielSousa:
i think cpu1 can only work ondemand, interactive or userspace.

only cpu0 can be smartassv2
[HTC Sensation] show-p1984:
It's not in there ;)

I would have mentioned you if I would use the L2 boost, no worries. I am not a stealing kid. ;)

Had it in there for a test build, but reverted it for several reasons.
[HTC Sensation] faux123:
Much appreciated bro. I always welcome other kernel devs to collaborate :D Are you looking into the 3D corruption issues?
[HTC Sensation] show-p1984:
currently doing exactly that :D

I was already making high jumps because I could play ~30 seconds of Cordy with my latest test build, but on a second try it was exposed as random luck -.-"
[HTC Sensation] tinker2000:
Hi,

Great work, but how about making it work with the Daemon Controller. Its the easiest way to control the clocks and governer.

Cheers :)
[HTC Sensation] undercover:
I personally think daemon controller is overrated. Frequences jump up and down whenever they want, app FCs etc. SetCpu has always been more stable till acpu turned up. ATM, System Tuner is the best one.
[HTC Sensation] tinker2000:
it works well for me and I havent noticed any FC's. I agree that SetCPU was great until recently. I dont like all the extras in system tuner, is too much for me....dont care for all of that, hence my preference for Daemon controller.

Different opinions, but equally valid I think. Thanks anyway :)
[HTC Sensation] smint86:
+1

Too many options in system tuner for me as well. I like a clean way, just want to set min/max ondemand, nothing else.

Neither SetCPU nor CPU Master do work for me, i'm using InsertCoin 2.4.3 with Bricked 0.3. Maybe somebody can help? Maybe building a custom setcpu.txt would help, but I currently don't find a thread which helps me. I'm quite new to overclocking, I don't know the frequencys which I should put into the setcpu.txt. Which is the stock frequency of the sensation? 1188000? A link to a thread/post where it is explained would be great (multiplicators, frequencys, and so on).

Last but not least thanks for your kernel, for me it's currently great, my Sensation is running with it, just the battery drain is a little bit too big for me. But it's very stable and smooth :)
[HTC Sensation] baadnewz:
you do know that daemon controller is a binary, and config files in etc. you can install those yourself
[HTC Sensation] undercover:
Yeah, i'm talking about control apk. Didn't like it, wasn't stable for me.
[HTC Sensation] 3c:
Stock Sensation freq are 1.18GHz. But CPU is supposed to run at 1.5Ghz or so!

System Tuner offers a lot of features but is quite simple on the overclocking side, just what you're asking for: set governor and min/max frequencies.

Then on the CPU side, it is able to use OC/Deamon if you prefer still offering the same UI.

On system supporting init.d scripts, it can set the CPU settings at boot using those instead of when Android completes the boot procedure, faster to set and much sooner = faster boot.

System Tuuner is an integrated tool offering a panel of features many uses all the time: task manager, cpu tweak and backup/restore feature, sd tweaks, memory tweaks.

All that provided without much complexities like in setCPU with the complex profile system. Doing so saves on CPU consumption in many aspects:

- One app listening to system events, instead of many listening to the same events.

- Simple settings so handling those do not consume much (compared to handling profiles which requires much more processing).

Anyway, a matter of opinion and personnal preferences.
[HTC Sensation] smint86:
I made a setcpu.txt with

in it. I placed it at /sdcard/ and configured SetCPU as you can see in the attachments.

Will it work properly like that, or does someone have some recommendations?
[HTC Sensation] show-p1984:
It will work, but I doubt that it will be running optimal. I tweaked the ondemand to work with 1536Mhz. Therefore 1188Mhz will run less optimal with ondemand. But you can test it, maybe the loss of efficiency is nearly 0, I haven't tested it.
[HTC Sensation] miniterror:
sorry to begin about this again but is the voltage lvl of the 1536 that you tweaked the same as 1188 thats default?

if its the same voltage lvl then i will give it a shot:p

if its using more juice i think i will pass;p

no offense to youre work though as i really appriciat it:D
[HTC Sensation] show-p1984:
It actually runs with less voltage @ higher clocks ;)
[HTC Sensation] undercover:
Pm show-p1984
[HTC Sensation] miniterror:
Nice its undervolted at higher stock:)

Gonna try it
[HTC Sensation] tinker2000:
Ok, Please can you give me some advice on how to get it working with your 2.25SSE rom and this kernel then please and I'll sort it. Thanks
[HTC Sensation] show-p1984:
Updated to v0.4.