[android-developers] Re: Android Dev Phone 1 DOA, or more correctly, DSAA
My Dev Phone 1 is DSAA as well. I plugged it in, let it charge for the three hours that the manual recommends, then turned it on to begin the setup process. While I was on the phone with T-Mobile, fixing an issue with my data plan, the screen went blank, and the green LED in the earpiece stopped flashing. I tried turning it back on, resetting it, no luck. Tried plugging it in to the charger, removing/reinserting the battery, nothing, not even an orange charging light. The phone is completely unresponsive, even tried removing the SD/SIM chips. Guess I'll be calling support tomorrow to get an RMA on this, because there's absolutely nothing I can do, the thing is a brick, even though the only thing I did was charge it and attempt initial setup. ./Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Android Dev Phone 1 DOA, or more correctly, DSAA
I got another quasi-DOA just before Christmas. The phone will run for about 1 min and then lock up. The screen usually keeps displaying the last image, but the phone will update or not respond to any input. After a lockup, holding power+home does not turn off the phone, I need to remove the battery. I tried charging the battery overnight, no difference. At some point, I was able to put in my google info quickly enough to get past the setup stage. At one point I tried timing the lockups under various use cases. The phone seems to run fine for about 45-60 seconds. The 45-60 seconds is from when I first push the power button. * I've tried running without a sim card -- still locks up. * I've tried running without the SD card -- still locks up. * I've tried going into recovery mode -- still locks up. The only thing that seems suspicious about the phone, is that the system recovery log complains that E:Can't open /cache/recovery/ command Also, I haven't tried loading any new firmware on the device. I haven't tried RMA'ing the phone yet because it works for a while -- it is not a total brick. I want to have some concrete evidence that there is a legitimate hardware issue with the phone... Anybody have any ideas? Thanks, -Derek On Dec 26, 4:56 pm, Clint Fisher clintonefis...@gmail.com wrote: In case anyone is interested, I finally received my replacement phone on 12/24. Shipping in both directions had been delayed by weather and I even had to pick the phone up from the FedEx depot in person just to get the package. Great support folks at BrightStar, who were very courteous, friendly, and sympathetic. I'd still like to see their policies amended to include advance-RMA in their available remedies for the occasional bad product that comes off the line. -Clint On Dec 12, 7:41 pm, Clint Fisher clintonefis...@gmail.com wrote: Boy what a rollercoaster ride this has been... The phone wasn't dead- on-arrival, rather it was dead-shortly-after-arrival. Anyone else have this happen? Got the Dev Phone yesterday morning (I think I did the overnight shipping option), turned it on, and tried to get the ATT APN working. I had it plugged into my desktop with the USB cable, charging. Looked away for a few minutes, and it was dead. Completely unresponsive. Popped the battery, and still dead. Checked 4v on the battery, - and, the battery was over 90%. So I called BrightStarCorp, initiated and RMA, and then, as a last- ditch move to see if it was just the battery, I took it to my neighborhood TMobile store (who may win my business) and the guy was nice enough to test-swap batteries. Much to my surprise, the phone worked again. And then worked again with my own battery back in it! Sweet! I was happy. Took it back proceeded to get the ATT APN working, etc. (sidenote: during this time, the phone rebooted a couple times on its own - just sitting there) So I began loading apps, etc. and began to develop a bond with it. Left it off, plugged into my USB overnight to charge it, and in the morning, the green charge light was on, but the phone was completely unresponsive. Couldn't reset by pressing home+power, etc.. Nothing. But, the green light stayed on. Popped the battery, and the light went off, but the phone never came back. TMoble folks did the test swap again (gotta love 'em), but to no avail. My battery worked in their phones, but none of their G1 batteries worked in mine. The phone is now a brick. A very expensive brick. So I emailed/called BrightStarCorp again today and tried to get the RMA going again. Their support people were nothing but friendly, but their RMA person had already left for the weekend. 2:30 my time. 4:30 their time. I'm not a happy camper. I wanted to at least get an address RMA# before the weekend so I could get it to UPS and on the way. No such luck. Nobody could do an RMA except their RMA person. I asked if I could do an Advance RMA, giving my CC# and an order as collateral for the dead phone. No such luck. BrightStar's people were all very courteous and sympathetic, but I still have a brick. I was told that it will be 1-2 weeks for a replacement. Add that to this lost weekend (when it could have been in-transit), and it could very well be next year before I get a replacement. The Grinch may have stolen my Christmas. So ya, I'm not too pleased with the BrightStar's RMA policies at all, but I'm apparently at their mercy, (unless of course I want to bail on the whole idea and file a claim with the credit-card company - dunno if/how that would go, and I don't like playing that game, but the turnaround time and lost opportunity here is agonizing). My guess is that BrightStarCorp is paranoid about getting failed- firmware-update bricks, but this little guy died right there on my desk, doing nothing but charging. That I have to wait two or more weeks to
[android-developers] Re: Android Dev Phone 1 DOA, or more correctly, DSAA
In case anyone is interested, I finally received my replacement phone on 12/24. Shipping in both directions had been delayed by weather and I even had to pick the phone up from the FedEx depot in person just to get the package. Great support folks at BrightStar, who were very courteous, friendly, and sympathetic. I'd still like to see their policies amended to include advance-RMA in their available remedies for the occasional bad product that comes off the line. -Clint On Dec 12, 7:41 pm, Clint Fisher clintonefis...@gmail.com wrote: Boy what a rollercoaster ride this has been... The phone wasn't dead- on-arrival, rather it was dead-shortly-after-arrival. Anyone else have this happen? Got the Dev Phone yesterday morning (I think I did the overnight shipping option), turned it on, and tried to get the ATT APN working. I had it plugged into my desktop with the USB cable, charging. Looked away for a few minutes, and it was dead. Completely unresponsive. Popped the battery, and still dead. Checked 4v on the battery, - and, the battery was over 90%. So I called BrightStarCorp, initiated and RMA, and then, as a last- ditch move to see if it was just the battery, I took it to my neighborhood TMobile store (who may win my business) and the guy was nice enough to test-swap batteries. Much to my surprise, the phone worked again. And then worked again with my own battery back in it! Sweet! I was happy. Took it back proceeded to get the ATT APN working, etc. (sidenote: during this time, the phone rebooted a couple times on its own - just sitting there) So I began loading apps, etc. and began to develop a bond with it. Left it off, plugged into my USB overnight to charge it, and in the morning, the green charge light was on, but the phone was completely unresponsive. Couldn't reset by pressing home+power, etc.. Nothing. But, the green light stayed on. Popped the battery, and the light went off, but the phone never came back. TMoble folks did the test swap again (gotta love 'em), but to no avail. My battery worked in their phones, but none of their G1 batteries worked in mine. The phone is now a brick. A very expensive brick. So I emailed/called BrightStarCorp again today and tried to get the RMA going again. Their support people were nothing but friendly, but their RMA person had already left for the weekend. 2:30 my time. 4:30 their time. I'm not a happy camper. I wanted to at least get an address RMA# before the weekend so I could get it to UPS and on the way. No such luck. Nobody could do an RMA except their RMA person. I asked if I could do an Advance RMA, giving my CC# and an order as collateral for the dead phone. No such luck. BrightStar's people were all very courteous and sympathetic, but I still have a brick. I was told that it will be 1-2 weeks for a replacement. Add that to this lost weekend (when it could have been in-transit), and it could very well be next year before I get a replacement. The Grinch may have stolen my Christmas. So ya, I'm not too pleased with the BrightStar's RMA policies at all, but I'm apparently at their mercy, (unless of course I want to bail on the whole idea and file a claim with the credit-card company - dunno if/how that would go, and I don't like playing that game, but the turnaround time and lost opportunity here is agonizing). My guess is that BrightStarCorp is paranoid about getting failed- firmware-update bricks, but this little guy died right there on my desk, doing nothing but charging. That I have to wait two or more weeks to get a replacement is very disheartening. We'll see what the RMA Person says on Monday. I haven't been encouraged much by people's stories of their orders taking three days just to process either. I wonder if BrightStar is just swamped, or if they're just too lean of a company for the kind of customer service most of us are used to. Oh well. We'll see. Back to the emulator with me. If anyone else runs into this issue, please reply - I'd like to compare experiences. -Clint --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
