Related
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.
Earlier, my G2 shut off on me about 5 times. -_-
First, I had it sitting in the car ,tried to take a pic but the stupid voice recognition menu kept coming up so I gave up and set it down in the console. When I got home, the phone felt warm and was.. off.
Then, I turned it on.. stuffed it in my pocket. A moment later, I pulled it out and YET AGAIN when I pushed the button I was greeted by a quick vibe and the HTC screen -_-
Then a few minutes later I ran a speed test (checking HSPA+ out in Vegas).. put it down on the table.. come back.. PHONE IS *(@#% DEAD AGAIN.
I HATE YOU! *glares at phone*
It's killing me because it either happens several times in a row, or doesn't happen for days! I've tried replacing the sim card, replacing the SD card.. moving the battery... no dice.
Maybe it's my SIM card? Would that cause it? My last phone did that -_- And I'm silly to have not yet changed the SIM lol
Good thing I have a spare sitting in my bag.
What battery are you using? Aftermarket? Is so, did you remove the sticker around the battery? If you did then make sure you place a piece of tape on the battery to avoid making contact with the metal sd card holder. The metal on metal causes it to shut down.
Sent from my HTC Vision using XDA App
Interesting. I've also been having random shutdowns (not reboots, which I've seen mentioned elsewhere, due to a hardware fault) --
HTC Desire Z, using default battery, but I'll try isolating it anyway with a slip of paper or something.
OP you on a custom rom with overclock? maybe your clocking your phone too high or low?
Also if the phone for whatever reason gets too hot or cold it will turn itself off.
Please see this forum: Phone powers down and won't turn back on w/o pulling the battery
I strongly believe that this may be an issue with the GPS and/or Google Maps. Once I have the GPS off, this has not occurred. Can anyone else try this?
I have the Bell Desire Z NAM with stock HTC Sense 2.2 ROM.
It seems to be quite prevalent, see the bottom of this review: T-Mobile G2 is speedy sequel to original Android
I think you may be onto something with that GPS note, but my phone doesnt' need the battery pulled to restart.
Also, it's running the stock firmware, stock battery (just exchanged battery and got a new SIM card yesterday, and it shut off again today.. so those aren't the problem)... so any issues I'm having are 100% stock related...
This time it shut off after using Maps so....
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
fablife said:
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
Click to expand...
Click to collapse
This was true before we received the first OTA update. Since then though the problem has been fixed.
I think it was definitely the GPS, that said I just got done with a really long phone call about this and have a replacement on the way.. but that was way too much effort AND I have to pay shipping (it's not much, but seriously.) I'm not happy that T-Mobile was THAT big a pain in the butt about getting the phone replaced with a new one in the 30 day return period.
Going by the pointers one of my close friends on sprint (that used to be on AT&T) gave me, I'd say this could've been worse with another provider.. but it shouldn't have been. The reception isn't the best so the customer service should make up for that, and it sorta does.. but it sorta doesn't.
Oh well.
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
djrajir said:
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
Click to expand...
Click to collapse
My Desire Z had the same problem and I returned it to HTC Service for repair. They said they change some cables? and a new battery. It has been nearly 3 days and I haven't experienced a single shutdown but there was one time it restarted by itself.
Yeah my only problem with that is, I am close to my upgrade date. How much did it cost. I may still do it so I can give this phone to my kid brother.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Just to update, I found that I can make it do it some times when playing with opening the hinge.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Possible cause/fix found
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Talked to tmobile CS today and was trying to get a replacement because my phone would randomly reboot and shut off. All he told me was go and pick up a new sim card. If that didn't help then they would be willing to give me a warranty replacement.
Sent from my T-Mobile G2 using XDA App
carquote said:
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobi.../513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Click to expand...
Click to collapse
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Is this possible fix something else than lining the back of the battery with a strip of paper?
whpsnp said:
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Click to expand...
Click to collapse
Sorry about that, I fixed the link and it should be working now.
Cool, thanks!
Sent from my HTC Vision using XDA App
I'm pretty sure mine is not caused by the metal strip since my battery's all proofed. I didn't have anything wrong with it until about half a month ago, and it always happened after using GPS and left it on. If I turn it off after navigation or any other app that requires GPS the phone won't go into SOD.
I switched back to CM7 RC2 around that time and starting to get the GPS no fix problem, and it could't be fixed by the dd=/dev/.... script. So I switched into Nightly 88 or something that at least I was able to get a fix but the not-so-random freezing started.
This morning I flashed the new 7.1.0 RC1 and the phone would just turn itself off (it used to just freeze and become hot), and I got really tired of it... My old G1 was much more reliable than this.
I tried the dd=/dev script again, so far after 5 min the phone is still on with GPS on....
@carcuote
Thank you! I haven't had this issue for months now. But the solution is so easy to do that I will try our anyways.
I had this issue the first month our so when I got the new phone, but went away permanently after the second month. Maybe the contacts in the battery got a little rusted? Don't know but the solution is simple enough to try...
Sent from my T-Mobile G2
I only have a couple days left, to return this phone.
Im having two huge bugs.
1. When I call people sometimes the phone calls them but the speakers never turn on, I cant hear them and they cant hear me... I cant even hear it ring...
2. Sometimes the proximity sensor goes ape bananas during a phone call and turns the screen off and on even when the sensor is next to my head.
Im using a custom rom but, Ive had both of these problems on the shipped rom as well. Is anyone else having these problems? If not Im assuming I have faulty hardware and will be returning my phone.
edit: Im pretty sure Ive gotten to the bottom of both of these issuses.
1. not being able to hear caller. This is a problem with all dk28 based roms. If you wait until you see the call is connected and the counter has started for a few seconds it should happen alot less often. If the problem still does happen usually turning on speaker phone and then back off again will remedy the situation.
2. proximity sensor freaking out. The proximity sensor works fine if you put your hand in front of it. The problem I was having is on occasion a small lock of my hair would be in between the proximity sensor and my head, this caused the sensor to bug out and turn the screen off and on. So if this happens to you just make sure the sensor located just to the right of the ear piece is point towards skin w/o hair in between it.
Most of the people on this forum, prolly have short hair and thats why they havent noticed it.
Go get it replaced before your time is up. Say that you are having issues that aren't being resolved through reloading di18
It is most likely hardware issue.
Sent from my SPH-D700 using XDA App
What android version are you on?
had the phone for a week and notice this problems, so i think i was on di18, which is 2.1 update
and currently im on 2.2.1 froyo
if no one else is having these problems, Im going to call them in an hour.
That isn't a common issue with the epic. Exchange it, remember to flash back to di18
Sent from my SPH-D700 using XDA App
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
AndrewZorn said:
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
Click to expand...
Click to collapse
hmm I guess Ill hold off another day before I return it, see if anyone else can confirm or deny these are software issues....
thx for the feedback so far.
AndrewZorn said:
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
Click to expand...
Click to collapse
This doesn't happen for me...what hardware version are you guys?
Sent from my SPH-D700 using XDA App
I have the issue with the phone calls not being able to hear them, or them hearing me.. Running 2.2.1. Did not have this problem before the upgrade to DK28.
I have not noticed any problems with the proximity switch, although every once in awhile my screen will not turn off like it is supposed too.
mrhocuspocus said:
had the phone for a week and notice this problems, so i think i was on di18, which is 2.1 update
and currently im on 2.2.1 froyo
if no one else is having these problems, Im going to call them in an hour.
Click to expand...
Click to collapse
I don't know if I am too late "chiming in" in here, but I can confirm that the call issue did not happen to me on the stock, out of the box, rom. However, every dk28 rom I have flashed has given me that issue. It is a "bug" in the leaked dk28.
The proximity sensor seems to be a hardware/software issue. That has never happened to me (the way you described it) For that - you should take the phone back before your time is up!
As someone posted earlier - flash/odin back to stock before you take it back!!
Got the same thing happening, using DK28 nebula rom, it happens like every other call.
I have experienced the call issue once after switching to 2.2 DK28, only once, and I have been running it since leaked.
as for the proximity sensor, I've heard of issues, but only seem to have an issue myself if I'm holding the phone at a odd angle.
If you have any concern at all, take it back and make them give you a new one, assuming your still in your buyers remorse period there shouldn't be any issues.
It's already been mentioned, but I'll repeat it again, flash back to DI18 before returning.
FWIW, I love this phone, very few glitches, very stable even running leaked DK28. There is not a better phone available through sprint at the moment.
Also wanted to add that the ROM I am currently using is Epic Experience 2.0.07
I think I have solutions to both of my problems, I have updated the op to reflect these events, and hopefully help other people.
Glad to hear you figured it out, I guess I just haven't noticed the first issue all that much.
I wish more people would update their posts like you did.
Sent from my SPH-D700 using XDA App
So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?
CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.
I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.
I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.
So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.
perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.
Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.