LightBlog

jeudi 19 janvier 2017

Google has Acquired Fabric, Twitter’s Mobile App Developer Platform

Crashlytics was founded in 2011, but was acquired by Twitter at the start of 2013. The team continued to work out of Boston, Massachusetts and had an SDK that was used in over 1 million applications. They developed software that enabled iOS, Android and Unity developers to pinpoint the reasons why their applications were not stable (down to the exact line of code in some cases). By the end of 2016, it was announced that their software had been installed on over 2 billion active devices.

Almost two years after Twitter acquired Crashlytics, they announced Fabric. This was their expansion into mobile application analytics, beta distribution, and also user identity and authentication. We have talked about the project on multiple occasions here at XDA, and Fabric had become quite popular within the mobile developer community. This was Crashlytics' first introduction of a modular SDK platform for the company. The modular functionality allowed developers to pick and choose which features they needed.

It's fair to say that Twitter hasn't had the best revenue stream over the last few years. As the company tries to reorganize their business model so they can become more streamlined, we're seeing them cut back in certain areas. This was a big reason why they chose to turn Vine into a simple camera application recently. Since Twitter doesn't feel Fabric plays a vital role in their social platform, they have been in talks to sell the technology along with the team to Google.

The team behind Fabric will now work under Google's Developer Products Group and they'll be working directly with the Firebase team. Both teams have a goal to help developers build better applications as well as helping them grow and scale their business too. We'll have to wait and see what the end goal of this acquisition is. Whether or not Google will let Fabric continue to function independently, or if they simply want to fold the technology into Firebase.

Source: Fabric



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

OxygenOS 4.0.2 and New Open Betas Released for the OnePlus 3 and 3T

Following closely on the heels of their last two updates mere weeks ago, OnePlus has begun rolling out incremental updates to both the OnePlus 3 and 3T. These updates are rolling out to both the official and beta channels for OP3/3T owners. All users should begin to see the update become available over the next few days and can expect to see numerous changes. Oxygen OS 4.0.2 brings some of the fruit of Betas 10 and 1 (N) to their respective 3 and 3T users, as well as improved stability thanks to the early adopters who have been bug testing it since its release in late December.

After OnePlus barely squeaked by their own self-imposed deadline to release a stable Nougat build for the 3 and 3T before 2017, it is reassuring to see that the OnePlus' development team has not slowed down. While OOS 4.0.2 is a very minor update, it still will offer users improved stability and some partial fixes for previous issues such as inconsistent WiFi connectivity, APN improvements for certain carriers, and other miscellaneous bug fixes. A tutorial for updating to OOS 4.0.2 can be found here for the 3T (which should also apply to the 3, after swapping device-specific update files). The process is identical to past updates for those already familiar, although OnePlus 3T users running TWRP will want to update to version 3.0.3-1 of the recovery (and 3 users to version 3.0.3-0), prior to applying the update.

Open Beta 2 (N) for the 3T and 11 (N) for the 3 have also been released to the public, containing the same modifications as 4.0.2 while also adding a few additional features – most notably Extended Screenshots. A mysterious new category in Settings, titled "OnePlus Laboratory", has also been unearthed with no present explanation available for what its purpose might eventually be. I will be awaiting official confirmation from OnePlus with bated breath, given rumblings in the forums that it could be something along the lines of the Xposed framework and its many affiliated modules.

The mysterious OnePlus Laboratory splash screen, discovered by OnePlus forums user smartanish7.

While OnePlus has still failed to release kernel sources for their Nougat-based OxygenOS release, these incremental updates are at least a small consolation for users in the meantime.


Source: OnePlus Forums (1)
Source: OnePlus Forums (2)



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

The Galaxy S8 is Rumored to Come with the Largest 5.7″ Panel

We were essentially in the dark about the Galaxy S8 until a few months ago, and since then we've seen numerous rumors published about their upcoming flagship smartphone. It's believed that they will be called the Galaxy S8 and the Galaxy S8 Plus and they will both be equipped with incredibly thin bezels at both the top/bottom and sides of the phone.

We're even seeing reports that they will have bigger screens than any previous Galaxy S device in the past, with the regular one being 5.7″ and the bigger version being 6.2″.

The feature image above (which you can view in its entirety by tapping/clicking on it) has been provided to us by @DforDesign, and is currently being reported as the actual glass that will be covering the screen. These actually seem like tempered glass screen protectors, but either way they give us a look at what the upcoming Galaxy S8 smartphones could look like. This thin bezel design actually meshes with the confirmation we received about Samsung investing in edge-to-edge display technology.

These screens won't go all the way up to the top and bottom edges, but they do show us what type of progress Samsung has been making lately. This image also coincides with the rumors about Samsung ditching their physical buttons for the S8 phones, and opting for virtual navigation buttons instead. They're also really close to what GSM Arena published late last week when they revealed a render of what the upcoming phone could look like.

Samsung hasn't made major design changes like this since they debuted the Galaxy S6 back in 2015. As the company faces more intense competition from Apple this year (which marks the 10 year anniversary of the iPhone), and Google as well, it will be interesting to see if this new design pays off for Samsung.

Based on the rumored specs, renders and this tempered glass protector, do you think the Galaxy S8 and Galaxy S8 Plus will succeed with the average smartphone customers?

Source: The Korean Herald

Feature Image Credit: @DforDesign



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

Huawei’s Security Advisory Announces Fixes for Multiple Vulnerabilities

Similar to the Android security bulletins that Google, LG and Samsung have, Huawei is another company that keeps track of vulnerabilities that are reported to them. The company published three of these this week and they are possible on a combination of three smartphones that Huawei is currently selling. Fixes for these vulnerabilities will be included in an OTA update that Huawei (or carriers) send to the consumer, but they don't give us an ETA as to when that update will go out.

The first vulnerability has been assigned the Common Vulnerabilities and Exposures (CVE) ID of CVE-2017-2711, and it targets the Huawei P9 Plus with a firmware version before VIE-AL10C00B352. This vulnerability will allow the attacker to crash the system software of the phone. The only way for this to happen is to trick the P9 Plus owner into downloading a malicious application, which then allows the attacker to crash the phone. To fix this vulnerability, the owner will just have to accept the OTA update for the new VIE-AL10C00B352 firmware.

The second vulnerability Huawei announced this week has been given the Common Vulnerabilities and Exposures (CVE) ID of CVE-2017-2703. This one is currently eligible on both the Huawei P9 as well as the Huawei Mate 9. Exploiting this vulnerability will allow the attacker to bypass the Phone Finder so they can enter the System Setting. All the person has to do is have physical access to the P9 or Mate 9 phone. Huawei has patched this vulnerability as well, so Mate 9 customers will want to look out for the MHA-DL00BC00B156 update, while P9 owners will need to look for the EVA-AL10C00B373 update.

Lastly, we have the vulnerability that has been issued the Common Vulnerabilities and Exposures (CVE) ID of CVE-2017-2698. This is currently affecting the Huawei P9 and Huawei Mate 8, and it allows the attacker to crash the system or even escalate user privilege. The only way this vulnerability can be exploited is by tricking someone who has root access to their phone into installing a malicious application. The fix for this attack has been patched in the NXT-AL10C00B386 update for the Mate 8 and the EVA-AL10C00B373 update for the P9.

Source 1: Huawei Source 2: Huawei Source 3: Huawei



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

mercredi 18 janvier 2017

Google Photos Prepares to Allow for Editing the Date and Time of a Photo

Google Photos has always been one of Google's more useful services. The photo backup service has garnered widespread praise for its unlimited, free backup features as well as its robust sharing capabilities. But one area that Google Photos has always lagged in is the ability to edit your photos. Luckily over time, Google has been introducing more and more features to allow you to customize your pictures to your liking (though the editing features are not as robust as those found in some of its competitors).

Editing your photo to produce a better image is one thing, but what about editing your image to make it easier to organize? Unfortunately, the ability ot Google Photos to modify EXIF data has been rather limited. Even today, the ability to edit something as basic as the date and timestamp of a photo is limited to the desktop version. But with Google Photos version 2.7 now rolling out, that may change. A teardown of the APK reveals that Google may soon allow you to edit the EXIF timestamp of your photos.

Although a teardown can provide valuable information regarding upcoming features, it is entirely possible that these features may not make their way into the final product. Do not take these teardowns as proof that a feature will be added, but rather as a hint of what could be coming.


Google Photos Teardown

Within the latest version of Google Photos, there is an interesting string located within the APK that hints at the ability to edit the timestamp of a photo:

  <string name="photos_mediadetails_details_edit_datetime_icon_content_description">Edit icon to allow the user to edit the date/time of the media.</string>  

As you can see, there apparently will be an icon within the picture detail screen that will allow you to simply edit the date/time of the media. Evidence for this feature can also be found with a new layout file that has been added to the APK:

Google Photos Teardown

exif_datetime_item.xml

  <?xml version="1.0" encoding="utf-8"?>  <LinearLayout android:orientation="horizontal" android:id="@id/exif_datetime_item_layout" android:padding="@dimen/photos_mediadetails_item_padding" android:layout_width="fill_parent" android:layout_height="wrap_content" android:minHeight="@dimen/photos_mediadetails_item_min_height"  xmlns:android="http://ift.tt/nIICcg">  <ImageView android:layout_gravity="center" android:id="@id/icon" android:padding="@dimen/photos_mediadetails_item_padding" android:layout_width="66.0dip" android:layout_height="36.0dip" />  <LinearLayout android:orientation="vertical" android:padding="@dimen/photos_mediadetails_item_padding" android:layout_width="0.0dip" android:layout_height="wrap_content" android:minHeight="@dimen/photos_mediadetails_item_min_height" android:layout_weight="1.0">  <TextView android:layout_gravity="start|center" android:id="@id/label" android:paddingLeft="2.0dip" android:paddingTop="8.0dip" android:paddingRight="2.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content" style="@style/quantum_text_subhead_black" />  <TextView android:textColor="@color/quantum_black_secondary_text" android:layout_gravity="start|center" android:id="@id/value" android:paddingLeft="2.0dip" android:paddingRight="2.0dip" android:paddingBottom="8.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content" style="@style/quantum_text_subhead_black" />  </LinearLayout>  <ImageView android:layout_gravity="center" android:id="@id/edit_icon" android:padding="@dimen/photos_mediadetails_item_padding" android:visibility="gone" android:layout_width="66.0dip" android:layout_height="36.0dip" android:src="@drawable/quantum_ic_mode_edit_black_18" android:contentDescription="@string/photos_mediadetails_details_edit_datetime_icon_content_description" android:alpha="0.38" />  </LinearLayout>  

 

The name of the layout file and the description of the string are quite clear: editing the EXIF timestamp of a photo may soon be available on the Android version of the application. Desktop users (and even iOS users) have had this ability for quite some time now, so hopefully it finally makes its way to Android as well.



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

The Future of the Pixel is Bright

According to trend analyses and reports produced by Wave7, a U.S. mobile market analyst, the Google's Pixel series have been selling consistently well over the three or so months it has been available. Given a selection of reporting around the time of launch that failed to clearly differentiate between Verizon being the exclusive Pixel carrier and Verizon being the only Pixel carrier, as well as displaying some reasonable hesitation about certain aspects of the relationship, there was no consensus among those covering the topic about the likelihood of Pixel succeeding as a product.

However, Verizon has made it clear that they were taking their exclusivity deal seriously and embarked on a multi-million dollar advertising campaign for the Google Pixel devices, as well as offering aggressive discounts and deals just after release that continued throughout the holiday season. Wave7 has found that Pixels have sold extremely well despite limited availability, reporting that Verizon representatives claimed that Pixels accounted for between 12.3% and 9.5% of all devices sold by Verizon in December and January, respectively. Given this fact, the limited availability of Pixel devices, a fact which has remained rather constant since launch, may well be a result of Google responding to greater demand than they had originally anticipated.

Regardless, with multiple financial analysts expecting around $2-4 billion in revenue from Pixel sales in fiscal year 2017, industry confidence in the Pixel is firm, albeit with plenty of room for growth. Gross margin estimates for Q4 2016 sales place Google's Pixel and Pixel XL at a bit more than half of the iPhone's industry-leading 41%, with overall profit estimates fluctuating around $400 to 500 million.

IHS Markit, Company Data, Morgan Stanley Research

Morgan Stanley estimates Pixels will bring in around $375 million of profit in Q4 of 2016. (IHS Markit, Company Data, Morgan Stanley Research)

This places the Pixel devices magnitudes below Apple's iPhone in terms of sales throughput and profitability, but the fact that it is profitable at all is of great importance. Given that Morgan Stanley's analysts term the Pixel as a program of "Android user monetization", the Pixel devices likely have a broader financial impact and utility for Google than can be seen simply by estimating device sales — past a certain point.


The Future of the Pixel Brand

Alphabet has been relentless in its willingness to shed internal groups and pursuits that fail to be profitable for too long. Fios, the Titan drone platform of Project Loon, and Alphabet's self-driving car program have all been either put on hold, cancelled, or spun off into non-Alphabet related entities in the last 12 months alone. With a central goal of profitability clearly for the most part taking precedent over any form of vision or other non-financial goals, any program that fails to show growth and profitability is likely at risk of being excised from Alphabet. Thankfully, Pixel appears to be safe for the foreseeable future, as long as it continues to perform well.

With the stability of the Pixel brand more or less assured for 2017, it is worth briefly considering what the future may hold for Google's nascent smartphone. XDA's own Mario Serrafero published an extensive review of the Pixel XL and concluded that "the Pixel XL is a great consumer smartphone, but not the Google flagship I expected. Nevertheless, it sets the foundations for something bigger, and as Google's ecosystem matures, the Pixel and its Assistant will get wiser with it." This sentiment aligns closely with the response most technical reviewers have had. The Pixel shows immense promise but has also demonstrated some rough edges and areas that could use improvement, something that we recently explored.

One of the reasons that I maintain a significant amount of hope for the Pixel's future, in spite of those rough edges, lies in the story of the development for the Pixel and Pixel XL. As discussed over at Ars Technica, there are a couple hints which suggest that the Pixel was pushed through a rushed development schedule of as little as 9 months from conception to production. As the article clearly illustrates, the Pixel features a large number of similarities with HTC's A9, ranging from the appearance of the device to its motherboard layout — this isn't odd considering who the actual assembler of the Pixel is. XDA also covered suspicious software-level tidbits that pointed to some HTC influence. Given unofficial reports that Huawei was initially pegged to manufacture the Pixel but backed out over concerns about Google's insistence on maintaining its own brand on the device as well as David Pierce of Wired stating that employees of Google blamed "running out of time" for the lack of waterproofing, a strong case can be made that the Pixels were rushed to market.

For how strong of a device it is, the Pixel's brief but mostly successful development is a notable accomplishment for Google (and possibly HTC). Dave Burke, Android's VP of Engineering, also told interviewers in early November 2016 that he had already been shown photos taken by a device that was to be released in fall of 2017. This suggests that Google's second foray into (semi) in-house smartphone development will have at least 12 months, and probably closer to 16 months, if a functional prototype existed only a month after the Pixel was released. With a more typical production cycle for the Pixel's successor, the few rough edges of the Pixel have a good chance of being alleviated. By potentially tripling the amount of time Google engineers will have worked from start to finish to bring an Android device to market, there is plenty of time for Google to mature its hardware development team and more effectively step into the role of being its own smartphone designer.

A Pixel successor that seriously addressed the original's flaws would be quite the sight to behold, and I am immensely excited to see what Google may yet accomplish before the end of 2017.


What do think about the Pixel and the approach Google has taken for its development? Let us know in the comments below if you have any thoughts or predictions for the future Google's in-house smartphone development. 

Source: FierceWireless (1)
Source: FierceWireless (2)



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

Qualcomm Maintains its Dedication to Security with Secure Boot

Along the lines of Android Nougat's strictly enforced verified boot and Windows' Secure Boot features, Qualcomm is also pursuing a set of security standards based on cryptographic image authentication to ensure a secure boot chain.

A typical secure boot chain. (Qualcomm, Ryan Nakamoto)

As Qualcomm Engineer Ryan Nakamoto muses, all devices with boot chains are potentially vulnerable to malicious image injection. If an attacker gains access to images earlier in the boot chain, particularly the primary or secondary bootloaders, they gain the ability to control much or all of what follows. In order to better prevent attacks like these, Qualcomm's implementation of secure boot secures every aspect of the boot chain, beginning with the first ROM bootloader. As a step of the chain finishes, the segment will verify that it is unmodified and then provide a signature that the next segment in the boot chain must cryptographically verify. If the signature produced is different than what the following segment expects, then the boot process will be immediately ended.

While secure boot implementations like dm-verity and Windows Secure Boot are the bane of many a custom ROM developers, the improved security they offer the lay-consumer is paramount.

As Microsoft and Qualcomm recently announced that upcoming devices would be able to run Windows 10 on Snapdragon hardware this year, it is far from surprising that Qualcomm chose to bring up its secure boot implementation in late 2016. Given the spate of Android security scares that arose throughout 2016, security has become a serious concern for many consumers, so Qualcomm's continued dedicated to secure software is more than welcome.


Source: Qualcomm



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