Hey guys..
I've been using my Nexus 4 for more than a year now. Everything was working fine until a few hours ago when my phone stopped registering touches in the center area of the screen. I didn't drop my phone and I had it in my pocket the whole time! I'm freaking out as I have no idea what happened. Flashed a new rom and kernel, but the problem persists in the recovery too. What am i going to do???? :'(
What rom and kernel you currently use?
Iago-Cobain said:
What rom and kernel you currently use?
Click to expand...
Click to collapse
Purity rom with matr1x 12.5
Do you use dt2w? You might wanna read this.
http://forum.xda-developers.com/showthread.php?p=52216128
Sent from my Nexus 4 using xda app-developers app
Definitely sounds like a hardware issue. Are you still under warranty?
Sent from my Nexus 5
I don't use dt2w and I'm not under warranty!
Sent From The Realm Of HADES
get the display replaced then, seems like its not rom issue
@S.H.A.D.E
I suggest you revert to stock and give it to the service, else they can say you messed around and spoiled it..
Which Service Centre are you going to give to? The one at Shastri Road?
Hope you get it fixed soon!
Sent from my LG-E610 using Tapatalk
Related
Good day, what is the current status for your nexus s self rebooting issue ?
No reboots whatsoever
NSCollab 60 with latest Franco kernel, 110 liveOC with a little undervolting, Deep idle enabled.
None
Sent from my Nexus S 4G using Tapatalk
There is a reboot issue?
Sent from my Nexus S
DZG said:
Good day, what is the current status for your nexus s self rebooting issue ?
Click to expand...
Click to collapse
None... there is no issue. That said if you under volt too much...
Bounced off a tower to a forum near you!
Non existent.. ASOPs ICS running strong
Sent from my Nexus S 4G using xda premium
http://www.google.com/support/forum...4f&hl=en&fid=1b777a366748b64f0004b3418a290418
DZG said:
http://www.google.com/support/forum...4f&hl=en&fid=1b777a366748b64f0004b3418a290418
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1376013
Greetz
DZG said:
http://www.google.com/support/forum...4f&hl=en&fid=1b777a366748b64f0004b3418a290418
Click to expand...
Click to collapse
Sorry don't have them
Bounced off a tower to a forum near you!
Perhaps the problem is with ota build. Most here are rooted with custom rom. Are you by chance running a custom rom or the stock one that was sent over the air?
Sent from my Nexus S 4G using xda premium
Bruce lee roy said:
Perhaps the problem is with ota build. Most here are rooted with custom rom. Are you by chance running a custom rom or the stock one that was sent over the air?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
phone is default updated OTA
Then perhaps you can root and install a custom rom. It seems to me when I download a custom rom ota, its more likely to be corrupt. If its stock you want, it's available here. Better yet you might try Pete's Bugless Beast- stock with some additional enhancements. That way you get the stock a stock experience ... but better
Sent from my Nexus S 4G using xda premium
It was the other way round for me, I've only had the rebooting issue on my 9023 when I was using a couple of different cm roms, and it went away when I went back to stock. Have tried some other non cm roms, but not for long enough to show any effects.
No reboot, fortunately
That's an issue with 2.3.1, just update to 2.3.4 ota and it should be gone
Sent from my Nexus S using XDA App
scrapperstoo said:
It was the other way round for me, I've only had the rebooting issue on my 9023 when I was using a couple of different cm roms, and it went away when I went back to stock. Have tried some other non cm roms, but not for long enough to show any effects.
Click to expand...
Click to collapse
The CM reboots and sod are know bugs for CM and many have reported the problem stems from the flashing alternative kernel. I've been on GLADOS CFS @ 1.4 for several days now and have had absolutely no problems.
Sent from my Nexus S 4G using xda premium
I've never had any random reboots on my NS4G...nor have I even heard of this being an issue with the NS line, at all. I've been flashing new roms/kernels like crazy for the last 3 months I've been using this phone...the longets I think I've gone without a single flash is probably 4 days....and I've never had a single hardware issue of any kind These phones seem really rock-solid to me!!
They've turned a Samsung hater into a Samsung fan overnight!!! I'd buy a GN in a heartbeat if I hadn't JUST bought my NS4G lol
Hi all does anybody have the problem of putting the 300 on sleep and picking it up a little while later only to find its all the way off?
Sent from my XT907 using Tapatalk 2
i have had this a few times but not sure whats causing it so im gonna try a few things to see whats up, what setup do you have, im on CROMi-X with hunds kernel v10
Yeah, I get this if I don't flash a rom for a few weeks. In other words, cleaning out the cache can help.
CM10.1
Sent from my TF300T using xda app-developers app
robgee789 said:
i have had this a few times but not sure whats causing it so im gonna try a few things to see whats up, what setup do you have, im on CROMi-X with hunds kernel v10
Click to expand...
Click to collapse
Ihave the stock tom but its rooted
Sent from my XT907 using Tapatalk 2
im on warp now mate and ive not had a single random reboot or crash at all
Bad SD Card or corrupt files
applesaregoodforeating said:
Hi all does anybody have the problem of putting the 300 on sleep and picking it up a little while later only to find its all the way off?
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
I had this problem on my tf300t. I am running kitkat omnirom and cm11. I can run either.
The sleep of death was 100% caused by a faulty sd card. Not sure if it was file(s) or the card. Fixed the problem in both Omni and CM.
Backup your card to your computer.
Erase/Format it using the system you are on.
Verify that the SOD problem is gone.
That has happened several times to me too. Completely stock. Formatted about 3 weeks ago. Has not done it until just now. went to check it and it won't come on. Have to wait til I get home and put it on the charger. I just charged it last night. Maybe I didn't connect it right. Well update when I know for sure.
Sent from my SM-N900T using xda app-developers app
Well bad news for me. Tablet won't come on at all. No lights nothing. I don't know where to go from here. Anyone?
Sent from my SM-N900T using xda app-developers app
billwinkle said:
Well bad news for me. Tablet won't come on at all. No lights nothing. I don't know where to go from here. Anyone?
Click to expand...
Click to collapse
Did you try to hold the power button down for more than 10 secs, then release it? But time it, seems awfully long...
So far that always fixed it for me.
Sent from my TF300T using Tapatalk
I tried bit no luck. Talked to Asus set up rma. $92 to fix it. Sending out today.
Sent from my SM-N900T using xda app-developers app
billwinkle said:
I tried bit no luck. Talked to Asus set up rma. $92 to fix it. Sending out today.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Ouch. $92 that's abit expensive. Perhaps you should had consider to topup abit more to get a new Memo FHD 16GB. It is about $250 at amazon.
I just got an email from Asus. I wil not pay $200 to repair an out of warranty tablet, when I can buy the exact same model from Frys for the same amount. They said the motherboard needs to be replaced. It took them one full week and 3 phone calls to get this quote in the first place. They told me that it was diagnosed on Feb 14.
I seriously doubt I will buy anything from Asus again. I was told that it would cost $92 to fix it. I will not spend that kind of money on an item that could break the minute I get it back as they do not even warranty their own repairs. This tablet was nice while I had it, but it was not the greatest either.
Basically, my N7's screen is frequently unresponsive. I was trying to start something in my launcher, and tried pressing it at least 6 times, but nothing happened. Then I tried swiping between launcher pages, and that worked just fine the first time.
This just started happening on an almost constant basis within the last 30-60 minutes, and I was wondering if anyone else has experienced this, or heard of anyone else experiencing it. I'm running the latest Minimus with Jassy's latest kernel (I just flashed them this morning, but it was probably 4-5 hours ago at least), with the DPI set to 290 (I just raised it from 280 to see if that would help anything). I also cleared the cache and dalvik.
Any ideas?
My girlfriends tablet has done that too, then it just randomly goes back to just fine
Sent from my Nexus 7 using Tapatalk 4 Beta
Why don't you try stock and see if you have an issue. This would allow you to rule things out at least.
Sent from my Nexus 7 using xda app-developers app
Same issue here...both stock and CleanROM
me as well. And this is my second tablet after returning the first one for dead pixels
My tablet is stock rooted and I have just experienced this. I had to reboot in order to fix it. Hopefully this doesn't happen again.
Sent from my Nexus 7 using xda premium
lyall29 said:
My tablet is stock rooted and I have just experienced this. I had to reboot in order to fix it. Hopefully this doesn't happen again.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here this has happened to me on stock, but a reboot fixed it.
I've only experienced this using Chrome. it got so bad that I'm using the molasses-in-the-winter-going-up-hill Firefox browser just to be able to web surf.
Same here stock, and clean ROM.. Haven't noticed anything on kanged cm nor pa yet. Can't get otg to work worth a crap either I bought chainfires app to help with otg worked with stock based ROMs but not cm based ROMs .. I'm pissed I bought the 16 GB model..
Sent from my Nexus 7 using Tapatalk 4
dincdoes.me said:
Same here stock, and clean ROM.. Haven't noticed anything on kanged cm nor pa yet. Can't get otg to work worth a crap either I bought chainfires app to help with otg worked with stock based ROMs but not cm based ROMs .. I'm pissed I bought the 16 GB model..
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
It happened to me as well (complete stock). Mostly (if not all) instances were with Chrome. I don't remember it happening again since I switched to Chrome beta. (Fingers crossed).
I just took mine back to Best Buy and exchanged it for the 32gb model. The guy at the store asked if anything was wrong with the tablet and I told him that it would freeze up and I would have to reboot in order to fix it. He told me that all tablets and phones freeze like that and that I should reboot the device at least once a day to prevent the freezing of the screen. I thanked him and told him that I would do that. These salesmen must think that everyone is as dumb as they are.
I hope my new tablet doesn't have the same problem, because if it does I might give up on the new nexus 7.
Sent from my Nexus 7 using xda premium
Hi guys,
I recently bought a Google Nexus 4. Great device! But now I have a problem with the touch screen I guess.
I have some ghost touches on the screen. They are always on the same places.
To be more specific, on the same X-as of the screen. 3 to 5 touches in horizontal direction, swiping and touching the screen.
It's not always there, that's what's bothering me.. what is gods name could it be...
I'll add a screenshot of the touches when I get a chance to...
I have this problem for about a week now. And I was wondering if someone knows the solution to this.
ROM: Cyanogenmod 10.1.2
Cheers,
Alexander
When did this happen?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
When did this happen?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It happens every now and then. It started a week and a half ago or two weeks ago. Not exactly sure.
Alexandersch said:
It happens every now and then. It started a week and a half ago or two weeks ago. Not exactly sure.
Click to expand...
Click to collapse
This is start on the stock or custom rom?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
This is start on the stock or custom rom?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I have installed the custom rom the moment I got this device. It didn't happen before.. So I doubt it is a software problem. I'd rather think of it as a hardware problem, don't you think?
No-one?
If it started on custom Rom then flash back to stock to see if it still happens. If not then there you go.
If still happens even on stock then RMA the device.
Sent from my Nexus 4 using xda premium
mariosraptor said:
If it started on custom Rom then flash back to stock to see if it still happens. If not then there you go.
If still happens even on stock then RMA the device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I flashed another ROM CM10.2 UNOFFICIAL. Did a clean install.
Untill now it is reacting normal.. Let's wait and see.
I am thinking, could it be of some backup settings it is recovering from my google account?
Because it has no Gapps installed yet. Downloading at the moment.
Thanks in advance
As suggested, try stock.
Sent from my Nexus 4 using Tapatalk 4
naenee said:
As suggested, try stock.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Ok, The CM10.2 did not work. I disabled auto backup and recovery of Google settings and stuff and flashed the Stock ROM 4.2.2.
Also there was an official update to 4.3. And surprisingly enough, the device is responding normal again. Still though, i think it was very strange that the problem was also in the recovery...
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Even we are facing similar issue on Note 2. Tried few things but issue still persists.
Seemingly got something to do with some service.
So it's not device related then?
Sent from my Nexus 4 using Tapatalk
Was just using my phone and tookna call, even when screen was on it still took a long time to show who was calling!?!
Sent from my Nexus 4 using Tapatalk
Seems to be getting worse! I have to wait for about 5 seconds now, or maybe it already did.
Does no one have a fix?
Thinking about reverting to stock to see if that fix's it then maybe flash each thing one at a time and see when it breaks.
Sent from my Nexus 4 using Tapatalk
If you're playing around with kernel's and under clocking the CPU this can affect how quickly the phone wakes up. But my phone has a delay of a few seconds before I am am aware of a call coming in. Maybe it will be fixed in a future update.
Phone : Nexus 4 /Rom : cataclysm / Kernel : Stock.
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
foxguard said:
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
yohan7 said:
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
Click to expand...
Click to collapse
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
foxguard said:
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
Click to expand...
Click to collapse
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Deni_NS said:
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Click to expand...
Click to collapse
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
lopezk38 said:
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
Click to expand...
Click to collapse
And now your kernel is?
Deni_NS said:
And now your kernel is?
Click to expand...
Click to collapse
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
lopezk38 said:
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
Click to expand...
Click to collapse
I'll try then r203. Thanks
I installed a different ROM with stock kernsl and had same prob.
Did a complete wipe and unroofed the phone, took back to stock and all was ok.
Rerooted the phone, installed PA, all fine. Installed r203 and still all good
Sent from my Nexus 4 using Tapatalk
foxguard said:
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
If you have DU Battery Saver or any similar app which puts your device on low CPU usage upon locking, then uninstall it. It worked perfectly in my case.