Related
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....
LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.
Steamy window, LOL! sorry guys. anyway keep up the great work.
Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.
Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.
I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.
ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.
themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG
bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.
this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*
Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.
I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.
It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?
Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without
I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?
I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!
You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..
Hello to all, am going to ask if anybody of you have a problem in TPs Touch Capacitive Pad? I used this app
Nav Debug Tool by HTC
http://forum.xda-developers.com/showthread.php?p=2511016
To check out this multi touch stuff in my TP (though I know before that it has a multi touch feature, I just want to check if it's working properly) but it seems that the pad has a problem. The problem was sometimes, it can register my touch and most of the time, not.. sometimes it can register the multi touch, and most of the time, not .. even the nav wheel has a problem which doesn't register the rotation most of the time. Is this a common problem in TPs or even Diamond??
I even use the signed os WM6.1 but still has a problem.. so I wonder if any of you guys having the same..
thanks!
It's been happening to me for about a year already as well. Seems like it's just defective. It resets thought after sleeping the phone and waking it. I'm not sure if it was because I used to use Sensor scroll or it's a little scratched up.
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
R^7Z said:
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
Click to expand...
Click to collapse
that made sense but why would HTC permit a buggy front pad???
You know, it seems many phone brands/cooperations come under fire due to lack of something or another; maybe proof of concept? Perhaps the debug tool is to blame? Or even the sensor degradation over time? One can only speculate so far before it becomes a volatile thought... Again, I point out the idea being good, conceptually. So, I don't know where that exactly puts us as being end users? Then again, I've never really had a decent experience with phones, much less with newer phones; my thoughts and expectations may be slightly on the negative/lesser side of things because of this.
I have the same issue. I used to use GScroll to flip pages in e-books, but finally it got so buggy I had to dump it (other GScroll features were almost impossible to use). I've used NavPad DBug. What I do find is that running the compact heaps command of SK Tools will temporarily fix things, at least most of the time. When I have NavPad DBug running, if it's logging compact heaps will clear out the traces. Somehow or other, it cleans things out when the nav pad gets confused or overloaded with inputs. But even compact heaps doesn't work all the time.
It would be sweet if the capacitative area really worked, but unfortunately it appears to get worn out about the time that you figure out all the things you can do with it. Lol.
Edit: I wonder if the device has problems distinguishing a single touch of your finger vs. several touches. That could really screw up the function of the device.
Hello, I have an issue with the touchscreen of my nvidia shield tablet.
I bought the tablet only one week ago and I'm on the Stock lollipop version 5.0.1 (2.2), but I had the same issue with the KitKat version.
When I hold my finger on the screen and I change direction, the shield take a long time (about 1 second) before validate this change of direction.
This issue make all my games unplayable in touch mode. (If I use a controller, this problem doesn't exist)
I wanted to post a video to show the problem but I can't because I'm a new user. (I can pm the link if necesserary)
On this video I activated, in the developer mode, the trace of the movement to see that the lines moves very late after my finger. (I'm doing the same test with LG G Pad to compare and see that it respond perfectly)
In the Real Racing Game: I move my finger with very little fast movements and the wheels doesn't move at all.
I tried the calibration tool in lollipop but the problem persists.
I tried also a Custom Rom ([ROM][4.4.2][wx_na_do] AOSP for Nvidia Shield Tablet LTE US)
My questions:
- Does every Nvidia Tablet Shield have this problem or is it only mine?
- Is there a way to configure the pressure and move sensitivity (from the config file /system/usr/idc/touch.idc)
I would like to know if someone has the same issue to know if I have to send back my tablet in warranty.
Thanks in advance for your time.
I've had this issue, but only while charging. More noticeably while charging using 3rd party chargers, though the nvidia charger does have some "lag" as well.
phuzznut said:
I've had this issue, but only while charging. More noticeably while charging using 3rd party chargers, though the nvidia charger does have some "lag" as well.
Click to expand...
Click to collapse
Thanks you for your answer.
I have always this problem, I never tried when the tablet is charging.
In fact the touchscreen is relatively responsive when I touch and release quickly.
The problem is when I let the finger on the touchscreen and I change the direction slowly with small moves.
Hello,
I re-up this post because I really need your help.
I sent back my tablet to the seller for my touchscreen issue.
But they don't undertsand and tell that there is no problem with the touchscreen.
They compared to another Nvidia shield and told me that the response is the same than mine.
I can't believe that all the Nvidia shield has the same response because for me all the games are unplayable.
So I would like to know if someone has the same feeling (delay) about the touchscreen when you slide and change laterally the direction with your finger to play games like racing or platform games.
Thanks in advance
Sorry if I open this again.
I've been going crazy with this issue too and have been looking around for a fix, too.
I tried applying different configurations to my /system/usr/idc/touch.idc file, without any noticeable differences.
The only setting that works for sure is 'touch.size.calibration': the possible values are "none | geometric | diameter | area | default". Whatever I set besides 'none' will make the touchscreen work like a touch pad (you scroll around and there's a little cursor moving, you tap and it taps on the cursor's location).
I'm not sure which setting (if any) can calibrate the touchscreen for small movements. The documentation is a little unclear (I only found this: https://source.android.com/devices/input/touch-devices.html ).
Does anyone know more about this configuration file? I believe it's a common issue for all the shield tablets, it would be great if we were able to fix this.
Please note that root is required to edit that file, of course. Plus, the /system partition needs to be writable (mount -o rw,remount /system).
Same issue on new k1
Same issue on K1
I purchased an new K1 today and am experiencing the same issue. After enabling "show touches" in developer options it is very clear that the display periodically becomes unresponsive. I have also tried to re-calibrate the display with the Sensor Calibration Utility with no change. This happens while NOT connected to a power supply. So, I'm not sure what else to try.
What have others done about this issue? Do you return the device to the reseller? Because as it is, I can't play most games and find a typical browsing experience annoying.
Thanks in advance for any advice.
After trying everything, including full wipe, different Rom etc, I have returned it to the reseller. I got another one and and am very happy with it. Turning screen off and back on gets the responsiveness back for a while. Good luck with swapping it for new one, reseller I dealt with made no issue of it.As I have restored tablet to factory settings,I have just shown a video of a tablet going all crazy to a guy at the counter, and he gave me a new one.
Acidicus said:
After trying everything, including full wipe, different Rom etc, I have returned it to the reseller. I got another one and and am very happy with it. Turning screen off and back on gets the responsiveness back for a while. Good luck with swapping it for new one, reseller I dealt with made no issue of it.As I have restored tablet to factory settings,I have just shown a video of a tablet going all crazy to a guy at the counter, and he gave me a new one.
Click to expand...
Click to collapse
Thanks. I appreciate you sharing your experience on this. I got it from Amazon, so I hope they are cool with it.
Hello. I have an Nvidia Shield tablet k1 on lollipop 5.1.1. Everything is great about this tablet except the touch screen. It is really sensitive. Also, when I am scrolling, it "jumps" and goes faster than I actually scrolled. It scrolls faster than it should. I found this thread on xda. It helped a little with the being too sensitive issue, but scrolling is still really weird. This is my second device since the first one's micro sd card was defective. They both are like this. Is there anything I can do, or do I just have to deal with it?
http://forum.xda-developers.com/shield-tablet/general/adjust-touchscreen-sensitivity-t2963326
I was opening a thread with this exact same issue. I'm not on stock though (using the latest CM12 nightly), so I don't seem to have the 'Sensor Calibration' option.
Also the touchscreen seems to register a touch even when the finger is not touching the screen.
On the other hand, if I scroll a very small distance (like 0.5 centimetres) the list I'm scrolling doesn't move at all. This doesn't happen on other devices such as my Nexus 5 and Nexus 7 and is very annoying in some cases (some games, or moving the cursor for keyboard input).
I'll try to record a video of this behaviour.
What can we do to fix this?
Update: found a video (not mine) showing the issue I'm talking about: https://www.youtube.com/watch?v=08uPtusOJHQ
anyone else with this issue?
I also have this issue on/off sporadically on stock rom.
I'll be scrolling and itll jump back the opposite direction
Its like it looses track of the touch then catches it again.
It's irritating as my S5, Nexus 2012 have no problems scrolling smoothly.
I don't recall the original shield i tested in store to have this issue either.
Currently having amazon ship me a replacement to see if its just limited to the one I received. (QA issues)
Calibrating screen might fix the issues: go to About in settings and tap on model number until the calibration screen comes up. then hit calibrate. don't touch the screen then when it asks to reboot, reboot.
variance said:
Calibrating screen might fix the issues: go to About in settings and tap on model number until the calibration screen comes up. then hit calibrate. don't touch the screen then when it asks to reboot, reboot.
Click to expand...
Click to collapse
Did it fix the issue I posted the video about? I'm on Cyanogenmod now so I don't have the option to calibrate the screen, but I would consider going back to stock if it fixed this issue...
Calibration doesnt help at all , same issue at brand new k1. Nvidia says thats normal functionality lol
Yeah, very normal for a gaming tablet which would require precision...
Not trying to take up for this thing but I haven't had the first touch screen issue with it . so maybe not all is affected?? I've tried to replicate the issue but just can't everywhere I touch and slide is smooth
You mean it doesn't "jump" like the OP said? I don't seem to have that issue either.
I'm more concerned about the touchscreen's precision, as shown in the video.
Hi everyone, moto global
Not a surprise in such a short time after Moto G 2016 has been updated to MM 6.0 internet is flooded with complaints. I had my update in UK for around a week now.
I have manufactory reset device since then twice due to following reasons and which did not solve the problem :
I am literally fuming because new update took everything away that made this phone super phone.
1) Battery time got much worse, neither my habits changed nor apps I use. I would say by 30% .
Simple browsing and reading drains 40% just in one hour.
2) Other thing is display touch issues.No matter how gentle or harder I press my finger or use fro same purpose other thinkers display thinks I want to open link, photo, jump into other page. In general open something or anything that is possible on current page. That happens flickering finger up normal speed , slower ,or faster doesn't matter.
There is clearly an issue because I had none of it while phone was on Lollipop.
3) I also noticed phone is slower opening apps, getting in and out of app , inside browser loading time got longer.
4) Why on earth would Moto not allow to downgrade it to Lollipop? I don't care you have MM6 I want to get back to Lollipop until you sort out mess around buggy MM.
......
What problems do you have?
People, please, stop exercising your flashing, roming muscle and how cool you are at that. This thread is for identifying actual/present problem on MM based Moto G 2015 .
The issue with the behavior of the touch screen is what really gets to me. I scroll and let my finger of the screen and it registers that as a press and opens some link if my finger happens to be over one as I lift it off.
I have two decent ways of reproducing some of my issues with the screen (being able to reliably reproduce problems is paramount if you want to report problems).
1. Go to http://www.msnbc.com/videos . Scroll a bit down the page and then move your finger rapidly up and down. No issue. It follows your finger perfectly. Now start playing a video on the page and try again. At least to me, after a fairly short while it simply stops moving and no longer registers my touch. I can lift my finger and put it back down and now it moves again. There's no freaking way playing a video should have priority in the kernel over keeping track of my touches. I get it's not the fastest phone in the world and i would be fine with a lot of lagging. But don't just "forget" i have my finger on the screen. Something is very clearly wrong. Not exactly sure how this was in lollipop, but I'm noticing a lot of touch screen issues in marshmallow.
2. If I scroll to the top of my app drawer (by moving my finger down) and try to scroll even further (which obviously I can't) it often takes the place where I lift my finger as a press and opens that app. If anyone can confirm this kind of behavior it will.be eaiser to go to Motorola with this
I erased the stock rom and put CM12.1 ... Solved my problems!
LeJay said:
The issue with the behavior of the touch screen is what really gets to me. I scroll and let my finger of the screen and it registers that as a press and opens some link if my finger happens to be over one as I lift it off.
I have two decent ways of reproducing some of my issues with the screen (being able to reliably reproduce problems is paramount if you want to report problems).
1. Go to http://www.msnbc.com/videos . Scroll a bit down the page and then move your finger rapidly up and down. No issue. It follows your finger perfectly. Now start playing a video on the page and try again. At least to me, after a fairly short while it simply stops moving and no longer registers my touch. I can lift my finger and put it back down and now it moves again. There's no freaking way playing a video should have priority in the kernel over keeping track of my touches. I get it's not the fastest phone in the world and i would be fine with a lot of lagging. But don't just "forget" i have my finger on the screen. Something is very clearly wrong. Not exactly sure how this was in lollipop, but I'm noticing a lot of touch screen issues in marshmallow.
2. If I scroll to the top of my app drawer (by moving my finger down) and try to scroll even further (which obviously I can't) it often takes the place where I lift my finger as a press and opens that app. If anyone can confirm this kind of behavior it will.be eaiser to go to Motorola with this
Click to expand...
Click to collapse
1. I have this issue to though it takes me quite a few times to move my thumb up and down before it freezes.
2. " and try to scroll even further (which obviously I can't) it often takes the place where I lift my finger as a press and opens that app" that's exactly what I have on facebook, androidauthority etc. Instead of page gliding further it registers finger as for press. This issue is so obvious on my phone. I can reproduce it fairly easy.
nebulaoperator said:
Hi everyone, moto global
Not a surprise in such a short time after Moto G 2016 has been updated to MM 6.0 internet is flooded with complaints. I had my update in UK for around a week now.
I have manufactory reset device since then twice due to following reasons and which did not solve the problem :
I am literally fuming because new update took everything away that made this phone super phone.
1) Battery time got much worse, neither my habits changed nor apps I use. I would say by 30% .
Simple browsing and reading drains 40% just in one hour.
2) Other thing is display touch issues.No matter how gentle or harder I press my finger or use fro same purpose other thinkers display thinks I want to open link, photo, jump into other page. In general open something or anything that is possible on current page. That happens flickering finger up normal speed , slower ,or faster doesn't matter.
There is clearly an issue because I had none of it while phone was on Lollipop.
3) I also noticed phone is slower opening apps, getting in and out of app , inside browser loading time got longer.
4) Why on earth would Moto not allow to downgrade it to Lollipop? I don't care you have MM6 I want to get back to Lollipop until you sort out mess around buggy MM.
......
What problems do you have?
Click to expand...
Click to collapse
You can downgrade to Lollipop 5.1.1 from Marshmallow..
Upgraded my Moto G 2015 to MM and had same issues like yours so I decided to downgrade to Lollipop and battery life is awesome in Lollipop... 5+ hours Screen on Time.
amangurung07 said:
You can downgrade to Lollipop 5.1.1 from Marshmallow..
Click to expand...
Click to collapse
How ? I did try factory reset it brings me back to MM 6. My phone is not rooted.
nebulaoperator said:
How ? I did try factory reset it brings me back to MM 6. My phone is not rooted.
Click to expand...
Click to collapse
Once you upgraded to MM factory resetting will not downgrade...
You have to manually flash the firmwares files for Moto G 2015 Lollipop
I am also suffering from the touch issue
I tried downgrading but it fails to write the bootloader, etc. Some detailed instructions on how to do this using fastboot would be awesome...
Can you downgrade to 5.1.1 without an unlocked bootloader?
And since the ghost input issue seems to be a software issue, can't we just tweak it somehow?
I don't experience the same issues. I really like MM, but I don't think that is much better or different from LL. But I think I have better battery, better image and no touch issues. Performance doesn't appear much different.
I upgraded from OTA and have a XT1541. Did a factory reset after the upgrade.
This upgrade to android 6.0 on my Moto g 3rd gen is killing me
- Random bouts of slowness, if it had a hard drive with spindles I'm sure I would hear it ticking away constantly
- lag when typing into search bar etc
- lag when hitting home button
- the unintended link-clicking thing when simply browsing a webpage is infuriating especially considering how SLOW it is to bring up the link then go back because you don't bloody want it opened I. The first place. aGhHHHhG!!!! ajdfhaahbs#!&#@[email protected]
- I've started receiving low battery warnings on a daily basis when I have in general not considered battery EVER during the day with this phone
- apps have been crashing or constantly bringing up the dialogue box about not responding and wait/kill it
- Gmail notification is inconsistent - I'm not getting status bar notifications for all new email, can't find a pattern - does work sometimes
Basically what was a decent phone has now turned into a P.O.S
What is actually better about MM ?
I want to downgrade to Lollipop - considering I'm taking matters into my own hands is Lollipop the best option?
Whats the best way to safely flash the phone to proposed O/S? Link to approved method please and THANKS
nebulaoperator said:
How ? I did try factory reset it brings me back to MM 6. My phone is not rooted.
Click to expand...
Click to collapse
The factory reset should have resolved most your issues. Did it not help?
MrTooPhone said:
The factory reset should have resolved most your issues. Did it not help?
Click to expand...
Click to collapse
I did twice. Didn't work for me. Now I did hard reset. Just signed in with my google account and nothing else. Not even updating apps . Will give a couple of days and see what's happening.
I can confirm after few days of hard reset issues persist. Sending phone back.
amangurung07 said:
Once you upgraded to MM factory resetting will not downgrade...
You have to manually flash the firmwares files for Moto G 2015 Lollipop
Click to expand...
Click to collapse
Did you manually flash everything but the bootloader and gpt.bin file?
playenball said:
Did you manually flash everything but the bootloader and gpt.bin file?
Click to expand...
Click to collapse
Yes...
I have problems with touchscreen too. I've documented them here: https://youtu.be/_hMp9vb2WUI
Same here. Touchscreen is driving me crazy since i updated my xt1541 to stock MM.
Specially when i scroll up/down but the phone reacts as if i clicked. (factory reset and wiping cache didn't solve the issue).
i fixed the issue wirh touch screen by just removing the screen protector (glass)
vipervault said:
I have problems with touchscreen too. I've documented them here: https://youtu.be/_hMp9vb2WUI
Click to expand...
Click to collapse
I have exactly the same problem. I think is related to the size of finger. Also at mine moto g, with the app that you used in your video, using 2 inch i having the problem, using the indices no So, with smaller touched area the problem not appear
About the ghost touch, i have no idea what they have combined in motorola, but seems that the touch is "software" managed (like a 3d render made by the cpu instead of gpu), and it seems that with the cpu under stress the problem worsens, and problably this is why it does not always happen.
I made another test: if you enable developer option and you activate the cursor position option (i don't know if is the exact english name, i'm italian), with 3 touch have a huge lag, with 4 is impossible to draw cursor positions. About this test i don't know if is a problem of touch or is a problem of developers tools. Is necessary to check with another android 6 smartphone.
I also found another bug about the energy saving. Yesterday, when the battery has dropped below 15%, the energy saving has been activated automatically, as i set, but after connecting the charger it is not deactivated. I had to repeatedly juggle with the power saving enabling option to disable it (notification bar and buttons bar still remained red even with the power saving option turned off). Today I realized that the phone lags so obscene and discovered that, although it was not notified of the power saving mode, only 1 core was active with variable frequency. I had to again turn on and off the power saving mode to have all the core active (in cpu-z the governor was ever interactive but with only cpu0 active before re enable and disable power saving mode). Some happened this thing?
F...k, i was so glad I bought a motorola moto g i hope they solve these problems.