Related
It only happens when I use any ROM based off the .47 OTA and now the newer froyo 2.2 versions that have been released. I realize they are not final but a final version is obviously not going to fix my problem.
I feel I am probably a very small number of people with this issue. If I run any other ROM I don't have the issue but obviously there is something either with my phone or in the kernel or something effecting my phone.
What do I mean by ghost screen touch? Randomly using the phone it will register touches at the top of my screen. Bad enough to make the screen unusuable and I have to turn the screen off and on multiple times till it goes away.
If it is happening in my app tray it will always select the first top left icon on my screen.
This is on a completely stock ROM without me adding any software or anything. I also have no screen protectors etc. I have eliminated everything I can.
The only thing I can think of is I know before the .47 OTA some people complained about a grounding issue. I never had that problem personally but whatever they changed I think may be causing this because any ROM before that is fine.
This also does happen to me more when the phone is plugged into the charger.
thanks for reading.
I have gotten it when I'm charging, to the extent I have to disconnect my phone to use it without the screen going crazy.
Have you tried running dotty to see if anything is registering?
Sent from my PC36100 using XDA App
SharkUW said:
Have you tried running dotty to see if anything is registering?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Installed dotty and nothing was showing. decided to touch it and when i stopped touching it 3 points were still showing as registered(i can max at 5 points) they are still showing as i look at the phone now not evening touching it. now they are flashing as if i was touching them both!
update..it seems like its normal for there to be points after you stop touching the screen in dotty i dunno..however when my screen does start going crazy in dotty it will show two touches parallel to each other on the top left corner just down a bit. it will actually flash between the two as if i was cycling my fingers back and forth.
MrDSL said:
It only happens when I use any ROM based off the .47 OTA and now the newer froyo 2.2 versions that have been released. I realize they are not final but a final version is obviously not going to fix my problem.
I feel I am probably a very small number of people with this issue. If I run any other ROM I don't have the issue but obviously there is something either with my phone or in the kernel or something effecting my phone.
What do I mean by ghost screen touch? Randomly using the phone it will register touches at the top of my screen. Bad enough to make the screen unusuable and I have to turn the screen off and on multiple times till it goes away.
If it is happening in my app tray it will always select the first top left icon on my screen.
This is on a completely stock ROM without me adding any software or anything. I also have no screen protectors etc. I have eliminated everything I can.
The only thing I can think of is I know before the .47 OTA some people complained about a grounding issue. I never had that problem personally but whatever they changed I think may be causing this because any ROM before that is fine.
This also does happen to me more when the phone is plugged into the charger.
thanks for reading.
Click to expand...
Click to collapse
the only time I saw something like this on my phone, the screen shaking, icons moving, like delayed touches, vibrating movements, ghost screen touches, etc. etc. and unresponsive, was when I ate a "Subway" sandwich, I had mayonnaise on my fingers, and I tried to use the phone, it looked like it was experiencing a seizure. I really worried that day. I even though of pulling the battery. It went away when I wiped the screen....
I can confirm the odd touch behavior while charging.
This may be unrelated but I recall seeing a post saying the HTC Music widget was causing scroll lag and touch issues on the new OTA over in the dev forum.
So does that mean you ruled out the fps hack?
I woudlnt worry much.. been getting this every once in a blue moon since the first OTA (while charged to PC.. not the wall)
I also have this issue, but its rare when it happens... I've seen this exact issue with my old pre as well...
Sent from my PC36100 using XDA App
baiatul said:
the only time I saw something like this on my phone, the screen shaking, icons moving, like delayed touches, vibrating movements, ghost screen touches, etc. etc. and unresponsive, was when I ate a "Subway" sandwich, I had mayonnaise on my fingers, and I tried to use the phone, it looked like it was experiencing a seizure. I really worried that day. I even though of pulling the battery. It went away when I wiped the screen....
Click to expand...
Click to collapse
Seriously? So you're what 12 then?
AssassinsLament said:
So does that mean you ruled out the fps hack?
Click to expand...
Click to collapse
Correct..I am not sure what has changed since the .47 OTA but from there on up the issue is there even stock.
DataDork said:
I woudlnt worry much.. been getting this every once in a blue moon since the first OTA (while charged to PC.. not the wall)
Click to expand...
Click to collapse
I'd love to not worry about it but it happens to me without it being plugged in also. Often enough to be very annoying.
You should take your phone back.
Sent from my PC36100 using XDA App
Are you using the stock htc USB cable? I know that certain cheap (i.e. Monoprice) chargers/cables cause people's screens to become unresponsive and just basically act weird. Though it doesn't explain why it is only doing this with Froyo. Okay nevermind, just throwing some ideas out there. =)
My screen is less responsive to touch when charging via A/C adapter sometimes. Probably a grounding issue. Doesnt bother me.
I am also having this issue, except it happens w/o it being plugged in and it is happening to the point that my phone is completely un-usable. I bought it on launch day, I am trying to get back to stock 2.2 using the OTA and take it into sprint and play dumb I dont know what to do at this point.
Update: I was able to roll back to 1.32.651.1 (initial release) and I did not have any "ghost input" issues at all, loaded up dotty (which interestingly only let me use *2* multi-touch inputs at a time, if I put three fingers down the 3rd wouldn't show) played with it for 10 minutes. Usually I encounter these symptoms within a minute or two. Then I started updating, It loaded that very small update 1.32.651.6 i think, again no problems at all. Next up was 1.47.651.1. This update is the one that is causing the problem for me. Within 45 seconds of getting into the OS after 1.47 I started encountering the issue and Dotty is showing the same symptoms that MrDSL is having (two dots flashing in the top left handish corner). For ****s I then installed the official 2.2, in hopes that it would resolve the issue, but I still have the same problems. So, at this point I can either run pre 1.47 which really isn't an options for me, or deal with the ghost input issue which also really isn't an option for me, it literally drives me insane and I can't even use my phone as it just does it's own thing, or take it back to sprint.
At this point since I purchased this phone on launch day from Radio Shack what should I do? I want to exchange it but I don't know if Sprint or Radio shack will take it back (we're coming up on two months since launch). I should not have to use Insurance for something that is their problem. Suggestions?
Anyone else having this issue besides me and DSL ? DSL what have you done to remedy this or are you just living with the hell?
nvous23 said:
Anyone else having this issue besides me and DSL ? DSL what have you done to remedy this or are you just living with the hell?
Click to expand...
Click to collapse
Since the offical 2.2 has come out I emailed Sprint to let them know and they created a ticket for me and told me to bring it to the nearest Sprint store who has a tech on site.
I played dumb and said the issue started at the .47 OTA and that I was hoping the 2.2 OTA would fix it but instead it actually got worse. So when I need to go to the Sprint store I'll just flash the offical 2.2 OTA.
I really don't have much of a choice other then that unfortunately
Do you have a screen cover?
Sent from my PC36100 using XDA App
I do not have a screen cover. Even if i did and it was causing the issue it would happen on pre 1.47...
No screen cover! Nothing!
This is even without adding any software..Completely stock!!
Yep, got the same thing here. It's some of the most annoying stuff in the world. I'll be typing on the keyboard, and it'll give me a triple-tap, then it'll flip down the notification panel, and it just does strange stuff. And then it'll be fine for the rest of the day. And then, it'll do it again. It's such a pain. I figured it was the FPS hack, since it runs everything at 110Hz or something, but then I noticed, like you guys, that it happens on stock as well. Pretty much a total pain.
so i bought a second hand slide for my wife maybe a month ago. it was supposedly brand new (i believe it was). i've rooted it and have cyan's latest running on it. today, however, several of the buttons quit working. home is okay and so is the genius button. but the menu, back, and touchpad have all stopped responding. is this something that's occuring with this phone with frequency? i haven't called tmobile yet as i'm currently restoring her app's from a fresh wipe but i'd thought i'd see if this has happened to anyone else.
damngood98 said:
so i bought a second hand slide for my wife maybe a month ago. it was supposedly brand new (i believe it was). i've rooted it and have cyan's latest running on it. today, however, several of the buttons quit working. home is okay and so is the genius button. but the menu, back, and touchpad have all stopped responding. is this something that's occuring with this phone with frequency? i haven't called tmobile yet as i'm currently restoring her app's from a fresh wipe but i'd thought i'd see if this has happened to anyone else.
Click to expand...
Click to collapse
No, never happened to me, did you say you already tried doing a full wipe/reflash? If that didn't work try flashing a different ROM like cr_mod or 3rd sense and see if the buttons work in those. Could be a corrupted ROM, redownload and reflash it. If you haven't already, update to 6.1.1.
next day the touch screen stopped working next. can't even answer a phone call. phone is fried. that was after upgrading. beginning to doubt htc as a phone maker. went through several g1's. my nexus has screen issues, now this. not a fan of motorola's phones. and samsung sucks too. well, she's due for an upgrade, just at a loss as to what she's going to get now. thanks for trying to offer help though
damngood98 said:
next day the touch screen stopped working next. can't even answer a phone call. phone is fried. that was after upgrading. beginning to doubt htc as a phone maker. went through several g1's. my nexus has screen issues, now this. not a fan of motorola's phones. and samsung sucks too. well, she's due for an upgrade, just at a loss as to what she's going to get now. thanks for trying to offer help though
Click to expand...
Click to collapse
What kind of torcher you putting your phones through? Lol
Seriously though, never heard of someone going through phones the way you describe. I have yet to have even 1 issue with an HTC phone. Same with any other HTC users i know.
Might i recommened the motorola defy to you lol
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
What kind of torcher you putting your phones through? Lol
Seriously though, never heard of someone going through phones the way you describe. I have yet to have even 1 issue with an HTC phone. Same with any other HTC users i know.
Might i recommened the motorola defy to you lol
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Haha, same here. I received a used g1 from a friend, I was its fifth owner I think, it had no issues, I ended up accidentally breaking it because I fell asleep on a recliner chair and it fell out of my pocket into the recliner mechanism and got its chin crushed. Poor thing. I took it apart and wiggled the bent connector a little bit, and it actually worked for a few more months, although fragile. Now it won't turn on anymore though, totally done. It lived a long life though.
Now I'm using the same friend's old slide, which he spilled a full glass of lemonade on. It didn't work for a week, then randomly started booting, so he gave it to me since he had already gotten a vibrant. The only thing that doesn't work on it is the camera, which I couldn't care less about.
HTC phones have been great for me, you must be treating your phones like they are $40 dumbphones made by nokia.
lol! no, that would be my son who treats his g1 like a hacky sack. it's my wife who's having all the bad luck. i may try taking it apart and seeing what i can do but believe me she pretty much uses her phone as a phone and to facebook. otherwise it sits in her purse. although she has gotten into angry birds lately and i do see her getting frustrated more & more.....
You bought a second hand phone that is now failing and you're blaming the manufacturer? It sounds like to me the previous owner may not have foreclosed some previous "incident" happening to the phone.
damngood98 said:
next day the touch screen stopped working next. can't even answer a phone call. phone is fried. that was after upgrading. beginning to doubt htc as a phone maker. went through several g1's. my nexus has screen issues, now this. not a fan of motorola's phones. and samsung sucks too. well, she's due for an upgrade, just at a loss as to what she's going to get now. thanks for trying to offer help though
Click to expand...
Click to collapse
I realize I'm arriving a little late to this conversation but Im wondering if you ever figured anything out with this? My phone did the exact same thing this last weekend and after completely tearing it apart and cleaning all the connections I could, with not fix, I finally gave up and bought a G2. If you do have any ideas it would be awesome!
Same thing happened to me, I have a thread in the general section, I'm on my fifth slide
Sent from my T-Mobile myTouch 3G Slide using XDA App
One of the Cyanogen Mod nightlies was very unresponsive on touch and a few other things.
You can try a more stable cyanogen rom, and see if that makes a difference.
Its not that. The slide isnt just unresponsive, its not working at all. I wiped it all to start over and try a stable but now I cant get past the start up screen where you have to tap the android haha. I bought a G2 so if I fix it, it would just be to sell or as a backup. Anyone know anyone that wants to buy it?
First, I thought I should mention that this isn't the same capacitive back button problem everyone else sems to be having. Instead of not working when I want it to, it decides to work when I don't want it to. It will randomly activate, causing whatever program I am in to be backed out of. I am on my second epic that is displaying this problem. However, this one has only started doing it since I upgraded to froyo. I am running the stock froyo just released. The only time it seems to happen is when the keyboard is extended...
Is it possible this is a software issue? (That could possibly be fixed by flashing a custom rom?) Could it be my case (fishbone)? It has been difficult to find others with the same problem since the issue of the back button not working is much more prevalent.
I appreciate any help.
I haven't had this issue.
It might be the physical back button on your keyboard and not the capacitive one since it seems to happen when your keyboard is extended. Not sure why the upgrade would have caused that, though it just might be coincidental. I hope you get it figured out.
budderocks said:
I haven't had this issue.
It might be the physical back button on your keyboard and not the capacitive one since it seems to happen when your keyboard is extended. Not sure why the upgrade would have caused that, though it just might be coincidental. I hope you get it figured out.
Click to expand...
Click to collapse
Unfortunately I forgot to mention that I have noticed the LED behind the capacitive back button flash when this issue occurs, indicating the capacitive back button was activated. Appreciate your attempt though. Thanks.
you are not making this up. I had the same problem you described exactly. I am on my second phone also. the new phone seems a little better. I am now in the habit of closing the slide out keyboard asap to make it do that less. on my second phone I got the $20 best buy screen protector and on my first phone I had a cheap screen protector that didnt go all the way to the bottom. The shorter screen protector may be the cause? but I was hoping the 2.2 would fix this, now I will be watching. I think its the phone really and you will have to do what I do. deal with it because its past the 30 days to get a different phone with actual updates. I watched it magicly back out of the browser from 3 feet away. pissed me off because I use it for band practice and I am standing in for a singer and it sucks when it bhappens in the middle of a song.I 2 do see the LED behind the page back button flash. great news eh, you arnt stupidly hitting the backbutton with your thumbs after all.
I assume since it appears to be a defect I could swing sprint into givng me a new one. The problem I have is that this phone was working fine before froyo. I have been waiting for froyo for months, but since I've had it there have been nothing but problems. As soon as the new roms come out I will see if this issue persists.
My phone does this too, always at the worst times. It just gets stuck in a back loop. It will do this really bad off and on for a few hours, then be good for a couple of days. I probably need to have it exchanged at a Sprint store, but I absolutely hate going to that place....
you do know that the sprint guy will tell you that since he cant see it do it then their is nothing he can do. and he will do a hard reset and call it fixed,from experience. then you get a referb phone probably sent to sprint for the same problem that cant be replicated. I am overjoyed about this phone but if you compare the evo vs epic you will like the display much better on the epic, that is the only reason keeping me from chucking the phone right now.
I had this same problem the second to last time I flashed dk28
My back button would randomly activate
I reflashed and everythin was perfect! (As far as perfect gets in dk28 atleast....)
Just reflash eb13 and try? I'm 95% sure its software related because it only happened during that one bad flash of dk28
Sent from my SPH-D700 using XDA App
I'm having this issue now.
I'm on an unrooted Epic flashed to boostmobile STOCK firmware 2.2.1 froyo eco5
Do you all get it fixed? How?
Will flashing from stock to a different rom fix it?
hockeyfan04 said:
First, I thought I should mention that this isn't the same capacitive back button problem everyone else sems to be having. Instead of not working when I want it to, it decides to work when I don't want it to. It will randomly activate, causing whatever program I am in to be backed out of. I am on my second epic that is displaying this problem. However, this one has only started doing it since I upgraded to froyo. I am running the stock froyo just released. The only time it seems to happen is when the keyboard is extended...
Is it possible this is a software issue? (That could possibly be fixed by flashing a custom rom?) Could it be my case (fishbone)? It has been difficult to find others with the same problem since the issue of the back button not working is much more prevalent.
I appreciate any help.
Click to expand...
Click to collapse
Lots of peeps including me, had this problem when the epic came out
I returned it back and got a new one never had the problem again
there is no fix for it that I am aware of..
Well I got my epic from ebay with Boostmobile flash so I don't have Sprint's insurance.
It seems like it only does the repeated back button presses when I use the keyboard back button then use touch screen after, so I don't
Sent from my SPH-D700 using Tapatalk
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
enigmaisdead said:
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my phone. I have actually gotten 3 new phones only to have them all do the same thing. I flashed to Jelly Bean hoping it would fix the issue but no luck.
Sounds like a hardware issue. I have flashed many roms, ICS and JB and all are good for reception. Once we got new radios 5 months ago it fixed my 3g to 4g handoffs when I would lose data for minutes if not an hour. All good now.
It's common issue for Google nexus. I am also having same problem. You may ask a replacement or switch network mode to "CDMA only" instead of "LTE/CDMA".
Sent from my Galaxy Nexus using Tapatalk 2
It happens to my Galaxy Nexus too. >_<
Happens to me too. From HSPA (which should bei constant high-quality in my area) down to 2G, and if I am in areas with bad coverage, it looses signal completely.
Finally, after several ROMs, and basebands haven't fixed it, I'm going to send it in, as soon as possible now.
Sent from my Galaxy Nexus using xda app-developers app
This is a hardware issue. I515.10 is the one I have and it does this as well, the I515.9 however does not seem to be affected. The .10 was made in china and the .9 in korea... or maybe the other way around, hell who cares... Bottom line is, its a huge issue that samsung should have addressed long ago.
For more info check out the samsung forums. I'm waiting on a replacement to come Monday.
Sent from my VS910 4G using xda app-developers app
Same thing
This is happening on mine too. I installed the stock rom on my Verizon GNex and the signal has deteriorated significantly, almost like 4.0.2
I'm hoping a fix, or the new binaries fix this issues and put it back to it's 4.0.4 state.
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Crandolph2001 said:
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Click to expand...
Click to collapse
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
enigmaisdead said:
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
Click to expand...
Click to collapse
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Crandolph2001 said:
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Click to expand...
Click to collapse
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
enigmaisdead said:
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
Click to expand...
Click to collapse
When it started acting up I hadn't rooted / romed yet. I am now rooted and have flashed to 4 different roms and every single one of them still had the issue. I may have had the issue on the first couple days and not noticed it for whatever reason...
I recently had the random menu pop up and bottom key freeze on my E4GT. It was real bad, my phone was barely usable. Sprint replaced my phone with a refurbished warranty phone, and same exact problem with that phone. Well I went thru 3 phones all with the same problem. I was told it was a glitch with a part in the bottom of the touch screen that apparently goes bad. They replaced the so called defective piece (the whole touch screen). That was done to my 3rd phone. And still same problem. It would always happen about 24 hours after I picked up my phone and it would act up worse when I was in a bad signal area. I became very aggravated. I can understand 1 phone but 3 ? Well the 4th phone I got doesn't act up but I'm still experiencing the bottom keys randomly freezing upon waking the screen. Happens about 4 - 5 times a day. I was on stock FI27 w/ no root. And also I found it odd that when I got the ota for FL24 my phone aborted it and stuck in stock recovery. So I rebooted and went to system updates and it said my software was up to date even tho I was still on FI27. I waited 2 weeks and never got the ota again so I decided to manually update to FL24. Few days after that when QBKing posted FL24 w/ root I decided to root my phone. The bottom keys still freeze randomly only upon wake. I'm afraid to ask for another replacement in fear of getting another bad one with the menu pop up. Id rather deal with the bottom key freeze then the other problem. But it is aggravating with the bottom keys freezing. I shouldn't have to deal with any issues. Anyone familiar with this or experiencing anything like this ? Or does anyone know anything about this? Any help would be greatly appreciated. Thanks
Sent from my SPH-D710 using xda app-developers app
Its called phantom key presses. Are you in a low signal area? It happens because antennae is behind touch buttons. When your in low signal area it causes interference. Theres a thread in detail about this. My previous e4gts did this. I just received a brand new not refurb phone from insurance was built 12-2-12. I have not seen this at all. Tell them you want a new one!!
Sent from my SPH-D710 using Tapatalk 2
The manager at my local sprint store (independently owned & operated) told my brother that the S2's are still garbage and he should buy an S3 instead. Take it for what it's worth. My phone randomly freezes with the screen off and kills the battery, even while I was on stock. My sister's phone has never had a single issue. She also somehow gets 18 hours out of a single battery charge with heavy wifi use. I'm lucky to get 10 with minimal use. I swapped the batteries, and no difference.
It seems these phones have relatively poor QC, but the good ones are great. Why do you think the refurbs were sent back originally? They "test" them and then send them right back out the door.
Yeah I think ur right. And I can't upgrade for a year.
Sent from my SPH-D710 using xda app-developers app
Just as a reference I have two SGs2Epic's since Oct 2011, never had any issues whatsoever,in fact we have not set foot in a Sprint store since Aug 2011. My wife has drop her phone dozens of times,once in the toilet, took it apart, let it dry out overnight in front of ac, reassembled the next morning and its still going strong. The only thing we did to these phones was replace the batteries this past DEC. Both phones are rooted ,mine is on st/ro jelly bean, hers on GB Calk's fabulous E4GT v3.0.
Your condition sounds kind of weird? MikeTuky may be right about the low signal theory, sounds plausible.
Correction/ Did go to a Sprint store around DEC 2011,looking for a doc for our phones. / got it at Amazon.
Pp.:beer:
Transmitted from another galaxy with a Jellybean infused P-5113 full of Unicorn porn.
Well like he said the ones that are good are great, but I've had nothing but trouble. 4 replacement phones and all the same problem b
Sent from my SPH-D710 using xda app-developers app
I have tried asking for a new one, they will not do it. I've even asked for a different phone and all they offered was the Motorola photon lol they said that's the equivalent to this phone. I have called sprint many times and spoke with many different supervisors. Now that you told me they replaced yours with a new one, I'm gonna keep calling and demand a new one. Should I call sprint or the insurance company?
Sent from my SPH-D710 using xda app-developers app
Greek81, by any chance do you work or live near radiation?
Radiologist?
Microwave inspector?
Moon rock collector?
Do drag your feet on a carpet while just wearing socks?
Just curious.
Pp.:what:
sent from a jellybean filled epic touch.
No don't live near anything like that. Its definitely the phone. I just need to get them to send me a new one somehow.
Sent from my SPH-D710 using xda app-developers app
i doubt they will give out new ones now, since the s3 has been out for a while and s4 rumors are running rampant and that usually means a release in the near future. what i don't get is how Samsung/sprint can let so many defective units remain in circulation. you would think a recall would have happened at some point. i cant get my gps to work if my life depended on it and i tried every trick in the book and 2 replacements to fix it. Though i guess it doesnt matter to me at this point since im jumping ship to t-mobile as soon as the s4 drops
although, im curious to know if the other gs2 variants have the same issues just to know who i should blame.