EU Plans to Fine Google for Anti-Competitive Android Practices

The road in Europe is looking to become rockier for Google and Alphabet, as the antitrust proceedings against the company in the European Union are looking to culminate with a hefty fine and some drastic changes.

As per a new report published by Reuters, EU's antitrust regulators are planning to order Google to stop offering financial incentives to smartphone makers to pre-install Google Search exclusively. This order is a result of the investigation against the search giant where it was accused to using Android and its dominance to shut out rivals, thus creating an anti-competitive environment.

The regulators plan to order Google to "halt payments or discounts" to OEMs given to pre-install Play Store along with Google Search. They also want to prevent the pre-installation of proprietary apps as well, if it restricts the ability to use competing OSs based on Android. The report mentions that Google "cannot punish or threaten" companies for not complying with its conditions.

In addition to all of this, EU also plans to levy a large fine because the anti-competitive practices are still ongoing from the time they went into effect in January 2011. The level of the fine would be "sufficient to ensure deterrence". The penalty could be based on European AdWords revenue, Google Search product queries, Play Store app purchases and AdMob's in-app advertisements.

These fines and orders are related to the anti-competitive nature of Android preloaded with the Play Store. There is one more investigation underway for the Search end of things, where Google is accused of favoring its own sopping service over those of its rivals. This could in turn be a separate fine, but the decision for this would be decided at a later stage.

All in all, the next few months could impact Google and Alphabet right in the pocket. The antitrust order also has the potential to change the Android landscape as Google would be forced to let off its aggressive hold on Android and loosen its stance on derivative forks. Companies like Samsung would then be open to test out Google Play Store-less routes like Amazon did with its Fire lineup of phones and tablets, without giving up the freedom to also continue with providing Android with the Play Store.

What are your thoughts on these purported fine and orders? Do you think Google deserves a fine for their anti-competitive practices? Let us know in the comments below!

from xda-developers http://ift.tt/2dgsFlf
via IFTTT

The OnePlus 3 and Axon 7 Show Affordable Phones Don’t Have to Come at the Cost of Software Updates

In the past, purchasing a "mid-range phone" meant a plethora of compromises: weak after-sales support, few and far between updates, and compromised feature sets (and, more often than not, an ugly user interface). OnePlus devices, too, had questionable software and update support.

The OnePlus 2 took ages to get a proper marshmallow update. The OnePlus X still doesn't have one one. However, things seem to be changing for the better as thus far with the OnePlus 3, the situation has vastly improved. In fact, while writing this article OnePlus sent out another OTA to version 3.2.7. Heading over to their official site, there are 9 software versions available for the 3. Some of these are community builds – essentially  refined betas – but the experience of installing them is pretty straight forward, and they do build upon previous versions with optimizations and great features (such as the increasingly-popular scrolling screenshot) that enhance the UX without taking away from what makes it pleasant. We've had our worries regarding the merging of the Hydrogen and Oxygen OS platforms through a unified development team, but OnePlus was quick to listen to criticism and ease concerns by announcing Oxygen OS would keep a Stock Android look in its System UI.

OnePlus 3 Update Screen

My most recent experience with updating my OnePlus 3 truly impressed. My device was on OxygenOS 3.2.4 rooted, with Xposed installed, a custom DPI, and TWRP as the recovery — if you are used to these features, you know how they can often complicate updates. However, OxygenOS detected my device was rooted and downloaded the full version of 3.2.6, rather than just the OTA. My OnePlus 3 then rebooted into TWRP and updated to 3.2.6 with no data loss, no hiccups, no booting issues. This process did replace TWRP with the standard OnePlus recovery, but it's rather simple to get back to TWRP anyway.

These frequent updates to the OnePlus 3 have added key features that the community asked for from day one such as RGB mode, but also the aforementioned  scrolling screenshots, improved auto-brightness, updated 4K recording codecs (as we pointed in our OnePlus 3 review, they were a mess around the time of launch!), and improved RAM management (which, again, is something we determined to be pretty bad early on). The OnePlus 3 is also up to date with the September 1st security patches, and all of this makes for a device that has improved every few weeks in tangible ways. We aren't sure if the merging of both ROM teams has already begun or if this continuous support is a product of that, but it's terrific to see this effort either way, and OnePlus has so far redeemed its poor reputation on this front with this product cycle.

One of the OnePlus 3's biggest competitors has to be the ZTE Axon 7, which actually carries some higher specifications in some areas, while still being in the same bracket. Thus far, after purchase support and updates have also been impressive as well.

Axon 7 Update Screen

The Axon 7 just received an update to version B27, and this is the third update my Axon 7 has received since launch. The phone's only been out for a few months and we've already have seem updates help with UI tweaks, battery life improvements, camera enhancements, and the latest September 1st security patches. ZTE has been communicative and responsive on their official forums regarding updates and features additions, too, which is always a plus.

Of note to our audience here at XDA is that ZTE has also come up with a method of unlocking the bootloader. There are some caveats such as losing the warranty, but the having the option is great and ZTE should be commended for at least giving us the option (albeit the OnePlus 3 is certainly much better in its warranty policy for us tinkerers). More manufacturers providing this option is good for the community, but we would really like to see this not come at the cost of losing the warranty.

Overall, both of these devices offer terrific hardware packages and incredible value for the money. There was a time when a $400 device would also come with a cost of reduced software support, infrequent updates, or drastically-reduced features (quantity or execution). The OnePlus 3 and the Axon 7 both seem to be defying this trend and, in turn, changing our expectations. Both of these devices right now have the latest security patches and both are running 6.0.1, and we have no issues recommending either device based on support thus far. It's especially reassuring to know that these companies have improved their communication channels with their respective communities, and are throwing us enthusiasts a bone or two by allowing us to tinker and customize.

Both devices should also get Android Nougat in due time, with the recent OnePlus Software AMA giving us some vague hints regarding its development. In any case, the openness of the OnePlus 3 means you can already try out Nougat on the device. Features like Dash Charging are also now available on custom ROMs, and OnePlus has also stated that they plan on finding ways to improve the camera quality on custom ROMs too, so the custom ROM experience is bound to only get better on this device. But if you don't want to go that route, OnePlus' official support is better than ever with promising prospects (assuming they keep their word), with more than just promises: tangible results in the form of feature-packed updates, and internal changes to accommodate for a new software model for faster updates. Devices like the OnePlus 3 and the Axon 7 are so far squashing the notion that more affordable devices come at the cost of software support, another item in the long list of preconceptions that these "flagship-killers" challenge when it comes to their price. At a time where updates are some of the biggest headaches in the Android world for a multitude of reasons, we couldn't be happier about that.

How important is software support to you? Share your opinion below!

 

from xda-developers http://ift.tt/2cTBkab
via IFTTT

MechDome is a Developer Tool that Automatically Converts Android Apps into iOS and OSX Apps

Cross-platform development has presented a major challenge for most independent developers for many years. Quite often, it's simply too much of an time and resource investment to learn a new programming language in order to port your app over to another platform.

For years, this fact of resource allocation is what has pushed many developers to primarily focus their efforts on iOS, due to the more lucrative market. Thanks to projects such as Xamarin, however, developers who are familiar with C# have been able to push their projects across iOS, Android, and Windows Mobile. But Android developers are most familiar with writing in Java, so using Xamarin would require a developer to familiarize themselves with a new language and build platform. We've covered one project aimed at bridging the gap between mobile operating systems by providing a cross-development platform for Java developers – Intel's Multi-OS Engine – but there's no telling where that project is headed. That's where MechDome comes in.

MechDome is a start-up company based in California and incorporated in January that has developed a conversion tool to automatically create native iOS and OS X apps from your Android app. No need to learn how to use a new IDE or API. All you need to do is send an APK file to MechDome (no need to send them your source code), and the fully automated tool will compile a standalone binary in seconds for iOS and OS X that the developer can then distribute on Apple's App Store. We sat down in an interview with MechDome's founder and CEO, Mario Kosmiskas, to see a demonstration of the tool in action – and it works. Although there are some limitations due to fundamental differences between how iOS and Android operate (which we'll discuss below), the tool has already produced a few live apps on the Apple App Store such as the open-source Reddit client RedReader and an open-source Sudoku client to prove it works.

---

Android Apps on iOS with MechDome

The stated goal of MechDome is to allow developers to convert an unmodified Android app into a native iOS or OS X app. Compared to technologies such as Intel's Multi-OS Engine or Xamarin, an Android developer does not need to know how to bind an Objective-C library because the tool will handle that for you. Nor is there any need to use a UI builder to modify your Android app, as MechDome handles converting all Android UI elements. Yes, even Android tablet apps translate nicely into a format suitable for iPads.

 

MechDome's biggest promise is that the converted Android app will function in a manner that users of the target OS will be familiar with. For instance, the Android share menu will be replaced with the native share sheet in iOS, and will include the ability to use AirDrop if applicable. Apps that post notifications in Android will instead display a notification in iOS's Notification Center. Certain intents such as opening a camera on Android will indeed open the camera on the iOS device, and URL intents on Android will call Safari on iOS. Content providers on Android that access contacts or the calendar will instead access the relevant iOS or OS X databases for this information.

In general though, all hardware functionality required for the use of an Android app will be mapped directly to use the relevant hardware in iOS. Software functions, though, can be split into 3 distinct categories: 1) functionality that doesn't exist on iOS (such as the toast message) will be implemented directly, 2) functionality that exists on both iOS and Android are replaced with the relevant iOS method, and 3) functionality that exists on iOS but not on Android (such as Apple's 3D Touch library) cannot be converted but can be implemented through the use of a library. Most activities, views, services, toasts, and basic content providers should be convertible from Android to iOS, according to MechDome's founder.

But as mentioned previously, there are indeed some limitations to this tool that are imposed by the nature of how iOS works. One of the biggest challenges facing an Android developer looking to convert his or her app to iOS is how to handle a background service. iOS is much more stringent with when and what kinds of background services that third-party applications can run, for better or worse. Furthermore, the rich intent system present in Android that allows for inter-app communication is largely absent on iOS. Finally, the Google Play Services API is currently not supported, so any app relying on Google services will not function. Thus, developers will be mostly limited to functionality that is accessed directly by manual user input, which should not pose a significant problem for most games or apps.

---

MechDome In Use

In a private demo, the tool does indeed seem to function as advertised. Mr. Kosmiskas demonstrated compiling several fully functional Android apps into working iOS and OSX apps. Toast notifications, notifications in the Notification Center, webview, location access, text input, and general functionality of UI elements all worked in demo. The AOSP calculator running on iOS looked and functioned exactly as it does on any Android device.

Updating an application and re-compiling it for iOS was also shown, and the process fairly simple. The developer, in this case Mr. Kosmiskas, demonstrated changing a text box to display "XDA-Developers" in Android Studio. He then exported the app, generated a signed APK, and compiled the iOS and OS X binaries in seconds from the MechDome server. When the iOS app was started using an emulator, the changes made in Android Studio were present.

Currently, MechDome is undergoing a free public beta program. Developers can register their app on the MechDome website to receive an invite to test converting their Android app. No pricing information has yet been unveiled for the service, unfortunately. Still, it's an interesting project to stay on the lookout for if you're an Android developer looking to eventually make waves in Apple's ecosystem without having to expend much effort of your own.

from xda-developers http://ift.tt/2dxa7Zc
via IFTTT

Google Reportedly Wants OEMs to Integrate Google Home in Products

October 4th is going to be a big day for the Mountain View internet giant. It's all but confirmed to be the day Google officially announces the upcoming Pixel and Pixel XL smartphones. We've seen mock-ups created, the the front display assembly leaked, photos showing the front and back of the devices, and software details about how they will have 2 of each partition and how that could allow community developers to do a number of unique things with custom software.

It's fair to say the Pixel and Pixel XL have not been shy over the last couple of months. We're looking forward to seeing these two devices officially announced next week, but rumor has it that smartphones won't be the only thing Google unveils on October 4th. If true, we could see Google announcing hardware products like the Chromecast dongle that can support Ultra HD video, the Daydream View VR headset, and Google Home.

You can think of Google Home as their way to compete with the Amazon Echo. A standalone device that allows you to access your entertainment (like playing songs and playlists), manage your everyday tasks (like setting reminders, making reservations, controlling your lights and thermostat), and having access to Google search all with just your voice. It was originally thought that Google would be the sole manufacturer of this device, but a new report says otherwise.

Variety is reporting that Google is wanting other OEMs to integrate Google Home into their own products. At first it seemed like this meant something similar to how they did their OnHub router where multiple manufacturers could make their own, but it could go beyond that. At a closed door meeting with Google, it's said that Google wants other OEMs to utilize Google Home like they have been with Google Cast. The report also says that Google might be displaying "aggressive muscle-flexing" in its negotiation by telling manufacturers that they'd have to incorporate the service if they want their products to be able to use Chromecast at all.

Either way, we could see a number of products like smart TVs, soundbars, Bluetooth speakers, and more have Google Home baked right into the product and as early as next summer.

Source: Variety

from xda-developers http://ift.tt/2dKwzBy
via IFTTT

Qualcomm is Reportedly in Talks to Acquire NXP Semiconductor

Qualcomm's financial standing seemed to have started going slightly down hill when Samsung opted for their own Exynos chipset over the traditional Snapdragon variant in select markets last year. The company had to revise their sales targets for the entire year because of this and while they did beat analyst expectations in Q3 of 2015, revenues were still down $7.1 billion during the same quarter the year before.

The company saw profits increase during Q1 of this year, but overall revenue was still down 19% YoY due to a fall in shipments. Qualcomm losing some of its modem business to Intel puts pressure on them too. So we can see Qualcomm hasn't had the best track record lately (more specifically, last year), but a new report suggests they can even this out with a possible acquisition. The Wall Street Journal is reporting that Qualcomm is looking to acquire NXP Semiconductor for upwards of $30 billion.

Less than a year ago, NXP had acquired Freescale Semiconductor for a cool $12 billion that made the company the "the world's top maker of automotive electronics." See, while NXP does offer some ARM SoCs, they are focused more on the low-power components for integrated devices. The company sells a number of automobile products like temperature sensors and power management controllers.

During the first two quarters of this year, NPX saw over a 50% increase in revenue growth compared to the same quarter a year before. So while we could see some overlap here with NXP's SoC business, this acquisition could be more about expanding away from smartphones and diving into other markets. This type of diversity would allow Qualcomm to still thrive if they happen to have another slip up like they did with the Snapdragon 810, and at the very least it allows Qualcomm to expand without as much risk by acquiring a repertoire of established designs.

Source: The Wall Street Journal

from xda-developers http://ift.tt/2dFc6uX
via IFTTT

LeEco Sends Out Press Invites for an Event in the US

LeEco, formerly known as LeTV, is a massive Chinese conglomerate that has their hand in all sorts of industries. The company deals with music, sports, smart TVs, cloud computing, driverless cars, and has made a big splash in China and India with their smartphone business. Much like Xiaomi, LeEco's smartphones are priced very competitively and with impressive build quality for the price you pay.

The LeEco Le Max 2 was already a popular phone for the company in India, and they just gave it a temporary price cut, down to Rs. 17,999 (~$270USD). It is hard for OEMs to compete with LeEco when it comes to price, and lately we've seen the company start to plan an expansion into the United States. They opened up their first United States headquarters in San Jose earlier this year, then bought over 48 acres of land from Yahoo a month later, and finally confirmed something big for the US this fall season.

At the time they announced their fall surprise for the United States, LeEco had already hired 400 employees. The company says they they are on track to grow this number to 1,000 before the end of the year so it seems obvious they are planning for something big in the states. Now, LeEco has started to send out press invites to various technology publications for an upcoming event that will take place in San Francisco on October 19th.

They have yet to confirm exactly what this event will be about, but many are speculating it will be the first time their products will officially be sold in the country, and some reports claim they might be bringing their services too. But again, LeEco is involved in a number of industries so it's hard to pinpoint exactly what they're planning. We would like to think they will announce plans to sell their smartphones in the US (and we believe it makes the most sense, given other similarly competitive companies are doing the same lately), but this could be about smart TVs, smart bikes, etcetera. We'll just have to wait a few weeks and see how things turn out.

Source: TechnoBuffalo

from xda-developers http://ift.tt/2cGeWTe
via IFTTT

Recreate a Matrix Effect in an Android App

A fun project to try inside of an Android app is to recreate the Matrix-like effect. XDA Recognized Developer sylsau has posted a tutorial detailing how you can achieve this Digital Rain effect inside a demo app.

from xda-developers http://ift.tt/2cGdakT
via IFTTT