yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] MIGhunter:
Not sure if it matters, When I change the settings through ES Explorer, it saves the file and retains the changes. I deleted the bak file. However, if I go into the performance menu, it still says ondemand. Even if I change it from that menu and reboot. The file still shows badass and badass=3 when I reopen it in the explorer.
[HTC Sensation] rdelar01:
Did you verify the permissions on the edited 99kernel file? Long Press the 99kernel in ES Explorer, scroll down, select properties, and make sure the permissions are rwx r-x r-x.
[HTC Sensation] 69gm:
If you don't want people to use any kernel tuners apps, perhaps you should state that in the OP to avoid future headaches. I know there will still be those that don't read but for those of us who do...just a suggestion. :)

You're stuff is awesome. Just keep on keepin' on! Looking forward to future awesomeness in your ROM.

Thanks!
[HTC Sensation] MIGhunter:
Ya apparently when I rebooted after changing the permissions, I didn't

Click the restore on boot checkboxes.
[HTC Sensation] Yogimax:
+1 please... That feature seems to have disappeared!

---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------

Have you tried the noise suppression option under the phone settings?
[HTC Sensation] dkephart:
Check out init.qcom.post-boot.sh, like Albinoman suggested, see if something is messing with your settings.

Did I say that ownership of 99kernel has to be root:shell?

Oh, yeah, I did say that

And I also mentioned NOT to use the Restore on Boot checkbox in Settings->Performance->Processor
[HTC Sensation] Element515:
where is that noise suppression option? I can't find it and am having similar issues
[HTC Sensation] Pikabat:
Cant get GetRIL working it says database is empty , anyone knows why?
[HTC Sensation] StuartTheFish:
READ, ffs.
[HTC Sensation] MIGhunter:
I don't have any cpu tuners or anything installed that would change it.

How can I tell if it's ownership is root:shell without using ABD?

I did get this in my inbox:
[HTC Sensation] 69gm:
Hi MIGHunter,

Open File Manager, navigate to 99kernel, long press it, choose Properties, choose PERMISSIONS, it should say everything you need.

Hope this helps! :)
[HTC Sensation] Skipjacks:
Many people know. They have even said why in this very thread.
[HTC Sensation] tdimarzio:
FYI - looks like ION is getting closer. http://xdaforums.com/showthread.php?p=40368248
[HTC Sensation] MIGhunter:
Yea, file manager has another menu that I don't see in ES Explorer. In that menu the permissions have two categories: Owner and Group. Do I set just Ownership as Shell? I don't see a option for root:shell. Does Root:Shell mean set Owner as Root and Group as Shell? Thanks.
[HTC Sensation] 69gm:
Yes, that is correct. ;)
[HTC Sensation] MIGhunter:
Hmm, I have it set to rwx r-x r-x and then it's set to owner as root and group as shell. When I uncheck the set on boot button and reboot, it switches back to ondemand. If I leave it checked and reboot, it goes to badass like I have it set.
[HTC Sensation] dkephart:
So that is a good result! Even though I don't have to enable set on boot....Duly noted.

Only thing I could think of is if you accidentally inserted a space before the word badass in 99kernel...or if a tuner app messed with you and left a qcom post-bootup.sh file...
[HTC Sensation] gururoop:
@albinoman887: can u pm me the way to introduce the hack so that u would not be required to bang ur head over it? coz there are hardly any people who have come across s2w problem in ur recent build besides me, so it would save u trouble of looking into it if i am doing something wrong with my settings that's actually causing the problem. i'm no expert programmer but i can give it a shot if its simple.
[HTC Sensation] hausofpine:
How to turn this Seep2ake Kernel?
[HTC Sensation] elgrego4:
Well I fkashed again and it all seemed well but when I play music without headphones plugged in there is no sound from the loudspeaker
[HTC Sensation] r#ch:
Had another random reboot overnight. (was not charging)
[HTC Sensation] meirhasin:
Hi, does anyone have answer for this problem?

Thanks!
[HTC Sensation] tomer1981:
That happened to me several times before, but it hasn't happened for a while now. What build are you on?
[HTC Sensation] meirhasin:
Hi

Now im with Revolution HD v7.2 because i can't work with CM10.1 AOSP 4.2.2 Jellybean due to the problem that i mentioned in this post so i don't have a build to tell you, the last time that i tried was before 2 weeks, since then, im checking everyday the ROM thread for update regarding to this issue and there is no update so i decided to ask this question, i have no problem to install it again with the latest build and check it again. but you think the problem was gone?
[HTC Sensation] Yogimax:
While you are in the phone dialer, hit settings and "Enable sound suppression" is there as an option towards the bottom.
[HTC Sensation] deepsaha007:
in this update screen going black and not turning sometimes after the mobile is idle and screen off for several minutes.. also sometimes when I get call,touch gets stuck..cant pickup call , cant disconnect or do anything but pressing power button pop's up the switch off menu.

also, sometimes the mobile,touch hanged after several minutes of screen off , none of the touch menu / options work... also there is a problem with mic.. the other person who on the call gets very low and a faint sound sometimes..
[HTC Sensation] jkolner:
I have seen same problem a couple of times.
[HTC Sensation] black_bottom:
thats a very good idea to do so! this thread is flooded with questions around this.

as a "template":

to adjust minfreq, maxfreq, governor, s2w, fastcharge, .. ONLY edit 99kernel to make any changes

you may use kernel tuner, android tuner ... but ONLY to check settings, NEVER use those tools to change them. NEVER enable the "on boot" checkbox.

also use settings->performance ONLY to check setting, NEVER use it to change them, also NEVER enable "on boot" checkbox.

regarding 99kernel:

use the delivered filemanager and before editing longpress 99kernel->properties and keep in mind the "look" of the permission checkmarks. after editing+changing check if the persmissions have changed, if yes correct them.

also check in this dialog the ownership of the 99kernel: owner=root, group=shell - correct this, if it is other.

maybe albinoman likes the idea to post this in a strong visible maner in the OP - I would appreciate this :)
[HTC Sensation] mandeep294:
disable s2w.
[HTC Sensation] a.key:
Dont know how u guys but April-13 just made me positively impressed:

I know that I've not used the phone much throughout the period but I don't remember seeing over 2days on that battery screen ever.

I've got anker battery if anyone wonders.
[HTC Sensation] sina87:
Holy crap on a cracker! :o 2 days! Hacks!!

I'm on the same build but mine lasts 8 - 9 hours max. I'm on stock battery though. But still.! 2 freaking days. I used to get such battery life on my Nokia 1100. :P
[HTC Sensation] ziaulh.ch:
You got no sync? Screen hardly used! You got v. good stand by perofrmance. I dont know if you got any push based app..

Overall good performance!
[HTC Sensation] simba4:
Nice!
[HTC Sensation] tomer1981:
Just try and see for yourself. Make a nand first.
[HTC Sensation] meirhasin:
will do. thank you.
[HTC Sensation] henry_hoo:
Thanks for your rom!!!
[HTC Sensation] duck0:
I'm on the April 13 build and was taking a look at the CPU action using the very nifty floating PerfMon, it seems that on my phone at least, the first core seems to operate just fine, obeying the android Settings > Performance, but the second core does not, and keeps going up to 1.5GHz instead of the set frequency of 1188MHz. This apparently happens both with badass and ondemand governors set in Settings.

My init scripts are all unchanged, so something clearly is amiss.

<insert sound of looking around>

Just booted (without set-on-boot) and set 1188MHz in Settings; sure enough...

shell@android:/sys/devices/system/cpu # echo 1 > cpu1/online && cat cpu1/cpufreq/scaling_max_freq
1566000
shell@android:/sys/devices/system/cpu # cat cpu0/cpufreq/scaling_max_freq
1188000

This however seems to work just fine:

shell@android:/sys/devices/system/cpu # echo 1 > cpu1/online && echo 1188000 > cpu1/cpufreq/scaling_max_freq && cat cpu1/cpufreq/scaling_max_freq
1188000

So if there's any point to this post, I guess this problem is somewhere in the CM performance settings program?
[HTC Sensation] K00li79:
If i cant use system tuner then how do i change oom settings and read ahead cache size? :)
[HTC Sensation] Sleepy!:
Y u no edit 99kernel script like Albino say? :rolleyes::sly:

(Insert meme image here)

Sent from my HTC Sensation on CM10.1

---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------

Hi. He is clearly talking about No Frills CPU control.

And that too with relation to CPU clocks. :rolleyes:

Sent from my HTC Sensation on CM10.1
[HTC Sensation] gauravmajithia:
Hi All,

First of all a big hand for Albinoman and thanks for your efforts.

I saw a lot of issues posted by users here. Fortunayly i do not face any of them except robotic disturbance while on call.

The problem does not exists on 31-march. I reverted back and tested the same. But on april-13 i face this wierd and uncommon problem.

Is there any fix for this?
[HTC Sensation] redback_rsa:
Someone posted a bit of text you can copy to your 99kernel file. It should change the RAC size. Just search for it.

Or use Sultan kernel, A1-7 adds the tweaks that Albinoman adds to the stock kernel. You can change all those values in the aroma installer.
[HTC Sensation] dkephart:
Check your pm. And you should try the latest version.

---------- Post added at 08:28 AM ---------- Previous post was at 08:21 AM ----------

You could try disabling dial pad touch tones. Or just redial if a call has a robotic-sounding ring when you first dial.
[HTC Sensation] duck0:
Because my interest is in making it work right, not fiddling with the system defaults. Clearly I could just as easily add a line to my /data/local/userinit.sh that modifies the cpu parameters.

I'm installing an ubuntu VM now to pull the repo and see if I can pinpoint the problem more, provided I get some spare time.
[HTC Sensation] dkephart:
I see that you ran your commands from the sys directory. Do you get the same happy results if you use the full path (/sys/devices/system/cpu/cpu1/ ... etc.?

I ask because something is funky about the directory structure when I try to look at the cpu1 files using File Manager.

Also, running 99kernel as root from the CLI gives errors about non-existent cpu1 files or directories.
[HTC Sensation] duck0:
This is because cpu1 (the second core) gets disabled when not in use, and the cpu tree disappears when the core is offline. That's why I do echo 1 > cpu1/online before trying to read the variables. The /sys tree isn't real after all, it's a direct kernel interface being presented as a filesystem.

I'm pretty sure a full or relative path makes no difference, it's just that the files aren't there all the time.
[HTC Sensation] MIGhunter:
My son rarely uses his phone. He got 3 days off an USB charge with sick battery.
[HTC Sensation] gauravmajithia:
Dial pad touch tones are already disabled. I also tried Disabling noise suspension... Actually the sound is not 100% robotic. Its has a disturbance as it comes when we forcefully try to amplify the sound. But when i restored back to march -31 the sound was normal. :what:
[HTC Sensation] dkephart:
Thanks. Someone probably tried to tell me this before, but I forgot.

But, unless you have enabled CM's Processor features at boot time, how could that be the culprit?

I notice in my qcom bootup script, that mpdecision & thermald are commented out.... Does this have an effect like you describe?

I notice there is no echo 1 > ...cpu1/online in 99kernel... do you think this is needed?
[HTC Sensation] duck0:
I'll have to confess I'm not very well versed with linux or android in specific, I keep mainly to unices like IRIX for my desktop SGI and NetBSD for the servers.

The thing about 99kernel is that it's run fairly early in the boot process, so the phone is busy starting up the android environment; ergo both cores are pretty much guaranteed to be online... Linux in a nutshell, it works, but only because some circumstances happened to coincide ;)

There really ougt to be a way to lock it online for the duration of the script (and there probably is, I just don't know about it). Enabling the core by echoing 1 to cpuN/online is a bad move, it introduces a race condition between how fast you can execute your command to cpuN/cpufreq/whatever and how fast the kernel is to disable the cpu because it's not used...

The mpdecision and thermald daemons can--as far as I know--be built-in to the kernel, so that's probably why they're disabled. If they weren't working your phone could overheat and ISTR the second core would never come online if mpdecision isn't running, but don't quote me on that :)

Oh yeah, I forgot. About the CM Performance settings, they're not the culprit in any other sense than that when you use it, only the max frequency of the first core gets set.
[HTC Sensation] a.key:
I don't use gmail, I use kaiten email and IMAP with 3 accounts

I've got whatsapp and talk

my taptalk and google+ have notification disabled

I don't have latitude enabled

I always have WiFi enabled and BT is 99.9% time off.

That's about it.

I've got 2% batt left now so will disappear shortly ;)
[HTC Sensation] gauravmajithia:
I just reached home from office and realised that i am even facing low network problem on this build. I am switch back and forth between mar-31 and april-13 build to test these things. network is good with mar-31. Wierd!!
[HTC Sensation] dkephart:
This is a great explanation. Thanks very much. And so... all's good, right? (Don't enable Set At Boot)
[HTC Sensation] duck0:
Err, yes.. I guess... :-]
[HTC Sensation] consolation:
Personally, I find it easier to delete the 99 script and use kernel tuner. I seem to get more consistent results that way.
[HTC Sensation] BuXuRa:
i have sweep2wake disabled i still have black screens and cant wake my phone
[HTC Sensation] dkephart:
/w

Did you enable power button hangup (in Settings->Accessibility) to hang up if you need to and Volume Rocker wake in Settings -> Display?

I don't think many people have this problem. Also (just checking) you did reboot after disabling S2W, right?
[HTC Sensation] BuXuRa:
s2w is disabled by default i havent changed anything

and yes i have volume rocker ticked
[HTC Sensation] biomech91:
I mentioned a while back that CPU1 isn't getting the settings applied to it because it is offline. Will doing it this way ensure it works? I don't use settings to set them though, just the script. But it doesn't stick for me, which I'm assuming means it doesn't stick for CPU1 because it's offline.
[HTC Sensation] anderl78:
I have seen this working in older builds too (guess build from around 20.Feb ?)

Tried to disable

ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420

In build.prop, but its still not working...

Since playing with the network settings I got roaming connections...

Is it possible to set the provider for example in build.prop?

Something different: for me it looks like since you changed

debug.composition.type=dyn
to
debug.composition.type=gpu

the phone needs more battery. I usually get around 4 hours screen on time, now only around 3 hours... Tried it now for 3 days with =gpu, will set it back to =dyn and see how it goes.
[HTC Sensation] duck0:
Pretty much. There's the very small chance that the governor shuts down the cpu before the second echo (it's just as if you run two commands, one to enable the cpu and the other to get the value), so it's a race, but pretty unlikely to be lost.

You really should check (by cat:ing cpu0/cpufreq/scaling_max_freq) and see if the first core is not getting set as well.

I should perhaps elaborate, since I see a lot of people repeating commands like magic mantras. I apologize if this seems basic, anyone who knows it can just skip this :)

The command

echo 1 > cpu1/online && echo 1188000 > cpu1/cpufreq/scaling_max_freq

Is actually two. It's the wonderful flexibility of the unix shell. First you have a command (echo) and argument (1) and a redirect (and clobber) this file (>) that makes the standard output, i.e. whatever echo echoes... into a file and then there's a separator (&&) which says, if the first command succeeded, then do what comes after, else stop. I have gotten into the habit of using && instead of ; because it will stop executing if a command fails.
[HTC Sensation] biomech91:
Thanks for the explanation!

I've checked before and cpu0 gets the correct settings, but cpu1 never does.
[HTC Sensation] dkephart:
Do you get an error message? And you don't get 1188 like duck0 did?

You should get an error message if cpu1 is offline when you attempt to set its max frequency. If it's literally being reset, so that the second cat returns 1566, then something other than the ROM is doing that.
[HTC Sensation] biomech91:
I didn't try his commands, but I'm just assuming this is what happens when 99kernel runs. cpu1 is offline so it doesn't receive the correct frequencies and it defaults back to the ROM's default.
[HTC Sensation] tdimarzio:
If you're worried about a potential race condition where the cpu1 interface disappears before you've had a chance to modify scaling_max_freq then you might try backgrounding the 1st part of the command while the second part runs. The && won't allow the second part to run until the 1st part is complete and only if it's successful. Something like:

$ echo 1 > cpu1/online &; echo 1188000 > cpu1/cpufreq/scaling_max_freq

or, if you're worried cpu1 hasn't come online yet by the time the echo to scaling_max_freq has run then add a fractional sleep (does android sleep support fractions?)

$ echo 1 > cpu1/online &; sleep 0.1; echo 1188000 > cpu1/cpufreq/scaling_max_freq

Just a thought. Maybe a better way would be a loop. Something like:

$ (while true; do echo 1 > cpu1/online; done) &

$ cpu1OnlineLoop=$!

$ echo 1188000 > cpu1/cpufreq/scaling_max_freq

$ kill $cpu1OnlineLoop

... haven't tested any of this. Just some potential solutions.
[HTC Sensation] Cubed Guru:
Bricked?

Soooooooooo,

Went to the April 13 build from the March 31 Build (i think) yesterday and the phone was working like a charm. Although, am using an iPhone right now to try the LTE in my area so it did not have an active SIM. The phone was fully charged and am using the Anker 1900 battery, about 3 months old.

Today, I got tired of the iPhone, so decided to turn on the Sensation. On pressing power, I got the normal startup, the boot screen (Cyan Logo) and then out of no where, the phone vibrated a quick double beat and shut down. Tried several thingsto make it to come back up, thought the battery was dead, so plugged it in to the computer (USB Charge) and I got the Orange Led to come up for about 3 seconds, then off, then 2 seconds, then off and then one second and off several times (the one second) and then off.

The phone wont turn on. Unplugged it and messed with several things in the back (removed battery, sim card, Micro SD) by removing and trying to turn it on but to No Avail.

Then plugged it to the computer again, and said, screw it, and got back to work. In about 5 minutes out of no where, for a pop up on windows saying installing driver (this computer was already used before with this phone). So confused, I checked the phone and tried to turn it on again but nothing.

Clicked on the pop up as it failed installation: QSHUSB_DLOAD

A quick search on Google and XDA leads me to believe that I now am in possession of a BRICKED Pyramid.

The phone has worked like a charm giving me no issues and was handled well as well.

Any thoughts? Any Resolutions? Any reasoning on why this could have happened after upgrade to 4/13 version?

FYI, it was S-off and Super CID if it matters.

And finally, Not pointing any finger or blaming the OP for this. The ROM was amazing. I am just trying to understand it, that is it. So please, I would appreciate if you dont tell me to read all the initial posts about "its not the dev's responsibility."

Again, Like I said, I am NOT blaming the OP/DEV for this. I am just trying to see what could have happened.

Thanks for understanding,

A Sensation Widow (stuck with iPhone till the GS4 comes in the mail :( )
[HTC Sensation] Pikabat:
My apologies , I havent been following this thread for a long time. What exactly is going on?
[HTC Sensation] albinoman887:
Tested this, cant reproduce. so sorry but you must have something wrong with your configuration

eh. i wouldnt delete the script. if you do sweep2wake will automaticly turn on and a couple other things you might not want. if you INSIST on using that app. just let its overwride the init script is ran only once at boot up

I'd say do a full wipe and dont let google restore your apps. see if its still there. if it is, maybe clean your sensor lens?
[HTC Sensation] roccatkone:
You are not able to get into the Recovery, too?
[HTC Sensation] rdelar01:
Did you try the HTC Unbricking project: http://xdaforums.com/showthread.php?p=23078349?
[HTC Sensation] topgeardave:
Here's what you're looking for:

http://xdaforums.com/showthread.php?t=1522351

Kind Regards

Dave
[HTC Sensation] roccatkone:
He said, he is on S-OFF. ;)
[HTC Sensation] dkephart:
You are correct. Check out the Unbricking the Sensation thread. This is usually caused by un-S-OFFing in an unsafe manner.

Thread link: http://xdaforums.com/showthread.php?p=23078349

Glad to see you are not blaming anyone but yourself.
[HTC Sensation] sina87:
Hi,

Can someone answer my question please?

Thanks! Appreciate it.
[HTC Sensation] rdelar01:
Try posting this in the Q&A thread here: http://xdaforums.com/showthread.php?t=2181751. This helps to keep this thread clean for development questions and findings. Of course, try searching first...
[HTC Sensation] Cubed Guru:
Negative on the Recovery. It won't even give me that nice litte (annoying) restart vibration.

I did look into the Unbricking project as used to read it when we were still in the very early phases of JB Alpha.

Did see and figured out that it may or may not help. As it is, it is bricked, so will give it a try anyways.

To user dkephart, I will never point a finger to the Dev, although, I am not blaming myself either tho. :D

I am just trying to figure out how it happened as everything was stock, no changes at all. Just a normal shut down and a restart.

Btw, loved the ROM all the time I was able to use it, so Huge Thanks to the Dev.

And to everyone else, will try the method as mentioned above with the Unbricking project as everyone mentioned the very same link.

Thanks again. Hopefully, I can unbrick it and will continue here, if not, off to S4 Forum, although, I doubt it would be as much fun as this one. :D
[HTC Sensation] duck0:
Well, it didn't half take a long time to check out android... 1.87GB of deltas. In any event, I found that the Processor setting does indeed only set cpu0, it's hardcoded. I suppose it expects them to scale in tandem or something? Is that perhaps a kernel setting? 2:30AM anyway so I'm off to bed.
[HTC Sensation] babelac:
Stuck on screen

Haiz...

Sometime the screen cannot touch... The best way at that movement is remove the battery and plug it in again...

It's often happen after receiving a call.

Should modified that bug please!!!
[HTC Sensation] WithAria:
Rather than pulling the battery, try to turn off & on the screen (power button) and the screen will be responsive for attending the calls. Or at least thats the way i do it
[HTC Sensation] mandeep294:
no it dosent work. u have to restart the phone
[HTC Sensation] erdal67:
Hey i flashed this ROM but my sim card doesnt work the signal bar is empty i flashed latest gapps and wiped cache but everytime i reboot the Phone it says the message app has stopped help please!!

Verstuurd van mijn HTC Sensation met Tapatalk
[HTC Sensation] BurnRubber90:
Try making a clean install. Check md5 sum of the zip.