Database Users

defective phone? (fixed) Cant hear called person & proximity sensor bugs

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

Blank/Non responsive screen.. bottom keys work

Anyone having a issue with the screen not coming back on and staying blank? I get this happening from time to time and the only way to fix it is to do a battery pull or do volume up + camera + power button to reboot. When it happens I can hit the power button to wake up the screen but it stays blank and just the keys on the bottom light up and respond to be touched but don't do anything.
Rooted with stock EB13, it did this on rooted DI18 also.

I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.

AmericanJedi001 said:
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
Click to expand...
Click to collapse
I used the Samsung installer.

Same thing has happened to me thrice today (since the upgrade last night, which came from ODINed DI18 usind update.zip).
And that's with no apps installed/running.
I've had this coming up couple times a week on DK28 ROMs, sometimes it's able to recover (like some sort of soft-reboot), most times I need to pull the battery.
I need to replace my Epic badly.. if the replacement behaves the same way, it will join a pile of junk WM6 phones in my basement.

No one else has had this?

Yes. It happened to me twice earlier today. Disturbing. I can't think of anything specific when it happened...once on Dolphin and once after using the camera i think. Have used those a lot since, and it hasn't happened again.
Stock, not rooted. I manually updated via placing the install.zip file on my SD card.

I can confirm this behavior.
Sent from my SPH-D700 using XDA App

Can you help me Fix my DEAD GPS? It use to work, but not anymore!

Ok, I need help troubleshooting/fixing my GPS.
Here is what is going on. I got the Vibrant when it first came out, I had the normal GPS problems as everyone else. Once Samsung released the GPS update, I applied it, and my GPS worked (as good as it could).
So everything was cool, until I installed KB1, my GPS died, never locked onto sats. So today I just tried istalling KB5 through Kies to see if this would resolve my issue. NOPE, GPS is still dead.
Next, I installed Rooted and deodexed KB5. My GPS is still dead. I have run Samsung's GPSRESTORE app, but it gets stuck on "Position FIX" and tells me to move to open sky and try again. I AM STANDING OUTSIDE.
My GPS DID WORK PRIOR TO UPDATING TO KB1, THEN DIED when I installed KB1. Something happend when I installed KB1.
My GPS is completely dead.
Any suggestions?

Try hardware fix, your GPS antenna might not even be connected inside.

nacron said:
Try hardware fix, your GPS antenna might not even be connected inside.
Click to expand...
Click to collapse
I don't think my issue is related to the GPS antenna. I say this because my GPS did work, but instantly went dead when I updated to KB1.
Clearly the two are connected, something happened after I installed KB1, unrelated to the antenna.

try flashing a custom rom. Seems like you've only tried the stock roms with broken gps. Look in the development section for the plethora of gps healthy roms.

DontJoinTheDarkSide said:
try flashing a custom rom. Seems like you've only tried the stock roms with broken gps. Look in the development section for the plethora of gps healthy roms.
Click to expand...
Click to collapse
Do the custom roms use a modified modem other than the one the stock uses? The dev went into kb5 modem and modified it?
Otherwise it should give the same result, if the modems are the same. No?

What happens if you ODIN to original firmware and then update to JI6 build which is 2.1 eclair ? Test it with this setup and check your gps under clear sky.
Next, try connecting to wifi and opening google maps. Also, do you have a dedicated gps app like copilot installed? Try opening that

VICosPhi said:
What happens if you ODIN to original firmware and then update to JI6 build which is 2.1 eclair ? Test it with this setup and check your gps under clear sky.
Next, try connecting to wifi and opening google maps. Also, do you have a dedicated gps app like copilot installed? Try opening that
Click to expand...
Click to collapse
When I ODIN to JFD, my GPS is still dead.
I haven't tried updating back to JI6, JI6 was the official release prior to Kb1, correct?
I will try that!
Can you explain the reason behind connecting with wifi? The issue is I don't connect to any satellites anymore. The GPS app I use is GPStest by chartcross.

Correct JI6 was official OTA update that was supposed to fix the GPS.
The reason I ask about wifi is because its possible that there maybe an issue with your sim and data so wifi will help google maps use data without your sim

VICosPhi said:
Correct JI6 was official OTA update that was supposed to fix the GPS.
The reason I ask about wifi is because its possible that there maybe an issue with your sim and data so wifi will help google maps use data without your sim
Click to expand...
Click to collapse
What could be the issue with the sim/data?
When I enter LBStest mode, and I click position test, it is basically dead. It doesn't even see any satellites. No action what so ever. All the fields are blank.
I can't find Ji6, is it in the development section somewhere?

Hmm, you can download JI6 from http://forum.xda-developers.com/showthread.php?t=798125&highlight=T959UVJI6
Regarding sim, I was just thinking a temporary issue with your area or your account. Have you performed hardware fix in the past? The reason I ask is sometimes the contact comes lose and breaks if you bent it too much.

VICosPhi said:
Hmm, you can download JI6 from http://forum.xda-developers.com/showthread.php?t=798125&highlight=T959UVJI6
Regarding sim, I was just thinking a temporary issue with your area or your account. Have you performed hardware fix in the past? The reason I ask is sometimes the contact comes lose and breaks if you bent it too much.
Click to expand...
Click to collapse
I've never opened up my phone, so no I haven't done the hardware fix. I'm pretty sure it got screwed up during the kb1 update for some reason.
Thanks for the ji6 link, I will try that.

Anytime after a new rom my gps doesn't work i use the digitaltoddy fix. Super easy, always works. Should be in my first signature guide.

s15274n said:
Anytime after a new rom my gps doesn't work i use the digitaltoddy fix. Super easy, always works. Should be in my first signature guide.
Click to expand...
Click to collapse
I'm installing ji6 right now, but I'll try that digitaltoddy fix also.
what is that? I haven't been active here for months, so I am totally out of the loop. Can you provide me the link to the thread please

Just installed ji6, GPS is dead, doesn't even see any satellites in view
completely dead

SamsungVibrant said:
Ok, I need help troubleshooting/fixing my GPS.
Here is what is going on. I got the Vibrant when it first came out, I had the normal GPS problems as everyone else. Once Samsung released the GPS update, I applied it, and my GPS worked (as good as it could).
So everything was cool, until I installed KB1, my GPS died, never locked onto sats. So today I just tried istalling KB5 through Kies to see if this would resolve my issue. NOPE, GPS is still dead.
Next, I installed Rooted and deodexed KB5. My GPS is still dead. I have run Samsung's GPSRESTORE app, but it gets stuck on "Position FIX" and tells me to move to open sky and try again. I AM STANDING OUTSIDE.
My GPS DID WORK PRIOR TO UPDATING TO KB1, THEN DIED when I installed KB1. Something happend when I installed KB1.
My GPS is completely dead.
Any suggestions?
Click to expand...
Click to collapse
2 weeks ago i had same problem. Now i am rocking with my vibrant, all i did was called samsung since it was still under warranty. I shipped my vibrant to samsung....they could not figure out what was wrong with it....all i knew was that they changed printed board (i guess its circuit board)...once i got it....GPS was working fine... That was my situation...rest u can decide what u wanna do!!!!

s15274n said:
Anytime after a new rom my gps doesn't work i use the digitaltoddy fix. Super easy, always works. Should be in my first signature guide.
Click to expand...
Click to collapse
oh i just found the digitaltoddy fix, going into lbstest mode, clearing gps data, setting to cold start? Ya i've done that already, but didn't know it had a name, haha.
I think my gps is totally dead

Sucks but seems like your gps is dead then. I'd say send it to Samsung and they should fix it. You could try opening the phone but why go through the hassle only to find the gps has electrical problem and needs replacement.
Good luck dude, didn't see you here since Froyo was rolled out

Sounds like it's dead. ODIN back to stock and exchange it for another.

I have the same issue.
I wish it had happened BEFORE I did the FFC mod and voided my warranty.
I may have to open this sucker up yet again to see if I can do another hardware fix.
ugh.

Put the stock cam back in, paint hole with black nail polish, then send in for warranty. I did with mine when my usb port got wonky. No questions were asked, and all of the in store sales reps knew I modded my phone.
Beware of angry gingerbread man

[Q] ics roms, screen turns black after answering

I have tried 3 different moded ics roms, and everytime i answer a call, my screen goes to sleep or turns black, i tried pressing all the buttons trying to wake it up but it just wont. the screen wakes up after the call. i tried to look for it maybe in the call settings somewhere, but no luck, anybody else having this problem??
thanks

Sense, AOSP/AOKP or both? I hate to beat this dead horse, but do you do a full wipe between flashes including the system partition?

estallings15 said:
Sense, AOSP/AOKP or both? I hate to beat this dead horse, but do you do a full wipe between flashes including the system partition?
Click to expand...
Click to collapse
aww man thanks for even attempting to reply to my problem. i posted this in the rootie thread and no one payed attention, so i must be the only one with this issue.
the first rom was rootie tootie and the other one was mexdroidmod.
Yes i went to cwm and reset to factory, clear cache and cleared davlik cache. flashed and did set permission.
My sd card is not partitioned so i have no partitions to clear.
I just flashed Hybrid HTC One Series and i thought i had the same issue, but with this one, i just press the power button, and the screen would wake up. So this would have been the perfect rom for my daily driver for now but i cant install swype on it and somehow some apps doesnt have sound, such as viber and voxer. the other party cant hear me..
Im going to use gb for now till awesome uploads the haters going to hate edition of his rootie and try again.
Im tempted to try to flash again and this time format my sd card. Any other suggestions, i wonder what im doing wrong...
or do you have any roms to suggest to try out?
thanks for the time.
awesome pic on ur avatar...i have the same on for my google+ hehe we must be near the same age...

Go to the mounts/partitions (I think) and format /system. Then do your normal wipe.
This is more thorough.
Now flash the ROM of your choice. Let us know if this solves your problems.

I just flashed awesome's rootie haters edition doing what you advised... and its still the same problem, The problem is intermittent, 3 out of 5 times it would do it. I was trying it with my dads phone calling my phone. I think maybe its some sensor issue or settings. with the htc one rom it does the same thing but i can press power and turn the screen back on... ugh.. is my phone just flaky! dropped it too many times. i would stick with the htc one rom but i cant get swype to work..and the sound issues with certain apps ..ugh

maybe its something i installed... ill try later with just a base rom without my apps..could google voice be doing it.. hmm

Did you flash anything other than the ROM?

estallings15 said:
Did you flash anything other than the ROM?
Click to expand...
Click to collapse
Ok, i just redid it a few moments ago and same problem
so i went to cwm , did reset factory, clear davlik, format /system /data and whatever else i can find..
flashed meXdroidMod Fried IceCream3! FINAL, the sufix aokp_fix.zip and gappsFINAL
thats it and tried it with my dad's phone, same problem, screen wont wake up, and its intermittent.
I dont know if this is relevant but my screen broke a week ago and had it replaced...

Have you checked to see if your proximity sensor works? There apps for that. Its at the top, front of your phone - opposite the camera.
Edit: I was just reading your posts. Are you flashing a ROM, restoring backed up apps and THEN having this issue?

aww , not yet, thats what im thinking is the problem... ill check that out tonight after work.

r0mmel said:
aww , not yet, thats what im thinking is the problem... ill check that out tonight after work.
Click to expand...
Click to collapse
OMG THANKS!!!! that was the problem my proximity sensor. oh man im so happy!!
this thread helped me fix the problem
http://forum.xda-developers.com/showthread.php?t=1431935
thanks guys! now just wondering if its worth fixing the proximity sensor or just let it be.. hmm

That's completely up to you. You can probably get a new phone on contract for cheaper than getting that sensor replaced.

[Q] Knock on just stopped working?

I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.

GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it

tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply

I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do

GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app

well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work

I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.

mine still says rooted so i'm kinda screwed right now

Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?

Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it

The only solution is returning the phone

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped

rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful

ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.

He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app

This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us

Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.