Recently I have really began to notice a few things with my nexus 7. They are really starting to bug me, so any help I can get would be great.
The first thing that I have noticed is charging port is crooked.I do not know how it happened, but it doesn't seem to want to have a charger in it very long. Its touchy, and the cable is ALWAYS falling out. I've tried fixing it several times, but nothing seems to really work.
The next problem I have is my screen has a spot where the backlight bleeds a little. It is in the middle-left part of the screen, so I'm wondering if there is a screw or something that is too tight in there.
The final problem is no matter how hard I try, the OTA update will not work. It will just say ERROR and nothing else. I will reboot and be in 4.2.2 again. Resetting the "googleservicesframework.apk" will let me download it again, but the same problem arises afterwards. I was rooted, but when it errored the first time I did a factory reset and it still didn't work afterwards.
Once again any help is appreciated, thanks in advance!
I can't help you with your hardware problems but you can install 4.3 manually instead of OTA.
The micro USB port is on its way out. Needs to either be Rma'ed or if you can't/won't send it in there are guides that will show you how to replace the USB/headphone I/O port
Sent from my Nexus 4 using Tapatalk 4 Beta
Related
Really weird.. Out of nowhere , the bottom right corner of my screen has become almost totally unresponsive to touch. The L and the backspace button on my keyboard are nearly unusable.. Anyone have any idea as to how I may be able to fix this? Its like there is a 2 inch by 1cm gap on my touch screen that doesn't respond to touch.. Thanks guys
Sent from my Nexus 4 using Tapatalk 2
Warranty exchange..
Wish I could... Bought the phone through tmobile and I'm getting the run around.
Sent from my Nexus 4 using Tapatalk 2
I have the same problem, but its a band across upper 1/3 of the screen causing weird typing and such, but only in portrait.
Sent from my Nexus 4 using xda app-developers app
Nexus 4 touch screen defect (dead zone, phantom touch)
I have the same problem, I have a permanent ~1cm tall dead zone spanning the width of my Nexus 4, right about the location of the SIM card tray.
On occasion it is not a dead zone, but rather a "very haunted zone" where there are MANY phantom clicks/drags on different areas of the dead zone in VERY QUICK SUCCESSION. When this happens I have found that constantly resetting the phone (maybe 5-6 times) until it returns to normal (see: dead zone) is the only way to fix it.
That whole situation can take up to an hour to sort out, especially since during the orgy of phantom clicks/drags on the dead zone, the touchscreen is essentially a write off and turning it off is next to impossible, meaning that my phone is bricked for a portion of the day. This happens arbitrarily about once every 5 days.
I purchased my phone from Australia one month ago. Was not aware of any problem until I had returned to where I am currently living in China. I'm absolutely gutted that my first android experience has soured, especially after shirking apple because of (living through years of) their own hardware/software issues.
Why can't I just have a quality, working piece of tech?
So far the warranty options available:
1) Store I bought it from says: Send it to LG Australia (1 non-international warranty)
2) Google says: No google store purchase number, no return
3) LG China? - Can't find any information about LG warranty claims in China.
If I send it back to Australia for repair I will be waiting without phone for weeks, AND I'll get taxed at least $100 by greedy China customs when the phone comes back in. (not to mention the postage there and back)
The problem has become worse and worse as have used the phone. Can any of ye android bros possibly offer any sort of advice or even better, a fix, for solving this problem?
tobiakazmer said:
I have the same problem, but its a band across upper 1/3 of the screen causing weird typing and such, but only in portrait.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have this right now. It's about a third of an inch located near the middle of the screen. It spans the entire width of the screen.
I sure hope it's just a software and not a hardware issue. I bought this in the US and I am now halfway around the world.
I had the same problem. For me it was right where the middle row of keys on the keyboard are or where the ring is on the lock screen.
5mm thick bar across the screen. I sent it back to be fixed and it's been fine ever since touch wood.
They replaced the entire screen on mine. This is definitely a hardware issue. I did a factory reset before I sent it back and the problem was still there.
Digitiser is too close to surface I think causing problems.
Sent from my Nexus 4 using xda app-developers app
Guys i have the same problem since this morning.
I tried everything change roms 4.3 / 4,4 and finally returned to stock.
Nothing worked although i had never the same problem before.
So i tried my last chance. Changed radio image with the help of a Toolkit of our forum ( thanks N-Cry Toolkit )
It seems to be fixed for now , i just rebooted.
Hope it will be ok and you could fix yours too
Hey!
denpeirazei said:
Guys i have the same problem since this morning.
I tried everything change roms 4.3 / 4,4 and finally returned to stock.
Nothing worked although i had never the same problem before.
So i tried my last chance. Changed radio image with the help of a Toolkit of our forum ( thanks N-Cry Toolkit )
It seems to be fixed for now , i just rebooted.
Hope it will be ok and you could fix yours too
Click to expand...
Click to collapse
This really worked for you?
em.faris said:
This really worked for you?
Click to expand...
Click to collapse
Well it worked. I cant understand the reason yet but it keeps showing after some time. I m trying changing roms / baseband / bootloader and return to stock trying to identify when it doesnt work and why. It's really annoying and i m tired of it.
denpeirazei said:
Well it worked. I cant understand the reason yet but it keeps showing after some time. I m trying changing roms / baseband / bootloader and return to stock trying to identify when it doesnt work and why. It's really annoying and i m tired of it.
Click to expand...
Click to collapse
well for me its a hardware issue, but since you said it worked fine when you changed the baseband it really surprised me up
actually happy, cuz there are many users who has this problem.
do keep us updated when you find your fix for this. will be of much help may be in future if something goes wrong on my N4
em.faris said:
well for me its a hardware issue, but since you said it worked fine when you changed the baseband it really surprised me up
actually happy, cuz there are many users who has this problem.
do keep us updated when you find your fix for this. will be of much help may be in future if something goes wrong on my N4
Click to expand...
Click to collapse
Had the same touch screen issue for months; had a dead spot in the middle of the screen that would interfere with browsing and games.
Updated OTA to stock KitKat just last week and the problem went away. Hope you guys get lucky as well. :cyclops:
Possible Deadzone fix!
capcanuck said:
Really weird.. Out of nowhere , the bottom right corner of my screen has become almost totally unresponsive to touch. The L and the backspace button on my keyboard are nearly unusable.. Anyone have any idea as to how I may be able to fix this? Its like there is a 2 inch by 1cm gap on my touch screen that doesn't respond to touch.. Thanks guys
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ok... i created an account here because ive had this same problem for the past month at least, but I think i found a fix. It may take a few people to try it as well to see if its definitive.
I have the same 1cm high deadzone spanning the width of my device just lower than halfway from the top.
My troubleshooting led me to this: If its hardware, its only because the software is telling it something it shouldnt be. I'm sure nothing is broken (i.e., from being dropped, etc.) Something is wrong, for sure, but not broken per se.
I took screen shots of temperature and voltage (using CPU-Z app) trying to figure it out. I paid attention to when it happened and when it did not. I boiled it down to two possibilities: temperature and/or voltage (i can explain how i came to this conclusion if you want... would take a bit more explanation).
I charge my phone with the charger plugged into the wall typically. I live in asia so the voltage is a lot higher (but within the appropriate range of the phone). Yet, lately when i go to sleep, I plug my phone into my laptop to charge, rather than the wall... when i wake up the problem isnt there. About 2 hours later or so the problem comes back.
I tried this for a week (charging my phone with my laptop) and the problem is dissipating. As quickly as it escalated (getting gradually worse) it is now getting gradually better.
Try it and see if it works for you. At night when your phone is nearly dead, charge your phone with your USB port attached to your laptop. Try this for a few days. Maybe it will help. Im still troubleshooting specifics to see if it is definitive.
UPDATE: today, the day of writing this, i haven't had the problem at all and it's been nearly 7 hours and the 3rd consecutive night of charging with USB on my laptop.
Nexus 4 - 4.4.2
My dead zone appeared post-Lollipop update
I created an account for the purpose of also reporting this "dead zone" issue.
I elected, on the Tuesday before Thanksgiving, to opt into the OTA Lollipop update. During the process of updating, I noticed my battery drained all the way to 0, while I thought nothing of it.
When the update was complete, I started to notice a dead zone in the middle of my screen when in portrait mode.
Actually, my dead zone spans an inch of my screen.
I have performed several hard resets, soft resets, learned about the ADK & adb, and downgraded all the way to 4.2.
I took the phone, this morning, to a cell repair shop and the technician said that it's not a hardware issue (although I'm not sure he's right).
So, that's my story. If I find a solution, I'll post it.
these dead spots IMO , are because of bad battery or bad charging ...
have any of you facing these issues have used any wall charger other than the default nexus 4 LG charger ?? maybe ur battery was not charged the way its suppose to be .. or maybe ur battery is getting bad.. can sm1 with the problem replace the battery and see if the problem get solved ???and u can try charging it from the original lg charger for 12hrs straight .. it may(temporary) fix the problem /...
Any new ideas for this post? Or is it dead.
Shubhamqweasd said:
these dead spots IMO , are because of bad battery or bad charging ...
have any of you facing these issues have used any wall charger other than the default nexus 4 LG charger ?? maybe ur battery was not charged the way its suppose to be .. or maybe ur battery is getting bad.. can sm1 with the problem replace the battery and see if the problem get solved ???and u can try charging it from the original lg charger for 12hrs straight .. it may(temporary) fix the problem /...
Click to expand...
Click to collapse
i could try the battery replacement on my nexus, when i get the time, ill get back to you if it works....
ok got the dreaded dead spot where the sim card is, i can't unlock my phone. i dont have usb debug enabled, i can push/pull files in recovery but not much more.
ive tried to change the dpi to move the pattern away from the dead zone by editing build.prop manually and pushing it to the phone but cm13 doesn't seem to take the change to build.prop so the dpi is stuck at 320.
now, im trying to set up usb otg and unlock my phone using a wired mouse and y-cable. but quanta doesn't have otg for marshmallow enabled out of the box and i dont have root access to enable it in an app.
is there a file that i can edit and push to the phone to enable otg_hack?
techparkour12 said:
i could try the battery replacement on my nexus, when i get the time, ill get back to you if it works....
Click to expand...
Click to collapse
Did you ever try this?
buffering.... said:
Did you ever try this?
Click to expand...
Click to collapse
i did it, battery has nothing to do with the screen, its better to just replace it.
I am running SACs23 4.3V4.2 rom. I have been having now issues. I plugged my phone in to charge for a couple of hours. Came back and the notification light was blinking for sms. I unplugged the phone and pushed the power button. The screen would not turn on. The notification light died out and now nothing. I have tried booting into recovery, hard reset, and pulling the battery. When I plug the phone back in with or without a battery there is no charging indication. The phone is lifeless. Not sure what to do, I have never seen this. When I plug it into the computer, nothing happens. I can not get into recovery or download mode...the phone does nothing. Any suggestions or ideas?:crying:
The micro USB charging port appears to be not working. You can buy it on Ebay for $10 and replace it yourself. Fairly straightforward.
stupid question but I have to ask, have you tried a different usb cable?
dewrust said:
stupid question but I have to ask, have you tried a different usb cable?
Click to expand...
Click to collapse
Yes. Charging port works fine. 2hrs later, I put the battery back in and it booted. Used my phone for the next 24hrs and then put it on charger. Woke up this morning and same thing. Very odd!
This happens to me when ever I don't use the original charger
Can you get into your recovery? Sacs, has an update to v4.3 in his op that's working very well if you can download it on PC and transfer to your sd card. Dirty flash it and see what happens. My guess is, you are having the same boot lag issues as most others were having and there is a zip file you can flash in Sac's OP for that also for v4.2.
If you can get into your recovery, dirty flash his update.
Your phone, charger port and wire are fine. It's the lag everyone was getting to get the screen to come up.
Sac's is doing one more update so it may be a few minutes before the link is up, but here is the direct link for you..
http://www.androidfilehost.com/?fid=23212708291682600
Until the update is reuploaded, for the heck of it, dirty flash v4.2 and DO NOT select any of the lockscreen effects like lightening or blue orb. The lag has been narrowed down to possibly being that problem.
Lag issue flash file to be flashed in recovery
https://www.dropbox.com/s/gy2d6ajg30utnjd/lag_fix.zip
Try pulling the battery and leaving out for say ten minutes or so
Some clarification:
1. I 've pulled the battery and waited from 10min to 3hours. No change.
2. Plugging into computer and the phone nor computer responds to eachother.
3. I am using the original Sammy charger.
4. This is the 2nd time this has happened but after 24hrs of being off it still will not respond to anything.
5. I took it to Sprint today and they ordered me a replacement phone. They had 3 of their best techs troubleshooting for 2hrs and couldn't find anything wrong with the phone, except for that it doesn't do anything.:crying:
6. I am hoping my new phone doesn't suffer the same fate. I can honestly say this is my 3rd Sammy phone and the 1st time I've had to take it back for anything and I am always flashing new roms from trusted devs.
This one has me puzzeled! Oh, this happened after I updated to MJA software and firmware but no KNOX! So, maybe I am having an issue with the new MJA....sounds like a lot of phones (various carriers) are. I'll update if I learn anything new.
cyiam39 said:
Some clarification:
1. I 've pulled the battery and waited from 10min to 3hours. No change.
2. Plugging into computer and the phone nor computer responds to eachother.
3. I am using the original Sammy charger.
4. This is the 2nd time this has happened but after 24hrs of being off it still will not respond to anything.
5. I took it to Sprint today and they ordered me a replacement phone. They had 3 of their best techs troubleshooting for 2hrs and couldn't find anything wrong with the phone, except for that it doesn't do anything.:crying:
6. I am hoping my new phone doesn't suffer the same fate. I can honestly say this is my 3rd Sammy phone and the 1st time I've had to take it back for anything and I am always flashing new roms from trusted devs.
This one has me puzzeled! Oh, this happened after I updated to MJA software and firmware but no KNOX! So, maybe I am having an issue with the new MJA....sounds like a lot of phones (various carriers) are. I'll update if I learn anything new.
Click to expand...
Click to collapse
Sprint just issued an update today that is suppose to fix this issue. If you can get back to stock take the OTA and see if it helps. You have the sleep of death issue and the mk2 OTA mentions sleep issues as the main fix. Hopefully this is what they are fixing.
Sent from my GT-N5110 using Tapatalk 4
Hey XDA, Really need some help here, i'll bullet point my problem for ease of reading:
- 1st Nexus 4 bought from google had wi-fi issues so got replacement
- 2nd replacement nexus 4 was good for about 2 weeks
- randomly screen touches weren't recognized by phone so reboot fixed that
- got worse and more frequent
- now my phone does not recognize screen touches at all
- phone is completely unusable, power volume buttons work though.
- need to ask XDA before another replacement ///
WHAT I'VE TRIED:
- i was on stock, so i tried to reflash stock to get rid of gravity stock and stock kernel
- rebooting phone 3950280359283 times.
- cleared caches.
- asked google play support, they're clueless.
- problem was here before i was unrooted, on complete stock 4.4.2
- also wondering whether its a software or hardware problem. i assume hardware however.
- i still have warranty
ANY IDEAS?!? thanks.
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Creepyficate said:
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Click to expand...
Click to collapse
My screen works now. However it will still come back every now and then and is fixed by a reboot. When i made this thread it did not work for a whole day, so my device will probably breakdown again. When I use TWRP it does not recognize touches. A good decider. So i guess it is hardware?
I think so, but wait for another reply confirming that.
I'd say it's a hardware issue. Definitely get it replaced again.
Kaleptik said:
I'd say it's a hardware issue. Definitely get it replaced again.
Click to expand...
Click to collapse
Lmao. You're definitely right. It's really annoying they sent me another device with a WORSE problem. Gonna ask google for some sort of compensation. I don't really have time to fiddle with devices re-rooting them transferring all my data again and so on. Too much work.
Good morning all,
my 6p looks completely dead. I've installed the latest Android O factory image from the Google Developer site, flashed it and was running withot issues until today.
I was about to write a comment on Facebook, and then the phone freezed. After seeing how the phone was not recoverying, I tried a hard reset by long-pressing the power and both the volume keys. Then, the phone got a black screen, didn't vibrate, and now looks totally dead.
It's not charging or responding in any way, no matter how I press it. I'm quite confident the phone was over 50% when this issue occurred.
I don't really know what coul've caused this, but on my side, the preview was flashed cleanly with a complete factory reset, and I've only restored media files, without rooting.
Any ideas as to what should I do?
Do you get anything showing up on a computer when you plug it in?
jmaclean62 said:
Do you get anything showing up on a computer when you plug it in?
Click to expand...
Click to collapse
Hi jmaclean, nothing, not even in Windows Device Manager...
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Zwitterion said:
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Click to expand...
Click to collapse
Yes a bad choice I would say - as an owner of a Nexus 6P device currently awaiting repair (thank god I'm in warranty) - I can tell you this device is plagued with issues that only become apparent as soon as your warranty is approaching expiry.
I love the phone, the design and build quality aesthetically speaking but would never be buying from Huawei again. The device is plagued with poor design that people believe leads to the CPU failing for some odd reason causing the dreaded bootloop issue.
My phone died literally in front of me and never worked again. I've contacted Huawei to get some clarification if this is an inherent fault as thousands are complaining about it and they just plain deny it and maintain if the warranty expires your out of luck. Apparently fixing the bootloop requires a motherboard change which in itself costs over $200 apparently. May as well get another phone for that as even the replacement component will eventually fail!
Sounds like a power issue. Maybe there's an open at the power switch or bad battery connector or battery. It most likely is nothing to do with Android oh it's just a coincidence. If you would have not even flashed Android O it would have still done this
seems like you will need to open up your nexus and unplug the battery, and then put everything together and try
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
paracha3 said:
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
Click to expand...
Click to collapse
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
murphyjasonc said:
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
Click to expand...
Click to collapse
Yes I was able to apply that and got it to work. Thanks
Hello, im desperate...
My sister took my Nexus 7 grouper and I think she installed some apps. My touchscreen isn't responding.
First of all I looked at the developer settings but there are no touches visible.
After that I restarted my tablet into the TWRP Recovery but there, the tablet doesn't recognize touches too.
So I thought it was a system problem.
I installed the official factory image from google with android 4.4.2 but I had no success.
After that I tried an other version. No success too.
Now I buyed a new screen with digitizer, plugged in but no changes too.
So because the new digitizer doesnt recognize anything I think it must be a software problem, but cause in TWRP touches won't be recognized too I think it is a HW problem.
Anyone have an idea?
Open it up and try reseating the connectors. If that doesn't fix it, then I don't think there's an economical way to fix it. Would also be helpful to get the dmesg logs to confirm if it's the same issue I had.
I had the same problem with my Nexus 7. I wasn't able to fix it, so I turned it into an altcoin miner. I like to think that it really wanted to work for my best friend Naomi Wu, who I'm sharing mining profits with.