Hi guys, my smartphone's screen gets black sometimes, and, after a quarter of second, it gets back. It's a Moto G Play (4th gen.). I want to unlock BL, root and change ROM too. But I'm scared about if it isn't a h/w issue.
If you can give me a hand, it'd be really appreciated.
Here's a logcat taken from the boot until 1 hour of activity reached: https://gist.github.com/FacuM/1bf3d99bf1c6c7dc4178051ab197074d
And here you can get a .zip packed version: https://gist.github.com/FacuM/1bf3d.../d2c32dcd9a3a30e28ae25e43d0c79f6427cda676.zip
Here, a logcat from when I wiped logcat until I opened a lot of apps with at least one black flashing: https://gist.github.com/FacuM/b72ae8c12bb50c5aebfec3c0eb3cf497
And here a .zip packed version: https://gist.github.com/FacuM/b72ae.../2e47f0cd8418ebda2c8522cac8b85b2bde826cdc.zip
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
dbal said:
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
Click to expand...
Click to collapse
Thanks for your answer. Basically, the problem as I see might be related to GBoard or Moto Display, as you say.
Also, I don't know if you've checked the logs I uploaded, but there are a lot of OMX decoding errors, I'm almost sure that there's no hardware failure there.
I'm now going to unlock Bl and see what's up with a custom ROM.
Sent from my Moto G Play (4th gen.) using Tapatalk
------
EDIT: Before proceeding, disabled Moto Display. Will give more feedback later.
Anyways, flashing again got the issue completely gone. Maybe your theory is the most appropriate.
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
dbal said:
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
Click to expand...
Click to collapse
BTW, I've already disabled Moto Display. I haven't fell asleep yet and it's 7 am here. Tomorrow I'll keep testing and hope it doesn't fail anymore. If not, I'll go for Bl unlocking and get rid of this Motorola's buggy attempt of softly modded AOSP.
Sent from my Moto G Play (4th gen.) using Tapatalk
Here I've uploaded a screencast of what appears to be related to the bug and shows clearly it's a software bug related to the video render in Marshmallow.
https://youtu.be/qhmUN43y0Pk
Sent from my Moto G Play (4th gen.) using Tapatalk
facuarmo said:
and shows clearly it's a software bug related to the video render in Marshmallow.
Click to expand...
Click to collapse
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
dbal said:
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
Click to expand...
Click to collapse
Sometimes, life's about taking the risk.
I've unlocked BL, flashed recovery and installed AOKP.
Now, no flickers found.
Prove:
https://youtu.be/T3e8-6dnyl0
Hope you like guys, and you take the risk too. Flashing a ROM solved everything.
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
dbal said:
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
Click to expand...
Click to collapse
I've compiled a kernel based on Squid2's sources with the fixed SELinux setup, then you should see no flickers so far in any ROMs.
Mine's working without any flicker, but I've only tested in Custom ROMs. Maybe you can try on stock?
https://forum.xda-developers.com/g4-play/development/kernel-somefeak-moto-g4-play-t3544556
Good luck and sweet flashes! :fingers-crossed:
Related
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
They must also fix
1)Choppy browser with and without flash.....
2)Random freeze of the gingerbread launcher...
slateac said:
Didn't Ry guy posted that a fix is coming and they already found the problem? Its been more than 2 weeks now..
Click to expand...
Click to collapse
I think it was posted that the reboot fix was coming, but not the loss of data.
Maybe I am just a lucky one, but I have had Nexus S since release and have only had a "random reboot" once; and no data signal loss issue AFAIK like Engadget has described. I have owned three Nexus Ss.
There are other issues, though, making it clear 2.3 is not bug free.
fchipm said:
Engadget just posted a story on the two major issues of signal loss and rebooting during calls.
Maybe with this Google will start to fix the problem? I sure hope so, as both are now affecting me more than ever.
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Click to expand...
Click to collapse
and they didn't even give us XDA credits
Perhaps 2.4 is coming sooner than planned and the fixes will be implemented in that? Just a wild guess.
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
i'm hoping they fix the quirky back button as well. that thing is driving me crazy!
I recommended the nexus s to my girlfriend, but seeing all these issues are making me regret it :\ there are no fixes/workarounds?
Sent from my SPH-D700 using XDA App
aaaaaand... 10char
Update: Huzzah! Just got a note from Google saying: "All of the issues described in the post are resolved and will be fixed with an OTA that will go out soon." Feel free to start mashing that "system updates" menu item.
Click to expand...
Click to collapse
that was fast.
Weird. I haven't had a single one of the issues described in any form. However, the browser issues do make me angry.
Glad there is a hotfix on the way (for the issues mentioned, that is, not necessarily the browser issues)!
The only issue that regularly bothers me is the vanishing ringtone one. It's not exactly critical from a utilitarian standpoint, but I think it's stupid that I should have to root and move files around my phone in order to set a custom ringtone. Still, I'm far too happy with pretty much everything else to switch.
I think one major sticking point with the Nexus S is that we have a fairly lengthy list of at least semi-common issues, but in several cases it's not clear whether those are hardware- or software-related. This is troublesome because the latter may be reasonably expected to get fixed in OTAs, while the former will probably only ever be resolved through workarounds, if at all.
I would be very pleased if Google were more transparent about what it's working on, or at least aware of, even if they (understandably) don't want to commit to fix dates. As a user, just knowing the basic nature of these problems and that they are being acknowledged would go a long way towards improving customer satisfaction in my book.
SooSpecial said:
The article was updated. Now saying that Google fixed the issues and an OTA is coming soon.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i read that there will be an ota update, but (maybe its a noob question) if your rooted will you still receive the update, and if so will it unroot the phone??
Fix the GPS!!!!!
Fix the keyboard: http://www.youtube.com/watch?v=RUZdvr6Pdjk
Discussed more in depth at this thread: http://forum.xda-developers.com/showthread.php?t=932838&page=13
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?
Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/
fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.
Try flashing a different kernel as that is what bridges hardware and software.
Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium
uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.
I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP
Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.
I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.
I can't figure out how to edit the top post on this
Got the update this morning and hardly noticed. One thing to note is the Verizon messaging application crashes when trying to send and receive MMS forcing me to use the new version. I only noticed because of this glitch. It has other instabilities as well and my battery suffered a loss, I only get about a full days use where I used to have almost 2. Also the phone keeps going into Airplane mode. The camera can't record in 4k mode either...
The first is the phone before the update, the latter two are after... Still near stock with circles widget. I can take it in to get it replaced, but I don't want the Verizon tramp stamp...
endafy said:
I can't figure out how to edit the top post on this
Got the update this morning and hardly noticed. One thing to note is the Verizon messaging application crashes when trying to send and receive MMS forcing me to use the new version. I only noticed because of this glitch. It has other instabilities as well and my battery suffered a loss, I only get about a full days use where I used to have almost 2. Also the phone keeps going into Airplane mode. The camera can't record in 4k mode either...
The first is the phone before the update, the latter two are after... Still near stock with circles widget. I can take it in to get it replaced, but I don't want the Verizon tramp stamp...
Click to expand...
Click to collapse
Is it a soak version or official? Yours is droid turbo or just Moto Maxx?
Please update more for us, thanks!!!!
chrisjenho said:
Is it a soak version or official? Yours is droid turbo or just Moto Maxx?
Please update more for us, thanks!!!!
Click to expand...
Click to collapse
Sorry Droid Turbo, and no I don't do soak tests. I rely too heavily on the device for business. I have a feeling the update may get delayed due to this. Trust me there are issues, and it is the only reason I noticed I got the update at all. The Maxx is the non-Verizon version.
Can you post some screenshot of the 'about phone'?
Any new stuff on the lollipop for droid turbo?
---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------
Also, I think you can downgrade the phone to 4.4.4 by RSD, if you need the firmware.xml, I get send a link to you.
If you've got lollipop, then why is the usb debugging icon from kitkat? :/
It's an alternative launcher....
So you got the update this morning? And yet you already know how the battery life is? Yeah nothing to see here, move along. Let's lock this before it gets out of hand
The op is also the guy that claims to have got root working.. Then provided Nada...
There's actually no indicative that it's lollipop. It's just the Google Now launcher before and after the update (app update)
Everything looks as kitkat as it could. Sorry, pal. You didn't fool us
Hey look, I got the update too!!
Its called an updated Google Now Launcher (or any other up to date third party launcher for that matter), not Lollipop.
endafy said:
I can't figure out how to edit the top post on this
Got the update this morning and hardly noticed. One thing to note is the Verizon messaging application crashes when trying to send and receive MMS forcing me to use the new version. I only noticed because of this glitch. It has other instabilities as well and my battery suffered a loss, I only get about a full days use where I used to have almost 2. Also the phone keeps going into Airplane mode. The camera can't record in 4k mode either...
The first is the phone before the update, the latter two are after... Still near stock with circles widget. I can take it in to get it replaced, but I don't want the Verizon tramp stamp...
Click to expand...
Click to collapse
Nice google now launcher. Nice try
cauebs said:
If you've got lollipop, then why is the usb debugging icon from kitkat? :/
Click to expand...
Click to collapse
This guys is a regular liar. He is using Nova, nay the Google Now Launcher.
zathus said:
So you got the update this morning? And yet you already know how the battery life is? Yeah nothing to see here, move along. Let's lock this before it gets out of hand
The op is also the guy that claims to have got root working.. Then provided Nada...
Click to expand...
Click to collapse
He also claimed that the soak test was over and Lollipop was rolling out two weeks ago. Of course, some of us know better.
Damn, the guy didn't even had the work to change the Kitkat debug logo on the status bar. I don't know if he's a bad pretender or really believed that his device was updated.
videtonator said:
Damn, the guy didn't even had the work to change the Kitkat debug logo on the status bar. I don't know if he's a bad pretender or really believed that his device was updated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58560723&postcount=10
Go ask Motorola for yourselves, it is past the soak test, and is now rolling out in the first wave. As soon as my device gets the update I will post screenshots, but I did provide proof of the Motorola conversation screenshot. I didn't even edit out my name. I stand by my word.
Click to expand...
Click to collapse
http://forum.xda-developers.com/dro...rbo-rooted-t3001024/post58177983#post58177983
I have it temporarily rooted, it loses root upon reboot, please wait until I can get a script working. I have been granted temporary root via camera. It grants temporary root via USB Debugging turned on with MTP and all that turned off. I have been able to remove VZW Bloatware... no luck on bootloader yet though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58794613&postcount=1
endafy said:
I thought I would, but everything I used to use root for I can do non-rooted now. This has all that I want and more, only a few minor setbacks.
USB OTG for storage, and USB gamepad, keyboards etc...
Wireless HDMI
USB Tethering I use PDA Net
Sideloading applications, provided they are signed, and signing an unsigned application isn't that hard...
--------------------------------------------------------------------------------
I can hide the apps (only drawback) but not uninstall them
I can't load kernel modules
Buttons are hardware so changing them is a non-issue
I can't change the battery icon
In fact up until the Lollipop update, the device has been fast, smooth, stable, and did everything I wanted. I think rooting and romming aside, and of course my next phone will be a developer phone, but I can live without root for a little while, this works well. I am off to the Verizon store to replace this so I can get a working Kit-Kat version, if I can get one without the Verizon trampstamp. If not I will just wait for a fix which will be coming shortly.
Click to expand...
Click to collapse
This guy is worthy of your ignore list. He first claims soak is over and Lollipop is rolling out weeks ago, then posts a launcher fake-out.
He claims he has root, then says he doesn't miss it? what a troll.
adrynalyne said:
http://forum.xda-developers.com/showpost.php?p=58560723&postcount=10
http://forum.xda-developers.com/dro...rbo-rooted-t3001024/post58177983#post58177983
http://forum.xda-developers.com/showpost.php?p=58794613&postcount=1
This guy is worthy of your ignore list. He first claims soak is over and Lollipop is rolling out weeks ago, then posts a launcher fake-out.
He claims he has root, then says he doesn't miss it? what a troll.
Click to expand...
Click to collapse
I already reported him as did a few others so hopefully they can deal with him. He must live a sad life, I really feel bad for him
All it took was 2 seconds looking at the wifi icon to see that this wasn't lollipop. I mean, come on, really? What's the point in this? I agree, definitely worthy of ignore list.
ahaynes42 said:
All it took was 2 seconds looking at the wifi icon to see that this wasn't lollipop. I mean, come on, really? What's the point in this? I agree, definitely worthy of ignore list.
Click to expand...
Click to collapse
Depending on the oem the wifi icon may or may not change. If you look at the s5 for verizon that icon didnt change.
the_rooter said:
Depending on the oem the wifi icon may or may not change. If you look at the s5 for verizon that icon didnt change.
Click to expand...
Click to collapse
That's touchwiz you're talking about. It doesn't look like stock android anyway. The Turbo (like most Moto phones) is meant to be as close to stock as possible. I'd be willing to bet quite a bit that our wifi icon will be solid white when we get the update.
How the hell does he get a full day of use if he got the update this morning. Please close thread and stop giving him attention.
Stop the bull****, the wifi icons are from kitkat
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
marcomsousa said:
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
Click to expand...
Click to collapse
Wish these were also available for the LTE model
[/COLOR]
Zylograth said:
Wish these were also available for the LTE model
Click to expand...
Click to collapse
Want to trade?
*WARNING* RE-enable OEM Bootloader Unlocking after Update!!!
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
I take it Root is still working?
bjacks12 said:
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
Click to expand...
Click to collapse
I've been thinking off using one of my phones as a hotspot for my laptop...Just not thinking it will be quite fast enough and stable enough to download and get a good MD5. My company watches everything.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why not just get it over with and UNLOCK it? Once you are unlocked, the state of that checkbox is irrelevant.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
s0101 said:
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
Click to expand...
Click to collapse
If you don't unlock, and leave your bootloader unlocked it can. If you have the check box checked then the bootloader remains locked. So if you get caught with a bad flash or anything else that causes a bootloop there is no way to gain access to the bootloader and run fastboot.
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Anyone get an OTA for the LTE version yet? They haven't posted the factory images which scares me a little that LTE might get left behind. The 5.0.2 links went up for both at the same time.
stuken said:
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Click to expand...
Click to collapse
Mine's still running really warm and it's losing power over USB just by being on. I'm watching the battery drain simply from the screen idling on Google Now. Come the **** on Google, heat and battery drain should have been primary concerns.
Edit: Fortunately though, it seems like the entire device is running buttery smooth, which is literally a first on stock Android for me. Even my Nexus 6 hiccups without a custom ROM and that has the S805 and 1 more GB of memory.
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
atomikpt said:
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
Click to expand...
Click to collapse
LTE takes time. I wouldn't worry about it. I bet factory images are up within a day or two. I'm an LTE owner too, so I'm in the same boat. I'm just happy it actually started rolling out, as it started to look like it wasn't happening. This is a much bigger update than 5.0.1 -> 5.0.2
Updated this morning. So far so good
So far, it's definitely an improvement on performance but it remains to be seen with this is another cache-wipe factor or something. One of the first-impression fixes is that the light sensor seems to actually work now, while it was almost useless before.
I noticed the stock kernel is now on 2,5GHz high and that both cores are allways on, which i am not sure if it was happening on 5.0.x. I remember Franco noticing it on Nexus 6 5.1 too, so i guess it's a common practice by google to not turn cores off anymore.
Well so far so good. I never had major issues before. OTA side loaded fine. Did a factory reset to set up fresh. Now that everything is set up I'm just waiting for it to charge completely. It did get warm installing and updating everything, but no issues so far. Everything went smoothly.
There's a new apk named 'Who Am I?' That is disabled by default in this update. Turns out it's a widget that literally shows you the time and what your name is. Maybe it's for people with dementia or short term memory.
The way things have been going, most of us might have needed that widget by the time this update got to us if we'd waited much longer.
Please take some time out to post on this (lenovo)forum:
https://forums.lenovo.com/t5/MOTO-G...nd/Moto-G-2nd-Touch-Delay/td-p/3318514/page/2
with the following info:
Also, we'd like to get some information about your phones. If you have ADB and know how to use it, please run the following ADB commands and report back the results.
adb shell cat /sys/bus/i2c/devices/5-0020/ic_ver
adb shell cat /sys/class/graphics/fb0/panel_ver
adb shell cat /sys/class/graphics/fb0/panel_supplier
This has been asked by a moto agent and she said on 27th may that it would be "evaluated by the engineers" but so far no reply. If you could please post on the forum with the info so that she could know that there are many of us who notice this bug. Maybe create a few new threads, too? Maybe with enough noise something might happen
For those who say "what bug, I don't know" try Local Warfare Portable from Play Store on 5.1 and 6.0.1 and see the difference. Besides games firefox scrolling is pretty messed up, I can't read an article properly on it.
Thanks
No news for now? Would be bad for Motorola to confirm an issue and do nothing to fix it.
I really don't think they'll provide any means of fixing this issue. This is not their flagship phone, and 6.0 will be the last Android support G2 will ever have. Even now beign Lenovo.
Google did the same thing by not acknowledging the Nexus 4 camera bug, their flagship at the time.
sky0165 said:
I really don't think they'll provide any means of fixing this issue. This is not their flagship phone, and 6.0 will be the last Android support G2 will ever have. Even now beign Lenovo.
Google did the same thing by not acknowledging the Nexus 4 camera bug, their flagship at the time.
Click to expand...
Click to collapse
You are wasting your time mate! Lenovo does not and will not respond to any problems with these phones. Look at the the hardbrick issue affecting 100's of Moto G2nd users. They just don't give a damn!!!! I have a working Moto G2 but but it will be my 1st and last Moto phone ever unless they change their attitude towards us ... The end users.
We failed, lol
After seeing their support, I'm certain about not buying any Lenovo/Moto device again
josfr4ncisco said:
We failed, lol
After seeing their support, I'm certain about not buying any Lenovo/Moto device again
Click to expand...
Click to collapse
Good luck with that. I've had Moto, Samsung, Huawei, and LG and support was crap on all of them.
Tel864 said:
Good luck with that. I've had Moto, Samsung, Huawei, and LG and support was crap on all of them.
Click to expand...
Click to collapse
Actually, had good support experiences with Samsung, but since their new phones are dev-closed, I'm looking for another brand. Currently looking at Xiaomi.
What's the touch issue?
NotFatMan said:
What's the touch issue?
Click to expand...
Click to collapse
The screen doesn't pick light/quick touches correctly. I recorded a video showing the issue a few months ago, here it is:
On CM13, doing a quick swipe to unlock the phone doesn't work correctly, you have to do a firm swipe. It's really annoying, mostly in some games like Vainglory (touch-based moba where quick taps are essential) and Pokémon GO (swiping to throw the pokeball doesn't work only you really press on the screen).
Sent from my Moto G 2014 using XDA Labs
Guys, Motorola pushed an update and seems like it fixes the touch issue. Can someone check?
josfr4ncisco said:
Guys, Motorola pushed an update and seems like it fixes the touch issue. Can someone check?
Click to expand...
Click to collapse
source?
Wolfcity said:
source?
Click to expand...
Click to collapse
Someone posted it on CM14's thread, also reported on Motorola/Lenovo's forums.
---------- Post added at 07:42 PM ---------- Previous post was at 07:13 PM ----------
Confirmed, the issue is gone on Thea. Checking Titan later.
Update: I'm talking with LuK about fixing the issue, and if we can find the firmware for XT1072, he probably will get it fixed. Can anyone help?
Confirmed: the touch issue was solved. Moto needs to release kernel source now so custom ROMs can be fixed as well.
known when the update will appear on the ROM retail dsds.retaildsdsall.en.03 ??
now my system is up to date
Guys, so seems like LuK found how to fix the touch issues. The latest stock ROM (the one released a few days ago) updates your bootloader to version 0x4887, and that new bootloader fixes the touch issue. When I mentioned the new bootloader to him, he asked me to flash CM13 because it could fix the touch issues, and it did! So, for those who experience touch issues on custom ROMs, please flash the latest stock ROM to update the bootloader, and then flash CM13/14 to have your issues solved
Could someone give me the link to the new update? Would avoid a lot of wasted time
dmop21 said:
Could someone give me the link to the new update? Would avoid a lot of wasted time
Click to expand...
Click to collapse
Here's the link for Moto's FileFactory folder: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Go ahead and check if the update for your model/country is already there.
I have XT1068 EU, can I flash bootloader of XT1068 BR?
Zenzero XT1068
Can someone upload just the bootloader for 1063 please? Poor connection with filefactory
Enviado desde mi Moto G 2014 mediante Tapatalk