Related
So my earpiece has gone.
Not crackly, not distorted, just nothing - silence.
It was fine a couple of days ago and now it's completely dead.
The phone hasn't been dropped (well, tossed on a mattress/duvet when I'm heading to bed but not onto anything hard and from no great height), I haven't tempted fate by submerging it, I've properly nursed this phone and it's still died on me.
The one thing that I did do between it working and today was flash a different ROM.
I'm just wondering whether there's any chance that might've had something to do with it?
I went from '3.4.2 131-003' to '3.4.2-155-2'.
I know it's a long shot but that couldn't possibly be the cause, could it?
Many people have already complained about that problem (just google it!), return the phone (if your warranty isn't void because of the flashing, but i think it only affects software warranty), and they'll get you a new one. As far as I know, the newly produced defys don't have that defect anymore, mine - which I bought a couple of weeks ago - works just fine (fingers crossed!).
I'm aware that it's a known issue, I was asking because it seems that normally the earpiece gets crackly then dies whereas mine has gone from absolutely fine to completely dead in a couple of days with no usage in-between and the fact it happened after I flashed a new ROM seems coincidental to say the least.
As for the warranty, I have flashed ROMs, so fingers crossed.
same problem
I've the same problem.. no crackling, total silence. yesterday it worked perfectly fine, but since today no sound at all.
didn't do anything weird with it; flashed another froyo rom one week ago, but I can hardly imagine it has something to do with it...
I red there were more persons with a earpiece problem, but I couldn't find anyone who's got total silence from one moment to another..
is there info about this issue?
greetz
mine has gone from working to total silent the way mine was crackly was if i blew into it, it would work sometimes but now nothing at all i need to get a replaceable but dnt ave time
The problem is due to a bad connection, so I suppose it is possible it would break cleanly, going from working to silence with no interference/crackling.
I was just hoping I could fix it myself without having to rely on the Motorola warranty lottery
The fix-it-yourself thread is here. It's easily done if you are even mildly practical. I have sourced 2 SE K850i earpieces as a hedge against the future, once I'm out of warranty.
However, I am currently in warranty, so I sent an email regarding my Defy to Motorola as soon as my earpiece started acting-up. I tried to demand a replacement on the grounds that they were offering for sale devices that they knew were defective. Unfortunately, they were adamant that a repair was my only option so I sent my phone to their centre. I followed their advice, backing up, removing SIM and SD card, performing factory wipe from within Settings/Location & Security, and only sending the phone.
My phone had a custom ROM with the "android" text boot-loader so it was obviously not stock but there have been no complaints from them and I'm able to track my phone through their system. It's been repaired and is in "final testing". I'm expecting it back early next week.
Given the perceived "openness" of android, it would be a PR disaster for Motorola to void the hardware warranty on the grounds of software modification.
Step666 said:
So my earpiece has gone.
Not crackly, not distorted, just nothing - silence.
...
The one thing that I did do between it working and today was flash a different ROM.
I'm just wondering whether there's any chance that might've had something to do with it?
Click to expand...
Click to collapse
mmm, i have something to say ... i flashed lots of different roms, two weeks ago i went back to China 0.26, still one of the best in terms of performance BUT, i had some trouble with the earpiece.
The first time it happened i thought "ok my earpiece has gone", it was just silent, people could hear me and i could hear nothing. Surprisingly after a reboot the earpiece was working, then silence again the day after... so on for 3 - 4 times.
Then i flashed the 3.4.2-155 and the problem disapperead. No failure, no silence, after 10 days it still works.
So, could it be the problem was related to that specific rom or software i used?
Btw, did you try to flash back to your previous rom?
I got same issue last week, and my mobile operator change my phone by a new one.
It's a know pb with first MB525 products.
After flashing did-you remove back door and battery to power off/power on you phone ?
I think when we do that, we push on the back of phone and so increase earpiece failure risk.
Thanks, I'd seen that thread before but I'm still well inside my warranty and have no urge to risk voiding it any more than I potentially already have.
I have no qualms about having to send the phone back to Motorola, I just want to be sure it'll be fixed when I do is all.
It's a shame that Motorola don't allow third-parties to fix the handsets - I know an engineer that works for one of the UK high street mobile phone retailers and he says that any earpiece issues, they have to send the phones back to Motorola themselves, they can't even source the necessary parts.
If they could fix it, I wouldn't think twice about the ROM as I know he couldn't care less, he'd get it sorted for me.
technome said:
Given the perceived "openness" of android, it would be a PR disaster for Motorola to void the hardware warranty on the grounds of software modification.
Click to expand...
Click to collapse
Also, since the issue is known to be purely hardware and there are plenty of cases of it afflicting handsets that are entirely stock, they would leave themselves in a very shaky legal situation.
Personally, I think I'd prefer to have my current handset repaired instead of replaced as it seems to be a little gem in terms of battery life.
As for the warranty, I doubt I'll have this phone for more than a year or so.
Part of the reason I chose it was the excellent deal on the T-Mobile contract I'm on meaning that if I get the urge to 'upgrade' early, I won't feel bad about buying a second phone out of my own pocket.
xdaid said:
Btw, did you try to flash back to your previous rom?
Click to expand...
Click to collapse
No I haven't.
I only discovered the problem at work this afternoon and started this thread as soon as I got home.
I might give it a go over the weekend but part of me can't really be bothered, I might just send it away.
edit:
MisterWB said:
I got same issue last week, and my mobile operator change my phone by a new one.
Click to expand...
Click to collapse
UK law only gives a customer a limited period after purchasing during which they can demand a replacement, after that a retailer is entitled to try and repair a faulty item if it is reasonable to do so.
Only if repairing the phone is in some way unsuccessful would the customer then be entitled to a replacement.
Sorry to hear that.
Let us know if Moto honor the warranty. It's very unreasonable to void hardware warranty just because of software modification.
My defy earpiece failed after 4 weeks. I had the orange 2.2 on the phone. Sent it to solidvision (they do warranty repair for motorola phones in belgium and netherlands). 3 weeks later they sent me a new phone, under warranty. On other sites I read that motorola doenst make a problem about earpiece issue even when you flashed other firmware.
So I handed my handset in to be sent away for repair on the 21st of March.
On the 18th of April I contacted CPW's repairs department to query where my handset was at 28 days had elapsed. The guy I spoke to raised a £10 voucher on their systems and put some sort of trace on it for me.
And on the 21st I was contacted by the store I'd handed my phone into to say it was back.
When I say 'it was back', it's not the same handset I sent away - it's a 'clearance' replacement handset. Thankfully my mate who works for CPW checked the handset's history on their systems and it's not a refurb, it was sat in a store for a month without being sold, then recalled to the warehouse so they had one to send to me.
I just hope this 'new' handset has as good a battery life as the one they kept...
Can anybody help me out with this? I've already searched but haven't found a clear cut answer on what to do.
For a while, I've had random events that cause my HTC Evo (running the latest stable release of CM7) cause my phone to suddenly show the "HTC Evo 4G" white screen, then go black and vibrate 5 times while having the green LED on, which never lets me do anything until I pull the battery out and start it up again. It used to only happen when I did specific things, like whenever I tried using Google Goggles at the store (and had to go through all the trouble of disassembling my 3 layer protective case just to pull the battery again). It even happened again yesterday when I was trying to use Goggles on a specific item, but it has happened before in other events since then, like when I was browsing my phone's running applications menu, or even one time when I was simply browsing the internet on it.
I've been taking steps to try and fix it, but I think it's been getting worse. I tried downloading CM7 and Google Apps again to flash on the phone to see if it fixed anything. I tried doing this again, but clearing the data and cache this time. I tried flashing the latest CM Recovery (since I stayed with 2.5.x.x for as long as I could remember), and I'm pretty sure it's gotten worse. There's points where I get to the CM7 boot animation and the phone then does the white screen and five vibrates again, and just a moment ago when I was sure I finally solved it after clearing data and cache, while filling out my Google account info, it happened again and I was greeted once again by that horrendous white screen and the five vibrates.
Now I don't know what to do. I still have S-OFF, but I have no plans to unroot. Can anybody think of suggestions? I've already tried Googling and haven't gotten anything useful enough to help me so far.
EDIT: I guessed it would help if I was a bit more specific. This started happening about two or three weeks ago after I tried using Goggles for the first time in ages. Since then, I've had this issue coming back over and over. It also puzzles me how Goggles usually works completely fine when I'm at home but causes the phone to go black and vibrates 5 times whenever I'm at a store.
Also, right now, I re-downloaded CM7 and Gapps from the CM mirrors instead of simply reusing the ones that ClockworkMod had saved for me already. I hope this somehow makes a difference.
Also, last edit, if I manage to solve this somehow, I'm going to definitely post the answer to what I did in case anybody else out there is having the same issue.
EDIT 2: Welp, re-downloading CM7 and flashing again didn't do anything to fix the problem. I'm going to try another ROM to see if the problem persists. I really want to stay with CM7, though.
Did you wipe everything? Cache and so on ect....?
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
SirSigma said:
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
Click to expand...
Click to collapse
Why would you lose root "for ever"?
Just curious ....
Sent From The Tree House Out Back!
I had the same exact issue with my Evo over the past 2 weeks. But I never use Goggles and run MIUI pretty much exclusively. I was never able to fix it and it just got worse. I unrooted and still have the same problems.
I notice it happens on 3g data, I can't remember when it happened on wifi.
I am selling mine back to Sprint tmrw and using my upgrade to get the Nexus S for$50. Then hoping the Evo 3D comes out within 30 days.
Sent from my PC36100 using XDA Premium App
I took it back to Sprint today, and after being treated like a second class citizen for rooting over and over, they managed to somehow fix the random reboots, but have initiated the OTA update for me. Now I'm sitting here with it and it's asking if I should install it now or later.
I'm hesitant because I tried to unroot earlier, and since then, the technician at Sprint said that it wasn't really unrooted or something (I remembered using unrevoked forever last year when I rooted). I'm scared that maybe I'll lose my chance at being able to root again if I accept the update or not. I'm also scared if I won't be able to get full root from here.
EDIT: SON OF A *****. I can't believe this. I applied the OTA update like a good boy and everything, and then the phone starts boot looping randomly again. This is the last straw. I'm going to go back to Sprint tomorrow and be more in-your-face about this problem. I'm through letting them treat me like **** just because I rooted my phone once.
I have a similar problem.....
My problem is random. My phone will go into constant reboot mode until I pull the battery out for 10 minutes. Just pulling the battery and putting it back does not help.
I also noticed that I am losing GPS signal occasionally. It is random too. The GPS will come on and work for about 5 minutes then just lock up. I have to reboot to get it working again and there is no rhyme or reason as to when it will stick (or wont) or how long it will last. It may work for 3 days and then not work a lick for 3 days.
The local Sprint store replaced the back red portion of my phone (the part with the camera lens and kickstand) stating it was an GPS antenna problem. I got 30 secs outside the store and tried the GPS....same problem. I went back into the store and showed them and they tried to convince me I needed AGPS on as well. AGPS always worked but is not as accurate as the satellite GPS. The repair shop refused to do more or order a replacement. I just got scammed out of $35.00 cause nothing is fixed.
I got so pissed, I called Sprint. They were terrific. They refunded the $35.00 the repair center charged me of the repair (the rip-off repair) and agreed to send a replacement phone. Awaiting arrival of the replacement but they are back ordered...so, maybe, I'll get a new phone instead of a refurb.
Long story short...I don't know what is causing your reboots. Mine could not be solved by software changes. My phone was rock solid until around a month ago. Then the GPS dropouts and reboots became more frequent until they became unlivable. I think you have a bad device and would seek replacement.
I had the same problem with mine about a month ago. It happened once about a month before that and then a month ago started happening a lot. I finally narrowed it down to how "hot" it was (body temperature in this case). So basically any time that I was in the car it happened. I was able to unroot (you have to make sure you to s-off on) and put a stock rom on it, and take it in with it happening. They took it for an hour and said they had not seen any issues. I finally convinced them and the replaced it with a refurb. I'm okay as long as it works, but it makes me wonder what happened. When I first got it I used fresh for about a week and then went to CM and was on it the rest of the time. I used an SBC kernel starting around the same time and am thinking maybe that had something to do with it... Just as a precaution I'm staying away from SBC kernels.
If I were you I would just go to the store and get a replacement if you can otherwise if it's like mine you won't be able to count on it working...
Good luck
Hey folks
These aren't really random reboots, and they don't seem to be caused by an app. They're more like 'when I touch it the wrong way' reboots. If I set the phone down, or pick it up, sometimes it will reboot.
I checked the battery contacts so that's not it. I'm thinking its either a problem with some internal contacts, or something with the accelerometer.
Has anyone experienced something similar? I just passed my 1 year manufacturer warranty period, unfortunately.
Thanks
Sent from my HTC Vision using XDA App
Hmm sounds like a hardware prob. It shouldn't be the accelerometer. Does it reboot when u are using it?
It rarely reboots when I'm using it. It will usually reboot when I pick it up or set it down. If I drop it on my bed from 2 feet up for example, it may reboot. What's weird is that its not a guarantee. In fact I've gone days without a reboot, and sometimes I'll get numerous reboots in a day.
Sent from my HTC Vision using XDA App
Several people have noted there can be a problem with the battery not fitting snugly into the chassis of the phone. When you drop it, the contacts on the battery can move slightly off the contacts on the phone and it can reboot. Some people just shim the battery down a little.
> Has anyone experienced something similar? I just passed my 1 year manufacturer warranty period, unfortunately.
I do not know how far you are out of warranty.
I was in the same situation 2 weeks ago. I was on my last day of warranty (so I thought), when I got tired of the constant reboots. I went to my local TMO store and they claimed that I was out of warranty by one day. Fortunately they put me on the phone with customer service. There it was confirmed that my warranty was out since 1 day. The person was very nice and said: "Let me see what we can do for you". She came back after one minute and offered me a waiver that would have allowed an immediate full upgrade. I told her that TMO does not really have any upgrade that I was interested in (I wanted a keyboard and stock Android), so she went back to her supervisor and came back with the offer that they would assume that my warranty would not run out on that day at 12am, but at midnight and that they would replace the phone under warranty. I have the phone now for a week AND no more reboots. TMO rocks !!
PS: I am with TMO for > 7 years
Yea tmo had some awesome customer service from my experience! I really hope they don't get bought out. Kinda inevitable though since the owners don't want it...boo!
Awesome experience! I work in Customer Service, so I know that I could theoretically get it replaced and whose arm I have to twist to get it. But I don't have the time to spend doing so. My phone hasn't rebooted in a few days now. I did a full wipe before I flashed my next nightly. I have my fingers crossed that it stays that way.
Sent from my HTC Vision using XDA App
I feel silly even mentioning this, because I thought I might be the only one dumb enough to suffer from it, but I will go ahead and mention it anyhow. I was hating the reboots with my G2, and found somewhere that I needed to actually make sure the SD basket was locked in place. I had replaced my SD card, and didn't realize it slides into a locked position. Have never had a reboot since I clicked it in place. That was months ago. Hope it is something that simple for you. Yes... I know I was a dufus for not realizing how the SD basket worked.
I had the exact same problem and I could not figure it out. I finally did a complete wipe and reinstalled problem stopped. I also converted my partitions to ext4 but not sure if that would make a difference.
Could it be the radio?
I did a full wipe prior to flashing CM #231. I used titanium backup to restore my apps. Now the reboots were gone!
But my GPS problems returned. I flashed the next best radio 26.08.04.30. Last time I initially switched radios to fix my gps problem. GPS is still broke, and now I am rebooting again.
Sent from my HTC Vision using XDA App
Hi all,
I recently sent my GN (Running 4.0.2 stock, yakju build) back to be repaired because my phones wifi stopped working. what happens is that the phone's wifi seems be stuck "turning on", but never actually does. No wifi icon or anything appears. wifi hotspot doesnt work either. I had my GN from about a week after it was released (I'm in australia so that was about the 22nd December), and around the 15th January is stopped working. This issue cannot be fixed with a reboot, a hard reset, flashing stock roms, toggling airplane mode or anything trivial like that, as I (and others) have tried.
Now i have searched a while on google while i have been without my phone and I'm finding this problem is surfacing for other people too. From what i have seen there seems to be a correlation between 4.0.2 and this issue. Also, it seems to happen some time into the phones life; they do not have this issue when first purchased. I am concerned that this may be a recurring issue which surfaces over time, due to a design flaw or some sort of software issue. If so, this problem will start affecting a lot more people. If anyone who reads this has the same problem, could you please post when it started occuring and what rom, build etc (and anything else which may be helpful) you are running so we can shed a little light on this issue. which many more users i am sure will experience. cheers in advance
just incase anyone actually reads this Galaxy Nexus was sent back, and it was found that the printed ciruit board (PCB) needed replacing. More forums have surfaced since i last checked up on this problem so numbers are slowly rising. Once again, post here if you get the issue, we need numbers
Hi same issue i have butni solve i am living in turkey and i use habertürk news and i saw this application make notification wifi turning om.i reset my phone i load factory firmware but nothing happen ...always say wifi turning on...you need to change your system language another still write wifi turning on on screen in eglish and a application cause to this like my haberturk app
Sent from my Galaxy Nexus using XDA
same problem
Hi,
i had the same problem, wifi mac info was not showing anymore on the Nexus. Reboot and factory reset didn't help. Wifi wouldn't come on anymore.
Ask for a replacement, that's the only thing you can do
Can i ask what version of android you guys had? I'm wondering if this is going to be a recurring problem with hardware due to software issues or if it is purely a design flaw (PCB burning out, etc..) Cheers!
I have the same problem which happened last Saturday and it frustrated the hell out of me, i flashed to different versions of OS....didnt help...
restored to factory firmware and didnt backup the pictures and stuff on the phone!! (FML)
and brought it in to Fido on monday to have it serviced....
talking about bad luck...sigh....
they told me the turn around time is 10-15 business days... (N)
will report back once i hear from them
Before the issue happened, did your phone have any other issues? Say heating up while charging or running the WiFi?
I received a device in for repair with this issue and the customer reported it got really hot before the issue started happening. Everything looked fine on the motherboard - the WiFi antennas were intact. Reloading the software did nothing which means it's a hardware issue..
So very strange. I wonder what's causing this.
i remember when my wifi stopped working i was running 4.0.2. I was actually on holidays in Japan at the time and i was wifi hopping quite a lot around the airport (i was walking around and the wifi would go out of range, latch on again... etc) not sure if that had anything to do with it. Hopped on the plane home and i remember i was on airplane mode using an app called colornote. the phone hung pretty hard and i had to pull the battery. rebooted and tried again and after 10 mins, phone crashed again doing the same thing. Got home and the wifi wasnt working. Not sure if any of this had anything to do with it, but maybe. Didnt notice any overheating, but then again i was around snow haha
hi mrmiklepower
just wondering if your phone has been good since you got it back from repair?
i noticed the phone would reboot itself over and over again after i flashed it back to the stock rom. I just called the third party repair shop that my carrier sent the phone to, they told me its still being fixed.
Oh i hope they will return me my phone soon.
My phone is actually still being repaired also. It's been a total of 2 months since i sent if back! they contacted me and all i know so far is that the phones PCD needed replacing. when my phone arrives i will update as soon as i can. should receive it sometime this week, but its not certain. the majority of my ownership of this phone has been me waiting for its return
Holy mother of lord...
I actually called the third party repair shop that my carrier uses to check on the status of the repair. And they told me its actually In quality control which means the problem was fixed and they're just testing it before they send it back to the store where I brought the phone too. Hoping they'll send it in on Monday so I can either pick it up on the day of or the next day.....keeping my fingers crossed.
Will keep you posted on the status of it too.
Sigh
Ok I got my phone back today.
on the reference sheet I got from the repair shop
it states REPLACED PBA, BGA Failure
I looked it up online and PBA means Printed Board Assembly
which probably means the motherboard was defective and had to be replaced.
and now the phone is working fine. So i guess when this phone was made, there were some flaws with the motherboard on it, thus causing this problem.
Anyways, I hope this information helps with others who experience the same problem
Thanks for letting us know! O got mine back today with the same thing. So looks like there is no way of fixing besides sending it back. Good luck to anyone else who gets this problem
Sent from my Galaxy Nexus using xda premium
So it seems there's no fix for this?
I've been doing some research and it doesn't seem anyone can fix this.. I tried reflashing, wiping every possible thing, etc.. even flashing the stock software via odin. Still no luck.. It seems that we are indeed stuck with sending it back in for a supposedly defective part which seriously blows.
My other question is.. you guys who already received your phones back, did anyone end up with the problem again?
PLEASE if anyone knows how to fix this.. chime in!!!
I had an issue similar to that with my transformer and to fix it I just flash a new kernel im not sure itwill fix the problem for you but it's worth a try
Sent from my Galaxy Nexus using xda premium
Since getting my phone back the problem has not occurred again. I don't think there is anything that can be done as a component needed to be changed apparently. Good luck :/
Zeon45 said:
I had an issue similar to that with my transformer and to fix it I just flash a new kernel im not sure itwill fix the problem for you but it's worth a try
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, when returning to stock it flashes a new kernel. Also tried it again for the hell of it with faux's kernel, still no luck .
This sucks! This very same thing happened to me yesterday! I Odined back to stock.. no luck! Now after finding this thread, it looks like a hardware issue! That blows! I'll have to give Sprint a call tomorrow!
Hmm sucks to hear it's still cropping up around the place, I heard someone say this issue entered quality control. But anyway, if it helps I've had my phone back for about a month and a bit and its still going strong. hopefully it doesn't happen again though. good luck, hopefully it won't take too long for your phone to come back!
Hi,
I'm with Telus in Canada and had the exact same problem and had my GN repaired. It took only 2 weeks and I just got my unit back. I had already read a lot online about this issue so I asked the Telus rep to tell me what the issue was. She told me that the report states that the board was replaced. This is definitely a hardware problem. I'm hoping that the new board doesn't have this problem and my phone won't need to be repaired again,
I run 4.0.1 on my phone. Telus hasn't released an update yet. I was going to update mine by switching to yakju, but that's when I noticed that the wifi is not working and I thought it's not a good idea to change the stock ROM.
After flashing the stock google (yukju) roms on my galaxy nexus, everything went fine for a couple of months and now I am getting weird haywire issues with my touch screen. Without me touching anything, the phone will act like a part of my screen is being touched, it will not respond when I am indeed touching it at times, the screen will flicker back and forth and generally act strangely. Then for the other 70% of the time it is fine. I have re-flashed all stock roms, did a factory reset, and the problem persists.
Is anyone else having these problems?
any idea what to do next.
After contacting my provider, they said they cant help me because I had unlocked the phone. I have since relocked the phone so I might try calling back and seeing if it will fool them, but I doubt it. Now that I have re-locked the phone should I try to deal with Samsung?
Any help appreciated!
It sounds like a hardware issue. Most likely the touchscreen itself is bad. If you still have warranty or insurance coverage then bring it back to the store and tell them it is defective. By the way, NEVER mention that you have ever unlocked or rooted your phone.
Sent from my Xoom using Tapatalk 2
Thanks for the reply. Im worried that, like you say, it is a hardware issue because I bought it used, and therefore will probably have problems with warranty/insurance. My carrier has already said that they wont help me with it so I would have to go right to Samsung. Any tips on dealing with Samsung? I have already returned to stock and re-lock the phone and I never rooted it, I certainly wont say I did anything to it in any way. Anything else I should be aware of? Will they even help me out since I wasn't the one who bought the phone in the first place?
GentlemanBasdard said:
Thanks for the reply. Im worried that, like you say, it is a hardware issue because I bought it used, and therefore will probably have problems with warranty/insurance. My carrier has already said that they wont help me with it so I would have to go right to Samsung. Any tips on dealing with Samsung? I have already returned to stock and re-lock the phone and I never rooted it, I certainly wont say I did anything to it in any way. Anything else I should be aware of? Will they even help me out since I wasn't the one who bought the phone in the first place?
Click to expand...
Click to collapse
Although most manufacturers offer a 1 year warranty on hardware, I doubt they will honor it since you were not the original owner. Your next option is repairing it yourself. It took a look at prices on eBay and it looks like the digitizer (touchscreen) for a galaxy nexus goes for about $30 and the combination of digitizer and LCD screen go for about $150. I don't know how difficult it would be to separate the digitizer from the LCD on your phone, but $150 for the set is still better than buying a new phone.
Sent from my Xoom using Tapatalk 2
As has been said, it is probably a hardware issue - I had an HTC Desire S before my GNex and had the same issue with it, started all of a sudden. (The screen would go haywire as you said, almost as if a ghost was pushing buttons quickly - that's the best way I can describe it). Mine did not have warranty coverage because I had rooted and unlocked it but the HTC rep was helpful and said it happens sometimes because of moisture or humidity or some such thing and to replace the lcd/digitizer. Cost me a little ($110) but phone was as good as new after that, used it for six months before selling it and buying the GNex.