LightBlog

jeudi 22 décembre 2016

OnePlus 2 OTA Update Brings OxygenOS 3.5.5 to the Device

OnePlus has announced they are starting to roll out a new OTA update to the OnePlus 2. This new update will bring your device up to version 3.5.5 of OxygenOS, and it comes with a lot of new features and changes. The company warns users that updating to 3.5.5 can cause issues with things like WiFi and network connectivity, as well as the fingerprint sensor if the person tries to downgrade back to version 3.1.0.

It is possible to downgrade to 3.1.0 without issue, but you'll need to use a special 3.1.0 downgrading version and flashing tool. Doing this will wipe all of the data from your phone. The main changes with this update are the new features that OnePlus has added. We're told that this update enables VoLTE functionality for select carriers but doesn't go into detail about which carriers and that it also comes with an App Lock feature.

They've added a Battery Saving Mode, a Gaming Mode, and put in some new options for the Alert Slider within the settings. The update comes with a redesigned volume adjustment bar, adds in some optimizations for their Shelf feature, and comes with an updated user interface for the clock application. We're also told that the Clock, Calculator, and Messages applications will be replaced with stock OnePlus apps unless you have updated the corresponding Google apps.

If this is the case for you, and you want to continue using Google's apps, then you can download them from the Play Store. This new OTA update brings new UI changes to OxygenOS as a whole, they've increased the stability, fixed a number of bugs, and included December's security patches too. OnePlus also warns that this update will reset "many" of the phone's settings (like device name, ring tones, accent colors, etc).

So you'll want to go back through your settings and adjust these options if you notice something is different from before.

Source: OnePlus



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

Rumor Reveals Specs of a 4.6″ Flagship from Xiaomi

Over the years, the screen size of smartphones has gotten bigger and bigger. A few years back, smartphone makers were ridiculed for releasing a product with a display that was 5″ or bigger. Some have enjoyed this transition while others merely put up with it. Then there are some within the community who outright loathe the trend and wish things could go back to the way they used to be.

Granted, there have been some smartphone OEMs who release smartphones with a screen smaller than 5 inches. However, the majority of these devices have low-end, or even mid-range specs, and do not get the software support that they deserve. Sony filled this gap with the compact series of their Xperia line, but even changed this year with the release of the Xperia X Compact and it's Snapdragon 650 SoC. Some people just want the latest hardware in their device and it's a market that has been largely ignored for years. A new rumor from China suggests Xiaomi may be looking to fill that void with a smartphone called the Mi S. If true, this device will have a 4.6″ display, Snapdragon 821 SoC, 4GB of RAM, and 128GB of UFS 2.0 internal storage.

The rumors say the dimension will be 128.3mm, 64.2mm and 8.2mm, with a 12MP Sony IMX378 sensor for the rear camera and a 4MP front-facing camera. The images show a fingerprint scanner in the bottom bezel of the display, they mention it has USB Type-C with Quick Charge 3.0 technology, and a 2,600mAh capacity battery. That battery size might be on the small with today's standard, but we have to remember that it only has a 4.6″ display.

Does this sound like a smartphone you would buy (even if you had to get one from a reseller)?

Source: GizmoChina



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

Flashtool for Sony Updated to v0.9.23.0 with Support for Nougat FTF

Users who have owned Sony devices and done any sort of software tinkering with them would have obviously heard of XDA Recognized Developer Androxyde's Flashtool. For the uninitiated, Flashtool offers Sony device owners the freedom to move around on stock packages for both upgrades and downgrades, and was once used as a means of flashing modified "custom" ROMs as well (before recoveries gained their popularity).

Flashtool's popularity stems from its use cases as well as the sheer number of device it supports. The PC-based software works across all Sony phones, ranging from the Xperia X10 that was released in 2009 all the way to the Xperia Z Ultra and newer. Now, the use case for Flashtool has added another milestone in the form of support for Nougat FTF flashing.

Changelog for the Flashtool v0.9.23.0 update is as follows:

  • Fix for Nougat sin files parsing. FT should now be able to flash Nougat FTF
  • TA raw backup for all devices exposed to dirtycow exploit. TA backup using dirtycow by rayman
  • More accurate USB log parser for creating fsc scripts
  • In advanced mode, some new TA features: Viewer and custom TA file generator or flashing
  • Added a new device property to tell if fsc is mandatory or not. Check of this property is done before flashing

In addition to all of its flashing use case, Flashtool also aids in TA backups. TA backups are usually done to protect the DRM keys on Sony devices, which are otherwise lost irretrievably if a user decides to unlock the bootloader. The update uses the recent DirtyCow exploit to allow for TA partition backups.

To download the most recent Flashtool, head on over to its website homepage. Additionally, you can also visit the forum thread. Since the software is open source, you can aso check out its sources over on Github.

Have you used Flashtool before? What has your experience been with the software? Let us know in the comments below!



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

mercredi 21 décembre 2016

2016 in Review: What are the Best Mobile Games of 2016?

As we enter the final days of the year, it's time to get your opinion on all the events, news, releases and controversies that we witnessed so far in 2016. We saw several new games in the headlines this year — some for captivating the masses, and some for failing to live up to expectations.

So, our question to you is,

What are the best games os 2016? What appeals to you in these games? Do you like them for their artwork and style, their concept and game mechanics, their approach to premium content, or simply because they are enjoyable or popular?

Let us know in the comments below!



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

Onsite at Huawei: How OEMs Test their Devices During the Design Phase

Honor has been around for three years and already sold over 100 million devices worldwide. With the Honor 7, 5x, and 8 bringing brand awareness to Europe and the U.S., they are beginning to make waves with their devices. Independent, Open Source Development on the 5X and 8 has been coming along over the last year, and with new devices looming, it's looking like 2017 could be a great year for Honor.

This past week was Honor's third anniversary, and I was privileged to be able to head to Honor's HQ in Shenzhen as part of their "Honorversary" celebrations. One of the key events involved visiting the HQ of Huawei, Honor's parent company, and taking a look at their mobile operations. A highlight of the day was getting access to Huawei's Environmental & Reliability Lab.

One of the advantages for a company like Honor is having a solid, reputable parent company which grants them access to the full range of resources. In the testing lab we were walked through the processes that each phone goes through during its design phase, and it is certainly quite extensivev–vthough without having been to another testing lab it's hard to know how their testing matches up with their competitors. When asked about that very thing, the confirmation was that Huawei (and Honor) meet or exceed the industry standards on everything.

Seeing as the processes and machinery and such are all very private, we were unable to take pictures, so I will relate some of the key points and tests. I should also make this disclaimer that the names of these tests are not exact, but instead convey the thought or purpose for the test.


Tumble Test, aka Run and Jump Test

This test had a phone in a rotating cylinder which simulates a phone falling out of your grasp while you're running, or the phone tumbling down stairs. The structure of the phone is tested to make sure that it remains intact after the test cycle, consisting of over being drop over a hundred times from a height of 1 meter in the cylinder.

Throw Down Test

From a height of 1 meter a phone is forcefully dropped, similar to throwing your phone down in anger at Verizon or AT&T requesting a bootloader unlock for your favorite device. A machine holds the phone in its vise-like grip and then forcefully accelerates it towards the ground. After each test, a test engineer makes sure the device still works — if it does the device, passes. Each side and corner of the device is tested, resulting in 12 total tests.

Friction Test

The goal here is to find out the friction a device encounters when in a woman's purse or in the pockets of coats or jeans. It's another cylinder test, similar to a clothes dryer, that contains multiple items like fine grains of sand, coins, etc. As the cylinder is rotated, over two thousand times, the phone comes in contact with these items and as collisions happen, it encounters friction and impact. The phone is then examined for scratches and/or anything that might affect how the phone works or any negative results of friction.

Sit Test

A phone is placed into the back pocket of a pair of jeans and then the machine presses down with a 25kg force into the center of the pocket causing it to bend. This is done over two thousand times and then the device is checked to see if it has bent, like an iPhone 6, or if it has retained its form.

Charger Plug Test

This test involves a phone being placed flat as the machine tests the plug mating of the USB connector into the phone over five thousand times. What the engineers are looking for is the socket's strength and connection to the internal board.

USB Cable Test

When you plug your USB cable into the phone, oftentimes you can be putting stress on the cable itself. This test takes the cable and twists it multiple angles, from 30 to 180 degrees and to the right and left, all while being plugged in. If the cable is not found to still be working, after ten thousand tests at each angle, it is discarded.

Power Button and Touchscreen Button Test

In order to make sure that the power button on the side of the phone turns on the screen and then that the touchscreen works to unlock the phone, the combination is tested one million times over 12-13 days.

Extreme Environment Tests

Devices are placed into large machines which control the temperature ranges from -22°C to 55°C and -40°C to 70°C over 2 days. This ensures that the devices will still work after being subjected to drastically-changing temperatures. Other machines control exposing the devices to 96 hours of humidity, while others control the atmospheric pressure.

Adapter Burn-in Test

This will test how well the adapters can survive while being used with different voltages. Two hundred and eighty eight adapters are tested in temperatures of 40°C to 70°C for 480 days, and if an adapter fails for any reason while being used during the tests it is discarded.

Solar Radiation Test

The devices are tested while sitting in a chamber where solar radiation is applied at a temperature of 40°C for 3 days. They are looking for discoloration of the surface of the devices or expansion of the casings.


In conclusion, one thing that really stood out to me was the lengths that both Huawei and Honor go to in order to ensure that the devices you get in your hand meet the most rigorous standards possible — and it's likely that the same case applies to other big OEMs as well. A story was told by the CEO of Honor, George Zhao, of a time a few years back where the tires on one of their device transports caught fire along with $20mil in devices inside. No one was hurt, and the devices were saved and not damaged, but Honor made the decision to destroy the entire shipment instead of possibly putting someone in danger or negatively impacting their image by shipping them out.

It was a very interesting time, and one I was fortunate to have been able to attend. Please let us know your thoughts in the comments below!



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

Some Nexus 6Ps are Shutting Down at Early Battery Percentages

The Huawei built Nexus 6P was the final flagship in the Google Nexus program before the Nexus program was unceremoniously killed off in favor of the Google Pixel.

Barely over a year old, the Nexus 6P is still a solid smartphone capable of running on the latest version of Android Nougat that many users will continue to use for months to come. But as time goes on, users may start to notice issues pop up that they never used to face. Of course, not every user will be affected by certain bugs, but sometimes the bug can be quite debilitating to the functionality of an older smartphone.

In this instance, a bug is affecting certain Nexus 6P smartphones causing the phone to shut down at early battery percentages. People are reporting that their smartphones have been rebooting at percentages as low as 15% or as high as 60%. It is obvious why this is problematic – a phone shutting down at seemingly random, potentially inopportune times can put a damper one's plans for the day. In my own experience, I've seen my Nexus 6P randomly reboot at around the 15% mark, but I chalked it up to running a custom kernel with some of my own configurations. But when I compare my experiences to that of what others on forums have been reporting, I believe that this bug may be affecting my own Nexus 6P as well.

Some users on Reddit and our own forums have been reporting this issue for quite some time, and it appears that the issue is more widespread than initially believed. The cause of this bug is unknown at this moment. Some users speculate that the issue is hardware related, while some blame the Android Nougat update for introducing the bug. An open issue was created on the AOSP Issue Tracker last month which has since been starred by over 1200 users and has had dozens of comments corroborating the bug's existence. All that's left is to wait and see if Google can determine the cause of the bug, which can seriously hamper the use of one's Nexus 6P.


Source: /r/Nexus6P on Reddit



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

Google Employee Suing Google for its Confidentiality Policies

An anonymous Google employee has filed a lawsuit in the California Superior Court in San Francisco claiming that Google's confidentiality policies are essentially a "spying program".

The man behind the lawsuit believes these policies violate the state of California's own labor laws, and they're trying to get something done about it. It's possible that this is the same employee who filed a complaint with the National Labor Relations Board earlier this year the same policies.

Google states these policies are currently in place in an attempt to prevent potentially damaging information from being leaked. These confidentiality policies go as far as to prohibit employees from even speaking about illegal activities within the company to lawyers. Instead, they reportedly encourage them to report other employees to higher ups within the company if they suspect someone of suspicious behavior (including allegedly just asking detailed questions about projects).

Google's own Code of Conduct states it classifies "everything at Google" as confidential information. Employees aren't allowed to write a novel about working at a large Silicon Valley corporation without getting final draft approval from someone within the company. Though it seems like the lawsuit is focused more on not being able to talk about specific legal violations to regulators and law enforcement agencies.

Our anonymous John/Jane Doe even used the Securities and Exchange Commission guideline as an example which prohibits companies from stopping their employees from reporting these violations. If Google is found guilty of violating California's labor law, they could be fined up to $100 for each of the 12 violations for each employee they have on its campus. With over 61,000 employees right now, this fine could be as high as $3.8 billion since it can be doubled (for up to a year) if the violations persisted past a single pay period.


Source: The Information



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