Well, as you can see from the video below, the guy set the highest volume, then place the smartphone near the Galaxy Nexus and the Galaxy Nexus respond to it. This is CLEARLY hardware issues. This could be the real reason Verzion still haven't release the Galaxy Nexus yet.
www.youtube.com/watch?v=BIFRYY25fDo
Thanks dnlsmy.
www.youtube.com/watch?v=y_mO_K7OYR0
Update 1
Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk
Update 2: Lee Johnston explain of "volumegate" issue
Let's talk about the Google Nexus "volumegate" issue.
Today Google said that they have fixed the problem in software, and that a fix is coming.
I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.
I'm a Systems Engineer and also a Developer. I deal with things like this every day.
What we have here is indeed a hardware issue, in that the radio interference is coming in through the radio hardware.
However things like this can be fix fairly easily in software. It's called debounce.
When you monitor an electronic input like the buttons on a phone there is always noise and flutter even when you just press the button. If testing by Google has shown that they just need to turn up the debounce time (the time which an input must exceed for it to be determined to be a genuine press) then it will more than likely just work and no one will ever see ti again.
Like I said I deal with this kind of thing every day, it's not a big deal as long as your debounce time is not excessive. But noise happens down on the order of 1 to 40 ms, real inputs when you press a button last from 100 or 200ms if you tap the button, up to seconds if you hold it down.
This is nothing like Apple and the iPhone 4 antennae problems that could not be fixed in software. I'm sure everyone will see in due time, the problem will be fixed, and the dust will blow over.
And people will be saying "wow, I was wrong, Google rocks
Cheers,
Lee
Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!
Yeah, and for further proof, he does it in the bootloader screen of the GNex
http://www.youtube.com/watch?v=y_mO_K7OYR0
This seems like it's a hardware fault entirely.
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
well you're mistaken then. the test is not inconclusive at all.
martonikaj said:
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
Click to expand...
Click to collapse
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
no software patch can fix this. the phone has inadequate RF shielding.
My bionic which I know is a different device does something similar. When I put it next to my corded work phone and the bionic switches to 4g it causes the speaker on my work phone to male a distortion noise even when it is hung up. So I can see where the radios cause some sort of interference on these 4g phones
Sent from my DROID BIONIC using Tapatalk
TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Would that have anything to do with the nfc chip?
DammitCubs said:
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
please read this post
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
dadsterflip said:
Would that have anything to do with the nfc chip?
Click to expand...
Click to collapse
it has nothing to do with the NFC chip or aerial
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
chandlerweb said:
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
Click to expand...
Click to collapse
yes, exactly - the internal radio on the Galaxy Nexus is causing the problem. that is why those of us who have been affected by this hardware defect have been so vocal about it.
vash1053 said:
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Click to expand...
Click to collapse
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
This is why I effing hate Samsung they always screw something up... Looks like the g-nex us going to be a big failure.. Hint hint goggle you should of stick with HTC to make your nexus line phones
Danrarbc said:
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
Click to expand...
Click to collapse
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
oscillik said:
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
Click to expand...
Click to collapse
Yeah, figured it was. And trying to work around it by analyzing radio signals to detect if it is a real button press or interference would be very hard too, they're going to have to do something about the phones already sold - this is a huge issue.
This is indeed bad. I guess this makes my decision easier about getting one from Hantec. Hopefully the Verizon version doen't have this issue since it uses different frequencies however, this may be the reason they haven't released it yet.
Nexus exchange?
The fact that Samsung have begun replying to peoples comments on their UK Facebook page asking for an email to be sent to technical support including their home address suggest they intend to replace the phone. It`s a great phone and it should never have happened but it`s how Samsung/Google deal with it.
For those who haven’t read the Facebook comment from Samsung :
Samsung UK Hi *, to ensure we investigate thoroughly could you please send the following details to [email protected]: Serial Number, IMEI number, date of purchase, place of purchase, details of issue
your name, address and phone number. We will get in touch as soon as we have more information.
Related
There are a few threads on the various Froyo releases, their features bugs etc. but nothing that touches on Froyo's GPS issues specifically.
I'd like to know whether anyone has successfully changed the 'look ahead' behavior that all the Froyo firmwares come with so far.
For those who have not experienced, i.e. not YET noticed this 'feature', here is a brief description:
On Froyo the GPS is showing you exactly where you are even while driving at speed. There is no delay whatsoever. All is well while you are going in a straight line.
The problems begin when you either stop abruptly or take a sharp turn. It then takes the GPS up to a few seconds to come to terms with what just happened. I can only assume this is due to some software component 'smoothing' the path by making up positions, i.e. looking ahead.
I uninstalled JPH and JPK. GPS doesn't do me any good when I see myself still driving down the same road after I took a right turn 5 seconds ago. JM8 and a number of other Eclair firmwares do not suffer from this.
Has anyone successfully 'downgraded' the GPS component of Froyo? Is this even possible? Is there a way to disable the 'look ahead'.....somewhere hidden in settings or some hidden menu?
ewok666 said:
Has anyone successfully 'downgraded' the GPS component of Froyo? Is this even possible? Is there a way to disable the 'look ahead'.....somewhere hidden in settings or some hidden menu?
Click to expand...
Click to collapse
Did you turn on the "Use Sensor Aiding" feature? That's new in Froyo. Try turning that off. It's in the Location menu.
hardcore said:
Did you turn on the "Use Sensor Aiding" feature? That's new in Froyo. Try turning that off. It's in the Location menu.
Click to expand...
Click to collapse
Thanks. I thought I had that disabled. Is this on by default? I'll give that a try next time I load a Froyo firmware....if there was a quick way to nandroid back without an Odin restore, EFS fixup plus all the Voodoo conversions that would be sooner rather than later ;-)
ewok666 said:
Thanks. I thought I had that disabled. Is this on by default? I'll give that a try next time I load a Froyo firmware....if there was a quick way to nandroid back without an Odin restore, EFS fixup plus all the Voodoo conversions that would be sooner rather than later ;-)
Click to expand...
Click to collapse
The default is off
It greatly helps when it's on I think
Arkanius said:
The default is off
It greatly helps when it's on I think
Click to expand...
Click to collapse
Isn't it meant to aid while walking? I can see that this may be causing when driving.
Well, there is absolutely no reason this option to decrease performance.. At least shouldnt be, unless Samsung screwed something up as usual. (which actually may be the case)
I had mine set to "off" by default. There is next to no difference while driving.
xan said:
Well, there is absolutely no reason this option to decrease performance.. At least shouldnt be, unless Samsung screwed something up as usual. (which actually may be the case)
I had mine set to "off" by default. There is next to no difference while driving.
Click to expand...
Click to collapse
As I said in the OP, I've always had the issue that GPS took seconds to realize that I changed direction or suddenly stopped. I'm just guessing that something that is intended to help stabilize GPS at slow speeds (walking, swimming with the dog, etc.) might cause a similar effect while travelling in a car.
swimming with the dog? I shat bricks ;d
Anyway, yes that right. Since its like phone is calculating from the sensor (compass, g-sensor -> speculating here) reads the approximate direction and pace you are moving at. It *might* be a problem with g-sensor read, becouse I find it quite flaky (using gps testing utilities exposes its terrible lag and low sensitivity)
BTW is it better after disabling it?
xan said:
swimming with the dog? I shat bricks ;d
Anyway, yes that right. Since its like phone is calculating from the sensor (compass, g-sensor -> speculating here) reads the approximate direction and pace you are moving at. It *might* be a problem with g-sensor read, becouse I find it quite flaky (using gps testing utilities exposes its terrible lag and low sensitivity)
BTW is it better after disabling it?
Click to expand...
Click to collapse
Well, there was a guy in another thread who claimed his Galaxy GPS was spot on. To proof that he uploaded a track of his walk with the dog and it clearly went right through the river a couple of times........I thought THAT was hilarious! ;-)
I might flash Froyo once again and play with that setting......still hoping that the Galaxy CAN do acceptable GPS. :-|
i'm mostly happy with the gps software on JPK (compared to JM8 which was already better than "official")
but the lag you're speaking about is killing me. there's waaay too much delay. sure it makes nice recorded tracks, but using it you'll see its crap
going to try my track with aiding stuff off tomorrow although im not sure its going to help
Well i am using JPK and the MOTONAV is running......ok, but i got "GPS LOST SIGNAL" every 10 minutes and the map jump around, after 10 seconds it will find signal again and back on track. anoying.
I borrowed an iphone 4 to test that thing's GPS and compare it to the Galaxy.
I have attached the Horror kml track file. It's no better, if not worse, than the Froyo stuff. I certainly did NOT expect that!
The kml can be viewed with Google earth and other GPS programs.....
And for the record....I did drive ON the road at all times ;-)
There is a new trend obviously. The more expensive the phone, the more messed up the GPS. LOL
What a total fail for the high-end devices these days.
bilboa1 said:
i'm mostly happy with the gps software on JPK (compared to JM8 which was already better than "official")
but the lag you're speaking about is killing me. there's waaay too much delay. sure it makes nice recorded tracks, but using it you'll see its crap
going to try my track with aiding stuff off tomorrow although im not sure its going to help
Click to expand...
Click to collapse
did not help ;D
bilboa1 said:
did not help ;D
Click to expand...
Click to collapse
Bummer......
Maybe they looked at the iPhone and thought it was a great 'feature'.
Oh man, if 2.2 firmware didn't get the GPS issues resolved, then it's pretty much useless for me. I'm happy with the overall phone as it is, minus the GPS issues.
stan28 said:
Oh man, if 2.2 firmware didn't get the GPS issues resolved, then it's pretty much useless for me. I'm happy with the overall phone as it is, minus the GPS issues.
Click to expand...
Click to collapse
The GPS issues will NEVER be resolved - it's a hardware problem. You probably just won't ever get Samsung to admit it, now they try those lame "sensor aiding" dirty fixes, but that's just another proof that it's a hardware problem - why else would they spend time doing the sensor aiding?
EDIT: I hope Samsung proves me wrong
MoWa22 said:
The GPS issues will NEVER be resolved - it's a hardware problem. You probably just won't ever get Samsung to admit it, now they try those lame "sensor aiding" dirty fixes, but that's just another proof that it's a hardware problem - why else would they spend time doing the sensor aiding?
Click to expand...
Click to collapse
PROVE IT!!! You are presenting hypothesis as fact, and that might be acceptable in places such as Digg, but it is inappropriate on developer websites.
Also, how do you know that sensor aiding required much much work? After all, it's predictable polling from already working/predictable sensors, unlike GPS sensors which pick up a fuzzy idea of where you are, is affected by satellite coverage, etc.
Sensor aiding can assist even GOOD GPS receivers indoors, tunnels and in areas where signal can drop (heavy trees, huge skyscrapers). Yes, even on Garmin units, this can be handy. We all know that the faster you travel the greater inaccuracies which are incurred, and this can help reduce inaccuracies in those scenarios. There are plenty of reasons to implement this functionality, and not all point towards bad hardware. Samsung probably has a few groups of programmers being thrown at different problems, because programmers aren't scalable, and there is a limit to the number of developers which can work on a specific issue/bug/improvement.
andrewluecke said:
PROVE IT!!! You are presenting hypothesis as fact, and that might be acceptable in places such as Digg, but it is inappropriate on developer websites.
Click to expand...
Click to collapse
I can't prove it - but I can use my brains to put together the circumstantial evidence. Sorry if that isn't good enough for you.
MoWa22 said:
I can't prove it - but I can use my brains to put together the circumstantial evidence. Sorry if that isn't good enough for you.
Click to expand...
Click to collapse
You SAID "The GPS issues will NEVER be resolved - it's a hardware problem", and spreading random rumors like that makes XDA appear unprofessional, and benefits nobody. I've just simply noticed a recent trend towards guesses being slowly changed to fact here in XDA developers, and I'd like to try to reduce the frequency of that happening
As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
I have called about this issue. First time around Verizon said take it back get a new one. So I did that and so on happened 2 more times same issue same results. Now on my 4th one its starting again. So verizon said it was Samsung and Samsung said Verizon.
So I was hoping for some input on what direction I should go now.
Sent from my Galaxy Nexus using XDA
After so many replacements, I can only imagine that this is happening because of your location?
Sent from my GT-P7510 using xda premium
My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA
srh21 said:
My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
srh21 said:
As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
when you said high pitch noises, do you mean that during a call you can hear a buzzing sort of noise when people speak? I get that on my nexus too, it's slightly irritating but I'll live with it, better than spending time to unroot it, go back to stock and then waste a whole week in the service centre.
akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App
Powell730 said:
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
That is correct. Audio outbound gets garbled and then lost completely. This is the worst bug of this phone. I can't count how many phone calls where I'd have to hang up and redial because the other person couldn't hear me anymore.
Sent from my Galaxy Nexus using Tapatalk
I'd blame the carrier, as i'm on Orange UK, and I use T-Mobile UK as well, and call quality both ends, is excellent
Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.
akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
Not sure how it could be user error as well. This isn't my first phone.
srh21 said:
Not sure how it could be user error as well. This isn't my first phone.
Click to expand...
Click to collapse
KWKSLVR said:
Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.
Click to expand...
Click to collapse
I pretty much tried everything. New sim cards, using it with nothing installed (stock) I'm super bummed I been waiting on a nexus device to hit Verizon for a while now. I'm not sure how much longer I'm going to put up with this.
What about rolling back onto 3G? Are you on the fringe of LTE connectivity at all?
I know a lot of people talk about call quality. Frankly, I haven't experienced any issues and no one has told me that it sounds like crap (and believe me, I have friends that would mention it, we're a HARSH bunch). I don't doubt they exist, and you certainly don't sound like 3/4ths of XDA that are overly dramatic whiners. Out of curiosity, roughly how many minutes a month do you talk? Any chance that it's just an issue where, well you know, the more you do something the more opportunity to experience something that goes wrong? I used to talk a ton for work, like 3000+ minutes a month. I had a lot more dropped calls then than now, know what I mean?
You know what I'd do, which Verizon would HATE but, hey, you are the customer. I'd take you and your wife's phone into Verizon, and have them flip the numbers around. Keep EVERYTHING else about the phones the same. Her apps stay, your apps stay, just swap the numbers around and try her phone with your regular use for maybe 3 or 4 days. If you can replicate the problem while she doesn't experience the issue at all on your phone, then you can probably narrow it down to either the tower your on, or maybe the phone really is just buggy after you've been on it for a while.
Every so often I'll have a long conversation and a call gets dropped, but I've never not been able to hear someone or them not be able to hear me. Like, they're the typical issues that you could assign to either being a tower pass off problem or the nature of LTE long before the phone (on either my end or the other person's end). But, like I said, that's a rare occurrence for me.
What version of ICS are you running? I had this same problem, specifically and most frequently the one where the audio cuts out of a call, sometimes it'd do it and force me to re-call my girlfriend as many as 3 or 4 times in an hour.
What fixed it was flashing ICS 4.0.4 released from Google themselves (if I waited for Verizon to do it I'd probably be single by now). This fixed it for me immediately right out of the gate. I've had the other issues you spoke of every so often but the audio cut out was constant. This fixed everything. Been running for a while without problems (month or so maybe?).
Eh...you didn't flash it straight from Google. At best, you flashed it straight from the Verizon/Google ota server the test ota is on
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
From here?
http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip
try a different SIM/Network. you'd be suprised
IINexusII said:
try a different SIM/Network. you'd be suprised
Click to expand...
Click to collapse
What network do you suppose he would try?
Sounds like the phone is doing you a favor. If I had to talk to my girlfriend for an hour a day I'd want my phone to kill itself.
lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
Did not fix the microphone going out issue for me :-( I just flashed the 4.0.4 leak on Tuesday hoping it would alleviate this problem, but I had the mic go out about 15 mins into a call last night. Same story as with stock, had to hang up and re-dial to continue the conversation.
Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.
[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]
People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.
However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.
So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.
This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.
If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.
It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.
[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]
Thanks!
I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
Sent from my Galaxy Nexus using XDA
TLDR: I kept having people telling me that I sounded like a robot.
Sent from my Galaxy Nexus using XDA
I had this problem on back to back to back phone calls this morning. Horrible.
Sent from my Galaxy Nexus using Tapatalk
My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.
Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
I had the same problem on my 2 rogers GNs(GSM version)
after I upgrade my baseband to i9250xxkk6, the problem gone
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
I'm in Raleigh, NC.
I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).
After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.
I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Click to expand...
Click to collapse
I can't help but be reminded of Steve Jobs.... "You're holding it wrong!"
I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.
gabe23 said:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
Click to expand...
Click to collapse
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!
adrynalyne said:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
Click to expand...
Click to collapse
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?
The only fix is going to be a software update from el goog. can't wait for it!!!
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.
Good to know I'm not alone, Minnesota is currently winning! :-\ :-(
AnotherHiggins said:
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Click to expand...
Click to collapse
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.
I have the same problem on the GSM version. Also Raleigh, NC.
Go here and see the issue. http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
I don't believe this is the fault of any ROM but actually a problem with Android/Google. So post in this thread and maybe when Google wakes up one day they will fix the issue. It killed me to see they rate the issue as Medium and not critical or at least Major!
this is a radio issue specific to quality control by samsung. issue has been addressed method of fix is to call in for replacement device
Thanks for the input, can you please supply me the official Google or Samsung news that this is a bug by Samsung and we should RMA it.
gaming09 said:
this is a radio issue specific to quality control by samsung. issue has been addressed method of fix is to call in for replacement device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=26009296#post26009296
I found your post and sorry to say but I don't buy it. Google has already stated they know about the problem with data drops, I posted the actual thread tracking the issue. I suggest that others post there too and say they have the problem. More posts = more attention. There is absolutely nothing there saying Samsung is at fault. But please, I am open to any ticket or comment from Samsung acknowledging that my phone is a lemon.
Qualcomm makes the radio in the Nexus. Don't see how Samsung is at fault at all.
Not to mention, Google chose it and closely monitors development.
Sent from my Galaxy Nexus using XDA
noticed the problem the first time i accessed the play pen. i have had my phone for only a few hours.
I just spoke with a Samsung rep over their Live Chat line on their site. They have no such issue with radio's for the Nexus model. No recall and no news announcements about this issue. She said to me that they are unaware of any problems of data drop with the phone, she apologized for the problems and suggested that I contact Google about the problem. I wanted to confirm after that guy responded here about RMA'ing the phone. Did not make any sense and there are LOTS of people with the problem. It all started with 4.0.4. I imagine we will see a fix for this issue soon. Like I said, more people who post they have the issue the faster it will get resolved.
Flukester69 said:
I just spoke with a Samsung rep over their Live Chat line on their site. They have no such issue with radio's for the Nexus model. No recall and no news announcements about this issue. She said to me that they are unaware of any problems of data drop with the phone, she apologized for the problems and suggested that I contact Google about the problem. I wanted to confirm after that guy responded here about RMA'ing the phone. Did not make any sense and there are LOTS of people with the problem. It all started with 4.0.4. I imagine we will see a fix for this issue soon. Like I said, more people who post they have the issue the faster it will get resolved.
Click to expand...
Click to collapse
lots of people is relative. usually people with problems scream the largest, but what is the % of those people in relation to the total number of phones sold.
samsung/google are the only ones that know that magic number.
Has anyone tried this? I will give it a go when I get off work....
Edit.sorry wrong link
http://forum.xda-developers.com/showpost.php?p=24545086&postcount=73
Sent from my Galaxy Nexus using Tapatalk 2
Smokeey said:
Qualcomm makes the radio in the Nexus. Don't see how Samsung is at fault at all.
Not to mention, Google chose it and closely monitors development.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Actually, Samsung has branded the CDMA radio, and VIA makes the LTE radio. Not sure who does the GSM one.
It might have licensed Qualcomm tech in it, but they arent Qualcomm radios.
Zepius said:
lots of people is relative. usually people with problems scream the largest, but what is the % of those people in relation to the total number of phones sold.
samsung/google are the only ones that know that magic number.
Click to expand...
Click to collapse
the problem is pretty rampant and probably more so for GSM users. I doubt Samsung can tell you how many GSM vs CDMA user there are. I don't just frequent this site, I frequent dozens of others sites and the problem is reported on all sites. That tells me MANY people are having the problem. I'd like to keep this thread on topic rather than detract from the problem at hand. Thanks.
Flukester69 said:
Go here and see the issue. http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
I don't believe this is the fault of any ROM but actually a problem with Android/Google. So post in this thread and maybe when Google wakes up one day they will fix the issue. It killed me to see they rate the issue as Medium and not critical or at least Major!
Click to expand...
Click to collapse
You know this article was addressed in IMM76I, right?
adrynalyne said:
You know this article was addressed in IMM76I, right?
Click to expand...
Click to collapse
All I know that I'm on 76I and still getting massive signal drops. Very frustrating. Tried dozens of different ROMS, kernels, radios, clock speeds, etc.
Sent from my Galaxy Nexus using XDA
What if you go back to 4.0.2?
Have the same issue as those that are complaining about the data drop issue.
1, after upgraded to stock 4.0.4, the reported issue starts happening.
2, I tried custom ROM, AOKP. Same issue.
3, I reverted back to 4.0.2 stock. The issue does not persist.
4, I upgraded back to 4.0.4 stock. The issue exist.
5, I flashed AOKP again and installed GetRIL from Google Play. Downgraded the RIL to 4.0.3. Issue seems to be resolved.
For about a month now, I haven't noticed data drop issue. Seems to be a valid workaround for the time being until Google fix the bug.
I'm on:
- GNex Maguro Yakuju, UK version.
- T-Mobile US
- LA area
Hope this helps.
adrynalyne said:
What if you go back to 4.0.2?
Click to expand...
Click to collapse
Its to my belief that prior versions whether it be 4.0.2 or .3 does not have this issue. I think its mainly the fact that we no longer cannot change our settings under the *#*#4636#*#* to GSM auto from WCDMA which I believe is partly at fault here.
Correct me if I'm wrong. I really want to be able to change it to GSM auto since it still forces HSPA+ even in bad signal areas instead of reverting to edge.
Sent from my Galaxy Nexus using XDA
chlehqls said:
Correct me if I'm wrong. I really want to be able to change it to GSM auto since it still forces HSPA+ even in bad signal areas instead of reverting to edge.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I believe it's the opposite> GSM auto will revert to EDGE sooner. WCDMA preferred will try to stick to 3G even with very low signal
Wow, a lot of people posted in that thread. I wonder if Google even reads that stuff or even cares.
I've suffered data drops since 4.0.1... tried lots of roms and kernels, but it keeps happening. GSM, Orange network, Madrid.
Sent from my Galaxy Nexus using XDA
gbalerdi said:
I believe it's the opposite> GSM auto will revert to EDGE sooner. WCDMA preferred will try to stick to 3G even with very low signal
Click to expand...
Click to collapse
Yeah that's what I meant, my sentence came out wrong since I was rapidly typing on the phone. Where I commute, I have pockets of low HSPA+ signals and currently it refuses to go to edge because of the changes on 4.0.4..
Sent from my Galaxy Nexus using XDA
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.