lundi 31 octobre 2016

PSA: Google Assistant says it’s “Offline” when you’re on a VPN, but everything still works

Google Assistant is one of the most advertised features for the new Google Pixel and Pixel XL smartphones, although there are ways to enable it on non-Pixel Nougat devices as well as on non-Nougat devices. Although Google has currently restricted official compatibility to a very small subset of Android devices, you can still get full use out of Assistant through these unofficial mods. Assistant is still clearly undergoing lots of changes, as many of the features shown off during the October 4th event have yet to make their way into the production build of the service. Though, we at XDA have been having some fun with the IFTTT integration that was recently released.

A few users have noticed a peculiar, yet ultimately benign bug in Google Assistant. If you regularly make use of VPN on your Android device, you will find that Google Assistant seemingly falls back to working only in offline mode. The choice of device does not matter nor does the means of getting Assistant working in the first place (eg. via build.prop edits or Xposed module), as the bug seems to be Google Assistant related. We say that the bug is benign because despite warning you that Google Assistant is in offline mode, everything still seems to work just fine. Some users of ad-blocking software that relies of creating a VPN are reporting that Assistant is not working for them, but we haven't been able to corroborate that claim.

In any case, to recreate the bug simply turn on any VPN connection (in my testing even Google's WiFi Assistant seems to trigger the bug) and open up Google Assistant. There you have it: in case you were confused why Google Assistant is saying you're offline, it's because of a bug triggered by whatever VPN you're currently running.

Notice the "You're Offline" Subtle Warning But Assistant still works. See: this totally legitimate Assistant command.



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

Xposed Module LeEco EUI Modder allows for a Near-Vanilla Android UI

XDA Member zyberkiddy has created an Xposed Module called LeEco EUI Modder that lets you customize a number of features included in version 5.8 of LeEco's EUI OEM skin. You can bring back the vanilla lockscreen, vanilla recent app switcher, and more.



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

ARM announces their second Bifrost GPU – the Mali-G51

Back in May of this year ARM announced the Mali-G71, the company's first GPU that utilized their new Bifrost architecture. This new architecture from ARM was quickly adopted into the high-end mobile market, due to growing demand for VR gaming along with other complex and constantly evolving power hungry mobile gaming content. When building their new Bifrost architecture, ARM wanted to create a GPU that could scale to any price point.

Thus, the Mali-G51 GPU was born. Aimed at the "mainstream" smartphone market rather than the high-end market, the Mali-G51 is ARM's attempt at creating a GPU capable of handling high-level graphics requirements without pushing the cost requirement. The company was able to tune the Bifrost architecture to the performance level and power limitations that most smartphones and tablets have. ARM says they were able to optimize Bifrost's low-level instruction set even further with the introduction of the new Mali-G51, and they've also implemented a new dual-pixel shader core.

ARM states that they've also redesigned the texturing units and improved the framebuffer compression as well. There's been a lot of work put into this GPU over the past 5 months, and ARM is clearly pleased with their results. The Mali-G51 GPU supports scalable performance for the latest graphics APIs including OpenCL 2.0, OpenGL ES 3.2 and the popular Vulkan. When compared to the Mali-T830, ARM says the G51 offers a 60% boost in performance density.

This performance boost is also accompanied by a 60% increase in energy efficiency, and the GPU as a whole is 30% smaller when compared to the Mali-T830 as well. ARM says the Mali-G51 GPU offers sustained performance thanks to the their latest advancements in energy efficiency, which is really important for those long mobile gaming sessions. The company says they will bring the Mali-G51 to its first SoC sometime in 2017, and that means we'll likely start to see it appear in many mobile devices in 2018 at the latest.

Source: ARM Connected Community



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

Mod Brings Night Mode Back to the Nexus 6P on Android 7.1.1

Many people have been disappointed with the removal of Night Mode on the Nexus 6P with the Android 7.1 Developer Preview. Now, a modification from XDA Senior Member SyCreed brings Night Mode, Pixel navigation bar icons, uncolored battery saver mode and more for the Nexus 6P.



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

Root is Now Available for the LG V20

We saw SuperSU released for the Pixel phones this weekend, but now root has made its way to the LG V20 as well. This root method is possible thanks to XDA Recognized Developer jcadduono, who walks you through the entire rooting process in his forum thread.



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

Sony publishes instructions on how to build Android 7.1 AOSP for Xperia Devices

Sony is one of the few OEMs that remains a firm believer in AOSP. Most companies do not bother providing necessary firmware binaries to allow developers to port AOSP onto the device. But while some OEMs actually do provide binaries for developers to make AOSP builds, like we saw with the OnePlus 3, Sony takes it a step further and ensures that AOSP functions properly on all of their devices. Although Sony's Open Device program does not extend to every device it releases, the work that they put out makes the lives of custom ROM developers far, far easier and the community could not be more appreciative for it.

Right now, Sony has published binaries and resources for the Xperia X Compact, Xperia X, Xperia Z5 Premium, Xperia Z5, Xperia Z5 Compact, Xperia Z3+, Xperia Z4 Tablet, Xperia Z3, Xperia Z3 Compact, Xperia Z3 Tablet Compact, Xperia Z2, Xperia Z2 Tablet, Xperia Z1, Xperia Z1 Compact, Xperia Z Ultra, Xperia Z, Xperia ZL, Xperia Tablet Z, Xperia E3, Xperia M2, Xperia T2 Ultra, Xperia T3, Xperia L and the Xperia S.

Sony has also been the only OEM to participate extensively in the Android N Developer Preview program as well. They have previously published a guide on how to build Android 7.0 AOSP for their various supported Xperia devices and this weekend they did the same for the newly released Android 7.1 Nougat Developer Previews. This is an early build though, and thus it is currently marked as Experimental. The guide assumes you're running Ubuntu, as the guide was made using Ubuntu 14.04 LTS, but it will work in a similar way on other Linux distributions.

The guide starts by having you prepare your Java environment, then has you installing the necessary tools to make an Android build and then has you download the Repo tool and set a PATH. Then, the guide walks you through initializing the AOSP tree, adding the necessary patches from the AOSP upstream branch, and then instructions on how to build AOSP images for Android 7.1 Nougat so they can be flashed to the device.

Be sure to check out the Sony Xperia Developer GitHub page and contribute in any way that you can.

Source: Sony Mobile Developer World



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

dimanche 30 octobre 2016

How to Unlock Bootloader on Honor 8

 

Before you can root your Honor 8 or install a custom recovery, you'll want to unlock your bootloader. In this tutorial, I'll show you how to get the unlock code for your device and how to use ADB to unlock your bootloader.

Backup your data first. Unlocking the bootloader will wipe the data on your Honor 8.

Get your unlock code

  • Go to this website and create an account.
  • Go to Downloads > Unlock Bootloader
  • Fill out the form with the S/N, IMEI, product code and model number
  • Your unlock code will be shown on the same page, at the bottom of the form

Turn on USB Debugging and OEM Unlock

  • On your Honor 8:
  • Go to Settings > About
  • Tap on Build Number seven times
  • Go to Developer Options
  • Check Enable OEM Unlock
  • Check USB Debugging

Unlock VIA ADB

If you haven't installed ADB yet, see this thread for instructions.

  • Plug your phone into your computer VIA USB
  • Type the command 'adb reboot bootloader' and hit enter.
  • Once in bootloader mode, type 'fastboot oem unlock [unlock code]'
  • Follow the on-screen instructions

unlocked

If you see this warning when your phone reboots, then you have done everything correctly.

We are working closely with Honor and several developers to make sure that there will be more development content for this device in the future.

For more Honor 8 content, check out the Honor 8 XDA forums.



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

samedi 29 octobre 2016

UMi Plus XDA TV Review

As we all know, flagship phones are not cheap. Many people simply do not have the money to spend on a high end flagship device. Today we are going to be looking at a phone that, while not a flagship, has many of the specs and features that you'd expect in one. This is the $200 UMi Plus.

 

Check out the YouTube video review from Miles to see how you can win an UMi Plus for yourself.

Thanks to UMi for sponsoring this video and letting us check out the UMi Plus.
See more info about the UMi Plus here.



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

vendredi 28 octobre 2016

Tiered Fees are Coming to Swappa on November 1st

If you haven't already heard of the service, Swappa is an online marketplace that was launched for people to buy or sell mobile devices. Over the years, the types of products available for listing on the site have expanded to include tablets, laptops, wearables, and even VR headsets. With other reseller marketplaces such as eBay becoming cluttered and expensive for the seller, Swappa quickly caught on among enthusiasts. When we shut down the XDA marketplace back in 2013, partnering with Swappa was a no brainer to fill the gap left behind by our now-defunct marketplace.

Since Swappa launched, the company has only charged a measly $10 fee to the seller when their device was sold. If the device goes unsold, then the seller isn't charged a penny which is more than you can say for some of the competitors out there. But with such growing demand for the service, it seems that this service model was not sustainable for Swappa to continue offering to its customers. Swappa has just announced that they will be introducing a tiered fee system that will be applied to all devices listed on the site starting on November 1st. The result is that some sellers will be charged more than the previous $10 flat fee, but it's still much less than its competitors.

To break things down, if your device is sold on Swappa within the $0 – $100 price range then the fee will only be $5. If the device you just sold on Swappa was priced between $101 and $300, then your fee will be the same $10 like it always has been. Any devices sold at a price over $300 will be subject to an additional $5 per price tier increase, as listed in the chart below.

Be sure to check Swappa's fee page for the full details, but looking at the price difference between the available services it's clear that Swappa's tiered pricing system makes Swappa the preferable choice for enthusiasts looking to buy or sell their device. If this article is the first time you've ever heard of Swappa, then go register an account using the XDA-Developers username integration, and keep on the lookout for great sales on a wide variety of products.

Swappa Fees

Source: Swappa



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

Sony Announces PS Vue for Android TV

Sony just made a big announcement for PS Vue users who also have a smart TV or a standalone box running Android TV. PS Vue on Android isn't new, as the app has been available on mobile devices for a few months now. The big news this week is that PlayStation Vue is finally available for Android TV. Sony says you can download the new PS Vue app on your Android TV device that's running "Android OS 4.4 or higher" (even though we know Android TV launched with 5.0 Lollipop).

If you already have a PS Vue subscription, then you can download their new Android TV application from the Play Store and instantly start watching the content on your TV right now. Those who have yet to try out PS Vue, Sony is offering a free seven-day trial over on the PS Vue website. After you sign up, you can easily connect your Android TV device to your newly-created account.

PS Vue comes with a number of different subscription plans that try to fit your personal usage. The Access plan starts at $30 per month, but could be $40 if you live in a city with "major live local broadcast stations". This plan comes with over 55 channels including live cable TV, movies, and sports. The Core plan is priced at $35/$45 and comes with over 70 channels including live national and regional sports networks.

The Elite PS Vue subscription plan will cost you $45/$55 and it comes with over 100 channels that add in movie and entertainment channels. Lastly we have the Ultra plan that will run you $65/$75, and adds in both Showtime as well as HBO. These plans also come with Sony's cloud-based DVR system that enables you to "record hundreds of shows at once with no scheduling conflicts."

Sony also tells us that PS Vue will be launching on both the PC as well as macOS soon, and that subscribers can stream PlayStation Vue content on up to five devices at the same time.

Source: PlayStation Blog



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

Oracle Files for an Appeal in its Case Against Google

Soon after Oracle acquired Sun Microsystems, the company went after Google for allegedly infringing on copyrights and patents that are related to Java. It took two years before the case went to trial and Oracle eventually lost as the courts were unable to find any evidence about what the company had claimed. Oracle then decided to revive part of its case thanks to the appeals process in the United States, with the second trial focusing solely on the APIs for Java.

During this time, we watched as Android 7.0 would not use Oracles proprietary Java APIs, an Oracle attorney revealed Android revenue information that was meant to be for their eyes only, the judge accused both Oracle and Google they were setting up the jury to fail. Oracle felt that Google should pay $9.3 billion for the way they used Java's APIs, but the settlement talks ended up falling through.

The jury agreed that Google's use of the Java APIs were considered fair use, and that they shouldn't be penalized for how it was implemented in Android. Oracle even tried to have their copyright trial loss thrown out because Google hadn't told the courts they were planning to launch Android apps on Chrome OS. This request was denied, but now they have filed for an appeal to the US Court of Appeals for the Federal Circuit.

It's unclear at this time if they will be granted the appeal, but it is highly likely since it is such a high profile case. If granted, Oracle will have an uphill battle as the tests for whether something is fair use or not are pretty subjective. So the case is now going back to the Federal Circuit, which is the same appeals court that originally said APIs could be copyrighted. Still, it will be a long and difficult road for Oracle's lawyers to try and pull off a win.

Source: Ars Technica



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

Which Past Phone Did You Like for its Innovation?

The recently released Xiaomi Mi MIX has opened up to a lot of appreciation for its bold approach in imagining what the smartphone future would look like, while still maintaining commercial sense (even if SHARP has done similar things before). With a nearly bezelless display, and all the innovation that went into making the phone possible, the Mi MIX is a breath of fresh air in the world of ordinarily rounded rectangles.

But the Mi MIX is not the first one to have experimented. There have been a lot of phones, both smart and feature phones alike, that stood out of the pack. They chose to redefine what the smartphone experience of the future would be like, albeit not all tasted the same success. So we ask you,

Which phone from the past did you like for its innovation? What did the phone bring to the market that was not considered ordinary at that time? Was it a new set of features, or was it a new software experience? How popular did the phone get, and how did it influence the future that we are living in today?

Let us know in the comments below!



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

Alphabet Brings in Over $5 Billion in Profit During Q3 2016

To round off the week, Alphabet has just published their 3rd quarter financial earnings for investors and the media. We can see that June, July, August and September were good for the internet tech giant. Overall revenue for the quarter increased to $22.4 billion when compared to the same quarter last year (which was at $18.6 billion). This quarter's revenue is up from $21.5 billion when you compare it to the second quarter of this year.

Google has reported that they were able to net $5.7 billion in total profit for the quarter, which is up from $4.7 billion compared to the same quarter of last year. This was mostly attributed to the profits that were brought in from the Google division. Google themselves saw their overall revenue go from $18.5 during the third quarter of 2015 up to $22.2 billion this year — with net profit increasing from $5.8 billion during the quarter last year all the way up to $6.7 billion from June through September of this year.

Naturally, Alphabet lost some of its profits thanks to their other bets/moonshot projects that they currently invest in. Alphabet's other bets consist of projects like Nest, Fiber, Verily, and more. They were able to increase overall revenue from $141 million during the third quarter of last year to $197 million this year. However, these other bets also cost Alphabet a total of $865 million and this is actually down from the operating loss of $980 million compared to the same quarter last year.

These types of results have been very typical ever since Alphabet was formed as the parent company of Google. We see the established products and services are bringing in enough profit to keep their moonshot projects funded. Sometimes these other bets don't pan out exactly as they originally planned. Which is what we're currently seeing with the fiber side of Google Access, but we can see that the company is still able to beat expectations.

Source: Alphabet Investor Relations



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

Google Assistant Gains IFTTT Support

This year, we're seeing Google take on the likes of Amazon, Siri and Microsoft in the personal assistant category with Google Assistant. The company will begin shipping out Google Home pre-orders within the next week, but the service won't be as powerful as its competition if it doesn't support a wide range of 3rd-party products and services. Many will be happy to use it for asking Google questions and interacting with Google services, but it will need more if it wants to be successful.

We've watched as Amazon has continually supported their Alexa personal assistant ever since the Echo was launched in November of 2014. 3rd-party developers are embedding the service into their own products (which is what Google is hoping for as well), and earlier this year they announced Alexa had over 1,000 skills. Amazon has even announced a year-long Alexa hackathon, and will be putting up a record-breaking $2.5 million purse for it.

So it's clear that Amazon is very dedicated to making Alexa work with as many services and connected devices as possible. This is why it was so surprising when Google announced the only products Google Home had support for was Philips Hue and Samsung SmartThings, as well as "given" ones like Nest. Granted, Google is just getting started in this market so it's fair that they aren't launching with support for hundreds of products and services.

Google just needs to be dedicated to the platform and it will easily be able to compete with the likes of Amazon Alexa. This is why it's such good news to hear that Google Assistant has gained support for IFTTT this week. Before Google Home has even been launched, it is able to connect with 258 different IFTTT channels. So, on the Pixel and Pixel XL, you can already do things like send a tweet by voice, send a note on Slack, add a new Google contact, add a Todoist task and so much more.

Be sure to check out the Google Assistant IFTTT channel to see all of the actions that are available.

Source: IFTTT



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

jeudi 27 octobre 2016

Verizon Pixel/Pixel XL Bootloader Unlock has been Released

When Google revealed they had struck a carrier exclusivity deal with Verizon for sales of the Google Pixel and Pixel XL within the United States, many of us feared the worst. Given Verizon's history of preventing bootloader unlocking, enthusiasts feared that even the standard bearer for Android, Google's first truly in-house flagship smartphone, would be subject to Verizon's draconian security measures. And indeed, that did appear to be the case. But cracking the Verizon Pixel/Pixel XL's bootloader seemed to be a matter of when, not if, and just the other day XDA Senior Recognized Developers beaups and jcase announced that they had figured out a way to unlock the bootloader. Furthermore, the two SunShine developers disclosed to XDA that their unlock method would be released for free which is something the two developers were under no obligation to do, but decided to do so for the benefit of the community.

Keeping their promise, the SunShine developers have just released dePixel8, a tool to unlock the Google Pixel and Pixel XL sold on Verizon Wireless in the U.S. or EE in the U.K.

According to the website, the tool works by forcefully enabling bootloader unlocking on the Pixel/Pixel XL by running the dePixel8 program on the target device. The tool does not actually unlock the bootloader, but that step can be easily done by issuing the usual fastboot oem unlocking command followed by fastboot oem unlock. You'll of course need to have the ADB and Fastboot binaries installed (we recommend Minimal ADB & Fastboot from our forums) and the appropriate drivers to allow your PC to recognize the device.

Because the tool is free to use, the SunShine developers will not provide any support for the product should anything go wrong. Though the tool is likely safe, you should accept any potential risk involved with using an unofficially supported bootloader unlocking method, so please do not go blaming the developers if something happens! If you appreciate the work that they've done (and you should), then all the developers ask of you is that you send donations to the Make-A-Wish Foundation.

We at XDA-Developers always appreciate the wonderful work done by developers, most of whom take precious time out of their lives to provide us the fruit of their labor for free. With the release of dePixel8, owners of the Verizon/EE Pixel and Pixel XL will soon be able to join their Play Store-bought brethren in flashing ALL the custom ROMs and kernels they desire.


Download dePixel8 from the SunShine website



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

Chainfire’s Systemless Root for Pixel Phones is Coming

We all knew it was coming. It's basically tradition that within days of Google releasing a new device, XDA Senior Recognized Developer Chainfire finds a working root method. In keeping with that tradition, earlier today Chainfire demonstrated he had achieved root access on his Pixel phone with a picture of ADB shell requesting superuser access. The news understandably brought much excitement to fans of the Google Pixel phones, but Chainfire quickly clarified that the method he used to achieve root access required modifying /system and disabling dm-verity.

Frequent readers of our Portal might recall that we wrote an article explaining the possible difficulties with rooting the Pixel phones, and it seems we were right on some fronts: Chainfire initially confirmed that disabling dm-verity would be problematic, and for a while he thought it would be impossible to disable dm-verity without changes to the kernel. But eventually he found a way to disable dm-verity, as usual, and within a day of poking around he achieved full systemless root by modifying the boot image:


This is exciting news for all Pixel owners, as systemless root has become the most common way of rooting devices since Android Marshmallow and now Google's latest phone can enjoy the benefits of root access, without the need for altering the kernel. Chainfire has once again worked around Google's changes to Android in order to bring root access to millions in the Android community, but the method is not ready for release yet. Chainfire says it'll take a few days to automate the process, clean up his work, and package it into a flashable zip, so please wait patiently for the release!

Keep in mind that to even attempt to root your device requires you to unlock the bootloader, which will cause SafetyNet to fail, so don't expect to play Pokemon Go or use Android Pay on your Pixel. Even with SultanXDA's temporary SafetyNet bypass patch, it's only a matter of time until Google updates SafetyNet to fix this loophole. Still, we were worried that disabling dm-verity would require modifying the kernel, but Chainfire proved us wrong. We can only hope that the ingenious developers on our forums can continue finding workarounds should the need arise, but at this point it's basically a game of whack-a-mole between developers and Google.

Feature image credit: The Legend



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

Android BBQ Vlog Day 2

The second day of the Big Android BBQ of 2016 was a bitter sweet experience. It was announced that this would be the last BBQ as there was no longer the sponsor presence needed to keep the event going. The event was a lot of fun and this video captures some of the final bits of the BBQ.

We were lucky enough to go to the Big Android BBQ thanks to our sponsor UMi. Their latest phone, the UMi plus, has 4GB RAM, a 4,000mAh battery, and stock Android for $149. Click here to check it out!
umidigi.com



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

XDA Forums Live for the Elephone S7 and Elephone R9

The curved display Elephone S7 and the almost bezel-less Elephone R9 now have their own sub forums over at XDA! Head on over!



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

AOSP 7.1 Lands Unofficially on the MT6752-based Jiayu S3

If you are looking to try out the absolute latest of Android, and have the MT6752 based Jiayu S3, try out the AOSP 7.1 builds from Team MAD.



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

Check out Unofficial CyanogenMod 13 on the Huawei P8!

XDA Senior Member nexolight's Unofficial CyanogenMod 13 is a Work-In-Progress ROM that showcases the stock Android experience on the Huawei P8. Be wary of the bugs though!



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

Qualcomm to Acquire NXP Semiconductors for $47 Billion

Qualcomm has officially announced today that it has reached a definitive agreement to acquire NXP Semiconductors. The agreement allows Qualcomm to purchase all issued and outstanding common shares of NXP for $110 per share, which gives NXP a total enterprise value of around $47 Billion. The acquisition has been rumored for a while, and Qualcomm has now made it official.

NXP's acquisition will help broaden Qualcomm's scope as areas of focus under NXP were primarily related to the automotive industry. This will reduce the dependence of the parent company on smartphone chips, as Qualcomm is seeing rising competition from Chinese and other Asian manufacturers in this area, which is likely to have its toll on profit margins in the future. The combination of Qualcomm and NXP is expected to have an annual revenue totaling more than $30 billion.

It is not all money though. Qualcomm will also see benefits in the form of additional expertise in the automative silicon market as well as the acquisition of sales channels, along with the sharing of NXP's portfolio of security solutions which in turn will complement Qualcomm's IoT solutions.

The acquisition transaction is expected to be complete by the end of 2017. While the tender offer is not subject to any financing conditions, the transaction is subject to regulatory approvals in various jurisdictions.

Source: Qualcomm



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

LG Looking to Incorporate MST Tech For Mobile Payments in LG G6

LG plans to go in strong with the G6. We do not really know a whole lot about the G6 at this stage, but recent developments have pointed that LG may finally be ready to move past dead technology and favor newer tech that offers more convenience.

A new report coming out of South Korea indicates that LG is giving up on the "White Card" payment method for mobile payments, which it was reportedly developing for its smartphones for about a year now. The White Card method needed the possession of a physical card in order to undertake mobile payments. LG is abandoning this method due to the White Card's "low usefulness, problems with batteries and lack of sales strategies", though the presence of a physical card (thus defeating the purpose of using your phone and not using a debit/credit card in the first place) sounds like a very good reason to not use this mobile payment solution from a consumer perspective. The White Card method sounds like adding inconvenience where it should not exist, and LG moving on is probably for the best.

LG's White Card that it was developing for LG Pay

LG's White Card that it was developing for LG Pay

What LG will use instead is the kind of MST (Magnetic Secure Transmission) technology that Samsung uses in Samsung Pay. Of course, Samsung does have patents on MST which should have granted it exclusivity over the technology. But LG is keen on avoiding infringement of Samsung's patents, which it will do by developing its own MST technology. LG will not outsource the development of this tech, and it has already selected partners to provide components for MST linkage. LG will start working with card companies at the end of this month for linking its payment system.

This MST tech will then be part of the LG G6, which is scheduled to come out in spring of 2017. The report also mentioned that the G6 will come bearing NFC and wireless charging as well. A separate report mentions that the LG G6 will also ditch the "Friends" module ecosystem as LG is not keen on staying aboard the sunk pseudo-modularity ship. We hope LG also manages to clean up on its QA systems, so that problems on its current flagships are not repeated in the future ones.

What are your thoughts on LG moving towards MST for LG Pay? Let us know in the comments below!


Source: ET NewsFeature Image: News1.kr



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

South Korea Grants Samsung a Patent on Fingerprint Scanner Gestures

We've seen multiple companies begin implementing fingerprint scanner gestures on their smartphones in the past. Huawei/Honor has been known for these gestures for quite a while, and many were hoping that it would be included in the Nexus 6P. This never happened, but Google was able to bring the feature with this year's Pixel and Pixel XL. However, it seems Samsung now has a patent for this type of functionality… at least in its home country of South Korea.

Samsung had actually filed for this fingerprint scanner gesture feature two whole years ago. So they have been thinking about this type of feature for a while now. The patent illustrations show off a different implementation than we've seen on smartphones today though. Instead of using the swipe gestures to trigger the notification shade, like we see on the Pixel phones, it looks like Samsung wants to use them for quick access to certain applications.

The patent shows someone swiping up on the fingerprint scanner to launch the web browser, swiping to the left to launch a saved contact, and swiping to the right to bring up your messaging application. If implemented, it's possible that these fingerprint scanner gestures could be customizable within Samsung's TouchWiz OEM skin, but we'll have to wait and see how the company plans to introduce it before we know for sure.

Just because Samsung now owns a patent for this implementation of fingerprint scanner gestures in their home country, doesn't mean we will see it in a product they will sell. Companies own lots of patents for things that are never used in their own products. So this might just be something that Samsung wants to keep in their trove of patents, but we could see it brought to life in an upcoming smartphone or tablet.

Source: SamMobile



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

Samsung and LG Both Announce Their Q3 2016 Financial Reports

Yesterday we saw HTC publishing their financial report for the third quarter of the year, and today we see that both LG and Samsung have done the same. All three companies were not able to put their best foot forward this year for different reasons, but some were able to come out better than others. LG wasn't able to sell as many units of the LG G5 as they had hoped, and Samsung had to deal with the Galaxy Note 7 debacle. So let's take a look at how these two companies fared this past quarter.

For Samsung, the company's overall revenue dropped by 3.87 trillion won to 47.82 trillion won when compared to the same quarter last year. As far as operating profits though, they were able to bring in 5.20 trillion won, which again is down by 2.19 trillion won compared to the 7.39 trillion they brought in last year at this time. When we specifically look at the company's mobile division, we can see that profits dropped a whole 96% when compared to the third quarter of last year as they were only able to bring in 100 billion won thanks to the Galaxy Note 7 being discontinued.

As far as overall revenue is concerned, LG was able to bring in $11.8 billion from the sales of their entire company. This resulted in LG being able to bring in $252.7 million in profit, but this is partially due to the company's Home Appliance & Air Solution business. LG's mobile division accounted for $2.3 billion of the company's revenue stream, which is down 23% compared to the same quarter last year. LG's mobile division actually had an operating loss of $389.4 million during the quarter, even though they were able to ship 13.5 million units.

It's safe to say that a number of smartphone companies haven't had the best 3rd quarter in 2016, but at least Samsung can say they were able to bring in some profit while others were unable to do so.

Source: Samsung Newsroom

Source: LG Newsroom



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

Google Announces New Tools for Creating Material Design Apps

In a new article this week, Google tells us that design is never done, because it's the art of continuous problem solving. Even if you optimize a user interface element for today's world, something will change that will require you to go back and work on it at a later date. To support this, Google has just announced some new tools for designers who want to collaborate with other's who practice the Material Design philosophy.

The first new tool that Google tells us about is called Gallery, and it works similar to how GitHub is currently set up, but specifically for designers. So those who are creating Material Design interfaces for applications can upload their designs, share a design that's currently on the website, and comment on them as well. The system is said to have version control as well so that you can upload new versions of the project you're currently working on.

The next Material Design tool that Google announced this week is called Stage. The goal of this tool is to help designers speed up the prototyping process. With Stage, application developers can test various elements of their project. This will also give developers a way to demonstrate how movement and animations work in applications much earlier. The quicker you can get a demo out to show your vision, the easier it is to communicate the idea to your team.

Last up, we have a new Material Design tool that Google is calling Remixer. This tool also helps with the prototyping process, but this one will actually get you a demo in your hand that you can interact with directly. Remixer will allow you to demonstrate the design of your application and even make changes to the app right on the smartphone/tablet, or even on a website.

Learn more about these new collaborative tools, and other Material Design articles on Google's Material.io website.

Source: Google Design



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

mercredi 26 octobre 2016

Google Confirms Fix for Huawei Phone/Android Auto Incompatibility is on the Way

Android Auto has remained one of Google's more low-key products these past two years since its initial announcement in 2014, but the project has slowly been expanding each year. During this year's Google I/O, the company announced that it would be working with Qualcomm to deliver a customized Snapdragon SoC aimed at car kits as well as allowing car manufacturers the ability to customize the user interface and even develop their own apps. (By the way, we're still waiting on that promised standalone Android Auto app for smartphones, Google!)

For now it seems that the only way to truly experience Android Auto is if you have one of the vehicles listed on the Android Auto website. But even then, it seems that some users are having issues connecting their Huawei device to their Android Auto-enabled vehicle. The issue, as reported multiple times on our forums, seems to be affecting the Huawei P9, P9 Lite, and P9 Plus. The apparent "incompatibility" bug could be affecting other Huawei devices, but we haven't seen reports from users on other Huawei devices as of yet. Fortunately, we now have confirmation that Google is aware of the issue and that they are working with Huawei to deliver a fix.

In the recently launched "Android Auto User Community" Google Group, one of the Android Auto Community Managers states that they've discovered an issue with some Huawei devices that marks them incompatible with Android Auto. How or why this issue occurs is not mentioned in any sort of detail, but at least they've acknowledged the issue and have promised to resolve it as soon as possible. If you've ever used Android Auto before, let us know your experience below!



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

Report: 70% of Note 7 owners will stick with Samsung

Unless you've been living under a rock these past few weeks, you've probably heard of the sometimes explosive nature of the Samsung Galaxy Note 7's battery. The fiasco has resulted in Samsung recalling the millions of phones it had shipped out: not once, but twice. Samsung has been so careful with trying to salvage what's left of the Note brand that they've even sent thermally-insulated return kits to press so any further news wouldn't blow up in their faces (quite literally). Despite having weeks to investigate the issue, the company is still unsure why their Note 7 devices keep exploding. Estimates peg that the Note 7 fiasco will cost Samsung a catastrophic $9.5 billion in lost sales. Despite these setbacks, a new report by BayStreet indicates there may be a silver lining for Samsung amidst the Note 7 chaos. According to the report, 70% of prior Galaxy Note 7 owners will remain with Samsung and will likely purchase a Samsung branded smartphone in the future.

The report continues with its findings and tackles a different question: how many Note 7 owners will abandon the Android ecosystem in favor of the premium iPhone 7 Plus? The answer is, apparently, very few. BayStreet finds that despite the fact that Note 7 owners are "aspirational" and "value premium brands", they are unlikely to favor switching to an Apple product due to their loyalty to Samsung. These findings are quite surprising, considering the fact that an exploding smartphone is quite literally one of the few things one would expect a consumer to abandon a brand over. Instead, BayStreet estimates that only 15% of total Note 7 owners (approximately 200-300k) will switch to an iOS device.

Another marketing information and analysis firm, CCS Insight, believes that Samsung will easily weather the storm of financial and reputational damage incurred by the Note 7's PR disaster. They note that the company's $70 billion war chest as well as the estimated 80 to 90 million non-Galaxy Note smartphones they will ship will more than make up for the lost revenue from the Note 7. But if there is one lesson to be learned from this mess, it's that Samsung cannot rush its future products. The Note 7 seems to be an isolated incident among Samsung products, but any repeat disaster could spell doom for Samsung's future in smartphone electronics.


Source: FierceWireless

Source: CCS Insight



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

Google Allo Updated to 2.0 With Split-Screen and Quick Reply Support

Google Allo did not quite have the start that Google had hoped for the app. In the saturated market of Instant Messaging platforms, Allo has offered very little to the average consumer that could keep the user, and his contact circles, hooked. Decouple the Assistant from Allo, and you're left with an IM app bereft of key messaging features found on other popular platforms such as Whatsapp.

Nevertheless, Google still has hope for Allo. The company has just pushed a new update to Allo which bumps up its version by a full number. Allo's Play Store listing does not yet display the change-log as the app is still rolling out, but the Google Nexus Twitter account has announced that the latest update brings Nougat split-screen support and quick-reply from notifications. However, a couple of community members have posted an unofficial change-log Allo 2.0's APKMirror page, which we've reproduced below.


What's new in Allo 2.0?

Allo 2.0 adds the following changes, in addition to presumed bug fixes and performance enhancements:

  • Support for toggling chats to monochrome
  • Direct Voice Recognition in Assistant
  • Splash Screen
  • Quick Reply Support
  • Split-screen Support
  • GIF Support in keyboard for 7.1+
  • App Shortcuts for 7.1+
  • Direct share
Monochrome Toggle Normal Chat Monochrome Chat

While the update might not seem significant enough for a full version number jump, the update does add a few useful features to the app. The addition of quick reply and split-screen support was necessary to take proper advantage of Android 7.0 Nougat's feature set. With the Pixel devices shipping with Allo pre-installed, it was important for Google to provide the same set of features and experiences that we've grown accustomed to from other apps on Nougat. The splash screen might seem like a trivial addition, but it does give users on older devices with longer loading times something pleasant to look at instead of just a blank screen while the app is loading.

You can download Allo 2.0 from the Google Play Store, however, the new update may take some time to roll out to all users. Alternatively, you can also download the update from APKMirror.

Have you tried out the new update? Let us know in the comments below!


Source: Twitter: Google Nexus



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

Google Pixel XL costs $285.75 to Manufacture – in line with Rival Smartphones

When Google finally unveiled the Pixel and Pixel XL on October 4th, many people were put off by the price tag of the two phones. While Google is no stranger to sticking a premium price tag on their products, many users hoped that the two Pixel phones would continue bucking the trend of expensive off-contract prices. Alas, this was not the case, but at least most users appear to be very satisfied with their purchase judging by early user reviews of the devices on our forums. Although many technology journalists have drawn similarities between the Pixel and iPhone in terms of price, just how true is this similarity? According to an IHS Markit teardown of the device, it appears that the cost to manufacture the Pixel XL is $285.75. At an unsubsidized price of $769 before taxes, this means that the cost-to-sales price ratio for the Pixel XL is similar to the iPhone 7 Plus and Samsung Galaxy S7 Edge.

google_pixel_xl_chart_exploded_version_two_revised


Pixel XL Price Teardown

In its press release, IHS Markit detailed how it determined the cost to manufacture the Pixel XL. The company deconstructed the Pixel XL to its base parts and then determined the approximate price point of each component, while adjusting for bulk purchasing costs. After assessing the cost of each component, IHS Markit determined that the bill of materials for the base Pixel XL model with 32GB of internal storage costs $278. Add to that a $7.75 cost to manufacture the phone in an HTC factory, and you get the $285.75 price figure.

googlepixelteardown

The company directly compares the manufacturing cost and design decisions of the Pixel XL to that of the iPhone and Samsung Galaxy S7 series, stating that the "total BOM costs for the Google Pixel XL are, not surprisingly, in line with those of other competitors, because the supply base and specs are very similar from phone to phone—whether it's an iPhone, a Galaxy-series phone or the Google Pixel XL" – Andrew Rassweiler, senior director of cost benchmarking services for IHS Markit. While Samsung is facing a tumultuous time with its Note 7 disaster, Google's Pixel XL arrives at the perfect time to challenge Samsung's dominance in the high-end Android smartphone market. It's clear that the Pixel XL was designed to compete with the upper echelon of premium flagship phones, and IHS Markit's price teardown only solidifies that point.


Source: IHS Markit



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

Android Wear 2.0 will Require Installing Apps from new Wear-based Play Store

Ian Lake is an Android Developer Advocate who has been responding to some Android Wear 2.0 questions over in the Android Wear Developers Google+ community. In one particular Google+ thread, a user inquired about the current distribution numbers for the various Android Wear platform versions. For now, Mr. Lake says that all watches are capable of running the latest version of Android Wear, so developers targeting minSdkVersion 23 in their app's manifests is fine. But then things started to get interesting as the discussion pivoted towards the upcoming Android Wear 2.0 update.

A developer asks if Android Wear 2.0 devices will support embedded APKs rather than the current method which requires installing the main application on the linked smartphone and beaming the Wear component to the smartwatch. In response to this question, Mr. Lake reveals an interesting change to Android Wear 2.0: with the upcoming wearable update, all users will need to visit the Play Store from their smartwatch in order to install an application on it. With the new update, users will no longer automatically load their smartwatch with apps from their smartphone, and will instead need to interact with their smartwatch to install new apps. In preparation for this change, Android Wear 2.0 applications will be allowed full network access and can be installed completely separately from the smartphone app.

Mr. Lake continues and tells us that Google is expanding the PlayStoreAvailability APIs for the developers who have apps that still utilize the companion app model, but he reminds developers that users will be able to download their apps independent of what's on the user's smartphone. The Play Store application for Android Wear 2.0 will show apps that you have currently installed on your phone at the top of the list for convenience, but the user will have the ability to choose whether or not they want to install it to their smartwatch.

This move is a significant departure from the original Android Wear user experience. Mr. Lake states that internal user studies show that users are not happy with the way the platform currently automatically installed apps to the smartwatch without the user's permission. This route should simplify things when the smartphone and smartwatch application are not required to be linked together. So for the Android Wear developers out there, be sure you're ready to provide support for Android Wear 2.0 as there are many changes included in the next big update for the wearable platform.

Source: Android Wear Developers

Via: 9to5Google



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

XDA Forums Live for the Xiaomi Mi Note 2 and Xiaomi Mi MIX

Xiaomi's latest flagship, the Mi Note 2, and its "concept" phone, the Mi MIX are the latest devices that can call XDA their home! Head on over to the forums to interact with other users!



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

9 Year Old Linux Kernel bug dubbed ‘Dirty Cow’ can Root every version of Android

Despite the fact that tens of thousands of users actively pore over the Linux kernel source code actively looking for security flaws, it's not unheard of for serious bugs to go unnoticed. After all, though the chances of missing something incredibly serious are lowered by having more eyes auditing the code, we're all still human and are bound to make a mistake. The mistake this time seems to be quite serious, unfortunately. A privilege-escalation exploit was recently discovered last week, and although it has already been patched in the mainline Linux kernel, the bug could potentially be exploited on nearly every Android phone on the market until each device receives the appropriate kernel patch.


Enter Dirty Cow

screenshot-dirtycow-ninja-2016-10-26-11-23-31

The privilege-escalation bug is known colloquially as the Dirty Cow exploit, though it is cataloged in the Linux kernel's bug tracker system as CVE-2016-5195. Though only discovered last week, the bug has existed within the Linux kernel's code for 9 years. Furthermore, the exploitable code is found in a section of the Linux kernel that is shipped on virtually every modern operating system built on top of the Linux kernel – that includes Android, by the way. What's worse is that the researchers who uncovered the exploit have found evidence that the exploit is being used maliciously in the real-world, so they are advising any and all vendors shipping software built on the Linux kernel to immediately patch the exploit.

Dirty Cow is itself not an exploit, but rather a vulnerability. However, this vulnerability allows for escalating the privilege of a user space process, granting it super user privileges. By exploiting this vulnerability, a malicious user space process can have unfettered root access on a victim's device. In more technical terms, the bug involves a race condition of the Linux memory duplication technique known as copy on write. By exploiting this race condition, users can gain write-access to memory mappings that are normally set to read-only. More details of the vulnerability can be gleaned from here, here, and here.

The security vulnerability is said to be rather trivial to exploit, and indeed within mere days of the vulnerability being made public a proof-of-concept privilege-escalation exploit has been demonstrated for all Android devices. Any Android device running a Linux kernel version greater than 2.6.22 (read: every single Android distribution in existence) can potentially fall victim to this proof-of-concept exploit. Though the proof-of-concept exploit does not actually attain root access, attacking the system using this vulnerability makes that quite simple. In an e-mail sent to ArsTechnica, Phil Oester, a Linux kernel developer who is cataloging known real-world exploits of Dirty Cow on his website had this to say about the bug:

Any user can become root in < 5 seconds in my testing, very reliably. Scary stuff.

The vulnerability is easiest exploited with local access to a system such as shell accounts. Less trivially, any web server/application vulnerability which allows the attacker to upload a file to the impacted system and execute it also works.

The particular exploit which was uploaded to my system was compiled with GCC 4.8.5 released 20150623, though this should not imply that the vulnerability was not available earlier than that date given its longevity. As to who is being targeted, anyone running Linux on a web facing server is vulnerable.

For the past few years, I have been capturing all inbound traffic to my webservers for forensic analysis. This practice has proved invaluable on numerous occasions, and I would recommend it to all admins. In this case, I was able to extract the uploaded binary from those captures to analyze its behavior, and escalate to the appropriate Linux kernel maintainers.

After further work by developers on demonstrating the effectiveness of exploiting Dirty Cow on Android, one developer was able to successfully root his HTC device within seconds by exploiting the vulnerability. We at XDA generally welcome the ability for users to acquire root access, but we do not celebrate the existence of root exploits such as this, especially one which is so widespread and potentially incredibly dangerous to end users. To give you an idea of how dangerous Dirty Cow can be in the wild, YouTuber Computerphile put together a quick video demonstrating the potential malicious attack vectors that hackers can use to quietly attain root access on your device.


Source: ArsTechnica [1]

Source: ArsTechnica [2]



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

The XDA Crew at the Big Android BBQ

Have you ever wondered who is behind the XDA-Developers website? Here are some of the people that work to create great content for the community and keep everything running smoothly. Check out this video to see all the XDA people that attended the BBQ.

There were a few awesome booths this year at the Big Android BBQ. We took a tour of the event and checked out some of the best booths.

We had a lot of fun at the Big Android BBQ which was made possible by our sponsor UMi. Their latest phone, the UMi plus, has 4GB RAM, a 4,000mAh battery, and stock Android for $149. Click here to check it out!
umidigi.com

 



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

Samsung Pay to Launch in 3 New Countries, New Features Coming

Samsung Pay was able to jump ahead of the other mobile payment services in part because Samsung acquired LoopPay back in February of last year. They ended up announcing Samsung Pay the very next month, but the service wasn't launched until August. Samsung Pay was first introduced in both the United States as well as South Korea and Samsung has been working hard to get it widely adopted ever since.

The company has had an advantage over other mobile payment services because of the technology it uses. Instead of requiring the payment terminal to be upgraded for contactless payments, Samsung Pay will actually work with payment systems that only support magnetic stripes. Samsung is able to do this by transmitting the credit card data to the terminal's swipe slot using an an electromagnetic field.

Samsung has just announced that Samsung Pay will be launching in Malaysia, Russia and Thailand by the end of the year. This brings the total number of countries that Samsung Pay is available in up to 10. Similarly to the announcement that Google recently made with Android Pay, Samsung Pay has also partnered up with MasterCard to offer a simplified and fast online payment and checkout option.

In this latest announcement, Samsung also talked about three new features that will be coming to their mobile payment service in the near future. Starting in November, users of Samsung Pay will be able to find deals from retail locations that are close to them. Another feature coming in November is the ability to use Samsung Pay for in-app payments thanks to a partnership with select merchants. Samsung say this feature is coming to Velocity, Raise, Fancy, Hello Vino, Wish, Touch of Modern and promises that more will be coming too.

With the company's latest financial partners (Capital One and USAA), Samsung Pay now supports over 500 banks and credit unions that represent over 85% of the debit and credit card market in the United States.

Source: Samsung Newsroom



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

HTC’s Q3 Financial Results Reveal $57 Million Loss

Since the glory days of the HTC Evo 4G, HTC has failed to make significant waves with most of their smartphone products. Even the much venerated HTC One was unable to dethrone its Samsung flagship counterpart. Continuing on that downward trend, it seems HTC is still struggling to recover from the financial issues they've been having all year. HTC has been able to slow down their continual revenue loss each quarter, but their efforts haven't been enough to actually bring a net profit to the company. Although, HTC fans and investors can still point to the fact that there is a slight upward trend in revenue each quarter when they discuss how the company is improving the business.

For the third quarter of 2016, HTC was able to bring in $700 million in overall revenue. This is good news for the company because the earnings are actually up 18% when compared to the second quarter of this year. The overall revenue for HTC in the third quarter of 2016 is also up by 4% when compared to the third quarter last year. HTC attributes this short-term success due to how well the company did in September when revenue was up 42% compared to August, and up 31% compared to last September.

Unfortunately, HTC was still unable to bring in any profits for the quarter. It's unclear exactly where all of the money is distributed, but it's possible they are investing in future technology, future designs, or simply pumping it into the company's marketing budget. We have been hearing rumors about the HTC Ocean series of phones and how HTC is attempting to innovate when it comes to how we interact with our smartphones, so it's possible that they are betting big on some unannounced project.

Still, for the third quarter of this year, HTC actually lost $63 million, which adjusts to be $57 million post-taxes. This is much better performance than we have seen from HTC in the past, but there still isn't any profit to be found. The company will either need to bring down costs somewhere, or they will need a new product that boosts sales to finally be able to take them out of the red.

Source: HTC (PDF)



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

Google: A Fix for the Pixel & Pixel XL Camera Flare is Coming

At the launch event for the Google Pixel and Pixel XL, Google advertised that its camera would be the best camera currently available on any smartphone. They backed up their claim by citing a stellar early review score from DxOMark, but some people were still skeptical. As early hands-on reviews started going live from various Android and technology publications, it became obvious that Google was definitely onto something with the camera optimizations they had touted.

The camera on the Pixel phones is easily one of the best we've ever seen on a smartphone and many feel that it has finally knocked the iPhone off its throne. However, as time went on and as more people started using their phones on a daily basis, one issue repeatedly surfaced. Some users began to notice a lens flare/halo effect in some of their photos. This issue was even discussed here in our forums, and many others across the Internet who are using it have also noticed similar artifacts in their photos.

This issue was raised in Google's official product forums within the newly launched Pixel User Community Forums and a Google employee confirmed they are aware of the issue. At first, Isaac begins talking about how the flare is a property of all camera lenses, but then moves on to mention that the shape, color, amount, etc. of the flare is attributed to a large number of different parameters when it comes to the lens structure and inclement light.

However, the Googler states that the issue will be fixed due to the fact that many users find the halo effect undesirable. Isaac says they are working on some algorithms that will be able to recognize the halo/arc flare and will then subtract it from the image entirely. We're told that a software update to resolve the issue is coming "in the next few weeks," but that users will need to use HDR+ to see the benefits of the update.

In the meantime, he also states that users should not send the phone in for an RMA and that all Pixel phones will have the same flare characteristics.

Source: Pixel User Community



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

Bootloader Unlock Achieved on Verizon-based Google Pixel

Back when the Google Pixel duo were still in the leak stages, there were reports that the Verizon based Pixel devices would come with their bootloaders locked, and with no way to officially unlock them in a straightforward manner. This created an important distinction between the carrier-unlocked Pixel as it was sold directly from Google, and the carrier-locked Pixel sold from Verizon, despite having virtually no differences in hardware.

In case you bought the Pixel from Verizon despite their past history with locked bootloaders, here is a bit of good news. The Firewater dev team has announced that they have managed to unlock the bootloader on the Verizon variant of the Google Pixel.

Before you jump on and celebrate, do keep in mind that the dev team, known famously for their SunShine unlocks and S-Off solutions for HTC devices, has not yet released the unlock for the device. There is a "maybe" attached to their announcement, indicating that there is a possibility that this does not get released for the public at large.

There could be a few reasons why one would prefer buying the device from Verizon rather than from Google. One of the main draws for people often is the trade-in value that they receive when they hand in over their older devices, which can be as high as $200. This removes the hassle of selling a device which otherwise would not command such a high value in the second-hand market. The other reason often is staggered payment plans, but since Google is also offering the same with the Pixels in the USA, this does not stand as strongly.

The Pixel devices on Verizon do come with bloatware, but the bloatware can be disabled and uninstalled. Early reports mentioned that the Verizon based devices would have their updates routed through Verizon, though it was later clarified that both the Verizon and non-Verizon Pixels would receive updates at the same time. The locked bootloader still remains a valid concern for XDA readers, that is until the devs release their unlock solutions.

The reasons to not buy the Google Pixel from Verizon continue to shrink down. Still, I would personally avoid Verizon, just out of principle.

What are your thoughts on this development? Did you purchase your Pixel from Google, or from Verizon? Let us know in the comments below!

Source: Twitter: Firewater Devs



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

mardi 25 octobre 2016

Join XDA at Droidcon UK & London Hack Weekend!

The largest Android developer conference in Europe is once again almost upon us as Droidcon UK returns to the Business Design Centre in London and XDA is sponsoring the conference. The event is a great opportunity to meet some of the biggest names in the industry, listen to some inspiring talks, enter to win loads of prizes and ask any questions you may have for the XDA staff, this year we will also be joined at the booth by staff from Honor. Attending the event for XDA this year are:

Jeremy – OEM Relations Admin @jerdogxda TK - XDA TV - @tkdsl8655 Mathew - XDA Portal & Social Media - @mbloomer04

The event will be a lot of fun as always and with some great prizes up for grabs including Nextbit Robins and Aukey accessories be sure to drop by the XDA booth between talks. You can find the full programme here and just a few of the talks here:
screenshot-2016-10-26-at-01-21-46

Keynote: VR and AR – Technologies 40,000 years in the making

"Virtual and Augmented reality are at once both sparkly brand new, and descendants of humanity's most ancient arts. Google's Chief Game Designer will bring some perspective to the origins of these technologies, why they matter to us in terms of evolution and storytelling, and give an overview of how Google is now supporting them with tech like Android N, Tango, Daydream, and Spotlight Stories."

screenshot-2016-10-26-at-02-57-06

Android Application Security, The Right Way

"In this talk you will discover the typical attack surfaces of an Android application. We cover the importance of code protection, implementing secure coding practices, strong crypto implementations, executing in a secure environment and hardening network communications. You will walk away with best practices and common pitfalls to create secure applications."

screenshot-2016-10-26-at-01-23-03

Optimising apps built for the next billion users

"More users are unable to make it through the day on one full charge on their device and have to rely on their battery packs. Battery consumption, which is a side effect of sub optimal usage of resources, is quickly becoming one of the main reasons why applications are being uninstalled by users.

In developing nations where the next billions user are, things like network conditions and types of devices available are quite different when compared to developed nations. One has to factor in aggressive optimisation techniques to ensure that consumption of resources is kept low."

screenshot-2016-08-23-at-17-35-05

Building a framework with Clean Architecture

"The complexity of many Android apps are already surpassing that which was previously only the domain of desktop and enterprise software. Gone are the days of the simple app which just acts as a thin layer on top of your backend (well for us it is at least). We've grown to expect features such as offline support where in some cases complex business logic must be handled client side. It's become clear that you need architectures to match this complexity. While there have been many attempts to solve this challenge, over the last couple of years, the concept of Clean Architecture has gotten more and more attention in the Android developer community."


Droidcon London Hack Weekend

But the fun doesn't end there! Even after the talks have ended there is still plenty to get involved with as the Droidcon London Hack Weekend begins. Running from Friday 28th till Sunday 30th at CodeNode, the annual Android hackathon gives you a chance to take part in team challenges for some great prizes, while getting the chance to try out the latest tech and learn a thing or two. Entry is free, all you have to do is register here.

dsc01020 dsc01073 dsc01062

Are you attending Droidcon UK this year? Leave a comment below!



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

BlackBerry Launches the DTEK60, Available for $499

BlackBerry is determined to remain in the smartphone market for as long as it can. In this endeavor, the company also had to take the tough decision to drop its hardware division, and concentrate solely on its security and enterprise solutions, one of their biggest USP's.

The BlackBerry DTEK60 is the second smartphone that comes out of their collaborative relationship with TCL, which is known for its Alcatel sub-branding in the Western markets. Just like the predecessor DTEK50, the DTEK60 is based off a reference design from Alcatel, and in this case, the device closely resembles the Alcatel Idol 4S. BlackBerry has upgraded a few specs off the spec sheet, making the DTEK60 a much more competitive device against the flagships of 2016.

The DTEK60 bears a metallic mid frame, sandwiched between glass on the front and back of the device. The device does have a much more premium appeal to it than its preceding DTEK device, but unfortunately, it also has a noticeably large camera hump on the back.

The DTEK60 comes with a 5.5″ QHD AMOLED display, and is powered by the still very competitive Qualcomm Snapdragon 820 SoC. You get 4GB of RAM and 32GB of internal storage, along with the option to expand it further via a microsd card as well. The phone comes with a 3000 mAh battery with Quick Charge 3.0 support via the USB Type-C port. The fingeprint sensor finds space on the back of the device, and there is also a programmable button on the side. A 21MP rear shooter with 4K video recording and an 8MP front shooter complete the camera setup on the device.

The BlackBerry DTEK60 comes with Android 6.0 Marshmallow out-of-the-box, although Nougat is already planned for it. Devices from BlackBerry are amongst the best you could purchase in the Android market from a security standpoint, as the company has taken Android's security updates very seriously (something we can appreciate). The hardened security of the device works best for Enterprise users, but this also means that the devices see absolutely no third-party development. The BlackBerry Priv is yet to be rooted, so if you are looking for a phone that can be rooted, the DTEK60 should be amongst your absolute last choices.

400x500_argon_softshell_na_eng

The BlackBerry DTEK60 is available for purchase from BlackBerry's official website for $499. If you purchase the device before November 8th, BlackBerry will also drop in a Soft Shell case and a Rapid Charger as part of the deal (depending on markets).

What are your thoughts on the BlackBerry DTEK60? Let us know in the comments below!



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

4G LTE Vulnerability Enables Eavesdropping on Conversations and all Data Traffic

For the privacy-minded readers on our forums, you probably steer clear of any open WiFi hotspot while you're out and about. If you're one of the lucky few who owns a select Nexus or Pixel device that is supported by Google's WiFi Assistant, then maybe you aren't so worried about using an unsecured network. But for the rest of us, we rely heavily on our carrier's 4G network to route any important financial, educational, or private data over the Internet. Unfortunately, though, it appears that our 4G LTE connection might not be as secure as we were previously led to believe. Wanqiao Zhang, a Chinese network security researcher from Qihoo 360, recently held a presentation at DEFCON 24 in August of this year describing the LTE vulnerability.

Source:

Source: Wanqiao Zhang

In the research paper, the team describes a method of forcing a targeted smartphone off of its LTE network and onto an unsecured, compromised network. The attack involves collecting the LTE device's IMSI and then tricking the device into connecting to a fake LTE network. Once the victim has connected to the compromised network, the attacker is able to perform a variety of malicious acts, including denial of service, redirection of calls/texts, or at its worst even sniffing on all voice and data traffic. Her team's demo specifically targeted the FDD-LTE networks that are currently operating in Britain, the United States, and Australia. However, Zhang says this type of attack is possible on any LTE network in the world, including TDD-LTE networks more commonly found in many Asian countries.

Sadly, the regulatory body responsible for overseeing and enforcing LTE standards had previously acknowledged this vulnerability all the way back in 2006 when they acknowledged the possibility of Zhang's man-in-the-middle attack. Recently in May, the 3GPP proposed a potential solution to the security vulnerability: refusing one-way authentication and dropping encryption downgrade requests from base stations. These measures would prevent a malicious femtocell from unilaterally hijacking your phone and downgrading its network security measures.

This vulnerability has not received much attention until security researchers wrote a paper about it last year (PDF). It was shortly after this paper was published that we saw the ACLU obtain documents that described the government's Stingray project had identical functionalities. Many still don't know exactly how the Stingray tracking devices actually operate, although people have started to draw similarities between the technology and the recently researched LTE vulnerability.

For those who want to keep their data and communications private, a VPN which uses OpenVPN and its TLS protocol will be able to keep your data private. You'll want to stay away from VPNs that use PPTP/L2TP/SOCKS connection methods as those could still be vulnerable to attacks. It's been over 10 years since the 3GPP was made aware of this issue and they have yet to implement updated LTE protocols to remedy this security hole. With readily available hardware that can pull off these attacks now, however, it will be up to you to keep your data private.

Source: The Register



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

Xiaomi Unveils The Mi Note 2, The Mi MIX Concept Phone and Mi VR

It has been an eventful day for Xiaomi, as the company took the wraps off several products at an event in Beijing. While the Mi Note 2 is what most people were expecting out of the event, Xiaomi did surprise all by releasing their own VR headset called the Mi VR, and unveiling a "concept phone" called the Mi MIX.

Xiaomi Mi Note 2

Starting off with the Mi Note 2, the device is just about everything that the leaks built it up to be (but with a single rear camera). The Mi Note 2 builds up on the curved glass back of its predecessor Mi Note, and brings the curves onto the front sides as well by making use of a flexible OLED display. The mid-frame of the device is made of aluminum, and the back is made of glass.

14702329_1184628468239411_5771718980858656671_n

When it comes to specs, the Mi Note 2 comes with a 5.7″ FHD OLED display, curved on the sides. The device is powered by the Qualcomm Snapdragon 821 SoC along with the Adreno 530 GPU. The device comes in two RAM (LPDDR4) + Storage (UFS 2.0) variants: 4GB + 64GB and 6GB + 128GB. There is a third variant as well, which is called the Global 4G+ variant although its memory specs are the same as the top variant. There is no support for microsd expandability on the device, though.

For extras, the Mi Note 2 has support for Qualcomm AQSTIC on-chip decoding with support up to 192kHz/24bit decoding. There is full NFC support, Bluetooth 4.2, 3.5mm headphone jack, fingerprint sensor (integrated on the home button on the front) and an IR Blaster, among other features. The Mi Note 2 also has a USB Type-C port, and a 4,070 mAh battery with Quick Charge 3.0 support.

Xiaomi Mi Note 2

For the camera, the Mi Note 2 bears a single rear camera, with the 23MP Sony Exmor RS IMX318 sensor with an aperture of f/2.0 and support for EIS and PDAF. The front camera on the Mi Note 2 is the 8MP Sony Exmor RS IMX268 with an aperture of f/2.0.

The most interesting part about the Mi Note is the band support on the device. The device supports dual nano-SIMs, but 4G LTE is supported in the first SIM slot only. This is the first Xiaomi device with Global network support as it has support for 37 global bands, including 22 for LTE. However, although this information is not confirmed from Xiaomi, we suspect that the global band support is present on the aptly named "Global 4G+" variant only.

14695602_1184649404903984_210181048818830875_n

The Xiaomi Mi Note 2 will be available in Silver and Black colors. The Mi Note 2 will cost CNY 2,799 (~$415) for the base 4GB/64GB variant, CNY 3,299 (~$490) for the 6GB/128GB variant and CNY 3,499 (~$520) for the Global 4G+ variant.

The question then remains, when can you buy the Xiaomi Mi Note 2? The Mi Note 2 will be available from the first of November in China. Availability and pricing of the device beyond China is unknown at this stage. Since the band support on this device is rightfully suited for using around the world, we strongly suspect that this will be the first flagship smartphone that Xiaomi launches in the USA.

Mi MIX

The Mi MIX is an interesting device. Xiaomi is calling this a "concept phone", which is a very curious term to use for a device that is actually in production and scheduled to go on sale in the very near future, and that too, at a price that is not obscenely expensive.

Xiaomi Mi MIX

Xiaomi is using the Mi MIX as a ground for giving consumers a taste of the innovation processes that they are undertaking. The Mi MIX is a virtually bezel-less device, with a 6.4″ edgeless FHD OLED display with an astonishing 91.3% screen-to-body ratio. The device frame and even the buttons are made of ceramic. The device also does not use any adhesives on the inside, relying on just connectors to hold everything in place.

Since the front is almost entirely dominated by the display, Xiaomi had to move around or innovate around a few parts like the front camera, the proximity sensor and the earpiece. The earpiece has been removed in favor of a Pizoelectric ceramic unit, that converts the sound into mechanical energy which the phone's metallic frame converts into sound. The infrared-based proximity sensor is replaced by an ultrasonic proximity sensor. The front camera module has been shrunk down and moved to the bottom right corner, though we doubt the practicality of the positioning.

Xiaomi Mi MIX Xiaomi Mi MIX

The Mi MIX also gets rid of hardware-based keys in favor of software keys. The fingerprint scanner finds its place on the back of the device. The usual extras with Xiaomi flagships, like the IR Blaster, full NFC support, USB Type-C port and the 3.5mm headphone jack are also present on the MIX.

On the spec ends, the Xiaomi Mi MIX is no slouch either, which is what happens otherwise with niche and unique devices. The device brings the latest Qualcomm Snapdragon 821 SoC and comes in two RAM (LPDDR4) + Storage (UFS 2.0) variants — 4GB + 128GB and 6GB + 256GB. There's a hefty 4,400 mAh battery with Quick Charge 3.0 support. The camera setup consists of a 16MP rear camera and a 5MP front camera.

Xiaomi Mi MIX

The Mi MIX comes only in black color, and will be available for purchase in China from 4th November. The device will cost CNY 3,499 (~$520) for the base 4GB + 128GB variant, while the higher-end 6GB + 256GB variant will cost CNY 3,999 (~$590). The higher-end variant will also come with an 18k gold trim around the camera lens and fingerprint sensor. There is no word on global availability, and since this is a "concept" device, we would not be surprised if this remains restricted to China.

Mi VR

Xiaomi also made use of the event to unveil the second gen of their own VR headset. Dubbed the Mi VR, the headset builds up on the Mi VR Play by adding in a built-in dedicated motion sensor. The device also comes with a 9-axis inertial motion controller.

Mi VR

The Mi VR is compatible with the Mi Note 2, Mi 5s, Mi 5s Plus and the Mi 5. The device is priced at CNY 199, which comes out to be around $30.


The Xiaomi Mi Note 2 and the Xiaomi Mi MIX were the main highlights of the event. We are particularly excited about the Mi Note 2, thanks a lot to its global band support. With LeEco already entering the US market recently, it was just a matter of time before Xiaomi rolled up its sleeves.

What are your thoughts on the new Xiaomi launches? Do you look forward to purchasing any of these devices? Let us know in the comments below!



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