Related
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.
Hi all,
I have recently been noticing ghost scrolls, where I would be slowly scrolling downwards, say, in the XDA app or reddit app, and randomly it would scroll quickly upwards when I lift my fingers. I was thinking this was a hardware issue so I got a replacement device on the way. However, I saw this https://www.reddit.com/r/GooglePixel/comments/7rczu2/scrolling_up_when_scrolling_down/.
Has anyone else been experiencing the same thing? I posted a vid and pic https://imgur.com/a/ny8fT. The second pic is touch input trace enabled in developer options, you can see there was a ghost long fast drag down to the bottom below the navbar.
Have been away from XDA for a while, please let me know if I am going against any rules about posting images hosted on other sites.
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Devhux said:
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
yep, thats happened to me a few times before as well. Not twitter specifically, but in reddit I would click on a post, and somehow I would end up on some random other post like 2 post below it, and if I hit back once, I get to the post I originally intended to click on instead of the subreddit list.
So there must be some sort of ghost touches/scrolls on finger release, causing the unintended post to be queued up just before the intended one.
I'm surprised there hasn't been more people bringing up this issue (assuming this is indeed a software 8.1 issue and not an isolated issue in the touch panel).
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Devhux said:
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
elliwigy said:
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
Click to expand...
Click to collapse
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
ethantarheels123 said:
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
Click to expand...
Click to collapse
prolly 8.1.. i got mine around december late nov. pretty sure its software related.. they had an issue with touch on the lockscreen right?
It seems like so many touch issues with 8.1 release. For this reason, I am still using 8.0.
https://productforums.google.com/forum/#!msg/phone-by-google/FfzV1578L8Q/1HcWw3CCAQAJ
https://issuetracker.google.com/issues/70344455
ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
ayoraider07 said:
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
Click to expand...
Click to collapse
Replacement device has the same issue, so this is definitely a software bug. Hopefully Google fixes it soon in the next patch update.
Nexus 6P here. I started getting these ghost touches with the last security update. 8.1 is the problem, not a solution.
My mom has the same issue of touch on places she doesn't touch, on Pixel XL.
Could it be the same?
Here is a video about it that I took, just by scrolling in the settings screen:
https://drive.google.com/file/d/1JCsTuMDvMNHh0CO7sF7yoLFT26uNIhUp/
It's a bit hard to reproduce, but it occurs eventually.
Has anyone tried to use Android P, and see if it helps?
Anyway, I've reported about this here too:
https://forum.xda-developers.com/pi...h-pixel-xl-t3807188/post76879468#post76879468
Any fixes yet?
I know this is old, but I wanted to know if anyone found a fix for this. I eventually found an Oreo 8.1 Rom that I like and this is the only issue that's bothering me.
Anyone here experiencing a sensitivity issue on samsung A70?
I had mine like few weeks ago and notice there is a lag on screen sensitivity. I used to play games (call of duty mobile and PUBG) on this phone and it is lag whenever i tried to make a minimum/fine tune movement. It is annoying and almost useless to play.
I believed to those who are using this phone for photo editing or painting or drawing will experience the same thing.
I compare with my samsung S9+ and note3, they works perfectly. No issue at all.
I also did a test with other demo set A70 phone in samsung store, they appears to have the same problem.
Not much info i can get from the net as for now.
I did report to samsung service center in Malaysia, unfortunately they said i'm the only one who is complaining about this matter. They ask me to check if there is a firmware update in future.
Please share your experience with me.
Please help.
Thanks
Same problem here, was looking all over the internet to find someone who experienced the same issue.
Just for the record, I have also switched on the 'Touch Sensitivity' option in the settings.
I've got this issue too. I've talked to Samsung about it through Samsung members app, and they told me to take the device to Samsung customer center, but they told me that there's nothing wrong with the device. I kept bugging them about it on Samsung members app until they told me that they're gonna pass the feedback to the team.
My advice would be that we all write them feedbacks about this issue, that way they'll listen to us. Also it's important to tell them that you don't have any screen protectors on, cause they're gonna put the blame on it.
I've also posted about this issue a couple of times here and there, on Samsung's Reddit and Twitter also. And I was trying to get some YouTubers attention to this issue so they can talk about it and get Samsung to listen, but YouTubers don't respond to me.
I am tired enough to contact samsung. I even did email their ceo through samsung email. No news from them yet.
Anyway, do you think it is a hardware problem or software problem? Or that is best performance a70 can do?
I am pretty sure this is a software issue. Because Snapdragon 675 should have no problem with this considering my sisters’s old Lenovo P2, with the Snapdragon 625, is perfectly fine.
Definitely software issue. The touch used to be worse but they fixed it, and now it's like this. Also, if it was a hardware issue they would've noticed it when I gave my phone to them to scan it.
I just came back from samsung service center. They told me it is like this due to screen type.. S9 and note3 having a better screen quality. So for A70 screen type there is a limitation of the delay.
I really dont agree with them but this is what they told me. I insist to have a report on this and ask them to highlight this issue to higher samsung representative. But i forgot to take the report number. Grrr...
Imo, this issue wouldnt solve unless you able to talk to someone who is 'working in a software department' and able to explain to them correctly.
And i guess they only take a very good care on their flagship model. S and Note.
Lowbk said:
I just came back from samsung service center. They told me it is like this due to screen type.. S9 and note3 having a better screen quality. So for A70 screen type there is a limitation of the delay.
I really dont agree with them but this is what they told me. I insist to have a report on this and ask them to highlight this issue to higher samsung representative. But i forgot to take the report number. Grrr...
Imo, this issue wouldnt solve unless you able to talk to someone who is 'working in a software department' and able to explain to them correctly.
And i guess they only take a very good care on their flagship model. S and Note.
Click to expand...
Click to collapse
What security patch you're on? And how can I test if I have the same issue?
Lowbk said:
I just came back from samsung service center. They told me it is like this due to screen type.. S9 and note3 having a better screen quality. So for A70 screen type there is a limitation of the delay.
I really dont agree with them but this is what they told me. I insist to have a report on this and ask them to highlight this issue to higher samsung representative. But i forgot to take the report number. Grrr...
Imo, this issue wouldnt solve unless you able to talk to someone who is 'working in a software department' and able to explain to them correctly.
And i guess they only take a very good care on their flagship model. S and Note.
Click to expand...
Click to collapse
That's not the case, they just don't wanna talk about it so that's their way of shutting you out.
I've just updated my phone to September security patch and I can see they're fixing the issue. It's not 100% fixed, but I feel like it's 99% fixed. The touch is better, but not the best. I compared it to my A50 and it's indeed closer than ever to being like it, regarding the touch response latency.
I'm gonna send them a message again to tell them that they're on the right path but it just needs a little bit more fixing. The sooner we report it, the sooner it is fixed.
+ No, most of their phones have great screens, I've been with Samsung for a decade now and I can tell from experience. It's just that this device has a software issue because they're so busy making new phones and giving updates to the A50.
Stanwar said:
What security patch you're on? And how can I test if I have the same issue?
Click to expand...
Click to collapse
It is 1 july 2019 security patch.
https://youtu.be/rTKHVaCJ8_Y
You able to tell the difference from the video.
SniperLolz said:
That's not the case, they just don't wanna talk about it so that's their way of shutting you out.
I've just updated my phone to September security patch and I can see they're fixing the issue. It's not 100% fixed, but I feel like it's 99% fixed. The touch is better, but not the best. I compared it to my A50 and it's indeed closer than ever to being like it, regarding the touch response latency.
I'm gonna send them a message again to tell them that they're on the right path but it just needs a little bit more fixing. The sooner we report it, the sooner it is fixed.
+ No, most of their phones have great screens, I've been with Samsung for a decade now and I can tell from experience. It's just that this device has a software issue because they're so busy making new phones and giving updates to the A50.
Click to expand...
Click to collapse
Where are you from? I am still with july security patch. No new updates yet.
I hope you are right about samsung.
Lowbk said:
Where are you from? I am still with july security patch. No new updates yet.
I hope you are right about samsung.
Click to expand...
Click to collapse
I updated the phone manually through Odin. I used the Israeli version since it's right next to Jordan where I live. The touch has improved, but it still needs some work. The fingerprint scanner has also been improved, it's faster now.
SniperLolz said:
I updated the phone manually through Odin. I used the Israeli version since it's right next to Jordan where I live. The touch has improved, but it still needs some work. The fingerprint scanner has also been improved, it's faster now.
Click to expand...
Click to collapse
Do you mean sept official update from Israeli samsung? If it is official, it must be available soon right?
Lowbk said:
Do you mean sept official update from Israeli samsung? If it is official, it must be available soon right?
Click to expand...
Click to collapse
I downloaded the update from Sammobile site, and yes it's the official one. It's up since 9/30.
SniperLolz said:
I downloaded the update from Sammobile site, and yes it's the official one. It's up since 9/30.
Click to expand...
Click to collapse
I got a call from samsung asking me to bring my phone to the nearest center, they gonna check and make a report for samsung hq to take action. Hope will works. :laugh:
Lowbk said:
I got a call from samsung asking me to bring my phone to the nearest center, they gonna check and make a report for samsung hq to take action. Hope will works. :laugh:
Click to expand...
Click to collapse
Tell them about this thread so they know it's a widespread issue.
Have you tried increasing the mouse pointer speed in the input settings? I bumped mine up a bit and it helped a little bit but it doesn't solve the problem of hitting a small target not being registered as a touch unless you zoom in. My old phone, LCD was able to hit small targets.
Sunspark said:
Have you tried increasing the mouse pointer speed in the input settings? I bumped mine up a bit and it helped a little bit but it doesn't solve the problem of hitting a small target not being registered as a touch unless you zoom in. My old phone, LCD was able to hit small targets.
Click to expand...
Click to collapse
Yes. I tried that too. But doesnt solve the problem.
SniperLolz said:
Tell them about this thread so they know it's a widespread issue.
Click to expand...
Click to collapse
Will do my best..
Lowbk said:
Anyone here experiencing a sensitivity issue on samsung A70?
I had mine like few weeks ago and notice there is a lag on screen sensitivity. I used to play games (call of duty mobile and PUBG) on this phone and it is lag whenever i tried to make a minimum/fine tune movement. It is annoying and almost useless to play.
I believed to those who are using this phone for photo editing or painting or drawing will experience the same thing.
I compare with my samsung S9+ and note3, they works perfectly. No issue at all.
I also did a test with other demo set A70 phone in samsung store, they appears to have the same problem.
Not much info i can get from the net as for now.
I did report to samsung service center in Malaysia, unfortunately they said i'm the only one who is complaining about this matter. They ask me to check if there is a firmware update in future.
Please share your experience with me.
Please help.
Thanks
Click to expand...
Click to collapse
same problem here bro???
Please vote, lets see how many user has this problem. (I know the Q/A topic contains similar topic but w/o voting)
My problem is similar. Yes when I pinch or zoom with two fingers it gets a little wonky but nit too terrible. My issue is with the setting "accidental touch" not working. My screen keeps turning on when in my pocket. Tired of companies putting out buggy defective JUNK!
As much I'd like to get this phone seeing so many people have this issue is stopping me from buying it. Guess I'll have to wait for samsung to address that they're putting out a fix for this.
After I put a tempered glass screen protector on it I've had no issues. They have pushed an update to the FE in Germany to address the issue but it's not pushed in the US yet.
teegale said:
After I put a tempered glass screen protector on it I've had no issues. They have pushed an update to the FE in Germany to address the issue but it's not pushed in the US yet.
Click to expand...
Click to collapse
I am glad you don't have the issue, because not everyone has it. Actually, I have put the latest DBT (Germany) latest firmware version on the phone a few hours after it was available, but unfortunately, it has NOT solved the issue, as I described it in this video.
carlosmeldano said:
I am glad you don't have the issue, because not everyone has it. Actually, I have put the latest DBT (Germany) latest firmware version on the phone a few hours after it was available, but unfortunately, it has NOT solved the issue, as I described it in this video.
Click to expand...
Click to collapse
Just tried that test. I guess I do have it but have never noticed it.
Unbelievable i also have issue with my Australian s20 fe, did not noticed this until I run the touch screen test. Unfortunately I have not received any updates firmware yet to see if Samsung fix them or not.
I had this issue too but with 1ATJ5 update which i received 2 days ago the problem solved
I'm surprised what take Samsung so long to release the updates to the rest of the world when its clear the problem happen to a lot of regions.
I have had too Multitouch issues. I have it returned. I have Pixel 5 now.
Was S20 Fe 5G red DE region.
I just bought US t-mobile model and I do have the crossing lines in that blue screen test app. However I haven't experienced any issues in my day-to-day use.
I have the Exynos version with november patch here in Brazil, the issue is present.
Fast catch in PoGo is a nightmare since we need to use 2 fingers to do it.
Exynos with latest patch, no issues on normal usage, only a few crossing lines on the test app.
Just ordered the FE 5G (Snapdragon).
Will update it and run some tests. Should be here in a week.
Hopefully they fixed it or will fix it with Android 11/OneUI 3.0
Is it really a software issue that can be fixed or Samsung just trying to cover it up?
Bl4cK_Pho3niX said:
Is it really a software issue that can be fixed or Samsung just trying to cover it up?
Click to expand...
Click to collapse
I saw some posts on reddit that claimed it was fixed with the latest software but I don't know how true that is as I haven't tried it myself yet.
Hopefully it's something that can be fixed via software. I've gone through PLENTY of Samsung devices and the hardware is always of good quality, even on their lower end devices.
I very recently got the Exynos version, CSC is SEB, ran touchscreen tests, no problems at all.
I don't know if it's touchscreen related or maybe screenprotector that i applied, but after using this phone for a bit more I notice that sometimes it doesn't register my touches. For example in pogo when I spin a ball suddenly it stops tracking as if i lifted my finger and yeets the ball somewhere to the side. Similar with HP:WU, sometimes it doesn't track my casts. :/
mxxcon said:
I don't know if it's touchscreen related or maybe screenprotector that i applied, but after using this phone for a bit more I notice that sometimes it doesn't register my touches. For example in pogo when I spin a ball suddenly it stops tracking as if i lifted my finger and yeets the ball somewhere to the side. Similar with HP:WU, sometimes it doesn't track my casts. :/
Click to expand...
Click to collapse
Did you you enable increased sensitivity?
My Note 10+ be a mess if I wasn't using that and accidental touch protection. If you're running Pie you can also download the app Double Tap which works great with almost zero battery usage.
The case also makes a big difference as naked I hate this phone; in the Bolt case it's great and it helps to prevent accidental screen touches while making it easy to hold.
Don't be too hasty to ditch Pie for Q... Pie is a fast, stable and a relatively secure OS.
With Q comes the cursed scoped storage.
Make sure to cure isn't worse than the disease.
blackhawk said:
Did you you enable increased sensitivity?
My Note 10+ be a mess if I wasn't using that and accidental touch protection.
Click to expand...
Click to collapse
Yes, I tried both in all combinations.
blackhawk said:
If you're running Pie you can also download the app Double Tap which works great with almost zero battery usage.
The case also makes a big difference as naked I hate this phone; in the Bolt case it's great and it helps to prevent accidental screen touches while making it easy to hold.
Don't be too hasty to ditch Pie for Q... Pie is a fast, stable and a relatively secure OS.
With Q comes the cursed scoped storage.
Make sure to cure isn't worse than the disease.
Click to expand...
Click to collapse
This phone never shipped with Android 9 so irrelevant.
And the problem is not accidental touches. The problem is it stops tracking.
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
UPDATE:
I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Was it à regular updates from Honor ?
TotallydubbedHD said:
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
Click to expand...
Click to collapse
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
marcox92 said:
Was it à regular updates from Honor ?
Click to expand...
Click to collapse
Yes it's a regular and official update.
Curious, didn't receive the update
nico97470 said:
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
Click to expand...
Click to collapse
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
marcox92 said:
Curious, didn't receive the update
Click to expand...
Click to collapse
You should tape in the three points upper in right in the app Honor Club( system update). Trying versions.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
nico97470 said:
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
Click to expand...
Click to collapse
Agreed.
Doing a reset will solve it, I have not done it and it works fine, I have been lucky.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
wolfaas12345 said:
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
Click to expand...
Click to collapse
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Ja5ka said:
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Click to expand...
Click to collapse
Sorry to hear that but glad I could help!
TotallydubbedHD said:
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Click to expand...
Click to collapse
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
wolfaas12345 said:
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
Click to expand...
Click to collapse
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
No its garbage logic in fact yes its been in dev for 13 years it has also been adding features for 13 years changin things for 13 years for same 13 years its also been supporting over 20k+ devices and working on them bugs are about normal with majority phones we dont see a lot cuz devs squash them before they push the update but variables that i mentioned prevent devs from covering all scenarios so shenanigans happen my problem was not with bug itself my problem is people like you talking crap because they refuse to wipe or expect flawless experience every time nothing is perfect especially software
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
I think you are an expert. Do you think it is possible to install Google Services Framework on Magic5pro? I have one but dunno how to do so. Thank you for your sharing.