Hi,
I'd like to start off saying I'm a newbie...
I originally thought it was a requirement to root you HTC Hero phone to get andriod 2.1, and I did root it I got Villain 12.
I later discovered you can update without rooting, to the offical firmware, now I have two heros (one is my bro's).
I was doing a comparison his has offical 2.1, mine has Villain 12, I can't really see much difference between the Official & Villain 12, other than Villain 12 takes about 55 seconds longer to boot up. So as far as that goes, that's a serious downgrade to the official version. Many people say it's faster and better, but my tests show that its much slower to boot and the same while using apps etc.
I was wondering if there was actually any benefits to the custom rom...
Also I was wondering how to unroot the phone, just incase I need to return under warranty etc...
Well with a rooted phone you can overclock your phone via Overclock Widget(Market) or SetCPU (search XDA to get it for free and put it on your sd card and download Astro Filemanage to install it) I use Cronos Droid 2.1.2 so I cannot speak for VillainROM 12. The phone does take a bit longer to boot up but I find it worth it because I can flash themes, change my bootanimation and do other crap such as try new kernels or try out experimental ROMS (basically any 2.2 Froyo ROM), so it is a matter of opinion if root is worth it. Also a simple search and there are threads stating the pros and cons of rooting
::EDIT::
Forgot rooted phones get app2sd (saves space on your phone so you can have more apps)
I would love to know the official 2.1 boot time. For a comparison to other boot times. FYI if VillainROM is taking 55 seconds longer to boot that would mean that the official boots in about 15 seconds (based upon my results). So my thinking is that something went wrong with your VillainROM install (for whatever reason). I would recommend wiping everything and reinstalling VillainROM or another ROM and seeing if you get the performance improvements that I am seeing in almost all rom's.
GPU Benchmarks
CPU/Boot time Benchmarks
If i remember correctly the official 2.1 took about 1:50-2:00 to boot up. Villainrom12 took 1:20, and Kimera2.1 takes 1:00 (very impressive)
Not as impressive as Chocolate Eclair 1.0 which takes about 50 seconds to load IIRC.
Related
I have my Sprint Mogul, and Sprint service, and i am currently running the 2.16 ROM. I am deciding whether or not to upgrade to a custom ROM (if so which one) or to just do the update to the new stock ROM 2.17, or even to just wait for the new ROM with GPS and EVDO REV.A. So if someone could please help me in deciding cause I really don't know which one has more benefits. I want it to be able to run fast, with good RAM, but also to run well with my Sprint service, cause ive been looking at the custom roms and i see that some of them don't work to well with sprint. So to sum it all up, which is better, a custom Rom for my Sprint Mogul, with sprint service, or the stock 2.17 Rom, which I know will work with my sprint service well because it was made for it. Thanks
A custom rom if a good one like dcd's newest rom then it will be fine since it is based off of the sprint rom anyway and will just allow you to choose what you want to install but it is all up to your preference. If you don't like it you can always flash back can't hurt to try right i personally would never use stock rom again since dcd's actually works with sprint better ex no glitches
mastachillz said:
A custom rom if a good one like dcd's newest rom then it will be fine since it is based off of the sprint rom anyway and will just allow you to choose what you want to install but it is all up to your preference. If you don't like it you can always flash back can't hurt to try right i personally would never use stock rom again since dcd's actually works with sprint better ex no glitches
Click to expand...
Click to collapse
x2. The new DCD 1.6.7 is the best ROM I've run yet. You'll be pleased.
Does it fix the memory leak problem that is with the stocks? and does everything like MMS and Internet, and all the other sprint service based stuff work? and lastly about how much faster is it and how much free ram do you have? Thanks for all the help.
Memory leak is still present from my experience.
So how is it running better than the stock ROM (newest 2.17)? Is it alot faster? since for me, the only problem with my phone is the memory leak, other than that, it barley ever freezes or locks up, and i only soft reset it about once a week, just to get my memory back (although the device would be running fine without soft reseting, I just like doing it). I just want to know, if it would be worth it for me to have to reinstall all my programs and settings, for a ROM that is not that different. Thanks
also on stock rom right now. kinda scared to do the do the custom rom but I will this friday. I will let u know if the 5 meg page pool speeds it up nutz on chin style. my biggest issue right now is when I click to write a text message. the text message compose screen takes forever to load. a good 5 to 10 seconds. and when I press the msg button at top of phone. that also takes forever and I bout done with it
Definitely get off of 2.16, it was horrible. My phone has been a LOT more stable on 2.17.
And, the "memory leak" isn't really a memory leak, it's a feature. I've seen this repeated over and over again. It's caching to make the system feel faster. It only becomes a problem if you actually run out of memory.
Either these roms are very easy to update or I'm missing something.
I read through the Kitchen thread and the Rom thread for dcd. Very interesting thread although i could not find any form of instructions. I searched instructions and it provided a link to the unlocker.
So I'm guess you run the hard spl unlocker and then the dcd rom update and its that easy?
calisoldier83 said:
So I'm guess you run the hard spl unlocker and then the dcd rom update and its that easy?
Click to expand...
Click to collapse
yes
eventually i will get instructions up..sorry
Well I have tried a few custom roms, made a few with the kitchen, and of coarse used the stock rom. I now find myself falling back on the stock rom because I feel it is the most stable for my use. I would recommend using a backup such as spb or something. That way if you ever jack up your mogul you can just do a hard reset and then restore it to how it was from the last backup. I really like what people have done with the custom roms, but I have just had a few minor issues that I do not have with the stock rom. Chad
By stock ROM, I am assuming you are using 2.17 right?
Title says it all. Will putting one of the froyo based ROMS on my phone get rid of the dreaded silent bug? I am currently running 2.1 with aloysius v12 and I get it pretty often.
I don't believe that there is anyway to be able to tell that just from which rom you run as everyone's phone is different. With that in mind though, the good thing about being rooted is that you can do a Nandroid backup, then flash another rom and see if it works out for you. If it doesn't, then you've only lost a bit of time with playing around with the new system. If you don't like it, then restoring your phone only takes a couple more minutes, then you'll know for certain. Good luck!
try a rom without sense. on the regular v3 leak i was getting the silent bug constantly, but after rooting and installing xtrrom(highly recommended) i have yet to get it
Hi,
I am currently using a Vibrant USA and I am running Bi-Winning v3 with the bullet kernel1.48ghz but i keep it at 1.27 max when I'm using it for most applications. I have been getting about a full 12 hour day out of a single charge while using Juice Defender ultimate.
First and Foremost I apologize if this question has been answered already, I did use all of the search tools described in the noob video
I have no complaints about Bi-Winning, I came from project-V and I have found both roms great and beautifully designed (with the trigger theme)
For my computer I am using a 27" Imac 2010 (osx 10.6.5 with current update) model with 8 gigs of ram and a core i7 processor. I recently found a program called the Winebottler. I was able to use this program to turn Odin into an Application that Mac osx can run. I am very intriuged by MIUI and CM7 as well as other roms such as Revolution rc1 however without knowing that odin will run properly I cannot try them. If odin messes up my phone install because Im not on windows then I could have corupt files that I could for that same reson not fix via Odin.
I was wondering if anyone has both operating systems or is a mac user with expierience in this issue. I have tried everything I have seen in other XDA formums telling me to use something like bootcamp or a disk partition (on my mac for dual os) but after several attempts I have not been able to get it to work at all. I would really appreciate any replies that might help me.
I was also wondering if the advantages in 2.3 would be noticable to someone who uses the phone for calls,sms,web browsing,video playback, verry little gaming(ocassional basic game like paper toss). I was also wondering if any of the 2.3 roms were fully working for everything but gps as I have a garmin for that.
One more thing, I once tried using rom manager to download and run miui 1.6.10 from project v but it gave me a hardware lock/rebootcycle wouldnt pass the vibrant samsung screen and no recovery or download mode was available. I know that It was totally my bad but that is my one expierience with flashing non edt roms.
have you tried heimdall it is a less buggy odin and it is for mac too...here is the link http://forum.xda-developers.com/showthread.php?t=755265
thanks button if i helped
Yes, try Heimdall. I think it's the only native app that will work on OSX. I use it when I'm booted into Linux too.
Thank you
Thank you for the very quick response, I am installing Heimdall as we speak Hopefully i'll be on gingerbread by morning
just be sure to follow all the instructions properly on any 2.3.4 install and you should have no need for heim/odin. of course theres always a chance of a random error. but once you get the cm7 initial kernel flashed youcan factory reset reflash from that. haven't had to odin back to stock and i've flashed cm7/miui and even tried the honeycomb 3.0 alpha rom. that was interesting. just take your time play it safe and go slow
as far as benefits go the aethetics alone to Me are worth the update to gingerbread. though i'm a pretty devout Miui fan the theming engine is gorgeous and the styles are slick.
Stability wise miui is good.
CM7 is... getting better
the Sgs II clone roms all feel solid and fast
and simply Honey is one many would swear by though i personally have yet to try it (really stuck on miui lol)
my recommendation get a few, try miui, simply honey and the sgs II clone (CM7 while awesome is still far from an excellent daily driver IMO) just flash one give it a whirl, titanium backup all your apps (not data) enter recovery factory reset, format system, cache, data, and datadata and flash the next one (fix permissions), rinse repeat till you find the one for you. No need to odin inbetween flashes. also rom manager when you enter it before using it to fix permissions set it up as 3.x to follow with teh version of clockwork recovery your using.
Simply Honey
http://forum.xda-developers.com/showthread.php?t=1021383
Miui
OC - http://forum.xda-developers.com/showthread.php?t=1099533
Standard - http://forum.xda-developers.com/showthread.php?t=1123922
SGS II Clones (take your pick both have excellent ratings)
Hybrid - http://forum.xda-developers.com/showthread.php?t=1124734
Revolution - http://forum.xda-developers.com/showthread.php?t=1131782
Bootloaders (careful with these read ALL fine print)
http://forum.xda-developers.com/showthread.php?t=1117990
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
I am writing to report that I am having trouble with the jockersax 3.3 beta. This is the first time that I have had a problem loading either one of the jockersax
CM 9 roms I hope this is of help. What I had to do was flash it twice going through fastboot into Android Recovery.
Any other ROMs tested after you failed with 3.3?
I'm starting to wonder if it's possible to burn out flash memory used for ROM.
My own Atrix works pretty well with 3.3.
I'd like to know how many times it's safe to flash a new ROM with respect to memory life?
flashed it once
flashed ver 0.3.3 only once and flashed gapps no issue.
even flashed 1.45 kernel
in the past had alternated between cm7 & cm9 without any issues. haven't gone back to CM7 ever since jokersax released 0.3
I have been using both turl's and jockersax's Kanged CM9s both work well but I have not been able to get the video to work which I use at times where I work. As I posted flashing jockersax 3.3 beta was the first time I had any issues with flashing a rom on my Atrix 4G, but it was a good learning experience as I learned how to use fastboot to navigate into Clockworkmod Recovery. Second on the issue of life span for memory I belive that pc solid state drives are supposed to be able to do over a hundred thousand rewrites so I would guess that you would buy a new phone before the memory was degraded. One thing I don't understand is why everything is not on removable media that way if you had a problem you could just flash onto a new chip and install, that is how the Raspberry Pi is and I don't see why it could not work for phones. But the truth is probable that it would work but then the "Providers" would have less control over us.