Related
im still using pancake 1.5, why you ask? because i want to wait until the final sprint release of 2.1 comes out and we get a custom rom fully working and bug free. plus i have my phone customized the way i want it.
so who else chose to not use any newer builds yet?
fixxxer2008 said:
im still using pancake 1.5, why you ask? because i want to wait until the final sprint release of 2.1 comes out and we get a custom rom fully working and bug free. plus i have my phone customized the way i want it.
so who else chose to not use any newer builds yet?
Click to expand...
Click to collapse
This isn't responding to your question, but I just switched over to DamageControl v1 and I love it. Pretty much every bug has been fixed, and since it's still Sense, it's possible to get the exact same customization that you had before. Just jump ship to 2.1
mrinehart93 said:
This isn't responding to your question, but I just switched over to DamageControl v1 and I love it. Pretty much every bug has been fixed, and since it's still Sense, it's possible to get the exact same customization that you had before. Just jump ship to 2.1
Click to expand...
Click to collapse
naw ill wait, thanks. i use a rom without sense included.
I flip flop between gumbo or modaco since they are so dang stable. Sometimes when I feel adventurous I will flash the new 2.1 Flipz rom. The main reason I dont stick with them permanently is because of little bugs that always seem to pop up and I also prefer to have all of my sprint apps working since Im payin for them.
pancake still
I am still on pancake. It works very well and I have it set how I like it (for now). I am very close to just taking the leap to one of the 2.1s though. Seems like they have most everything working well. Besides, we never know just how long it will be before sprint releases 2.1.
cheers,
ryan
I still use Fresh 1.0 because it has Rosie and it's set up EXACTLY how I want it and there are no bugs. I have tried out all of the new 2.1 Roms except the Legend and there are bugs in pretty much all of them. DamageControl is the closest 2.1 Daily driver I have found
Finally made the jump to damage 1.0 and everything works.
The only thing that will not function is Sprint VVM, and I think GVoice Dial has a problem.
Hell the full screen weather effect from HTC clock is worth the switch. Should see the iPhoners drool when I show them that.
Well, for anyone who's refraining from switching to Damage Control due to concerns about bugs, I'd say that DC1.0 now feels like it genuinely has fewer bugs than Sprint's stock 1.5 does. Really.
With the stock ROM, my bluetooth never worked reliably, my voicemail counter was stuck in perpetually-incrementing mode since late November, and I'm not even going to mention the hell and grief I endured having to pick my poison between HTC's useless keyguard and LockBot's "good cop"/"bad cop" weeks when it would screw up the phone every other time I unlocked it (making itself home, waking up on volume bar presses, etc).
I've now gone for 2 whole days without ONCE taking the phone out of my pocket and finding it unlocked (I deleted HtcKeyGuard* and use the stock Eclair (Flan?) keyguard instead). Google Maps doesn't keep going senile and forgetting how to show traffic unless I reboot. I get 1/4 the FC errors I got with stock (Astrid used to FC so often, I'm amazed it ever managed to work). And countless little things that positively drove me to distraction daily. Thanks to DC, I genuinely like my Hero again. How good is DC compared to stock? If my Dad had a Hero, I'd make him reflash this weekend. If my Mom had a Hero, I'd do it for her. DC1.0 isn't a toy to screw with before groaning and going back to a ROM that works... it's the real deal.
bitbang3r said:
Well, for anyone who's refraining from switching to Damage Control due to concerns about bugs, I'd say that DC1.0 now feels like it genuinely has fewer bugs than Sprint's stock 1.5 does. Really.
With the stock ROM, my bluetooth never worked reliably, my voicemail counter was stuck in perpetually-incrementing mode since late November, and I'm not even going to mention the hell and grief I endured having to pick my poison between HTC's useless keyguard and LockBot's "good cop"/"bad cop" weeks when it would screw up the phone every other time I unlocked it (making itself home, waking up on volume bar presses, etc).
I've now gone for 2 whole days without ONCE taking the phone out of my pocket and finding it unlocked (I deleted HtcKeyGuard* and use the stock Eclair (Flan?) keyguard instead). Google Maps doesn't keep going senile and forgetting how to show traffic unless I reboot. I get 1/4 the FC errors I got with stock (Astrid used to FC so often, I'm amazed it ever managed to work). And countless little things that positively drove me to distraction daily. Thanks to DC, I genuinely like my Hero again. How good is DC compared to stock? If my Dad had a Hero, I'd make him reflash this weekend. If my Mom had a Hero, I'd do it for her. DC1.0 isn't a toy to screw with before groaning and going back to a ROM that works... it's the real deal.
Click to expand...
Click to collapse
You should work in advertising! Also loving DC1.0
I went from Damage back to Fresh. Fresh is more updated and clean. Damage has too many .odex files.
I can't get BT data transfer to work on 2.x with apps like BT File Transfer I get that lower library level error or whatever so I haven't jumped because that's the only reason I would other than that I can do without the pimped out more battery intensive Sense experience...but don't get me wrong I am excited for it...just gonna wait for the official however I did the radio update so we'll see how it shakes out when I do the upgrade lol.
Do the switch, there bugs are minor...I don't plan on going back to 1.5 ...
I'm pretty happy with DC 1.0 ...
I can't get BT data transfer to work on 2.x with apps like BT File Transfer I get that lower library level error or whatever
Click to expand...
Click to collapse
Have you tried a recent (past few days) build of DC? I'm hoping to finally dig into bluetooth this weekend (as soon as I get NBAndroid to work with API >= 5), but it would be immensely reassuring to hear that someone who already knows how to use it has gotten it to work. Few things are harder than trying to simultaneously figure out how to use something AND figure out whether it's crashing because of something YOU did, or crashing because of a problem with the underlying OS/library itself.
fixxxer2008 said:
im still using pancake 1.5, why you ask? because i want to wait until the final sprint release of 2.1 comes out and we get a custom rom fully working and bug free. plus i have my phone customized the way i want it.
so who else chose to not use any newer builds yet?
Click to expand...
Click to collapse
I use fresh 1.0, the 1.5rom. I like it b/c everything works. And I like visual voicemail and mms. I also depend on my phone way too much to have something not reliable.
someonenewhere said:
Do the switch, there bugs are minor...I don't plan on going back to 1.5 ...
I'm pretty happy with DC 1.0 ...
Click to expand...
Click to collapse
I have used every 2.1 that has been deved aside from damage's( that one will be next) but just had to ruu yesterday due to phone freezing. I use my phone constantly and rarely have time to flash or root or anything else. I love the 2.1 roms and will flash again when I have time but for now I am staying with complete stock till I know that the complete lockups are over and it was not a phone issue. That way if I have to get it warrantied then it is not rooted and flashed.
BTW: every rom I used was amazing in its own way. My personal fav was flipz 2.0b.
I'm not sure why people are calling DCv1 unreliable but I flashed coming from fresh 2.0b2 and haven't had a single fc. Everything works and the speed is awesome. Apps2sd was automatic, handcent works great and I'm thoroughly satisfied. I can't imagine going back to 1.5 for anything.
swaze said:
I'm not sure why people are calling DCv1 unreliable but I flashed coming from fresh 2.0b2 and haven't had a single fc. Everything works and the speed is awesome. Apps2sd was automatic, handcent works great and I'm thoroughly satisfied. I can't imagine going back to 1.5 for anything.
Click to expand...
Click to collapse
Time to change your sig maybe? LOL just playin.
obannvi said:
I went from Damage back to Fresh. Fresh is more updated and clean. Damage has too many .odex files.
Click to expand...
Click to collapse
me to Fresh 2.0 feels more refined to me I also don't really use the video record so no big deal and all the Sprint apps work not including VVM. Damage seemed to loose Sprint tv after a day and the verizon tab kept showing back up in the market. I would have to pull it put after reboots. Both are good roms don't get me wrong and it's nice to have a choice.
I'm still sitting on Sprint's stock 1.5 ROM (I thought it was called Cupcake, not Pancake?), mostly because I haven't had any real issues with it. See no reason to change. I suspect that after the 2.1 update, there won't be any more, and then once I get sick of 2.1 I might start flashing custom ROMs, for speed.
Still love Sense though. Couldn't use Android without it, I think.
Would enjoy an easy way (without rooting) to get the Sprint crapware off the upcoming 2.1 stock ROM. I don't care about NFL, Nascar, or TV, but want to keep Sprint Navigation. Also, a way to get rid of the HTC native apps such as Peep and the native IM application.
tduck: There is a ROM called Pancake, and it's different than the stock 1.5 Sprint ROM.
I'm currently using Pancake 1.5. I thought about using the newer builds when the dev's got Camera working but decided to hold off until the final release is issued by sprint, no real reason as to why.
i just got into this and i wanted to know who has the most stable rom available im sure its between damage and fresh rom wat do u think .....
killacammiami said:
i just got into this and i wanted to know who has the most stable rom available im sure its between damage and fresh rom wat do u think .....
Click to expand...
Click to collapse
In my opinion, Fresh Rom 2.0d followed by DarchLegend.
Ill put my hat in Fresh's corner. I used damage's rom as well. You cant really go wrong with either.
I've tried DC 2.05, 2.06, 2.07, and 2.07.2 and each one becomes unusably slow after just a couple of hours. I don't know why. I would literally wait 10 seconds for the Settings menu to show up.
I switched to Fresh this morning and so far it's running well. Not as well as DC 1.0 did (I have no idea why the Eris ROM is so much faster) but well.
I've been using DarchLegend for a while now, and it is by far my favorite. Especially with visual voicemail working in the latest release, it is a very solid rom. But you just have to try them. Make a nandroid backup, then just start wiping and flashing like crazy
im trying to download it but it says could not be saved, because the source file could not be read. contact server or admin why is this
honestly, none of the current 2.1 roms cut it for me because of several issues including the audio loss. if you want a 100% working/stable/fast rom go with pancake 1.5.
I'd say fresh's feels the most stable
I do have a place in my heart for darch's AOSP so I am going to say that's my favorite, hopefully he gets that update out soon.
killacammiami said:
im trying to download it but it says could not be saved, because the source file could not be read. contact server or admin why is this
Click to expand...
Click to collapse
It's an issue with your computer. You don't have to post in every unrelated thread about it.
fixxxer2008 said:
honestly, none of the current 2.1 roms cut it for me because of several issues including the audio loss. if you want a 100% working/stable/fast rom go with pancake 1.5.
Click to expand...
Click to collapse
I had more issues on 1.5 than I ever have on 2.1 (especially DarchLegend like I mentioned above)
jonnythan said:
It's an issue with your computer. You don't have to post in every unrelated thread about it.
Click to expand...
Click to collapse
lol thank you im just trying to get this installed i been anticipating forever to get a rom and now i rooted it and i want to go all the way lol im going to restart
Right now I would have to say Fresh then Damageless. I find myself using both more than all other dev's ROMs but Fresh's ROMs always seem to give me the least hassle and run the smoothest. I love trying them all out though. I am addicted to flashing ROMs and modding my phone.
Leukay said:
I had more issues on 1.5 than I ever have on 2.1 (especially DarchLegend like I mentioned above)
Click to expand...
Click to collapse
strange...to each their own i guess.
fixxxer2008 said:
honestly, none of the current 2.1 roms cut it for me because of several issues including the audio loss. if you want a 100% working/stable/fast rom go with pancake 1.5.
Click to expand...
Click to collapse
Not everyone experienced the audio loss issue. To the OP, just do a nand backup and try them all out.
fixxxer2008 said:
honestly, none of the current 2.1 roms cut it for me because of several issues including the audio loss. if you want a 100% working/stable/fast rom go with pancake 1.5.
Click to expand...
Click to collapse
x2
/thread
My main issue with all the 2.1 roms is the battery life..it flat out sucks.
I'll plug my phone in and check it about every hour and see its gained about 5% battery life. Yay! If I can turn my phone on and the battery loses 2% while im looking at it, its useless to me.
I'm running Pancake 0.1 with Sense and even on heavy use I get easily 20+ hours out of it. Yesterday I unplugged my phone at 8 in the morning and I sit here at 4pm the next day with 5% battery left. On a smartphone? WOW!
Time to plug it in!
man fresh rom has so many problems keep gettin force close apps audio problem doesnt ring and hate the thing when i make a call i feel vibration
ive never had any problems with any of fresh's roms most stable by far! ive been using darchlegend for the past week, and i love the new widgets no problems at all except my 5.0 doesnt have vvm i havent upgraded to 5.0.5 yet.
hey u live in my area im in miami .. but yea i put it on and i did the wipe i keep getting error that says force close things also i couldnt hear my ringer .... im trying the [ROM](1ST with all recent fixxes built into one rom)DamageR_2.7 but do i suppose to update my radio??? ima noob
my votes for regaw. Been stable for me no problems
I was installing the new Myn's Warm lastnight upgrading from the previous version. It did not install properly and COMPLETELY BRICKED my phone. It won't turn on, can't connect to computer via USB, nothing at all! Anyone else have this problem? OR any solutions other than taking to Sprint?
I doubt that your phone is bricked. Hopefully you DO have a rooted EVO though. I would plug it in and let it charge. Then take out the battery and put it back in and turn it on while holding down power and volume down keys to boot into recovery. Also hopefully you made a nandroid backup so restore that and go from there. I had no problems with flashing RLS5 at all. Hopefully this helps. Otherwise maybe someone with a little more knowledge can help you...
Sprint is DEFINITELY not the answer...
do a battery pull and try to get it to hboot. then try and run the RUU. if not you may have to take it to sprint.
The phone won't charge, won't turn on, can't hboot. I do have backups if I could get it to turn on I could restore it. Had no problems before. I will attempt to charge it as you have suggested but I even put a different fully charged battery in and the phone does not even make at attempt to turn on. I agree I doubt that Sprint is the answer
did you flash any radio updates? any prls, I've never heard of flashing a rom making a phone brick, but definitely heard of radio updates bricking devices.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
i really doing think his update bricked your phone
This means that while installing Warm you bricked your phone. Don't give his ROM a bad name.
I would recommend trying to charge it and maybe try a different battery, but then just run the RUU and go from that. I had the same problem with RLS 4.
Sent from my EVO using XDA App
If you used the package to update the pri, radio, etc then that may be the problem, hopefully you aren't bricked.
Sent from my PC36100 using XDA App
Are you sure that you didn't flash the radio? I flashed Myn's rom last night and I didn't run into any issues, in fact I've never heard of a rom bricking a phone, that usually happens when a radio flash goes terribly wrong. Anyhow, you can take it back to Sprint since it's still under warranty and they will replace it for $35.
CheesyNutz said:
i really doing think his update bricked your phone
Click to expand...
Click to collapse
ive heard several people say it has in fact jacked their phones up. hence why i have not upgraded to it yet.
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
the radio update isn't included with the rom.
it's also been highly advised in the warm thread itself to flash just the radio, then just the wimax, then perhaps the nv/pri, because so many people have been having trouble with the pri update.
the radio combo pack isn't bundled with anything else and, right now, many think it should be avoided for reasons just like this.
not a solution, just clarification and friendly advice for anyone else who's curious about possible trouble with the upgrades.
I updated my radio/pri/wimax and all that jazz before the last Fresh update, so I had no need to this go around. I simply wiped data/dalvik/cache and flashed the RLS 5, with no problems. I did run into issues after I tried restoring my apps + data, but that was a Titanium Backup issue
arcurtis said:
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
Click to expand...
Click to collapse
Just my 2 cent.. often times we flash before reading the thread and then complain about a kernel,ROM or theme.
After reading what you said I can only come to the conclusion that you and all the others complaining about the radio update are obviously impatience. All who have had problem with the update on the radio all stated their phone sat on the white screen and they did a battery pull.
Yet the radio update thread says it will/can take up to 30 min to flash. The best way to check your phone would be to use another battery. I have never heard a bricked phone that doesn't cut on. That's a battery issue.
What kernel were you using before flashing?
What ROM?
What's your hboot?
Sent from my PC36100 using XDA App
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
arcurtis said:
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
Click to expand...
Click to collapse
Does the phone attempt to charge when you plug it in?
Sent from my PC36100 using XDA App
I can confirm brick.
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Nope the phone will not even charge. I've changed batteries and chargers. I am assuming I am one person who has just had extremely bad luck with a random flash. I was running Myn release and did a backup and wipe then phone would not reboot and completely shut down. I got the android guy with the arrow and then it went completely dead and won't turn back on.
dth4310 said:
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Click to expand...
Click to collapse
That is almost exactly what happened to me. I considered doing the same thing but don't really want to chance getting busted for a rooted phone
i've never flashed a radio update, i'm too chicken lol.
the quickest way to brick any phone is a f'ed up radio flash. or pulling the battery while flashing a radio.
i would take it to sprint and tell them you accepted a over-the-air update and then your phone shut off and this is what happened.
Headache after headache after headache since I got the Froyo OTA.
Lots of freezes causing me to pull the battery several times a day. Also the battery power drains so quick I can't even come up with a comparison. Then don't get me started the 3G going down all the time...this is f***ing ridiculous. I did root it but I have seen no change. I have even disabled the bloatware...anyone have any suggestions for me.
Much thanks in advance,
Doc
You can try odining back to DL09 or whatever, re-update OTA, and see if the problem happens again...
If not, I would just leave it stock and return it to verizon with the 1 year warranty
Ive had the same issue! I rerooted and flashed evil fascination and I am not having hardly any problems. Ive had a few forcecloses but nothing like what came with stock froyo
My girlfriend is having the same issue after i MADE her update to the OTA 2.2. Text messages dont get sent and it is very laggy. The whole phone is too slow to use so i plan on flashing a custom rom or going back to 2.1 with odin. What roms are pretty similar to stock that maintain that whole touchwiz feel?
Sent from my Galaxy Tab using XDA App
Did you perform a factory reset? That seemed to fix a few problems.
For starters, this is common. The stock Froyo update screwed a lot of people up. Next, simply rooting it doesn't *FIX* anything, all it does is give you the ability to run Apps as Administrator, giving you more power/control. So, you rooted it, that wasn't going to fix your issues. Flash a custom ROM. I personally recommend the Community ROM. If after flashing a different ROM, after wiping Cache, Dalvik Cache, and user data, etc. you still encounter the same issues, then yes, I'd exchange it.
Dread This Day said:
For starters, this is common. The stock Froyo update screwed a lot of people up. Next, simply rooting it doesn't *FIX* anything, all it does is give you the ability to run Apps as Administrator, giving you more power/control. So, you rooted it, that wasn't going to fix your issues. Flash a custom ROM. I personally recommend the Community ROM. If after flashing a different ROM, after wiping Cache, Dalvik Cache, and user data, etc. you still encounter the same issues, then yes, I'd exchange it.
Click to expand...
Click to collapse
Common? Really?
About the same time as the ota froyo was released, verizon had a bunch of 3g & 4g data issues on their network (perhaps it was shortly thereafter).
Otherwise, I see as many posts about the surprisingly good performance of the current stock rom as I see reports of issues.
No offence to the op, but we have no idea how these rooted phones have been messed with before the complaints are conveyed...
So I agree with the suggestion to odin back to a stock pit/modem/kernel/rom and let the ota process repeat from a clean start. From that result, flash a solid voodoo kernel, enable lag fix, pick your favorite rom, etc...
Sent from my SCH-I500 using XDA Premium App
I am currently running the ota 2.2 froyo update...only thing I have done is root and debloat and the phone is very fast! Only issue I have is google voice search force closes.
I think the update is fast... but despite what rom I use there is still intermittent gps issues, voice and data issues even on the first warranty replacement. Dropped calls in solids 4 bar territory on stock or dev roms and 3g fading un and out even after the dmu fix. All issues never had before the update.
Waiting on a call to see if I can get a better replacement option. No interest in Palm, BB or the Dinc Droid Pro or DX they want me to take as a replacement.
Out of the DInc2 Charge and TBolt which is the best options in my fellow forum friends minds. Have my own looking for outside opinions to consider depending on the options I am offered.
sent from my ComRom ED01 Froyo - Voodoo - Fascinate via Tapatalk Pro
My GF is having OTA 2.2 pains also...signal issues may be due to network, but also noticed lag, camera issues (black screen and force closure when camera opened)...text not received...probably will root and flash custom ROM...if she lets me..LOL....
4GivenByChrist said:
I think the update is fast... but despite what rom I use there is still intermittent gps issues, voice and data issues even on the first warranty replacement. Dropped calls in solids 4 bar territory on stock or dev roms and 3g fading un and out even after the dmu fix. All issues never had before the update.
Waiting on a call to see if I can get a better replacement option. No interest in Palm, BB or the Dinc Droid Pro or DX they want me to take as a replacement.
Out of the DInc2 Charge and TBolt which is the best options in my fellow forum friends minds. Have my own looking for outside opinions to consider depending on the options I am offered.
sent from my ComRom ED01 Froyo - Voodoo - Fascinate via Tapatalk Pro
Click to expand...
Click to collapse
Download the app "gps booster". Seem to fix my gps issue... locks in quick and within 10ft. As far as the signal issue, I had the same thing until I replaced the stock battery cover. have yet to drop any calls and my 3g is alot better now! I am absolutely impressed with this phone since doing these little "tweaks"! O and I vote droid charge if your dead set on a replacement! Seems to have better battery and display over the other two.
sccafun said:
My GF is having OTA 2.2 pains also...signal issues may be due to network, but also noticed lag, camera issues (black screen and force closure when camera opened)...text not received...probably will root and flash custom ROM...if she lets me..LOL....
Click to expand...
Click to collapse
I heard that! My girl is hesitant to let me do anything to her phone after she saw the learning curve i went through with my captivate haha
bmeek said:
Common? Really?
About the same time as the ota froyo was released, verizon had a bunch of 3g & 4g data issues on their network (perhaps it was shortly thereafter).
Otherwise, I see as many posts about the surprisingly good performance of the current stock rom as I see reports of issues.
No offence to the op, but we have no idea how these rooted phones have been messed with before the complaints are conveyed...
So I agree with the suggestion to odin back to a stock pit/modem/kernel/rom and let the ota process repeat from a clean start. From that result, flash a solid voodoo kernel, enable lag fix, pick your favorite rom, etc...
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I stated nothing about the the OP's 3G outtage, any of us who are techy-like at all or who pay attention know what that was about. I was referring to their other issues. And I agree, MANY people have great performance after updating to stock 2.2, while many others are also getting screwed up. It's just one of those things. The OP wasn't one of the lucky, so, either Odin back and try the update again, or go custom ROM.
Well I have a couple DInc2s coming next week.
Really have to send the love to all the Devs who have made the Fascinate fascinating. Just can't wait on Sammy and VZW to get the tools in the hands of the devs to make the most of these phones.
Almost went TBolt but don't want to extend the contract until there are more 4g phones out there.
Wife is excited about FFC so happy wife will be good for me
Would have preferred to stick with the Fascinate but a couple replacements later and even the great roms and kernels couldn't get it to where it should be. Here's hoping that good source drips for everyone soon.
So for free and no contract extension I'll check out HTC...
sent from my ComRom ED01 Froyo - Voodoo - Fascinate via Tapatalk Pro
I did OTA Froyo update on a stock fascinate and my battery also began draining rapidly, about 8-10 hour life in standby I finally figured out that it was the built in facebook sync that was doing it, I had earlier turned off all syncing then noticed fb synced new events to my calendar after that so I completely removed my fb account and now its back to the ~2days of battery life with light use I had with 2.1. Not sure if this is what everyone else is experiencing with battery life problems but its worth a shot. I haven't tried putting my fb account back up to see if it happens again, I'm going to wait until I get around to rooting to do that.
I swear I had these issues with 3g data out completely. This fixed it in 3 minutes. ESN Swap to repartition data. No BS need for another phone.
http://totalhack.ws/esnswap.html
Hope this helps.
Well... Been using the DInc2 for over a day now... Short time but very evident that there is a major issue post update on the Fascinate. Right back to the great download and upload speeds I had pre ed01. No ATT like dropped calls, etc.
Without voodoo quadrant scores on stock in the 1400 - 1600 range consistently.
Just a huge thanks to all our awesome Fascinate developersfor making it a great phone while I had it.
Hope the DInc2 developers are as committed and talented as this team. Right now they are working on getting perma root....
Sent from my ADR6350 using Tapatalk
Hey everyone,
I just put the cyanogenmod 7.0.2.1 on my HTC EVO 4G about a month ago. At first it was working fine, now it will just randomly restart not while I'm ever using it, but when it is sitting idle it will just restart at odd times. Has anyone else had this issue?
Everything else with the ROM is working awesome. Please Help.
No issues here, why don't you come up to date and flash the stable 7.0.3.1. Are you running any custom kernels by chance?
Here's the link to 7.0.3.1 just flash over your current rom and wipe dalvik-cache.
http://mirror.teamdouche.net/get/update-cm-7.0.3.1-Supersonic-signed.zip
Oh thanks, been really busy with work, and hadn't had time to check for any updates. I appreciate the help very much. DL'ing the new ROM now.
Upgrade to the newer version. Maybe it'll help? Definitely clear cache & dalvik when you update.
Evo 4G / CM 7.0.3.1 - Tiamat 4.0.2 SBC / XDA Premium
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What ROM did you go to?
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
Yeah I like the CM7 ROM, but just can't take the restarts. I am going to upgrade to the newest stable release and see if that fixes it. I would like to stay with the CM7 if at all possible.
Swype
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
beaukincade said:
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
Click to expand...
Click to collapse
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
dirkyd3rk said:
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
Click to expand...
Click to collapse
no its gone and won't let me use titanium backup to reinstall it either
beaukincade said:
no its gone and won't let me use titanium backup to reinstall it either
Click to expand...
Click to collapse
Do you have the latest titanium backup version? If you can't get it going the swype apk is all over the place lol. *wink wink*
Get the latest version (beta) from their site.
http://swypeinc.com/
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
I have ran many different roms and CM7 was the ONLY one that caused my phone to reboot many times a day. A quick google search can show you threads about owners who had phones that bricked after running CM7. I never said it was gospel, I just dont need my phone rebooting multiple times during the day and it was way more often when I had wimax connected. CM is a great rom but its not the second coming of Android and not worth my phone rebooting during the day.
And I am running Smooth N Sexy V1.2 A sense ROM that looks like gingerbread.
Reboots
I've been through several ROMs now and the reboot problem appears to be not a ROM issue!
Here is the story. I had started with Baked Snack, very good, but I wanted more battery and to try CM and get away from Sprint messaging update nag.
CM worked great, I updated to 7, until the reboots started to happen during heavy use of Angry birds.
So I restored to early CM 6.x, and reboots continued off and on every few days, getting progressively worse.
So I tried Warm 2.2, same issues.
I went back to CM7 and still trouble.
I went to Fresh and It was fine for a week, and then on Friday, (I noticed that Friday was significant), reboots again.
So after a month of this the reboots are so bad that I can't use the phone. I called Sprint, de-provisioned the EVO, went back to my Palm, and then unrooted and went back to Stock ROM, but with no Cell access.
The phone is stable now. As long as it's off the Sprint Cellular network!!!
All of the reboots were related to cellular activity. Messages coming in, ads being updated, calls coming in, tower switching, roaming, or worse of all, no tower signals at all.
I will post back here if the phone remains stable without cellular. But all of the research I have done on the issue has pointed to cellular access. I am on wifi and all the apps and functions are working without issues so far. I am starting a dialog with HTC to see if there is a hardware problem.
The reboots also caused heat in the general area of the SD card...don't know what else is there but I do know the cellular antennas are on that side of the phone. Leaving the battery out all night, after an off state recharge would help stabilize the phone for a while, including cache wipes and factory resets.
But once the phone had been on for a while, or Friday morning would come, the reboots would continue.
I have been a computer nut for 30+years and I solve issues for a living. I strongly suspect the radio hardware or firmware as the culprit in this reboot issue. Every other account of this has had similar connections to the radio use.
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
dirkyd3rk said:
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
Click to expand...
Click to collapse
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
misterzeno said:
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
Click to expand...
Click to collapse
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
dirkyd3rk said:
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
Click to expand...
Click to collapse
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
misterzeno said:
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
Click to expand...
Click to collapse
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
dirkyd3rk said:
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
Click to expand...
Click to collapse
You win, you obviously have the bigger nerd e peen. I should go back to a flip phone. *Bowing to phone gawd*
You wouldn't be as much as an ass if you happen to suggest ONE resolution to the rebooting.