Related
I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??
dw77x said:
I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??
Click to expand...
Click to collapse
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?
jenisiz said:
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?
Click to expand...
Click to collapse
Stock charger and not happening on DL09. It does it really bad (2.2) whenever the charger is plugged in, I have heard this is a known issue. Perhaps somehow related to my problem?
do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...
M00NEY said:
do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...
Click to expand...
Click to collapse
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!
dw77x said:
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!
Click to expand...
Click to collapse
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.
this dosent help but i have the same problem at least we not alone
micdawg12 said:
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.
Click to expand...
Click to collapse
Yes, I forgot to mention it happening in certain spots, then eventually the whole screen.
It "seems" to me that the touch screen is prematurely shutting down with the back light still on. Although, sometimes this happens right after I unlock it. Grrr frustrating!
bubbleywine said:
this dosent help but i have the same problem at least we not alone
Click to expand...
Click to collapse
How bad have you had it? bad enough to flash back to eclair or have you been dealing with it? It drove me nuts, I went back. I sure would like to figure it out though!
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.
jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it?
Click to expand...
Click to collapse
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.
jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.
Click to expand...
Click to collapse
I have the issue on and off the charger, mostly off.. I don't think thats the case.
dw77x said:
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.
Click to expand...
Click to collapse
Yeah for me it ended up being the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. Then after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.
jenisiz said:
Yeah...it's as a result of the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. The after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.
Click to expand...
Click to collapse
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?
dw77x said:
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?
Click to expand...
Click to collapse
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.
jenisiz said:
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Click to expand...
Click to collapse
I guess when an oem Froyo comes out <sinkers quietly> I will odiin back to E101 and try and ota and see what happens.
jenisiz said:
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.
Click to expand...
Click to collapse
Not to bash Samsung but sheesh, if they are that fussy, I will probably not buy again.
my Samsung OMNIA 7 phone has got itself caught in a constant beep loop. This started automatically i tried everything and after that i found that this sound is of battery charging on/off sound which come when the phone is plugged for charging.
Now i have to keep the phone on vibrate mode and it does not go in lock mode ( display is always on )
After searching on internet i found that this problem is faced by three to four persons and the problem is related to battery port malfunction and hard reset will not solve the problem. no other information is available on internet
As i am in India and the phone is not launched and supported here cant give it to service center. Please if any one is having any solution,
it will be of great help
have you tried flashing it?
Sent from my OMNIA7 using XDA Windows Phone 7 App
few days back i have flashed Mango RTM is this problem is related with it?
please let me know if you have any solution
it is a hardware problem ... my phone does the exact same thing b/c i guess i must have been too rough with it ... part to replace it is:
3722-003065 IFC600 JACK-MINI USB
This worked for me (from answers.microsoft.com - how-do-i-stop-the-battery-icon-on-my-focus)
"Slightly move the pin inside the cellphone charging port away from the wall using a sharp item (I used board pin).....I think it is touching the wall and hence it keeps charging..."
bartathalon said:
it is a hardware problem ... my phone does the exact same thing b/c i guess i must have been too rough with it ... part to replace it is:
3722-003065 IFC600 JACK-MINI USB
Click to expand...
Click to collapse
where did you get the part, could you post the link please.
vamsitp said:
This worked for me (from answers.microsoft.com - how-do-i-stop-the-battery-icon-on-my-focus)
"Slightly move the pin inside the cellphone charging port away from the wall using a sharp item (I used board pin).....I think it is touching the wall and hence it keeps charging..."
Click to expand...
Click to collapse
This a hardware issue and this trick worked for me. Thanks Champ
Trick with the USB port bending only worked a few day's for me.
I have send my Omnia back to Samsung.
Send the Omnia 9 january and still waiting....
The USB port you can get here:
http://www.parts4repair.com/samsung-i8700-omnia-7-charging-port/
My omnia 7 has just developed this same fault today. It must mean this is some manufacturing defect since this is happening to a lot of people..
javedmiah said:
My omnia 7 has just developed this same fault today. It must mean this is some manufacturing defect since this is happening to a lot of people..
Click to expand...
Click to collapse
Same as the Bluetooth problem...
Maybe Samsung.de is investigating my Omnia. (my Omnia is there for 1 month now)
Bman said:
Same as the Bluetooth problem...
Maybe Samsung.de is investigating my Omnia. (my Omnia is there for 1 month now)
Click to expand...
Click to collapse
Oh, so the bluetooth That doesn't works without wifi enabled is a construction problem? Damn it! If I sent it to assistance they'll change it with a brand new?
Same happening here after one year of use....
It's quite annoying.
Besides the "moving pin from wall" is absolutely bogus for me, I actually disassembled and tryed pushing/pulling every part of the usb socket and everything remains the same. I can barely get it charged poking and proding it randomly. It charges for a couple minutes, then the looping returns.
I really can't figure WHAT pin users pushed into WHAT "wall" to make this supposed fix so easy...
Ok so maybe I spoke too soon. Yesterday I was telling my brother that the Note is the most reliable phone I've ever owned.....then....
I started having issues with charging. My Note would not charge, then it would change after several resets. It would charge, then stop, then start again etc etc....making a lot of beeping noises.
Now, it seems to be charging, but Voice talk keeps loading, and I've turned off the home key activation option. I also get the notification icon saying to disable car mode.
I really hope someone can help, thanks in advance.
kris
Great, now it's not charging, again!
Actually when I get the notification issue from Voice talk, the battery starts charging for a second until the notification disappears and stops charging....
Now factory reset my phone again and charging worked while restarting and restoring but when loaded the voice talk app keeps coming up and going off, so I have a black flashing screen constantly....gonna try restarting/reset without restoring...
Hi leicashot, this shouldn't happen. Which firmware version are you currently running? I recommend installing the latest LB1 stock, unless you have AT&T Note.
Some users have reported similar symptoms when there was dust in the mini usb port. Try cleaning the device, and if all else fails, you should send it back to Samsung for repair.
Bassarnis said:
Hi leicashot, this shouldn't happen. Which firmware version are you currently running? I recommend installing the latest LB1 stock, unless you have AT&T Note.
Some users have reported similar symptoms when there was dust in the mini usb port. Try cleaning the device, and if all else fails, you should send it back to Samsung for repair.
Click to expand...
Click to collapse
I'm using the latest 2.6.35.7. Any idea how to try clean the port? Definitely seems like something is wrong with the port....
No charging issues for me but my Note started doing the driving mode thing at about 3am today and has been doing it on and off all day!
Exceedingly annoying!
are you trying to charge from a PC or a wall outlet?
I usually charge via mains but it wasn't charging or even plugged in at the time this started happening. It was just sitting on the table by my bed. I even powered it off but it switched itself back on!
Here is how to fix it.
Take out the battery and take a plastic edge like credit card or even a regular tiny small screwdriver and push the pins (strip) inside the phone. I mean, to take the screw driver and push in the pins back inside the phone, in inside the usb charging port. your problem will disappear. make sure your plastic flexible after-market phone cover has a big enough hole at the bottom to allow you to connect a usb cable easily to the phone, or else, cut open a bigger hole on the cover.
Good luck
so here it is again: you have to push in the usb port pins back inside the phone, straight in without bending them. you can also buy a usb charging port from ebay for 22 bucks and change it yourself in 10 minutes. its a hardware problem so stop resetting your phone.
Nop bro i dont think so, cuz it happened same with me sometime after i bought galaxy note same thing happened with me too. I mean exactly same. So before i didnt knew rooting and flashin roms and all so i gave to service centre and they put newer version of ron in it and my problem was fixed after that.
Sent from my GT-N7000 using XDA
coolcrab said:
Nop bro i dont think so, cuz it happened same with me sometime after i bought galaxy note same thing happened with me too. I mean exactly same. So before i didnt knew rooting and flashin roms and all so i gave to service centre and they put newer version of ron in it and my problem was fixed after that.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Indeed. I remain convinced this is not hardware and is software related. The main reason for my thoughts there are that as well as the driving mode thing it seems that some piece of software is trying to load up as it asks me if I want to run whatever it is in either Clock or TuneIn Radio. Bizarre. Also, the first time it happened it was bang on 3am. Everytime I turned the phone off it would come back on exactly two minutes later.
The second night it started doing it bang on 1am.
I'm waiting to see what time it starts tonight.
It doesn't (so far) do it at all during the day.
Going to give it a couple of days to see what happens then go figure out how to go back to a factory ROM rather than the the Rocket 22 I have on here now.
Lakota said:
Indeed. I remain convinced this is not hardware and is software related. The main reason for my thoughts there are that as well as the driving mode thing it seems that some piece of software is trying to load up as it asks me if I want to run whatever it is in either Clock or TuneIn Radio. Bizarre. Also, the first time it happened it was bang on 3am. Everytime I turned the phone off it would come back on exactly two minutes later.
The second night it started doing it bang on 1am.
I'm waiting to see what time it starts tonight.
It doesn't (so far) do it at all during the day.
Going to give it a couple of days to see what happens then go figure out how to go back to a factory ROM rather than the the Rocket 22 I have on here now.
Click to expand...
Click to collapse
Same thing is happening to me. I tried pushing the USB pins in slightly. I'll let you guys know if it helped or not.
Sent from my GT-N7000 using xda premium
I've been having the same problem for a few days now.
I've just pushed the pins in with the corner of my charging cables connector and the problem stopped.
There was also a notification that flashed up saying something like: USB connector or device removed.
Voice talk is still managing to launch itself, even after pushing the pins in. I'm on stock LB2 so maybe I've finally found a reason to flash a GB rom?
Happened to me yesterday. Got a toothbrush and cleaned usb port on phone. Now seems ok
Sent from my GT-N7000 using xda premium
engineer
aftabbabar said:
Here is how to fix it.
Take out the battery and take a plastic edge like credit card or even a regular tiny small screwdriver and push the pins (strip) inside the phone. I mean, to take the screw driver and push in the pins back inside the phone, in inside the usb charging port. your problem will disappear. make sure your plastic flexible after-market phone cover has a big enough hole at the bottom to allow you to connect a usb cable easily to the phone, or else, cut open a bigger hole on the cover.
Good luck
so here it is again: you have to push in the usb port pins back inside the phone, straight in without bending them. you can also buy a usb charging port from ebay for 22 bucks and change it yourself in 10 minutes. its a hardware problem so stop resetting your phone.
Click to expand...
Click to collapse
this method solve my problem.
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.
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.