Hi guys.
I've been noticing a strange message that occurs some times, after unlocking my GNex (4.2.2) and quickly enter Whatsapp. The screen background goes dark green, with the app logo in the middle and, at the bottom, the word "jogos" (games in Portuguese). This screen somehow remembers me the installation screen. Then, after half a second, the screen changes back to normal known chat screens.
I read that Whatsapp is moving towards gaming. Maybe this is a preloaded code to quickly permit the future launching of the inside gaming platform, as a glitch.
I'm trying hard to get a screenshot, but the screen doesn't appear very often.
Any thoughts??
Sent from my Galaxy Nexus using Tapatalk
What's the exact build number of the app?
Anyone having the same issue and have found a solution?
Phone suddenly stuck at some instances even with non-extensive usage.
Yesterday I was only using Facebook app. When messenger bubble pop up, my phone suddenly spiked. Moved once and then it got stuck already. You'll notice that it's not Facebook app only that's not functioning since nav. buttons are also stuck. You can't go press home and clear recent apps/hibernate apps. Power and volume buttons are also not functional.
So I assume the main system crashed. I only did a long press on power button to restart.
I installed Franco kernel r73, and thought that issue would only occur with stock kernel.
However, it occurred again today, I was viewing photos in Stock Photos app. I haven't started viewing the first 10 images yet, so memory should not be consuming that much. I turned on the auto rotate to view the image larger. When I turned the phone landscape, it reacted like it's about to rotate. And suddenly it got stuck. This time, power button is functional. It turns the screen on and off but it still turns to the same stuck screen, not the lock screen.
I've been experiencing this since 5.0.1. and almost everyday since I updated to 5.1.
I'm not sure if this is a hardware issue on my unit since mine is already about 1 year and a half old. I don't want to buy another phone yet!
Or is this a common issue nowadays due to Lollipop upgrade. If so, then could you provide temporary fix before they update this on 5.1.1.
Thanks a lot!
I had something similar . When I put forward the curtain hangs notice and then everything worked fine
Meh
I've seen this behavior on my Nexus 5 only on 5.1, and I'm pretty sure, it was introduced with that specific lollibug version. It's really annoying, that you have to reboot the phone every two or three days to avoid the freezes.
There's already in issue for that, it has got the ID 161032.
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.
I have a XT1032 and a few days ago my screen started to ghost, while using certain apps like Gallery, Adobe Acrobat and WhatsApp ghost touches will occur, zooming in and out, opening menus and more. When exiting the app the problem continues until I turn off the screen, when I turn it back on it behaves normally. Didn't care that much but it started to get worse, and today I left my phone on the table, without touching it while WhatsApp chats screen was open, the phone screen started pressing itself and managed to send a message to various chats sharing an invitation to a group I created.
I've tried with various ROMs, from exodus 6.0, to Slim 7.0 and more but doesn't seem to get fixed.
What can I do??
Mh, sound like hardware problem
It seems no one is reporting anymore ghost touch issues anymore since oneplus released an update but I'm on the latest 10.0.2 update and I continue to get the occasional ghost touch at the top area of the screen. I had to send this phone to be repaired twice and still continue to get ghost touch issues. My two best friends who also purchased the 7 Pro on my advice are also getting ghost touches with one RMAing her phone due to this issue. Both are/were on the latest update.
When Im typing on whatsapp the phone will navigate to the contacts profile due to a ghost touch on the contacts icon.
I used a sketching app to see if I can visualize the ghost touches and noticed that, although infrequent, I can get ghost touches at least every few minutes.
One thing I also noticed is that there is significant touch latency in at the corners of the screen which can be visualized using the sketch app.
Anyone else having this issue?