Tag: IFTTT

The folks at HellomotoHK stumbled upon a mysterious batter cover for an alleged Motorola device, posting the image to their Facebook page for all to see. The image — which we’ve color corrected — shows black battery cover with kevlar-like material woven throughout. It’s not too unlike the back covers we’ve seen on the Motorola Droid line, currently exclusive to Verizon.

Although there appears to be 2 HTC One M8-style camera holes, we wouldn’t go that far in our assumptions. More than likely, the bottom hole will be used for the Motorola logo (which is absent on this battery cover), although we will admit it’s a bit strange to have a cutout for what is normally a printed logo.

Now, exactly which device this leaked battery cover belongs to is anyone’s guess. HellomotoHK lists off a few possible devices, naming the Motorola Moto X+1, a Google Play edition of the same phone, or some upcoming Motorola Droid 2014 device as likely candidates.

We hope this is only the beginning of a flood of leaks that will begin pouring out like we saw with last year’s Motorola Moto X.

from Phandroid http://ift.tt/1suM152

Ahead of their Q2 2014 earnings call, Google has issued an official press release for their Q2 earnings. Revenue is up 22% from last year, hitting a cool $15.96 billion.

Operating income came in at $4.26 billion (up from $3.47 billion the previous year), making for 27% of their revenue. When all is said and done, Google’s net income came in at $3.42 billion. For those curious about how Google did last quarter, they posted $15.4 revenue and $4.12 billion net (27% of revenue). That’s a nice 3% increase.

Google sites (Google owned properties like YouTube, Maps, etc.) accounted for $10.94 of their total revenue, a 23% increase from last year (partner sites accounted for $3.42 billion). Paid clicks saw a 25% increase from 2013, while cost-per-click dropped 6%.

Patrick Pichette, Google CFO Patrick Pichette said during the call:

“We are moving forward with great product momentum and are excited to continue providing amazing user experiences, with a view to the long term.”

Google also mentions they saw 300% increase in bringing traffic to businesses via smartphones and tablets and when it came to the Motorola team, they’re said to still hard at work, seeing “strong sales in emerging markets” with the wallet-friendly Motorola Moto E and Motorola Moto G.

from Phandroid http://ift.tt/1yygD6j

After the rumored NVIDIA Shield Tablet appeared in a Global Certification Forum database earlier this month, we were curious to see what NVIDIA had up their sleeves for the upcoming gaming tablet. Today, we may finally have our first look.

Rumored to usher in the NVIDIA Tegra K1 processor, there’s no question the tab would be able to handle Android’s current crop of high-end games. But how will the thing look? Well, @evleaks is once back again doing the honors, presenting an alleged press shot for the upcoming tablet. In the render, you’ll notice stereo front facing speakers housed in what could be an aluminum body. Other than that, well, there’s really not much else.

Evleaks mentions the tablet is due out sometime this year (2014), but no word on exact timing of release. It was only a year ago NVIDIA launched their Shield handheld to lackluster sales. We suppose now is a good time as any to introduce something new. We’re sure to learn more about the NVIDIA Shield Tablet as the weeks progress, so stay tuned.

[@evleaks]

from Phandroid http://ift.tt/1nQ03LL

A new update for Pressy has just arrived over at Google Play, tightening up something annoying bugs and bringing new features that users should be excited for. Let’s get the old out of the way first by seeing which bugs have been squashed:

• Fixed a bug where some Samsung users could not use the speaker-phone while Pressy was inserted.
• The earphones icon will no longer be displayed when Pressy is inserted (on all devices).
• Few issues with Bluetooth speakers and headphones are resolved.
• Fixed a bug where notifications volume was changed on some devices when Pressy was inserted.
• No email account found – users who get this error message during activation will now be able to input their email address manually.

The item listed in bold was a big annoyance for users since receiving their Pressy units so we’re glad to see it cleared up so fast. As for what’s new? You can score five new triggers to bring us to a total of 14. The 5 extra triggers will only be found within the “slow” mode so if you’re not fond of that then you’ll be limited to the original 9. Pressy exclaims that this is not because they want to be cruel, but due to a technical limitation. They’re the professional developers so we’ll definitely take their word for it.

You’ll also be able to assign a trigger to an app shortcut now instead of just apps, so if you want to be taken right to a folder, a specific page within the settings menu, or open a message to a specific contact you will finally be able to do all of that. It’s just another small piece that makes the entire puzzle look a lot better. If you’re lucky enough to have received your Pressy units already you can find the update waiting for you at the link below.

from Phandroid http://ift.tt/1mRQls5

We’ve already seen tons of great watch faces for Android Wear smart watches pop up in the Google Play Store, but Google says developers should hold their horses before going a bit too crazy. Wayne Piekarski revealed that the company is working to bring an official API that will make it easier for developers to create custom watch faces.

As it stands, he says apps have to be tweaked a great deal to make sure the watch faces act as behaved. That includes implementing ambient mode correctly, appropriately positioning status indicators and more. As such, when the latest API arrives there is a fear that current implementations might be broken or might not work as intended.

Google isn’t asking developers to stop making watch faces. Instead, they’re encouraging developers to keep their apps in “alpha” or “beta” status until the API is released and they can be be properly implemented. Otherwise developers might find themselves in a sea of complaints should users accept the platform update and find their favorite smart watches to be broken without apparent cause.

So when can we expect all this to happen? Piekarski said they’re planning to introduce the API once they migrate the Android Wear platform to Android L later this year, so we might still be a few months out from see anything. Develop on, we say, but make sure you keep an eye out for those new APIs as soon as they’re available.

from Phandroid http://ift.tt/1peOdZt