This thread has the objective of testing the latest Hero's ROMs available, through CPU benchmarking.
To perform these tests the following applications have been used:
Linpack 1.1.2 - GreeneComputing benchmark application for CPU and Dalvik VM performance. Measured in MFLOPs. [link]
BenchmarkPI 1.11 - Application used for benchmarking CPU performance. The objective is to calculate the 1st n digits of PI. Measured by a timer. [link]
Benchmark 1.03 - Softweg's test suite for benchmarking. All tests, except the GPU one, done here to account for CPU, Memory and File System performance. Measured by an internal score. [link]
All the ROMs were clocked @ 691MHz "Performance Mode" under SetCPU [link], unless specifiied otherwise.
After each ROM installation, the 4 applications were installed, Airplane mode was turned on, the phone was rebooted 2 times, and I clocked the 3rd boot time.
5 dummy tests were made prior to the real 5 valid tests, per application, so the results would be clearer.
The higher the score, the better, except for BenchmarkPI, since it is a timed test.
Non-JIT and non-BFS kernels were used in these tests.
Also, I forgot to time the Official 2.1 Boot time, my bad. Feel free to do it.
This work was made as a complement to Arkymedes 3D/OpenGL benchmarks. See his thread [here].
>> If you have a ROM request, just post it and I will test it. <<
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog
Changelog @ 15/July/2010:
HebVillain 1.1.2 [link]
RoboMIX 0.5.5 [link - android.com.pl]
Changelog @ 13/July/2010:
Chocolate Eclair 1.1r2 [link]
RoboMIX 0.2.1 [link]
Changelog @ 12/July/2010:
Fallah 1.3 [link]
Changelog @ 11/July/2010:
Chocolate Eclair 1.1 [old link]
Changelog @ 9/July/2010:
aHero 1.1 [link]
Androbin CR4 - CMH 5.0.7 [link]
Chocolate Eclair 1.0.1 [link]
Cronos Droid 2.0.2 [link]
Cyanogen Mod 5.0.8 [link]
Daguu Espresso 1.3 [link]
Daguu Sense 1.0 [link]
EzHero 5.0.1 [link]
HeroDroid 0.7 [link]
Kimera 2.1 [link]
Official Android 2.1 [link]
SuperHero 2.0 [link]
Vanilla Eclair 4.0 [link]
VillainROM 12.0.0 [link]
Looking forward to the charts.
Holding off trying new ROMs for your results.
scouzer said:
Looking forward to the charts.
Click to expand...
Click to collapse
quote for subscribe
Graphs added. Enjoy.
respect your work. Very nice work done here. Thanks
Feeyo said:
respect your work. Very nice work done here. Thanks
Click to expand...
Click to collapse
I'm tired, lol.
Almost 12 hours straight (with some pauses, obviously).
Thanks for the comment.
As usual Kimera shows up and kicks the ass off whole dev teams.
Very interesting work. Thank you very much. You must have worked hard.
scouzer said:
As usual Kimera shows up and kicks the ass off whole dev teams.
Click to expand...
Click to collapse
Really?
From looking at those results I thought it was interesting to see there wasn't one clear cut better rom as they all seem to excel in different areas..
Although considering super hero is based off vr12 I was shocked to see sense adding 10 secs to the boot time....
As im running vr12 but using launcher pro and no sense widgets might aswell switch over...
Thanks for putting in the time to do this!
Very nicely done.
Nice work.
Only comment (take it as constructive criticism btw for next time, don't worry bout it), is that in the last graph, it's really pretty hard to see which bars are for each ROM. It may be my eyes, but I just felt it harder than the others. A little gap between each possible?
Nice work btw.
I was also interested to note that VR12 is 10 seconds longer to boot than SuperHero, despite both being based on very similar base ROMs, and made in the same way.
anon2122 said:
Nice work.
Only comment (take it as constructive criticism btw for next time, don't worry bout it), is that in the last graph, it's really pretty hard to see which bars are for each ROM. It may be my eyes, but I just felt it harder than the others. A little gap between each possible?
Nice work btw.
I was also interested to note that VR12 is 10 seconds longer to boot than SuperHero, despite both being based on very similar base ROMs, and made in the same way.
Click to expand...
Click to collapse
I thought SuperHero was a stripped down version of VR10.3?
Great Job! Love it, but could you add Jit to them to?
xenoside said:
Great Job! Love it, but could you add Jit to them to?
Click to expand...
Click to collapse
JIT is unstable and tends to lag the menus performance, though it increases the Linpack score. It may be seen has a ghost improvement, since you pratically don't have any advantage with JIT enabled.
I speak for myself. I prefer an overall fluid ROM than a JIT enabled one, that will FC every 10min and reboot every 30min.
Correct me if I'm wrong.
shokkapic said:
JIT is unstable and tends to lag the menus performance, though it increases the Linpack score. It may be seen has a ghost improvement, since you pratically don't have any advantage with JIT enabled.
I speak for myself. I prefer an overall fluid ROM than a JIT enabled one, that will FC every 10min and reboot every 30min.
Correct me if I'm wrong.
Click to expand...
Click to collapse
I vote for this benchmark to be STICKY! Seriously good job and well worth reading.... Cheers m8!
I'd like to see results with and without JIT enabled.
It would be a good measure of the performance improvements/losses possible on different roms (sense/AOSP etc..), and maybe even throw in a "# of FC's with JIT enabled during benchmarks" graph to show how stable/unstable it is.
Also maybe a game/fraps type benchmark would be useful?
Nothing like tripling all the hard work you're doing
rakig said:
I'd like to see results with and without JIT enabled.
It would be a good measure of the performance improvements/losses possible on different roms (sense/AOSP etc..), and maybe even throw in a "# of FC's with JIT enabled during benchmarks" graph to show how stable/unstable it is.
Also maybe a game/fraps type benchmark would be useful?
Nothing like tripling all the hard work you're doing
Click to expand...
Click to collapse
The same way the results are very similiar without JIT @ Linpack application, the same similarity would appear with JIT enabled.
About the # of FC's, I would need a lot more time than 30 / 40min per ROM (the amount of time I used in these sequence of tests), and that is time I simply don't have, for now. To test the # of FC's and restarts I would need something like 3 hours of intense use per ROM, opening a whole bunch of different apps, basically "wasting time" until something goes wrong.
About the game/fraps type benchmark, Arkymedes is doing something similar. Read again the first post. You will find the link to his post there.
anon2122 said:
Nice work.
Only comment (take it as constructive criticism btw for next time, don't worry bout it), is that in the last graph, it's really pretty hard to see which bars are for each ROM. It may be my eyes, but I just felt it harder than the others. A little gap between each possible?
Nice work btw.
I was also interested to note that VR12 is 10 seconds longer to boot than SuperHero, despite both being based on very similar base ROMs, and made in the same way.
Click to expand...
Click to collapse
I will try to fix the last graph. Since it is made in Google Docs and updated automatically, it doesn't have the amount of editing settings as in Microsoft Excel.
I had to repeat the VR12 boot for a 4th time, because it was taking 90+ seconds, already overclocked @ 691Mhz on boot. The 4th time was the best I got from all the other 3. Maybe if there was a 5th try, the results would be more similar. I will check it now, since VillainROM was the latest rom to test, and I hadn't flash any since yesterday. I will edit this post in 2min, just to boot it once more. BRB.
Edit: 73 Seconds... The 70 seconds boot was made with Airplane Mode on. This boot wasn't.
----------------------------------------------------------------------------
I'm very glad you guys are taking my "little" work so serious. It means a lot to me.
Also, the last graph was updated, and the differences between the ROMs are clearer now.
Thank you all, once again.
Great stuff, the boot times made me test Vanilla Eclair 4 and it rocks (UI was more responsive to me than ezHero 4.0)! I'd suggest to add (for the future) the amount of free RAM after rebooting with standardized autokill settings. Vanilla Eclair scored very very well here, better than other rom I have tested.. a shame I cannot get the HTC dialer in vanilla roms :-(
Awesome work I'm happy to see daguu roms score that high - maybe this will help flzyup gain some popularity because apparently his work is on par and sometimes better than most of other devs' work.
Related
Hermes WM Roms Benchmarks
My Hermes is dead.. this isnt going to get updated again, im so sorry
One of the MOST common questions we get, is, what's the lites rom? And what's the fastest rom?
How to make your rom faster
A new program called WMRegOptimizer, which you can get here, has had noticed improvements on the speed of my phone and others.
For more detailed info and a few helpfull recommendations.
My Methods:
I take the rom, fresh from the chef, and flash it, that's it, no UC, no changes, nothing!
I run the tests unplugged, and before connecting to activesync.
All i install is my battery drain tool, and my benchmarking tool.
I dont change the Pagepool, or the cache settings, for the main benchmarks.
Below there will also be benchmarks of the rom i use, and other members of XDA, post yours up as well!
Also, attached you will find a XML you can import with Advanced config, or use in your UC, this is cache tweaks, and i will post benchmarks to show how they help.
I know that My benchmark suit isnt the best around, i chucked it together in 5min, but, as im using the same on all roms you can compare without worrying to much!
If there was any "odd" readings, aka something much higher/lower, I re benchmarked, re flashed, until I was sure its not an error I can do anything about.
About each section :
Rom name: name of the rom
Rom build: The build of the rom
idle power consumption (mA): This is the power it was draining in mA (milliamp) sitting in the power consumption tool with the backlight (at rom default), the device was not allowed to turn off ect. And i left it for 2-5min to average.
Integer: How quickly the phone performed Integer calucations, see here for more info
floating point: How quickly the phone performed floating point calucations, see here for more info
RAM Access: How quickly the phone could access the RAM
Draw Bitmaps: How quickly the phone could redraw bitmaps on the screen (graphical performance)
Main Storage read/write: How quickly the phone could read/write to the main storage.
Higher is better apart from for idle power consumption, where lower is better.
Power consumption is VERY MUCH affected by screen brightness, I should have standardised this.. but it still give an idea..
My conclusions
RBS roms are faster than Non BS
Compressed roms are slower and use more power in idle for the most part
Some roms are faster but use more idle power, and different roms have there strengths and weaknesses!
.zip has all the benchmarks so far, along with graphs.
Pagepoll tests
I decided to take 3 roms and test 6v8meg PP, the results are in the .zip
For the most part, the 8meg PP roms where faster, but has less ram (duh). I would do more tests, but it would take far to much time..
Graphs
These are out of date compared to the .zip, I will update them asap.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There ALL in the .zip, they would take up to much room to post here.
Performance XML
This file can be run with UC, or imported with advanced config.
What this does is fine tune the cache sizes to what I think gives the best performance.
Updated on 25th August
Added Power management tweaks to the XML
Updated the Cache settings.
Added tweak to remove the delay when taking pictures.
Examples:
CRCv12.9 BS naked 8meg PP pre XML benchmarks. (See that the higher pp is faster than the 6meg one in the main benchmark tests)
Integer: 181.9167
Floating Point: 5.779
Draw Bitmaps: 710
RAM Access: 1620
Main storage (write): 710.62
Main Storage (read): 3690.09
CRCv12.9 BS naked 8meg PP post XML benchmarks.
Integer:184.3587
Floating Point: 5.783
RAM Access1632
Draw Bitmaps: 726
Main storage (write)710.37
Main Storage (read)3685.66
Performance settings if you dont want to use the XML:
File system cache: Enabled
File system cache size: 2megs
File system filter cache: 8192 sectors
Glyph Cache: 128KB
What to benchmark your own rom? See this post for the program I use!
Notes: None of the tweaks in the XML is my work, apart from making it and posting it here, im just trying to make it easier for the newbies to get the most from there device!
WM 6 roms
This thread here by KarhU has benchmarks for most WM6 roms
Todo:
*Add links to rom thread in the spreadsheet.
*Work out why there is the MASSIVE increase in main memory speed on CRCv12.7 and roms based on it. (seems to be some due to some tweaks in the rom!)
If this has helped you, or you like what I do, maybe consider a small donation, anything is very gratefully received!
I'm shaking
In my chair, waiting for the results, ..... half an hour too long, get your a into g
zocster said:
In my chair, waiting for the results, ..... half an hour too long, get your a into g
Click to expand...
Click to collapse
It takes 10min per rom And i keep having to text/call mid power usage test ;/
Bravo
Awesome work, ...
Excellent job, thanks a lot !!
That all the current roms done, Ill try to make it easer for you to see what everything means tomorrow, right now I need to get working, get my Hermes back to how I like it, and do some work
Any feedback? Any roms you want me to do? any graphs? Just say!
Impressive..simply impressive..
blackout128 said:
Impressive..simply impressive..
Click to expand...
Click to collapse
Thanks you!
Now, to get the ball rolling, lets see your benchmarks!
Heres mine: CRCV12.9BC-naked 8meg PP
Integer: 181.1740
Floating point: 5.773
Ram Access: 1637
Draw bitmap: 721
Main Storage (write): 708.24
Main Storage (read): 3683.45
veyka said:
Thanks you!
Now, to get the ball rolling, lets see your benchmarks!
Heres mine: CRCV12.9BC-naked 8meg PP
Integer: 181.1740
Floating point: 5.773
Ram Access: 1637
Draw bitmap: 721
Main Storage (write): 708.24
Main Storage (read): 3683.45
Click to expand...
Click to collapse
Mine fully loaded, with MSN pushing mail, and activesync on 2003 OWA sync.
integer: 178.6745
floating pt: 5.751
RAM Access: 1600
Draw bitmaps: 565
Main Storage Write: 614.46
Main Storage Read 3723.64
Heres mine: PDACorner NRBSN V20 8 Meg PP
Integer: 176.8177
Floating point: 5.746
Ram Access:1626
Draw bitmap: 716
Main Storage (write):631.45
Main Storage (read): 3453.63
@ veyka!
idle power consumption higher is better or lower is better ?
dvha79_ddt said:
Dear peyka!
idle power consumption higher is better or lower is better ?
Click to expand...
Click to collapse
Lower is better! Wooops! Ill correct that in my first post. Thanks
veyka said:
Lower is better! Wooops! Ill correct that in my first post. Thanks
Click to expand...
Click to collapse
Thank you for your fast reply, This topic is real mean.
Good luck!
dvha79_ddt said:
Thank you for your fast reply, This topic is real mean.
Good luck!
Click to expand...
Click to collapse
Thanks again! Im just benchmarking another 4roms! update asap.
5 roms added! New better graphs planned for later today!
Awesome work!
Keep it up!
Any Schap's 4.40 Beta benchmark??
Nico
thank, man - you do a nice work
Thanks man very useful, I'm still on WinMo6.0 deciding where to go.
colombia7 said:
Any Schap's 4.40 Beta benchmark??
Nico
Click to expand...
Click to collapse
I can do! Ill look into getting a non locked copy!
And thanks everyone
I ran out of steam last night But ill finish off the updates for today.
[APP] RogueTools v1.1 - [Overclock & Change Screen Density] - [Updated: 04/27/2010]
I now present you with RogueTools v1.1.
Summary:
This application is designed for the Vogue, Kaiser, Polaris and Nike devices. It allows you to dynamically overclock your device as well as change the screen density.
Requirements:
This application requires write access to your /system so this will only work on EXT2 and NAND installations.
Overclocking Notes:
Overclocking results will vary. Based upon the beta test results everyone was able to Overclock to 500mhz and have very stable results. Above this results really were mixed. Give it a try, I'd love to hear your results.
To download, search in the market for "RogueTools"
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before (400mhz) and After (500mhz) CaffeineMark Benchmark
HUGE thanks to all of the beta testers. You guys did an outstanding job!:
citrit, cp0020, damianiw, DmK75, dzo, GriloVirante, Incubus26jc, inertone, jnadke, mblaster, Millence, mssmison, paipo, pyrator, scouzer, vrflyer
Disclaimer:
As always, I’m not responsible for anything that happens to your phone while using these files.
Future Versions:
I'm looking for some creative ideas on other additions you'd like to see added to this application. So if you have some thoughts, please let me know.
Changelog:
04/27/2010
Added device support for Nike
04/24/2010
Version 1
Awesome. Can't wait to try.
Will this affect the battery life?
Right now the battery is bad enough with android, but it does sound really nice.
Nice,
will try it out
Overclocking will always effect battery life negatively. Under-clocking will increase it.
You don't always need your Kaiser running at 400 Mhz, but I think Android throttles it anyway.
Dukenukemx said:
Overclocking will always effect battery life negatively. Under-clocking will increase it.
You don't always need your Kaiser running at 400 Mhz, but I think Android throttles it anyway.
Click to expand...
Click to collapse
When sleeping it underclocks to ~200Mhz (it seems that "cat /proc/cpuinfo|grep BogoMIPS" displays something around the clock value).
nice work bro...works great on my tilt
could you upload the update.tar ?
Tukang PDA said:
could you upload the update.tar ?
Click to expand...
Click to collapse
Can't You read?
To download, search in the market for "RogueTools"!!!!
Awesome.
Kaiser
Benchmark
400MHz : 91 points
475MHz : 130 points
500MHz : 140 points
Nice!
Appears to work on my tilt!
Nice Job!
liveskelet said:
Awesome.
Kaiser
Benchmark
400MHz : 91 points
475MHz : 130 points
500MHz : 140 points
Click to expand...
Click to collapse
600Mhz : Called fire brigade....
zenity said:
600Mhz : Called fire brigade....
Click to expand...
Click to collapse
Are you serious?
I may have to raise the max threshold for you Kaiser users. 700???
Holy crap this works awesome. Tried it on Polymod 2.1d and it kinda blew my mind. I've only overclocked to 450mhz so far, but it's a night and day difference. Thanks a ton myn, great work.
tonyc0642 said:
Holy crap this works awesome. Tried it on Polymod 2.1d and it kinda blew my mind. I've only overclocked to 450mhz so far, but it's a night and day difference. Thanks a ton myn, great work.
Click to expand...
Click to collapse
I've set mine to 500 Mhz, any chanche for overheating (when going higher then 500)?
(I've deleted some .apk packages (voice dialer,...) and together with this tweak it runs really great, almost 40MB free ram whe killing all apps)
Great app. Can someone give a bit more info about the "increase screen dpi" option? When and why would I want to use this feature? What is a "good" value?
robuser007 said:
I've set mine to 500 Mhz, any chanche for overheating (when going higher then 500)?
(I've deleted some .apk packages (voice dialer,...) and together with this tweak it runs really great, almost 40MB free ram whe killing all apps)
Click to expand...
Click to collapse
I can't say for sure since I'm not the one that developed this, but it seems to me that it should actually save your battery since it underclocks when the phone is sleeping, unless of course you're actively using it a lot while at 500mhz or more, in which case you'd use your battery quicker and run the risk of overheating. Like I said, I can't be certain, so you may want to wait for a reply from myn himself on it.
jt131 said:
Great app. Can someone give a bit more info about the "increase screen dpi" option? When and why would I want to use this feature? What is a "good" value?
Click to expand...
Click to collapse
It should be set at 120dpi by default, at least it was for me. The dpi is "dots per inch," which is pretty much what it sounds like. If you make the value higher, it will make things larger. If you make it smaller, well you get the idea. I played around with it some to check it out, but I'm happy with the default dpi.
Thanks tony. I guess it could be useful for applications that do not work correctly in Kaiser's QVGA, like iGO for example. Would a lower dpi setting compensate for iGO's larger resolution design?
Reducing the DPI makes everything small so iGO might work but it will make reading everything harder.
jt131 said:
Thanks tony. I guess it could be useful for applications that do not work correctly in Kaiser's QVGA, like iGO for example. Would a lower dpi setting compensate for iGO's larger resolution design?
Click to expand...
Click to collapse
Who needs to read, so long as you can see the map and hear the voice commands?
FroydVillain 1.6.0
This bit’s the introduction. If you’re not interested in who we are, or how we got here, or are of the TL;DR mentality, then skip this entire section.
Well folks... For those of you still with a Hero (like me), then you might remember the name VillainROM vaguely. It's been a while. The last time I posted a ROM was back in the days of VillainROM 6. That seems like ages ago. And I spent 16 hours solid working on it, and vowed never to touch another ROM ever again.
As many of you have noticed, I’ve just posted a ROM... So what went wrong? Well, I was playing about, finding out how fast I could compile the latest CyanogenMod on a quad core i7 box... Then I decided it might be an idea to try and build for Hero, as it might not be fruitless wasting of the world's trees and energy supplies. So off I went, and compiled a ROM. I downloaded it, and to my surprise, it actually booted! Albeit, this was without Apps2SD, or many other things. The kernel wasn't as fast as I was used to, and had a few old bugs that we had fixed before.
I decided to tweak some things and rebuild it. And over time, FroydVillain 1.6.0 was born. After about a month of working on this, I think it's finally time to release it. I've built, rebuilt, tweaked, reverted, changed, footered, kicked, punched and hammered this ROM into shape, and it should be the best of what's been available over the last month on Cyanogen's sources.
Before I go onto the ROM, I would like to thank a fair load of people. First of all, all the Cyanogenmod developers. Without them, this ROM would not exist. Big props out to them for their excellent work. Next, the VillainROM developers, including Ninpo for his ARM optimisations in CM6.1, Kendon for his usual behind the scenes scripts and time in setting things up, DMzda for his dedication in helping me test this ROM in the latter stages, MikeBeecham for his artwork and designs used throughout the ROM, HomerSp for his help taking Mike's bootscreen to life, and everyone else who has been there helping... Shen, Lenny, NPRussell, Mike, RaiderX, RichardTrip, Acolwill, Alankila and sorry if I forgot anyone. But this ain't an Oscar speech, so I must stop now.
Finally big props go to Erasmux, whose FlyKernel 11c has been tweaked slightly for performance. Details of the tweaks below...
So here we go...
FroydVillain 1.6.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That linpack is after a day's heavy use, no reboots, on 576 MHz stock, interactive governor. No taskillers or other cheating took place
NOTES:
Nothing much, but let's proclaim the glory of CyanogenMod again Thanks guys.
INSTRUCTIONS:
1. Boot into recovery
2. Nandroid backup
3. FULL DATA WIPE AND DALVIK WIPE. EXT WIPE OPTIONAL, BUT HELPS
4. Flash the ROM
5. Reboot. At setup screen, give it time to complete optimisation after boot... Should settle down in about 5 minutes, more if you didn't wipe EXT.
Your download link:
http://www.villainrom.co.uk/forum/showthread.php?3458-FroydVillain-1.6.0-Released!
2799be21d3a5ae24d1e92b25edf8464d FroydVillain-1.6.0-signed.zip
Join us on irc for banter (chat.freenode.net : 6667 - #villainrom) for support!
We hope you enjoy the ROM!
Finally, kernel tweaks. This is not important to anybody except developers. There's nothing to flash or look at here, it's all "geeky" stuff
Base kernel (cheers, Erasmux, and big props) https://github.com/erasmux/hero-2.6.29-flykernel/tree/flykernel-11c
Modified CPU table:
Code:
static struct cpufreq_frequency_table msm72xx_freq_table[] = {
#if defined(CONFIG_TURBO_MODE)
{ 0, 19200 },
{ 1, 176000 },
{ 2, 352000 },
{ 3, 576000 },
{ 4, 652800 },
{ 5, 691200 },
{ 6, 710400 },
{ 7, 748800 },
{ 8, CPUFREQ_TABLE_END },
Touchscreen driver fix from https://github.com/Ninpo/kernel-hero/blob/master-oc/drivers/input/touchscreen/synaptics_i2c_rmi.c added
To repeat myself, this table and touchscreen fix is not important to anybody except developers. There's nothing to flash or look at here, it's all "geeky" stuff for GPL code sharing with any other dev (Erasmux might want to look at changes we made to his work, or anyone else for that matter)
FroydVillain 1.6.1 Beta Patch
OK. Got a little update folks. It's beta, as I've not tested it for the usual number of hours, but it's been tested by sadape and a few other folk on IRC
http://www.villainrom.co.uk/forum/showthread.php?3515-FroydVillain-1.6.1-Beta-Patch-Released is the update, flash over the top of the current install.
Should fix
- lack of swipe to remove notification (for some people)
- issue a couple of folk reported with CPUSpeed not actually setting anything
- maybe other things that I've forgotten about
Not too major an update, no wipe required.
FroydVillain 1.6.2 Beta Patch
Thanks go to MATTYYEY for this little update to the Youtube app, talkback service, and terminal app.
Get it here: Clicky
After installing, YOU MUST CLEAR YOUTUBE APPLICATION CACHE FROM SETTINGS MENU!
Recommended Settings:
Disable google backup AND restore from privacy menu
Use interactive governor in normal mode, conservative in sleep.
Don't massively overclock, it's fast at 576 Higher is EVEN faster
More to be added later
Welcome back, we have missed TeamVillain.
Welcome back! excited on re-flashing my hero after few months of waiting... i think this will be the one Mad props to you pulser!
Thats to bad, I was hoping the next release would be a froyo Sense rom.
I guess I have to wait a bit longer.
You still did a great job on this one!
You guy reincarnated my Hero, thanks for that!
Great!
downloading.......
Nice to see your back, downloading now!!!!
Testing tight now
WHAAT??? AWESOME TO HAVE YOU BACK GUYS! sry for caps btw
This is exciting, first impression...
Very fast!, apps open the moment u touch them
yeh yeh yeh, this is what I'm waiting for long time
Thanks a lot
A bit early to be making big claims yet, but this ROM feels really fast, and runs incredibly smooth. If the performance holds then I am a very happy camper.
Pulser cheers mate.
great rom but the dialer ruins it
there isnt any dialer nearly as fast and as smooth as the htc dialer
too bad
ray dialer is the fastest but doesnt come near to the htc ialer
downloading and flashing, hopefully there are no more problem with display percentage and bad battery life as in FV1.5.0
good work for Team Villain.
Wow... pulser, dude, you did this eh? I simply MUST try this on for size
Sent from my HTC Hero using Tapatalk
thankyou
Villain Team My Hero in My HTC Hero Welcome back..
pulser_g2 said:
Touchscreen driver fix from https://github.com/Ninpo/kernel-hero/blob/master-oc/drivers/input/touchscreen/synaptics_i2c_rmi.c added
Click to expand...
Click to collapse
Whats the problem with the original touchscreen driver?
is this bettert than standard cmod? im running 6.1 rc1 or whatever the newest rc1 is, which runs very smooth! most the time
also can i use themes from that rom? or do they not work on here?
i hate the theme youve used but like flashing things so would like to give it ago until (fingers crossed) a 2.2 sense appears
Great stuff. Looking forward to checking this out.
erasmux said:
Whats the problem with the original touchscreen driver?
Click to expand...
Click to collapse
Thats what im wondering aswell, I like to know the big advantages of this rom, before flashing it.
Anyone know a big diff betwien this or Floyo / CM6.1??
And don't say its from the villainteam
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM WILL NEVER BE THEMED, THERE ARE TOO MANY OUT THERE THAT ARE AND EASY TO ADD TO THIS ROM IF YOU LIKE THOSE THEMES I PREFER STOCK, THIS ROM WILL BE UPDATED ONLY TO INCLUDE NEW FEATURES, IT WILL BE OPTIMIZED. I ASSUME YOU BOUGHT THIS PHONE FOR PURE GOOGLE EXPERIENCE AND THAT IS HOW IT WILL STAY.
First get ROOT HERE
This is a ROM i put together, it is stock, zipaligned, deodexed with the battery fix that displays proper battery charging status. Included is netarchy's kernal 1.3.2 CFS. This was taken from stock rom so everything works. This rom is voodoo supported and all features work flawlessly.
THANK YOU TO NETARCHY FOR HIS KERNAL, COMBINED WITH THIS ROM GETS A QUADRANT OF 3103 WHEN OC'D TO 1.3 smartass
Make sure to wipe all, including delvik, cache, and data. Flash and enjoy. Also i get the best results when i set setcpu to 200 min and 1.3 max.
V_1 http://www.4shared.com/file/ZTt2qKd7/Gerbal_ROM.html?
***Just a word of advice, i seem to get no performance boost going from oc'd 1.3 to 1.4, i think it affects the governor in a bad way.
I have parted with my Nexus S 4G due to connection, reception, issues that I couldn't wait for sprint or Google or Samsung to address. I will update this rom with tweaks and such but the base will not but updated as i have returned to the Evo forums.
Updated the bootanimation in the rom..you will have to redownload and flash for it to take affect or download the bootanimation and flash via adb to /system/media
I'm getting the Nexus S 4G tomorrow and will be giving this a try. I'm coming from the Evo and I hope the Nexus 4G gets just as much love from developers as the EVO did. I doubt it, but thanks kpkimmel for the Rom. Like I said I will be flashing soon!
So how does the battery tweak work? I understand the 93% full charge is a safety feature. Does the tweak offset the numbers?
Yes, it offsets, so it should show 100%
Updated adfree to current host.
When you have a chance mind posting some screen shots? Thanks
Very nice, smooth and fast. I've been trying just about everything that's been coming out for the NS4G and this is one of the best. Thanks.
dragondagger55555 said:
When you have a chance mind posting some screen shots? Thanks
Click to expand...
Click to collapse
No need dude, its stock gingerbread, i didnt' theme it in anyway. Its themeable if you would like you can check out the forums as some member have begun creating themes.
EDIT: Uploaded some for your eye candy.
will give this a shot tonight
These pictures are kind of blury, is that a battery percentage inside the battery up top?
Sent from my Nexus S 4G
dkotoric said:
These pictures are kind of blury, is that a battery percentage inside the battery up top?
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes it is, saw it on another rom and like it. Part of battery tweak.
I like this ROM, did a few adjustments with setCPU (posted a thread in General with my slightly modified advanced settings) and my battery is doing well. Haven't had this phone for more than 5 days, but noticed better results than other roms.
Clean, quick, and a job well done. Thanks!
itsallsubliminal said:
I like this ROM, did a few adjustments with setCPU (posted a thread in General with my slightly modified advanced settings) and my battery is doing well. Haven't had this phone for more than 5 days, but noticed better results than other roms.
Clean, quick, and a job well done. Thanks!
Click to expand...
Click to collapse
Any lag while screen off and turning back on after period of time? On NS4G I ran into issues randomly with screen turning on I would have little or huge amounts of lag... Tried several kernels and nothing helped... Keep having same issues. Running with ADW EX. Any suggestions on launcher besides stock?
tandxcstar1 said:
Any lag while screen off and turning back on after period of time? On NS4G I ran into issues randomly with screen turning on I would have little or huge amounts of lag... Tried several kernels and nothing helped... Keep having same issues. Running with ADW EX. Any suggestions on launcher besides stock?
Click to expand...
Click to collapse
No lag, maybe adw, not sure how compatible it is with gingerbread, havn't looked into it much.
tandxcstar1 said:
Any lag while screen off and turning back on after period of time? On NS4G I ran into issues randomly with screen turning on I would have little or huge amounts of lag... Tried several kernels and nothing helped... Keep having same issues. Running with ADW EX. Any suggestions on launcher besides stock?
Click to expand...
Click to collapse
I use Launcher Pro Plus, no issues at all. and in setcpu i have only one profile setup, its screen off max:400 min:100... any lower than 400 the screen doesn't turn back on.
same kernal included in rom (net's 1.3.2)
if you are having issues, try reverting to netarchy's stable release
i believe a BFS kernal is supposed to rid lag and latency, i dunno, i just use CFS, i feel its better on battery
itsallsubliminal said:
if you are having issues, try reverting to netarchy's stable release
i believe a BFS kernal is supposed to rid lag and latency, i dunno, i just use CFS, i feel its better on battery
Click to expand...
Click to collapse
CFS is better on bat, i havn't had any issues with the kernal provided but if you do have problems you can simply flash an alt. kernal.
thx for the quick response ev1. Ya I have tried the stable and beta builds and so far 1.3.2 CFS works the best on my phone. But any kernel I use I have lag from time to time.. I am starting to think its ADW EX issue now... FML I love it too.. Oh well I will try another and test out. But about to flash this ROM now to check it out. Thx again ev1 AND thank you for the work you contribute to the XDA community!! Much props.
Is there any way i can use the battery mod with stock rom? I'd flash this rom but i wanna stick with stock for a little longer since i just bought this phone.
Right now I'm running FXP054 with the kernel OC'd to 1.4GHz. I also have cut down on a lot of running services in the background through the Autostarts app [ https://market.android.com/details?id=com.elsdoerfer.android.autostarts ].
What would be the best governor, I/O scheduler, & OC for the CM7.2.0 CDMA kernel?
What build.prop settings should I apply to get the most out of 3D gaming?
Any other options/settings/apps that I should be aware of for better gaming performance in general on my Xperia Play?
I'd greatly appreciate any insight. Thanks.
Download the Ram Manager pro app from the market. Use the default balance option when not gaming and use the hard gaming option when gaming.
I've tried all tweaks and zips and governors and everything possible. This application has made the biggest difference so far. Especially the lock home launcher option.
How much of a difference between that & the v6 Supercharged script in terms of performance?
CrimsonSentinel13 said:
How much of a difference between that & the v6 Supercharged script in terms of performance?
Click to expand...
Click to collapse
Night and day. It's very difficult to give empirical evidence, so metaphors are about the best you'll get from me
V6 supercharger had zero to little effect overall. It did lock the launcher SOMETIMES, but other than that had very little effect on performance.
Ram manager pro is giving me a lot of performance and the different profiles are very clear and understandable. Unlike the vague and ambiguous settings on the supercharger.
I'll have to try that app out. How well does it do with Gameloft games? I tried Asphalt 6 last night & it ran well for a while until it decided to slow to a crawl on screen. I'm aiming to get a consistent gaming experience regardless of 2D or 3D.
3dawg said:
Download the Ram Manager pro app from the market. Use the default balance option when not gaming and use the hard gaming option when gaming.
I've tried all tweaks and zips and governors and everything possible. This application has made the biggest difference so far. Especially the lock home launcher option.
Click to expand...
Click to collapse
That app actually doess nothing at all for the launcher.
Its the grouping shift without changing a single priority.
Its all about aggressive task killing without user input and that's it.
Use Update 9 RC4 as it has more options for high ram devices and makes recommendations based on ram.
Sounds like you used Update 8.
zeppelinrox said:
That app actually doess nothing at all for the launcher.
Its the grouping shift without changing a single priority.
Its all about aggressive task killing without user input and that's it.
Use Update 9 RC4 as it has more options for high ram devices and makes recommendations based on ram.
Sounds like you used Update 8.
Click to expand...
Click to collapse
Thanks for the insight.
You're welcome
I really dislike it that people are being mislead into believing that it actually does something for the launcher.
zeppelinrox said:
You're welcome
I really dislike it that people are being mislead into believing that it actually does something for the launcher.
Click to expand...
Click to collapse
I did indeed use update 8. I will give the latest a try.
You say it does nothing for the launcher but I'm seeing some fantastic results i.e the launcher literally never dies.
It had to redraw once after playing modern combat 3, and the whole phone slowed to a crawl unexpectedly for 10 seconds and then back to normal. Other than that the application has been great.
Using the script, the launcher died regardless of which setting I chose even when it said I had a "hard to kill" launcher or whatever. It would work for a while but redraws were too common. Also, all tutorials seemed based around motorola phones so I had difficulty finding what options would suit mine the best.
Regardless, I'm grateful for fantastic devs like you, and this script is undeniably innovative. Expect a donation at the end of the month
EDIT:
IGNORE EVERYTHING I SAID EARLIER, HOLY CRAP UPDATE 9 RC4 IS DAMN GOOD.
Seriously, I uninstalled Ram Manager pro, it's totally unnecessary.
Supercharger update 9 RC4 using option 6 has been flawless for me.
ah yes U9 is much improved.
If you can spare the ram, just bulletproof the sucker
zeppelinrox said:
ah yes U9 is much improved.
If you can spare the ram, just bulletproof the sucker
Click to expand...
Click to collapse
What apps should be bullet-proofed? I'm using script for the purpose of getting better gaming performance.
I just uploaded an RC5 test so try that
I meant the launcher... so if you eve get any redraw, pick bulletproof launcher so it can't be killed but then again if you don't have enough ram to load big games then the default die hard launcher is good enough... it should still almost never happen.
zeppelinrox said:
I just uploaded an RC5 test so try that
I meant the launcher... so if you eve get any redraw, pick bulletproof launcher so it can't be killed but then again if you don't have enough ram to load big games then the default die hard launcher is good enough... it should still almost never happen.
Click to expand...
Click to collapse
Where do you have the RC5 sh located at? I checked your beta page for it & don't see it.
Ah.. it's on the last page of the thread... I plan on having a newer one up soon so I uploaded it for a little bit of testing but it's really solid as is
zeppelinrox said:
Ah.. it's on the last page of the thread... I plan on having a newer one up soon so I uploaded it for a little bit of testing but it's really solid as is
Click to expand...
Click to collapse
I started using RC5-test last night. It works really well. I noticed that it now has the Cust-OOM calc settings, which I'll apply tonight & see how it runs.
I really like how well done it is. I'll have to test out a few games this week.
Thamks
If you go to custOOMizer it will ask if you want to load the calculated values so that you only have to say yes or no lol
zeppelinrox said:
Thamks
If you go to custOOMizer it will ask if you want to load the calculated values so that you only have to say yes or no lol
Click to expand...
Click to collapse
Even easier, I was thinking I would have to record the values & make sure I got it right.
Hi Zeppelin!
I would to test now Update 9 RC5. What ins the best Option for Play. On Update 8 i use Option 6 or 9 (MegaRam 2) but 6 feels smoother in the Launcher & UI.
Gesendet von meinem R800i mit Tapatalk
Test the calculated values as they are based on your actual ram.
I added that feature for device that fell between the HP group settings.
I tried to calculate balanced values but course you can tweak them to be more or less aggressive by playing with the slot 3 value as that has the biggest effect on typical free ram.
The other great addition is the auto calculated min_free_kbytes value so that you won't ever get too low on free ram while allowing for apps to be cached for speed.
Thanks for answer. I now use Option 10 Custom Settings on U9 RC5. Launcher is Die Hard.
Here a Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you Update the Supercharger to final U9 must i Run this or is RC5 okay?
Gesendet von meinem R800i mit Tapatalk