Hi everyone!
I'm getting an extrange touchscreen behavior in my Nexus 4, eventually a part of the screen stop registering touches, but from one time to another it becomes active again, or, when I lock and unlock, it starts working perfectly. I'm rooted on android 4.2.2 fresh and new install. But in a full charge cicle, that ocurred maybe 5 times whith 4,3 hrs of screen. Can't reproduce that behavior, it occurs randomly (I think). Sorry for my english, I'm from Argentina.
Thanks for your help.
My advice to you would be to try a different kernel and maybe even a different ROM.
The Franco.Kernel has a couple of entries that claim better handling with the touchscreen.
overhauling said:
My advice to you would be to try a different kernel and maybe even a different ROM.
The Franco.Kernel has a couple of entries that claim better handling with the touchscreen.
Click to expand...
Click to collapse
Hi, I'd tried sotck kernel, Harsh and now on Faux kernel whithout any difference. I'll give franco kernel a try, and commet later. I'm thinking on a hardware problem, but how could it be possible if it's not all the time?
I just try franko kernel With no luck same extrange touch screen behaviour.
anyone who could helpme?
Anyone who could help me with any idea?
If changing the kernel and ROM didn't help the issue, the problem is most likely hardware. You can try a few other kernels or ROMs, but you will most likely need an RMA
In, thanks. The problem is that I'm from argentina and can't even contact Google for nexus 4. I have one person in the us but he needs the address to take the nexus and I can't give it. The RMA is just by Mail? Anyone knows?
Thanks!
Now, I'm using it with android 4.2, and its working fine. Immediately when the firmware was installed it doesn't work but now I'm using it for about half hour without any problem? Could it be any disabled built in disabled app? Or any other issue related to android 4.2.2?
Sent from my Nexus 4 using xda app-developers app
Update: not working fine. Just intermittent. Anyone who deal With RMA can tell me is there's a place where I can send the phone in, cause in muy country there's no Google support.
new update: After about 1 and 1/2 week turned off, I strated up to re-flash stock rom 4.2.2 (I was on stock but to be safe decide to re-flash again) and lock bootloader, and now it's working and not making any kind of error, how could it be possible? I'm expecting the error, to tell to my reseller, and it's not happenning. But, is there any way to know if it will happen again? if Google recieve a supposed non-defective device, will they return it?
Final update: My reseller sent back to US, and they told me Google will replace my defective Nexus 4 with a new one. Hope get it back soon, and never have to view any problem on my nexus 4. Thanks for the answers and help.
Conclusion (at least for me): If you have problems with touch-screen (not the sensitivity) and no custom kernel/rom solve it, that's a hardware problem.
Please close thread.
Related
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
Hi
I'm on my 2nd N4 after the first one developed a case fault. I had no problems with that one when using Minco or PA.
However this one seems to have a habbit of becoming completely unresponsive at least once every couple of days. The only way to bring it back on is to hold the power button in for a few seconds and then reboot it.
I will be putting it back to stock tonight and giving it more of a chance. But I thought i'd ask and see if anyone else has experienced this type of issue or knows if it's a sign of a more serious problem such as the red light of death.
Thanks
Phils7 said:
Hi
I'm on my 2nd N4 after the first one developed a case fault. I had no problems with that one when using Minco or PA.
However this one seems to have a habbit of becoming completely unresponsive at least once every couple of days. The only way to bring it back on is to hold the power button in for a few seconds and then reboot it.
I will be putting it back to stock tonight and giving it more of a chance. But I thought i'd ask and see if anyone else has experienced this type of issue or knows if it's a sign of a more serious problem such as the red light of death.
Thanks
Click to expand...
Click to collapse
I did actually experience this when I'm on stock 4.2.1 out of the box state, rooted and custom recovery.
transfered to PA for a couple of days and reflashed stock images from google site. after going back from PA to Stock I haven't experienced the lock up/screen unresponsive yet. hopefully it flashing back from PA to stock fixed this.
I've been using my phone for a month with rooted stock rom, custom kernel, unlocked bootloader, custom recovery, busybox and there's no single lag or lockups. Maybe you got a bad phone. I hope it can be fixed though.
I have a rooted stock ROM, unlocked bootloader, I don't have busybox permanently installed because I use apps that require a 'unrooted' phone but I have Stephen Stericson busybox installer at the ready.
I've not had a single lockup since I bought this phone.
So, just a little bit of background, I got my Nexus 7 on Christmas 2012. Recently, my Nexus 7 has been "shutting off" (I put it in quotes because it isn't really shutting off: the screen is just refusing to turn on) in the middle of the night. I've also noticed the whole screen freezing when controlling volume in certain conditions. Since I use my tablet for my alarm, having it off is doing me no good. Does anybody have any idea how to fix this? I thought it was a loose battery connector in the internals, but there was nothing loose.
I am running Google's official stock KRT16S with Oxydo kernel v14.
Thanks!
Sent from my Nexus 7 using Tapatalk 4
I suggest you go back to stock Rom with stock kernel and make sure the problem still exist.to solve a problem, first thing you have to do is find the cause of the problem, especially in here you have to find if it's software issue or hardware.So go back to complete stock conditions and check if the problem persist and if yes I would conclude it could be a hardware issue. It's hard to give more help without knowing more specific details like when did it started and if it's in that condition all the time ? Some pictures or screenshots will get you more help
go back to the stock kernel or try not to undervolt your kernel, you are having screen of death issue, device is not getting enough power.
also try a different kernel, not all kernels behave good on all devices.
Hi,
I didn't found any solution or working ROM/Kernel/Radio so maybe someone will point me to any direction except going back to 4.3
Like many users I have problems while listening music by my bluetooth headset. I have random disconnections while listening to audiobooks and calls. While listening to music it's usually random I can listen for 20-30 minutes nothing happens and sometimes it will disconnect after 5 and only reboot will fix the issue. Second problem is disconnect while calling. I have disconnections and reconnection's every 5 to 30 seconds. It's also random. Sometimes it works - usually it doesn't.
I'm using right now AOKP ROM but according to @aalvico post that problem exists also on Slim/PA/Purity and not on Omni and XeonHD.
Changing radio didn't solve issue. I tried AOKP/Franco/Hells Kernel. Same issue.
I started to experience this issue on KVT49L build.
So final question is - do any one knows 4.4/4.4.2 ROM that doesn't have this issue (meaning someone fixed it)?
I didn't had stock 4.4.2 yet, any one knows is the issue present there also?
This issue is so annoying that I would even go to stock to get rid of it.
Well, I'm using the nexus 5 port (KOT49H) with matrix 13.5 kernel and v4a and I never experienced problems like that, neither did I on previous builds.
Sent from my Nexus 4 using xda app-developers app
Oxious119 said:
Well, I'm using the nexus 5 port (KOT49H) with matrix 13.5 kernel and v4a and I never experienced problems like that, neither did I on previous builds.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks for reply. Could you give me more details what Rom you are using? I changed from AOKP 4.3 directly to 4.4.2 so I missed a lot nightly builds to catch this issue earlier. I don't really expect much of the rom except battery, I used AOKP ROM since second day I had my N4 so I don't really know how other roms/stock rom perform or what features I have in AOKP that I would not have in other (I needed ROM with quick pin unlock feature because of Exchange policy - now Xposed framework/mod did the job).
This issue is so annoying that I even considered selling N4 and buying something else.Then I thought first I need to try change the rom.
I have been terribly quiet for over 3 years and right now I can't even write in developer topics :/
Yes i had this some kind of similar bluetooth issue not with audio(actually didnt tried) but with bluetooth transfer from my pc to n4. the file got transfered successfully but my n4 hanged and restarted. Im using Purity rom with hellscore b45 stable kernel. This happened only once now the problem is solved on its own.
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Loopy Frog said:
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Click to expand...
Click to collapse
My N4 had a broken mic out of the box brand new lol. It was the latest batch, made in October 2013
I fixed it by getting a new mic because i diagnosed it wasn't a software issue
I ended up flashing "LRX08 B15.5S" from [L][5.0] Android L-pv N4 [B15.1 updated 10-27-2014] and I also put the "91u-a9: AOSP/L" Kernel from [KERNEL] [4.4.4/CM/(L)] [Bleeding Edge] Unleashed Kernel Series [91u-a9] [10/28/2014] Thinking there might be a chance it would fix my problem bringing it to 5.0 instead of 4.4.4.
I thought it worked all day yesterday without the data cable needing to be plugged in, I ran tests all day and it worked fine. Today is a different story though. I guess the data cable creates some form of initial connection the phone needs for my mic to work, and leaving it long enough it looses that connectivity. I'm not sure.
I don't have any intentions sending the phone in to get fixed, or repaired, as I'll be upgrading my nexus soon enough. I guess at this stage my fix is too cut the very end off of an old cable and have it in my pocket for incoming and outgoing calls. Anyone else have another solution?
Best Regards.
Loopy
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I believe that's what I did in the very very beginning of the problem, however on the possibly note that I didn't I'll do that just before Nov 3rd, if the official L is update is available then. Thanks ark
Yup...
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
flashed stock. Problem still persists.