Just received a new T-mobile Wing today and I am underwhelmed by the stock rom. I am considering reflashing the rom but I have a question concerning the battery. My previous phone was T-mobile Dash which I also reflashed the rom on. However because of the reflash, something with the charging program got messed up which resulted in the phone shutting off suddenly when listening to music, using the wifi, or even making a simple phone call. A couple people on the Dash side of this forum experienced the same problems. So my question is, has anyone experienced a similar problem when reflashing their Wing/Herald to any of the custom roms available?
nope. we've never experienced that.
sometimes the devices turn off unexpectedly, but its rare and seems to be device specific
Yeah Never happened with us...Maybe you and the others got a "bad batch" of dashes haha...But the Wings alot better than the dash...Ive had both!! Welcome to the Herald Side of the Forum!!
The Stig said:
Just received a new T-mobile Wing today and I am underwhelmed by the stock rom. I am considering reflashing the rom but I have a question concerning the battery. My previous phone was T-mobile Dash which I also reflashed the rom on. However because of the reflash, something with the charging program got messed up which resulted in the phone shutting off suddenly when listening to music, using the wifi, or even making a simple phone call. A couple people on the Dash side of this forum experienced the same problems. So my question is, has anyone experienced a similar problem when reflashing their Wing/Herald to any of the custom roms available?
Click to expand...
Click to collapse
Yeah, never had any problems with ANY of the roms posted here.
Hi.
I've got myself a Tattoo about a week ago and are mostly happy with the phone. However, the last two days I've been comming in late for my job. The reason for this is the Tattoos power saving. When the alarm shuld go off the phone is just silent and dormant. When I unlock the screen the alarm goes off happily.
This seems like the same problem as I had with my HTC Diamond, where SMS'es was not notifyed until the user woke the phone up. The problem there coud be fixed by a regedit. But regedit is, of course, out of the question on a Android
Do anyone have a this same problem as I have, and does anyone know about a fix. I've checked HTC.com and there is no official patch for this.
Best Regards
Tommy
Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).
Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.
What carrier are you on?
this happens to me too.its so annoying. im on att
Can't find the thread but it was pretty long.
nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.
This sounds like an att problem not a nrsux one problem
I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.
I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One
Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.
I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.
Sounds more like a network issue than a hardware issue, IMO
This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.
I have a samsung vibrant, but my wife has the G2, so i haven't been following this forum too closely. I have a problem i'm hoping someone can shed some light on. I tried a search with no luck, so sorry if this has been discussed and/or fixed.
I rooted my wifes G2 for her a couple of months back and installed what ever release candidate was available for CM. After a while the phone had a few bugs that started rearing their ugly heads (as expected on an RC release). So when CM6.1 stable dropped I upgraded, but after a while the same bugs were still there and same with CM6.1.1.
The bugs that my wife and i have been noticing are the alarm doesn't vibrate when set to just vibrate, sometimes random notifications will sound but there will be no text or email (this mostly happens when playing slacker radio in the car), and sometimes the screen will become sporadically unresponsive when web browsing.
Has anyone else had these issues? I've tried doing all sorts of searches on google and here on xda but i haven't been able to find any thing about this. What should i do? full wipe? flash a different rom? trying to avoid that since its a huge pain in the ass to restore all her apps and texts.
Any help is appreciated. Sorry if this has been discussed, but i did try to search. also any suggestions on alternative roms would awesome as well. if it were my G2 i would have already tried them all. thanks!
Not sure if this will help but after I reformatted my micro SD card and copied all the data back to it, my G2 started making random sounds.
I went in and checked all the notification sounds and they were all set to default, I reassigned them the way they were before and that seemed to fix it...
Try it and see.
ok thanks. i'll give it a shot tonight. if that doesnt work i think i'll just do a full wipe and reflash...or try a different rom
thanks again for the response
Hi,
I've looked through as many posts as possible, and although there's many with similar problems, I've not found the same as mine.
I've had my HD2 for about 8 months and no problems at all. It came with a pre installed Energy ROM and I also was running SPB Mobile Shell etc. Anyway, I recently dropped it on a plane journey to the US, so it never fell far and the headphones were plugged in so it landed on it's head with a minor shunt but was still working 100%. Then I found that when I was using WinMo it would keep freezing up however I had Android on the SD card so I could still use that without freezing. Now I'm back in the UK, I keep getting random black screens, no response or lights from the buttons and no light comes on if I connect to mains/USB. If anyone calls me, they get the ringing tone but again nothing from my phone.
I backed up my contacts etc, did a hard reset and I get the same problem. So I thought perhaps it's the OS so I tried flashing another energy ROM and the same problem again, black screen. I thought then since Android worked, then I'll use that in the mean time, but it happened with that too.
Could the slight fall have killed something inside? When it's on, there's no problem at all, it only seems to die when sleeping. So is there anything else that I can do with it or would it be best to see if it needs serviced.
Any help would be most appreciated. Thanks.