Is it possible for me to install the VillianROM on my HTC Droid Eris or am I going to brick my phone?
are you rooted?
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
droidkevlar said:
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
Click to expand...
Click to collapse
I'm pretty sure its a g2/hero Rom.
droidkevlar said:
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
Click to expand...
Click to collapse
Evil Eris = Ported Villian Rom ;P
1. I am rooted and running:
- Eris_Official 0.81T2
- Senseless patch
- Nexus One patch
- Nexus Launcher w/LWPs
It's nice, but more laggy than I'd like. Is Evil Eris really the ported VillianRom?
After downloading SetCPU, I've been able to set my processor at a higher normal frequency and am experiencing better performance.
Turnyface said:
After downloading SetCPU, I've been able to set my processor at a higher normal frequency and am experiencing better performance.
Click to expand...
Click to collapse
what settings are you using?
droidfreak said:
what settings are you using?
Click to expand...
Click to collapse
I'm utilizing different profiles.
Normal:
Max = 528 mhz
Min = 245 mhz
Sleep/Standby
Max = 245 mhz
Min = 160 mhz
Battery temp > 50 C
Max = 160 mhz
Min = 160 mhz
Someone told me to do this because we actually can't overclock yet:
...fire up a adb shell and do a cat /proc/cpuinfo while it's over clocked were just curious to see if the program is in fact over clocking the cpu
Click to expand...
Click to collapse
when I did that, it came up with 526 which is not overclocking... funny thing was when I used a different profile to slow it down, it still said 526...
The highest frequency the Eris can attain at this time is 528 mhz. We're not overclocking, just simply setting the running frequency to a constant number. I don't think you're going to see a difference between 528 and 526. 2 mhz is such a minute amount.
right it is minute, but my point was that 528 is what the eris can do... but maybe youre right that set cpu keeps it at a constant... set it lower and run what I said and it probably still will say the 528... thats what I did not understand and never got an answer... it did not seem as though setcpu had throttled it back at all... I saved the app though waiting til we can get over 528..
Turnyface said:
1. I am rooted and running:
- Eris_Official 0.81T2
- Senseless patch
- Nexus One patch
- Nexus Launcher w/LWPs
It's nice, but more laggy than I'd like. Is Evil Eris really the ported VillianRom?
Click to expand...
Click to collapse
I'm runnning that exact same config, and I haven't noticed any lag.
It has been getting better as the night has gone on. The one issues I'm consistently having is the Nexus One Launcher force closes from time to time, making my phone useless and forcing me to pull the battery and start again. Maybe I'm doing something wrong?
Framework43 said:
Evil Eris = Ported Villian Rom ;P
Click to expand...
Click to collapse
really?
they dont act the same.
i have a friend who has the Villian Rom and well u kno i ran the Evil Eris and it was seemingly 2 totally different devices. even tho u say its the same thing?
Related
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
hopoffbaby said:
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
Click to expand...
Click to collapse
It's as simple as; some phones simply can't handle higher MHz
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
hopoffbaby said:
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
Click to expand...
Click to collapse
It will probably freeze but there are kernels the isn't overclocked that high by default
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
hopoffbaby said:
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
Click to expand...
Click to collapse
Yes. Many ROMs aren't set to the highest available clock speed by default because there are phones like yours that can't handle it
Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
I run 768 with no problems.
SikYou said:
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 are you ****ting me?... is it set to performance?
Notxok said:
806 are you ****ting me?... is it set to performance?
Click to expand...
Click to collapse
Interactive
Sent from my nonsensikal froyo
Hmmm. I'm trying 806 now.
SikYou said:
Interactive
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Hungry Man said:
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Click to expand...
Click to collapse
Your 486 Makes me Envious.. Would you mind PMing m your set-up ( ROM Set CPU info and current task killer? )
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Hungry Man said:
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Click to expand...
Click to collapse
I don't get above a 415-420 really.. any suggestions or help?
Notxok said:
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
Click to expand...
Click to collapse
806 seems to be running a fraction faster but to me it is hardly noticeable coming from 768.
Notxok said:
I don't get above a 415-420 really.. any suggestions or help?
Click to expand...
Click to collapse
Don't read too much in the benchmarks . I usually run happily around 430.
I use SetCPU (interactive 768 / 245)
I don't run any task killers, in my experience they are more trouble than they are worth.
The other thing IMHO if you don't use an app, get rid of it.
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Hungry Man said:
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Click to expand...
Click to collapse
Thanks Guys... Ill keep that in mind.. I was using auto memory killer
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
In my personal experience, I would disable set on boot in SetCPU and start gradually bumping the speed up. Usually at 787 my phone runs best (fastest and most stable). Then, I'd go back and bump it to 806. It WOULD run but after about 5 minutes of playing with my phone it typically causes it to lock. 825 Causes an immediate lock. So I typically leave it at 787 and all Froyo roms seem to run fine at that for me. I don't even test anymore...just restore SetCPU app and data with Titanium on initial boot of a new rom. So far, no problems.
Sent from my ERIS using XDA App
What's the best setting? Ondemand? Interactive? Prefermance..etc
Sent from my VANILLA TAZZ using XDA App
806 no problem using the Collins script.
Anything higher than 710 on my phone locks it up.
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
i think you have to wait for the source code for the kernal to be released and tinkered with to get anything useful from all that...but who knows
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Odinist said:
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Click to expand...
Click to collapse
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
SuperFly03 said:
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
Click to expand...
Click to collapse
pretty much what I did, minus everything but the screen off
I always set the screen off on my evo 4g to 245 max, and will probably do the same here. Kinda waiting for kernal source code to be released so I can use the smartass governor. I always liked that one.
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
I cannot wait to tinker once HTC releases the kernel source!
mthorn79 said:
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
Click to expand...
Click to collapse
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
nosympathy said:
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
Click to expand...
Click to collapse
Ok I'm not an idiot, I know quadrant scores don't mean anything but some people use it as a gauge to get an idea on how their phone is. (If u feel it does nothing for you then don't use it if u don't want to no one asked you to)
If you know anything about phones you know certain people's will vary in speeds, I'm just posting my experience...this IS afterall a "Post Your SetCPU Settings' thread, so don't be getting all uppity.
Sent from my ADR6400L using Tapatalk
Jimmy058910 said:
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
Click to expand...
Click to collapse
Yes. I think they releases it within 45 days or something like that. It will most certainly be here soon.
Sent from my ADR6400L using Tapatalk
Any incoming call issues with Screen Off set at 245?
Steeler86 said:
Any incoming call issues with Screen Off set at 245?
Click to expand...
Click to collapse
no and their shouldn't be, unless you down the road, since you couldn't do it now, use one of the governors like Conservative which tend to really slow the phone down. On my Evo 4G it used to take a good 30 seconds to unlock the screen is I used that with screen off at 245Mhz.
1570 for me on stock rom.
I got 2000+ quadrants on stock ROM. SA for setCPU, I can't get my CPU to clock down by force with any app. I think the kernel source is going to be needed. Probably have perflock on like they did on my inc. Let me know if setCPU works please.
SetCPU works, you just have to hit the menu button and click "disable perflock"
1376 on VirusRom but it is soooo snapppy
Seems to be working for me. 39% battery after 12+ hours. Just with the "screen off: max245" setting.
Sent from my ADR6400L using XDA App
We finally got the source code!
Do I need to flash this to overclock
http://forum.xda-developers.com/showthread.php?t=1016916
or can I wait for SetCPU to update?
Since detule has pushed in patches that require an app to overclock now instead of inserting the appropriate lines in the startup.txt file, I am looking to get a better understanding of what exactly the line in the startup.txt file did and how to achieve similar settings in an app like setCPU.
I have setCPU, and set it up to run the default program at 710MHz both the Max and the Min. I am not really interested in battery saving features of the program or anything else. I just want it to run at 710MHz all the time. I thought it pretty much did this when using the startup.txt command set to 710400.
My question is, am I correct that if I set it up setCPU that way is that mirroring what the command did or am I going to get worse battery life then I did before because the app does something different?
I know the phone still sleeps with the app set that way. What happens in sleep with both the startup.txt command or this app? Does Android knock the processor down when going into sleep by either method or both?
Shifting only the MAX to a desired frequency achieves the same as using, what used to be, the command line method and specifying oc_freq_khz.
Shifting the MIN to match MAX will result in poorer battery life, though your phone will run constantly at the desired frequency.
When going into suspend, the driver first down-shifts the clocking frequency and then powers down ARM11 completely regardless of the OC settings.
detule said:
Shifting only the MAX to a desired frequency achieves the same as using, what used to be, the command line method and specifying oc_freq_khz.
Shifting the MIN to match MAX will result in poorer battery life, though your phone will run constantly at the desired frequency.
When going into suspend, the driver first down-shifts the clocking frequency and then powers down ARM11 completely regardless of the OC settings.
Click to expand...
Click to collapse
So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower? I have the minimum set down to 245MHz now, hopefully I won't see too much lag with that.
slickdaddy96 said:
So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower?
Click to expand...
Click to collapse
It would down-shift to 245, unless under load.
slickdaddy96 said:
So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower? I have the minimum set down to 245MHz now, hopefully I won't see too much lag with that.
Click to expand...
Click to collapse
You probably won't. The chip just goes to 245 if it is just idling. Under load, it'll snap back up to your desired frequency. It is kinda like the i7 2600K when in Turbo Core mode. It'll drop to 1.6 gh/z when doing nothing, then snap up to whatever it is set for when under load.
My settings are 787max and 122 min (This is ACL's OMGB NAND, but it'll probably be similar) and I don't notice lag in comparison to just leaving it at 787.
i need something to speed this thing up a little.... my electrify broke
moparfreak426 said:
my electrify broke
Click to expand...
Click to collapse
um, what?
wizardknight said:
um, what?
Click to expand...
Click to collapse
My rebadged motorola photon(electrify broke) and kind of had to switch back this touch pro 2 (rhod500)
Sent from my MSM using XDA
moparfreak426 said:
My rebadged motorola photon(electrify broke) and kind of had to switch back this touch pro 2 (rhod500)
Sent from my MSM using XDA
Click to expand...
Click to collapse
If you are using kernel 3.3.6 just grab your favorite overclocking tool from the market. If not, go to the thread for the rom you are using and ask for help.
wizardknight said:
If you are using kernel 3.3.6 just grab your favorite overclocking tool from the market. If not, go to the thread for the rom you are using and ask for help.
Click to expand...
Click to collapse
2.67.96 I think..... need to look for kernal 3.3.6
Sent from my MSM using XDA