Hello everybody. It happened 2 months ago on my Nexus 10 and I don't know why. I've been trying to find somewhere in my area to fix this issue but it seems to be impossible. I bought my Nexus 10 on ebay.de, do I have to send it back to Germany for fixing it? If anybody know how to fix this error please tell me. Thank you so much
TOPmastermind said:
Hello everybody. It happened 2 months ago on my Nexus 10 and I don't know why. I've been trying to find somewhere in my area to fix this issue but it seems to be impossible. I bought my Nexus 10 on ebay.de, do I have to send it back to Germany for fixing it? If anybody know how to fix this error please tell me. Thank you so much
Click to expand...
Click to collapse
Is it software related? If not you should send it back.
Sent from my Galaxy Nexus using XDA Premium HD app
TOPmastermind said:
Hello everybody. It happened 2 months ago on my Nexus 10 and I don't know why. I've been trying to find somewhere in my area to fix this issue but it seems to be impossible. I bought my Nexus 10 on ebay.de, do I have to send it back to Germany for fixing it? If anybody know how to fix this error please tell me. Thank you so much
Click to expand...
Click to collapse
Did you let it fall or something? My Xoom had a similar issue, and it's hardware related issue. I suggest you changing your screen if you can (or if you still has warranty try sending it back to the seller, but contact him before explaining everything).
Just making sure it's a HW issue, factory reset your device, or see if there's any problem in the screen when booting (Google Splash Logo is a great example).
Hope this helps,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4
XxLordxX said:
Did you let it fall or something? My Xoom had a similar issue, and it's hardware related issue. I suggest you changing your screen if you can (or if you still has warranty try sending it back to the seller, but contact him before explaining everything).
Just making sure it's a HW issue, factory reset your device, or see if there's any problem in the screen when booting (Google Splash Logo is a great example).
Hope this helps,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4
Click to expand...
Click to collapse
I agree- it is DEFINITELY hardware related.
Related
I bought omnia 7 today and i tryed to turn it on and i failed now i'm charging it for hour or two but i cant still turn it on i just got logo Samsung omnia 7 and nothing
how can i fix this?
Was it bought as new or used?
Hey guys,
Sorry for the minor bump, but I've just bought an Omnia 7 and I'm having the same issue. The Samsung Omnia logo flashes for a brief second and then disappears.
switchblade920 said:
Hey guys,
Sorry for the minor bump, but I've just bought an Omnia 7 and I'm having the same issue. The Samsung Omnia logo flashes for a brief second and then disappears.
Click to expand...
Click to collapse
This is so strange. You are like the 5th user reporting something like this. I saw another post over at wmpoweruser describing something similar.
Yeah, it's very odd indeed.
Did they mention any fix it all? In any case, I've already reported the phone as DoA and I should be getting a replacement soon. Hopefully the new one isn't dead either
EDIT: Returned my phone as DoA. Looks like the people who sold the phone to me can't get it working either. So, I think best bet for this problem is to get it fixed/replaced under warranty if possible.
Please see attachment, it is a screenshot similar to the problem I have.
A part of the screen is not touch-respondsive. It only happened recently, never had this problem before.
Possible to fix? I have trouble unlocking the 9 dots pattern everytime I turn on the phone because of this problem.
Please help, thanks.
Never mind, flashed a different kernal and its working now.
edit: Wait, no it's still there.
update: I wiped everything and installed factory 4.2.2 patch (occam-jdq39-factory-345dc199.tgz) but still cannot fix this problem. Please help!
update: Tried this method http://forum.xda-developers.com/showthread.php?t=2027476 still not working :crying:
update: This also not working for me http://forum.xda-developers.com/showthread.php?t=2163924... possible hardware issue?
verdict: I will live with this for now, after 1 day and still can't fix it then I will contact google hopefully for a replacement.
bump
I am having the exact same issue. That almost makes me think it could be a software issue but you said you already did a factory reset.
The weird thing is that it looks like the same part of the screen. Its a horizontal section in the very middle.
My best conclusions are that its the digitizer. It just started happening out of no where though. Very frustrating. Makes it impossible to hit the send button on the stock messaging app without minimizing the keyboard! I take excellent care of my Nexus 4. It has a case and it hasn't been dropped. It hardly has a scratch on it! Its a month old.
Sent from my Nexus 4 using xda app-developers app
Strongertyer I can feel your frustration.
Here's mine (the one in my op was found from google). Mine is a bit lower, it blocks the top half of the qwer line on the keyboard and the yes/no buttons on prompt windows.
I can still type qwer just fine by pressing the bottom half of the keys, but for the the prompts I have to tilt and rotate the screen every time so the buttons aren't under the "dead zone".
Strongtyer are you also thinking of sending the phone back to Google?
Sent from my Nexus 4 using xda app-developers app
Just talked to support and they seemed helpful. However, his first suggestion was to do a factory reset of course. He said if that didn't work then I could send my phone back for a replacement. Did a factory reset and still the same issue. Looks like I'll be calling again tomorrow.
I guess the plus side is that they send brand new phones and not just refurbished ones.
Any luck on your end?
Sent from my Nexus 4 using xda app-developers app
I gave up fixing it already as you can see in my 2nd post and I believe it is not possible to fix it other than having the whole screen replaced, so I asked directly for a replacement under warranty. Then after a brief moment google emailed me a set of instructions for packing the phone.
So on Sunday evening I booked the courier, printed the documents, picked everything back in the box, warped and taped it. And today the courier came and collected my phone.
Now I have to use my good old HTC Legend again. However it uses regular SIM card, so I had a bit of fun making myself an adapter to up size the Nexus 4's micro-sim!
I talked to Google today and they are sending me a replacement. They told me I can keep the phone till the new one arrives. I just have to return it within 21 days.
Just crossing my fingers that they don't say the damage is my fault. I don't know how o could have caused it. I haven't does it and I take really good care of it.
Sent from my Nexus 4 using xda app-developers app
Same problem
I do have a same touch screen problem.
Sliding vertically is not smooth and cannot clicking, but swiping horizontally is working.
im also having this problem but i dont live in the US. how can i go about fixing it?
redsuns said:
im also having this problem but i dont live in the US. how can i go about fixing it?
Click to expand...
Click to collapse
You should contact google anyway if you want a warranty replacement. Go to the link below, click contact google, answer a few check box questions and there should be a phone number.
https://support.google.com/googleplay/answer/2411741?hl=en&ref_topic=2803008
Because I believe that the only way to fix this is to have the screen replaced.
Have the same problem here. I have the phone for 1 month now.
I live in the Netherlands and the nexus 4 did not get official release here. Should I still contact Google?
Could it be this problem only happens with the newer phone's? I have the one with the little feet on the back. Version 605 I thought. What version do you guys have?
Also should I unroot and lock the boot loader when I send it in for repair ?even though the problem has nothing to do with it.
Sorry for the poor English...
herrieherrie said:
Have the same problem here. I have the phone for 1 month now.
I live in the Netherlands and the nexus 4 did not get official release here. Should I still contact Google?
Could it be this problem only happens with the newer phone's? I have the one with the little feet on the back. Version 605 I thought. What version do you guys have?
Also should I unroot and lock the boot loader when I send it in for repair ?even though the problem has nothing to do with it.
Sorry for the poor English...
Click to expand...
Click to collapse
Welcome to xda-developers. Your English is fine.
You should contact Google.
Interesting that you mention the newer version of the phone -- I'd be interested in knowing if this is in fact a result of a newer manufacturing process, different materials, or maybe the place of manufacture (Korea or China). The place of manufacture can be identified by the letter in the fourth position of the serial number found on the box.
can someone update us on this issue? I have the same problem and i am so sad! I saved up 8 months to get this phone!
2nd
herrieherrie said:
Have the same problem here. I have the phone for 1 month now.
I live in the Netherlands and the nexus 4 did not get official release here. Should I still contact Google?
Could it be this problem only happens with the newer phone's? I have the one with the little feet on the back. Version 605 I thought. What version do you guys have?
Also should I unroot and lock the boot loader when I send it in for repair ?even though the problem has nothing to do with it.
Sorry for the poor English...
Click to expand...
Click to collapse
yup just to chime in same problem here too .. its pretty widespread !
Same ISsue - Nexus 4
jeetash said:
yup just to chime in same problem here too .. its pretty widespread !
Click to expand...
Click to collapse
well, its certainly a hardware issue.
Digitizer, for what I know.
But no easy solution.
Would have happened due to the faulty charger.
But google is not helping!
I have the same exact issue. Playing PVZ2 is now extra difficult because of this issue.
Is there any other fix other than an RMA (currently not in the US)? :crying:
Verbl Kint said:
I have the same exact issue. Playing PVZ2 is now extra difficult because of this issue.
Is there any other fix other than an RMA (currently not in the US)? :crying:
Click to expand...
Click to collapse
Fixed with the update to KitKat!
Posted via Tapatalk
Verbl Kint said:
Fixed with the update to KitKat!
Posted via Tapatalk
Click to expand...
Click to collapse
I have this same screen issue. Mine is is first row from top which makes it very frustrating. I am on 4.4.2 and still have this issue.
Can you describe what you've tried in more detail?
I have the same problem but mine is like 2 inches from the bottom of the screen. I can use the softkeys in portrait but they are unusable in landscape. I have had the phone since Nov 12 so sadly my phone is now out of warranty. LG's approved repair centre want £95 for a new screen. I am thinking maybe buy a Nexus 5 and trade this in for £70. I could sell it for like £130 but I would feel bad selling a phone I know the screen is on its last legs.
Hi everyone,
I recently bought a 16gb 2013 nexus 7 at Walmart, and I really love the feel and the screen clarity of the device. But it has this shutdown problem when I first remove it from the box. Like during the initial setup when I enter in the user name and email address, it turned itself off at least after each step. One after entering my name, one after entering my email address, and one after registering itself with google. After the initial setup, it then do the automatic update to 4.3 and the. It shut itself down a few time during that sessions.
Also, it shut itself down twice white I was watching some YouTube video, and about three other random times while I was casually reading a website forum, I was reading about the issue of nexus 7 random shutdown by the way.
Anyway, I immediately returned the device within that same day of purchase. Though I really like the device and would like to buy it again.
I was wondering if all 2013 nexus 7 device suffer from this random shutdown issue, or did I just got a bad unit.
Thanks everyone
Don't know. You should probably go ask in the correct forums.
Sent from my Galaxy Nexus
Pirateghost said:
Don't know. You should probably go ask in the correct forums.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
But this is the nexus 7, and it says troubleshooting and questions and answers. I think I'm in the correct forum.
Wrong or right topic, I had this issue with my N4 once since I got it a month back.
I turned on 3G and my N4 rebooted on its own without reason.
Send from my Nexus 4
Oops, I am in the wrong forum. Please excuse me.
I've had 3 N7's, 2 16GB that had the random reboot issue and my current 32GB that has the random shutdown. Back to Staples this one goes too. Perhaps this will all be sorted when the 32GB LTE is released.
xxcysxx said:
But this is the nexus 7, and it says troubleshooting and questions and answers. I think I'm in the correct forum.
Click to expand...
Click to collapse
xxcysxx said:
Oops, I am in the wrong forum. Please excuse me.
Click to expand...
Click to collapse
Haha )
Hi guys & girls,
My daughter keeps wrecking smartphones and so we got her a Motorola Defy+(PAYG). It was bought new and unlocked with the French Retail ROM and once i put in the SIM(O2-UK) and tried to top-up her credit(4444) it would not dial out and did not give any problem message. I also tried to ring her number from my phone which came up with "it has not been possible to connect your call - please try again later" message.
I did a hard reset and got the same problem so I downloaded the latest UK Retail ROM from XDA(this went on no problem) and tried again - Same problem. The box states it is for use in EU & UK/IE so this cannot be a problem.
I have the correct APN settings and have tried 2 other O2 SIMs but still the same problem exists??!!
The only thing i think it could be is a hardware fault and i need to send the phone back.
Everything else works fine WiFi, GPS etc etc.
Apologies for the long winded explanation but i thought you would get more responses this way :highfive:
Any assistance would be of utmost value as im stuck with a daughter needing her mobile like yesterday!!
The ril bug is present in the stock rom, which is responsible for this issue. The fix for this is board replacement. Alternatively you could try cm7, which will give you an error confirming the issue, and may even fix it
Sent from my MB526 using Tapatalk 4
thekguy said:
The ril bug is present in the stock rom, which is responsible for this issue. The fix for this is board replacement. Alternatively you could try cm7, which will give you an error confirming the issue, and may even fix it
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for you for the speedy response 'K Guy' I have messaged the seller and await his waffle before i get my money back. I would try CM7 if it was my phone but i'll wait to get my money back first.
Is there a phone similar to the Defy+ which my daughter wouldn't break in 5 minutes because i take it the ril bug would affect all Defy+ mobiles??
Once again thanks for your input :victory:
The closest would be one of those Xperia models, but nothing beats the indestructible defy. I have personally dropped mine 85854 times
Sent from my MB526 using Tapatalk 4
thekguy said:
The closest would be one of those Xperia models, but nothing beats the indestructible defy. I have personally dropped mine 85854 times
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Thanks!!...I think im getting a full refund so I will look for a good replacement :fingers-crossed:
I created a thread in the T-Mobile forum, so I hope this doesn't seem redundant, but I didn't find many solutions on that thread. Here's a thorough explanation of the problem that I'm having and everything about my device. If requested, I'll upload screenshots from my phone that could potentially help, but I have uploaded a photo of my "About device" screen. Apparently the issue I'm having is very likely not hardware related, so if anyone could solve it I would really appreciate it.
Details on my device: My device model is a the T-Mobile variant (G900T). I purchased it from a reputable seller on Swappa in "Open Box, New" condition. Upon receiving it, I immediately unlocked it via Unlockunit, which is apparently a good site for unlocking phones. I received the code with no problems and it worked. My phone has had the problem I am about to describe since making my first call about eight days ago.
Problem: All callers are reporting that they hear themselves echoing on their end of the call. Basically, when they talk, they hear themselves talking as well as me. They report my voice as sounding like I'm "in a tunnel." Also, when I move the phone, they pick up a lot of distortion. This happens during all phone calls and is not dependent on the signal strength or location of the person I am calling. It does *NOT* happen when using speakerphone.
What I've done to try to solve it (nothing has worked): I've factory reset my device both from the "Backup and reset" menu and through Odin. I called Samsung who helped troubleshoot the device. The representative had me clear the cache in the phone app, remove the battery and SIM, and replace the battery and sim. I then contacted AT&T who tried a few things in the background (details were never given on what was going on) and said they would check the towers in my area. Next I tried swapping SIMs which also did not work.
Current state of the phone: The phone is currently completely stock, unrooted, and with no custom recovery installed. Still, I am experiencing the issue.
Bump
Do you have a case on the phone
Sent from my SM-G900V using Tapatalk 4
irish84 said:
Do you have a case on the phone
Sent from my SM-G900V using Tapatalk 4
Click to expand...
Click to collapse
Yes, but I've removed it and it occurs without the case on, too.
Sorry them I am of no further help. Me and my wife have life pro cases and it is a know defect with them to cause feedback "alien voice". Called them up and they are sending out a case that should take care of the problem. Good luck.
Sent from my SM-G900V using Tapatalk 4
irish84 said:
Sorry them I am of no further help. Me and my wife have life pro cases and it is a know defect with them to cause feedback "alien voice". Called them up and they are sending out a case that should take care of the problem. Good luck.
Sent from my SM-G900V using Tapatalk 4
Click to expand...
Click to collapse
Yeah, I read about that but I don't have a Lifeproof case. Thank you for the suggestion, though.
Bumping this again. I'll be sending the device out for repair tomorrow unless somewhere on here can help me figure this out. I really don't want to do that, though, because my Knox is tripped and I'm pretty sure that it won't work out for me, but it's my last hope. Hopefully someone on here can solve this. Thanks!
Still having this problem. I hope there's someone out there who knows how to fix it.