Develop Bugs

[Q] Just un-rooted my EVO to apply 3.29 update... WHY ROOT NOW?

I feel bad but I just un-rooted my regaw_leinad rooted EVO using djR3Z method so I could apply the new update. I know there were other ways of doing it but it just seemed the more sensible way for a noob. I really wanted to root to get rid of that FPS cap anyways. I didn't do one single thing to my EVO while rooted besides download a screengrabber app that I didn't even use... I am still learning all about what is possible with root on Android, and until I find something totally mind blowing I think I'll keep stock.
Can anyone give me any reasons why I should have root besides custom roms??? I love the idea but not the headaches it gives me...
And, if custom roms are the big idea, what benefits will that give? Don't they run a little finicky anyways? Not all features are enabled, e.g. 4g?
Please list here.
********update12/26/10******
Just rooted again with unrEVOked 3.22 on Ubuntu 10.10.
***************************

generalExpert said:
I feel bad but I just un-rooted my regaw_leinad rooted EVO using djR3Z method so I could apply the new update. I know there were other ways of doing it but it just seemed the more sensible way for a noob. I really wanted to root to get rid of that FPS cap anyways. I didn't do one single thing to my EVO while rooted besides download a screengrabber app that I didn't even use... I am still learning all about what is possible with root on Android, and until I find something totally mind blowing I think I'll keep stock.
Can anyone give me any reasons why I should have root besides custom roms??? I love the idea but not the headaches it gives me...
And, if custom roms are the big idea, what benefits will that give? Don't they run a little finicky anyways? Not all features are enabled, e.g. 4g?
Please list here.
Click to expand...
Click to collapse
Custom ROMs are usually faster and have more features and customizations than the stock ROM. There are also tons of root-required apps that let you do crazy things to your phone like get free wireless hotspot, backup all of your apps with data and Market links, and change the apparent density of your display.

I'm somewhat of a noob and just made the switch.
WiFi tether
Remove some sprint apps
Custom boot animations
Like the above said, custom roms show a performance increase
Love the Quick Boot app
There are a bunch of threads around with more root apps you will most likely like.
Sent from my PC36100 using XDA App

General, the benefit is freedom. if you waited a litttle bit you would already be able to flash the exact same rom rooted which is readily available. http://forum.xda-developers.com/forumdisplay.php?f=653
Good luck though.

Also, rooting takes like 2 seconds now that unrEVOked Forever is out.

A rooted phone nets you more options. There's no drawback to it. Why not?

generalExpert said:
I feel bad but I just un-rooted my regaw_leinad rooted EVO using djR3Z method so I could apply the new update. I know there were other ways of doing it but it just seemed the more sensible way for a noob. I really wanted to root to get rid of that FPS cap anyways. I didn't do one single thing to my EVO while rooted besides download a screengrabber app that I didn't even use... I am still learning all about what is possible with root on Android, and until I find something totally mind blowing I think I'll keep stock.
Can anyone give me any reasons why I should have root besides custom roms??? I love the idea but not the headaches it gives me...
And, if custom roms are the big idea, what benefits will that give? Don't they run a little finicky anyways? Not all features are enabled, e.g. 4g?
Please list here.
Click to expand...
Click to collapse
Not everyone roots their phone - just the people here So, if you feel no need to root your phone, then don't.
I'm not a power user or speed freak so uncapping the fps isn't a big issue for me. I originally rooted my phone so I could use wireless tether. I'm staying rooted because I can play around with my phone a little more - change the boot animation (and turn off the sound), remove the Sprint apps that I don't use but that turn off automatically, and back up my apps and data and monitor my battery usage.
The custom roms are a quick way for me to accomplish my needs. I don't really like the Sense UI (which surprised me because I always though it was great-looking), so the roms give alternative ways to set up my phone.

Help with OTA
Hey guys. Okay I saw there is a update on xda. I'm using unrevoked3. Do I need to delete Unrevoked or just download the zip file that was released. I'm talking about about the deodexed and rooted.Im still lost on how where to put the updated file at? Please if anyone is in my boat and have had good results please tell me,im a noob,beginner,novice.
There is got to be someone who can explain in plain english lol..
Thanks everyone

Yes, I do feel crappy about it... I wish I was still rooted. I know the rooted update was available, but just thought that the OG update would run a bit better..?.. I guess I wanted to unroot to learn how among other things too. Believe it or not, doing that taught me a lot about hboot and recovery. At least I know I can always root again.
And YES, I HATE SENSE!!! But, I was reading on Cyanogen that CM6 had problems with the 4g and had a few bugs. But that vanilla android look is what I want!
Also, when non-rooted, is there no recovery? I clicked back into it just to check and it gave me a red exclamation mark over a phone...

TheBiles said:
Custom ROMs are usually faster and have more features and customizations than the stock ROM. There are also tons of root-required apps that let you do crazy things to your phone like get free wireless hotspot, backup all of your apps with data and Market links, and change the apparent density of your display.
Click to expand...
Click to collapse
Hey, thanks for the info... But along with all of the "Customness" and features aren't there also, bugs that go along with it? Like random reboots, and battery issues, and some other stuff?
Yes I love hacking stuff and know that this is all part of the fun, but I think I just need to research a little more. If you can't tell already I'm kind of paranoid about screwing things up. I rooted and really wanted to flash CM6 but didn't have the balls to. Maybe in a month or so i'll redo it.

generalExpert said:
Hey, thanks for the info... But along with all of the "Customness" and features aren't there also, bugs that go along with it? Like random reboots, and battery issues, and some other stuff?
Yes I love hacking stuff and know that this is all part of the fun, but I think I just need to research a little more. If you can't tell already I'm kind of paranoid about screwing things up. I rooted and really wanted to flash CM6 but didn't have the balls to. Maybe in a month or so i'll redo it.
Click to expand...
Click to collapse
Most of the custom ROMs are very stable and have better battery life than the stock ROM. As long as you make a nandroid backup there is ZERO risk to flashing a new ROM (assuming you don't like pull the battery out while flashing or something), so you can try one out for a few hours, and if you don't like it you can instantly go back to what you had before. Simple as pie. Give the major ones a whirl and see what you like. I know that there are some HTC ROMs themed to look like CM6 that have working 4G.

I also avoid cm6 because of the lack of 4g. Instead I use Vaelpak because it has minimal sense but enough so I can have my 4g. I'm thinking of trying Virus' mostly senseless rom.
Sent from my PC36100 using XDA App

generalExpert said:
But that vanilla android look is what I want!
Also, when non-rooted, is there no recovery? I clicked back into it just to check and it gave me a red exclamation mark over a phone...
Click to expand...
Click to collapse
When you mention the vanilla android look, what exactly are you referring to?
Is it the Vanilla theme and icons? -De-Odex roms would allow for custom themes that give the vanilla android look i.e. MrPuffin's Vanilla AOSP and Vanilla theme for Sense UI
Is it the android launcher? -Launcher Pro and ADW launcher are quite nice replacements to the Sense launcher
I'd think that if you didn't like the HTC Sense look, you would have kept root and just themed your phone to look Vanilla. Then again, it all comes down to what you believe provides the best user experience.
And regarding recovery, I believe Clockwork and Amon Ra require root.

mizzos4 said:
When you mention the vanilla android look, what exactly are you referring to?
Is it the Vanilla theme and icons? -De-Odex roms would allow for custom themes that give the vanilla android look i.e. MrPuffin's Vanilla AOSP and Vanilla theme for Sense UI
Is it the android launcher? -Launcher Pro and ADW launcher are quite nice replacements to the Sense launcher
I'd think that if you didn't like the HTC Sense look, you would have kept root and just themed your phone to look Vanilla. Then again, it all comes down to what you believe provides the best user experience.
And regarding recovery, I believe Clockwork and Amon Ra require root.
Click to expand...
Click to collapse
Yes, by Vanilla Android i'm talkin Nexus One. Those themes look pretty good though. I'm already jonsen for root again and it's only been a half day.
Launcher Pro? Doesn't that just overlay Sense and therefore cause a bit of a slow down, use more memory, and possibly more battery. (probably not noticeable though..)
Yes, Clockwork and Amon_Ra require root. I was just wondering if there was a recovery in NON-ROOTED. When I'm in a non-rooted EVO at hboot, and select Recovery I get that red Exclamation mark over the phone and have to pull the battery.
Thanks for all your help!

Whoa thr new kernel allows up to 53 fps but std is 8+... on netarchys' kernel it was about 54 - 56 with a std of 4... at least that is how it behaves on mine.
Sent from my PC36100 using Tapatalk

halorin said:
A rooted phone nets you more options. There's no drawback to it. Why not?
Click to expand...
Click to collapse
there may be security drawbacks to those that are not cautious with the apps they install.
generalExpert said:
I feel bad but I just un-rooted my <EvO>.
I really wanted to root to get rid of that FPS cap anyways.
I didn't do one single thing to my EVO while rooted besides download a screengrabber app that I didn't even use
Can anyone give me any reasons why I should have root besides custom roms??? I love the idea but not the headaches it gives me...
And, if custom roms are the big idea, what benefits will that give? Don't they run a little finicky anyways? Not all features are enabled, e.g. 4g?
Click to expand...
Click to collapse
- why feel bad?
- if the next statement is true, then the FPS cap must not have been an issue; else you would have done a google search on the issue and corrected it.
- if this statement is true, why feel bad?
- i dont find the need for so many custom ROMs (not like back when i was running on WinMo6). once you have 'root', adding/removing apps is straightforward and most of the ROMs are just a "here is my theme and apps, it's built on someone else who did the low level tweaking". custom ROM just makes it easier to get closer to what YOU want for an applist and themelayout. i like cm6 and dont' like theme's so life is easy for me.
- CM6 is AOSP. this means they will not use propriarty code (like Sense). for the EVO it also means the 4G radio software has to be written from scratch since there is no opensource 4G stuff to use yet. if you pick a Sense based rom (ie: anythign that doesn't refer to itself as CM6 or AOSP based).
Note: AOSP Like means that it is a Sense based ROM but it's been made to look/act similar to the CM6 or AOSP ROMs. 4G and Radio and such should work normally.
enjoy the free time associated with being Root-less.

Well, I'm re-rooted. Used the unrEVOked method. It was just so easy, there was no reason not to. Really want to get on cyanogen but waiting for the 4g.
sent from my bad-ass EVO!

Android 2.3 (Gingerbread) Being Pushed To AOSP

http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )

These are very good news
I already see my Hero running CM 7
:happy face:

Excellent News Lets see who get's their GingerBread ROM out first

Sweet, if the hero really will be supported!

Cooooooooooooooool man very nice go go go go gooooooooooooooogle

Tchuup-tchuup! Hotness train is leaving the stations

ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.

dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...

Good news
Sent from my HTC Hero

C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress

I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor

I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero

l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.

Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?

That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project

Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero

I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...

Especially the repo syncing... that just takes ages ;

krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!

Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents

[REQ] Calling for support for Dedicated iTouch-like Android build for HD2

Just telling you guys the story first.
I have this spare HD2 lying around after getting the Sensation which also has a severely cracked screen (LCD working, and screen protector on top to prevent injured fingers when using ). A thought occurred to me: Why not build Android to function like an iTouch? I.e: Remove anything related to the SIM card/ remove everything that involves making calls, SMS, etc but retain the functionality of Android apps etc(As I will be using DATA SIM). Most importantly, I want it to be fully optimised for those (I believe that the phone/sms functions running in the background would affect the full potential for the HD2 running music, video, and other apps). I do know how to flash ROMS, and customise downloaded ROMS (e.g: Slipstreaming apps I want, remove some apps I don't want, customise build.prop, etc) and also some programming (a bit of obj-C, a bit of C#, and lots of VB.NET). However, I do not know how to build Android from scratch. Hence I would appreciate if:
-I can get devs to assist me in building Android from source code and customise it so it fits my expectations
-I can get support for this project as I plan to release my work to the public when its done
I will give credit to those who helped. Thanks.

Reserved for future use.

Reserved again.

arikyeo said:
Just telling you guys the story first.
I have this spare HD2 lying around after getting the Sensation which also has a severely cracked screen (LCD working, and screen protector on top to prevent injured fingers when using ). A thought occurred to me: Why not build Android to function like an iTouch? I.e: Remove anything related to the SIM card/ remove everything that involves making calls, SMS, etc but retain the functionality of Android apps etc(As I will be using DATA SIM). Most importantly, I want it to be fully optimised for those (I believe that the phone/sms functions running in the background would affect the full potential for the HD2 running music, video, and other apps). I do know how to flash ROMS, and customise downloaded ROMS (e.g: Slipstreaming apps I want, remove some apps I don't want, customise build.prop, etc) and also some programming (a bit of obj-C, a bit of C#, and lots of VB.NET). However, I do not know how to build Android from scratch. Hence I would appreciate if:
-I can get devs to assist me in building Android from source code and customise it so it fits my expectations
-I can get support for this project as I plan to release my work to the public when its done
I will give credit to those who helped. Thanks.
Click to expand...
Click to collapse
arikyeo said:
Reserved again.
Click to expand...
Click to collapse
arikyeo said:
Reserved for future use.
Click to expand...
Click to collapse
Sir, i seriously doubt your state of mental stability.
And as for your request, the best you can do is use in Airplane mode and switch on wireless. Works for me when i don't want to waste my battery.
Just so that you know, the Qualcomm processors have 2 ARM CPUs on the die, 1 for Radio(Wireless/bluetooth/GSM etc) and 1 for the General purpose/Logic etc... I don't think GSM functions and the phone app running in the background would even mean or translate into anything near a burden or even something which would affect the performace for the CPU in your HD2.

you're pretty much dead-end on this one mate.
android is built ground-up for use in mobile phones. look at those cheap shenzen tablets..they all have no network icon in top bar, and com.android.phone must be running. removing this will only result not working phone as these also include core services-market access etc
only hope you have for doing what you want is to somehow get honeycomb workin' on qsd8250 and tiny fingers to interact with it.
imho best bet would be to just install CM or MIUI, and hide phone etc from launcher.
refer to post above for "very exact explanation" of everything you are trying to do

Why Root

I have one question....
Why root a phone? I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too. No offense to the developers I just didn't see a benefit.
Am I wrong?

With root you can
1. Run custom ROMs to make your phone your own
2. Remove bloat
3. Tether for free .99
4. Install custom kernels & voltages to increase your batter life or speed up your phone
That's just a few I can think of off the top. Don't think that magic will happen just because you root your phone...your phone can be rooted and still behave exactly how it did prior to root.

Root makes it possible to customize your phone to your liking. You can change the look and feel of just about everything. Root is also great for making battery life better or making your phone snappier by installing custom kernels and root only aps. I agree with you that a lot of roms are buggy and can be a pain, but some people like the trouble shooting aspect of figuring something out and making it work. I my self usually stick to the stock or mostly stock roms, and then remove, change, add features that i want. Without root your stuck with what htc and verizon gives you. Its all about freedom and choice and the ability to make your phone look how you want, and do the things you want it to do.

I am relatively new to rooting (this past summer), but what it gave me was a vastly superior phone to what I used to use. I have flashed about 5 ROMS - two Cyanogen Mod and three Sense based ROMS - out of the 5, I only had big problems with one. The other 4 made my phone faster, smoother, and gave me access to some apps (Titanium Backup, Font Changer) that have allowed me to customize my phone to my liking. It's made me change when I was hoping to get a new phone (now I don't care that much - yet) and I literally feel like I've had new phones every time I flash another ROM.
Doing it successfully also required that I read A LOT about phones, hardware, software, etc. - geeky stuff - that I didn't know. (I'm still learning a lot.)
So, maybe you're just not that into your phone and the geeky stuff?

epescina said:
I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too.
Click to expand...
Click to collapse
It sounds like your phone is afflicted with the common PEBKAC bug.
Given that, I think you are making the right decision by not rooting in the future.
For those genuinely wondering about the benefits of root, you can check the various stickies throughout this forum or the hundreds of articles that have been written about it. Alternatively, you could do a market search for "root only" to see all the unique apps. Or you could read about what custom roms offer. Or custom kernels. Or a host of other things.
If you don't know why you want to root, you probably shouldn't be rooting.

byrong said:
It sounds like your phone is afflicted with the common PEBKAC bug.
Given that, I think you are making the right decision by not rooting in the future.
For those genuinely wondering about the benefits of root, you can check the various stickies throughout this forum or the hundreds of articles that have been written about it. Alternatively, you could do a market search for "root only" to see all the unique apps. Or you could read about what custom roms offer. Or custom kernels. Or a host of other things.
If you don't know why you want to root, you probably shouldn't be rooting.
Click to expand...
Click to collapse
PEBKAC bug? I'm assuming thats stands for something smart lol.
Edit: Haha nevermind i figured it out.

ummm, cuz its awesome...i feel like i escaped from alcatraz

Thanks for all of the great post guys! They were all very informative!
I guess it's true, I must educate myself more about rooting. I always assumed my phone would work better, allow me to use custom roms (that actually worked), and apps that were root only.
I jailbroke my ipod and other devices and they were easy to do and use and not to mention stable. I guess I was expecting the same outcome here.

Why wouldn't you root your phone? All it does is give you full access to your own device. If you don't follow directions and/or load a buggy rom it has nothing to do with rooting.

If you're having that kind of trouble with ROMs, you're doing something wrong (unless you're using AOSP, then you're ALWAYS going to have issues.) I simply won't use a ROM that isn't stable. I probably won't stick with one long even if it is stable and patched together like some Frankenstein chocked full of scripts and patches to make it work. Reliability is the top priority for me. There used to be devs on this device that valued that more than they seem to now, with a few exceptions. Most of them, from using them, are buggy, unstable projects that probably shouldn't have ever been released as anything but experimental betas. Some of them, like WildStang's, are VERY reliable. Just gotta do your research. This is a totally different world than Apple, and a LOT more powerful.

loonatik78 said:
If you're having that kind of trouble with ROMs, you're doing something wrong (unless you're using AOSP, then you're ALWAYS going to have issues.) I simply won't use a ROM that isn't stable. I probably won't stick with one long even if it is stable and patched together like some Frankenstein chocked full of scripts and patches to make it work. Reliability is the top priority for me. There used to be devs on this device that valued that more than they seem to now, with a few exceptions. Most of them, from using them, are buggy, unstable projects that probably shouldn't have ever been released as anything but experimental betas. Some of them, like WildStang's, are VERY reliable. Just gotta do your research. This is a totally different world than Apple, and a LOT more powerful.
Click to expand...
Click to collapse
I have to say that I have had zero issues with cm7 and most aosp ROMs out for this phone. sounds like you're doing something wrong.
cm7 gives you so many opportunities for customization and runs so flawlessly I will not be running sense again. Galaxy nexus here I come barring some glaring issue with it, i'm done with HTC for awhile.
Sounds to me like the OP hasn't properly wiped all data before flashing his roms.

br125 said:
I have to say that I have had zero issues with cm7 and most aosp ROMs out for this phone. sounds like you're doing something wrong.
cm7 gives you so many opportunities for customization and runs so flawlessly I will not be running sense again. Galaxy nexus here I come barring some glaring issue with it, i'm done with HTC for awhile.
Sounds to me like the OP hasn't properly wiped all data before flashing his roms.
Click to expand...
Click to collapse
I've flashed at about a dozen different versions of CM on that phone. Of those 3 or so didn't even boot. Of the ones that did, they had some kind of issue that couldn't be remedied like quirky screen brightness, reboots and FC's right off the bat. Of the couple of versions that made it past the first day, only one lasted more than a couple weeks before getting REALLY weird. A friend with an identical phone had a very similar experience. What's more, CM hasn't proven to be any more reliable on the EVOs I've flashed it on. In fact, about half the versions don't even boot. I've been doing this long enough to know I'm not doing it wrong. CM just sucks if reliability is a required trait.

loonatik78 said:
I've flashed at about a dozen different versions of CM on that phone. Of those 3 or so didn't even boot. Of the ones that did, they had some kind of issue that couldn't be remedied like quirky screen brightness, reboots and FC's right off the bat. Of the couple of versions that made it past the first day, only one lasted more than a couple weeks before getting REALLY weird. A friend with an identical phone had a very similar experience. What's more, CM hasn't proven to be any more reliable on the EVOs I've flashed it on. In fact, about half the versions don't even boot. I've been doing this long enough to know I'm not doing it wrong. CM just sucks if reliability is a required trait.
Click to expand...
Click to collapse
that is the furthest from the truth of anything I've ever read. Go to the cm thread and write that. I've been on cm for a looong time without any FC's, reboots, or anything quirky. Stop spewing false opinions as fact, you're not helping anything.
Also, how could such an unreliable, buggy ROM be the most popular over a plethora of devices? Think about it.

Sounds like that nasty PEBKAC bug. I'm on CM 7.1 and it's been heaven. Almost everything works BETTER than stock.
For example, my car (Cruze 2011) can't utilize my phones contacts over Bluetooth on my stock sense rom. If I allow the car access to my phonebook, my Bluetooth will drop in and out and not work properly. So I have to tap "don't allow" and even though I checkmark the "remember my decision" box, it comes up every time I get in my car unless I grant it access. Annoying? Lets just say I'm thankful for the cyanogen team. Works absolutely flawless.
I adore the new lockscreen in 7.1. It's like a reverse sense 3.0 style where instead of dragging the apps to the ring, you drag the ring to the app. I still overall prefer the sense 3.0 lockscreen, but to get that I have to sacrifice a lot of stability. There are lists upon lists of features that make CM7 the rom to be on.
The one thing I will concede about CM7 is the auto brightness is a bit wonky. There are auto brightness tweaks you can mess with but something like that should work out of the box, so to speak. Another could-be annoyance is the heavy emphasis on customization, since CM comes pretty bare. CM9, however, will be feature rich per ICS.
Sent from my ADR6300 using XDA App

screenshot
For one thing, you can't even take a screen shot without rooting. If you want a stable phone that is mostly stock, you can root, install ShootMe, and call it a day. Of course, it looks like they're finally fixing that fatal flaw with ICS (which this phone will never see from HTC).

loonatik78 said:
If you're having that kind of trouble with ROMs, you're doing something wrong (unless you're using AOSP, then you're ALWAYS going to have issues.) I simply won't use a ROM that isn't stable. I probably won't stick with one long even if it is stable and patched together like some Frankenstein chocked full of scripts and patches to make it work. Reliability is the top priority for me. There used to be devs on this device that valued that more than they seem to now, with a few exceptions. Most of them, from using them, are buggy, unstable projects that probably shouldn't have ever been released as anything but experimental betas. Some of them, like WildStang's, are VERY reliable. Just gotta do your research. This is a totally different world than Apple, and a LOT more powerful.
Click to expand...
Click to collapse
Thanks, you seem to be the first to admit that most ROMS are unstable and buggy which is what really turned me away from most roms! I researched over and over and couldn't find stable roms, they all claim they are stable but that was never the case.

br125 said:
I have to say that I have had zero issues with cm7 and most aosp ROMs out for this phone. sounds like you're doing something wrong.
cm7 gives you so many opportunities for customization and runs so flawlessly I will not be running sense again. Galaxy nexus here I come barring some glaring issue with it, i'm done with HTC for awhile.
Sounds to me like the OP hasn't properly wiped all data before flashing his roms.
Click to expand...
Click to collapse
So what is the proper way to wipe all data before flashing? I thought all you had to do was select the two flash boxes and run it!

epescina said:
So what is the proper way to wipe all data before flashing? I thought all you had to do was select the two flash boxes and run it!
Click to expand...
Click to collapse
That's your problem, you're using ROM Manager to flash/install ROMs. You need to boot your phone into ClockworkMod Recovery and install it from there. Once in CWM Recovery, do:
1. Go into Recovery
2. Clear data: Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
3. Select Install zip file from SD Card, browse to the ROM zip file, select it with touch pad to install

epescina said:
So what is the proper way to wipe all data before flashing? I thought all you had to do was select the two flash boxes and run it!
Click to expand...
Click to collapse
Don't use Rom manager. Boot into recovery and factory reset/wipe all user data, then flash the Rom. It also doesn't hurt to wipe dalvik cache and format the system if you are still having issues.
If you post in the thread of the Rom you're trying to flash, the users may have some more 'rom specific' instructions.
Sorry for getting off topic before, but I can't stand someone spreading false information about a very good Rom that may cause someone like you to not try it, when in all reality you may enjoy it, as very many droid incredible users do.
Edit: Try what he said above me too. That is almost an overkill amount of wiping, but it can almost guarantee that you won't have issues with the flash.

br125 said:
Don't use Rom manager. Boot into recovery and factory reset/wipe all user data, then flash the Rom. It also doesn't hurt to wipe dalvik cache and format the system if you are still having issues.
If you post in the thread of the Rom you're trying to flash, the users may have some more 'rom specific' instructions.
Sorry for getting off topic before, but I can't stand someone spreading false information about a very good Rom that may cause someone like you to not try it, when in all reality you may enjoy it, as very many droid incredible users do.
Edit: Try what he said above me too. That is almost an overkill amount of wiping, but it can almost guarantee that you won't have issues with the flash.
Click to expand...
Click to collapse
This is true, probably overkill, but doesn't take long at all to do, and haven't had any issues yet installing any ROM. Battery Stats is an optional wipe.

[ANSWER] -_/*~Kernel~*\_-

There are many explanations that people will tell you to the answer to the "what is a kernel?" Like this great one from Omnicide
Spoiler
Omnicide said:
The best way i seen it put was, think of the kernel as the engine and the rom as the body of the car. The body of the car (rom) just makes the car look nice and user friendly. Now when we talk about the engine (kernel) simply put red lining the engine will get you to go fast but burn gas. Keeping the rev down low will make you run slower but saving lots of gas. Thats just one way to look at it, rpms being the cpu.
Click to expand...
Click to collapse
or this great one from androidcentral.com
Spoiler
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example --when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
. You probably didn't get it at all, so let me tell you what a kernel is in about 17 words. A kernel is "what makes the phone work, and connects the hardware (camera, storage, etc.) And the software (the Rom)."
I don't want to be thanked for this, thank omnicide, and androidcentral.com for the great explanations.
~~~~~~~~~~~~~~~~~~~~~
Samsung galaxy s2
Rom: Jedi knight 6
kernel: Jedi kernel 2
~~~~~~~~~~~~~~~~~~~~~
And you thought celebrities weren't smart! =P

Kernel can correlate to brains function in the human body meaning the manager of the perishing body.
Or the manager of the resources available.
Or the manager of the body.
Sent from my SAMSUNG-SGH-T989 using xda premium

I flashed JB Jedi 2 which came packed with a rom while it works great I wonder what will happen if I want to switch back to a different Rom will it be compatible with the kernel it installed?

All roms install their own default kernel each time you flash them.
They are usually chosen by the rom's Dev for good reasons (usually stability) .
It's up to you if you then choose to replace the included kernel with one of your own choosing.
At that point you should think twice about posting glitches you encounter on the ROM developer's forum because you have now changed a fundamental component of his work which is not of his choosing. It would be kind of rude to clutter his thread with problems that may be caused by the replacement kernel.
Feel free to push the envelope, just make a backup first then post problems to the kernel's thread.

Ohh ok I really didnt know that as some roms I have downloaded are 90mb some are like 330mb does that mean they are all compressed in different ways?

davcohen said:
Ohh ok I really didnt know that as some roms I have downloaded are 90mb some are like 330mb does that mean they are all compressed in different ways?
Click to expand...
Click to collapse
No. Some ROMSs gave more data or bloat. Slim ROMs, are well, slim. Leaks, like, Jedi jelly, tend to be pretty big, due to all the bloat they have.

LoopDoGG79 said:
No. Some ROMSs gave more data or bloat. Slim ROMs, are well, slim. Leaks, like, Jedi jelly, tend to be pretty big, due to all the bloat they have.
Click to expand...
Click to collapse
Bloat = the stuff, APKs in this case, someone decided are not necessary.