Project Fi 8.1 Update Pending. 5/18/18 - Moto X4 Guides, News, & Discussion

5/18/18
I just spoke with a Moto Rep and There is no confirmed date for the release of the 8.1 update for Fi Moto x4

I have Android 8.1 on Project Fi. It updated a few days ago.

Try clearing app cache of moto software updater and reboot. Worked for my wife's phone.
Sent from my Nexus 5X using XDA Labs

It's already been released.

I literally spoke with them yesterday, I wonder why the rep told me it hasn't been released, clearly people have it, I tried clearing Moto cache and no go

azazelcrey said:
I literally spoke with them yesterday, I wonder why the rep told me it hasn't been released, clearly people have it, I tried clearing Moto cache and no go
Click to expand...
Click to collapse
Don't get too excited about it. 8.1 breaks USB connectivity if you use any kind of lock screen. They don't have an estimate on a fix either.

I just want it so I can have root again and twrp. I'll probably root and wait for lineage.

Related

[Q] Lolipop Update

Hi, I'll be quick,
I know almost all nexus devices have now Lolipop, everyone on my friend with a nexus 5 have now Lolipop, but for some reason i don't have any update prompt. If it can help, I bought it from a carrier here in canada called Fido.
fastboyz said:
Hi, I'll be quick,
I know almost all nexus devices have now Lolipop, everyone on my friend with a nexus 5 have now Lolipop, but for some reason i don't have any update prompt. If it can help, I bought it from a carrier here in canada called Fido.
Click to expand...
Click to collapse
I have received the update yesterday and i'm also using fido in the montreal area. My advice: stay away from this update for the moment. Lots of bugs.... will probably flash back the 4.4 image tomorrow and will wait for 5.1 instead.
My son just got the OTA on Telus this afternoon. Be patient, you will get it.
Sent from my Nexus 5 using Tapatalk
lucky
I'm in montreal area too but i still dont get it why I'm not even reciving the update prompt . I feel like there might be something wrong.
fastboyz said:
I'm in montreal area too but i still dont get it why I'm not even reciving the update prompt . I feel like there might be something wrong.
Click to expand...
Click to collapse
believe me, you don't want to update.... be patient and wait for 5.1. lots of issues in 5.0. Android L is great in general, but with all those bugs, it doesn't worth it for now. Actually I can't even charge my phone unless I turn it off...
And there is nothing wrong, google said it could take many weeks before all N5 get the update.
fastboyz said:
Hi, I'll be quick,
I know almost all nexus devices have now Lolipop, everyone on my friend with a nexus 5 have now Lolipop, but for some reason i don't have any update prompt. If it can help, I bought it from a carrier here in canada called Fido.
Click to expand...
Click to collapse
Don't worry about the OTA, just flash a ROM and call it a day.

Marshmallow 6.0.1 for LG G Stylo

Do you think that the LG G Stylo will receive Android 6.0 and Android 6.0.1? I know the variant from T-mobile will get the updates, they have confirmed that, but will the Stylo's on Metro PCS get them too? Its exactly the same phone. Metro PCS fb reps won't comment on this.
LordHades21999 said:
Do you think that the LG G Stylo will receive Android 6.0 and Android 6.0.1? I know the variant from T-mobile will get the updates, they have confirmed that, but will the Stylo's on Metro PCS get them too? Its exactly the same phone. Metro PCS fb reps won't comment on this.
Click to expand...
Click to collapse
chances are yes and with the record so far you guys are the only ones that will get the KDZ as well
most likely, Metro pcs is owned by T-mobile.
DB225 said:
most likely, Metro pcs is owned by T-mobile.
Click to expand...
Click to collapse
Didn't know that lol
6th_Hokage said:
Didn't know that lol
Click to expand...
Click to collapse
yep, they bought it about what two years ago or so now.
http://www.cnet.com/news/what-t-mobiles-merger-with-metropcs-means-to-you-faq/
So now the question is.... How long do we wait.. Any ideas?
Their comments on it. I don't think the customer reps know much anyways though...
Well I think I need to switch to metro then. No word on boost love. There's nothing to lose. And I'll gain an extra gb of ram
Boost and sprint are getting the marshmallow update zv7. Don't know about T-Mobile and metro
Just grabbed a Boost Stylo today for a decent price, installed the rooted system image from 6th_Hokage and have it working fairly well after freezing out a lot of stuff but even so the RAM usage seems pretty excessive with not much going on - this is with no apps running after a reboot and at about 1 min I started up System Monitor Lite to take a peek:
I mean, I've gutted it of most everything I can that could interfere with the startup and suck out the RAM en mass so, I suppose it'll work itself out. Not bad performance I suppose but of course the Boost/Sprint variants of the Stylo are handicapped for no good reason with 1GB of RAM and when I had a MetroPCS variant a few weeks ago it was very noticeable in terms of overall performance.
Anyway, I just noticed this Marshmallow info over at another site so it's pretty cool to see it being pushed from Boost just before the end of the year, pretty cool indeed. I don't know if I'll bother with it at this point since root is a must and I'm not sure if or when we'll see it for Android 6.0.1 on this device (LS770). Will be nice to see if there's any improvement in this after-boot RAM usage as well, especially after some removal of some bloatware whenever it happens.
Will be interesting to see how things progress now that it's finally here, definitely.
according to T-Mobile's software update tracking site the Stylo is confirmed for getting a 6.0 update, although they haven't really given a timeframe for it. It's currently listed as "Manufacturer Development" which means that they most likely haven't started their own testing on it just yet. My best guess is that we'll see it come before Q2 of next year on T-Mobile, and possibly a similar timeframe for MetroPCS as well (since they're a child company of T-Mobile).
Can't really say for the Boost/Virgin/Cricket models though. Sprint already has 6.0 pushed to the Stylo in some markets and is supposedly rolling them out across more now. And since Boost and Virgin are child companies of Sprint, they'll probably also see an update soon.
jxthrx said:
And since Boost and Virgin are child companies of Sprint, they'll probably also see an update soon.
Click to expand...
Click to collapse
The Boost 6.0.1 update (LS770ZV7) came out on December 28th and is currently being pushed to devices:
http://devicehelp.boostmobile.com/d...Boost_Mobile/en/Software_Updates_-_LG_G_Stylo
br0adband said:
The Boost 6.0.1 update (LS770ZV7) came out on December 28th and is currently being pushed to devices:
http://devicehelp.boostmobile.com/d...Boost_Mobile/en/Software_Updates_-_LG_G_Stylo
Click to expand...
Click to collapse
dont receved the update
emanuelrv said:
dont receved the update
Click to expand...
Click to collapse
It will probably be soon. They can't roll out updates to everyone all at once. They usually do it by region.
Ehh....warned my bro that has my rooted Stylo not to except any system updates....hopefully we can crack that update soon
If it's rooted it shouldn't accept any updates, at least that's how most every phone running Android is these days: any tampering or changes to the system partition (which obviously flashing your rooted system img does) should prevent the OTA check from being successful. At least that's how it is on some other devices I've owned in the past 1.5 years - if the device ain't pure 100% bone stock with no mods done at all the OTA's usually just don't even happen but, this could be different, I don't know but I suppose we'll find out soon enough.
br0adband said:
If it's rooted it shouldn't accept any updates, at least that's how most every phone running Android is these days: any tampering or changes to the system partition (which obviously flashing your rooted system img does) should prevent the OTA check from being successful. At least that's how it is on some other devices I've owned in the past 1.5 years - if the device ain't pure 100% bone stock with no mods done at all the OTA's usually just don't even happen but, this could be different, I don't know but I suppose we'll find out soon enough.
Click to expand...
Click to collapse
i mean that he doesn't try to install the update cause it will download
6th_Hokage said:
Ehh....warned my bro that has my rooted Stylo not to except any system updates....hopefully we can crack that update soon
Click to expand...
Click to collapse
I've been using your rooted system for weeks. Works perfectly.:good: Thank you.
Just received the update ( ls770zv7 ). I uploaded it. Hope you can crack it too.
https://drive.google.com/file/d/0B8jh0cpIovnMTlBOelVLdVBIdnM/view?usp=sharing
So is that 6.0.1 marshmallow or just 6.0. What variant do you have (boost)? Just curious

First time setup question

So, I picked up a new unlocked 4a from BestBuy today. Before I set it up, I want to know if I should let the phone upgrade to Android 11 or try to keep it on 10? I know there have been some problems with 11. What's the opinion on this?
woody1 said:
So, I picked up a new unlocked 4a from BestBuy today. Before I set it up, I want to know if I should let the phone upgrade to Android 11 or try to keep it on 10? I know there have been some problems with 11. What's the opinion on this?
Click to expand...
Click to collapse
My opinion is to wait for the November or December update and then upgrade to Android 11.
I'm still on Android 10
woody1 said:
So, I picked up a new unlocked 4a from BestBuy today. Before I set it up, I want to know if I should let the phone upgrade to Android 11 or try to keep it on 10? I know there have been some problems with 11. What's the opinion on this?
Click to expand...
Click to collapse
No issues with A11; Oct update smoothed out a few rough edges that weren't that jagged to begin with. Every update brings drama from the fringes. Gotta decide what camp you fall into.
Are there any Android Auto issues with the current version of 11? I think there were some at one point. BTW, I'm upgrading from an OG Pixel XL which is still going strong.
Weird mine came with 11 out of the box.
Limeybastard said:
Weird mine came with 11 out of the box.
Click to expand...
Click to collapse
You're in the UK? I think your release date was later than other countries so that's probably why.
WAusJackBauer said:
You're in the UK? I think your release date was later than other countries so that's probably why.
Click to expand...
Click to collapse
I'm based in USA although an expat. I bought mine from Best Buy today.
Just my 2 cents. I just got my 4a yesterday and it came with 10, i updated to 11 during setup. I have ZERO issues. I was actually a little worried reading stories about issues, but i don't have a single issue.
tCizler said:
Just my 2 cents. I just got my 4a yesterday and it came with 10, i updated to 11 during setup. I have ZERO issues. I was actually a little worried reading stories about issues, but i don't have a single issue.
Click to expand...
Click to collapse
Of course you didn't. For every negative report there are vastly larger numbers of perfectly happy users. Widespread issues draw a huge response over multiple boards that easily stand out from run-of-the-mill grumbling.
DB126 said:
No issues with A11; Oct update smoothed out a few rough edges that weren't that jagged to begin with. Every update brings drama from the fringes. Gotta decide what camp you fall into.
Click to expand...
Click to collapse
Plus if you DO have problems after "use 10 for a bit, install 11" then you'll probably end up factory resetting and doing all your reinstallation, config again.
(I recall from back when i could be bothered fiddling with cyanogenmod that nobody was interested in bug reports if you did a "dirty flash" - you had to do a factory reset first as it cured all sorts of problems. i wonder if google doesn't test stuff properly and you end up in the same situation and that's why factory resetting fixes so many problems).
The devices came with 10/11 based basically of release date in your state/region you live. I for example live in Italy and I bought mine from Google directly. It arrived 8 Oct with already 11 installed and with Oct security patch. No issue here with 11, as the major part of the other people. Let's say that's generally is expected to have some problems when there is a major release come out, as with any other software piece, not only android, but generally a couple of update fix all. And it seems so with Google security patch too.
I've decided to go ahead and update to 11. I assume that the pending update is for the Oct release,, but the notification doesn't show which release it is, only that it's for v11. I don't really want to factory reset before the update. Does anybody think it's a good idea to do a reset first?
woody1 said:
I've decided to go ahead and update to 11. I assume that the pending update is for the Oct release,, but the notification doesn't show which release it is, only that it's for v11. I don't really want to factory reset before the update. Does anybody think it's a good idea to do a reset first?
Click to expand...
Click to collapse
On Android 11 because phone shipped with it .
Should be no need to reset first.
No touch screen issues with Spigen protector.
Android auto works fine with the assistant lagging from time to time. However that could have been due to poor service....
woody1 said:
I've decided to go ahead and update to 11. I assume that the pending update is for the Oct release,, but the notification doesn't show which release it is, only that it's for v11. I don't really want to factory reset before the update. Does anybody think it's a good idea to do a reset first?
Click to expand...
Click to collapse
It's best to factory reset AFTER updating.
Also I'm fairly sure by now every region would have the October security update.
I did the update this afternoon. The update was for the September release, but then there was a 2nd update which brought it up to October. The phone seems to be running well after the updates. It seems a little zippier than before.

December update, OTA

Is anyone else still waiting for the December update to be available for OTA download? Google Pixel 3, unlocked, not rooted, not happy. Never waited this long before.
Is it a Verizon phone? Verizon updates are supposed to roll out this week. The update for non-Verizon phones was available last Monday.
I don't get OTA updates on my rooted phone because of root. I don't know if just being unlocked prevents OTA. You can always download the factory image and manually update. The images are at https://developers.google.com/android/images.
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Fat fingers! 1st sentence intended to be "Thank you for the response".
BlackKeys said:
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Click to expand...
Click to collapse
In that case, you will have to apply the update manually. The factory image is at the URL I gave previously. Edit flash-all.bat/sh to remove the -w from the last line in the file so the phone is not wiped.
You could also apply just the OTA manually. The OTA images are at https://developers.google.com/android/ota. I have not done that - I use the factory image method.
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
BlackKeys said:
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
Click to expand...
Click to collapse
You can search for update errors in logcat. See https://forum.xda-developers.com/t/tutorial-how-to-logcat.1726238/ on how to get a logcat. If you did the manual "Check for update" look in the log at the time you did the check. Logs are kept for quite a while, so the info should still be available.
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
dcarvil said:
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
Click to expand...
Click to collapse
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
TonikJDK said:
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
Click to expand...
Click to collapse
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
dcarvil said:
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
Click to expand...
Click to collapse
That has always been there, very sure of that. A lot of us went done that rabbit hole with the Pixel 1 or 2. We never new for sure what it did, but I remember freezing it and had all kinds of connection problems.
Other carriers have those types of things too. They are built into the image and go live when the phone sees what carrier it is on.

Question Still on November Security patch

I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
T-Mobile I'd imagine. Just use Pixel Flasher or https://flash.android.com
I joined the beta program
BladeRunner said:
I joined the beta program
Click to expand...
Click to collapse
How is it? Stable enough to daily drive? I was stuck on the Nov. 22 patch as well until I sideloaded via ADB last night.
Nov 1 is the latest Play System Update afaik, at least thats what the QPR shows....
Google is having problems
This is one of those moments where it's not you it's them is actually true and not gaslighting . Play Updates are not rolling out properly
BladeRunner said:
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
Click to expand...
Click to collapse
Seems you are not alone.
T-Mobile is running way behind on Google Pixel security updates
Timely updates are supposed to be a prime Pixel perk
www.androidpolice.com
Yeah I am on December update very annoyed with Google nothing has changed
Deleted
That sucks and should not be the Pixel experience. I would call T-Mobile and ask them why you are on an old update?
I have had decent updates so far but would be rather upset if I had a security update that was older than other OEM as that is part of the reason for getting a Pixel.
Sign up for Beta and you'll get QPR2 Beta 2. In my experience, it is much more fluid and responsive than previous builds. It fixes the scrolling issues and seems to have improved battery compared to the December update.
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Colchiro said:
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Click to expand...
Click to collapse
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
EtherealRemnant said:
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
Click to expand...
Click to collapse
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Colchiro said:
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Click to expand...
Click to collapse
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Also mine show November as last play service update (I'm on the beta). Italian unlocked phone
Nov is the latest still for play system. There wasn't a Dec and Jan hasn't rolled out yet
EtherealRemnant said:
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Click to expand...
Click to collapse
There's also the indeterminate minutes, if/when something goes sideways...
This is being delayed for un-branded devices as well, such as mine purchased G-Store direct, based on some sort of carrier-block. I'm tempted to go dig through some dev-docs, to see if I can find this (could be an section not published for most, I suppose), but I figure to what end, mostly.
As you mention, easy side-load, but without knowing why this is being blocked for non-TMo (branded, so not gated by their release of their OTA) devices, it's a gamble of sorts...
I just posted in another thread that I think this is an odd situation. I use an MVNO Boost Mobile that uses T-Mobile and I got the update on the 5th. Maybe I got it before they pulled it? Why would they hold the update back to T-Mobile customers but not the MVNO?

Categories

Resources