It was just last week that the Google Glass team started pushing out eagerly awaited update to XE16. It was followed less than 24 hours later by a silent hotfix dubbed XRE15C. Unfortunately, these updates left many Glass owners with complaints about stability and an even shorter battery life than the device was already known for. Yesterday, in a bid to resolve some of these issues, the team began rolling out a new update to XE16.1. There still hasn't been an announcement or changelog regarding the new firmware, but several users have already identified a pretty severe problem: it's sending their devices into perpetual boot loops, leaving them effectively soft bricked.

2014-04-23 18.44.47

Word of the bad behavior quickly spread through the Glass Explorers Community Forum, prompting the developer team to halt distribution of the update to investigate the issue. While the bug is not affecting all units, it is fairly widespread among those that have received the update. Note, this is a silent update, so it likely would have been installed without prompting users.

Hi, I'm the Software Lead for Glass. I've been reading your reports of Glass not working correctly after updating to XE 16.1. While this problem only affects a subset of Explorers, as soon as we saw the reports, we immediately paused the update so we could investigate and fix the issue.

Some of you were affected before we stopped the update, and the team and I are very sorry for the inconvenience. We're on it and working on a solution.

About 2 hours later, a follow-up post acknowledged that the issue has been discovered and a new fix was in progress. Unfortunately, users with devices already trapped in a boot loop will have to work with Glass support to restore normal functionality.

Hi everyone, we've identified the cause of the problem and we're currently working to patch XE16.1 to fix this issue. For people whose devices are "stuck" and won't load, we need to work with you individually to repair your Glass. We'll be reaching out to those who posted about this issue, but if we miss you, please feel free to get in touch with us directly as well.

In the meantime, Glass owners that have already received the update to XE 16.1 (build XRV16) but haven't yet suffered from boot loops might want to keep the unit charged and avoid restarting until a fix is distributed. And for those that haven't received the update, you can probably breathe a sigh of relief for dodging this bullet.

Update: It looks like the fix is starting to roll out already. Version XE 16.11 (build XRV22) is on the way! This should prevent the issue from occurring for anybody who isn't already experiencing boot loops.

Source: Glass Explorer Community (private)

Cody Toombs
Cody is a Software Engineer and Writer with a mildly overwhelming obsession with smartphones and the mobile world. If he’s been pulled away from the computer for any length of time, you might find him talking about cocktails and movies, sometimes resulting in the consumption of both.

  • darkdude1

    I like Google's response to this problem, at least they were honest and up-front about this. And yes, I'd probably be annoyed to, but it's beta for a reason, it's to be expected.

    • https://plus.google.com/+MichaelBond codemonkey85

      I agree completely, but this is still going to reflect poorly, since the device costs $1500 and is already fighting for consumer acceptance.

      • IamTheFij

        I think everyone who has it knows it's bleeding edge. As long as they fix it, it's fine in my book.

        • https://plus.google.com/+MichaelBond codemonkey85

          The key phrase being "everyone who has it". My concerns mostly revolve around the public at large. (But I'm still okay with the beta nature of the thing too.)

          • IamTheFij

            Oh I see what you mean. Eh, I don't think the public at large really pays attention to these sorts of things. Most are like "talk to me when it's less expensive" and they don't read any news about it until someone they know who is a "techie" tells them something or they see it on TV. :)

        • Crispin Swickard

          Other than the 2, and a half year old electronics that power it. ;)

          • IamTheFij

            True! *mumble mumble*low power consumption*mumble mumble*

            But really, it's a single purpose device. My Glassware is mostly "in the cloud" and that's really the primary design pattern. Even my native GDK glassware is really just pinging a web service and pulling information. CPU isn't really holding me up anywhere.

            That is not to say it's not holding back other devs with other ideas though.

          • Crispin Swickard

            True the hardware may be powerful enough to run things fine especially at the resolution it displays, but there is much more power efficient hardware available, and becoming available. When they had made slight change in the design I was suspecting some internal changes, but not so much. Performance shouldn't be an issue, but there would be all the other benefits of newer hardware.

  • mustbepbs

    Beta products, by Google.

    Please pay us $1500 now.

  • melhiore

    Google needs to fix the price of this thing. I do not care if anyone is so called explorer or not, price is just wrong, full stop.

    • Good_Ole_Pinocchio

      You can't be "wrong" in pricing when it's specifically for developers. Esentially they're paying for early access. This price means nothing since it's not a consumer price.

      • IamTheFij

        It's not specifically for developers. I think they happen to be a lot of the early adopters, but if you look at the forums, it's not the target.

        They are looking for use cases. The only way to get use cases is to have a lot of different people use them. The price could be explained by the small volume and limits on supply chain.

    • yo

      if you can get away with it wouldn't you?

  • Mayoo

    At first I read "Google Hats" and I wasn't even shocked.

  • veRdiKt

    I was in a conference right after I updated my Glass. Started tweaking the hell out while I was giving a presentation.

  • jhawkkw

    I seemed to have gotten the 16.1 update this afternoon and dodged the bullet since it still seems to be working on that version.

  • Gerrobe

    My Glass just updated from 16 to 16.11, and is now stuck in a boot loop. Anyone else seeing something similar?