[ROM][8.16.11][ODEX]EVOlvedROM r3chargeD RC1 "Just Another S

You might not have got a good wipe before install. I've heard (hasn't happened to me yet) that that is what happens from time to time.
 
I had no problem with it but it just wasn't fluent enough for me. It got laggy at times and it just erks me.

So back to decks 1.2.1 stable. 365MB free and only 300MB of ram left :) plenty of room and speed!
 
I had no problem with it but it just wasn't fluent enough for me. It got laggy at times and it just erks me.

So back to decks 1.2.1 stable. 365MB free and only 300MB of ram left :) plenty of room and speed!

On stock GB 2.3.3 I had 150MB of storage free. With r3chargeD and the same apps loaded, I have 270MB. HUGE improvement. I'm not getting any lag out of mine, but if it gets that way, I'll flash another. My only criteria is 99% of the stuff has to work which eliminates CM7 completely. I played that game before GB came out.
 
My only criteria is 99% of the stuff has to work which eliminates CM7 completely. I played that game before GB came out.
What doesn't work on CM7? If you "played that game" before GB, then you were on CM6 so I'm not sure how you can say 7 doesn't work.
 
What doesn't work on CM7? If you "played that game" before GB, then you were on CM6 so I'm not sure how you can say 7 doesn't work.

I wasn't on CM6. I had root with CM7 before the OFFICIAL GB came out for the Evo. I went back to stock and ran it. Now I'm rooted again and enjoying several other ROM's that aren't CM-based.

CM7 bugs - CyanogenMod Forum
CM7 Bugs and To DO list - xda-developers
Has they fixed the horrible little bugs in Cm7 stable yet? - Android @ MoDaCo

There are a few links. (just Google "CM7 Bugs" for more) I had major issues with CM7 and so did/do a lot of other people. Their RC's should be Beta's and their Beta's shouldn't be released. I may get flamed for that statement, but it doesn't bother me...I'm just a dog. Woof.
 
Last edited:
I'm not asking what other users have, I'm asking what problems you had and what currently doesn't work.

You linked me to a Motorola Defy and Viewsonic forum. I'm getting the sense you're just trolling. I'm not a CM7 fan boy, I'm not even running it, but I dislike when people make stuff up regardless the topic.

Please share what specific bugs are still present on CM7 on the Evo.
 
whats the prefered way to install this properly?

also does anyone know if it supports N-wireless?

thanks in advance!
 
I'm not asking what other users have, I'm asking what problems you had and what currently doesn't work.

You linked me to a Motorola Defy and Viewsonic forum. I'm getting the sense you're just trolling. I'm not a CM7 fan boy, I'm not even running it, but I dislike when people make stuff up regardless the topic.

Please share what specific bugs are still present on CM7 on the Evo.

Calling someone a troll is a violation of the TOS so I'm not going to get into that with you as I don't know, nor do I care who the hell you are. I don't know what problems CM7 STILL has because I don't run it. I had several problems of my own like no GPS, no SMS and MMS not working after one of their nightlies, no front facing camera, horrible battery life (worse than stock) and at one time my dialer didn't even work. A dialer not working on a phone? WTF? I quit running it after the dialer episode that seemed pretty rare, but when it happens to you, it's not rare anymore. If you were able to read and find your own way through forums, you would have found a very hefty EVO4G problems on CM7. No links this time because you said you didn't want them. I will not reply to you anymore, just so you know, so feel free to type whatever you want. I joined this to share knowledge and gain knowledge; not to argue.
 
Not taking sides on this, just an update to it. All of those bugs are working now. Nightly builds are expect to have bugs as they are not consider official releases from cm. Curtain nightly builds I had did have bad battery life and some good. Right now with Nightly #162 all is good.
 
whats the prefered way to install this properly?

also does anyone know if it supports N-wireless?

thanks in advance!

Boot into recovery and wipe the system, davlik cache, and do a Factory Data Reset (FDR from recovery). then install from zip file, find the r3chargeD.zip and flash it. When done, reboot.

Don't know about Wireless N, but I thought one of the sites I was reading said it does. Hell, 3G, 4G, and wireless work at least, so no drama there. So does everything else I've used or looked at. It's a smooth ROM and frees up 100+ MB.
 
Not taking sides on this, just an update to it. All of those bugs are working now. Nightly builds are expect to have bugs as they are not consider official releases from cm. Curtain nightly builds I had did have bad battery life and some good. Right now with Nightly #162 all is good.

Good to know after 162 nightlies they got the bugs worked out...(?) All I said was my criteria for selecting a ROM was that 99% of stuff has to work and that CM7 didn't fit that bill for me, and it opened a can of stupid. I was one of the first to start downloading CM7 when it came out and was actually a fan of theirs for about a week. I was expecting them to have it ironed out in a month or so, but it just kept going. I got tired of it and started running others. When the OFFICIAL GB was released, I went back to stock and waited for root. It was nice not having my phone crash every 5 minutes, and all my apps working when I needed them to work. I said I was going to root again ONLY for a wireless tether, and to offload the bloatware...then this ROM and 2 other AOSP's appeared and I'm happy. I wouldn't be saying that if I was running CM7...I'm positive.
 
I didn't call you a troll, I said you were trolling, which is a description of your behavior not an assessment of you as a user.

Nightly builds are buggy, period, you can't compare. There is nothing that doesn't work on CM7 stable on the Evo. There will always be users with bugs, just like there will be isolated bugs on this ROM, and there are. Isolated, user bugs are not the same as systemic errors; CM7 has no systemic errors, crashes, missing features, or non-working functionality.

This isn't the CM7 thread so it's not worth arguing much further, but I will defend a ROM from baseless trashing like you're doing. It damages the whole community and gives AOSP a bad name when you spread false info about a very good ROM.

I'm not on here trashing EVOlved r3chargeD, it's a great ROM for those that want this style, skin, and feature design, but Android is about choice, so please stop willfully misleading the users in here.
 
Boot into recovery and wipe the system, davlik cache, and do a Factory Data Reset (FDR from recovery). then install from zip file, find the r3chargeD.zip and flash it. When done, reboot.

Don't know about Wireless N, but I thought one of the sites I was reading said it does. Hell, 3G, 4G, and wireless work at least, so no drama there. So does everything else I've used or looked at. It's a smooth ROM and frees up 100+ MB.
When you wipe the system and do a factory reset, my backups still stay right? I made a nandroid backup of my stock rom just in case, and I don't want to lose it.
 
When you wipe the system and do a factory reset, my backups still stay right? I made a nandroid backup of my stock rom just in case, and I don't want to lose it.
As long as you're just wiping data, cache, and dalvik cache, it won't touch your SD card.
 
I didn't call you a troll, I said you were trolling, which is a description of your behavior not an assessment of you as a user.

Nightly builds are buggy, period, you can't compare. There is nothing that doesn't work on CM7 stable on the Evo. There will always be users with bugs, just like there will be isolated bugs on this ROM, and there are. Isolated, user bugs are not the same as systemic errors; CM7 has no systemic errors, crashes, missing features, or non-working functionality.

This isn't the CM7 thread so it's not worth arguing much further, but I will defend a ROM from baseless trashing like you're doing. It damages the whole community and gives AOSP a bad name when you spread false info about a very good ROM.

I'm not on here trashing EVOlved r3chargeD, it's a great ROM for those that want this style, skin, and feature design, but Android is about choice, so please stop willfully misleading the users in here.

"My only criteria is 99% of the stuff has to work which eliminates CM7 completely. I played that game before GB came out. "

Oh yes, I sure trashed CM7 and the entire AOSP community with that post....Completely baseless...I'm surprised I didn't get banned or at least sued for slander...

Learn how to READ. "I played that game BEFORE GB came out". BEFORE GB came out, CM7 was really buggy. EXTREMELY buggy. That was MONTHS ago, and I don't run it anymore, but I have 2 OTHER AOSP ROM's sitting in wait that I've checked out and like, so how do you figure I am giving AOSP a bad name? If you're talking about my other answers where I gave you specifics when you ASKED for them TWICE; if you didn't want to hear the answer, don't ask the question. That's your own damn fault if you didn't really want me the answer.

Unwad your panties, and quit exhibiting the trollish behavior you claim to despise!
 
Last edited:
Is there anything I shouldn't wipe so I don't lose my backup? Just want to make sure. I'm a noob here. :)

Just don't format, wipe, or erase your SD card and you'll be fine. If you are using titanium backup, or any of the others backup programs, it will put your apps back on for you too. You'll be fine.