LightBlog

jeudi 13 octobre 2016

LG to Launch Their 15W Wireless Charger This Month

Back in March, LG Innotek initially announced they were working on a 15W wireless charger. The company told us they would begin manufacturing these modules for smartphones and vehicle chargers sometime this year. It seems LG has been hard at work on this accessory as the company has just announced they will begin selling this product in North America, Europe, and Australia sometime this month.

At the time of its announcement earlier this year, we were told this wireless charger would support both WPC 15W and PMA 5W.  However, the press release for the product now does not mention PMA support at all. Instead, it just mentions that it meets the standards laid out by the Wireless Power Consortium (which is the organization that brought us Qi wireless charging). So we should not expect the charger to work with PMA (Power Matters Alliance) devices at this time.

Typical wireless chargers use a 5W charging module, but this new Quick Wireless Charging Pad from LG will use a 15W module. The company says it will be able to charge a battery to 50% within 30 minutes. Oddly enough, LG doesn't give us a battery capacity when talking about this statistic though. As a reference point, we've seen Samsung's fast wireless charger completely fill the 3,000mAh capacity battery of the Galaxy S7 in about 2 hours.

LG Innotek says they're focused on keeping heat generation down as well. They understand that heating the battery up too much can cause degradation of the battery as well as making the battery more susceptible to explosion. To combat this, the company says they've embedded a sensor into the Quick Wireless Charging Pad to monitor the temperature of the smartphone. If it reaches a certain limit, then it will stop charging the device for a few moments.

Once the device reaches the desired temperature again, the Quick Wireless Charging Pad from LG will go back to charging the battery.

Source: LG Innotek



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

mercredi 12 octobre 2016

Want a ZTE Flagship with Stock Android? Vote for it in ZTE’s Project CSX

We've talked about ZTE's Project CSX before. For a recap, ZTE is crowd-sourcing ideas on what its next smartphone should be. The ideas will be collected from the public, and after voting, the most popular of these goes on the road towards becoming a reality.

Now we've come to the point where the ideas have been submitted and the first few rounds of shortlisting have taken place. Here are the final 5 contenders on what ZTE should work next:

  1. Eye Tracking, Self-Adhesive Phone: A true hands-free experience that allows you to scroll up or down based on eye movement and a self-adhesive back that would allow the phone to stick to a wall or flat surface.
  2. Intelligent Smartphone Covers: Expend the power of a smartphone through functional cases such as a gamepad, stylus or e-ink flip cover.
  3. Powerglove: An exo-glove that controls your fingers for use in learning or rehabilitation settings, all powered by your Android smartphone.
  4. Stock Android Flagship Phone: The next generation of Axon to include stock Android as well as improvement in performance and camera.
  5. VR-Interactive Diving Mask: A waterproof VR mask allows you to swim in a pool or lake and feel like you're in the open ocean.

While all ideas do seem innovative in their own right, the one that piqued our interest (and we guess it would pique yours too, since you are reading this on XDA-Developers) was the 4th idea. Of all the five, this seems the most feasible, one that would still be within the realms of smartphone conventionality so as to not feel like an experiment to the consumer, and yet appease to the people who want a high-performance, and hopefully affordable, flagship grade device that run stock Android without ZTE's skin.

Voting for the ideas has begun, and will continue onto October 19. The idea that gets the most votes will be announced as the winner on October 20. The winner idea will hopefully made a reality in 2017.

If you would like to vote, head on over to the Project CSX website. You can also use the widget below to vote for your favorite choice.

//

Image Credit: Axon R Idea Thread

What are your thoughts on ZTE's Project CSX? Which idea should win in your opinion, and why? Let us know in the comments below!



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

Win a Pixel XL from XDA and RhinoShield, Because Bumpers are Back

Phone skins are really great to add style to any phone, plus they're not expensive, but they provide minimal protection if you happen to drop your phone. On the other end of the spectrum are cases, which are generally more expensive but offer much more protection. Cases are bulky and they don't let the beauty of your phone show through because they often have to cover all four edges as well as the back of the phone.

rhinoshield1

That's where CrashGuard by RhinoShield comes in. CrashGuard is essentially a bumper case, which means that it does not cover the back of your phone but only the sides (thus giving your device a more "naked" feel), but because of how it's engineered, it provides more protection than most cases. CrashGuard is far superior to the bumpers of the past because it has been engineered to absorb impact. This is done by utilizing a proprietary polymer material that is far more shock-absorbent than plastic, and it also has a protective honeycomb structure within the bumper to disperse impact properly. In fact, within the honeycombs are compartments of pressurized air that act as airbags and deflect impact energy. If that sounds really elaborate, it is, and the net result is that you can drop your phone from a variety of heights (up to 11 feet) and if you have a CrashGuard bumper on the phone, you're going to have a completely unmarked phone. If you want to see how incredible this protection is, watch this video from David Pogue where he does everything in his power to smash his phone by dropping it from a tall ladder.

rhinoshield2

Not only are CrashGuard bumpers durable, but they're lightweight (with most of their bumpers coming in under 14 grams). They're also pretty grippy thanks to the matte finish, and they come in a variety of colors. Another thing we really like about the CrashGuard line is the pricing: they're all priced at $19.99-$24.99, and they're shipped free on Amazon. Check out the listings for the Nexus 6P, Galaxy S7, and OnePlus 3. You can also pre-order a CrashGuard for the Pixel/Pixel XL.

But let's get into the contest, which is open to all countries, and the winner gets to pick the color! Use the below widget to get started. Contest ends on October 22. Good luck!

Win a Pixel XL!

Thanks to RhinoShield for sponsoring this post and contest.



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

Renders of Flat and Curved Variants of the Huawei Mate 9 Leaked

It's been almost a year since Huawei launched the Mate 8 (and just a few months since they launched the P9), so the time is about right for a refresh in their flagship Mate lineup. While the device is still some time away from official launch, we've got some leaked renders to sate our thirst for new information about new devices.

Coming to us courtesy of Evan 'evleaks' Blass through his publication VentureBeat, the renders show us two different variants of the Mate 9. One is the standard variant, the other boasts of a display with curved sides.

mate-9

Top: Manhattan; Bottom: Long Island

The devices are known right now by their internal codenames. The flat display variant is codenamed Manhattan, while the curved display variant is codenamed the Long Island. Manhattan is said to be the "base" version with an FHD display, while the Long Island is the more premium of the duo with its QHD display that will reportedly be up to Android's Daydream spec. However, Long Island is said to be a China-exclusive, while Manhattan would be released globally.

Huawei Mate 9 "Manhattan"

Huawei Mate 9 "Manhattan"

Specs of the Huawei Mate 9 point to the devices having a 5.9″ display, an octa-core HiSilicon Kirin 960 SoC and several memory configurations, the highest of which will be at 6GB of RAM and 256GB of storage. The camera setup will be the similar dual-lens, dual-sensor Leica setup similar to the one seen in the Huawei P9. The lenses and sensors are reportedly improved though, as it is tipped to be 20MP at f/2.0.

And since almost everyone looking at the renders will be thinking of it: Yes, the curved display variant looks like a Galaxy device. And yes, that looks like a button on the front. And yes, looking like the Note 7 might not be such a good idea from a marketing perspective, although it looks pretty nice in its own right.

The Huawei Mate 9 is set to be unveiled on November 3. We hope to come across more information on the devices as the launch date approaches.

What are your thoughts on the leaked renders of the Huawei Mate 9 variants? Let us know in the comments below!

Source: VentureBeat



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

Samsung is Reportedly Increasing Production of the Galaxy S7

It seems Samsung is unable end 2016 on a good note due to the Galaxy Note 7 issues. After the company's replacement Galaxy Note 7 units continued to have battery issues, multiple carriers and retailers choose to no longer sell the device anymore. Instead, they offered to let their current Note 7 customers come in and replace the phone with any other phone in the store, or to get a refund on it as well all accessories they have purchased for the device.

Shortly after these announcements, Samsung themselves said they would temporarily halt sales and production of the Galaxy Note 7 so they could investigate what was going on with the replacement units. The company was unable to give any statements about new incidents other than saying they are waiting for the burnt unit to be shipped back to them so they can determine whether or not it was a "safe" Galaxy Note 7, or one that had previously been recalled.

Just one day later, The Wall Street Journal reported that Samsung had decided to discontinue the Galaxy Note 7. And this makes sense from a marketing perspective. The reputation for the Galaxy Note 7 is so tarnished right now, that it will likely spill over onto the Galaxy Note 8 as well (if there even is a Note 8). Considering how much money Samsung has lost on labor and resources, on top of the investors that have sold their stock in the company, the move to discontinue the Galaxy Note 7 sounds smart.

It's now being reported that Samsung has diverted their resources to increase production of the Galaxy S7 as well as some of their lower-end smartphones. The report cites an "industry source who wanted to be unnamed," and says the company is planning to increase production in order to minimize rumors of a price drop. Another source also tells The Korea Herald that Samsung doesn't have any plans to push the launch date of the Galaxy S8 forward.

Source: The Korea Herald



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

Sony IMX378: Comprehensive Breakdown of the Google Pixel’s Sensor and its Features

IMX378 Overview

We reached out to Sony to try to learn a bit more about the IMX378 sensor that is used by the upcoming Google Pixel and Pixel XL phones, as well as by the Xiaomi Mi 5S. Unfortunately, Sony was not able to distribute the datasheet for the Exmor RS IMX378 sensor just yet, but they were extremely helpful, and were able to provide us with some previously unreleased information about the IMX378.

First up, the very name itself was wrong. Despite rumors stating that it would be part of the Exmor R line of Backside Illuminated (BSI) CMOS sensors like the IMX377 before it that was used in the Nexus 5X and Nexus 6P, our contact at Sony has informed us that the IMX378 will instead be considered part of Sony's Exmor RS line of Stacked BSI CMOS sensors.

While many things have remained the same from the IMX377 to the IMX378, including the pixel size (1.55 μm) and sensor size (7.81 mm), there have been a couple key features added. Namely it is now a stacked BSI CMOS design, it has PDAF, it adds Sony's SME-HDR technology, and it has better support for high frame rate (slow motion) video.

Stacked BSI CMOS

Backside illumination by itself is an extremely useful feature that has become almost standard in flagship smartphones for the last few years, starting with the HTC Evo 4G in 2010. It allows the camera to capture substantially more light (at the cost of more noise) by moving some of the structure that traditionally sat in front of the photodiode on front illuminated sensors, behind it.

Backside Illumination CMOS Sensor Design

Surprisingly, unlike most camera technology, backside illumination originally started appearing in phones before DSLRs, thanks in large part due to the difficulties with creating larger BSI sensors. The first BSI APS-C sensor was the Samsung S5KVB2 that was found in their NX1 camera from 2014, and the first full-frame sensor was the Sony Exmor R IMX251 that was found in the Sony α7R II from last year.

Stacked BSI CMOS technology takes this one step further by moving more of the circuitry from the front layer onto the supporting substrate behind the photodiodes. This not only allows Sony to substantially reduce the size of the image sensor (allowing for larger sensors in the same footprint), but also allows Sony to print the pixels and circuits separately (even on different manufacturing processes), reducing the risk of defects, improving yields, and allowing for more specialization between the photodiodes and the supporting circuitry.

Sony Exmor R vs Exmor RS BSI vs Stacked BSI CMOS image sensor

PDAF

Phase Detection Autofocus PDAF Example by cmgleeThe IMX378 adds Phase Detection Autofocus, which last year's Nexus phones and the IMX377 did not support. It allows the camera to effectively use the differences in light intensity between different points on the sensor to identify if the object that the camera is trying to focus on is in front of or behind the focus point, and adjust the sensor accordingly. This is a huge improvement both in terms of speed and accuracy over the traditional contrast-based autofocus that we've seen on many cameras in the past. As a result, we've seen an absolute explosion of phones using PDAF, and it has become a huge marketing buzzword which is held up as a centerpiece of camera marketing across the industry.

While not quite as quick to focus as the Dual Photodiode PDAF that the Samsung Galaxy S7 has (also known as "Dual Pixel PDAF" and "Duo Pixel Autofocus"), which allows every single pixel to be used for phase detection by including two photodiodes per pixel, the merger of PDAF and laser autofocus should still be a potent combination.

High Frame Rate

There's been a lot of talk lately about high frame rate cameras (both for consumer applications, and in professional filmmaking). Being able to shoot at higher frame rates can be used both to create incredibly smooth videos at regular speed (which can be fantastic for sports and other high-speed scenarios) and to create some really interesting videos when you slow everything down.

Slow Motion Pineapple Falling Into WaterUnfortunately, it is extremely difficult to shoot video at higher frame rates, and even when your camera sensor can shoot at higher frame rates, it can be difficult for the phone's image signal processor to keep up. That is why while the IMX377 used in the Nexus 5X and 6P could shoot 720p video at 300 Hz and 1080p video at 120 Hz, we only saw 120 Hz 720p from the Nexus 5X and 240 Hz 720p from the 6P. The IMX377 was also capable of 60 Hz 4k video, despite the Nexus devices being limited to 30 Hz.

The Pixel phones are both able to bring this up to 120 Hz 1080p video and 240 Hz 720p video thanks in part to improvements related to the IMX378, which sees an increase in capabilities of up to 240 Hz at 1080p.

The sensor is also able to shoot full resolution burst shots faster, stepping up to 60 Hz at 10 bit output and 40 Hz at 12 bit output (up from 40 Hz and 35 Hz respectively), which should help reduce the amount of motion blur and camera shake when using HDR+.

SME-HDR

Traditionally, HDR for video has been a trade-off. You either had to cut the frame rate in half, or you had to cut the resolution in half. As a result, many OEMs haven't even bothered with it, with Samsung and Sony being among the few that do implement it. Even the Samsung Galaxy Note 7 is limited to 1080p 30 Hz recording due in part to the heavy computational cost of HDR video.

RED HDRx Demonstration

The first of the two main traditional methods for HDR video, which Red Digital Cinema Camera Company calls HDRx and which Sony calls Digital Overlap HDR (DOL-HDR), works by taking two consecutive images, one exposed darker and one exposed lighter, and merging them together to create a single video frame. While this allows you to keep the full resolution of the camera (and set different shutter speeds for the two separate frames), it can often result in issues due to the time gap between the two frames (especially with fast moving objects). Additionally, it can be very difficult for the processor to keep up, as with DOL-HDR, the phone's ISP handles merging the separate frames together.

The other traditional method, which Sony calls Binning Multiplexed Exposure HDR (BME-HDR), sets a different exposure setting for every pair of two lines of pixels in the sensor to create two half resolution images at the same time, which are then merged together into one HDR frame for the video. While this method avoids the issues associated with HDRx, namely a reduction in frame rate, it has other issues, specifically the reduction in resolution and the limits on how the exposure can be changed between the two sets of lines.

BME HDR Example Image

Spatially Multiplexed Exposure (SME-HDR) is a new method that Sony is using to allow them to shoot HDR at the full resolution and at the full frame rate that the sensor is capable of. It is a variant of Spatially Varying Exposure that uses proprietary algorithms to allow Sony to capture the information from the dark and light pixels, which are arranged in a checkerboard style pattern, and infer the full resolution image for both the dark and light exposure images.

While Sony unfortunately was not able to disclose the exact pattern that they use at this time (and they may never be able to disclose it — companies tend to play their cards very close to their chest when it comes to cutting edge technology, like that which we see in HDR, with even Google having their own proprietary algorithm for HDR photos, known as HDR+), there is still some publicly available information that we can use to piece together how it may be accomplished. A couple of papers have been published by Shree K. Nayar of Columbia University (one of which was in collaboration with Tomoo Mitsunaga of Sony) that contain different ways to use Spatially Varying Exposure, and different layouts that can achieve it. Below is an example of a layout with four levels of exposure on an RGBG image sensor. This layout claims to be able to achieve single capture full resolution HDR images with only around a 20% loss in spatial resolution, depending on the scenario (the same accomplishment that Sony claims for SME-HDR).

Spatially Varying Exposure SME HDR RGBG Example

Sony has used SME-HDR in a couple image sensors already, including in the IMX214 that has seen a lot of popularity lately (being used in the Asus Zenfone 3 Laser, the Moto Z, and the Xperia X Performance), but is a new addition to the IMX378 compared to the IMX377 that was used last year. It allows the camera sensor to output both 10 bit full resolution and 4k video at 60 Hz with SME-HDR active. While a bottleneck elsewhere in the process will result in a lower limit, this is a fantastic improvement over what the IMX377 was capable of, and is a sign of good things to come in the future.

One of the big improvements of the IMX378 over the IMX377 is that it is able to handle more of the image processing on-chip, reducing the workload of the ISP (although the ISP is still able to request the RAW image data, depending on how the OEM decides to use the sensor). It can handle many small things like defect correction and mirroring locally, but more importantly, it can also handle BME-HDR or SME-HDR without having to involve the ISP. That could potentially be a major difference going forwards by freeing up some overhead for the ISP on future phones.

Sony Full Frame APS-C and 1/2.3" Exmor CMOS Sensors

We would like to thank Sony once again for all the help with creating this article. We really appreciate the lengths that Sony went to in helping ensure the accuracy and depth of this feature, especially in allowing us to uncover some previously-unreleased information about the IMX378.

That being said, it really is a shame that it is so hard to access some of this information, even basic product information. When companies try to put information on their websites, it often can be rather inaccessible and incomplete, in large part because it is often treated as a secondary concern of the company's employees, who are more focused on their main work. One dedicated person handling public relations can make a huge difference in terms of making this type of information available and accessible to the general public, and we're seeing some people trying to do just that in their free time. Even on the Sony Exmor Wikipedia article itself, where over the course of a couple months a single person in their spare time laid most of the foundation to take it from a nearly useless 1,715 byte article that had been mostly the same for years, into the ~50,000 byte article which we see there today with 185 distinct editors. An article that is arguably the best repository of information about the Sony Exmor sensor line available online, and we can see a very similar pattern on other articles. A single dedicated writer can make a substantial difference in how easily customers can compare different products, and in how educated interested consumers are about the subject, which can have far-reaching effects. But that's a topic for another time.

As always, we're left wondering how these hardware changes will affect the devices themselves. We quite clearly will not be getting 4k 60 Hz HDR video (and may not be getting HDR video at all, as Google has not mentioned it yet), but the faster full resolution shooting likely will help substantially with HDR+, and we will see the improvements of the newer sensor trickle into the phone in other similar small but substantial ways as well.

Google Pixel Phones EIS On and Off Comparison

While DXOMark lists the Pixel phones as performing slightly better than the Samsung Galaxy S7 and HTC 10, many of the things that gave the Pixel phones that small lead were major software improvements like HDR+ (which produces absolutely fantastic results, and which DXOMark dedicated an entire section of their review to) and Google's special EIS system (which can work in tandem with OIS) that samples the gyroscope 200 times a second to provide some of the best Electronic Image Stabilization we have ever seen. Yes, the Pixel phones have a great camera, but could they have been even better with OIS and Dual Pixel PDAF added in? Absolutely.

Don't get me wrong, as I said, the Pixel phones have an absolutely stunning camera, but you can't really blame me for wanting more, especially when the path to those improvements is so clear (and when the phones are priced at full flagship pricing, where you expect the best of the best). There's always going to be a part of me that wants more, that wants better battery life, faster processors, better battery life, brighter and more vivid screens, louder speakers, better cameras, more storage, better battery life, and most importantly, better battery life (again). That being said, the Pixel phones have many small fantastic features that could come together to create a truly promising device, which I am excited to see.



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

Moto and Updates: More Planned Obsolesce from Lenovo’s Motorola

Planned obsolescence is a tricky grey area in every field. Advancements in science and technology allow equipment and components to last longer and perform reliably, but these improvements also have a very direct short-term impact on the sales of your future devices.

After all, if the previous device is still working, that is one less compelling reason for a consumer to purchase the next device that the company will release a short while later. A lot of decisions that smartphone makers take also play directly within the scope of planned obsolescence, even if the prime motive behind the decision was something else. Sealed batteries, forced updates that slow down the device and as is the case with Android OEMs, not providing updates at all — everyone is guilty of factoring in some element of obsolescence in their releases.

Just to take our minds off phones with sealed batteries for a change, let's talk about Lenovo and Motorola. Before Lenovo acquired Motorola, the company was praised for its Moto X lineup, how they performed for the money they asked for, and how quickly the devices got updated owing to their minimal skin over pure Android. The Moto X 2013, on Verizon of all carriers, received its Android 4.4 KitKat update just around three weeks after KitKat was announced — even before the Nexus 4 got the update!

The Moto X from 2013 was a Motorola phone that received an update faster than a Nexus

The Moto X from 2013 was a Motorola phone that received an update faster than a Nexus

But ever since Lenovo acquired Motorola, things have been…different. And we're not talking only in the terms of the delay in receiving updates to an OS skin which is a fairly minimal touch-up to stock Android. We're also talking about some of the weird decisions regarding updates that the company has taken in the recent past. To recall, Lenovo had just about killed off the update support for the Moto E 2015 only 6 months after the device's release. But after a lot of bad press, the company yielded and promised an Android 6.0 update for the device in some regions.

We're at yet another of these perplexing update decisions from Lenovo with regards to Motorola branded devices. Motorola's recent Android 7.0 Nougat announcement for its devices included a long list of devices, which included devices like the Moto G4 Play and the Moto X Play. Curiously, as brought to our attention by our forum members, the list is missing devices like the Moto G3 and the Moto G Turbo Edition.

The Moto G3 was launched in July 2015 while the Moto G4 Play was launched in May 2016. Ironically, the G4 Play sports the same CPU and GPU as the G3 but at a lower clock speed (go figure!). As mentioned above, the device is getting the official Android 7.0 Nougat update while the G3 will not. Similar, yet slightly more befuddling, situation exists with the Moto G Turbo Edition which was launched in November 2015 and shares the exact same CPU and GPU as the Moto X Play which was launched earlier in July 2015. The Moto X Play will receive Nougat, while the newer Moto G Turbo Edition will not.

misc-jackie-chan-lNow factor in this: Android 6.0 was officially released in October 2015, and Android 7.0 was officially released in August 2016. The oldest devices from the above mentioned four are the Moto G3 and the Moto X Play, both of which were released in July 2015, but only one of them is receiving its Android 7.0 update. A device released a few months later with the same SoC as the update-receiving phone, is however, not getting the update. Confused? We are too.

There is no clear update policy at play here with Motorola and Lenovo. One cannot argue that they are favoring only the most recent of devices, because with the Moto X Play in the picture, they are not.

One also cannot argue that the devices in question sport weak and outdated SoCs which makes the update technically infeasible, because other devices with the same SoC released by Motorola itself, are being promised an update. Yes, SoC is not the only roadblock in bringing an update to a device. But with the number of hardware similarities between the Moto G3 and the Moto G4 Play, a large part of the update work is already done in some form by Motorola.

One could also come on to argue that pricing of the devices is what Motorola used to decide which devices are worth updating. But if you take a look at the predecessors of the Moto G3, both the Moto G and the Moto G2 received two Android updates that spanned over version numbers — KitKat and Lollipop for the Moto G, and Lollipop and Marshmallow for the Moto G2. The Moto G3 will sadly, remain on Marshmallow under Motorola's current plan.

With the MotoMaker options, the Moto G 2015 provided great hardware. But sadly, poor software update support.

With the MotoMaker options, the Moto G 2015 provided great hardware. But sadly, poor software update support.

So that brings us back to the starting argument of this article — planned obsolescence. Motorola's update plans are nothing short of planned obsolescence. By not providing the latest in terms of software, Motorola and Lenovo hope to fleece customers into purchasing newer phones that are the same in terms of SoC. The lack of update is the mechanism put into place to induce consumers to abandon perfectly capable and working hardware, in favor of newer devices that are more of sidegrades than upgrades. Motorola is not even supporting devices in its budget lineup for 18 months of software updates anymore, as is evident from the Moto G3.

What you do get now from Motorola and Lenovo is uncertainty. You simply do not know if the device you purchase will be updated for another year or two. Granted, the low end of the market is not where one should expect the most in terms of after-sales updates, but Motorola's recent actions reaffirm that they are back with the rest of the Android OEMs into ignoring the budget devices. Which is pretty ironic, considering that the Moto G, the budget hero, was Motorola's best selling smartphone of all time. And to be fair, while we keep using the name "Motorola" here, we really should be calling out Lenovo — these issues and other controversies became prominent after Lenovo's acquisition, as it was under Google that Motorola has begun releasing updates faster.

Our forum members are petitioning for the Moto G3 and the Moto G Turbo Edition to receive some Nougat love from Motorola. If you would like to support their cause, please visit the forum thread. We hope bringing light to this issue manages to convince Lenovo once more that there's value in software updates.

What are your thoughts on Motorola's recent update plans? Are you looking forward to purchasing a Motorola device in the future? Let us know your thoughts in the comments below!



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