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.
Related
I have no idea what happened.
I'm using Cyanogen last update and the phone is so slow it is useless.
Specially when closing an app and going back to the home screen... it takes forever for the phone to be available and ready.
What is the problem ? Any hint?
nricci said:
I have no idea what happened.
I'm using Cyanogen last update and the phone is so slow it is useless.
Specially when closing an app and going back to the home screen... it takes forever for the phone to be available and ready.
What is the problem ? Any hint?
Click to expand...
Click to collapse
Im guessing you have alot of apps open in the background then, you should consider getting a task killer app from market.
Not really...
A wipe fixes everything.
Thank you guys.
The phone is slow 5 seconds after a reboot.
Home screen takes forever to appear and some time forces close.
I might try another room, I don't know.
Everything you need is right here:
http://forum.xda-developers.com/showthread.php?t=567610
I had the same issue. Here is what i did to fix it
Did a Nandroid backup, wipe ,flash with the 1.6 base rom first, then the latest CyanogenMod rom.
Thanks
Will try your suggestions and post the results
Mine was slowing to a crawl as well, turns out (I think) it didn't run as well with compcache enabled. Since disabling it again it is running much better.
nricci said:
I have no idea what happened.
I'm using Cyanogen last update and the phone is so slow it is useless.
Specially when closing an app and going back to the home screen... it takes forever for the phone to be available and ready.
What is the problem ? Any hint?
Click to expand...
Click to collapse
My hint would be ditch Cyan(buggy arse rom)mod and switch to something better and more reliable like either rom in my signiture.
shadowch31 said:
My hint would be ditch Cyan(buggy arse rom)mod and switch to something better and more reliable like either rom in my signiture.
Click to expand...
Click to collapse
Did you just call cyanogen buggy? Them's fightin' words *spits into spittoon*
JAguirre1231 said:
Did you just call cyanogen buggy? Them's fightin' words *spits into spittoon*
Click to expand...
Click to collapse
Erm I do believe I did! *spits into spittoon and listens for the 'ting' noise*
I'll even go as far to say any dev putting the word stable in the title of a rom (at his own admission when it is anything but and needs to be tested) yet still continues trying to fool himself by still saying its stable deserves to have it labelled buggy crap
shadowch31 said:
Erm I do believe I did! *spits into spittoon and listens for the 'ting' noise*
I'll even go as far to say any dev putting the word stable in the title of a rom (at his own admission when it is anything but and needs to be tested) yet still continues trying to fool himself by still saying its stable deserves to have it labelled buggy crap
Click to expand...
Click to collapse
Let's just remember, cyan is basically the base for many roms
JAguirre1231 said:
Let's just remember, cyan is basically the base for many roms
Click to expand...
Click to collapse
Oh I know that fella, I'm using Super D at the moment which is a mix of cyan and dwang and whilst they use the base they also inherite the annoying little bugs too
He has done one hell of a lot for the community, still doesn't detract from the facts though.
shadowch31 said:
Oh I know that fella, I'm using Super D at the moment which is a mix of cyan and dwang and whilst they use the base they also inherite the annoying little bugs too
He has done one hell of a lot for the community, still doesn't detract from the facts though.
Click to expand...
Click to collapse
I used cyan for a week then went back to hero.Now im back on hero(espresso).
On the concept of "stable" I think people have preconceived definitions without merit. Take for example the definition of a "stable stochastic process", which though it is nicer to deal with than many Levy processes, is still a pure jump process. If one can accept the idea of a pure jump stochastic process as being "stable" then it is no problem to see any Cyanogen ROM as stable.
As a side note, I have not had any issues with CM that could not be easily resolved. I love his ROMS, but have a lot of respect for the extremely stable work put out by Enom (I only used his ROM for awhile, but switched to CM for the ease in theming).
This has happened to me before with Cyanogen but I found it was more to do with the SD Card. It would happen anytime I removed the USB cable without "Ejecting" the phone first, amongst other things.
The solution was to format the SD Card and reflash but the downside is you lose everything including apps.
So, here is my story.
I have tried Fresh 1.1, and I found that I was getting may too many reboots both on the phone and on Sense for my liking.
So I switched to Modaco 2, and have been very happy for a while...
I just had yet another reboot.
I was listening to some music, when I had a notification for an email. Looked at the email, tried to lock my phone, then tried to unlock, and that's when the music went off, and my phone rebooted itself....
I'm really getting tired of this. I have not loaded any new apps in the past 2 days. I have minimal apps anyway (Facebook, Weatherbug, Handcent, NPR News, Touchdown, Power Manager and Droidswap, that is it)
does anyone have any history of problems with Droidswap ?
I'm really getting frustrated. I hate when this happens, and I'm giving realy consideration into curtailing my brief incursion onto Android and returning back to the iphone....which is a real shame, as I f**king hate ATT
I would recommend taking your phone back to the store. I have not have had one unplanned reboot the entire time I've had my Hero (bought on release date Oct 9). I'm running Fresh 1.1 now, and had 1.0 previously. There is something seriously wrong with your phone.
I have no problem speaking for the entire android community when I say...
"its been nice knowing you, good luck with the iPhone and att"
Honestly...I have never had a full reboot on its own.
I have seen Sense close out and have to reload usually after I play an intensive game, racing or something like that with alot of graphics. I assume it just runs out of ram and does its thing to get resources back.
That's a rare occasion there's not much people that it has happened to from what I seen. Did u try to wipe your phone and cache & whatnot, do some of that and see what happens
(off topic)
Jdog stop trolling because u definitively don't speak for the Android community...
bronxknight28 said:
Jdog stop trolling because u definitively don't speak for the Android community...
Click to expand...
Click to collapse
I think I can speak for the whole Android community when I say. "Please don't go" - The more of us we have the better. Given, I completely understand frustration and disappointment.
bronxknight28 said:
That's a rare occasion there's not much people that it has happened to from what I seen. Did u try to wipe your phone and cache & whatnot, do some of that and see what happens
(off topic)
Jdog stop trolling because u definitively don't speak for the Android community...
Click to expand...
Click to collapse
Bronx,
Myself and many other members of this site and over at modaco's site have given advise on this issue. Griff insulted flipz and other devs in the fresh Rom thread, then went to modaco and started talking trash on the devs here.
Every post is about this reboot problem, that no one can seem to replicate.
I apologize for being rude but if someone doesn't take any of the advise given,then continues to clutter up the forums with new threads about the same thing it ticks me off...
Try TTG. It's made a world of difference for me.
thedudejdog said:
Every post is about this reboot problem, that no one can seem to replicate.
I apologize for being rude but if someone doesn't take any of the advise given,then continues to clutter up the forums with new threads about the same thing it ticks me off...
Click to expand...
Click to collapse
The advice he should be taking is to STOP LOADING APPS.
Out of the apps he has listed, I only use Facebook and Handcent SMS... so I'm willing to vouch for those two as not being the culprit. If he hasn't done a wipe and tried running with minimal apps, then the problem is his own fault.
some people just arn't made for android, and apple's buisness model is "you're too dumb to want to do that" actually applies to some people
EDIT: and there is nothing and I mean NOTHING in the world that gives me more of a nerd-boner than someone "rage-quitting" it puts a beautiful smell in the air... the smell of victory
thedudejdog said:
Bronx,
Myself and many other members of this site and over at modaco's site have given advise on this issue. Griff insulted flipz and other devs in the fresh Rom thread, then went to modaco and started talking trash on the devs here.
Every post is about this reboot problem, that no one can seem to replicate.
I apologize for being rude but if someone doesn't take any of the advise given,then continues to clutter up the forums with new threads about the same thing it ticks me off...
Click to expand...
Click to collapse
Erm, ex-****ing-scuse me, but can you PLEASE copy the link to the post where I insulted Flipz and started talking trash ?
x99percent said:
The advice he should be taking is to STOP LOADING APPS.
Out of the apps he has listed, I only use Facebook and Handcent SMS... so I'm willing to vouch for those two as not being the culprit. If he hasn't done a wipe and tried running with minimal apps, then the problem is his own fault.
Click to expand...
Click to collapse
I haven't got lots of apps loaded.
And I have gone back to stock, wiped, formatted my SD card many times...etc...etc.
All I am saying is that I am experiencing completely random reboots, and I'm desperate to hear if anyone else is.
This dudejdog or whatever he likes to call himself is plain wrong. I have never, and never will trash anyone. I urge him to prove if I have.
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
grifforama said:
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
Click to expand...
Click to collapse
You could try stock and maybe figure out the Apps2SD scripting that way you have both.
grifforama said:
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
Click to expand...
Click to collapse
Did you try removing any partitions you might have set up (for Apps2SD or swapfiles)...just an idea, simply reformatting your SD card will NOT delete partitions.
grifforama said:
I haven't got lots of apps loaded.
And I have gone back to stock, wiped, formatted my SD card many times...etc...etc.
All I am saying is that I am experiencing completely random reboots, and I'm desperate to hear if anyone else is.
This dudejdog or whatever he likes to call himself is plain wrong. I have never, and never will trash anyone. I urge him to prove if I have.
Click to expand...
Click to collapse
Okay...you said you've gone back to stock. When you go back to stock without any other programs loaded, are you still experiencing the issue?
If not, what I suggest is to load each of your programs one at a time, pausing after you load them for at least 12 hours to see if the reboot occurs. I know that's a time consuming process, but it may help to isolate.
If you are having reboot issues with no additional applications loaded and while you are using the stock ROM, I think there maybe something wrong with the hardware and you should take it back to Sprint for replacement.
Hopefully this helps, or at least points you in a direction to go.
grifforama said:
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
Click to expand...
Click to collapse
When you return, let us know your results and we'll try to help you. I'm thinking it is an application. I had this issue when I tried to update the Superuser Permission program. When it tried to update from Android Marketplace, it would reboot the phone (I actually saw "System crash is inevitable" in the trace log when it tried to update the program).
If you don't mind me asking, what version of the Stock ROM are you using? I did have issues when I was running a custom ROM (Modaco) running 1.29 and tried to upgrade to a custom ROM (again, Modaco) with 1.56. My issue was force close issues that I could not fix. The solution was to revert back to stock, let the OTA update upgrade the phone, reroot and apply the new Modaco ROM.
I understand this isn't a force close issue, but your problem may be similar in nature.
ljmeli said:
Did you try removing any partitions you might have set up (for Apps2SD or swapfiles)...just an idea, simply reformatting your SD card will NOT delete partitions.
Click to expand...
Click to collapse
How do I check for partitions ? I thought formatting would get rid of that ?
I remember partitioning a while back, but I have since formatted, and presumed that would have cleared it ?
I'm not back to Stock 1.56.651.2 build CL85027
I took a chance and re-installed pretty much every application I had previously, apart from the obvious rooted apps like droidswap and cachemate.
It's looking fairly stable for now, but I'll report back over the next few days to see how it goes.
I have to say, I've not once slated anyone on this forum. I have total respect for Flipz and I paid Modaco the subs to try his 2.0 beta and then the release. I really would like to use the rooted ROMS, but right now, I just want to see why my phone is doing what it's doing...
thedudejdog said:
I have no problem speaking for the entire android community when I say...
"its been nice knowing you, good luck with the iPhone and att"
Click to expand...
Click to collapse
hahahahahahahahahaha...
awesome..
but ya, no problems here, sorry mate!
(either user error or bad hardware)
thedudejdog said:
I have no problem speaking for the entire android community when I say...
"its been nice knowing you, good luck with the iPhone and att"
Click to expand...
Click to collapse
As jdog says in a few posts below the one I'm quoting... I have done everything I can to try and help him. I have directly worked with him. Along with a ton of other members on this forum. He chose to go to modaco and say that it fixed all his problems and trash fresh. Now here he is saying he's having the same problems.... again.
Edit: With the hard reboots you are getting, I honestly think you need to go exchange your phone.
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
***Put away your pick forks and torches, the search function is disabled the only stuff I keep finding on google is either people overheating their phones or having the same issue as me but all the replies are retarded.***
It's really annoying. About 75% of the time I get on youtube or try downloading something big like a cyanogen update my phone restarts. I've been putting up for it for quite some time now but I'll be depending on my phone next week and this **** needs to stop. It's not the rom since it happens when I install fresh rom (to do prl and all that other sprint crap). I usually cruise with cyanogen (6.1 atm). It happened with mym's warm sumthin rom too. I don't let it overheat... EVER!... I've noticed the stand acts like a heat dissipater so I always keep it open when in use. Also I'm constantly checking to see if it's getting warm. I don't overclock/undervolt it (unless this is a feature added to cyanogen... which to the best of my knowledge isn't... I just skim the changelogs though so I might be wrong)
The phone also restarts when I play need for speed, but I don't really care about that. Would really appreciate help with this one. I'm sure there are other people getting screwed over with this one.
My phone:
Hardware version: 0002
(One of the phones that were handed out for google i/o prior to the official release.)
Cyanogenmod 6.1
Stock cyanogen kernel
Baseband:2.15.00.11.19
PRI: 1.77_003
PRL: 60674
Did it start happening when you updated to the latest radio? I thought I read something about people having freezing or rebooting issues with that radio and cm6, but I could be crazy. I'm almost certain that if you're running a sense rom, it needs to be based off 3.70 to use that radio.. so if the Fresh rom you tried was a little old, you may try the latest. If all else fails, I'd wipe, flash Calk's combo zip with radio/pri/wimax/nv, and then flash a 3.70 based sense rom (I recommend Calk's EViO rom). If problems still persist, it may be a hardware issue.
My phone was doing this with the latest MIUI rom and one of the new gingerbread ROMs that's going around ( I forget which). It only happened once using CM6 nightlies. For me the problem was with the kernel that I was using and my wifi at home. Experiment with some different kernels, that's what I did. The most successful combination is the one that's in my signature, the random reboots ended.
Here's thread dedicated to this problem.
Good luck.
xviiivx said:
Did it start happening when you updated to the latest radio? I thought I read something about people having freezing or rebooting issues with that radio and cm6, but I could be crazy. I'm almost certain that if you're running a sense rom, it needs to be based off 3.70 to use that radio.. so if the Fresh rom you tried was a little old, you may try the latest. If all else fails, I'd wipe, flash Calk's combo zip with radio/pri/wimax/nv, and then flash a 3.70 based sense rom (I recommend Calk's EViO rom). If problems still persist, it may be a hardware issue.
Click to expand...
Click to collapse
Nah, I've had this problem since 6.0 if i'm not mistaken. I did try flashing calk's combo but it gave me an error. It did it again so got my ass back on the computer to make this post. Right now I have fresh latest. Btw I install using rom manager and clockworks flash image. I used to use amonra but switched to clocks and for some reason my phone wont switch back to amon...
@semperlux
thanks for the link. i'll go read that now :3
pirokosan said:
***Put away your pick forks and torches, the search function is disabled the only stuff I keep finding on google is either people overheating their phones or having the same issue as me but all the replies are retarded.***
It's really annoying. About 75% of the time I get on youtube or try downloading something big like a cyanogen update my phone restarts. I've been putting up for it for quite some time now but I'll be depending on my phone next week and this **** needs to stop. It's not the rom since it happens when I install fresh rom (to do prl and all that other sprint crap). I usually cruise with cyanogen (6.1 atm). It happened with mym's warm sumthin rom too. I don't let it overheat... EVER!... I've noticed the stand acts like a heat dissipater so I always keep it open when in use. Also I'm constantly checking to see if it's getting warm. I don't overclock/undervolt it (unless this is a feature added to cyanogen... which to the best of my knowledge isn't... I just skim the changelogs though so I might be wrong)
The phone also restarts when I play need for speed, but I don't really care about that. Would really appreciate help with this one. I'm sure there are other people getting screwed over with this one.
My phone:
Hardware version: 0002
(One of the phones that were handed out for google i/o prior to the official release.)
Cyanogenmod 6.1
Stock cyanogen kernel
Baseband:2.15.00.11.19
PRI: 1.77_003
PRL: 60674
Click to expand...
Click to collapse
There is a thread on here for evo official random reboots. There was a lot of troubleshooting done, but most of us have a Hardware issue. A lot of people got there phones swapped out from sprint.
I picked up my launch day Evo hardware 0003. It always rebooted (even before rooting), but for the last 2 months it got really bad. No matter what I tried (SD card, Formatted SD card, no SD card, CM, Sense, Stock, rooted, unrooted, full wipe with no apps installed), it rebooted.
I purchased at bestbuy with their warranty. I had to deal with bestbuy warranty once already, and didnt want to ship it out and have them not find anything. I went to 3rd party sprint store that did repairs. Showed them the problem and they ordered me a new phone. I had to add Sprint TEP on, which I had no problem doing. I went and cancelled my bestbuy black tie protection.
Have new Evo for a month now, no reboots.
Before the EVO reboots do you notice a fair amount of heat??
Your PRI is the wrong version, just sayin'
Same problem...though i was blaming it on the super battery charge kernels I was using. Found that it is still a problem without the battery mods but less frequent.
It seems to me to happen only when downloading while charging and the screen is off. Also, if I am listening to something at the same time it wont reboot. Lastly, I've caught it a couple of times right before it happened and the phone becomes completely unresponsive.
I'm running with all the latest updates on Azrael's rom.
Sent from my PC36100 using XDA App
1st post, 1st android - LOVE this forum!!
So, I managed to figure out how to root several weeks ago, mainly so I could wifi tether. Been waiting (and waiting... and waiting...) on Sprint to put Froyo out. Toyed with the idea of doing it myself, based on several threads in the xda forums, but just couldn't quite pull the trigger.
Finally took the plunge last week & also flashed my first custom ROM, Syndicate Frozen. Had a couple of 'Oh $hit' moments, but made it through and very glad I did. The speed increase is amazing!
Getting ready to try midNIGHT next... just for kicks.
Just had to say I couldn't have done it without all the awesome help from this forum. Just hope I'm able to contribute, someday...
Cheers!
I remember that from when I got my first Android, the HTC Hero. Such good times.
I am running Syndicate, too. It's my favorite ROM. MidNIGHT is a second, the only reasons I don't use it is because he uses the beta swype in his ROM (meaning you have to renew it every so often), and his rom doesn't support 1x/3G icons like syndicate's does. Though, I must say, MidNIGHT is VERY, VERY stable and will probably not force close ANYTHING you run on it. In other words, MidNIGHT is what stock should've been.
Glad you took the plunge and did it. Its definitely worth it isn't it. On on the latest bonsai rom and its awesome. The.main difference with this rom is you don't have to wipe all your data before you flash.the rom. It backs up all your data and restores it when you flash the rom so you don't have.to start from scratch
Sent From My Evo Killer!
whitfield77 said:
1st post, 1st android - LOVE this forum!!
So, I managed to figure out how to root several weeks ago, mainly so I could wifi tether. Been waiting (and waiting... and waiting...) on Sprint to put Froyo out. Toyed with the idea of doing it myself, based on several threads in the xda forums, but just couldn't quite pull the trigger.
Finally took the plunge last week & also flashed my first custom ROM, Syndicate Frozen. Had a couple of 'Oh $hit' moments, but made it through and very glad I did. The speed increase is amazing!
Getting ready to try midNIGHT next... just for kicks.
Just had to say I couldn't have done it without all the awesome help from this forum. Just hope I'm able to contribute, someday...
Cheers!
Click to expand...
Click to collapse
Ptfmedic did an awesome job in creating the most flexible and stable (with the BYOR edition) Rom I have ever seen to date, even spawning from the old Windows Mobile 6.1 days... ahhh...
Not to mention the dude has a heart of gold. If you do decide to flash one of his roms, be sure to read some of his blogs and if you feel it stir inside you, help out his cause.
Welcome. This forum is very arousing.
Tried to flash midNight BYOR, after using Odin to get back to a stock with root & CWM, but for some reason it kept failing. Something about couldn't open the zip. Going to try to download the Standard version; maybe the BYOR was corrupted during download.
bighuta said:
Ptfmedic did an awesome job in creating the most flexible and stable (with the BYOR edition) Rom I have ever seen to date, even spawning from the old Windows Mobile 6.1 days... ahhh...
Not to mention the dude has a heart of gold. If you do decide to flash one of his roms, be sure to read some of his blogs and if you feel it stir inside you, help out his cause.
Click to expand...
Click to collapse
Yeah, I did take the time to read through a few of his blogs. The Broken Heart one was gripping - will definitely make me think twice the next time I'm approached. The man definitely has a heart of gold & the patience of a saint. And he still takes the time to make great Rom's from what I hear. I should know here in the next hour or so - multiupload is slower than...
Guess I'm supposed to wait 5 minutes between posts...
whitfield77 said:
Tried to flash midNight BYOR, after using Odin to get back to a stock with root & CWM, but for some reason it kept failing. Something about couldn't open the zip. Going to try to download the Standard version; maybe the BYOR was corrupted during download.
Click to expand...
Click to collapse
Not to sound offensive or mean, but did you follow his instructions exactly as written on his Android Development page? When it comes to flashing roms (at least with the Epic) one minor mistake can be the difference between a perfect flash and a faulty one. I learned that the hard way -.-
Edit:
Oh and I forgot to mention, although it hasn't happened to me yet, i hear that bad flashes can occur; I.E., something went wrong in that instance alone, not necessarily the entire thing is debunk, but rather just that one time. Try it again and you might have better luck.
Cheers
Overstew said:
I remember that from when I got my first Android, the HTC Hero. Such good times.
I am running Syndicate, too. It's my favorite ROM. MidNIGHT is a second, the only reasons I don't use it is because he uses the beta swype in his ROM (meaning you have to renew it every so often), and his rom doesn't support 1x/3G icons like syndicate's does. Though, I must say, MidNIGHT is VERY, VERY stable and will probably not force close ANYTHING you run on it. In other words, MidNIGHT is what stock should've been.
Click to expand...
Click to collapse
Not sure why he did that either, but he's recently started using the stock swype we all paid for.
I have to second what you said. I came from a moment and the epic is a huge step up. I'm also running the syndicate rom as well and it sure is a speed demon. I am starting to get the hang of flashing now, though I probably go overboard when I do it. I usually end up flashing back to stock and then install cwm, then I go and flash the rom. This forum is outstanding too. The people here are (for the most part) intelligent and willing to help.
Sent from my SPH-D700 using XDA Premium App
bighuta said:
Not to sound offensive or mean, but did you follow his instructions exactly as written on his Android Development page? When it comes to flashing roms (at least with the Epic) one minor mistake can be the difference between a perfect flash and a faulty one. I learned that the hard way -.-
Edit:
Oh and I forgot to mention, although it hasn't happened to me yet, i hear that bad flashes can occur; I.E., something went wrong in that instance alone, not necessarily the entire thing is debunk, but rather just that one time. Try it again and you might have better luck.
Cheers
Click to expand...
Click to collapse
No offense taken at all. I'm definitely a noob, so I'd rather have someone point out the obvious than assume I knew what I was doing.
Tried it a couple ways. 1st time, I was already rooted with CW3.0.0.6 with flashed syndicate. Wiped davlic, cache, and user 3 times. Tried to install the BYOR version & got the error. 2nd time, I used Odin to get back to EB13 rooted with CW3, no other custom rom. Then tried install BYOR version again (after wiping 3x) and got same error.
Decided to Odin back again, EB13, root, CW3; wipe 3x & then installed the midNIGHT Standard & it worked like a charm. I've had bad file downloads from multiupload before, so I'm gonna pin the blame there for now.
Been exploring midNight this afternoon & like it so far. Figured I should give it a few days before I decide which to go with.