Strava's one of the most popular tools for runners and cyclists to track their progress, and its usefulness can depend on its interoperability with existing platforms, like Fitbit, Apple Fitness, and Google Fit. Unfortunately, that last one had been presenting something of a problem, as Strava users found themselves unable to sync their fitness data with Google Fit.
Google may need a reminder on how reminders are supposed to work. Multiple users have complained about not being able to set reminders with Google search — it's a feature that has gone missing time and again over the past couple of years.
This week has been an exciting one for us Android geeks, what with the stable release of Pie and all. For some (including me), however, that enthusiasm for the latest version of our favorite mobile OS was a bit tempered. See, the update messed with our Gear devices (S2, S3, Icon X) and now they won't connect — though, some people are saying their stuff is fine. Thing is, this has been a known issue since at least Developer Preview 2 several months ago, but Samsung says it's working on a fix.
Judging by the Google Assistant help forums, Twitter, and Reddit, a whole lot of people are having trouble getting their phones to respond to voice commands. Twelve of the 20 top posts are complaining about the problem on several different device models and even in several languages. Google says it's on the case, though.
Around a week ago, BLU issued a broken software update for its Life One X2 phone. In at least some cases, users who applied the update were locked out of their phones. Late this afternoon, BLU's official Twitter account—which, much to the chagrin of affected users, was silent on the subject for almost a week—issued a statement that the problem had been fixed via a new update.
As infrequently as budget phones are updated, owners of low-cost phones should be glad their phone is continuing to receive support. However, a software update released on November 28th for the BLU Life One X2 has users less than thrilled. On first boot, the phone displays a new password screen—unfortunately, nobody has the password. Without a way to unlock the phone, users are resorting to factory resetting the phones with mixed results.
For some of us, breaking a smartphone is unimaginable. For others, it's only a matter of time. Either way, it could pay to have your ducks in a row. Samsung has introduced a new device replacement plan, and since no less than 107% of the world's phones were made by the manufacturer, a good number of people could benefit from this. But it won't come cheap.
Samsung's "Protection Plus Mobile Elite" plan costs $99.99 and provides coverage for two years. This price doesn't mean you get a replacement device as soon as yours breaks. Instead, you will have to pay a service fee each time you issue a claim.
It was only three months ago that Android got SEGA's latest entry in the obligatory kart racing genre, Sonic & SEGA All-Stars Racing. Now the sequel, which came out a year later on the consoles, has graced our platform only a day behind iOS. But don't reach for your wallets just yet: there are some serious issues with Sonic Racing Transformed that might mean it's not worth the $5 entry fee. I'll elaborate below.
Sonic Racing Transformed puts a few new ideas into the tired kart racing genre, with vehicles that change from cars to boats to planes at different sections of each track.
Update: The Verge has a response straight from the horse's mouth. It doesn't completely dismiss the idea of local content playback, but it doesn't exactly justify Google's disabling of the feature, either. Basically it's a "hurry up and wait" situation - we won't know exactly how Google intends to go forward until the developer preview for the SDK ends.
We’re excited to bring more content to Chromecast and would like to support all types of apps, including those for local content. It's still early days for the Google Cast SDK, which we just released in developer preview for early development and testing only.
CyanogenMod 10 is still cooking, and heck, CM9 isn't even fully baked for all devices yet. That hasn't stopped Steve Kondik, aka the guy who puts the Cyanogen in CyanogenMod, from posting preview builds of CM10 over on XDA for the AT&T and T-Mobile Galaxy S III variants. Plus, a third preview build being posted for the Sprint version by another developer. Keep in mind, of course, that "preview build" translates into "absolutely nothing is guaranteed to work." It is exciting, nonetheless.
The threads go out of their way to point out that CM10 isn't even close to being ready to ship and that just about everything that could go wrong probably will.