Skip navigation
1 2 3 Previous Next

Republic Help Updates

43 Posts authored by: theproductguy Employee

Hello again…. Product Guy here with another MR update for the Moto E (1st Gen) and introducing a new update for the Moto X (2nd Gen).

 

The Moto E (1st Gen) Lollipop MR has finally made it out of the Sprint lab. It’s free !!!!

 

We have Technical Acceptance and are getting ready to ramp up for the soak and rollout, so let’s talk about the next steps of the rollout plan and when it is going to happen:

 

Communication will go out via email on 8/22 to all active Moto E (1st Gen) members to let you know what to do to upgrade the phone cleanly to Lollipop.  

 

The soak test will start on 8/22 giving us enough time to clear the increased ticket volume after launch.

This means that 1% of the devices will receive a notification about the update.

 

Pending the results of the soak test, the plan is to start the full rollout on 8/30, and will continue over the rest of that week.

 

This one has been a long time coming, and we are happy to get it to you.

 

Stagefright fixes for Moto X (2nd Gen) are also coming along right on the heels of the Moto E (1st Gen) update.  

This has already reached the lab on 8/15 and is scheduled to come out of the  lab on 8/29.  We will have more updates on this as we near the lab exit date.

 

Keep an eye out for the emails starting next Monday.  We appreciate your patience.

 

As always, stay WiFi my friends.

Welcome back to another update on the Moto E (1st Gen.).

 

The Moto E (1st Gen) Lollipop build has one low level issue that we are trying to resolve with the lab.  We don’t believe this will be a hold up for rollout, but it has delayed the release of the build from the lab by a few days.  We hope to have Technical Acceptance (aka Lab Exit) by the end of this week.

 

If we get the TA this week, it will not impact the proposed plan we talked about in the last post.

 

To reiterate, our current plan is to start the soak for the Moto E on August 18th.  This test will run for a week and devices will be selected at random.  The push of the build to all devices will start the week of August 25th.

 

Here’s a link to the previous Update if you would like to read in more detail.

Device MR Progress Report 7/18/16 

 

I will post another update on the 16th to let you know the plans for the soak etc.

 

As always, stay WiFi my friends.

Welcome back. Here’s the latest update on the Moto E (1st Gen.).

 

We have some great news to share.  The Moto E (1st Gen.) Lollipop software build did indeed make it to the lab, if a couple of days late, on July 14th, and is enjoying it’s time in the luxurious Sprint lab.  (I’m obviously trying to make it sound more glamorous than it is… it’s sitting on a shelf while waiting for tests to be run)

 

In these scenarios, no news is good news.  We haven’t heard anything so far, so we expect to hear good news and a passing grade by the middle of next week, the 27th.  Think good thoughts….

 

After that, we have a confluence of events….

 

As we said in our last update, we were working with our tech support teams to determine capacity for support as we are launching a plethora of new devices on July 28th and want to make sure that Moto E (1st Gen.) members get our full attention to make sure that if there are issues, we are on top of them and helping you out.

 

Based on that conversation, our current plan is to start the soak for the Moto E on August 18th.  This test will run for a week and devices will be selected at random.  The push of the build to all devices will start the week of August 25th.

 

We will publish another update on August 1st to confirm the details and rollout schedule.  If, for whatever reason, the device doesn’t exit the lab this week, I will post an update to the blog with details of the changed schedule.

 

If you missed the update a couple of weeks ago, here's the link to that update.

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]


As always, stay WiFi my friends.

Here’s the latest update on the Moto E (1st Gen.).

 

Some phones are just more challenging than others.  During our dogfood process, we have discovered an issue related to our carrier partner network connectivity that we have had to fix. 

 

This one is a little inside baseball, but hang with me.  Let's get into the weeds...

 

The PRL file (Preferred Roaming List) basically contains the list of towers the phone can connect to.  The carrier updates this file periodically when they add new roaming partners or change agreements.  This file is compressed and then stored in a fixed memory space on the cellular modem.  The latest file we received when compressed was 96 bytes too big for the allotted space in the modem.  This caused issues when connecting to the cellular network, as the file checksum was incorrect, and the file was corrupt. 

 

We have created a patch for this for the phone so that we won’t put the updated PRL in the modem if it is too big to fit in the allocated space. We are also working with the carrier to increase the compression to try to make the file smaller. Lastly, our carrier partner had to make a network side change to make sure that phones don’t get updated with a big fat PRL before the fix rolls out that will stop them from operating.

 

In addition, we have been working with Motorola to reduce the number of apps in the build to make sure that the install and pre-compile process introduced in Lollipop will run through successfully.  This has worked, so we are confident that this process will make installation less of an issue with memory management.  We outlined the majority of these issues in the last blog post.

 

Next steps are to do another round of regression tests, and prepare the build for the lab.  When the phone enters Slate, we submit to Google certification as well, so we are preparing for this to happen shortly.

 

Our Lab Entry date is tentatively schedule for July 11th with 2 weeks for lab certification, then soak test, and a staggered rollout of the build.

 

We are working with our tech support teams to determine capacity for support as, surprise, surprise, we are launching a plethora of new devices on July 28th and want to make sure that Moto E 1st Gen members get our full attention to make sure that if there are issues, we are on top of them and helping you out.

 

Our latest estimate is that we will start a staggered rollout process for this in mid August (assuming nothing changes between now and then) to start updating your Moto E 1st Gen to Lollipop.

 

Thanks again for your patience, and we’ll publish another update in a couple of weeks. This has been, literally, the most difficult build process we have done, as there are a lot of technical challenges and physical limitations with this phone.  We have considered at several points on the way whether this phone has been worth updating to Lollipop, but we made promises to you as customers that we would.  It has taken a lot longer than we have anticipated, but we are in the home stretch.

 

Apologies for the full autopsy report on where we are, but we wanted to share full context into what is happening.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

Have a great week.

 

As always, stay WiFi my friends.

We hope you all had a relaxing weekend.  Here’s the latest update on the Moto E (1st Gen.).

 

The internal dogfood on the phone is wrapping up, and we wanted to share the findings with you.  We have seen some memory space issues with the Lollipop build on the phone.  The Lollipop build is pretty big, and combined with the way that Lollipop optimizes all the apps to run when it starts up, creates some memory space challenges. 

 

So, what does that mean for you?

 

If you are going to upgrade to Lollipop on the Moto E (1st Gen.), we would advise you get an SD card for your phone to move your media and apps to.  This won’t completely solve the issue because some apps can’t run from the SD card, and when apps are updated from the Play Store, they move back to the phone, but it is a temporary fix for creating more storage on the phone.  Another option (or as well) is to pare down the apps you really need on the phone.  If you are like me, outside of my “go to” apps, I download a new app, look at it once or twice and then forget about it.  So, now is a good time to take stock of the apps you have installed and need.  Our advice is to uninstall the ones you don’t use as they will take up valuable space when Lollipop arrives.

 

This is not a Republic specific problem, but is an issue across the board for Lollipop.  Lollipop has a larger footprint than KitKat, and there is a large increase in the size of Google Mobile Services apps. This is especially challenging with a small memory footprint such as the 4GB Moto E (1st. Gen).  It hasn’t been as much of an issue on the other phones as they have more memory.

 

We still feel that the calling and texting performance of the phone has been significantly improved, and that’s why we are pushing ahead with the update, but we are going to make the update optional on launch and see how the update looks.

 

So, what are the next steps?

We have to incorporate one final round of Android Security patches. Android is releasing updates on a more frequent basis, and in order to make it through Google Certification, we have to include them.   We will do a round of regression tests, and prepare the build for the lab.  When the phone enters Slate, we submit to Google certification as well, so we are hammering to get this done in the next couple of weeks.

 

Ok, so when is Lollipop going to happen? We will go through the normal steps:

 

Integrating newer Android Security patches: About 2 weeks.

Regression Testing: A week or two.

Slate: One week for lab preparation

Lab Entry: 2 weeks for lab certification

Soak : 1 week for soak

Rollout will start the week following the soak.  These are tentative timings, but we are pushing to accelerate them if we can.

 

We appreciate your patience, and we’ll publish another update in a couple of weeks. I hope this level of detail is useful.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

Have a great week.

 

As always, stay WiFi my friends.

With everything else going on last week, we haven’t forgotten about the Moto E update to Lollipop.  The good news is that the build has gone through the QA process with no major issues. Next up, we are going to start the internal dogfood process. This process is usually takes about 2 weeks.

 

This is a big milestone.  It means the phone has cleared the first set of tests (to make sure that the basic functions perform within tolerances) and we are now using this phone internally. 

We had initial concerns about the performance of the device on Lollipop, but these have been alleviated, and we are pushing forward.

 

We are continuing to work as hard as possible to get this done. We want you to enjoy all the Adaptive Coverage goodness announced a couple of weeks ago.

 

We appreciate your patience, and we’ll publish another update in a couple of weeks.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

We hope you enjoy your weekend.

 

As always, stay WiFi my friends.

Another update for the Lollipop MR for the Moto E (1st Gen).  We have a fix for the WiFi issue and are now waiting for the latest round of Android Security patches to be integrated. Android issues security patches on a periodic basis, and based on timing, Android insists that these patches be integrated before being released.

 

We are inching closer….  We understand that this is a frustrating process, especially the lag between the G and X and now the E. The E has hardware and memory constraints that the other phones did not have, so it really is a unique case.  We are working as hard as possible to get this done because we want you all to be able to take advantage of the Adaptive Coverage updates announced in the last week.

 

As we have said, when we have a stable and functioning build, we will move on the next phase of the process.

 

We appreciate your patience, and we’ll publish another update in a couple of weeks.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

We hope you enjoy your week.


As always, stay WiFi my friends.

Here is the slightly overdue update for the Lollipop MR for the Moto E (1st Gen).  We are currently investigating a WiFi connectivity problem unique to this hardware and software combination that is causing issues in staying connected to a WiFi network when trying to place a WiFi call. This is holding up forward progress at the moment, and we are working to try and diagnose the root cause of the issue, so we can continue to run through the test suite.

 

When we have a stable and functioning build, we will move on the next phase of the process.

 

Unfortunately, these things are difficult to predict how long it will take to find and what will need to be done to fix the issue.  As we have said in previous bulletins, we have to make sure the build is of a high enough quality before we release it.  The team is focused on trying to get the build completed, but It is taking longer than expected, but we are continuing to work on it. 

 

We appreciate your patience, and we’ll publish another update in a couple of weeks.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

We hope you enjoy your week.

 

As always, stay WiFi my friends.

 

Apologies for the tardiness on getting the report out this week.

 

We have been working on the bugs discovered in testing on the Lollipop MR for the Moto E (1st Gen), and will be getting another build from our partner soon.  As we progress and feel confident releasing dates, we will publish a schedule for you.

 

Until then, we’ll update you again in 2 weeks.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

We hope you have a great weekend.


As always, stay WiFi my friends.

As promised, here is the next update in the series. 

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

We are down to our last major software update. 

 

Moto E (1st Gen.) - QA has uncovered several bugs that will require a new build, so we are currently waiting on that from our partner, and then we can re-test and continue progress.

 

Installation Progress

Moto E (2nd Gen.) -  We are currently seeing about 80% of the members with a Moto E (2nd Gen.) have updated. This update fixes the audio issue that was being heard on calls.

 

You can go download and install it immediately, or keep an eye out for the notification.

Detailed instructions are available here: https://community.republicwireless.com/blogs/republic/2016/02/25/moto-e-2nd-gen-emr-update

 

Look for another update on March 29th.


As always, stay WiFi my friends.

Another MR update.  The finish line is approaching. We are a little late getting the report out this week, but there’s a good reason for that.

 

As always, here’s the full back catalog of past updates:

 

[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

Remaining Updates to complete:

Moto E (1st Gen.) - QA has started in earnest.  The process of uncovering issues and getting fixes has begun !!!

We will keep you updated on progress with QA and our internal dogfood testing to keep you all in the loop.

 

Moto E (2nd Gen.)We are ready to go. Some of you already received the update as part of the soak test. It went well and the download rate was over 80%, which is really great for a soak test. This morning, we rolled out the full update and it is now available to 100% of Moto E (2nd Gen.) phones.

 

You can go download and install it immediately, or keep an eye out for the notification ... Detailed instructions are available here: https://community.republicwireless.com/blogs/republic/2016/02/25/moto-e-2nd-gen-emr-update

 

With the QA and internal dogfood process starting on the Moto E (1st Gen.), there won’t be a lot to communicate over the next few weeks, so we’re going to take this update back to every 2 weeks until we have a schedule locked down.

 

Look for another update on March 15th.

 

As always, stay WiFi my friends.

 

Welcome back to another MR update.  Shorter and sweeter this week than last week.

 

As always, here’s the full back catalog of past updates:


[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

Remaining Updates to complete:

Moto E (1st Gen.) - We have been slightly delayed in starting QA on this build, build but expect to be kicking off as soon as possible.  Based on the quality of the build, we’re planning to kick off the internal dog food process in the next couple of weeks  We will keep you updated on progress over the next few weeks.

 

 

Moto E (2nd Gen.) -  We have completed lab and are waiting for the final paperwork to be signed off.  This has delayed the soak a little, but we will be rolling out the update to everyone at the same time, rather than staggering it.
Current estimation dates for Moto E (2nd Gen.) are shown below:

  • We’ll do a public soak test with a small number of our members, starting on Wednesday, February 24th, or Thursday, February 25th, pending final paperwork from Sprint
  • We’ll roll out the Over the Air (OTA) update to the Moto E (2nd Gen.) phones starting on Wednesday, March 2nd or Thursday, March 3rd.

 

We’re getting close…

 

As always, stay WiFi my friends.

 

Welcome back to another MR update.  Short and sweet this week.

 

As always, here’s the full back catalog of past updates:


[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]

 

Remaining Updates to complete:

 

Moto E (1st Gen.) - We are kicking off QA for this build in the next few days and are already  marshalling resources internally to start a dogfood test.  This will go on for about 3 to 4 weeks.
If there are no issues discovered, we will then start the SLATE and Lab entry process.  As we mentioned last week, we are still a few weeks away (but a week closer !) from this being ready to go.  We will let you know a more concrete plan when we are through the QA process.

 

Moto E (2nd Gen.) -  We are in the lab starting yesterday.
Current estimation dates for Moto E (2nd Gen.) are shown below:

  • We’ll do a public soak test with a small number of our members immediately following, starting on Monday, February 22nd, pending lab exit.
  • We’ll roll out the Over the Air (OTA) update to the Moto E (2nd Gen.) phones starting on Monday, February 29th or Tuesday, March 1st with the same staggered rollout process we have used for the other phones.  In the event that we do move to Tuesday, we will create a new thing called a Leap, Leap year, and reclaim the day to February 30th to make our end of February target date.

 

We’re getting close…

 

As always, stay WiFi my friends.

Hello again. We hope you had a great week.

 

We had a quiet week this week, with no surprises and good pick up on the ongoing MRs for G and X.

 

As always, here’s the full back catalog of past updates:


[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]
Updates in progress:

  • Moto G (1st Gen) Lollipop is fully available and over 93% of members have downloaded it.  We have reached the peak of installs for this update now.  There will always be some members who decide not to update, so as of today, we are removing this update from the report moving forward.
  • Moto X (1st Gen) EMR is at the same point as the Moto G MR, so as of today, we are removing this update from the report moving forward.
  • Moto X (1st Gen) Lollipop was at 85.6% this morning. That’s the big jump we were expecting.  Again, we’ll be sending out reminders to those who haven’t downloaded it yet starting this week. This, too, is peaking out, so we’ll take this one out of the report.

 

Remaining Updates to complete:

 

Moto E (1st Gen.) - We are starting QA shortly for this build and are looking to get the internal dogfood process started as soon as possible afte that. If there are no issues discovered, we will then start the SLATE and Lab entry process.  As we mentioned last week, we are still a few weeks away (but a week closer !)  from this being ready to go.  We will let you know a more concrete plan when we are through the QA process.

 

Moto E (2nd Gen.) -  No news is good news here.  SLATE testing started on Monday, and we are still following the plan of record from last week.
Current estimation dates for Moto E (2nd Gen.) are shown below:

  • If there are no issues discovered in SLATE, we will enter the lab on Monday, February 15th.
  • We’ll do a public soak test with a small number of our members immediately following, starting on Monday, February 22nd.
  • We’ll roll out the Over the Air (OTA) update to the Moto E (2nd Gen.) phones starting on Monday, February 29th with the same staggered rollout process we have used for the other phones. 

 

We are really pleased with the progress of the uptake on the X and the continued progress on the both versions of E. 

 

We will give you a progress report again next week.

 

As always, stay WiFi my friends.

 

Here’s the latest news on the MR updates.  MR’s continue to roll out for G and X, with E2 and E1 coming shortly.

 

As always, here’s the full back catalog of past updates:


[If the OS release process is new to you, please see this PWK blog post for some background on what goes into the OS release process.]


Updates in progress:

  • Moto G (1st Gen) Lollipop is fully available and 92.5% of members have downloaded it. A slight improvement over last week, and we’ll be sending out reminders to those who haven’t downloaded it yet starting this week.
  • Moto X (1st Gen) EMR is fully available and over 94% of members have downloaded it. This is a really awesome number to see.
  • Moto X (1st Gen) Lollipop was at 73% this morning. That’s the big jump we were expecting.  Again, we’ll be sending out reminders to those who haven’t downloaded it yet starting this week.

 

Remaining Updates to complete:

  • Moto E (1st Gen.) - We are still queued up to fully test this build.  We have received an updated  build and this is next in line to go through the full QA process.  When we have completed QA, we will go an internal dogfood (i.e use it ourselves) for a few weeks, and if there are no issues discovered, we will then start the SLATE and Lab entry process.  We are still a few weeks away from this being ready to go.  We will let you know a more concrete plan when we are through the QA process.

 

  • Moto E (2nd Gen.) -  We have been pushing very hard to get this build out, and have tried to compress the schedule (as we have communicated) to try and cut a couple of corners.  Unfortunately, when something goes wrong, that sets us back.  We discovered an issue late last week that resulted in us not being ready for lab entry this week.  The next available lab entry slot is February the 15th.  That actually gives us the time to do QA and SLATE in sequence, rather than in parallel, giving more breathing room to get any remaining issues ironed out.   We are doing everything in our power to avoid further delays.

 

Current estimation dates for Moto E (2nd Gen.) are shown below:

  • SLATE will officially start on Monday, February 8th, but if we can start earlier, we will.
  • If there are no issues discovered in SLATE, we will enter the lab on Monday, February 15th.
  • We’ll do a public soak test with a small number of our members immediately following, starting on Monday, February 22nd.
  • We’ll roll out the Over the Air (OTA) update to the Moto E (2nd Gen.) phones starting on Monday, February 29th with the same staggered rollout process we have used for the other phones.  We were targeting some time in February for this release, and the leap year may give us that one extra day we need.

 

This update isn’t as full of good news as previous ones, and we understand that this may be frustrating for some, but it is imperative that we get the quality of these releases where they need to be before we release them.

 

We will give you a progress report again next week.

 

As always, stay WiFi my friends.

 

Filter Blog

By date:
By tag: