yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] tk_xda:
You mean from send log app? Please PM me your email, as those logs are over 100k. Sorry about the double post. Tapatalk malfunctioned and made me think it didn't get up the first time.
[HTC Sensation] show-p1984:
There is a pretty neat invention called pastebin.com out there.
[HTC Sensation] i900frenchaddict:
So far everything is fine for me with beta7

I had no black screen when getting a call since I flashed beta7, but I just realized I flashed beta7 just after updating my ROM (to ARHD 3.6.11, Sense 3.0) and I forgot to flash CRT animation as usual...!

What I'm sure is that I had the black screen when getting call even without CRT animation on beta6, not using auto-brightness seemd to be a solution.

No, I have auto-brightness, no CRT animation, Beta7....and no black screen on incoming call :confused:
[HTC Sensation] q9650:
Make the backlight darker

Is it possible to make the backlight of the screen darker? It is still too bright even on lowest level when i turn auto brightness off ;) Just by the way :p
[HTC Sensation] show-p1984:
Kernel setting is @ 6 of 255 iirc, no Rom uses levels that low afaik.

So blame your rom ;)

btw:

If only 2 ppl got the callscreen issue, then I will release b7 as 1.6 final.
[HTC Sensation] q9650:
Awesome :D
[HTC Sensation] zx34:
We are ready for the 1.6 final.... :p

●● █ ELEGANCIA Rom Series™ █ ●● HTC ● Sensation Z710e ●
[HTC Sensation] tibere86:
Let her rip!
[HTC Sensation] show-p1984:
EDIT:

False alarm ;)
[HTC Sensation] StuartTheFish:
I'd hardly say it's finished if it still doesn't work right, but it's your call since you're the guy making it.

I get frequent random reboots even though it's not undervolted or stupidly overclocked, and the screen not waking on incoming calls. My phone works perfectly on the stock kernel, and in fact on most of your previous kernels too, and then these problems arose from beta6. It's not an issue with anything else on my phone since the other kernels pretty much worked fine, and absolutely nothing has changed on my phone other than the kernel, and then the problems started.

I've still not got round to making logs yet, since I'm now back on beta6 so that my phone is still useable. When I get a day when I'm not depending on my phone as much, I'll flash beta7 again and try making logs for you.

Can you just modify the final release of 1.5 so that the camera doesn't crash since you managed to fix the issue? As then I'd have a kernel that actually worked properly?
[HTC Sensation] Tromador:
Sorry to report that I've just had the same wake on call black screen bug with beta 7

Teleported in from my HTC Sensation Z710e
[HTC Sensation] masondoctorjt:
Try faux's latest kernel for a day... I bet you'll get random reboots as well. If so, I'd say it's a ROM issue.
[HTC Sensation] StuartTheFish:
I've already used faux previously. Faux caused my phone to run too hot hence why I no longer use it, it never caused rebooting though, nor the black screen issue.

Like I repeatedly keep on saying, it is NOT a ROM issue, I've used several bricked kernels as well as stock on THIS SAME ROM and only bricked 1.6 beta6 and beta7 caused the black screen on calls issue, and only beta7 caused the reboots too.
[HTC Sensation] i900frenchaddict:
as it was already pointed out (arf, I'm lazy to look at previous pages, sorry man, you who pointed it out first), oncall screen issue may be related to CRT animation and/or auto brightness.

Guys who have this bug, maybe you should also tell if you use one of the two options above, and also try to remove CRT or not use auto brightness to see if the bug remains

just my 2 cents :p

(PS: in my case, beta6 without auto brightness and with CRT animation was OK, and Beta7 with auto brightness but without CRT animation seems to be OK....:confused: )
[HTC Sensation] q9650:
Please guys, let us have MORE INFORMATION, about addons, etc. Are you using UV Script? Are you overclocking? What Apps do you have installed? KMSG log, etc. ;)
[HTC Sensation] guyd:
I for one can attest to that. Three different ROM's all had the Black Screen on Call Issue for me (InsertCoin v2.2.5 SSE, ARHD v3.6.11, ARHD v4.1.9) on the recent Bricked Kernels. If I remove the CRT Animation in these ROM's, no more problem. If I flash them back, problem comes back! I prefer to leave Auto Brightness on, but turning it off also worked for me.

With all the various ROM's in use with people that have had this issue, it's very hard to pinpoint what's in common! All I can say is that either of the above two methods work around the issue for me. I miss the CRT Animation, but oh well...
[HTC Sensation] show-p1984:
So it's an improvement, isn't it? ;)
[HTC Sensation] lampshade90:
Got a black screen on incoming call latest beta (7), after deep sleep a few days ago, after disable autobrightness its gone... happiest bricked user :D

Coredroid without any mods overclocking undervolting or whatever
[HTC Sensation] show-p1984:
As soon as I have reached a logical pause point on my 3.0 kernel, I will release another beta with another PM fix, should not have to do anything with that, but usually exactly those things do. :rolleyes:
[HTC Sensation] StuartTheFish:
The older kernels worked fine with this ROM like I keep on saying, that includes the CRT animations since the ROM hasn't changed.
[HTC Sensation] i900frenchaddict:
Yes it is :) I prefer having auto-brightness, CRT animation is nice but I can easily live without it.

I have a question, maybe out of topic (I don't really know if it's ROM or Kernel related): Playing GTA3, with full effects enabled, I realized forcing CPU1 online gives far smoother gaming.

Very strange, since my O/C tool reports both CPU online when GTA3 is running (both at 1.72 ghz, full effects on this game need it). But really, it's not a placebo, it's completly obvious, forcing CPU1 makes the game way smoother...and faster too.

I used to force CPU1 all the time until you released v0.91 and following, then I forgot about this trick since my UI was 100% smooth with your kernels.

So how can this game run better with CPU1 forced online, while it takes so many ressources that CPU1 is already online without forcing it?
[HTC Sensation] guyd:
There is nothing wrong with using an older Kernel. I'm using v1.5r1 beta 1 #528 which runs very good on ARHD v3.6.x (without CRT animation). In fact, I find that the battery life is better on the v1.4 and v1.5 kernels! I'm sticking with #528 because it was the first build to have the power button fix, but I have ZRAM disabled for better stability.
[HTC Sensation] mat9v:
I got interested in the subject and found some info about problems with forcing CPU1 online - about 5 months ago Qualcomm made an addition for it's post boot file to start mpdecision and thermal deamon. I guess they had a reason for it - it is not a problem with Sensation only but all phones based on MSM8660 (and 8960 got the same treatment about a month later). I removed my script forcing CPU1 online and while benchmark scores are lower the system on the whole feels smoother. It is counter intuitive but maybe the system get "stupid" deciding on which cpu to run a thread (I know I'm just guessing and not smartly but I too have found no explanation) while maybe the game is created with MP in mind.

Alternatively you could try disabling mpdecision daemon (/system/bin/mpdecision), forcing cpu1 online and testing the system responsiveness.

Hmmm, I may try that myself :)
[HTC Sensation] StuartTheFish:
The only problem I had with older kernels is the camera crash bug, hence why I'm trying the 1.6 beta's in the first place. I just want everything to work and still be able to overclock to 1.5ghz. Disabling CRT animations isn't a fix, it's bypassing an issue rather than curing it.
[HTC Sensation] i900frenchaddict:
thanks mat9v for your explanation.

So yes, it may be related to the way threads are shared into CPUs, or maybe forcing CPU1 online removes kind of a latency (mpdecision ?)

It's also the same with N64 or PS1 emulators, when you play games that don't run full speed in terms of Frames Per Seconds: you get better results if CPU1 is forced online than when you let the system decide. But if you let the system decide, CPU1 is reported as online and max frequency all the time...So there shouldn't be any difference, but there's one, not visible in the UI, but visible when running the rare games that are not full speed at 1.7ghz.

I stop here, it's out of topic and was discussed already, sorry, just I had forgotten about it, since using Bricked 0.91 and following Bricked kernels I had stopped forcing CPU1 online, just GTA3 reminded me this trick ;)
[HTC Sensation] guyd:
Not, it's not a fix, but remember that v1.6 is a beta kernel. That's why most of us are here testing it, and posting the issues we have found. I think you have made your dissatisfaction loud and clear.

Have you though about going back to the Stock HTC Kernel? There is a 1.5 GHz CPU 300 GPU version and a 320 GPU version out there by SebastianFM. I've ran it, and it works rather nicely! Here is a link if you feel like trying it.

[KERNEL] Overclocked Sensation and Sensation XE HTC stock kernel for HTC GB ROMs
[HTC Sensation] StuartTheFish:
Ooh, thanks for that! I'll be giving them a go!

I know these are just beta kernels we're currently talking about, but there was talk of making beta7 the final release, which I didn't agree with since they're still not right yet.
[HTC Sensation] masondoctorjt:
#528 had zram? I never realized that.
[HTC Sensation] akpe:
For the past two-three days I had experienced random freezes while using the camera on v1.5 (mostly when exiting the camera, one time when opening it) and once while exiting youtube. They just started happening out of the blue.

I reflashed ARHD 3.6.11 and (after a day of using the cam A LOT without issue) I got another freeze. So I decided to revert back to 3.6.9, until I read about a camera bug in the wiki on pre-1.6 beta versions. Was this the said bug?!

There could also be a relation with autobrightness there (back on v1.5), since AFAIK camera turns brightness all the way app when opening.

It's actually strange, I was on Bricked v1.5 for a while now and the issue just presented itself in the past few days.

Anyway, just flashed b7, hope that solves it :D
[HTC Sensation] guyd:
Starting from build #490 and all the way through #539 had ZRAM

Show removed it for the v1.6 Beta
[HTC Sensation] TriTopaz:
Hi,

I got a strange issue two days ago. The Sensa was fully loaded in the afternoon. I did nothing with it and just lay it next to my bed to hear the alarm 7 hours later. But until then, the battery was completely empty.

Its the place, where I allways lay down the phone, so it shouldnt be a matter with radio reception (I suppose).

The next day it runs for 1Day 7 Hours and 45 Minutes, until 3% were reached.

I don´t have any Task, Battery or CPU tools running. IC3.4.5, Kernel 1.6beta6.

Now, I´m a little bit afraid of coming too late to work :confused:
[HTC Sensation] Darnell_Chat_TN:
I use #528 as-is and it's always been the best one for me. To me it's even more stable than a stock kernel.
[HTC Sensation] adritati:
upgrade it to v1.6b7

Hi guys, I have InsertCoin 3.4.5 and I flashed few weeks ago Bricked-Kernel v1.4, it was supposed to be stable and it was, no FC at all, smoth... till with the past time it started to freeze some seconds sometimes, the phone was completely blocked when I closed the camera, etc so I decided to upgrade it to 1.6 beta7 this morning.

For now all I can say is camera feels like working fine, even though when I close it the panel is showed empty a couple seconds and when I push the power button to unlock it I have black screen for one or two seconds and then it shows the unlock screen.

I have autobrightness and CRT animations. Some thoughts?
[HTC Sensation] StuartTheFish:
Is there a zip available to remove the camfix and revert back to normal? Without resorting to flashing the entire ROM again? Does the camfix overwrite any files, or does it just add more that override the original files?
[HTC Sensation] guyd:
I think you may need to reflash your ROM to get it back to stock.
[HTC Sensation] StuartTheFish:
Bugger, CBA to wipe, flash and install everything again...

Could I not just see which files are in the camfix.zip archive file, then open up the zip the ROM is in and pick out the files that were replaced?
[HTC Sensation] StuartTheFish:
I just tried what I mentioned, looking through the camfix zip, noting down it's contents, and then pulling the originals from my ROM zip file. I then zipped them up, booted into recovery and installed it successfully. Now all modes of my camera work, including burst mode with the amaze mod. This is on SebastianFM's hex edited overclocked stock kernel anyway, with EVERYTHING 100% working now. So I guess I'm staying on that kernel until bricked improves and ends up stable and reliable.
[HTC Sensation] show-p1984:
For most of us it is exactly that.

Btw Bricked will not support ZSL until the drivers are released by HTC, which can take some time. SebastianFM hacked the HTC Stock kernel to oc it (hexedit), there are no other mods present.

You could have just flashed your rom.zip without wiping, since those files change never (except if you apply some mods, then you would need to reapply them again) you are good to go in 30 seconds.

I can't provide a flash back to pre camfix zip since most roms use different versions of the files, and hacked them and stuff. There is no one single overall solution.

pyramid_XE betas have suffered a bit from my unbroken work effort to port the 3.0.8 caf-kernel ;)

They will revive once I have less on my plate (car is in the shop.. yet again, I am sick (cold), my dog is sick too and it's my fathers birthday soon...). I wish I had 4 hands and at least 3 eyes, then I could actually do everything I want to... I feel so limited in this body! GOD, Y U NO MADE ME WITH 4 ARMS AND 3 EYES? :p
[HTC Sensation] tibere86:
Now this excites me! I hope you can eventually get it to work.
[HTC Sensation] StuartTheFish:
Yeah, I'm aware it's just an edited stock kernel, but the CPU and GPU overclock was all I personally wanted from a kernel change anyway, so it suits my needs. I can't say I've noticed anything running slower than on your kernels though, and so far everything I've tried finally works, so I'm happy.

And as for removing the camfix, I'd assumed the files might be tweaked for each specific ROM, hence me picking out the files from my ROM's zip and installing them. Didn't realise I could have just flashed the ROM again though, oh well.

Thanks for all your hard work so far, I'll keep trying your future kernels from time to time to get undervolting back, etc.
[HTC Sensation] sszz:
How to check GPU frequency

Dear show,

Is there a way to tell the actual highest GPU freq for a kernel, like for the CPU with SetCPU or System Tuner?

I am still using 1.5 beta 1 for stability reasons and wanted to check GPU clock setting however I did not find any easy way comparable to checking CPU frequencies.

Is there a file somewhere that controls speed? Or a terminal command?

Thank you in advance.
[HTC Sensation] mat9v:
Look for file scaling_available_frequencies in /sys/devices/system/cpu/cpu0/cpufreq

View file, it contains all frequencies that are available for your kernel.
[HTC Sensation] sszz:
Thanks, but this is for CPU, I am aware of that. I want to check the same for the GPU (graphics processor). Is there a similar file for that?
[HTC Sensation] mat9v:
AFAIK those values are not exposed like the cpu ones.
[HTC Sensation] show-p1984:
correct.

maximum on Bricked is 300 though.

However you can check the current gpu speed through (a few seconds delayed though)

cat /sys/class/msm_kgsl/kgsl-XdY/gpuclk

where X may stand for 2 or 3 (2d or 3d core) while Y can stand for 1 or 2 if X=2 and only 1 if X=3.

This lets you check both 2D cores and the 3D core.
[HTC Sensation] i900frenchaddict:
I know I'm really off-topic here, but show-p, with your knowledge, maybe you could explain (sorry again for being off topic, also I opened a theread in the Q&A, so you can blame me here):

Fpse was updated with an openGL plugin. Graphics are huge, real PSX now, no more pixels even on our QHD screens.

But using the openGL mode, games are way slower on the Sensation and the Evo3D

Way slower than on devices with Adreno 205 :eek: (and way slower than Mali400 too)

Example: tekken 3 is 20fps for me, and 80 fps on an Xperia Play! The average performance difference ingame is more than 50% in favour of single cores with Adreno 205 compared to our dual cores with Adreno 220

Even with older versions of your Kernel, including the GPU 320mhz overclock, it makes no difference at all.

Any idea of what was so badly coded by HTC concerning Adreno 220 drivers??
[HTC Sensation] sszz:
Wow, thank you, this is exactly what I was looking for! Thanks again.
[HTC Sensation] jkolner:
Last night i installed Bricked latest Kernel and Camfix. For now im very impressd with stability, speed and battery life. Im on Energy ROM and Sensation XE.

It was this on:

"Bricked_XE-1.6.beta7-ondmnd-1536-192.show-p1984" and "camfix-for-1.4".
[HTC Sensation] show-p1984:
I don't have enough knowledge about fpse, but it may be that it primarily uses the 2D core, if it is the case, it will fail on our sensation. The adreno220 has a very bad 2D performance. It may also be the case that it is only using one of our 2 2D cores. No idea tbh. Maybe the acceleration it not working at all on our sensation? ;)

I got no time at the moment to dive into this, sorry ^^

####################

For anyone with callscreen problems, here comes b8 with some bugfixes for power and sleep management, caf fixes, overall improvements and fauxs capacitive led auto dimming feature.

It was meant as internal only, and therefore has no downloadlink on gcode ;), but I figured that more ppl testing for the callscreen bug would accelerate the process.

Click Me @ Dropbox

SHA1: 5d97f0c2ac452dbbb5d9f135877808ad30bb6d68
[HTC Sensation] zx34:
Thanks for beta 8, testing in progress.... :p

●● █ ELEGANCIA Rom Series™ █ ●● Bricked-Kernel ● 4EXT Recovery ● HTC Sensation Z710e ●●
[HTC Sensation] aNYthing24:
Does it really? I thought it had a dedicated 2D graphic engine to improve performance. I know Quadrant isn't a good benchmark, but...

---------- Post added at 09:01 PM ---------- Previous post was at 08:49 PM ----------

To backup my point, I ran Fps2D (a 2D benchmark as you can tell by the name), and I get 60 fps (probably limited by vsync).

Sorry to pile on you show-p, just trying to justify what I'm saying.
[HTC Sensation] masondoctorjt:
I don'tseem to have any bugs, but I'll use b8 and see what happens.
[HTC Sensation] phoenx06:
Could anyone give me a list of current roms this will work with? Or does it only work with InsertCoin?
[HTC Sensation] show-p1984:
it 100% with every 2.3.4-HTC based rom. 2.3.5 based too, the latest sensation xe leaks and releases, as well as 2.3.3. The rest needs to be tested. AOSP Roms won't work, but you can test it ofc. ;)
[HTC Sensation] jlevy73:
Still having 3D gaming issues. Heavygunner3d dies on me every 30 seconds. Granted this game for some reason gives every device issues (SGS2 can't even handle it) but V0.7 handled it no prob
[HTC Sensation] show-p1984:
Maybe due to the workaround. Just stay put, I will fix remaining errors in the coming days, as well as cleaning my currently verrrrry dirty hack. ;)
[HTC Sensation] phoenx06:
Sweet! SO I should be able to flash it over the new Virtuous build, and use the Daemon without any further changes (of course I'll wipe cache, dalvik and such)?
[HTC Sensation] show-p1984:
Deactivate the daemon, make a nandroid, wipe /cache (dalvik cache only needs to be wiped when you change apks, since it is the apk cache), and try it ;) If it ain't work provide logs @ issuetracker. I will look into that.
[HTC Sensation] Dano79:
Good work Im using Insert coin with your kernal My phone has never ran cooler thanks
[HTC Sensation] jlevy73:
No worries, just reporting my findings. Thanks
[HTC Sensation] RayHeath:
Me too, just reporting.... I´ve flashed the 0,8, and on the CoreDroid works fine... no lags, reboots, or freezes. :)

Thanks guys!
[HTC Sensation] GabrielSousa:
i have oc daemon, works great with your kernel ;)
[HTC Sensation] jlevy73:
Regarding XDA and releasing Source Code there isn't really a hard and fast rule here. According to my friend, who may or may not be a Mod here :), says typically they will give developers 5 days to post code. To that end, the OP is well within his right to not release the code immediately.

---------- Post added at 01:27 AM ---------- Previous post was at 01:25 AM ----------

I addressed this in the post above it.

In terms of GPL as it applies to companies like HTC, Sammy, etc., they have 90 days to release source from the time they issue the OTA.
[HTC Sensation] show-p1984:
Nice and shiny, but as I said in the beginning 7 days. ;)

No compromise, no partially release before. 7 days it is. Live with it.

I need the time to clear this very dirty fix. It has some flaws too. (scrolling in the htc news widget will cause a ~30sec freeze and then restore itself)

And I am not the guy that releases unfinished stuff, I learned of this flaws after the release.

I earnestly think that 7 days are not that much. I could have not released the kernel and all of you guys would not even think about the possibility of a 3d source code ;) But that would have been unfair to the majority of users that want to use heavy 3d apps.

So be happy it worked out. You will get your share of the cake soon enough ;)
[HTC Sensation] alhuang69:
In supporting your great work, here is some more beer, cheers

Confirmation number: 5CF08540SR085952N
[HTC Sensation] show-p1984:
Thanks! Very much appreciated!
[HTC Sensation] pakraider:
It looks like HTC location service isn't working with 0.8.. (can't find location on clock or weather widgets). Might just be a coincidence, but it started right after flashing.
[HTC Sensation] show-p1984:
Must be a Coincidence. Works flawless. Wipe cache.
[HTC Sensation] pakraider:
Wiping caches did the trick. Super work! Btw, which call recording App do you recommend?
[HTC Sensation] NYCguy2020:
Anybody has a link to V0.7? thanks a bunch.
[HTC Sensation] NYCguy2020:
Anyone??!

10 Char.
[HTC Sensation] agentaaron:
Seriously???

Its in the first post!

Click Here
[HTC Sensation] show-p1984:
So I get that there are no problems anymore? :P

Either way there will be another small beta before 1.6 will be final ;)
[HTC Sensation] Tromador:
I applaud your enthusiasm Mr ShowP, but could we get a bit more testing time other than a quick 5.5 hours when most of Europe is sleeping anyway ;) :p
[HTC Sensation] show-p1984:
I just wanted to get it through before XDA goes black ;)
[HTC Sensation] masondoctorjt:
used it overnight. No problems here, love the led buttons turn off when watching video now. I notice the 2d cores run at only 228mhz vs the 266 that your other kernels ran at. My antutu scores were almost 6000, and now only 5388. But the phone runs smooth so I don't care, just mentioning it cause I know some people only care about benchmarks.
[HTC Sensation] tibere86:
Thanks for the new beta Show. Flashing now. Will report back.

Edit: No issues so far. Everything running smooth as butter. Zero hiccups.

Edit 2: I'm seeing a bit battery life than beta 7 after ten or so hours of use/kernel stabilization. Many thanks again show-p1984!
[HTC Sensation] Tromador:
Seems ok - phone appears to be waking up properly, but then I've said that before and had random blackscreens after using the kernel for a few days.

Hopefully it's sorted.
[HTC Sensation] masondoctorjt:
Still no issues with beta 8 for me. I didn't notice battery issues, but I don't pay too much attention to the battery.
[HTC Sensation] kazi639:
Used beta 7 over beta 5r1 #528...No issues at all...No black screen/ No problems..but my Antutu benchmark went down to around 5300..(that doesn't bother me;)), but handset was getting hot even while playing simple games like angry birds, same with asphault..felt like phone was getting too much worked up :( So back to beta5 r1...benchmark got to 5900 :eek:.. the phone feels super solid and super cold:p