Touch screen problem on 4.2 roms? - One (M7) Q&A, Help & Troubleshooting

Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One

Hrodriguez77 said:
Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One
Click to expand...
Click to collapse
There is a firmware package from 2.17.401.1 RUU available here http://forum.xda-developers.com/showpost.php?p=39225672&postcount=2
This update includes updated touch screen drivers which should sort out your problem.
However in order to flash this package you need to s-off your device so you may wish to stay as you are and live with it.

rider5512 said:
There is a firmware package from 2.17.401.1 RUU available here http://forum.xda-developers.com/showpost.php?p=39225672&postcount=2
This update includes updated touch screen drivers which should sort out your problem.
However in order to flash this package you need to s-off your device so you may wish to stay as you are and live with it.
Click to expand...
Click to collapse
Sorry if I wasn't too specific, but I'm s-off and I'm also on the newest firmware. I don't think the firmware is the issue because I was exhibiting this problem when I flashed ARHD 10.0, and this was before I flashed the newest firmware...which makes me believe it must be with roms based on 4.2.2. Anyone else seeing this issue?

Which sibuti
It's something I can live with, definitely not something I would want to downgrade to 4.1.2 roms for. I just want to see if maybe this is related to 4.2.2 roms. Thanks for the advice, unfortunately since I'm on the latest firmware, I don't think that is the issue. Am I alone with this issue here?

Hrodriguez77 said:
It's something I can live with, definitely not something I would want to downgrade to 4.1.2 roms for. I just want to see if maybe this is related to 4.2.2 roms. Thanks for the advice, unfortunately since I'm on the latest firmware, I don't think that is the issue. Am I alone with this issue here?
Click to expand...
Click to collapse
I don't think that this is a 4.2.2 issue as most people, myself included, found the touch screen to be more responsive after flashing the latest firmware.

It definitely is more responsive besides this one problem. Did you try that test I suggested to see if it happens to you? Holding the home button while on the home screen then try tapping on something? I'd like to know if anyone else can repeat this.
Sent from my HTC One

Hrodriguez77 said:
Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One
Click to expand...
Click to collapse
It doesn't register the tap because it is waiting for you to press the home button again to bring up multitasking. I also get the tap issue in the situation which you described, however it doesn't affect me

Ok thanks for your help, I'll live with it
Sent from my HTC One

Hrodriguez77 said:
Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One
Click to expand...
Click to collapse
I've noticed this too completely stock odexed 2.17 with firmware.

Is it on the stock 4.1.2 rom?
Sent from my HTC One

I don't think it's the new firmware since I noticed it happening before I updated it.
Sent from my HTC One

Touch disable after ROM......
Hello friends .
I have a device 7 " A13 cortex A8 processor with a 1.2 model for touch screen GSL2682 chip , this chip is on the edge of the flat cable that goes to the screen , I opened the unit to be able to identify him because no ROM tested works TS on my device , I currently have a JB 4.2.2 ROM and only the wi - fi and camera function , G- sensor and TS no .
I tried this driver across the web and have not found the driver for the touch ... you have something to tell us about ?
Thanks again .
This is my lsmod now
C : \ android- sdk \ sdk \ platform -tools > adb devices
List of devices attached
200804118822c70 device
C : \ android- sdk \ sdk \ platform -tools > adb shell
root @ android :/ # lsmod
lsmod
8188eu 767 523 0 - Live 0x00000000
8192cu 666 125 0 - Live 0x00000000
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
ASIX 24601 0 - Live 0x00000000
sun5i_csi0 33355 0 - Live 0x00000000
gc0308 18608 1 - Live 0x00000000
61054 1 camera sun5i_csi0 , Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0 , Live 0x00000000
videobuf_core 20242 2 sun5i_csi0 , videobuf_dma_contig , Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 199911 69 - Live 0x00000000
ump 34161 17 mali , Live 0x00000000
nand 225000 8 - Live 0x00000000
root @ android :/ #

Related

Xperia X1 Problems

Hi,
I've had my X1 for about 4 months now and love the phone. Overall its been great but there have been a few annoying problems with it.
I was wondering if any of you guys out there have heard of the following problems on the X1 and know of any solutions:
1 - I installed HTC's Phone Keypad (Version 1.5 Build 32687) and it's great except that sometimes when press a key, it defaults to a letter - eg, if i press button 2, it defaults to the letter c instead of giving me a choice of a, b or c!
2. - Also when texting, the phone keeps randomly freezing for around 5-10 seconds which is really annoying.
Is there a newer version of the Keyboard i could try installing?
S
I look at it, I am Chinese, I do not know that you use the English-speaking countries use what is ROM. To be able to help you, then I will try my best to help you
Hi,
I've got the latest R3 Rom installed from the Sony Website.
Thanks.
n9805928 said:
Hi,
I've had my X1 for about 4 months now and love the phone. Overall its been great but there have been a few annoying problems with it.
I was wondering if any of you guys out there have heard of the following problems on the X1 and know of any solutions:
1 - I installed HTC's Phone Keypad (Version 1.5 Build 32687) and it's great except that sometimes when press a key, it defaults to a letter - eg, if i press button 2, it defaults to the letter c instead of giving me a choice of a, b or c!
2. - Also when texting, the phone keeps randomly freezing for around 5-10 seconds which is really annoying.
Is there a newer version of the Keyboard i could try installing?
S
Click to expand...
Click to collapse
1 - to me it's no surprise that HTC keyboard is NOT working properly on SE device.
Install something made generically for WindowsMobile. There's plenty of keyboards
2 - texting: on screen? basically X1 has this problem, especially when typed too fast on screen, but may be also caused by this keyboard or
word prediction (if you use any).
Thanks for that Doministry... have you any suggestions on the best keypad to use?
Tried the XT9? Check out the thumbs in the 1st post. http://forum.xda-developers.com/showthread.php?t=494026
Thanks for that, I'll have a look at the Thumbs app you suggested.
I have used the XT9 keyboard and it seemed to have similar issues to those described above.
n9805928 said:
Thanks for that, I'll have a look at the Thumbs app you suggested.
I have used the XT9 keyboard and it seemed to have similar issues to those described above.
Click to expand...
Click to collapse
I used Teksoft FingerTouch
http://forum.xda-developers.com/showthread.php?t=321074
Great one. But I don't use any of these.
WM one is the best feature-wise.
Could someone help me! My Sony X1 has a problem with calling! When I talking on the fone which automatically stop at 12- 14 seconds! Eventhough, I reset hardware, restore or change sim card.
i agree wiz u

Screen unresponsive

Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far

[Bug][ICS 4.10.405.1]Touchbug

Hi all
I recieved the Update to ICS on 2. July. I was very happy about it and it is really great. But I recognized 2 problems:
-Preformance is not the best
and
-the touch doesn't always recognize more than 1 finger.
What I did to fix:
I tried a hard reset and it fixed the performance, but not the touch.
When does the bug appear:
Often, but not always. Sometimes it works fine and then it doesn't work properly
When I play games, some games needs to tap at varius points on the touch. When I fast tap then the touch doesn't always recognize any fingers. With 1 finger, the touch works fine, with 2 fingers, it doesn't always work.
I attached a link to show how the touch doesn't always work.
https://dl.dropbox.com/u/4910238/IncSTouchbug.mp4
I started the thread to find other people who have the same problem. At the moment I'm writing with the htc support, and I hope that I find more people who has the same problem, so I can give him the link and they try to fix that annoying bug.
i hope I'm not the only one out there and we and HTC can find a fix.
best regards
MrToastbrot
MrToastbrot said:
Hi all
I recieved the Update to ICS on 2. July. I was very happy about it and it is really great. But I recognized 2 problems:
-Preformance is not the best
and
-the touch doesn't always recognize more than 1 finger....
Click to expand...
Click to collapse
Hi MrToastbrot. I have the same issue, after getting OTA 4.0.4 update, from HTC. I noticed the problem early, so I've been searching all over the web to find some solutions, but couldn't find any.
Please write a message, if HTC Support does give you some useful information about this problem.
Best regards
Luckyone.
My Incredible S acts similar, if it is touched by 4 fingers - then fingers on screen are detected "jumping", like in video. That continues even when only 1 finger is still on screen, but ends when nothing touches the screen.
I would post a link of google ''android issues'' page, but I can't because of ''Spam protection''.
The thing I wanted to say is, that this problem doesn't only concern HTC users, but it appers on, for example, Galaxy Nexus with different android versions too.
One guy wrote : ''I've heard people claim its something to do with the digitizer losing calibration when getting hot and that locking and unlocking the device recalibrates it.''
Still waiting for solution.
Edit : p.s. yeah - factory reset didn't help it.
Edit2: ....or it did? Right after factory reset, i tested the multitouch - it still wasn't working. After I downloaded some apps, I decided to test it again, just in case, and it seems to be working now. .
Edit3: It seems, that the theory about digitizer getting hot is true. A minute after I plugged my phone to charger the multitouch stopped working properly. Sad. Well, I guess we will have to wait some updates from HTC, or put our phones in a fridge or something.
Cheers!
ALMOST Solution found!
All we can blame is HTC Sense. You see - when you unlock the phone, the locker(sense locker) does something to make multitouch not working.
When you go to the ''Apps'' menu in ''Settings'' and Force Kill HTC Sense(the one with green HTC logo), touch screen starts working flawlessly again.
After you lock and unlock screen again - it won't be working.
The thing is - I'm a bit afraid to disable Sense permanently.
Let me know if this work for you guys.
Cheers.
Edit : Force Stop ''HTC Sense'' with launcher logo too. I'm really confused, because I can't understand what Stock Launcher has to do with multi-touch issues...
Nice, so we have only to wait until htc fix this bug. But one question:
Why does HTC Sense affect, that the touch isn't working correct in games?
Sent from my HTC Incredible S using xda app-developers app
MrToastbrot said:
Nice, so we have only to wait until htc fix this bug. But one question:
Why does HTC Sense affect, that the touch isn't working correct in games?
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Solution, I think, is to do HARD reset. Atleast it's working fine now in ''MultiTouch Visualizer 2''. Haven't tried in games.
:good:
Note: This will return your device to its original factory settings(all the data from internal storage will be removed).
- With the phone turned off, press and hold the Volume Down key;
- With the Volume key held down, press and release the Power key;
- Release the Volume down key;
- Press the Volume down key twice to highlight FACTORY RESET/CLEAR STORAGE;
- Press and release the Power key;
- Press the Volume up key to factory reset the handset;
The phone is restored to factory settings.
:good:
EDIT: GOSH, I'm sick of trying every freaking thing. Doesn't work with Hard reset!!!!
---------- Post added at 10:21 PM ---------- Previous post was at 09:47 PM ----------
The problem is inside HTC's kernel, so we can't really do anything about it.
And I think I will go for a custom kernel, because HTC will take it's time to fix this and realese update.
Cheers.
Luckyone199 said:
Solution, I think, is to do HARD reset. Atleast it's working fine now in ''MultiTouch Visualizer 2''. Haven't tried in games.
:good:
Click to expand...
Click to collapse
I tried a hard reset 1000 times and it doesn't work. I just think, the htc developers are noobs lvl infinity and the devs on xda are real pro's
We have to wait until htc releases the kernel source and the xda devs fix this bug
Sent from my HTC Incredible S using xda app-developers app
Any news? I'm getting pretty annoyed with this problem, because i can't write on Smart Keyboard Pro.
Yup. I'm facing this bug too. YOU'RE NOT ALONE.
Sent from my potato chips using xda boost
Any news on the touchbug yet?
I'm experiencing the same problem.
When I type fast (with two fingers) in Wahatsapp or SMS, the keyboard starts acting weird.
On a HTC Rhyme with ICS and Sense 3.6 (frow htcdev.com) everything runs smoothly. (same processor and resolution as htc incredible s).
So it's bug specific on HTC Incredible S ICS/Sense 3.6 software.
Has anyone received news yet or contact with htc about this? It's pretty annoying and I would think that HTC should issue a patch to resolve this.
hotdenio said:
I'm experiencing the same problem.
When I type fast (with two fingers) in Wahatsapp or SMS, the keyboard starts acting weird.
On a HTC Rhyme with ICS and Sense 3.6 (frow htcdev.com) everything runs smoothly. (same processor and resolution as htc incredible s).
So it's bug specific on HTC Incredible S ICS/Sense 3.6 software.
Has anyone received news yet or contact with htc about this? It's pretty annoying and I would think that HTC should issue a patch to resolve this.
Click to expand...
Click to collapse
With arhd, xs-kernel and v6 supercharger, i'm not facing the problem anymore.
MrToastbrot said:
With arhd, xs-kernel and v6 supercharger, i'm not facing the problem anymore.
Click to expand...
Click to collapse
I think so, or maybe it is less apparent
Sent from my Nexus 7
The problem is in kernel, so i guess if you put a custom kernel this bug will disappear.
Edit : nop, that didn't work for me.
Go for gingerbread, ics has to much issues for me, just like jb.
Sent from my HTC Incredible S using xda app-developers app
Silversniper said:
Go for gingerbread, ics has to much issues for me, just like jb.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
False. Just flashed Nik Project X v4.1 with HTC Sense 4.0.
Multi-touch bug is gone, even though they use stock kernel. I guess the problem was in HTC Sense 3.6.
P.s. ROM is working flawlessly. Best rom I've ever had. :laugh:
I'm also facing the multi touch prob using niks project x v4.0, with lost prophets Kernel
Cheers
Sent from my HTC Incredible S using xda app-developers app
I'm getting tired. And anything I could say now is - ''What the f**k?''
Multitouch was working on Nik Project X v4.1 fine until.. I don't know really.
And now, when I want to get it working again, I randomly change some settings or force close some apps(for example ''Media Link HD setup'') it starts working again, but, unfortunately - not forever.
Trying to find solution, but can't find any.
Begging for solution... :laugh:
Peace!
p.s. Multitouch is working in some apps. For example N.O.V.A 3, but not working in other apps, like Jet Car Stunts, Gangstar Rio: City of Saints, MultiTouch Visualizer 2 etc. Zooming in browsers and something like that works fine.
can't type "P" or "0" on keyboard. dead spot on touch screen.
I can't type the alphabet "P" or "0" on sense 3.6 Rom.
and on sesne 4 rom, can't type "0" ( P is working)
With show touches & pointer location from dev option, clearly about 1 cm of touch screen is not working. (no touch show beyond 1 cm of right margin.)
take a look at pic, pls.
Because of dead spot, I can't type alphabet "P" and "0" and can't play some game like https://play.google.com/store/apps/...DEsImNvbS5lY2FweWNzdy5vbmV0b3VjaGRyYXdpbmciXQ..
drcrazy91 said:
I can't type the alphabet "P" or "0" on sense 3.6 Rom.
and on sesne 4 rom, can't type "0" ( P is working)
With show touches & pointer location from dev option, clearly about 1 cm of touch screen is not working. (no touch show beyond 1 cm of right margin.)
take a look at pic, pls.
Because of dead spot, I can't type alphabet "P" and "0" and can't play some game like https://play.google.com/store/apps/...DEsImNvbS5lY2FweWNzdy5vbmV0b3VjaGRyYXdpbmciXQ..
Click to expand...
Click to collapse
Have you tried changing kernels?

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk

Flickering screen after 4.3 update

Hi! I have a problem with my Xperia SP. I updated it 2 times (i had to hard reset few times) to 4.3. I have a strange problem - my screen flickers about 1 flicker per second (or 2 sometimes). I tries disabeling HW, hard resetting etc. etc. Everything workes fine on 4.1.2. Is there any solution?
wojtek0018\ said:
Hi! I have a problem with my Xperia SP. I updated it 2 times (i had to hard reset few times) to 4.3. I have a strange problem - my screen flickers about 1 flicker per second (or 2 sometimes). I tries disabeling HW, hard resetting etc. etc. Everything workes fine on 4.1.2. Is there any solution?
Click to expand...
Click to collapse
I have the same issue. This bug is also present in CM11. Someone on this forum told me previously that it is caused by the auto-brightness, but turning it off does not fix the issue (the backlight still pulsates, but less noticeably so).
So far I've had this issue with stock 4.3, CM11 and Vanir. Would be great if someone found a fix for this. It is also unforgivable that Sony would release their 4.3 update without doing anything about this issue! I would have happily waited a bit longer for it to be released The pulsating backlight is the only reason why I'm not using CM11...
wojtek0018\ said:
Hi! I have a problem with my Xperia SP. I updated it 2 times (i had to hard reset few times) to 4.3. I have a strange problem - my screen flickers about 1 flicker per second (or 2 sometimes). I tries disabeling HW, hard resetting etc. etc. Everything workes fine on 4.1.2. Is there any solution?
Click to expand...
Click to collapse
Same problem for me. Flickering after updating... No solution yet..?
wojtek0018\ said:
Hi! I have a problem with my Xperia SP. I updated it 2 times (i had to hard reset few times) to 4.3. I have a strange problem - my screen flickers about 1 flicker per second (or 2 sometimes). I tries disabeling HW, hard resetting etc. etc. Everything workes fine on 4.1.2. Is there any solution?
Click to expand...
Click to collapse
same problem... :S i got my xperia sp yesterday and the first thing i did was root and update to 4.3 custom rom.. and i notice that flicker everywhere(games,ui,images).. it flickers even in cwm recovery and cause of that i thought it was hardware problem.. then i roll back to 4.1.2 and problem gone.. i think its something about gpu drivers
One solution...
follow steps....
1. Select any stock wallpaper
2. Hit home button for 5 - 8 times
3. then the prob solved...!!!!!
OR
1. select wallpaper using google + wallpaper tool ( its in wallpaper selection)
2. hit home button for 5 - 8 times
3. Prob solved ( but the resolution of wallpaper changed )
Hit one time thanks if I helped you.... :laugh::laugh::laugh:
Experiencing same issues on my XSP C5303 UK Unbranded w/ CE .266 4.3 C5303 firmware flashed, UBL, NO Root
Most visible with notification bar down (looking at wallpaper through transparent part) you'll notice wallpaper changing gradient almost :'(
Anyone know how to fix this?
ArunThazhathuveetil said:
One solution...
follow steps....
1. Select any stock wallpaper
2. Hit home button for 5 - 8 times
3. then the prob solved...!!!!!
OR
1. select wallpaper using google + wallpaper tool ( its in wallpaper selection)
2. hit home button for 5 - 8 times
3. Prob solved ( but the resolution of wallpaper changed )
Hit one time thanks if I helped you.... :laugh::laugh::laugh:
Click to expand...
Click to collapse
Really can this be the solution?? anyone tried it??.. i dont want to flash 4.3 if im not sure this will work.. i have same flickering in recovery mode (cwm).. but with 4.1.2 problem dissapear.. btw problem was on cyanogenmod fxp 308 on both 4.1.2 and 4.3 versions :S wtf??????
EDIT: didnt work (didnt expect to) ty anyway
anyone? :crying:
But it works for me....!!!!!
check with no animation selected.... may be it will work ( or put animation scale to .5x in developer option)
ArunThazhathuveetil said:
But it works for me....!!!!!
check with no animation selected.... may be it will work ( or put animation scale to .5x in developer option)
Click to expand...
Click to collapse
tried everything... its weird cause i have the same problem in cwm when i have 4.3 rom installed... not only on os
ParaSense. said:
tried everything... its weird cause i have the same problem in cwm when i have 4.3 rom installed... not only on os
Click to expand...
Click to collapse
Same problem in every recovery..
I installed 4.3 12.1.A.1.201 this morning and I experience this flickering too. It's exactly like in the following video:
Also it seems the screen isn't aligned that well, because there is a black bar of about 2 pixels at the top. I noticed this because I saw rounded corners at the top, but not at the bottom. I never noticed there being a 1 or 2 pixel border ont top in 4.1.2.
ArunThazhathuveetil said:
One solution...
follow steps....
1. Select any stock wallpaper
2. Hit home button for 5 - 8 times
3. then the prob solved...!!!!!
OR
1. select wallpaper using google + wallpaper tool ( its in wallpaper selection)
2. hit home button for 5 - 8 times
3. Prob solved ( but the resolution of wallpaper changed )
Hit one time thanks if I helped you.... :laugh::laugh::laugh:
Click to expand...
Click to collapse
The above method didn't work for me, however I could be doing it wrong as I am not very clear on what you mean by "select any stock wallpaper".
Rubecula said:
I installed 4.3 12.1.A.1.201 this morning and I experience this flickering too. It's exactly like in the following video:
Also it seems the screen isn't aligned that well, because there is a black bar of about 2 pixels at the top. I noticed this because I saw rounded corners at the top, but not at the bottom. I never noticed there being a 1 or 2 pixel border ont top in 4.1.2.
The above method didn't work for me, however I could be doing it wrong as I am not very clear on what you mean by "select any stock wallpaper".
Click to expand...
Click to collapse
Read this and complain here..
http://talk.sonymobile.com/t5/Xperia-SP/Bugfixes-on-12-1-A-1-201-and-flickering-that-still-exists/m-p/629113#U629113
maybe they will care if more ppl with this problem complain there..

Categories

Resources