• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Damageless ROM?!

And there are no problems with your phone? I bricked my phone updating a radio..

Nope, I just made sure I named it radio.zip and then flashed it and didnt touch it while it was flashing. But I bought my phone at bestbuy and they have a 30 day return policy so if anything happens ill just get another and anytime i return my phone the 30 days restarts so idc if i brick it or not but the only way you couldve bricked your phone was if you didnt follow directions to the "T" or if the radio file was corrupt.
 
I just installed radio with RA1.5.2 and everything was copacetic with DamageControl1.0.... we'll see how it load-tests tomorrow. First impressions are only that there was no loss of quality in the fringe area where I live.

On a different note, When I connected it to my computer to load the radio.img file onto the sdcard, I got my first sign-in error in a few days; which was once again promptly fixed by cycling my airplane mode widget twice. That is my magic cure if any of you ever have problems with that.
 
Okay, I decided the dive in and install the new radio image on DamageControl. I did this for a couple reasons. First, I like tinkering around. The fact that I rooted the phone in the first place is because I love new toys. Sure I wanted to improve the phone, but the stock Hero was plenty acceptable to me. Secondly though, I've been running Fresh for 2 or 3 weeks and I was getting anywhere from 24 to 36 hours per battery charge (projected out). Since I installed DC this weekend, I seem to be getting 16 to 20 hours (projected). That's still pretty acceptable, but since some have commented they got better battery life I figured I'd give it a shot.

I've only had it installed a couple hours, but here is my initial feedback. I don't seem to be getting anymore bars inside my house, but I have noticed that it has remained on a 3G connection constantly. I'll test it more tomorrow. I'll charge fully tonight and test out the battery life tomorrow as well.
 
anyone getting SMS problems today? my phone was working fine and this morning when i send a message (stock app) its says SMS Error general problems, when you click on details it says Cause Code: 34, Error Class 2
I did do the MMS update after i flashed the ROM. wondering if i should do a nandroid restore. It was working flawlessly until this morning.
 
well i downloaded chomp and it was working and then later on i was getting undeliverable messages. My friends said some were coming through that said they werent, but not all are going through. Also tried handcent and the same thing. Wondering if i should go back to Fresh.
 
I do still get the Voicemail notification, however I can confirm that it only happens on power-on. It is slightly irritating, but easily fixed.
 
well i downloaded chomp and it was working and then later on i was getting undeliverable messages. My friends said some were coming through that said they werent, but not all are going through. Also tried handcent and the same thing. Wondering if i should go back to Fresh.
I was getting this, too. I wiped and reflashed DCv1 last Friday and not a single undeliverable yet! (knocks on wood)
 
Well I have to say that I thoroughly enjoyed this ROM while it lasted. If anything, it gives us a preview of what the real 2.1 update will be like.

I had to revert back to 1.5. I was getting a few bugs here and there, and after reflashing and reflashing, I would get different bugs, errors, Fcs, etc. The browser seems faster at first glance, but it actually lags a lot more in screen resizing and scrolling. Very irritating. A lot of my games would FC unexpectedly. The last straw was people kept telling me on the phone that my voice would randomly sound super far away, very annoying when I was trying to tell my wife directions somewhere, and she couldnt hear half of them. This might be due to the new radio? Not sure. Also, my battery life was ridiculous. Not even a half day (7-8 hours max)

So I RU'ed my phone, it reverted to the oild radio. Re rooted, and restored a backup of Fresh 1.1, GCK, and setCPU. I might give it another go, well see.
 
Well I have to say that I thoroughly enjoyed this ROM while it lasted. If anything, it gives us a preview of what the real 2.1 update will be like.

I had to revert back to 1.5. I was getting a few bugs here and there, and after reflashing and reflashing, I would get different bugs, errors, Fcs, etc. The browser seems faster at first glance, but it actually lags a lot more in screen resizing and scrolling. Very irritating. A lot of my games would FC unexpectedly. The last straw was people kept telling me on the phone that my voice would randomly sound super far away, very annoying when I was trying to tell my wife directions somewhere, and she couldnt hear half of them. This might be due to the new radio? Not sure. Also, my battery life was ridiculous. Not even a half day (7-8 hours max)

So I RU'ed my phone, it reverted to the oild radio. Re rooted, and restored a backup of Fresh 1.1, GCK, and setCPU. I might give it another go, well see.


I keep kicking around this idea too... I get frustrated with voice mail, and I've also had people say they've tried to call me but haven't been able to get through to me. I also have issues with some of the websites I used to visit (Flash Sites) that no longer allow me to watch videos.

I'm torn... I love the new O/S, but I can't go a day without a bug :(
 
I keep kicking around this idea too... I get frustrated with voice mail, and I've also had people say they've tried to call me but haven't been able to get through to me. I also have issues with some of the websites I used to visit (Flash Sites) that no longer allow me to watch videos.

I'm torn... I love the new O/S, but I can't go a day without a bug :(
I too decided to wait for the Sprint release, mainly the voicemail issue so I wiped and restored a nandroid backup of the gumbo 1.5c ROM and am having people tell me the same thing... have been trying to call me, though the phone has not rung nor showing any missed calls.:confused:
 
I unrooted my phone...back to stock...........and probably gonna stay like that till the update comes out...

Which is why I love open source software (Android/Linux). We are free to use our devices how we want. For me personally, I haven't encountered any show stopper issues. To this point I am receiving all my calls. The only 2 issues I have are that dial out with Google Voice doesn't work, and of course the visual voicemail doesn't work. GV dial out is minor since I can initiate a call from the website. It's not as convenient, but acceptable until the issue is resolved. Regarding VVM, I could use GV but I'm already using it for work and I haven't quite figured out how to get it configured just right. I'm sure I can do it, just haven't had the time yet. So in the meantime, I tried YouMail yesterday and it's working good so far.

The bottom line for me is that I'm going to stick with the DamageControl ROM until Sprint releases an official ROM, at which point I will still run a modified version of it. Of course if I start to have more serious issues, everything I just said goes out of the window. :)
 
LOL....I rooted again this morning and flashed Darch's ROM ....

it's pretty stable too.. I like it..one thing I didn't like..you can't receive images over 300k...weak!
 
Anyone have problems using swype with damage control? The first time I flashed it was working fine when I installed it. But after I reboot the phone it will not work. The message says something about swype being set for another device.
 
Anyone have problems using swype with damage control? The first time I flashed it was working fine when I installed it. But after I reboot the phone it will not work. The message says something about swype being set for another device.
i rebooted phone today as well and thats the message i got. i had the registered beta..... dunno yet wtf is going on
 
The unlock screen seems to act differently than those on other ROMs. When swyping from top to bottom, the phone doesn`t unlock. Swyping from the middle to the bottom will unlock it. Strange
 
The unlock screen seems to act differently than those on other ROMs. When swyping from top to bottom, the phone doesn`t unlock. Swyping from the middle to the bottom will unlock it. Strange

Yep. However, since I've been running DC now for about a week I have adjusted to it.
 
i actually just went from Darch's to Damages, and i have to say, Damages is much better....the only thing i didnt test yet is mms, but everything else is absolutely perfect. I run Helix from the market and my phone for me is perfect right now.
 
Would you guys suggest me to do this?

some people it's helped, some it hasn't. My signal didn't get any noticeably better, and I have no real idea if it helped battery life, but I don't think it did much for it. The biggest problem with this ROM (and I believe all of the 2.1 ROM's at the moment) is that is defaults to search for GSM, causing your time without signal to be very high (mine was at 85% yesterday...but I was probably actually without signal for half of that anyway lol). That seems to be a big battery killer, but there's a fix for it that you have to do every time you reboot
 
Back
Top Bottom