Proximity sensor popping hardware or update issue - opinions please! - Epic 4G General

I have an unrooted stock Epic 2.2.1 with many UPDATE issues, but this issue started weeks after OTA came through, (for which I have do 2 hard resets that only brought out more issues.)
I have been having an issue with the sensor popping continously when using the touch screen and the tech replaced the chip card which helped for about 3 or 4 days.
Point of fact: the video camera had gone out too and he said they were on the same card. The new card fixed the camera permenantly.
I am searching for examples of similar issues on reputable sites like XDA to show his head tech who had never heard of it and thinks he knows everything. Has anyone else had this problem? My phone is less than 2 months old. And I do not want a refurbished replacement from using my insurance!!!
So I wonder if this is a hardware issue or more of an update issue... any thouhghts?
Thanks!
Sent from my Stock 2.2.1 SPH-D700 using XDA Premium App

Related

Got this from Sprint today on their forums

got this from a "sprint rep" on their forums
TiNy-2nz -
I apologize for the frustrations associated with the current issues with the GB release... Please know that we are aware of many of the issues people are experiencing and are working with HTC to resolve them. Although I don't have a time frame now, they will be sending out a patch to resolve issues associated with your device.
SOOO take it for what its worth and maybe there is a hair of hope .....
TInY
hope this is true.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
I had a prompt to download an update today. I skipped cuz I'm still holding out for root on this update that I'm on. I'm not actually having issues other than I can't root...
sent from my 2.3.3 unrooted piece o ****....
I was also prompted for an update today, after just being prompted for the GB update the other day. I was hoping maybe they were being true to their word and unlocking the bootloader.
It was a rather lengthy update process with two reboots involved.
tiny2nz said:
got this from a "sprint rep" on their forums
TiNy-2nz -
I apologize for the frustrations associated with the current issues with the GB release... Please know that we are aware of many of the issues people are experiencing and are working with HTC to resolve them. Although I don't have a time frame now, they will be sending out a patch to resolve issues associated with your device.
SOOO take it for what its worth and maybe there is a hair of hope .....
TInY
Click to expand...
Click to collapse
Kiduno99 said:
hope this is true.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Not to sound like a douche, but I think it's pretty obvious that Sprint & HTC plan on releasing an update that would fix the problems presented with the GB update.
There was the 4.22 update,GB
Then the 4.24 update,GB fix,
Are you guys saying there is a 3rd update being pushed?
Sent from my PC36100 using XDA App
I'm wondering the same thing...I've already had two updates. I took both of them because I like my evolution stock, only reason I ever rooted my hero is because Sence made it sluggish.
Sent from my SPH-P100 using Tapatalk
at this point in time....i am not confident that we will have any sort of solution in the near future, we will simply have to deal with this horrible android version of gingershitbread, i never tought id hate the awsomeness that is an EVO , but currently...i kind of do, clearing user data, resetting,done it all, it still sucks arse and glitches half the dam time,its horrible, if id have known i would have stayed with stock 2.2 (not because of root but because it actually friggin functioned better)
I waited a couple weeks and did the rooted stock rom, 4.24
Have had no issues after a full week of use.
Sent from my PC36100 using XDA App
the more i think about it you think he said that just to shut me up and so the sprint forums dont get filled up with posts about it ??? I dunno; like the corp store told me; "as long as you can make and recieve calls there is nothing wrong with your handset"
IT suxx to be stock its like having a maseratti that only goes 55MPH

Droid X Gingerbread Cellular Disconnect

Has anyone else here had issues with the Droid X having cellular network disconnect issues?
What I mean by this is that the 3G stops all together, you cannot make outbound calls or SMS messages. The 3G icon goes away, yet I can see bars on the antenna strength meter.
The only way to fix this is to reboot the phone, even putting in airplane mode doesn't work. It happens about every 1.5 to 2 days on this phone. I've factory reset it, gotten a replacement phone, etc.. Nothing works and it all started with the Gingerbread update.
I'm not the only one I can tell you that, many others on the moto forum are having it too.. https://supportforums.motorola.com/thread/52111
I have an ADB logcat that I could send to some folks smarter than me if someone wants to look..
http://androidforums.com/droid-x-support-troubleshooting/354058-loss-data-voice-connection.html
Another forum posting I've found..
Glad to see there are more people with the issue.. Now its getting Motorola to listen....
There must be something unique that you are doing. I burn about 2200 min a month of cell time, and I've had no issues.
Yeah that happens to me, I sbf back to froyo, and now I'm on liberty rom, no more cell disconnect
Sent from my DROIDX using XDA App
I'm to the point where I want to get away from Motorola all together.. This phone has always been quirky, now its just totally unreliable. I have an HTC incredible (CM7) and have 0 issues with this, so I know its not a cell reliability issue in my area.
I can tell you that I ran CM7 for a few days on the DX with no issues at all. However CM7 has a few other annoyances that the wife didn't want to deal with.
I'm working with Verizon and it sounds like they're to the point of offering up a different phone..
I was having a similar issue. Spent countless minutes on tech support with vzw, countless resets, even sent me a replacement phone and had the same issue. Determined it was google voice at fault. Had to do a factory reset from the moto bootloader (not from settings/privacy), and it finally solved the issue.
If you're using google voice, try getting rid of it, and disconnecting it from your phone.
Sent from my DROIDX using XDA App
Well, I don't use GV, but had it on my phone...
I've uninstalled, and rebooted (not factory wipe)...
I'll see how it goes...
I asked in the moto forum and one user responded so far saying that they have the issue but don't have google voice installed..
I had the same problem with OTA Gingerbread. Cyanogenmod 7 fixed all my problems. No lie.
Sent from my DROIDX using XDA Premium App
Hi,I'm now having these issues and more since gingerbread. Sad thing is, I had NO issues with this phone while on froyo. Verizon wants to do a complete factory reset, but that means i'd lose everything on the phone. I have it all backed up, but it takes a while to set up the damn thing the way I have it. I feel if tat what Verizon recommends, they should help set it back up.
Sent from my SCH-I800 using XDA Premium App
After dealing with the issue with Verizon they agreed to let me swap the phone out for a different phone. The only rule was no 4G or no iPhone. Right now we settled on the HTC Incredible 2. I have the original Incredible, while the HTC software isn't perfect, but at least I haven't had these issues..
Bye bye Motorola.. Another plus, if this HTC has issues, as least I can run CM7 easily now..
I had(?) the same problem
history:
before upgrading to 2.3.3 my Droid X was on Froyo and rooted. In fine noob fashion I deleted bloatware during that time without backing it up so when I attempted to updated to Gingerbread I was **** blocked.
The resolution was to SBF the phone back to stock Froyo then upgread to Gingerbread, it worked like a champ... sorta
I kept noticing that the phone was really sluggish on reboots, it also kept dropping the network connection, mostly when I moved out of a wifi hotspot, the 3G wouldn't connect, not until I rebooted. I tried a few things, uninstalled misc programs blah blah blah, some of it seemed to have worked temporarily but nothing was permanent.
So, yesterday, I did a Factory Data Reset, actually had to do it 3x's since the first 2 times somehow goofed the market so that it wouldn't download and install . But 3rd time was the winner and now everything seems resolved, no more whacked out loss data connections and faster reboots!
so my suggestion - Factory Data Reset
I totally agree. Vzw tier 1 tech support can be a waste of time. After taking 30 minutes to tell me to turn on wifi, one guy told me to right click on the settings menu. I told him it was a touch screen, does that mean I have to use my right hand?
Sent from my DROIDX using XDA App
I have the same problem on rooted OTA gingerbread. My solution for the time being is to setup tasker to reboot the phone at 3am everyday. If i go back to froyo the problems go away. I posted about this a while ago. It doesn't fix the problem it just masks it but I start with a fresh phone every morning.
I have the issue too, it started right after Gingerbread.
It was *really* bad until I re-activated my phone but it still happens almost every 48 hours.
As best as I can tell, it is most likely to happen when wifi is on and you have a weak cdma/3g signal.
I'm glad to hear that CM7 seems to clear it up. Between hardware instability, the compass quality being degraded and the ever imposing presence of Blur, I'm thinking I'll never again own a phone with a locked bootloader if I can help it.
I also setup tasker to reboot my phone at 3am every night. Did this several weeks ago and I've not had a network access issue since. Not a great solution but if you got root it does seem to make the problem go away.
Hey, let me know what you think of it. I thought about grabbing one cheap and using it until a good 4G & dual core comes out.
Not sure I could go with the smaller screen though.
Sent from my DROIDX using XDA Premium App
I have this issue on an unlocked dev dx which has slightly older hardware than the current DX's but I'm glad to hear I'm not the only one with the issue. I'm going to experiment with some different radio versions, because this didn't happen with all the different leaked GB radios. It wasn't until I think the 588 build that it started for me.
+1
I have had this issue ever since GB dropped for it. I am on my third X since GB. The first one smoked a memory card and battery. So I got a like new phone and all the fixings. Then the second one was also having the data issue and the camera took a **** (shutter was stuck closed). All of these have also not only rebooted randomly from day 1 with GB. Go to make a call phone reboots, send a text phone reboots. I thought it also was apps and heard about Google Voice causing it. So when I got this third one I only setup apps that it came with and nothing else. not even 2 days into having it the same **** was there. Less frequent but still there. They are going to get screamed at until I get a new device.
Switch to cm7. I love it.
Sent from my DROIDX using XDA Premium App

Nexus Restart Bug

Just a quick question i bought this phone when it was released and it suffered from this awful restart bug so it got sold.
With the ICS update being available what i'd like to know is has this been resolved and if not will flashing a custom ROM cure all that ails it?
Also will it bring at least 720p video recording?
TIA
Darkwun said:
Just a quick question i bought this phone when it was released and it suffered from this awful restart bug so it got sold.
with the ICS being available what i'd like to know is has this been resolved and if not will flashing a custom ROM cure all that ails it?
TIA
Click to expand...
Click to collapse
Try doing a factory reset ... maybe that should clear it up... but if anything it should fix with next update .. did u buy the phone from someone who had a custom rom on it?
Sent From In between Your Moms Boobies
Sorry i just realised i wasn't very clear.
When i bought one from a retailer it had the reset bug so i sold it as it was a common thing and this was a while back. Now i'm planning on getting another one seeing as ICS is coming out so i wanted to know if that restart bug is still around
FYI when i had it i do remember factory resetting it offten but it didn't fix it
Nah that was probably that phone.. the only bug known is the i9020A and it has a search bug where if ur signal is low it starts activating the search bug non stop until u restart or simply turn the screen off and on. But yeah its the only issue known. =]
Sent From In between Your Moms Boobies
There is no known issue with restarting. Either you downloaded a buggy app or there was something wrong with that phone. You should of returned it for a new one.
And to answer ur question about 720p recording... it doesn't do 720p
Just wait for the Galaxy Nexus
Sent From In between Your Moms Boobies
YourMainDude said:
Nah that was probably that phone.. the only bug known is the i9020A and it has a search bug where if ur signal is low it starts activating the search bug non stop until u restart or simply turn the screen off and on. But yeah its the only issue known. =]
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
This is pretty much fixed with the lastest ROM and/or screen replacement.
Cool well although the vid recording isn't 720p I may still get one, my problem is in the UK we get stiffed on the price of phones and £540 is more than I'm willing to pay.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App

headache situation about replacement!

okay, i received a n7 with a transfomer rom preinstalled on it 3 weeks ago, i called up customer service after a day trying and they said "do everything to make it work" and they will send me a email with instruction returning it.
headache: i managed to put a stock rom back on it, activated and everything, but i find out it's not as smooth as other devices (well, playing games for the first week is fine, than keep getting lagg after time), but luckily, i took a picture when i first start up the device (with transformer wallpaper,system info..)
currently the n7 is on stock rom with bootloader unlock and rooted, so if i return with this stock rom, are they will pass the examine of faulty and not "charge" me for another device? or i just go to the transformer section and flash their stock rom )
thanks for any advice
i dont think anyone have this case before -.-
That's weird.... was this straight from Google or did you buy elsewhere?
Sent from my Nexus 7 using xda app-developers app
There have been several instances where people have gotten ics (not TF, all asus products have the tree background) test roms on their devices, and experienced the same lag you are experiencing. It appears they got early pre-production devices, where the software (and perhaps hardware) has not been finalized yet, which may be what is causing the lag. I believe they will take it back if you change your complaint to "extreme lag", and explain what happened to it.
Good luck
kangxi said:
That's weird.... was this straight from Google or did you buy elsewhere?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, straight from play store.
hanthesolo said:
There have been several instances where people have gotten ics (not TF, all asus products have the tree background) test roms on their devices, and experienced the same lag you are experiencing. It appears they got early pre-production devices, where the software (and perhaps hardware) has not been finalized yet, which may be what is causing the lag. I believe they will take it back if you change your complaint to "extreme lag", and explain what happened to it.
Good luck
Click to expand...
Click to collapse
Yeah, i just afraid thr bootloader is unlocked, rooted, but this is all done before the device get to me, and because its up n working again, im just afraid they wont pass the examine
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

[Q] Does anyone have this touchscreen issue?

There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Tried that on quick memo. I dont have it luckily.
Sent from my LG-D802 using xda premium
Tried it also. No problem for me too.
Sent from my LG-D802 using Tapatalk
My first one developed that after some time, same place too. Went to verizon, showed them that, and they replaced it with a "certified like-new" which thankfully seems to be new as far as i could tell.
UberMario said:
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Click to expand...
Click to collapse
Saw it already reported here before. But I do not have it.
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
robogo1982 said:
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
Click to expand...
Click to collapse
I have the LG-D801 aka T-Mobile US version. The software version on it is D80110C_00. I used the LG flashing tool and flashed a .kdz file named "T-Mobile USA D80110C_00.kdz" since I bought it from craigslist and wanted it back to 100% stock (guy sold it for $80 since he rooted it and then did the OTA which caused him to go into that recovery boot loop issue and only way to fix it was to flash that .kdz file)
I'm not rooted and I am not using a custom recovery. I guess I'll do the OTA update the phone was bugging me to do.
EDIT; Installed the latest OTA. The issue is still there but it did decrease the dead zone. The biggest problem is that I can't press "install" for apps in the play store since the button is right in the dead zone.
Getting the same problem here on my device, suddenly. I updated to the new Kit Kat update (I'm on Sprint) but didn't seem to make a difference. How annoying this suddenly happened and my phone was not dropped or damaged or anything. My other friend with a G2 had the issue and it went away on its own over time somehow. i'm noticing the bar where I have trouble is aligned exactly with the power button on the back, so I wonder if that has something to do with it, in the hardware.
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
randomvector said:
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
Click to expand...
Click to collapse
This is very weird, same thing happened to me today around noon, phone was fine all morning, then dead zone in same area, wth is this, is At&t or LG doing something ota that we do not know about.
edit: just wanted to add, I am on the D800
I'm don't think so as I'm on a custom rom. I've heard from some on xda the update fixes it but I've used the stock KitKat Rom and no luck there. I'm now using cloudy flex 2.2 still the dead zone is there.
Sent from my Nexus 4 using Tapatalk
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
coreygator said:
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
Click to expand...
Click to collapse
Funny how this happened to me right after the ota as well...
Dead zone in the same spot ..
And well in order to fix it( the install button atleast) is to change the DPI to 330
I called lg and they gave me an authorization to send it in for repair.
Call and see what they tell u guys
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
Yep. VS980 Stock Kit kat rooted with TWRP 2.7.0.0
Same exact issue. Same exact spot. Can't hit install on the play store. Haven't tried taking it to Verizon yet. I bought my phone through Target though I hope Verizon will replace it if it is in fact a hardware issue. I'm not gonna try and take it in until after I try a couple different ROMS to make sure it is a hardware issue.
I am on D800 was on CloudyFlex when it happened so it has nothing to do with OTA exactly, I returned to fully stock At&t 4.2.2 and it was still there. I am getting a replacement under warranty. Something weird is definitely happening if so many have seen this issue. It is almost like a timer going off in phone coding and bam that part of screen is deactivated. Whatever it is, this will be my last LG phone. Never had an issue with my iphone or galaxy s2 skyrocket.
Same problem here, VS980. It started happening right after I tried the newest build of CloudyStock with knock on support. I've been browsing through multiple CloudyROM threads and I'm seeing identical problems, (including the exact area of the dead spot, around where the install button is on the Play Store). I can't post in any of them because a. I don't have enough posts, b. Cloudy in his FAQ states that the VS980 is only for testing. I've tried flashing different AOSP and Stock roms including the latest PA and XDABBEB builds and the problem crosses over after full wipes. Has anyone figured out a way to fix this yet other than returning the phone for another?
To be clear: This phone has no damage to it whatsoever. No scratches anywhere including the screen, etc. I'm worried about how Verizon will take a warranty seeing as there's an "UNROOTED" flag in the bootloader.
Has anyone tried to update touch firmware?
Sent from my LG-D803 using XDA Premium 4 mobile app
jester12345 said:
Has anyone tried to update touch firmware?
Click to expand...
Click to collapse
I've read some people do it to no avail, but I'd like some confirmation on that. The service menu still hasn't been discovered on the VS980 from what I've read. It's not the same code with a different model number at the end like the D802. For example, Every other model of the G2 is 3845#*XXX#, but the Sprint model is 5689#*980#. 3845#*980# for the VS980 doesn't work.
Dang. Now im worried to update.
Sent from my LG-D803 using XDA Premium 4 mobile app

Categories

Resources