Related
Ever since the gingerbread upgrade, I've noticed that when answering calls, I have to wait 2-3 seconds before saying "hello".
Anyone else notice this?
lol I thought I was the only one that notices this
I have also noticed this issue, sometimes I have to repeat the greetings even though I already hear the other side.
This is a know gb nexus problem try the search button next time
Sent from my Nexus One using XDA App
I have to do this also. I say hello and they don't hear me. I didn't know it was a known issue.
please star the issue on the tracker
http://code.google.com/p/android/issues/detail?id=15297
same thing for me and 2 other nexus users I know
just answer, pause half a second and say Hello or Yellow or S'up or whatever you kids say these days
There's an app on XDA CM7 thread called Dewonkificator--solved my problem
It is run on rooted phones--not sure if you guys are rooted--or can run the app if not
Ken
I've had this issue on my nexus since I got it. On the shipping ROM as well as CM6, Enoms Official and CM7. It seemed that until the call timer appeared on screen during a call no one could hear me. I also never had the call wonk on CM7 when I was still using my nexus.
wastegate13 said:
I've had this issue on my nexus since I got it. On the shipping ROM as well as CM6, Enoms Official and CM7. It seemed that until the call timer appeared on screen during a call no one could hear me. I also never had the call wonk on CM7 when I was still using my nexus.
Click to expand...
Click to collapse
Exactly, I thought this has always been present too. I've always just waited till the timer starts before speaking.
RogerPodacter said:
Exactly, I thought this has always been present too. I've always just waited till the timer starts before speaking.
Click to expand...
Click to collapse
Glad I wasn't the only one. My uncle has a nexus also but I've never asked him if he experiences the same thing.
To make matters more exciting, this is NOT an issue & has been declined by Google! Check issue on Google Code.
If you're having the call delay problem (note this is not the wonk, which appears in CyanogenMod 7, that's a different problem), please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
As KoolPal said, Google recently declined this known Gingerbread bug, 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.
Maybe that's why the SGS GB update was pulled by Google.
cb474 said:
If you're having the call delay problem (note this is not the wonk, which appears in CyanogenMod 7, that's a different problem), please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
As KoolPal said, Google recently declined this known Gingerbread bug, 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.
Click to expand...
Click to collapse
I can't get behind that. My nexus always had that little quirk and not only on gingerbread. My inspire on cm7 has never had this issue.
wastegate13 said:
I can't get behind that. My nexus always had that little quirk and not only on gingerbread. My inspire on cm7 has never had this issue.
Click to expand...
Click to collapse
I don't know how to explain that. The problem has been very widely reported with Gingerbread on the Nexus One and you're the first that I've seen who says they had it before Gingerbread. I certainly didn't.
The problem has also been widely reported on the Desire and reports are starting to come in on the Galaxy. But everyone says it started with Gingerbread.
Perhaps your problem is slightly different? Or a carrier/network problem?
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
cb474 said:
I don't know how to explain that. The problem has been very widely reported with Gingerbread on the Nexus One and you're the first that I've seen who says they had it before Gingerbread. I certainly didn't.
The problem has also been widely reported on the Desire and reports are starting to come in on the Galaxy. But everyone says it started with Gingerbread.
Perhaps your problem is slightly different? Or a carrier/network problem?
Click to expand...
Click to collapse
I have the exact issue that you're describing, answer a call and the other party can't hear me for the first few seconds. I got in the habit of waiting for the call timer to appear before I started to speak and that worked for me. My nexus always did this, every single time and on every ROM that I ever ran.
wastegate13 said:
I have the exact issue that you're describing, answer a call and the other party can't hear me for the first few seconds. I got in the habit of waiting for the call timer to appear before I started to speak and that worked for me. My nexus always did this, every single time and on every ROM that I ever ran.
Click to expand...
Click to collapse
Well, that is strange. Many many people are reporting this issue as something that appeared with Gingerbread. You are the only person I've seen say they had it before Gingerbread. I don't really know how to explain that.
Looks like the bug report I started on this, expanding the issue to include all affected devices (not just the Nexus One), has been reopened. See comment #89.
http://code.google.com/p/android/issues/detail?id=16230
And someone else pointed out that the googlenexus twitter feed says the upcoming 2.3.4 update has bug fixes for the Nexus One.
https://twitter.com/#!/googlenexus
Hooray. Perhaps there is hope after all. Although I'll believe it when I see it.
Ok So my phone has done this a couple of times. Basically what is happening is randomly my phone is making a standard ringing sound of 3 or 4 beeps (or so) a pause then the beeps again. This is completely different from the standard sounds i have set on my phone and when this ringing is happening i am not receiving a call nor am i receiving a text message. so far it just happens randomly and even when i put my phone into sleep mode it still rings requiring me to take the battery out to make it stop.
Has this happened to anyone before? what dose it mean exactly?
hofuldig said:
Ok So my phone has done this a couple of times. Basically what is happening is randomly my phone is making a standard ringing sound of 3 or 4 beeps (or so) a pause then the beeps again. This is completely different from the standard sounds i have set on my phone and when this ringing is happening i am not receiving a call nor am i receiving a text message. so far it just happens randomly and even when i put my phone into sleep mode it still rings requiring me to take the battery out to make it stop.
Has this happened to anyone before? what dose it mean exactly?
Click to expand...
Click to collapse
Happened to me until a factory reset. Came back though after reinstalling my apps. You can stop it by making a call. It is a little easier than removing the battery. Still annoying though. I think it could have started after an app was moved to the SD card, so I batch moved everything to the internal storage except for some games. Has not happened for a couple days, but I would not be surprised if it came back. I wish I knew what caused this.
Sprint ZIO or Cricket ZIO?
Sent from my Zio using XDA App
Happened with me, too, on the Cricket Zio. Still searching for a solution. Doesn't seem to be a Zio specific problem, though. I read somewhere that it was happening on the Motorola Droid as well.
Mattix724 said:
Sprint ZIO or Cricket ZIO?
Sent from my Zio using XDA App
Click to expand...
Click to collapse
weeel the picture under my name says sprint soooo. lol
The XDA app doesn't show it. Please don't insinuate that anyone here is stupid. I, for one, don't appreciate it, and neither does anyone else. WE are trying to help YOU, and we ask questions for a reason. A clear, simple answer is what you should give when asked a question IF you want our help.
Sent from my Zio using XDA App
Quite ringing sound
This happens on the Cricket zio as well. It normally happens when you are in a low signal area for any extended period of time. Normally rebooting or making a phone call will stop it. As to why it is happening I have no idea however I do recall this was a problem on one of the old kyocera slider phone I had in the past.
Is there any point in digging into this? It's beginning to happen to me a lot (as my coverage at home sucks despite living in downtown Charlotte).
Every problem has a solution but I'm wondering if the new OC'ed kernel will eliminate it.
One can only hope.
Sent from my Zio using XDA Premium App
mattpedigo said:
despite living in downtown Charlotte.
.
Click to expand...
Click to collapse
Charlotte NC ? I live in Kannapolis.
pomeroythomas said:
The XDA app doesn't show it. Please don't insinuate that anyone here is stupid. I, for one, don't appreciate it, and neither does anyone else. WE are trying to help YOU, and we ask questions for a reason. A clear, simple answer is what you should give when asked a question IF you want our help.
Sent from my Zio using XDA App
Click to expand...
Click to collapse
WOH calm down sir. i don't appreciate how you are treating me right here. i guess you think everyone on this site has used the XDA app. well i have never used it before. therefor i did not know that thos images showing whos carrier is being used weren't shown.
you are a very rude person.
hofuldig said:
WOH calm down sir. i don't appreciate how you are treating me right here. i guess you think everyone on this site has used the XDA app. well i have never used it before. therefor i did not know that thos images showing whos carrier is being used weren't shown.
you are a very rude person.
Click to expand...
Click to collapse
Can we stay on task here and stop with the petty squabbling. Nobody cares how anybody reads the forums but being a smart-a$$ about it will ultimately result in this sort of argument.
Fact is, that we're trying to address an issue here. And to that point, my phone is still making the ringing noise, even with the new OpenZIO ROM. How can that be?
My guess is that the ringing noise is tied up somewhere not on the typical hard-drive of the phone. Kinda like a beeping mechanism on a computer motherboard. And since somebody reported that it happened on an older Kyocera phone, that only furthers my theory in this.
Evidently, it seems to be triggered in poor reception.
mattpedigo said:
Evidently, it seems to be triggered in poor reception.
Click to expand...
Click to collapse
This much I know is 100% correct. The first time it happened to me and my wife we were traveling to the beach and this happened while we were in "Dead Zones" and now it happens to me on a daily basis on my commute to and from work. I drive through a lot of "Dead Zones".
Fate43 said:
This much I know is 100% correct. The first time it happened to me and my wife we were traveling to the beach and this happened while we were in "Dead Zones" and now it happens to me on a daily basis on my commute to and from work. I drive through a lot of "Dead Zones".
Click to expand...
Click to collapse
A lot of dead zones in the Charlotte area? Where are you commuting to and from?
I have also had this issue a couple of times while running rooted 2.2.
I too was in a poor signal zone. An interesting fact is that when I would adjust the volume while it was making the funny sound, it would say that it was adjusting call volume not ringer volume. It was a while ago since it happened last, but I'm also pretty sure the sound comes from the ear speaker and not the louder back speaker, which is why the sound is so soft.
I'm having the same issue!
I'm having a hard time isolating what application could be causing this. It probably doesn't help that I'm EXTREMELY new to this forum.
also having this issue
this happens to me also in a low signal area.. it happens at 5am and again at 9pm. i'm home way before 9pm so i don't know what the signifigance of that may be?
You have all been hax0rd!!! Mwuaaahahahaa!!!
Just kidding.
I have never had this issue before. You could try installing my ROM to see if that fixes the issue?f
**edit: just read upwards -- appears that someone has already tried installing the ROM.
This leads me to believe that it could be a hardware issue.
Perhaps you can take it in for an exchange?
ROM won't fix it. I was having the issue on stock 2.12 as well. It did not start till the update so has to be a bug in the OS.
Sent from my Zio using XDA Premium App
Take your phone back to cricket for an exchange (provided you can reproduce the sound to a rep).
Be sure to flash a stock rom to ur phone or they wont touch you.
Has anyone experienced this problem on the RAZR i (but possibly not realised it or thought it was just occasional) with regards to people phoning you, you saying hello and them clearly not hearing you as they don't respond. Only when you say 'hello' again is it quite clear they didn't hear anything at first as they don't act surprised or confused.
It must be 1-2 seconds or so at most, but it's quite annoying and seems to be happening every time I answer. This makes me suspect it's the phone, not the network (Orange/EE if anyone cares).
I thought it might just be the person at the other end not listening, but I've since asked people who didn't respond if they heard my first hello and they say no - so it's as if the mic isn't activated straight away.
Before I report it as a bug to Motorola, I really want to know if anyone else has suffered the same problem?
mee to
81.5.32002.XT890.Retail.en.EU
Rooted with Motofail2go
Never noticed it but i'll take notice tomorrow to see if my GB firmware also does it.
wozn said:
Never noticed it but i'll take notice tomorrow to see if my GB firmware also does it.
Click to expand...
Click to collapse
So you know, my phone is;
81.5.31002.XT890.Retail.en.GB
I have exactly the same problem, but on my 2 years old Desire, and I've only had it since I installed the latest version of a custom ROM, so there is a very big possibility, that it's just a software bug. But I agree, it gets annoying as hell, so it would be great for as many people with this problem to let Motorola know about it, so they fix it as soon as possible.
Can't wait to get my hands on this beauty, by the way!
Mine is fine. Done a reset?
I checked mine out as not noticed a problem. Turns out to be fine. Hope you sort the issue.
Sent from my XT890 using xda premium
mine doesn't work anymore, i m downloading 8.1.5.40002.Retail.en.EU to test
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39892
it's pretty sad that there's only 45 votes on this issue. Here's a hint: bugs won't get fixed if people don't speak up about them. And don't think your voice exactly resonates here on XDA.
Just star it, and leave a comment. Doesn't have to be anything long winded either.
Sent from my Nexus 10 using xda premium
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Troute said:
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Click to expand...
Click to collapse
While agree it's not the end of the world, it's a complaint I see often here in kernel and ROM threads. While a lot of it is due to wonky behavior due to OC (either CPU or GPU), it's really just exacerbating an issue that is already present.
Besides, UI bugs are some of the most prevalent and immediately noticeable to more "common" end users. While functionally it's not debilitating, it's an aesthetic scar that doesn't need to be there.
Sent from my Nexus 10 using xda premium
Hmmm.. So I assume it doesn't matter that I need exactly 15 seconds everytime I get a notification to pull down the status bar, caused by flipbacks. Okay I'm like 1000% sure Google noticed it anyway, cause its on most devices, also 100% stock ones (like me) so...
Sent from my Galaxy Nexus using xda premium
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
jbdan said:
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it would bounce back after a reboot one time, I wouldn't care, but its always there, it doesn't matter what I do, it bounces every time... So its a bit annoying.. This is the only thing which sometimes makes me want to throw the 7 at a wall...
Sent from my Galaxy Nexus using xda premium
Thanks OP, have added my star.
I had not noticed this problem but I was intrigued.
I could not duplicate the problem, but I am using Apex launcher, not the stock launcher. Does the problem occur in all launchers? Also I am not using the stock ROM.
I wonder if this problem happens with only some units, or perhaps it relates to those user's expectations. Maybe they expect their device to react more quickly than it is able to.
Far be it for me to be dismissive of people's satisfaction with their devices, but that bug-report thread has a lot of problems. It contains over-reaching claims and supposed knowledge of the problem's causes and solutions.
Again, I don't write off these people's unhappiness but I personally would not star that issue.
i too have this problem when on stock rom..now on PA beta 9 with m-kernel, the problem still exist...and it's very annoying...i even thought there was a problem with my touch screen panel and sent it to asus for repair but when i got it back, the same problem still remains..
Not starring because it does not bother me.
Life has too many other issues to worry about having to occasionally re-swipe.
Now pop-up ads in the Yahoo app could get me started...
squshy 7 said:
Come on guys, with all the members here and all the people who like to complain, it's pretty sad that there's only 45 votes on this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
I noticed this issue minutes after pulling this thing out of the box, this might not bother you people who casually use their tablets, but top those of us who have been using android since the G1 notice this. It bothers me so much that I am considering taking this junk back and using the money to get a real tablet from Samsung.
This issue is so annoying to me, I not only notice it on the stock launcher, but also Nova and Apex. Now, the launcher I can deal with, but where I becomes a deal breaker for me is the browser, whether it's chrome or the stock browser in CM10. Trying to scroll around the OS that requires some flicking reminds me of trying to flick scroll on a resistive touch screen, I think that best describes the issue.
I just wanna know if it's fixable through a software update or a hardware problem, cause if it's the latter, this thing is going back, and that's too bad because it was a Santa gift, so I'll have some explaining to do.......
compact_bijou said:
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
Click to expand...
Click to collapse
As I stated (not in precise terms sorry) in the OP, it would be a mistake to think that xda threads are the first place companies like Google and Asus check to see what issues people are having. They have issue and bug trackers for a reason. The universe does not revolve around our little community.
Also, this issue pertains to the general consensus that touch screen issues (like bounce back) have become exacerbated on 4.2 and above. Not anything regarding physical QC issues (though, to be fair, may very well be the root cause, but that is an entirely different issue; the fact of the matter remains that anecdotally it appears the touchscreen responded better on 4.1.2)
And besides, I'm just looking out for the well being of this device's future. Reporting bugs on bug trackers is important to these developers.
Sent from my Nexus 10 using xda premium
to be honest, this annoys me a lot.
starred and commented.
This really annoys me as well. I voted and commented. Hopefully they can get this fixed soon. Otherwise I might switch to CM10.
Sent from my Nexus 7 using xda app-developers app
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
leonclement said:
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
Click to expand...
Click to collapse
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
farmerbb said:
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
Click to expand...
Click to collapse
Yea the notification bar is better on 4.2.2, but the launcher still does it, nova prime does it too, and even when on dolphin or boat browser sometimes when you flick it will scroll nicely & sometimes a flick wont move the page much at all, weird and annoying, would be a much better experience if it was fixed!
This is a huge issue for me. Is there a way to increase or decrease sensitivity? Maybe that would help.
Sent from my Nexus 7 using xda app-developers app
Interesting, I thought I was the only one who had noticed this. Don't know why I haven't seen this thread earlier.
For me I solved this by using apex launcher, somehow you never get those annoying jumpbacks. I tried nova launcher as well but it worked as bad as the original launcher. Going to star tomorrow.
Sent from my GT-I9300
I've reported on this a few times in the rom threads, but I figured it'd be a good idea to post here as well. Sounds in the Google Edition fade in when having been idle for a time. This is most easily observed in the dialer. When you press a number, you can hear the sound fading in, instead of presenting at full volume. This is also very obvious in the game "What's the Phrase?" where all sounds suffer under this problem.
I took a brief logcat and hopefully captured all the events associated with it. Would a developer be able to delve into it and see why sounds are not presenting at full volume immediately?
This sounds oddly similar to the volume drop issues people have observed on CM/AOSP-based ROMs. Sorry I don't have more info than that.
Sent from my One using Tapatalk 2
michaelalias said:
This sounds oddly similar to the volume drop issues people have observed on CM/AOSP-based ROMs. Sorry I don't have more info than that.
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
It's not. The only happens when the speakers have been idle. The other happens even if the speakers haven't been idle.
Sent from my One using Tapatalk 2