Tuesday, March 5, 2013

Android Authority

Android Authority

Google Play gift cards are now available in Tesco UK

Posted: 05 Mar 2013 02:29 AM PST

ukgiftcards

We learned yesterday that Google was planning to launch its Google Play gift cards in the UK very soon. Although the cards haven't been given an official coming out party yet, they have made their way to at least one retail store in the country.

To be more specific, the Play Store prepaid cards were spotted hanging out with their friends at Tesco by a Eurodroid tipster, who captured the outing on the picture below. We know that the gift cards will be available in £10, £25, and £50 denominations, but it looks like Tesco only has stocks for the £10 and £25 cards for now.

google-play-gift-cards-uk

If you happen to have some already, you can redeem the codes by going here. You won't be able to use them to make hardware and accessory purchases, though.

Excited about the arrival of Google Play gift cards in the UK? Planning to scoop some? Have you spotted them in other places? Let us know in the comments below.

The post Google Play gift cards are now available in Tesco UK appeared first on Android Authority.

Android 4.2.2 update for Verizon Galaxy Nexus leaks, official OTA definitely coming soon

Posted: 05 Mar 2013 02:21 AM PST

banner-galaxy-nexus-i515-pac-man-rom-121122

Although the Galaxy Nexus is almost one and a half year-old (how time flies, eh?), you would think that the 4.65-incher would always be one of the first to get updates to the latest versions of Android. You know, given the device is a Nexus and all.

And yet the LTE-enabled version on Verizon is still stuck on 4.1 Jelly Bean. With 4.2 being around ever since November 2012. Not cool, but what can you do?

Well, starting today, you can flash a leaked build of 4.2.2 that looks like the real thing. The ROM has apparently being pulled out straight from Google's servers, so an official 4.2 bump is definitely in the final testing stages and around the corner for an OTA rollout.

Then again, ain't nobody got time to wait for Verizon (or Samsung) to make the thing officially available, right? In which case, here's the direct link to download build JDQ39 and bring your flavor of Android up from 4.1.1 to 4.2.2.

android-422-galaxy-nexus

You probably know the drill by now, but just in case you don't here’s the skinny. First off, the firmware is to be installed only on devices running stock software. The ROM can't be flashed over another custom ROM, so don't even try that.

Also, you're going to need a custom recovery tool. From there on, it's smooth sailing for anyone with a basic knowledge of these things, but if you need additional help here are the step by step instructions for both rooted and non-rooted devices.

A couple of final warnings and we'll wrap it up. Although everything points at the leaked ROM being the real deal, it can still be buggy or laggy. After all, there’s a reason why Verizon and Samsung are still delaying making it official.

Also, remember that any kind of unofficial software tweaking will void your warranty, so if you care about those things you might want to wait it out a while longer. Now go and have fun, you crazy kids!

The post Android 4.2.2 update for Verizon Galaxy Nexus leaks, official OTA definitely coming soon appeared first on Android Authority.

Opera pushes a beta of their WebKit powered browser to the Google Play Store

Posted: 05 Mar 2013 02:17 AM PST

The headline above is going to confuse a lot of you without some backstory, so here’s what you should know: Opera has been making web browsers for as long as we can remember. They’ve always used their own browsing engines, and in 2003 they launched “Presto”. It’s an engine that’s served them well, but today’s world is dominated by WebKit. WebKit is the name of the open source rendering engine that Apple uses for Safari, that Google uses for Chrome, that Nokia used over half a decade ago in Symbian, and what RIM’s using in the latest version of their BlackBerry platform.

In other words, if you’re not using WebKit, you’re just plain weird.

Last month, about a week or two before Mobile World Congress, Opera said that they’re going to switch to WebKit and throw Presto out the window. The internet got pissed, saying that we need competition to exist, and blah, blah, blah. We don’t know why people would be so upset with the idea of a company as talented as Opera contributing to an open source project that benefits everyone.

Anyway, all that brings us to today’s news. Today Opera published a beta version of their web browser for Android. You can grab it from the Google Play Store right now. It looks different, it has an improved “Speed Dial”, which is Opera’s version of homepage bookmarks, and there are a ton of other small tweaks in there as well.

Should you check it out? Absolutely, but we wouldn’t be surprised if you decided to go back to Chrome, or Dolphin, or whatever you prefer. We’ll definitly take Opera’s browser a bit more seriously once it’s out of beta, but we know some of you like to live on the bleeding edge.

The post Opera pushes a beta of their WebKit powered browser to the Google Play Store appeared first on Android Authority.

LG Optimus F5 to arrive on Verizon as the Lucid 2

Posted: 05 Mar 2013 12:21 AM PST

LG Optimus F5 2 aa 600 1

Having been made official a few days before the start of MWC 2013, we were determined to get to know the LG Optimus F5, the company's latest mid-range smartphone, a little better in Barcelona last week. The result, as you may already have enjoyed, was our Optimus F5 hands-on video.

For those who are wondering about the Optimus F5's availability in America, we're hearing that the phone will arrive stateside via Verizon Wireless.

LG-Lucid-2-Verizon

According to Unwired View, the F5 has been tapped by Big Red to replace the aging LG Lucid 4G on its Android lineup. Aside from being stamped with the usual Verizon logo, the phone will also get a name makeover, as it'll be known as the Lucid 2 instead.

Specs-wise, you won't find anything too awe-inspiring, but the Lucid 2 offers some improvements over the predecessor, starting with its bigger 4.3-inch qHD display. The rest of the specs include a 1.2GHz dual-core processor, 1GB of RAM, 8GB internal storage with microSD support, 5MP main camera, 1.3MP front cam, 4G LTE, NFC, 2,150mAh battery, and Android 4.1.2 Jelly Bean.

Expect the LG Lucid 2 aka Optimus F5 to hit Verizon stores in the coming months.

The post LG Optimus F5 to arrive on Verizon as the Lucid 2 appeared first on Android Authority.

Embarrassing: LG clones Samsung’s Flip Covers, rebrands them as Quick Covers

Posted: 04 Mar 2013 09:47 PM PST

Whenever LG announces something, anything, we have to throw the story around the office like a hot potato because none of us want to write about yet another widget that LG copied from Samsung. Today’s newest doohickey: Quick Covers. They’re cases for LG’s new Optimus G Pro that function exactly like Samsung’s Flip Covers, the ones that have been shipping since … we can’t remember because it feels like they’ve always been out.

Is LG ever going to stop copying Samsung? We certainly hope so. Several of you give us flack for making fun of LG, that them existing is a healthy for the Android ecosystem. We don’t exactly agree with that. What’s so healthy about introducing subpar products to market when there are better gizmos available? There’s a reason why HTC fanbois exist, because they’re passionate about HTC’s products. The same can be said about Samsung. But LG? No one uses an LG phone because they bought it with their own money, chances are they got it as a gift or free on contract from their operator.

But let’s get back to these Quick Covers for a second. Samsung likes to offer their Flip Covers in white, black, baby blue, lime, orange, pink, and maybe one other color, this writer’s memory isn’t that good. LG will offer the exact same colors, including a purple hue!

That’s innovation people. Purple.

How much will these covers cost and when will they hit the market? They’ll be in South Korea “soon” for between $36 and $40. That’s not terribly unreasonable, especially considering that they replace the back of the device, which is again, exactly how a Samsung Flip Cover works.

The post Embarrassing: LG clones Samsung’s Flip Covers, rebrands them as Quick Covers appeared first on Android Authority.

Mobiroo: What if you could pay $5 and download as many apps as you wanted?

Posted: 04 Mar 2013 09:23 PM PST

There’s a company out in Canada that wants to take a business model we’re all familiar with, monthly subscriptions, and bring it to the relatively young market of third party applications. It’s called Mobiroo, and here’s how it works: You sign up for the service, which is $2.49 per month for a limited time, normally it’s $5, and then you can download as many applications from their app store as you want. According to the official press release, some apps in the store cost as much as $20, so you’re actually saving quite a bit of money.

What types of apps are in the Mobiroo store? We don’t really know. They say that there are some EA games in there, as well as apps from publishers such as Herocraft, Vector Unit, GameHouse. There’s also a free seven day trial which we need to investigate at some point later today.

Will this take off? That’s incredibly hard to say. Everyone knows what happens when you buy a new phone. You spend the next few days hunting for apps, you find the ones you like, and then that’s it, you stop consuming. Sure, you might hear about a game from a friend or on a tech site like this one, but you don’t spend time just scrolling through new apps like you once did.

We’re extremly curious to see how Mobiroo pans out. Subscription music is one thing, we’re all huge fans of Spotify here at Android Authority, and subscription movies are obviously a win, we can’t tell you how much we all love Netflix, but subscription apps? It’s one of those concepts that sounds good on paper, but in the real world it’s just … strange.

The post Mobiroo: What if you could pay $5 and download as many apps as you wanted? appeared first on Android Authority.

Amazon’s new ad API aims to hit Google where it hurts, but will it take off?

Posted: 04 Mar 2013 08:41 PM PST

Google is an innovate company, no one is denying that, but many people don’t understand how they many money. Everything Google does comes back to advertising. Android was created so that phones with web browsers could become cheap. Gmail was created so Google could serve you ads based on what you were talking about with your friends. Google Maps was created so Google could offer you ads for nearby restaurants and bars.

The list just goes on an on.

Samsung creating a new operating system doesn’t register on Google’s radar. Neither does Windows Phone or Microsoft’s Surface tablet. But when a company tries to enter the ad game, that’s when the proverbial shit hits the fan.

This brings us to today’s news: Amazon is introducing an ad API that anyone making Android applications can use. That means developers who are currently relying on AdSense to make money now have another choice, and that choice is the largest retailer in the United States.

Will Amazon’s ad API take off? It’s really early days, and we haven’t even seen it in action yet, but here’s one thing that needs to be pointed out: Amazon is a household brand in the USA, but in other countries they might as well not even exist. Amazon will obviously try to address that over the coming years, but even then, if you’re a developer in Germany who’s trying to make a game that’ll appeal to people in America, you’re going to think about going with Amazon’s ads instead of Google’s ads, right?

As soon as we know more, we’ll let you know. Also, let’s not forget about all those Amazon phone rumors that cropped up in 2012. Maybe we’ll finally see the device in 2013?

You never know.

The post Amazon’s new ad API aims to hit Google where it hurts, but will it take off? appeared first on Android Authority.

IDC: This year will be the first year that smartphones outsell feature phones

Posted: 04 Mar 2013 08:20 PM PST

The bean counters at IDC have just published a prediction that we’re not going to dispute: Smartphones are going to outsell feature phones in 2013. They say that 50.1% of the mobile phones sold this year will run some sort of smart operating system, and that by 2017 that number will hit 66%.

What’s responsible for this shift? It doesn’t take a rocket scientist to figure it out. Smartphones used to be painfully expensive devices that were only sold in Western markets where operators offered subsidies. But gradually, thanks to the relentless pace of technological innovation, people today can buy a device with the same specifications as the Nexus One for less than $200. You could probably find a single core 1 GHz Android phone with a 5 megapixel camera for even less than that actually.

Which country is the biggest consumer of smartphones? Again, easy answer: China. There are more people living in China than there are in Europe and the United States combined. Many of those people starting to climb up the socioeconomic ladder, and they can now afford a smartphone, whereas before it was just a flight of fancy.

In the number two spot is America, but it’s nowhere near China. IDC says China will buy over 301 million smartphones this year. America on the other hand, “just” 137.5 million. Granted, many of the devices that will be sold in America will be subsidized superphones, whereas in China they’ll be sub $200 smartphones from local players, but still, a smartphone is a smartphone.

What operating system is going to power a majority of these smartphones? Android, of course, but you already knew that. People cry about Android fragmentation all the time, but it’s because of fragmentation that $99 Android smartphones exist in emerging economies.

Should Google be scared of a so called “cheap” iPhone? We’ll just have to wait and see.

The post IDC: This year will be the first year that smartphones outsell feature phones appeared first on Android Authority.

Here are the first two legitimate renders of what the Samsung GS4 will look like

Posted: 04 Mar 2013 06:36 PM PST

The man or woman behind the Twitter account @evleaks just dropped two huge bombshells on us. They’ve published two renders of the upcoming Samsung Galaxy S4. Should you trust @evleaks? We do. We can’t count the number of times that they’ve published accurate information. In fact, we’re not even sure if @evleaks has ever said anything that was incorrect.

But enough about that, let’s discuss the renders. The device looks more square than the GS3. We’d go so far as to say that it even looks a bit like the original 5.3 inch Galaxy Note. The bezels are insanely thin, which we like, and there appears to be no front facing buttons.

If true, that would be amazing, since that’s the number one complaint we have about Samsung hardware. That and cheap plastic that flexes far too easily.

Looking at the top, the hole for the front facing camera looks massive. Earlier today we filed a report that said the GS4 would include a feature that tracked a user’s eyes while they were reading a web page. When the user reaches the end of the last paragraph, the device scrolls automatically for them. Having an advanced front facing camera is needed for that. Let’s also not forget about all the wide angle stuff HTC has been doing with their front facing cameras. Perhaps this is Samsung taking a lesson from their enemy in Taiwan.

We’re 100% sure that more leaks are going to take place between now and the 14th, when Samsung officially announces the GS4. You’re either going to love the leaks or hate them. This writer falls into the latter camp, but at the same time he also understands that most people love this sort of stuff.

That’s life.

The post Here are the first two legitimate renders of what the Samsung GS4 will look like appeared first on Android Authority.

Android and Chrome OS: what does it all mean?

Posted: 04 Mar 2013 05:57 PM PST

chrome

We've all seen the Android statue, placed above the entrance to the building on Google's campus in which Chrome is developed and maintained. The speculation ran rampant, and still does. Is Android going to destroy Chrome? There is a line of code present in Chrome that mentions Android, lending credence to the panic. Google is saying nothing, as usual, so we're still left to wonder why that statue is there, and what (if anything) it means.

 Is Android coming to Chrome OS?

The natural assumption is that Android and Chrome OS are merging, or that Chrome OS will get Android somehow woven into it. When the statue emerged, we were pretty sure there was going to be some kind of Android inside of Chrome OS. Some cheered, many jeered. Do we need that? Do we want that? The Chrome faithful thought it to be a slight against their OS, while Android fans were just confused as to why Google would do that.

To some, it seemed a concession that Chrome OS was less-than, and needed Android to survive. Chrome OS is severely lacking in apps, which means it simply doesn't have the functionality it should. Being based on the web has a downside, and that's a major one. Was Google making a simple fix for the app situation by baking Android in?

chrome-beta-for-android-header

Would Android help Chrome OS?

They may both be Google services, and share some traits, but Chrome OS and Android are very different. Take a similar function, like Google Drive: Chrome has the full-fledged version, while Android has an app. A great mobile app, but nowhere near the functionality of the desktop version. Without more functionality, it’s hard to be truly productive.

There are apps for Android, like Quickoffice, that really are better suited for Chrome, yet Chrome OS goes wanting (for now). We wondered if somehow implementing Android was a quick way to add a bunch of functionality and appeal to Chrome. It makes immediate sense, but on closer review… that may not work, or even be smart.

SamsungChromebook21_large_verge_medium_landscape

Why Android makes sense to Chrome OS

The Chromebook Pixel is meant to pave the way for Chrome OS, and a large part of that is the touchscreen. While the touchscreen on the Pixel is really cool, it has a long way to go. So far, we can press some buttons, or scroll through pictures as in Android, but not nearly the gamut of function we would like. We can't pinch to zoom on every page, which is the immediate desire when looking at something small. All that functionality is available in Android, which is probably why we want it on the Pixel.

To our minds, a touchscreen is a touchscreen. We neither want or care to differentiate between platforms or devices. If I can do something on my phone or tablet, I want to be able to do it on the desktop. The mind wants what it wants, and it doesn't want to think critically about can and can not before taking action. The touch interaction is the most glaring benefit of Android to Chrome, and it just makes more sense to take some really good functionality and implement it rather than build your own.

new-google-chrome-logo

Is Chrome coming to Android?

Here is where it gets tricky. If Android isn't coming to Chrome, are we getting it the other way around? Why does Chrome have a mobile browser, and an additional Chrome beta browser? It's pretty clear the Chrome team is up to something, but exactly what that is remains a mystery.

Chrome beta… again

The Chrome browser you have for Android isn't all that old, nor out of beta for very long. It was put through its paces, then released to the wild. Chrome has now been cloned into a new beta, which does some different stuff. It has full-screen functionality, which is pretty awesome, especially on a tablet.

So, why do we need a beta on top of the stable Android version? When released, the beta version of Chrome for Android was version 25, same as the desktop Chrome variant. The stable Android version of Chrome was release 18. Google would like to have both Chrome variants updated on the same 6-week cycle, so this move would satisfy that. Both versions of Chrome for Android are now on the same update, but the beta is still being toyed with.

The same version of Chrome solves an update issue (a small concession, really), but it has much more implication than that. The same iteration of Chrome, updating at the same time, with the same functionality sounds more like Google wants a single Chrome browser than it does anything else. We'd all love a true cross platform browser, so this is a great move by Google… but is it just another sneaky way for Google to get us to do their beta testing?

chrome-os-tablet-mockup

 

Chrome OS on mobile devices

There are a few other platforms which utilize web apps rather than native apps in Firefox and Ubuntu. Those are two platforms that, while lacking in comparison to Google and Chrome, will have a cross platform presence. Web apps may be a bit cumbersome right now, but the usability on all devices is convenient and welcome. It also makes Chrome OS on mobile a much more salient option, and perhaps one that suits a larger need. Google has admitted to Chrome OS coming to mobile, but nothing has come to light.

Let's ponder a company with employees on the go. They're in the office about 50% of the time, and the rest of the week they're out in the field. If those employees could tote a tablet around, rather than a Computer or even a Chromebook, it makes a bit of sense. If your needs don't require a full-fledged computer while out of the office, Chrome OS for mobile is a great option. An office full of Chromeboxes, and a staff armed with tablets. This makes apps like docusign much more useful for Chrome OS, where an e-signature is required.

Pinching a bit of project butter or the Android keyboard into Chrome OS makes the platform much more viable for a greater cause, which is enterprise. The more arrows Google has in their quiver, the more companies will begin to see the benefit of their services. With Google's recent acquisition of Quickoffice, enterprise seems to be the new battleground… and Google is serious about controlling it.

Google Chrome

Where is it?

Just what is going on with Chrome Os for mobile? Nobody has a clear answer. We can, however, follow the breadcrumbs. Those breadcrumbs lead us to a trail, and it also answers a few questions about development of Chrome OS and how it relates to mobile.

First, development. Web apps are harder to develop for touch, and the industry standard keep shifting. This may be why the push for HTML5 has been so widespread, and the shift so sudden. It seemed that, overnight, companies were willingly dumping languages like Java for HTML. Let's forget the security implications for a minute and consider just how radical a shift this was, and is. Apple paved the way, but everyone following suit so quickly thereafter is telling.

Now for the breadcrumbs. Google announced a Chrome OS for mobile in 2011, and went on to say there would be tablets running the it. When the Pixel was released, the story was that it was two years in the making. In 2011, we had Chrome OS for mobile being developed, which is primarily a touch-based platform. We now have a Chrome OS machine.. touchscreen and all… meant for developers. It's all coming together, now.

chrome-bugdroid-google-campus-1

Conclusion

Android has a lot of functionality to offer Chrome OS, especially if that platform really is coming to mobile. If we take a look at the evidence, it seems as though Android functionality is being folded into Chrome because of Google's desire to take that platform mobile. We may not get full Android within Chrome, but the functionality is welcome. Apps and widgets would be cool, but the core functionality is of more consequence to Chrome OS.

What does this mean for Android? Nothing… yet. Right now, Android is at the top of the food chain, and taking up more of the market share all the time. Is it wise to have two platforms? Google seems to be doing well with it, just as Apple is. Shared functionality is one thing, a copycat platform is another. Then again, if Linus Upson, Google’s Vice President of Engineering, was right, Android may be counting the days to retirement. Look at the picture above and tell me… does that look like a wave hello, or goodbye?

The post Android and Chrome OS: what does it all mean? appeared first on Android Authority.
Posted by at 4:33 PM

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)