Related
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
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
should probably backup your things and reflash, preferable with odin i would think.
KateC1 said:
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
Click to expand...
Click to collapse
You could take it in to the store and see what they can do...they will probably just do a hard reset....I think your best bet is to, like the other poster said, do a fresh install of EB13. Most of the problems with this update were with the update and not with the clean install...good luck!
I could probably assume you don't know what odin is and everything so.. maybe someone could post a link to odin and the eb13 tar??
From My Samsung Epic Using TapaTalk.
It's just your install, use the full 200MB samsung exe after backing up your data and you should be good to go. That's not a bug of EB13, just the way your phone patched to it.
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
KateC1 said:
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
Click to expand...
Click to collapse
Sorry you did all of that for nothing :-( Download Z-Device Test from the market. There is a test for the proximity sensor in there. If it is not working in the test, I would say you should go to Sprint and have them fix it...I searched for others with your problem and there were a few (not from updating, you might have had it stop working by coincidence). They all ended up going to sprint and having the screen replaced. Just make sure that if you have a screen protector you remove it so Sprint doesn't try to blame that.
Good luck Katie
P.S. If you are feeling adventurous, you could always Odin back to DI18 and see if the sensor works and the back to EB13 to see if it still works....you could also try installing a ROM on top of EB13 and see if that makes it work (though I don't see why it would) Good Luck
Patrick
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
KateC1 said:
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
Click to expand...
Click to collapse
No problem... just tell them it happened after the update and I don't see any reason that they should charge... they seem to be hit or miss about charging sometimes, try a different store if they want to charge... good luck Katie. Let me know how it turned out.
Sent from my SPH-D700 using XDA App
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?
*deleted post incorrect information
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?
chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED
How did you solve the issue?
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.
xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.