okay i have this weird problem in my Miro. manytimes when i get a call and the phone rings, the touch suddenly stops working. the power buttons work fine but the touch just does not work. then either i have to pull the battery or touch responds automatically if i try later. i have faced this problem a few times earlier also(all on variants of stock based roms and pure stock) but ignored.
another thing that when the service reply messages comes say like when you turn off data, then i notice a small lag(including partial touchscreen disability). is this a bug in Miro stock rom maybe?
presently i am on vengeance reloaded with 5.8 firmware. anyone else faced such problem ever? any suggestions?
Related
Hi there,
someone has problems that the touchscreen is not responding?
Have CM11 - current nightly, Fournace kernel 1.0.2 and OPO lockscreen flashed ....,Only the lower right corner is responsive to inputs.
I had the problems also 2 times with the CM11S-ROM.
Has anyone else this problem?
Sun_Dancer said:
Hi there,
someone has problems that the touchscreen is not responding?
Have CM11 - current nightly, Fournace kernel 1.0.2 and OPO lockscreen flashed ....,Only the lower right corner is responsive to inputs.
I had the problems also 2 times with the CM11S-ROM.
Has anyone else this problem?
Click to expand...
Click to collapse
I have the same problem. It's intermittent and goes away after a while but it comes back often enough to make my device unusable when needed. I literally can't answer calls or log into my device because of this. Is no one else having this problem? The issue persists into recovery so it might be hardware.
Franco r13 has new touch drivers implemented. Try it.
OP you say it as if your screen is never responsive, only in the bottom of the screen. That sounds like a RMA.
I will look into Franco r13 tonight. In the meantime, here is how my problem happens:
- Most of the time touch screen is working as expected
- Sometimes the touch screen becomes unresponsive to many areas on the screen, but some small areas still work
- When the above issue occurs, it is only temporary. If I let the phone sit for a few minutes it usually comes back.
- Restarting does not fix the problem, and the problem persists into recovery mode (I forget which recovery I have, but it has touch screen input)
- The problem started with phone being 100% stock, although only after the OTA update a few days ago
notten said:
I will look into Franco r13 tonight. In the meantime, here is how my problem happens:
- Most of the time touch screen is working as expected
- Sometimes the touch screen becomes unresponsive to many areas on the screen, but some small areas still work
- When the above issue occurs, it is only temporary. If I let the phone sit for a few minutes it usually comes back.
- Restarting does not fix the problem, and the problem persists into recovery mode (I forget which recovery I have, but it has touch screen input)
- The problem started with phone being 100% stock, although only after the OTA update a few days ago
Click to expand...
Click to collapse
Yeah, try Franco then. Mine feels better now. It wasn't too responsive before either.
My GF's M2 Aqua has a bug with the accelerometer. If she makes a longish phone call the accelerometer stops working (i.e. no auto-rotate) without a reboot. Looks like I'm not the only one:
https://talk.sonymobile.com/t5/Xperia-M2-M2-dual-M2-Aqua/accelerometer-bug/td-p/918650/page/16
Anyone else facing this?
Apparently Sony are finally looking into it and hopefully will issue a fix in another firmware release.
Usually I'd just flash a custom ROM but there doesn't seem to be any reliable builds with a fully working camera...
I confirm that this happens to me too, I just hate it because it worked if I had NFC activated in the update before 18.3.1.c.1.13.
temporary solution
it seems that the proximity sensor has something to do with it.
somehow after a long call it stucks and blocks even the accelerometer and the compass sensors.
it happens even to me and you have to restart your device to work again, but if you talk using the headset or if you press the power button while you are talking at the phone you can avoid the bug.
for me is working all the time and i can wait patiently until the official fix
Looking at the other thread I posted, one of the users said a new firmware update has been pushed with the same version number. Let's hope it fixes it...
Accelelometer bug tread
maxray said:
it seems that the proximity sensor has something to do with it.
somehow after a long call it stucks and blocks even the accelerometer and the compass sensors.
it happens even to me and you have to restart your device to work again, but if you talk using the headset or if you press the power button while you are talking at the phone you can avoid the bug.
for me is working all the time and i can wait patiently until the official fix
Click to expand...
Click to collapse
Thanks for the tip, but :confused for how long should i press the power button...just one click or during the conversation?
Just enough to wake up the screen, can't say as my M2 has it as never had a problem of on my own one
D2303 stock 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality
I think it only affects the Aqua (2403) model. Anyway, I installed a kernel for the standard M2 model following the instructuions here: http://forum.xda-developers.com/xpe...a-2403-root-philz-touch-t3072833/post60152564 and it seems to have fixed the issue.
Apparently Sony are about to issue another software update, but I'll hold off on that until I know the status of this bug...
I have the latest update 1.15 and it seems that it doesn't have the bug anymore. I am quite happy now with phone. Hope it works for everybody
Every few hours the touch barely responding, it takes me like 4 minutes just to reboot the phone, and rebooting is the only way to make the touch work again.
I tried to replace the the rom to cm12 nightly, change the kernel and modem. I even flash to stock cm11s and wipe every thing! And it still not fixed. Please help me!
edit:
https://www.youtube.com/watch?v=S6drgJb6OFg
this is no me but it is exactly what happened to me
Same problem here! Don't know if its related, but I just went on a ski vacation, so maybe the cold has something to do with it? Cause that's when the problem started.
The touch problem is very irritating when I try to unlock my phone, cause I can't draw the unlock pattern. Also scrolling trough photos or apps doesn't work cause it doesn't recognise scrolling, but does pressing instead.
I hope this is a software problem!
I use stock ROM cm 11. Did nothing else with it, I have my oneplus only 3 weeks now.
Hi Guys.
Greetings from Ireland. I have an Xperia Z3 D6603. Its running stock Andriod L 5.0.2 with Apex launcher instead of Xperia home. Its a great phone and besides some small issues I love it. The main issue however is that it randomly stops vibrating which can be quite irritating. It started acting up about a month ago and I presumed it must have been an app causing the phone to misbehave, however when I boot the phone into safe mode the same occurs. Usually from boot up it will work for about 10 key presses, for eg the home button pressed multiple times and then it stops working. Then after a few minutes it will kick back in. This is most noticeable when typing and is annoying. Its like the motor gets tired and cuts out if that's even possible? Anyone else had a similar issue? I searched but couldn't find any applicable information.
Thanks in advance,Barry
Bxperiaz3 said:
Hi Guys.
Greetings from Ireland. I have an Xperia Z3 D6603. Its running stock Andriod L 5.0.2 with Apex launcher instead of Xperia home. Its a great phone and besides some small issues I love it. The main issue however is that it randomly stops vibrating which can be quite irritating. It started acting up about a month ago and I presumed it must have been an app causing the phone to misbehave, however when I boot the phone into safe mode the same occurs. Usually from boot up it will work for about 10 key presses, for eg the home button pressed multiple times and then it stops working. Then after a few minutes it will kick back in. This is most noticeable when typing and is annoying. Its like the motor gets tired and cuts out if that's even possible? Anyone else had a similar issue? I searched but couldn't find any applicable information.
Thanks in advance,Barry
Click to expand...
Click to collapse
...
the lag could be from the launcher and its eating the cpu and thus when typing its slow to respond to the touches, have you tried it with the stock launcher?
Richy99 said:
the lag could be from the launcher and its eating the cpu and thus when typing its slow to respond to the touches, have you tried it with the stock launcher?
Click to expand...
Click to collapse
Hi Richy. Yeah I booted into safe mode and the same occurs. I thought it was the launcher or a third party app but in safe mode if I repeatedly tap the home key for 10 times the vibration disappears. Really has me confused, I don't see how it could be hardware when the motor actually does work when it wants to?
Bxperiaz3 said:
Hi Guys.
Greetings from Ireland. I have an Xperia Z3 D6603. Its running stock Andriod L 5.0.2 with Apex launcher instead of Xperia home. Its a great phone and besides some small issues I love it. The main issue however is that it randomly stops vibrating which can be quite irritating. It started acting up about a month ago and I presumed it must have been an app causing the phone to misbehave, however when I boot the phone into safe mode the same occurs. Usually from boot up it will work for about 10 key presses, for eg the home button pressed multiple times and then it stops working. Then after a few minutes it will kick back in. This is most noticeable when typing and is annoying. Its like the motor gets tired and cuts out if that's even possible? Anyone else had a similar issue? I searched but couldn't find any applicable information.
Thanks in advance,Barry
Click to expand...
Click to collapse
I have EXACTLY the same problem. It is super irritating and I have the feeling too that it's a software problem. Maybe something that the previous software update is causing. It even just happened when I typed this. Maybe someone has a clue?
I have tried every single ROM on this Forum for Moto G 2015 Osprey 1GB version. However I am having same issue on evry ROM . Often I recieve a call my screen goes blank and I am not able to answer the call . Also when dialling out my screen goes blank after pressing dial . As a result I am not able to put teh call to loud speaker or use any other in call options . Can some please help me how to fix the issue . (I know work around to use Power Button to end calls and Volume to answer calls however that doe snot suite me as I ended up answering few calls which i did not wanted while mobiel in my pocket ).
Things I have done so far
I have tried this with both a screen protectoron and now have taken screen protector off . Issue still there
I have a a backup of orignal Motoroal ROM and this issue does not happen on orignal ROM
I have installed Nano gapps to make sure I have unough RAM free issue still there
I have tried most of the ROM 7.1.1 and even 6.0.1 all ROMS including Cynogen mod+ Lineage 13 and 14, ressurection remix, AOPS . Experience, Slim, AOKP, Cosmic , AOSP extended and list goes on and on but issue is still; there
Is there any specific reason for this issue ?
Is this to do with RAM, Sensor or custom ROMS issue ?
Is teher any way to turn teh sensor off which turn screen off whiel in a call and when i take mobile near my face (I am thinking if sensor incorrectly so wanst to check if turning thsi off makes any difference )
Can anyone please help
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
acejavelin said:
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
Click to expand...
Click to collapse
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
chungomungo1 said:
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
Click to expand...
Click to collapse
Just take the newest one there... Best you can do.
As far as testing the proximity sensor, make some calls and have someone call you... You can try a sensor tester app like https://play.google.com/store/apps/details?id=com.mtorres.phonetester too
Brilliant , Thanks alot . will try that
FACING EXACTLY SAME PROBLEM ON XT1550
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
abhishekturumella said:
FACING EXACTLY SAME PROBLEM ON XT1550
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
There is only one fix. find where is proximity sensor, usually it is on the top near front camera . when ever screen goes blank dry your thumb and clean screen with teh thumb where proximity sensor and screen will wake up .
Also you need to keep you pockets extra clean. It is better if you can hoover inside them as most of the time I noticed there was a little dirt always on my screen when screen went blank. I am noit sure if my mobiel screen has gone very catchy to dirt after 1 year use
I intially though iut was due to custom ROMS and I have gone back to stock ROM and recieved two motorola security updated still issue is there so this is not because of the ROM .
Try this
Goto settings and search default from the search button then select phone app and set the default app.
Just saw this and thought I'd try Phone Tester. covered or uncovered, my proximity det always said Far. I tested phone by making a call and then covering it and the screen immediately went black. I would suggest that some screen protectors might interfere a bit but you've already taken that into account. Note where it is (on my xt1540 top just right of ear speaker) and make sure surface is clean. Otherwise just may be defective.
EDIT: if you feel it's "defective" You might consider replacing the screen/digitizer in hopes that that would fix it and it's not a motherboard issue.
Facing same issue
My stock rom on moto G3 2015 was working fine. Yesterday i rooted and installed tesla when this issue started. Frustrated i tried ASOP Extended and here too same issue.
It's not the issue of the sensor since Stock rom was fine till 2 days ago.
Have tried Phone notificaion settings as well.
Any updates on this or else i may have to reinstall Stock ROM