Originally Posted by Darnell_Chat_TN

I also use EnergyROM (March 15 release) and just tried to move up from Bricked v0.5 to v0.9. I also have the issue described by feanor91. No matter what option I choose for Sweep2Wake (with or without), GPU overclock (on low or off), I still have the issue of android.process.acore stopped unexpetedly continually popping up. (I kept I/O sceduler at its default.) So much, that I cannot do anything but reboot into recovery and restore my backup, to go back to v0.5. With v0.9 on I cannot get to the point of even opening an app.

Maybe you should provide a log to show, then he would be abled to do something about it. Just an idea... However, I don't think that it's kernel related, as both of you are using the same ROM and nobody else did report that problem. Did you tell the problem in the ROMs thread already?

Originally Posted by DarkPrinceByWWW

Screen on time? Seems like you weren't doing something with the phone except of turning screen on to read the time ^^

paying bejeweled 2

Originally Posted by smint86

Maybe you should provide a log to show, then he would be abled to do something about it. Just an idea... However, I don't think that it's kernel related, as both of you are using the same ROM and nobody else did report that problem. Did you tell the problem in the ROMs thread already?

Yea, I know about making a log. Just offering an initial bit of feedback here since someone already posted about it. I came here to mention it, since they did mention it in the EnergyROM thread too and yes we're also discussing it there. But not everyone using EnergyROM has this issue.

I do have the ICS patch from HTC applied, if that makes any difference.

Hello

I tried previous version 0.851 same problem

Testing v0.9 kernel with sweep to wake low gpu oc and stock cpu settings, all is going very good. Marvellous job.

Thank you very much.


Envoyé depuis mon HTC Sensation Z710e

Originally Posted by feanor91

Hello

I tried previous version 0.851 same problem

I have a question for you in the EnergyROM thread, please see.

Originally Posted by smint86

See my updated post. I don't think that stock Sensation has a built-in screen off profile. So you set the screen off frequency same as max freq.
That's right. Beat works, when it comes with the custom ROM. Show is talking of some improvements, like Anthrax made them in his kernel.

The stock kernel of the Sensation has no maxscroff profile.

Originally Posted by brice83

work well for me.
---------- Post added at 11:06 AM ---------- Previous post was at 10:59 AM ----------
hi, since v0.61, sometime i've noticed long delay (6 to 8 seconds) betwen the time when i kaunch a call and the time when the call screen appear.

I don't see how that should be the kernels fault, since no one else has this issue. Maybe your callrecorder app interfering? #userspaceissue

Originally Posted by cyphol

I'm sorry. Is this fact or myth. Because I played with both of them (AnthraX and Bricked) but the sound from Bricked is still not comparable to AnthraX. If Show-p has fixed it, then it's really a good news. Show-p has to clarify this matter. And one more thing, the only driver which I found that really as beautiful as Beats is coming from 'Dolby Mobile' in a custom rom from Webstar1, which is his Xperianse V1.0.

Originally Posted by smint86

This was discussed multiple times in this thread, which is the reason why I won't repeat all of it. In short: Anthrax doesn't fulfill GPL guidelines, which makes it impossible for show the include it. He actually is writing his own stuff, which will come with a later version. That doesn't affect beats which comes with your (custom) ROM (for stock music player), but is adressed to a system-wide beats mod.

Indeed. I will call it Soundz by Prof. Show and make milions. Nope, ofc #opensource.

Originally Posted by feanor91

Hello
Just to know, is it dangerous to push the Snapdragon S3 to 1.5Ghz, or is it conceived by default to achieve this speed? I know Sentation XL is at this default speed but what for a basic Sensation?
I found some infromations elsewhere, but it is not very clear for now.

Originally Posted by df1ech

All people say so but has this been actually verified ? As Qualcomm delivers the CPU chips in various speeds 1 - 1.5 GHz (i took that off the internal info and yes I do work for Qualcomm and no not for the chip.division)
Couldn't it be that better yields go to higher clocks and the ones that are of less production quality go out as lower clocked versions like Intel and AMD do ?

Take this as verification:
Qualcomm specified our soc to run in the 1188-1512Mhz range. HTC decided to clock it with 1188Mhz because they feared it would suck the battery of the stock sensation dry in minutes. That's why you see the "pimped" Sensation with a bigger battery and 1512Mhz.

Originally Posted by Astug

The first thing I noticed was the speed improvements over faux's kernel, which is odd. Clocks are set to 1512/384 & 594 when off. Yet, things open faster than with faux's kernel at 1728, f.ex. opening system settings/about phone/software information/more is quicker with Bricked at 1512, there's always a tiny delay with faux's kernel when you do this. Any reason as to why this is show-p? It's a very good thing ofcourse but I'm curious.
Sweep2wake is just awesome, I find it easier to use than actually using the hardware button.
So far, battery life seems good, I don't think it's being affected by the sweep2wake feature at all.

I have no idea why there is a difference, but then I haven't studied fauxs source to make an assumption about that.

Originally Posted by feanor91

Hello,
i've just flash last kernel version and I have this message after boot :
android.process.acore stopped unexpetedly...I clear cache and dalvik I boot 2 times.

Originally Posted by Darnell_Chat_TN

I also use EnergyROM (March 15 release) and just tried to move up from Bricked v0.5 to v0.9. I also have the issue described by feanor91. No matter what option I choose for Sweep2Wake (with or without), GPU overclock (on low or off), I still have the issue of android.process.acore stopped unexpetedly continually popping up. (I kept I/O sceduler at its default.) So much, that I cannot do anything but reboot into recovery and restore my backup, to go back to v0.5. With v0.9 on I cannot get to the point of even opening an app.

Originally Posted by Darnell_Chat_TN

Yea, I know about making a log. Just offering an initial bit of feedback here since someone already posted about it. I came here to mention it, since they did mention it in the EnergyROM thread too and yes we're also discussing it there. But not everyone using EnergyROM has this issue.
I do have the ICS patch from HTC applied, if that makes any difference.

Originally Posted by Darnell_Chat_TN

I have a question for you in the EnergyROM thread, please see.

Wild guess: If only people with energy rom installed have this issues, then it does seem to be a rom problem, doesn't it?

[...]
the simplest hypothesis proposed as an explanation of phenomena is more likely to be the true one than is any other available hypothesis
[...]
-- Swinburne, 1997
Occam's_razor

Originally Posted by show-p1984

Indeed. I will call it Soundz by Prof. Show and make milions. Nope, ofc #opensource.

I instantly like the name "Soundz by Prof. Show" better than beats, lol. It would please me to no end if someone was showing off beats on their device and I could whip out my Sensation with Soundz

Originally Posted by Astug

The first thing I noticed was the speed improvements over faux's kernel, which is odd. Clocks are set to 1512/384 & 594 when off. Yet, things open faster than with faux's kernel at 1728, f.ex. opening system settings/about phone/software information/more is quicker with Bricked at 1512, there's always a tiny delay with faux's kernel when you do this. Any reason as to why this is show-p? It's a very good thing ofcourse but I'm curious.

I know show-p allrdy answered it, but I experienced this too, because the most important thing for me is, how fast the ui/apps etc. reacts. Fastest kernel for me is rc mix one's, but bricked is fine also. Faux one's I experienced as the slowest one.

All of the Kernel chef's have their own priorities and this makes each one slightly different.We too are all different and have different preferences and its these differences that makes life great...Find one you like and stick with it

I have been using Bricked since he started and have rarely had any issues...A good solid kernel that's fast and doesn't devour my battery.

Happy days thanks to 0.9