LightBlog

mardi 18 octobre 2016

Optus: LG G5 Expected to Receive Android 7.0 in Mid-November

LG made massive headlines when it was revealed that one of their smartphones would be the first available with Android 7.0 Nougat out of the box. Indeed, the LG V20 is the first to have Android 7.0 Nougat installed on it right out of the box, but most of the general public hasn't even received their device yet. Pre-orders have been up at most major wireless carriers, and some will begin shipping their orders this month, but others have to wait until November to ship to their customers.

With LG getting the jump on Android 7.0 though, many were curious as to what their progress was for Nougat on other smartphones. LG does have a good reputation of pushing out fast updates in their home country of South Korea. However, getting these brand new updates to major markets like Europe and the United States has been a completely different story. Many people were disappointed about how long it took Android 6.0 Marshmallow to finally land on the LG G4.

So the question is, how long will it take LG to complete the rollout of Android 7.0 Nougat on the LG G5? It's too far off to know that right now, but we do have an idea as to when the rollout will begin though. Optus, an Australian wireless carrier, just published their timeline for the Nougat update on the LG G5. Optus is telling us that the update is currently in testing, and that they are expected to begin the update process in the middle of next month.

This timeline should not be treated as a date that is set in stone. It's currently in the testing phase and there could be many roadblocks in its path. With it being in testing right now, Optus could find something wrong with the update, a connectivity issue for instance, and that will cause a delay in the roll out. For now though, at least we know that LG is working on the update for multiple regions and many are hopeful it can be completed before the end of the year.

Source: Optus



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

A Look at What Has Changed from the Snapdragon 820 to the Snapdragon 821 in the Google Pixel Phones

We reached out to Qualcomm to get a better look at the Snapdragon 821 processor that is making an appearance in the upcoming Google Pixel and Pixel XL, the Asus ZenFone 3 Deluxe, the Xiaomi Mi 5s, and the LeEco Le Pro 3. With the Snapdragon 821 in the Pixel phones running at the same clock speed as the regular Snapdragon 820, many people were asking what benefits the new SoC brings, and why choose it if they're not going to use the higher clock speeds it can bring.

Google Pixel Press Image Vertical Very SilverOur interest was piqued when the Android Platform's Performance Lead mentioned that Google was not underclocking the Snapdragon 821 (contrary to popular belief), and thus implied that rather the version that they were using came running at the same speeds as the main version of the Snapdragon 820 by default.

The short version is that not much has physically changed in the design of the Snapdragon 821 from the 820, but we were able to make some interesting discoveries in the process. The Snapdragon 821 is a revision similar to the Snapdragon 801 and 800, and is brought about primarily by improving yields.

These improved yields have allowed Qualcomm to release essentially a revision of the Snapdragon 82x that can either use 5% less power at the same clock speeds as the original version, or be tuned for slightly higher clock speeds at around the same power usage as the 820. This follows closely in the footsteps of the Snapdragon 800 and Snapdragon 801, where the improved yields allowed Qualcomm to release a slightly improved version of the 800 halfway through their regular development cycle.

Qualcomm informed us that there are indeed two revisions of the Snapdragon 821. One running at the advertised maximum CPU and GPU clock speeds of 2.34 GHz and 653 MHz (respectively), and a separate one running at the same 2.15 GHz and 624 MHz that was found in the main Snapdragon 820. The Pixel phones are using the later one, which we have been informed is called the MSM8996 Pro-AB. While we have not yet been able to get confirmation about the name of the higher clocked model, if it is following the same model as the Snapdragon 800 and 801 chips, it may be either the MSM8996 Pro-AA or the MSM8996 Pro-AC.

One thing to note is that despite rumors to the contrary, Google did not pick the Snapdragon 821 because of the Snapdragon VR SDK. While definitely a nice tool, it works on both the Snapdragon 820 and 821, and is not a distinguishing feature between the two chips.

Qualcomm Snapdragon VR Virtual Reality Reference Platform3With how heavily Google was pushing the improvements to the Pixel phones' camera, we thought there might be some Image Signal Processor improvements, and at first glimpse there appeared to be, with the Snapdragon 820 being listed as being capable of processing 25 MP images at 30 Hz, and the Snapdragon 821 being listed as being capable of processing 28 MP images at 30 Hz; but that turned out to be a typo, which has since been corrected. The Qualcomm Spectra ISP in both SoCs are capable of processing the same 28 MP at 30 Hz.

Instead, Google sought out improvements to their HDR+ processing speed by finding ways to better leverage Qualcomm's Hexagon DSP, through the use of Qualcomm's Hexagon Vector eXtensions. Google is offloading substantial portions of processing for HDR+ to the Hexagon DSP that used to be handled by the CPU itself, and that has played a major role in both decreasing the time it takes to process HDR+ shots, and in allowing the Pixel phones to continue shooting HDR+ shots, with DXOMark finding that it could shoot one HDR+ shot every three seconds indefinitely. This pairs very well with the faster shooting capabilities brought about by the Sony Exmor RS IMX378 image sensor to create an exceptional camera.

While not directly related to the processor itself, Google has mentioned that they have put substantial work into helping improve the scheduler found in the Pixel phones, which is fantastic news as schedulers are, in the words of John Poole, "horrendously complicated pieces of code", and small improvements can have major impacts on real world performance.

Overall, the Snapdragon 821 should be a solid revision, but if you're looking for a big jump in performance, you're going to have to wait a couple more months to see the real next generation of chips start appearing in flagship phones next year (the rumored Snapdragon 830), which Qualcomm just announced will be using their new X16 LTE Modem. The new modem is particularly interesting, as it will bring some substantial improvements like LTE Dual SIM Dual Active, Category 16 and 13 downlink and uplink, multi-carrier 4×4 MIMO, 4×20 Carrier aggregation, and a theoretical peak download speed of 1 Gbps.

What do you think of the Snapdragon 821? Are you excited for its use in the Pixel phones, or are you rather anticipating next year's flagships with the Snapdragon 830 and the X16 LTE Modem?



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

[LAST CALL!] Win an Honor 8: 4GB RAM, Dual-Camera, Premium Design

CONTEST ENDS TODAY!

We're back with another Honor 8 contest, and like before, it's open to all countries! You can enter the contest in numerous ways. Each point you earn is considered an entry, so the more points you earn, the higher your chances are of winning. As a reminder, the Honor 8 is the current flagship from Honor and sports dual-cameras, USB Type-C with fast-charging, a Kirin 950 CPU with 4GB RAM, and a 5.2″ 1080p display. We will pick the winner around during the week of October 17. Good luck!

Win a New Honor 8!

  Honor 8 XDA Review   Honor 8 Forums

  Win Stuff from Honor



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

lundi 17 octobre 2016

Introducing the Qualcomm Snapdragon 653, 626, and 427: Qualcomm Announces Successors to Popular Mid-Range SoCs

It has been a good year for Qualcomm so far — the Snapdragon 65x series has garnered rave reviews for providing stellar performance in the mid-range market segment, and the Snapdragon 820 has received an improved critical reception over the Snapdragon 810. To build on the successful year, Qualcomm has announced the successors to some of its popular SoC lineups for the midrange and entry-level market segments, the Snapdragon 653, 626, and 427.

Qualcomm Snapdragon 653 626 427 ImprovementFirst up is the new Qualcomm Snapdragon 653 SoC, which as you may have guessed, is an incremental upgrade over the Snapdragon 652. When compared to its predecessor, the Snapdragon 653 provides an improvement of up to 10% higher performance and twice the addressable memory, with support for 8GB of RAM now. Further, the Snapdragon 653 is using the new X9 LTE modem which is found in the Snapdragon 625, an improvement over the X8 LTE modem found in the 652. The X9 LTE modem is still a Category 7 modem for downlink, same as the X8, however it does bring some extra features, namely the addition of Ultra HD Voice (EVS) over VoLTE (which was only supported by the X8 LTE modem on certain SoCs), Snapdragon Upload+, and Category 13 LTE uplink. Interestingly, the Snapdragon 653 also adds support for Qualcomm's Clear Sight dual camera technology, which is a fad that has been mostly limited to flagship devices. Only a couple devices like the Honor 8 and LG V20 have dual cameras so far, and even fewer utilize both cameras at the same time in the way that Qualcomm Clear Sight does. The Snapdragon 653 continues to use a 4xA72 + 4xA53 core combination on a 28 nm process with an Adreno 510 GPU and LPDDR3 RAM, like the Snapdragon 652 before it, however it increases the clock speed of the A72 cores to 1.95 GHz and has support for 802.11ac MU-MIMO.

The extremely power efficient Qualcomm Snapdragon 625 from the lower mid-range is also seeing an upgrade with the Snapdragon 626 coming into the picture. Qualcomm promises an increase in performance of up to 10% over the 625, although the Cortex-A53 cores used in the Snapdragon 625 are not known for being particularly powerful. The Snapdragon 626 also adds support for dual cameras, and uses the X9 LTE modem as well. The Snapdragon 626 continues to use an 8xA53 core configuration on a 14 nm process with an Adreno 506 and USB 3.0 support, but it increases the clock speed to 2.2 GHz and has support for Bluetooth 4.2.

Towards the low end of the market, the Qualcomm Snapdragon 425 is seeing an upgrade in the form of the Snapdragon 427. The biggest improvement is the modem on this SoC, which is now an X9 LTE modem with support for Category 7 LTE downlink and Category 13 LTE uplink. This is a substantial improvement over the X6 LTE modem that was used in the Snapdragon 425 and 430, which was only capable of Category 4 and 5 downlink and uplink. Qualcomm is pushing for adoption of their Clear Sight technology relatively heavily, with even the Snapdragon 427 gaining support, although we remain skeptical about the finesse with which low end devices can handle dual-cameras. The Snapdragon 427 has the same 1.4GHz 4xA53 core design on a 28 nm process as its predecessor has. It also continues to use the Adreno 308 GPU that was found in the Snapdragon 425, which is disappointing to see, as it limits the SoC to OpenGL ES 3.0, which may cause issues with software updates.

Qualcomm Clear Sight DiagramWith the Snapdragon 653, 626, and 427 all supporting Qualcomm Clear Sight technology, we may start to see dual camera setups trickle down to mid-range, and potentially even low-end, devices by mid 2017. It will be very interesting to see what effects this has on the cameras of mid-range Android phones, as that has historically been an area where they have struggled, and dual camera technology has shown some relatively impressive results.

Additionally, all three of these new SoCs support Quick Charge 3.0, helping solidify support for fast charging across Qualcomm's entire product lineup. This further increase in SoC support for Qualcomm Quick Charge will make it easier to find devices and accessories that can fast charge, even at the low end of the market. The Qualcomm Snapdragon 653 and the Snapdragon 626 will be commercially available by the end of 2016, while the Snapdragon 427 is expected to be commercially available in devices in early 2017.



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

Samsung Galaxy Note 7 Batteries Were Tested Within the Company

Now that the Galaxy Note 7 has been discontinued permanently, everyone wants to know what caused the issue with the batteries. Not only has Samsung launched an internal investigation into the issue, but the South Korean government has also jumped in with an investigation of their own. A lot of people seem to have their own theory as to what happened with the batteries, but no one has been able to present evidence to prove their case.

Some publications are putting the blame on the rounded edges of the Galaxy Note 7. The theory here is, that due to the rounded corners on the phone, there is a high probability that the battery cells will bend and make contact with another cell. Others have suggested that a tweak made to the hardware to increase the charge time is the underlying cause of the issue. This theory indicates that the batteries themselves were safe, but the way they were being charged was the culprit.

Again, there are multiple theories floating around but none have been proven as of right now. Interestingly enough though, a new report from The Wall Street Journal talks about how Samsung was in charge of the testing process for these batteries. This is unique because other smartphone OEMs use a 3rd-party lab to test whether or not the batteries used in their devices are safe or not.

In order to sell a smartphone in the United States, a handset OEM must have their batteries tested at one of the 28 labs certified by the U.S. wireless industry's trade group. According to CTIA, Samsung is the only manufacturer to use in-house battery-testing facilities. Both Lenovo and Nokia have operated CTIA-certified battery labs in the past, but both say their labs are in the process of being closed down. Further, Samsung's in-house testing had not revealed any issues with the Note 7 batteries.

Samsung says they are "working around the clock" to figure out what caused the issue with the Galaxy Note 7, and also plans to make "significant changes" in its quality-assurance processes. The company declined to comment whether it plans to use third-party labs for battery testing.

Source: The Wall Street Journal



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

Samsung Starts Mass Production of SoCs With 10nm FinFET Technology

Samsung has announced today that the company has started mass production of 10nm FinFET based System-on-Chips. The South Korean OEM claims that their SoC is the first one produced with such technology.

In comparison to its 14 nm predecessor, Samsung's new 10nm FinFET process (10LPE) adopts an advanced 3D transistor structure with additional enhancements in both process technology and design enablement. As a result, users should get a 27-percent performance boost, while the power consumption is expected to be reduced by a whopping 40 percent. In plain English and simpler context, this means that future Samsung devices should be more powerful while consuming less battery.

Company's Executive Vice President Jong Shik Yoon finds Samsung a leader in advanced process technology. According to him, the South Korean company will continue to deliver top-notch products to its customers. It's understandable that Samsung faces really strong competition in Qualcomm and MediaTek, with both the chipmakers craving to maintain their great market positions.

Newly announced chips will not be the only produced in the 10nm process. Samsung will also produce a second generation of system-on-chips (10LPP) "with performance boost". From what we learn, production for the same should commence in the second half of 2017.

According to the official press announcement, the company will sport its new chips in digital devices launching early next year. We have to remind that Samsung has recently ceased to produce the Galaxy Note 7 due to hardware defects. So while this new technology provides good opportunity to make up for lost reputation, it is all the more important to take one's time and do things right. We hope the upcoming SoCs help bridge the performance gap that the Android market sees when compared to Apple's SoCs.

What are your thoughts on the beginning of production on the 10nm process? Let us know in the comments below!

Source: Samsung



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

Xiaomi Rumored to Feature Its Own SoC in “Meri”

China's biggest OEM — Xiaomi, is rumored to use their own in-house SoC in its upcoming phone models. In-house chips will reportedly be used in lower-priced devices in the last two-quarters of 2017, which sound like good testing platforms for the OEM before it moves on to higher performance devices.

This move is not entirely unexpected, as the Redmi producer planned to join the SoC market for quite some time now. First mentions about it surfaced two years ago when a company called Beijing Pinecone Electronics owned by Xiaomi signed an agreement with Leadcore Technology Ltd. That deal was about designing 4G multiple mode chips.

News about the possible use of the chips was published on Chinese microblogging site Weibo. The first device with an in-house chip will reportedly be the Xiaomi Meri. AnTuTu screenshots from the device point that the phone and the SoC will use a Mali-T860 GPU and come with a 5.46″ Full HD screen. The rest of the spec sheet is still a riddle.

pinecone meri-antutu

Seems like this news is quite bad for two of the biggest SoC makers in the market currently, Qualcomm and MediaTek, as they were delivering chips for Xiaomi for the last couple of years. It's a big thing as the Chinese OEM sold over 10 million devices in Q2 2016. We hope that Xiaomi will maintain good GPL practices and will release the mandated source for its in-house chip.

What do you think about this move? Would you get a device with a brand new SoC? Let us know in the comments below!

Source: Gizmochina



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