Related
Is it me, or did froyo fix the "crazy screen" bug? I also noticed that my phone doesn't get as hot when it's been charging on my car dock.
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
lorin.bute said:
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
Click to expand...
Click to collapse
This, and I'm on FRF85B
Gotta be the best part of froyo for me, crazy screen bug fix, flash player, Jit compiler.
Which crazy thing happening are you guys screaming about? Are you talking about when the touchscreen would begin to register touches in the wrong place until the screen is turned off and on again?
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
RogerPodacter said:
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
Click to expand...
Click to collapse
Funny thing is that I had those issues on an AT&T-banded phone and they have gone way downhill since Froyo.
I find the granularity/preciseness of the screen better, and more responsive when, for example, you are dragging left-to-right and you start dragging up-down. However, I only do this in the browser so it could be down to better browser performance and/or JIT?
Still have screen uncalibration issues but seem to be better in 85 than 72
Does indeed seem to be a thing of the past, and on a similar note, it's improved the capacitive button accuracy as well.
Good that they've done it, but now I keep hitting them in the wrong place.
I'm using FRF91. Crazy screen bug happens with me twice a day. I don't know what I do to go away, but after a few minutes it stops by itself.
Ok I have been noticed a new problem for the past few days where the screen did not response at all when I turned on the phone. I cannot slide the unlock bar to unlock it. I had to turn it off and on again for one or two times to make the screen response again. Anyone else having this same problem?
Crazy screen occurrence definitely reduced.. however, it still happens when phone heats up significantly.. say, on a dash board while navigating. It's most definitely heat-related... so it must be hardware =(
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
vzontini said:
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
Click to expand...
Click to collapse
I've had the N1 since day one and never had this bug. But I don't use Skype...
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Same problem here! I don't need to take out battery, just reboot device
Any idea? Root? What ROM?
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
i have noticed the same thing too, but i am running Sheep Rom, it seems intermittent. what rom are you running?
coola71 said:
Hi everyone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
Click to expand...
Click to collapse
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
CyberGhos said:
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
Click to expand...
Click to collapse
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
ChodTheWacko said:
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
Click to expand...
Click to collapse
This. You shouldn't go Samsung or Android if you don't want to do some finetuning. If you want an out of the box solution take buy an iPhone. Then you can wait for Apple to release updates instead of being able to fix it yourself the same day.
i agree, its not even a hardware problem, its a software problem. i can accept small glitches as long as i can fix them, unfortunately you cant fix a hardware malfunction with software, unless of course the patch your applying is going directly over the antenna like a certain iGadget4
coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Hi
Even i am facing the same issue n need to know what is the sol. If it is a hardware issue should i get my phone replaced. I bought it only yesterday.
For me too it happens occassionally and requires restart of the phone.
Please help someone.
Just a guess - if all users r not facing it is it a hardware issue
I had this happen once after about 4weeks of using sgn. I don't know if i had made a call prior or what, just before it happened. A reboot made the problem go away for an hour or so. It came back.
I had installed an app a few hours earlier (dell store mobile app). I removed it - not really expecting to fix it. . . It didn't.
After some futzing, I rebooted into cwm recovery: flushed dalvic cache and fix permissions and rebooted. .. it has been working ever since.
This has happened only once, a few days ago. I'd wager it is a software issue.
Sent from my GT-N7000 using xda premium
Even I am also facing the same issue on Sheep ROM
Is this a ROM specific issue or Kernel ?
Same problem here !
I have been using the SGN for the past 4 days. I had this problem in the Stock ROM and it remains even after rooting the phone.
This phone/tablet seems to be a premature release with loads of small problems here and there. I guess they plan to remove these errors directly in ICS.
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
It happened with me too, 2-3 times. Few hours ago I was checking a pdf document and I received a call and the other party couldnt hear me well. While he was calling me again everything froze. Neither touch buttons nor the screen was working. I had to take the battery out, since I couldnt turn it off because of the unresponsive screen. This is really bugging me off.
I've had this occur to me twice, first time I was fidgeting with some app I can't even remember which, second time just a while ago (and that's why I went in here searching), right after making a call.
Using the S-Pen to swype-gesture back and menu they work though, it's just the buttons themselves that are dead.
Wouldn't think the proximity has anything to do with it (nice idea anyway) because then the whole screen should be unresponsive to touchm, wouldn't it?
BTW I am using xlite rom now, and maybe I could go for the cache wiping.
EDIT: I had cleared cache partition and dalvik cache this morning, ths afternoon the note has been sitting idle on the desk, 2mA drain according to battery monitor widget estimates, and without any calls the buttons stopped working again...
xinato91 said:
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
Click to expand...
Click to collapse
+1 I'm using Abyssnote kernel too - no problems with soft buttons yet.
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Reset and Root - CFKernel and AbyssNote worked for me
n0thingr3mains said:
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Click to expand...
Click to collapse
I had rooted and applied CF Kernel to my rom and had faced a few problems. But after wiping and applying CFRoot (latest) again I did not face any problems.
I have had no problems in the past 24 hours.
You can use the guide by Chainfire to root and apply CF Kernel (the best guide ever) and test for a day or two. then try moving to AbyssNote1.4 (I moved because I wanted to test OC)
Before you root and flash kernel, I will recommend factory resetting(since you are unrooted at the moment) and do not install any apps - because that is what actually worked for me.
UPDATE :
I havr started facing button issue on 1.4 AbyssNote as well.
Same problem here not woking :-( :-( :-(
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
How to fix this bug???
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
ephestione said:
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
Click to expand...
Click to collapse
I can confirm high battery drains with Abyss 1.4 (revert back to 1.2). But it is the only kernel which don´t suffer "touch buttons bug"
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
It might have been a bad flash. Try redownloading the rom and flash again. Also, make sure that you do not have too many apps installed. How much free space do you have on system?
The only apps that I had were the ones that came with the ROM itself, didn't download anything before or after flashing it.
may i know does this rom support audience cancelling noise?
thx
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
scrypt said:
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
Click to expand...
Click to collapse
ICS ones, but the Dev thread tells that & more.
I don't miss Nandroid when I'm backing up with Super Manager, Super Backup for data, apks, call logs and SMS.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
When my screen first appears after a reboot it does that, too, shows half the screen, then the other half, but only for a couple of seconds, I figured it's because it's still reading media, loading widgets, screen, etc. Doesn't last more than 2 seconds, fortunately.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
Were you still running the Glitch kernel that installs with the ROM?
It's odd that it went from working to not working. It sounds like something changed something which caused a conflict or corruption... it wouldn't have boot looped otherwise.
If not had any issues like this...
It was a fresh install of the ROM itself, was running for ~ 5 minutes. I didn't install anything via the Market or anything like that....
Un-invert Calendar?
I like Doc's V5 ROM a lot. Best I've used so far. However, I don't care for the inverted apps and am using the "Revert Inverted Apps to Stock" tweak mentioned here. It works just as expected except for the Calendar app - it remains inverted.
Can anyone else confirm so I'll know it's not just me?
Does anyone have a solution?
Thanks!
Bob
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Anyone have vibration issues when receiving texts?
battery life
Battery saving settings - LiveOC 126%, MaxCPU=800*1.26=1008MHz. Nexus KB3 Modem. No deep idle sleep, no screen state settings, no internal voltage settings, ARM voltages are OC/UV. Power saver in ROMSettings enabled.
Boraltis said:
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Click to expand...
Click to collapse
has any one experienced having a feedback loop in either your end or their end when using either the speaker phone or a headset?
Sent from my SGH-I897 using XDA
I am having an issue with the system time. It won't update automatically. Just gets stuck at a particular instance like 3:45 and won't update until I manually change the clock from 24 hours to 12 or vice versa. The happens after long sleep periods like two hours. After this the problem is persistent until I flash a new kernel.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
xThe Enforcer said:
Anyone have vibration issues when receiving texts?
Click to expand...
Click to collapse
Yes I am having this same problem no vibration with texts
no vibration with texts
Yeah. Same here. No separate vibration for SMS. But if you turn "Vibration only" system wide - it works for SMS.
Awkward.
scrypt said:
Yes I am having this same problem no vibration with texts
Click to expand...
Click to collapse
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Well anybody having an issue with time???please read my previous post^^ and tell me if it's sounds familiar , thanks
It happens when you switch a kernel as well? Try switching ROMs and see if it does it then go back to this, I haven't used this ROM since this incident ( OP ), using DK3 atm =p
b-eock said:
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Click to expand...
Click to collapse
I love you.
Sent from my SGH-I897 using xda premium
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
flashroyal said:
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
Click to expand...
Click to collapse
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
stefan2012 said:
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
Click to expand...
Click to collapse
Logs?
JoinTheRealms said:
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Click to expand...
Click to collapse
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
flashroyal said:
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
Click to expand...
Click to collapse
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
JoinTheRealms said:
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
Click to expand...
Click to collapse
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
flashroyal said:
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
Click to expand...
Click to collapse
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
JoinTheRealms said:
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
Click to expand...
Click to collapse
I don't know why, but every time I tried to record screen, phone just reboots. I tried with various apps, every time same thing. I cant find built in app in beanstalk 4.4. I'll try stock again but cant before tomorow. Thank you for your time
Use beanstalk with grouper blobs, and press vol up and power simultaneously to record
Sent from my LG-P880 using Tapatalk 4
My biggest issue with this phone is that every now and then my phone becomes very unresponsive in relation to the user input, up to a point where trying to type becomes frustrating. Actually, you can only notice this behavior while typing. Only rebooting or putting the CPU's governor into performance mode seems to help.
It happened to me for almost half a year on PixelExperience rom + HEX Kernel. Motivated by the thread's responses, I decided to switch to Havoc and even left its default Kernel, just to try a completely different software.
To my surprise, the behavior is exactly the same, every now and then that lag appears and makes typing in the keyboard very hard.
Any ideas? Is this happening to any of you? Is there a way to automatically change the governor when the keyboard is launched?
This happens to me too.. just typing on the keyboard, I didn't mind it as it maybe an app issue (referring to Messenger) but when I am playing this game (Mobile Legends) were most of the time it won't respond to when tapping the skills buttons.
That made me thinking if it is an issue with the phone. I'm just hoping its just an app problem. Mine is stock and just recently put in the Poco launcher.
I didn't realize it could also impact gaming,as I my self don't play. I was about to ask if you could try setting your cpu governor to performance and check the response but I see that you are in stock rom.
I will probably try another rom soon, and the latest hex kernel. However, having installed the latest havoc after more than have year different, and seeing the same issue, I suspect the problem is way bigger.
My phone has exactly the same problem. It is intermittent and really frustrating ....
That's the mistake. Is it worth sending to a manufacturer's service? :-S
I have the same problem, right now I'm on stock rom but also had this problem in miui (converted to 6x), I think is a hardware problem.
I would like to know if everyone is having this problem or not. I feel like it should be a hardware problem but at the same time the fact that it is intermittent could be an indication that there something behind it that we don't know, and maybe could be fixed by software.
I think hat putting it on performance doesn't fix it completely when it happens.
Yes I have the same problem, i thought it could be fixed by changing rom but seems like it wont be fixed by doing that.
---------- Post added at 06:01 PM ---------- Previous post was at 05:59 PM ----------
Interesting, reading on internet, it seems like it is an issue with the google keyboard and swipe to text feature, i have read that disabling it fixes the issue, will try to do so and report if something happens.
alexche77 said:
Yes I have the same problem, i thought it could be fixed by changing rom but seems like it wont be fixed by doing that.
---------- Post added at 06:01 PM ---------- Previous post was at 05:59 PM ----------
Interesting, reading on internet, it seems like it is an issue with the google keyboard and swipe to text feature, i have read that disabling it fixes the issue, will try to do so and report if something happens.
Click to expand...
Click to collapse
I don't use the google keyboard ever. I use swift key. Will try that anyway. But I see the lag also in the apps and launcher as well.
Well, issue is fixed, it was actually the gesture typing that was causing the issue.
Anyways, try disabling similar functionality on swift keyboard, or try using a lighter keyboard.
I recommend Google keyboard.
alexche77 said:
Well, issue is fixed, it was actually the gesture typing that was causing the issue.
Anyways, try disabling similar functionality on swift keyboard, or try using a lighter keyboard.
I recommend Google keyboard.
Click to expand...
Click to collapse
I don't think it is related to google keyboard as it also happens while playing games when keyboard is not shown, please continue to test with swipe typing disable and report back
I have same problem with Swiftkey keyboard so it is not google keyboard related, in games like trials frontier and asphalt 9 too
I am back, you are right, it is giving me problems, is not always, but it is there.
Hmm.
I would debug it if I knew how to recreate it, but unfortunately it is really hard to replicate because it happens randomly
---------- Post added at 09:17 AM ---------- Previous post was at 09:09 AM ----------
Reading around I found that playing with the gpu settings in developer options might solve the issue.
Will do and report if anything changes.
godlesplay said:
I have same problem with Swiftkey keyboard so it is not google keyboard related, in games like trials frontier and asphalt 9 too
Click to expand...
Click to collapse
I dont have the A2 but was experiencing the same issue on my Mi8. I resolved the issue ( the exact same issue that you guys are having ) by changing the kernel default setting to Schedutil, I had it set to to conservative.
This may or may not help you, but it's definitely worth checking. Also, this issue happened a couple of months ago on the Miui EU Developer rom, so it could be a bug with the OS as well.
Thanks for the advice but I'm fully stock so I can't change kernel governor
I have this issue too. Keyboard laggs when typing. Touchscreen not working. I rebooted many times but the problem still persists. Then i installed Touchscreen Repair from Playstore. It seems to fix the problem. I can't confirm how good the app is cause i've just install it 2hrs ago. You guys should give it a try. The name of the app is Touchscreen Repair. All the best!
Sent from my Mi A2 using Tapatalk Pro
sorry for ressurect an old topic, but i did some research and found some interesting stuff:
Aparently this is a problem that occurs commonly on white screen Xiaomi phones (mine is gold) because they use different hardware for the black and white versions.
After i read this some people posted that comparing their other Xiaomi phones like Redmi notes this problem also occurs and just on the white phones.
I still doesn't have a solution, it might be a shot to replace the screen for a black one but i couldn't find anybody who did this to know if it's going to work
uttashmori01 said:
I have this issue too. Keyboard laggs when typing. Touchscreen not working. I rebooted many times but the problem still persists. Then i installed Touchscreen Repair from Playstore. It seems to fix the problem. I can't confirm how good the app is cause i've just install it 2hrs ago. You guys should give it a try. The name of the app is Touchscreen Repair. All the best!
Click to expand...
Click to collapse
Yes, that app seems to fix the problem for me. Thanks!
Well just came here to update on the touch issue i had on almost every ROM (stock included)
Whenever the touch issue happens, nowadays i just hit the touchscreen hard using a single fingertip (like a hammer) and it starts working really, really good! I mean so good that even restarting the phone didn't fix it to this level haha ?
Earlier i just locked-unlocked the screen but this didn't always work. Restarting worked but its not really feasible always.
This solution is soo damn good in my phone right now that I can use this phone for a year from now if my screen doesn't break from the hammering ? earlier was thinking to exchange it with realme x2 pro real soon.
rahulmanpur said:
well just came here to update on the touch issue i had on almost every rom (stock included)
whenever the touch issue happens, nowadays i just hit the touchscreen hard using a single fingertip (like a hammer) and it starts working really, really good! I mean so good that even restarting the phone didn't fix it to this level haha
earlier i just locked-unlocked the screen but this didn't always work. Restarting worked but its not really feasible always.
This solution is soo damn good in my phone right now that i can use this phone for a year from now if my screen doesn't break from the hammering earlier was thinking to exchange it with realme x2 pro real soon.
Click to expand...
Click to collapse
what solution?