yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] galaxys:
Melvins Beast rom w/No Sense!!
[HTC Sensation] imlijunda:
CM7 of course
[HTC Sensation] nrvnqsrxk:
for what you listed, CM7 is what you're looking for
[HTC Sensation] r3v0Lut10n:
InserCoin, if u like Sense, otherwise CM7

Your decision.
[HTC Sensation] nrvnqsrxk:
Lol the more I read this the more it bothers me.

Of the four requirements you listed two of them are subjective (simplicity, usefulness). If you're gonna call this an open discussion, frame the questions so we can compare facts against facts, rather than opinions.

Like what do u mean by usefulness? CM7 is useless to me since I hate the keyboard and camera. But based on the criteria u set, it's very fast with decent battery. Simplicity? Di u mean which Rom has the least settings so u can't make any changes to optimize the phone to suit your needs?

Sent from my HTC Sensation
[HTC Sensation] dr.m0x:
Cm7 + faux kernel. As simple or complex as you like to make it, great battery life, no sense logging, and every interaction responds notably fatter than sense. Camera lacks a little its true but its good enough for now until they finish fixing it.

Remember also its an alpha release so not quite finished yet but its still very stable for daily use.s

Sent from my Sensation using Cyanogenmod
[HTC Sensation] EniHS:
Tried ARHD, Insertcoin and CM7 v7.

First of all, I use Go Launcher EX (over Sense and ADW).

The fastest was ARHD 3.1.1 with built-in kernel. CF-bench scored higher than SGS2 and all 3d games worked perfectly, but battery life was weak. 100% to zero in 1,5 hour when using with screen on (stock battery).

Then I tried CM7 v7. Go Launcher worked perfect, like on other mentioned roms. But, CF-bench score was really low, much lower than Sensation should have according to CF-bench graphs. You probably say, that I shouldn't care about benchmarks. Yes, it's true, but... CM7 was also weak in games! I tested Let's Golf 2 on all these roms, and on CM7 it was almost unplayable. FPS was good, but there were many lags and I couldn't properly hit the ball. And there is no Sense camera and dialer and weak FB integration. So far - CM7 not for me.

Now I use InsertCoin 2.5.5-2 + bricked kernel and it's perfect. Battery life is very good, all games works perfect, no lags in Let's Golf 2, 3d issue games (f.e. Cordy, Roboto), also work great with no issues. Everything is very smooth and I'm not going to change it for a long time (maybe for ICS if it will be on Sensations).
[HTC Sensation] daman215:
Point blank coredroid or rcmix3.5 both are different than all these roms good battery and everything to me if you want cm7 just go buy a nexus s the new one all stock android and faster than cm7
[HTC Sensation] casht0wn:
all of them...

Tried ARHD and for a sense rom it was nearly flawless except for the battery life (i'd carry a second battery to get thru a day). Then I tried InsertCoin and it was everything i wanted it to be. Super speedy, rock solid and had all of the extras i would usually add in anyway like the advanced power menu and quick settings. But alas it was a sense rom and I wanted to unleash the horsepower my HTC Sensation is packing, so I tried the CM7 <i>ALPHA</i> and i knew i was home. There isn't even a nightly build out yet for my phone and i cannot see any reason i would ever switch to another! even in alpha it is fast, stable, powerful, theme-able, and my daily driver! I say try a few before you choose because if you dont likke it... just flash another. Happy Flashing.

Thanks to kmobs for the selfKANGs!! :D
[HTC Sensation] jayyo:
CM7 + Tiamat + GO Launcher EX

Came from the Nexus One, which I lost :mad:. I was running CM7, with Tiamat kernel, and GO launcher EX. I tried several Sense ROMs and several nonsense ROMs. Ending up going back to my Nexus setup. Plenty fast, all the features I want, battery life so far has been excellent. I don't like Sense.
[HTC Sensation] rust1n:
nrvnqsrxk,

I understand that simplicity and usefulness are conflicting and confusing for some people so let me clarify it a bit more,

by simplicity I meant: user friendly-ness

by usefulness I meant: handy, basically on the opposite spectrum of simplicity

Each ROM could be clarified as either simple or more useful

For example, CM7 is useful but Sense is simpler, respectively of course

Does that help?

Also, since you accused me of not contributing, although I spent the time writing the thread and splitting it into categories, I will say this about the kernels, the faux kernel in my opinion is not very good on battery life but the bricked kernel is, in my opinion, stupendously fast when scrolling through the Sense homescreens and also good on battery life. With these opinions Sensation owners can then make their decision based on people's experience, therefore I do not need to frame the question you can if you would like and that is why it is called an open discussion.
[HTC Sensation] yacbos:
dr.m0x how about battery life compared to android revolution HD 3.6.7 ?, the CM7 doesn't have sense i believe!!

lagging ? i never experienced lagging from neither stock neither the ARH

usefulness ? are you serious ? its an android, you can change it looks add launchers, customize it looks and all your daily apps will work on what so ever rom :D

it is YOU who make it useful
[HTC Sensation] Ali_Shaikh:
Insert Coin no other choice. Been with it since the start
[HTC Sensation] akbisw:
maff's SENSE STOCK OPTIMIZED ROM is BETTER than ARHD in Battery LIFE and SNAPPY AS HELL. ALMOST LIKE CM7 no DELAY. Makes my friends Razor look like made in china i swear (the software atleast)
[HTC Sensation] UNDFTD:
CM7 is the best rom in terms of my preferences.

CM9 (ICS) is just around the corner too.
[HTC Sensation] nonione:
Rc3d

No doubt about it specially since the new version 1.0
[HTC Sensation] redbullcat:
CM7! Stock Android (with some tweaks thanks to Cyanogen) is just the best.

As said before, CM9 is just around the corner as well!
[HTC Sensation] shadow666:
ARHD or CM7 grear ROMS
[HTC Sensation] swiftinmotion:
used every ROM you asked about. used cm7 for months but I'm stuck on tripnmiui. to me clowns on cm7. I won't use a cm build again till cm9 is out.
[HTC Sensation] Rickdaddy:
ran arhd for a while and was pretty happy with it, then switched to cm7 and my mind was blown.
[HTC Sensation] RAWLiNGS007:
Battery Issue

Hi Guys!

I just upgraded to a Sensation from a Desire, and Its an amazing phone and i love it. :)

I installed CM7 alpha, with the recommended radio, but unfortunately im getting extremely bad battery drain. I barely used it today and its down to 38% in 8 hours. When i say barely used, I mean less then 15 mins of calling, and no more then 30 mins browsing. Can you guys give me some advice on this matter?

I did wipe data, cache, dalvik before flashing...

Thanks.
[HTC Sensation] daman215:
All of them are good,Devs do it for free respect all
[HTC Sensation] Bronyr:
ARHD for sense and CM7 for AOSP.

I don't like sense so CM7 is my daily driver.

Sense rom is like a bloated and decorated cow... AOSP rom is like a musketeer - all action and no nonsense.
[HTC Sensation] marcos600rr:
Agree mate
[HTC Sensation] Jonny:
Leedroid super sensational 4.2.1 is a rock solid ROM that has never caused me problems so even though its not on the list, I definitely recommend it :)
[Nexus S Android Development] kevinngck1:
What are creative guy…so many useful mod. Great!!
[Nexus S Android Development] Igotsanevo4g:
Just when I start to think what else can this guy come out with.. lol

Trying it now
[Nexus S Android Development] kevinngck1:
Is the liveoc file just included in morfic teuv kernel???
[Nexus S Android Development] Ezekeel:
Morfic's TEUV kernel was the inspiration for this mod. It is not implemented in any kernel yet.
[Nexus S Android Development] Ezekeel:
The first bugfix.

The sleep frequency is also adjusted according to the selected OC value, so a proper sleep frequency is chosen when the device is suspended.

Bug fix: http://www.pastie.org/2635644
[Nexus S Android Development] franciscofranco:
Pretty impressive idea and implementation.

Although I don't have this phone (hope to get one soon as it's for a great price here in Portugal), I stumbled upon this thread and I liked it very much. Keep it up!
[Nexus S Android Development] lolokman:
This is eactly what I want!!!

You're my hero;)
[Nexus S Android Development] simms22:
very nice.

i wonder why the increased battery drain. are you still getting similar numbers in setcpu's "time in state" as you were with teuv?
[Nexus S Android Development] window7:
My goodness! Ezekeel! You're just that excellent! ;)
[Nexus S Android Development] cdesai:
Nice idea, although I don't have a nexus S, (thanks @tapatalk for showing me this thread)
[Nexus S Android Development] morfic:
I'll need some time to wedge this in.

Check why the compile fails after adding the failed hunks (looks like possibly missapplied fuzzy hunk)

Aside i would want it to work with each kernel type, be it TEUV, TUV or T12, T13, T144 or T1544

Since that is all layed out as Kconfig options i'll have to check where to apply the code you added to stock source so it will indeed work for all the speeds, kind of as a added bonus to the current speeds.

Then i would have to shoehorn in a voltage control and OCing without voltage control is not a good idea, 1.0GHz has some obvious headroom, but the OC speeds especially will want a nudge on the voltage side if you nudge the bus/cpu/gpu across the board by x%

and with kernel.org up (not android.git.kernel.org (unless we android geeks just totally hammered it)) i would prefer to grab latest samsung source, freshen up all builds, then work on integrating this.

I could see the netarchy layout benefit from this patch as there are no Kconfig #ifdef to deal with :) (I'm looking at you mathkid ;P lol ;) hah! coo ;) <3)

Just a little timeframe setter to tune the expectations to a realistic level.

Thanks Ezekeel
[Nexus S Android Development] Ezekeel:
Thanks to all your kind words.

Seems like the sleep frequency fix also took care of the high battery drain.
[Nexus S Android Development] morfic:
Very nice.

Told you those hummingbirds are picky about their sleep freq :)

Now we know OCing it causes high drain instead of the typical SoD when no high enough clock is available.
[Nexus S Android Development] simms22:
imagine that..

a better sleep makes a happier kernel ;)
[Nexus S Android Development] kenvan19:
Dude, ezekeel do you ever sleep or think about anything other than making our phones more powerful? How can so much utility come from one guy and why are you not employed by the government finding new and exciting ways to kill people. Imo you deserve a massive salary with a brain like yours.

Sent from my Nexus S MV from the XDA Premium app.
[Nexus S Android Development] morfic:
He codes on the job, i think that makes a big difference on the time availability front. ;)
[Nexus S Android Development] lolokman:
Any news or update?

Seems no kernel has added this mod:(

Really want to have a try:(
[Nexus S Android Development] jorim.tielemans:
It 's coming to Matr1x..
[Nexus S Android Development] SA-07:
Its here!!! Matr1x 8.5
[Nexus S Android Development] belvedere:
how do you set the 'oc_value' in the 'liveoc' file?

oc_value = 110

totally guessing here.

edit: the reason I ask is because MathKid has implemented this into his Matr1x kernel and there is a blank liveoc file.

I've attempted to edit with Root Explorer's text editor but the changes don't seem to stick.
[Nexus S Android Development] caleb1783:
i think you have to change 'oc_value' file on /sys/class/misc/liveoc

I tried changing it but got reboot when i saved. gonna try again with ondemand governor
[Nexus S Android Development] Lalaca:
Root Explorer doesn't, strangely enough, save to a Unix-compatible format. What you need is something like Notepad++ (for Windows) to edit the file.
[Nexus S Android Development] Maximilian Mary:
If it's like his other mods, you would set it in terminal emulator:

su

echo 120 > /sys/class/misc/liveoc
[Nexus S Android Development] as6:
liveoc is a directory

i think it should be

echo 120 > /sys/class/misc/lieveoc/oc_value

Can't get it running on Matr1x. Everytime I set a value I get a reboot. Already raised the voltages.
[Nexus S Android Development] igor.tonky:
ezekeel - is there a limit of 20% on OC? i'd like to try more, like 25% :)
[Nexus S Android Development] Maximilian Mary:
Good call. Maybe it also needs

echo 1 > /sys/class/misc/liveoc/enabled

Edit: nope. Just what as6 said.
[Nexus S Android Development] pan1980:
this mod changes all frequencies from 100MHz to X.

but if we want to use say 220MHz bus only in max frequency and all other states stay with normal bus speed ? is it possible ?

so we can have 100MHz/200MHz/400Mhz/800Mhz with default bus speed and 1100MHz with 220Bus speed.
[Nexus S Android Development] Maximilian Mary:
It seems the bus clock/cpu steps don't like to be changed while the system is running. Is it possible to store the oc_value somewhere the kernel can read it as it is loading? Then one could change the value and reboot to apply.

Edit: Nope, that's not the problem.

Changing the oc_value sets max_freq to the highest clock speed available, and for some reason, my phone can't handle 1752 MHz. :rolleyes:

More info at the matr1x thread.
[Nexus S Android Development] Bradart:
I can't get it working on the latest matr1x. Its being very cryptic about what it wants me to do. Liveoc does not show as a directory, but the terminal tells me that it is.
[Nexus S Android Development] Maximilian Mary:
It is a directory in ramdisk, not on the filesystem, so you can't edit it like a traditional file. Use the method above, along with one of the workarounds in the matrix thread to keep it from clocking to an obscene speed.
[Nexus S Android Development] Ezekeel:
Fixed.

When OC value is changed, the minimum and maximum frequency limits set by the user are adjusted according to the new frequencies.

Bugfix: http://www.pastie.org/2691219
[Nexus S Android Development] Ezekeel:
New patch.

Made sure the bus speeds and frequencies are not changed while a frequency change is currently ongoing.

Bugfix: http://www.pastie.org/2710098
[Nexus S Android Development] Ezekeel:
Bugfix for the last bugfix.

Instead of a spin lock (which leads to problems) we use a mutex to make sure the bus and frequencies are not changed while a frequency change is ongoing.

Bugfix: http://www.pastie.org/2710386
[Nexus S Android Development] belvedere:
so is there a way to confirm changes have actually been made other than the phone freezing if it can't handle too high of a setting? I just did 105 to start out conservative. on Matr1x 9.0 and my phone appears to be ok...

Thanks as6 for the terminal commands. :)

edit: nevermind, just came across this post - http://xdaforums.com/showpost.php?p=18383836&postcount=3350

edit again: I've yet to attempt to make igor.tonky's script but I just noticed in SetCPU my min frequency is 105 (100) and max is 1260 (1200). so I guess it's working ?
[Nexus S Android Development] thoth77:
Adequate Voltages?

Mr. Ezekeel

I'm using Matr1x_v9.0

This is my LiveOC Script

Adequate Voltages?

#!/system/bin/sh

echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "110" > /sys/class/misc/liveoc/oc_value

echo "1450 1400 1340 1240 1190 1040 940 940" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "1100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "lazy" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

http://xdaforums.com/showpost.php?p=18383836&postcount=3350
[Nexus S Android Development] Ezekeel:
First raise the voltages and set the max frequency, then raise the OC value. The order is important!
[Nexus S Android Development] thoth77:
How about this?

#!/system/bin/sh

echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "1450 1450 1400 1250 1200 1050 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "1320000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "110" > /sys/class/misc/liveoc/oc_value

echo "440000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "lazy" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

---------- Post added 20th October 2011 at 12:27 AM ---------- Previous post was 19th October 2011 at 11:59 PM ----------

Reboot loop :confused:

Raise Voltages more?
[Nexus S Android Development] Ezekeel:
echo "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

1320MHz is not available until the OC value is raised to 110.

Ask mathkid about the voltages.
[Nexus S Android Development] thoth77:
Works Well

#!/system/bin/sh

echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "1450 1450 1420 1250 1200 1050 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "110" > /sys/class/misc/liveoc/oc_value

echo "400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "lazy" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Thanks :)

I will ask mathkid95 about the voltages
[Nexus S Android Development] Ezekeel:
Small change.

If no mutex lock can be obtained, an error value is returned to inform

the caller that the frequency was not changed.

Bugfix: http://www.pastie.org/2746226
[Nexus S Android Development] thoth77:
increasing the voltage for the maximum state by 30mV

"I am currently running my Nexus with an increased performance +10% using the stock frequencies 100->110, 200->220, 400->440, 800->880 and 1000->1100 and after increasing the voltage for the maximum state by 30mV everything is working fine without a reboot for 24h now."

Raise them all by 30

or

Raise the only voltage for max frequency by 30?
[Nexus S Android Development] thoth77:
No reboot

Matr1x v9.5 kernel & Oxygen 2.3.1 rom

echo "1450 1390 1330 1250 1230 1050 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

or

echo "1450 1390 1330 1280 1200 1050 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

or

echo "1450 1390 1360 1250 1200 1050 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

---------- Post added at 10:50 PM ---------- Previous post was at 10:10 PM ----------

Matr1x v9.5 kernel & CM Nightly #233 also no reboot

Very Smooth~~~

My Choice :

#!/system/bin/sh

echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "1450 1390 1330 1280 1200 1050 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "110" > /sys/class/misc/liveoc/oc_value

echo "400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "lazy" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[Nexus S Android Development] JmPTaz09:
Great mod; thanks Ezekeel
[Nexus S Android Development] Ezekeel:
1. Reverting back to mutex_lock to make sure no important request like enabling/disabling further frequency changes are skipped.

2. The mutex is unlocked before the CPUfreq stats are resetted. With the above modification this seems necessary to avoid lockups when changing the OC value.

3. The frequencies and bus speed are updated only when the selected OC value actually did change.

Bugfix: http://www.pastie.org/2756640
[Nexus S Android Development] as6:
Why do you set the governor to conservative then at the end to lazy?

Btw great mod Ezekeel.
[Nexus S Android Development] thoth77:
igor.tonky

according to igor.tonky

http://xdaforums.com/showthread.php?p=18383836#post18383836

and

http://xdaforums.com/showthread.php?p=18557005#post18557005

"First raise the voltages

and set the max frequency,

then raise the OC value. The order is important!"
[Nexus S Android Development] as6:
Ok but why set at first the governor to conservative.

Shouldn't this also work?

echo "1280 1200 975 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "120" > /sys/class/misc/liveoc/oc_value
echo "400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "lazy" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[Nexus S Android Development] thoth77:
Hmm...

I'm simply careful

http://xdaforums.com/showthread.php?p=18380830#post18380830

▽

http://xdaforums.com/showthread.php?p=18383836#post18383836

Let's ask Ezekeel about "what it is good for"
[Nexus S Android Development] v3rk:
my phone always locks up with those voltages and live oc set at 120.

i've never in my life messed around with voltages before learning about this mod, it's actually really exciting. i have a lot of things i'm wondering about. should voltages be altered in certain increments, or can i try any voltage and test the results? should voltages be altered by the same amount across all frequencies? if not, which level of frequencies require more juice to avoid lockups?

thanks in advance, like i said i'm very new to this but eager to learn.
[Nexus S Android Development] polobunny:
Increments, always. The biggest danger with increasing voltage is heat. Heat is nearly always what kills components. When you increase your voltage, your create more heat, so always have a look on your temperatures when trying something higher.

Further down the road, there's electron migration, but that shouldn't be a problem for any of us.
[Nexus S Android Development] timeToy:
Dude, don't scare the guy, we are not running our phones remotely with enough voltage or for long enough to cause electrons migration. This is problem for people overclocking CPU with LN2 and juicing them to really insane level.

The WORST that can happened is a battery pull freeze.
[Nexus S Android Development] polobunny:
You'll note the last part of my comment:
[Nexus S Android Development] v3rk:
thanks for the input, guys! leads me to another. . . what increments should be used when upping voltages? 5? 10? more?
[Nexus S Android Development] as6:
Try these voltages:

1280 1200 1050 950 950

they should be stable

If they are stable install setcpu and try to lower the voltages. I do first 25 and then 5mV steps. Don't mark set at boot. When you found your lowest working voltages write them in the script.

Ready

I use only 480 and 960MHz and got a smooth phone and good batterylife.
[Nexus S Android Development] Ezekeel:
I am currently running at a performance +25% with a bus speed of 250MHz and a maximum frequency of 800->1000 @ 1250mV and it seems as long as the maximum CPU frequency does not go beyond a certain critical value (for my phone around 1400MHz), the device can handle higher bus and GPU speeds just fine. So I increased the maximum OC value from 120 to 150 which should give people enough room for experiments.

Bugfix: http://www.pastie.org/2768535
[Nexus S Android Development] ellesshoo:
Ezekeel,

How do I know if live oc is successful? I ran my desired commands in terminal. I can see that it did change my voltages in setcpu. But all my available clock speeds are like "200000, 400000, 800000, etc" I passed 120 to liveoc so I guess I was expecting to see "220000, 440000, 880000, etc... ". Any help?

Also, do the settings persist after reboot?

If I make an init.d script for applying settings at boot can I created the script in something like script manager? And do I need to mess with the scripts permission settings in root explorer? Please keep in mind I'm trying to accomplish this without the use of adb/computer since I'm rarely near one with adb installed.
[Nexus S Android Development] Ezekeel:
There should be a message in the dmesg log about the change of the OC value. Frequencies should change right away, so something definitely went wrong there. Or this is just a problem with SetCPU not updating; try force closing it.

The OC value resets to 100 on boot, so you need to set it on boot with an init.d script or similar. I always use adb and vi to create a new script; I have no experience with other methods.