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..
I have an Asus TF700 android tablet running Jelly Bean 4.1.1.
When I play games, use apps or just use the tablet even in the play store, the screen will occasionally flicker (i.e. a small part of the screen in the game/app will slightly move and "flicker").
I'm using the "stretch to fill screen" setting. I tried the other setting to no avail.
I took the tablet to the lab and was told that this is a software related issue.
Any help/ideas would be appreciated.
Thank you in advance,
Gali.
Splashy2k said:
I have an Asus TF700 android tablet running Jelly Bean 4.1.1.
When I play games, use apps or just use the tablet even in the play store, the screen will occasionally flicker (i.e. a small part of the screen in the game/app will slightly move and "flicker").
I'm using the "stretch to fill screen" setting. I tried the other setting to no avail.
I took the tablet to the lab and was told that this is a software related issue.
Any help/ideas would be appreciated.
Thank you in advance,
Gali.
Click to expand...
Click to collapse
I have this when I'm reading PDFs in Repligo or Mantano -- doesn't matter in which program. Might be a driver issue. Haven't noticed it in the games we play on the 700, but then I do not game all that much and my 4-year-old son will probably totally miss out on the glitch.
I am not sure if this is related, but have you guys tried this: Setting -> ASUS customized Setting -> uncheck Enable smart backlight adjuster?
huy_lonewolf said:
I am not sure if this is related, but have you guys tried this: Setting -> ASUS customized Setting -> uncheck Enable smart backlight adjuster?
Click to expand...
Click to collapse
Hmmm
Haven't even thought about that.
Does this do away with the screen bugs?
Thats OK said:
Hmmm
Haven't even thought about that.
Does this do away with the screen bugs?
Click to expand...
Click to collapse
I don't know, I am just throwing out suggestions. On the tf700, there is this feature called "Smart dimmer", which acts like a second auto-brightness , changing the screen brightness based on the content of the page being display and causes the screen to flicker a lot. Can't hurt to give it a try.
Thanks for the suggestion but I already tried that before I took the tablet to the lab and it didn't help.
Well, anything automatic causes bugs. That's a given. So it could indeed be the light adjusters.
Also, are you running in performance or balanced mode whilst playing those games? Try changing it to the other, some games have problems with performance mode.
Another option is a factory reset.
ShadowLea said:
Well, anything automatic causes bugs. That's a given. So it could indeed be the light adjusters.
Also, are you running in performance or balanced mode whilst playing those games? Try changing it to the other, some games have problems with performance mode.
Another option is a factory reset.
Click to expand...
Click to collapse
Thanks for the suggestions. Right now it's running on balanced mode.
I did a factory reset and it's better than before but it still happens from time to time.
Hello. Try to enable "Settings"-"Developer options"-"Disable HW overlays".
kba7 said:
Hello. Try to enable "Settings"-"Developer options"-"Disable HW overlays".
Click to expand...
Click to collapse
With all due respect, no. I think that would do more harm than good. I'd rather have battery left. Reference, for example: http://rootzwiki.com/topic/28977-disable-hardware-overlays/ -- from which I will quote directly:
"Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping. Basically, using hardware overlays can reduce CPU usage by quite a bit, so I would leave it enabled."
and
"Disable it and the latency period for applications and the OS (any OS, not just Android) itself to render things will go way way up because it has to check to make sure it's not screwing with memory that is supposed to be dedicated to another task than its own. Hardware overlay ensures everyone has their own partition of memory so they don't have to do those checks and so latency to render things on the screen decreases dramatically."
From that, your suggestion doesn't seem like a good idea to me. But that's just me.
ShadowLea said:
Well, anything automatic causes bugs. That's a given. So it could indeed be the light adjusters.
Also, are you running in performance or balanced mode whilst playing those games? Try changing it to the other, some games have problems with performance mode.
Another option is a factory reset.
Click to expand...
Click to collapse
I've tried all your ideas before -- I have noticed it on every ROM I've tried so far, although it's the least noticeable on stock, and then CleanROM. It was prominent on BlackBean, but that was an early version (although I believe it remains one of the less mature ROM -- correct me if I'm wrong).
huy_lonewolf said:
I don't know, I am just throwing out suggestions. On the tf700, there is this feature called "Smart dimmer", which acts like a second auto-brightness , changing the screen brightness based on the content of the page being display and causes the screen to flicker a lot. Can't hurt to give it a try.
Click to expand...
Click to collapse
You're right in suggesting to disable it, and that's one of the first things I do when on a stock(-based) ROM. Therefore, unlikely to be the issue here.
Thanks for thinking along, everybody! Maybe it is just a driver thingy, or an API?
This is a well-known JellyBean-specific issue. So far, there is nothing that can be done to fix it (unless the latest OTA update addresses it)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
MartyHulskemper said:
With all due respect, no. I think that would do more harm than good.
..
From that, your suggestion doesn't seem like a good idea to me. But that's just me.
Click to expand...
Click to collapse
It is definitely fixed my problem with flickering in ScummVM (part of the screen was slightly moving). Can't see any negative effect till now. I think i'll stay with it as current solution.
Well here's my two cents to this: I've found that my screen mostly flickers when I'm playing music through my headphones in particular through Spotify. I've rechecked a couple of times and definitely noticed no flicker over a reasonable period while my tablet is silent and spotify is off.
Ive noticed when i dont use my tablet i dont get the flicker OR the black line at all!!!
/sarcasm
Yeah.... the things we put up with......
I thought I was the only one with flickering game problems but I see a few people have it too lol well that puts me at ease. But any fix for this?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
lovey08 said:
I thought I was the only one with flickering game problems but I see a few people have it too lol well that puts me at ease. But any fix for this?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
It's a nvidia driver issue so unless they update the graphics drivers it's unlikely you will see a fix. Some have it worse than others it would seem. I rarely see any lines or flashes. Make sure you turn smart dimmer off as well in the ASUS Customised settings.
sbdags said:
It's a nvidia driver issue so unless they update the graphics drivers it's unlikely you will see a fix. Some have it worse than others it would seem. I rarely see any lines or flashes. Make sure you turn smart dimmer off as well in the ASUS Customised settings.
Click to expand...
Click to collapse
Thanks will do!
Sent from my SPH-M930BST using xda app-developers app
lovey08 said:
I thought I was the only one with flickering game problems but I see a few people have it too lol well that puts me at ease. But any fix for this?
Click to expand...
Click to collapse
I mainly have problems when reading PDF:s using RepliGo Reader. Turning off forced GPU rendering helps a little.
Thwapped on my Asus TF700T with courage
I went ahaed and turned off the smart dimmer on the asus settings and noticed an increase of black lines and flickering all over apps, its not just when i play wild blood hmm strange ill try to turn it back on and see if it changes anything...
Sent From My Phone Using XDA-App
Asus Transformer Infinity TF700 User
lovey08 said:
I went ahead and turned off the smart dimmer on the Asus settings and noticed an increase of black lines and flickering all over apps, its not just when I play wild blood hmm strange. I'll try to turn it back on and see if it changes anything...
Click to expand...
Click to collapse
lovey,
Is "Force GPU rendering" selected down in: settings/Developer options/Force GPU rendering/ selected?
This might help some with any game that's compatible with the setting.
Hi,
so the title just says all about it. When using two fingers (or more) to scroll and zoom around (for instance Google Maps), it is very jumpy. It seems to be completely random. There are days where it doesn't happen at all.
I have turned on this feature where it shows you the trace of your finger movement on the screen: Normally you could just draw two lines, each one with one finger. But when this issue occurs one of the lines just disappear or the both disappear and start from scratch. So it looks like the system thinks that I put both fingers up briefly and starts a new trace.
I hope you get what I'm trying to say, not a native english speaker
Ah, more info: The tablet is on stock rom. I use one of those microfibre textiles to clean the screen <- that maybe the problem?
Thanks for any tips!
Am I really the only one with that issue? Any ideas would be VERY welcome as this problem is really annoying!
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.