Android Archive

Samsung, LG announce new flagship phones

Both Samsung and LG announced their new flagship phones for the year, and lo and behold, there's actually something interesting to discuss. First, let's get the new Galaxy S7 and Galaxy S7 Edge out of the way: even though they look very similar to the S6 and S6 Edge, Samsung has brought back a few things that many here will like: water resistance, and a microSD card slot. In addition, Samsung has revolutionised the smartphone industry by making the S7 and S7 edge slightly thicker to fit a much, much bigger battery and to reduce the camera hump.

The new LG G5 is more interesting. The phone is, of course, kitted with all the latest processors and RAM and whatever, but at the bottom of the device, there's a slot that you can use to snap on all kinds of additional hardware.

Two of these new accessories plug directly into the LG G5's bottom. A small key on the side of the phone pops open its lower section, which can be pulled out along with the battery, then the battery is fitted into the next module and that straps back into the phone. The whole process sounds finicky, but there's nothing flimsy about the way LG has constructed either the phone, its battery, or the extras, so everything can be done quickly and forcefully. And yes, it really does feel like loading a fresh clip into your gun.

If this reminds you of Handspring's Springboard, you're not alone. As with virtually everything in mobile today - everything can be traced right back to Palm.

In any event, as much as I personally always like these kinds of experiments, the problem is that generally, nobody ever builds anything worthwhile for it. These expansion slots always tend to kind of fizzle out, with few actually, really good accessories to ever be released. Which, in turn, raises the question of why you would invest in it in the first pace.

That being said, let's give it a year or so and see what LG and possible third parties are going to do with this. I like the G5 overall, and the expansion slot is a fun and gutsy move (the fact that it is tells you a lot about the state of the industry, sadly).

As always, be careful with these phones if you care about running the latest Android: flagships or no, updates for these things will be messy.

Remix Mini wants your next PC to be Android

After initially thinking this would be great for people who want to do some of the stuff usually done on PC without the expense, now I'm not so sure who it suits. It fits only very simple work, ideally just in the browser or in Google apps; it's not enjoyable or smooth enough for leisure time use; for viewing content you'd be better off with a set-top box; and you can just plain forget playing games on it.

The Remix Mini has its appeals and uses only for pretty basic work. But as it is, here and now, it's not the post-Windows solution that some of us are looking for.

I applaud what Jide is trying to do, but at this point, with Google having openly stated they are working on bringing Android to the desktop, and giving it proper multi-window and all other features that come with it, I see little to no reason to invest too much into these products.

Google rolling out Marshmallow for Android Wear

Evidence has been mounting over the last few days and it looks like it's finally happening: Android 6.0 for Wear is starting to roll out. Googler Wayne Piekarski just announced on his Google+ feed that OTAs have begun and should continue over the next few weeks.

An official blog post by Google lists some of the new features we can expect in the new firmware, including: newly navigation gestures, audio support on speaker-equipped watches, and expanded support for messaging clients.

The update itself seems a bit 'eh', but the interesting thing here is that all Android Wear devices will be getting this update to Marshmallow, even the first generation Wear smartwatches.

Goes to show that Google does, in fact, know how to do this - now they just need to apply this to phones and tablets.

Google wants to take ‘Apple-like’ control over Nexus devices

Two very interesting articles about Android's future that are strongly related. First, Vlad Savov wonders why Android OEMs continue to make Android phones when there's little to no profit to be gained.

If there's no money in it, why would a company continue to be an Android OEM today? Ideally, every mobile OEM would like a bottom line that looks like Samsung's, but no others have achieved it. It's not even certain that Samsung Mobile will sustain its profitability, with industry analysts describing its present Herculean efforts as "running to stand still." So how do others bridge the cognitive dissonance between the desired outcome and the perpetual failure to achieve it?

It's no secret that Android OEMs are facing hard times, and since there are no alternatives people are willing to buy, they really don't have anywhere to go... Except exit the smartphone business.

Interestingly enough, that's where the second article, from Ars Technica, comes into play.

A report from The Information (subscription required) states that Google wants to take "greater control" over the design and building of Nexus phones. Currently, a Nexus device is a co-branded partnership between Google's Android team and an OEM, but this report says Google wants to move to a more "Apple-like" approach.

The report says that in the future, "hardware makers will be much more like order-takers, similar to the way contract manufacturers like Hon Hai (Foxconn) follow Apple's directions for producing the iPhone." Apple designs its phones, SoC, and other parts and then ships the plans off to third-party factories to have them built.

I'm sure Google is looking at the massive profits Apple is raking in with its iPhone, as well as the tight control Apple gets to exert over its hardware, and thinking to itself: why aren't we doing this? Looking at the complete failure of OEMs to properly update phones, I can't do anything but strongly applaud Google taking the Nexus program closer to its chest, and build true Google phones.

BlackBerry: “the future is really Android”

Speaking with The Economic Times of India, Damian Tay (Senior Director for Product Management, BlackBerry Asia Pacific) described the new Priv as "essentially our transition to Android ecosystem. As we secure Android, over a period of time, we would not have two platforms, and may have only Android as a platform . But for now, we have BB10 and Android platforms for our smartphones."

If those comments somehow left you in any doubts about the company's intentions, Tay continued: "The future is really Android. We went for Android essentially for its app ecosystem. In addition, all the enterprise solutions that we have been doing have been cross-platform for a long time now. So it's a natural progression towards Android."

Just in case you thought BB10 had a future.

Google tests installing Android apps straight from Google Search

But Google over the past year or so has gotten serious about getting more apps in front of more users, particularly in search results - which remains Google's bread and butter. App indexing - wherein Google actually sorts through the content of an app so it can present it back to users in any number of ways - is the key to all this. You can open a traditional web search result directly into an app. And later Google would show a button that take you to the Play Store to install the app.

And now Google has cut out the middleman - for some of us, at least - by skipping the step of opening the Google Play Store app before installing. Technically speaking, that's probably not a huge leap. And, frankly, it's not as big a deal as headlines are making it seem.

Installing applications is just one of the many things where Android outshines iOS. For instance, it's 2016, and you still can't install applications from the App Store web listing to your iPhone or iPad. I spend most of my computing time on my desktop computer, and I've lost count of how many times I came across an interesting iOS application, only to realise that the only way to actually install on my iPhone was to actually get my iPhone, which could be anywhere in the house, open the App Store, search for the application, hopefully actually find it (search in the App Store is dreadfully bad), and then install it, all the while hoping the App Store app won't soil its undies halfway through.

For Android applications, I just click install on the Play Store web listing, and I'm done. It's one of those niceties that companies that understand web services can do properly without much effort. And it seems like Google is taking all this a step further now, allowing you to install stuff straight from Google Search

Meanwhile, the iOS App Store application is so unreliable and terrible, it needs a hidden "tap ten times to reload" shortcut.

OK.

Dutch consumer group sues Samsung over Android updates

Well, this is interesting. The Dutch Consumentenbond, the largest consumer protection advocacy agency in The Netherlands, today filed a lawsuit against Samsung demanding the company starts properly updating its Android phones. The Consumentenbond had been in talks with Samsung about this issue for a while now, but no positive outcome was reached, and as such, they saw no other option but to file suit.

The Consumentenbond is demanding that Samsung provides two years of updates for all its Android devices, with the two-year period starting not at the date of market introduction of the device, but at the date of sale. This means that devices introduced one or even more years ago that are still being sold should still get two years' worth of updates starting today.

There's actually an official English version of the press release (as a translator, I am genuinely surprised about that).

Bart Combée, director of the Consumentenbond: "On buying a Samsung Android device, consumers are given inadequate information about how long they will continue to receive software updates. The Consumentenbond is demanding that Samsung provide its customers with clear and unambiguous information about this. Samsung moreover provides insufficient information about critical security vulnerabilities, such as Stagefright, in its Android phones. Finally, the Consumentenbond is demanding that Samsung actually provide its smartphones with updates."

The Consumentenbond's own research has shown that 82% of the Samsung phones sold in The Netherlands did not get updates to the most recent version of Android in the two-year period, which leads to all kinds of security issues and other problems. While Samsung, which has a smartphone market share in The Netherlands of about 80% (yeah... Sorry about that), is the focus of this particular lawsuit, the Consumentenbond notes that other manufacturers are guilty of the same problems.

It will not come as a surprise to any of you that I sincerely applaud this effort. The Android update clusterfrick is by far the biggest problem in the Android world, and OEMs should be, if possible, prosecuted to the fullest extent of the law for their negligent practices regarding updating their software. There is an extremely strong mandatory EU warranty policy on all products sold in the EU of at least two years, and Samsung and other Android OEMs are clearly failing to follow this law.

That being said, the minutiae of any possible outcome of this lawsuit are extremely crucial. Not only should Samsung and other OEMs be legally forced to release updates for their smartphones for at least two years (I would personally prefer three or four years, actually, but let's start somewhere), the updates ought to be timely. Every Android smartphone should be updated to the latest version of Android for two years after sale of said smartphone, with each update being released no later than four weeks after code availability from Google.

If this means they have to spend more resources on their development team - so be it. If this means they can no longer sell outdated, crappy hardware because newer Android versions would be too slow - so be it. If this means they have to work more closely with Google to prepare for new releases - so be it. None of that should be the concern of any consumer.

Sony’s Z5 Compact is coming to the US

If you long for the days of 2011, when 5.3-inch smartphones were enormous outliers rather than the norm, Sony has some news that may interest you: its flagship Xperia Z5 smartphone and its smaller-but-still-high-end sibling the Xperia Z5 Compact are coming to the US on February 7, 2016.

Sony smartphones are the only non-Nexus Android phones I'd even remotely consider buying. Even though they, too, suffer from the ridiculous update situation, they are at least trying to sell a nice, compact, high-end Android phone. In fact, I find it kind of remarkable that some version of the Z5 Compact isn't available in a Nexus configuration.

Remix OS 2.0 alpha released

The first alpha release of Remix OS 2.0 - which we talked about a few days ago - is now officially released. It's clearly an alpha, though, so don't try to use this on any important machines. I have been unable to get it to work - I just get "checking media fail" upon boot - but others are reporting it works, so I guess your mileage may vary.

That being said - I'd be a little weary of the EULA. It seems like it contains some regular Chinese boilerplate stuff (other Chinese companies are using the same boilerplate stuff, such as Xiaomi), which sounds incredibly heavy-handed to us. Not sure what to make of this just yet - maybe the company will clarify this one.

Cyanogen OS now serving Microsoft ads in its Android UI

Speaking of Cyanogen OS:

Following the Cyanogen OS 12.11 update for the OnePlus One, you may have noticed something worse than the automatic inclusion of Cortana. Now upon selecting a file without a set default application, you will see adverts for Microsoft apps and services on the "open with" menu.

I feel like a broken record player at this point, but don't trust these guys. Selling out to Microsoft has never done anyone any good.

Cyanogen OS update adds deeply integrated Microsoft Cortana

As promised, Cyanogen has released an update to Cyanogen OS (which is not CyanogenMod) that integrates Cortana into their Android offering.

In the Cyanogen OS 12.1.1 update, we are excited to introduce Microsoft Cortana. What makes this such an exciting partnership is that by having Cortana's voice command capability deeply integrated into the Cyanogen ecosystem, we're opening the door to future capabilities that don't currently exist.

So, they're going to "take Android away from Google", and then give it to Microsoft? This Microsoft?

OK.

Look - like Microsoft, Google collects data. A lot of it. We all know it, and at least all of us, OSNews readers, make a conscious choice to use Android anyway. While I don't trust Google in any way, there's at least the comfort that they are probably the most closely monitored company when it comes to privacy, and there's little to no risk of the company folding and being up for grabs - meaning, your data will remain within Google, and won't end up in somebody else's, less trustworthy hands just because they happened to buy Google.

Cyanogen Inc., however, is a whole different ballgame. This is a start-up funded by venture capitalists who are clearly looking for a quick buck. They're making a lot of grandiose claims and a ton of ruckus, and as I've said before, I give them a few years before they're acquired by someone else - at which point your data could end up anywhere, completely beyond your control, with little to no oversight.

Venture capitalists - and by extension, those who depend on them - have no interest in you. You are irrelevant. All they care about is cashing in on their investments as soon as possible, everything else be damned.

Don't buy into Cyanogen. Just don't.

Jide to release Remix OS 2.0: Android for PCs and Macs

Jide Technology has released Remix OS 2.0 as a free download available on January 12th designed to run on the majority of Intel and AMD devices such as PC and Mac. The company which was founded by three ex-Google employees has developed the OS thanks to a partnership with the Android-x86 project enabling it to run on almost any PC.

This is pretty much what Android on desktop and laptops - what Google itself is currently working on - is going to look like. It's designed first and foremost for Jide's own devices, but starting 12 January it'll also be available for select generic x86 devices, including some Macs. There's no proper up-to-date compatibility list as far as I can tell, so we'll have to wait and see just how useful it can be.

It looks quite interesting, and the fact that it's run by former Google employees gives some hope regarding its longevity and legitimacy. That being said, with Google itself working on bringing Android to desktops and laptops, you have to wonder how much longer Jide can maintain itself.

Google confirms Android N won’t use Oracle’s Java APIs

Google is replacing the Java application programming interfaces (APIs) in Android with OpenJDK, the open source version of Oracle's Java Development Kit (JDK). The news first came by a "mysterious Android codebase commit" from last month submitted to Hacker News. Google confirmed to VentureBeat that Android N will rely solely on OpenJDK, rather Android’s own version of the Java APIs.

"As an open-source platform, Android is built upon the collaboration of the open-source community," a Google spokesperson told VentureBeat. "In our upcoming release of Android, we plan to move Android’s Java language libraries to an OpenJDK-based approach, creating a common code base for developers to build apps and services. Google has long worked with and contributed to the OpenJDK community, and we look forward to making even more contributions to the OpenJDK project in the future."

If this is what it takes to get those Oracle slimebags off Android's back, so be it.

Android on the desktop

Android is the most popular mobile OS on the planet, and Google has brought the OS to cars, watches, and televisions. And, according to a report from The Wall Street Journal, Google will soon be bringing Android to yet another form factor: desktop and laptop computers. Re-architecting Android for a mouse and keyboard is going to require major changes to the smartphone operating system, but Android is actually much farther along that path today than most people realize.

It really is - but there's a definitive oddness about it, though. In any event, Google has already confirmed it's working on bringing multiwindow to Android, and if the company is really serious about putting Android on actual laptops and desktops, it's going to have to be more than just the kind of My First Multitasking Windows 8's Metro had (implemented 1:1 in iOS 9). It's going to have to be the real deal, with windows that can be moved around, resized, stacked, etc. - all the kinds of things you'd expect from any other desktop operating system.

I think the biggest problem they're going to run into is the black bar at the bottom of the screen, housing the back/home/windows button. Unless they can come up with a way to logically let the back button handle multiple activity stacks, I would suggest getting rid of the bar entirely, or just converting it into an all-out taskbar. They obviously can't have that black bar on 23" desktop displays or whatever.

Android 7 is going to be very interesting!

The Pixel C was probably never supposed to run Android

It appears that the Pixel C was planned as launch hardware for a new, all-touch version of Chrome OS which at some point got canceled - necessitating a switch to Android. The story is a lot more complicated than that, though. What follows is the best timeline we could piece together showing the Pixel C's troubled development history.

The launch of the Pixel C is baffling. Not only is it lacking features that Android needs to work well on the device, it's also got numerous bugs, indicating the Android port was done in a rush. I just don't understand why Google didn't just wait with this device until Android 6+1 with multiwindow was done. Now they've severely blemished their Pixel name.

Android Studio 2.0 preview: Android Emulator

An early preview of the new Android Emulator is now available to try out. As a part of Android Studio 2.0, the latest version of the Android Emulator can help you test your app on a wide range of screens size and configurations beyond the physical Android hardware you use to test.Moreover, using the official Android emulator enables you to test with latest Android versions.

Google claims this new version contains serious performance improvements - which were sorely, badly needed - and it sports a brand new interface.

Pixel C reviews: Android on tablets still sucks

Pixel C reviews are pouring in, and they're all virtually the same: pretty awesome hardware, but Android on tablets just isn't any good. The Verge:

But the performance issues, the lack of apps, and the lack of split-screen functionality show that, right now, Android isn’t really even trying to participate in that future. Simply put: the Pixel team has mostly delivered something really good, the Android team has not. Android may not be Google’s answer for the next generation of computing on a tablet. Maybe that will have to wait for whatever weird hybrid ChromeOS / Android thing that Google is supposedly working on.

Ars:

iOS and Windows are both much better suited to a larger form factor device. Maybe some day Google will implement that "experimental" multi-window mode, which will help. However, right now it's selling a $650 tablet/keyboard combo that can display a single app at a time. Even with a hypothetical split screen mode, you'd still have to deal with a sea of phone apps from developers that are reluctant to implement a large-format layout, in part because even Google doesn't take its own tablet platform seriously.

They're all right, of course. That being said, it's clear the Pixel C isn't really intended as a mass-market product - at least, not right now. No, the real purpose of the Pixel C is to serve as a development device for Google's Android developers, who are currently, by all accounts, working hard not only on combining Android and Chrome OS, but also on bringing more traditional functionality, such as multiwindow, to Android.

Android is movin' on up, and the Pixel C is nothing more than the ladder Google's Android developers need to get there.

HTC HD2 gets Marshmallow port

The HTC HD2 began its life unassumingly enough back in 2009 as a simple Windows Phone 6.5-powered smartphone. We highly doubt HTC knew of the legacy the phone would end up carrying. As most of you probably know, we're talking about how dev-friendly and dev-embraced the phone has been over the years, finding various ports of Unix, modern versions of Windows Phone up to 8, Firefox OS, and of course Android.

Over the years, the HTC HD2 has seen Android 2.1, Jelly Bean, KitKat, Lollipop, and now Android 6.0 Marshmallow.

The HD2 might be the greatest phone of all time.

The Nextbit Robin cloud phone is taking shape

The one thing that disappointed me about the Robin was the state of its software optimization. Nextbit hopes to ship out the first handsets to preorder customers and Kickstarter backers in late January, but it still has a long way to go until its software is up to the task. The Robin's current Android build is slow, in spite of the capable Snapdragon 808 processor within, and unfortunately buggy. The camera app, for example, is not yet functional, so there's nothing to judge one of the phone's key components on.

This phone would be a lot more interesting if they cut the cloud nonsense, and just focused on delivering this unique design as a high-quality, affordable pure Android phone.