LightBlog

lundi 26 septembre 2016

Motorola to Launch the Moto Z Series in India Next Month

When Motorola and Lenovo first announced the Moto Z and Moto Z Force, we were told the Force Droid variant would be a Verizon Wireless exclusive. This is still the case, but we did recently see an unlocked version of the Moto Z go up for pre-order in the United Kingdom last month and this month in the United States. This device still carriers its hefty $700 price tag for those in the US but thankfully there is an alternative for those who don't really need a flagship smartphone right now.

The Moto Z Play is an upper mid-range smartphone with a $450 pre-order price right now in the United States. It comes with a 5.5″ 1080p Super AMOLED display, Qualcomm Snapdragon 625 SoC, 3GB of RAM, 32GB of storage, microSD card slot with a 16MP rear camera and a 5MP front-facing camera. It's going to be hard for the Moto Z Play to compete with the likes of the Axon 7 and the OnePlus 3, but it is an option for those who prefer a Motorola smartphone.

Until now, Motorola had not announced a launch date for any of these devices within the country of India. Over the weekend though, the Moto India Twitter account confirmed at least one of these Moto Z devices would be launching next week. The teaser video doesn't goes into specifics about whether they will be launching the Moto Z, Moto Z Play, or both of them on October 4th. We just get a video with a big Z on it as they highlight the JBL Moto Mod that will enhance the audio capabilities of the device.

We will find out exactly which device(s) Motorola will be launching in India, and we'll also find out how much they will be charging for them. The Moto Z Play has been getting a lot of praise for its impressive battery life so far, so this could be a major selling point for the device.

Source: @Moto_IND



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

How to Access the Hidden Hardware Diagnostic Tools on your Android Phone

If you're buying a phone secondhand, the first thing you should absolutely do is complete a thorough check of the device's hardware to ensure that everything is working as intended. So you pop in your SIM card, head on over to the Play Store, and download one of the many hardware diagnostic testing apps available for free. But there's no need to install any third-party app, for within most Android smartphones you'll find a hidden hardware diagnostic app.

After all, when you send a phone into the manufacturer, the technicians need a tool to properly assess the state of your phone in order to focus on what parts to refurbish. That's why you'll notice some odd system APKs pre-installed on your phone that on first glance seem to be some kind of inaccessible bloatware, but if you figure out how to access them they will provide you a set of diagnostic tests to run on your phone.

Disclaimer: this is just a fun discovery we're going to share, because in the real world it's far easier to just install a third-party app rather than dig around your phone for a hidden app.


huawei-mmitestHuawei's HwMMITest

 

Do you own a Huawei device, such as the Huawei Mate 8, Huawei Mate S, Huawei P9, or even the Nexus 6P? If so, then when you navigate to Settings –> Apps and enable the option to show all system apps, you'll find an app called HwMMITest. This is an app that is pre-installed on all Huawei devices, and is normally inaccessible from any application launcher.

nexus-6p-bootloader-mmitestIn order to access this secret diagnostic app, you will need to first reboot into the bootloader. How this is done differs between various Huawei devices, but on the Nexus 6P all you need to do is hold Vol Down + Power while the device is shut down. Then when you are within the bootloader menu,  navigate to the Factory option by scrolling through the options with your volume keys and then confirm the option by pressing the power button to trigger the boot process. Alternatively, you can try typing fastboot oem enable-hw-factory through a command prompt.

Once you boot back into Android, you will see two persistent notifications in your notification bar. One is for a secret menu called Project Menu (the purpose of which I'm unsure of) and the second is called MMI Test which when clicked will begin a guided test of the device's hardware, provided that your current battery level is between 55% and 80%.

mmitest-notification

What exactly does the app test? Everything. Here's just a short list:

  • LCD brightness/color test/dead pixel test
  • Touch Screen/digitizer test
  • Front/Back cameras
  • Compass/GPS/Gravity sensor
  • Light sensor
  • Vibration motor
  • Speaker test
  • Microphone/headset test
  • Bluetooth/WiFi/SIM card test
  • etc.
screenshot_20160801-203011 screenshot_20160801-203056 screenshot_20160801-203132 screenshot_20160801-203202 screenshot_20160801-203257 screenshot_20160801-203422 screenshot_20160801-203715 screenshot_20160801-203728

Though the above screenshots were taken from a Nexus 6P, they are only indicative of the hidden diagnostic tool on Huawei devices. There are different steps needed to access the diagnostic tool on devices from other manufacturers. For instance, on the Moto X Pure you can directly access the tool without having to boot into fastboot by launching its hidden activity. Try finding out how to access the tool on your own device, and let us know if you could find it in the comments below!



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

Signs of Life For Android Pay’s Global Rollout

With rumors swirling about Android Pay's expansion into more countries, Google has started taking steps towards preparing for those launches. Unfortunately, most of the preparations happen behind closed doors where we can't see them (negotiating with banks, helping the banks put forth Requests For Proposals to find implementers, navigating each country's legal framework, etc.), but some are publicly visible.

Android Pay Help Page LanguagesOne such public facing step is the localization of help pages for each country, and Google just added a slew of them. Localization often isn't strictly required (although some countries like Canada can get very prescriptive about requiring support for all official languages), however companies often won't launch a product without it. Localized help pages can be a very small thing, but having the spelling that you are used to on them (not to mention them being in your language) can make a huge difference for how comfortable you are using them, and for customer satisfaction.

While Android Pay has already launched in the United States, the United Kingdom, Singapore, and Australia (and has the appropriate localizations for each of them), both Canada (English and French) and Ireland have been there for a couple months now without any public action being taken on them. That would indicate that talks are in progress for those countries, but are coming along slowly (for Canada in particular, Apple Pay ran into some trouble launching, and Samsung Pay is also seeing some delays compared to when they originally hoped to launch).

The interesting new additions are Spanish, Brazilian Portuguese, Korean, Polish, and Traditional Chinese. This would indicate that Google may be hoping to reach Hong Kong before Samsung pay launches there later this year, and Spain and Brazil are likely also on Google's agenda for the near future (both of which already have Samsung Pay).

The two countries that stand out the most however are South Korea and Poland.

South Korea is Samsung's stronghold. Samsung Pay launched there in August 2015, and Samsung holds around half the smartphone market all by themselves. It'll be interesting to see how Google approaches the South Korean market. Will they focus more on LG (who are supposedly working on their payment solution) and other phone manufacturers? Or will they try to take Samsung head-on?

None of the major smartphone payment solutions have targeted Poland yet, however their high adoption of EMV tap to pay terminals could result in them being a fantastic choice for Android Pay's expansion. We'll have to wait and see if any real announcement about Poland comes forth, but it could be a fantastic first step into continental Europe.

Where do you think will see Android Pay first? What countries should Google target that they haven't yet? Sound off below!

Source: Reddit



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

Google’s October 4th Event Likely to Talk about Android-Chrome OS Hybrid “Andromeda”

We had every reason to be pumped up about the upcoming October 4th event from Google. After all, it's not everyday that Google releases new hardware that has had heavy influence from the Search Giant — keeping in mind that Google is still primarily a software company. But recent news might give us even more reason to be excited about the event.

First up, Google's SVP of Android, Chrome OS and Google Play, Hiroshi Lockheimer tweeted a cryptic message about October 4th being a significant point in recent times, much alike the time when Android was first released.

By itself, the tweet tells us nothing new. We know Google will be releasing its "made by Google"-marketed Pixel devices on this day, so the tweet could be complete in that sense. That's a significant first for Google and for Android, so it is not far-fetched to think of it as being something very important for Android as a whole, especially if Google decides that Pixel is the route that they are going to stick with for the future instead of Nexus.

But once the tweet went out, multiple sources started pointing that Pixel might just be a part of the complete picture. Android Police went on record to say that Google might tease the long rumored Android-Chrome OS hybrid, codenamed "Andromeda", during the October 4th event. This hybrid OS was first talked about when The Wall Street journal published a report a year ago claiming information from multiple sources of the existence of this OS. They mentioned that while the OS will be unveiled in 2017, Google might show off an early version of it in 2016. With 2016 entering its last quarter, and with Google having an event planned already, the stage is set for the world to know more about Andromeda.

Then, 9to5Google came forward with a report claiming that the unreleased Andromeda is being tested on the HTC-made Nexus 9. They found multiple references to Andromeda in the Android source code. One such set of references is in SurfaceCompositionTest, which is said to be a set of low-level tests to measure graphics performance.

According to the tool, the minimum score (all we know is that these scores generally refer to a device's graphics performance) needed for Andromeda is an 8.0. By comparison, Android seemingly requires at least a 4.0. One of the more notable aspects of this specific test is that it was performed on the Nexus 9 which scores "around 8.8," a score just barely surpassing Google's minimum requirements.

Another reference to Andromeda is here, and coincidentally, the Nexus 9 is once again referenced as well.

image-001

Andromeda gets yet another mention here, where an upcoming free-form window management feature (which is already present on Android 7.0 Nougat but is not easily user-accessible) is being talked about. There's no mention of the Nexus 9 here, but talking about something like free-form windows makes sense if your OS targets tablets, PCs and laptops more than just smartphones.

So from what we know so far, Andromeda is real and it is coming in the distant future. There's a good chance that Google just barely teases the new OS in the October 4th keynote, but there are slim possibilities that an early alpha release might just be announced as well, which would be in-line with The Wall Street Journal's report. Even if the Pixel and Andromeda do not excite you, October 4th is the event to look forward to for the future of Nexus, Android and Chrome OS to see what Google's plans are.

What are your thoughts on Andromeda, Google's upcoming Android-Chrome OS hybrid? Should Google release yet another operating system? Let us know your thoughts in the comments below!



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

Replacement Galaxy Note 7 Units Continue to Have Battery Issues

Samsung has been trying to replace defective Galaxy Note 7s as quickly as possible, but it looks like the South Korean tech giant has run into yet another issue with the device. It's being reported that customers in South Korea who have had their Galaxy Note 7 replaced are still experiencing issues with the batteries inside their smartphones. Thankfully, it's not the same defect that has been causing units to catch on fire and explode, but this isn't helping the company's reputation at all right now.

South Korean customers have reported their new replacement units are having one of two new issues with the device. Some people have noticed their Galaxy Note 7 begin to overheat while the device is charging. There haven't been any new reports of explosions from this overheating issue, but it definitely is a possibility if they heat up past a certain extent. Other customers have noticed their Galaxy Note 7 is actually losing battery life while the device is plugged in and supposed to be charging.

Samsung is currently calling these new issues "isolated incidents" and cannot confirm whether or not this will be happening in other parts of the world. So far, there hasn't been any reported issues like this for those in the US having their Note 7 replaced, but it is something that customers should look out for. So even if your Galaxy Note 7 has the green battery indicator in the status bar, you'll still want to keep your eye on the device while it's being charged. It would be a good idea to not only monitor if the device is actually being charged, but to also check and see if it is overheating too.

We'll be keeping our eye on the Galaxy Note 7 forums here to see if this turns into a common issue in other parts of the world. We are bound to learn more in due time.

Source: The Wall Street Journal



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

Mediatek Officially Unveils the 10 nm Helio X30 and 16 nm Helio P25

At a press event in China, MediaTek held their official launch event for their long awaited flagship Helio X30, and their latest mid range chip, the Helio P25.

The Helio X30 is a 10 core big.LITTLE chip, with two 2.8 GHz A73 cores, four 2.2 GHz A53 cores, and four 2 GHz A35 cores on TSMC's 10 nm FinFET+ process. The Helio X30 brings support for up to 8 GB of 1866 MHz LPDDR4x RAM, support for eMMC 5.1 and UFS 2.1, faster image processing (claiming support for up to 28 MP at 30 fps), video encode at up to 4k 30 Hz with both HEVC and VP9, hardware accelerated video decode at up to 4k 10 bit 30 Hz with support for both HEVC and VP9 (although unfortunately not VP9's successor AV1, which is expected to start making waves next year when the Helio X30 releases), 2560×1600 displays at 60 Hz or 1920×1080 displays at 120 Hz, better audio with a claimed 120 dB SNR and -100 dB THD (up from 110 dB and -95 dB on the Helio X20), a faster sensor processor (using a higher clocked Cortex-M4), category 10 LTE with 3x carrier aggregation, and a 2×2 802.11ac wifi radio.

Helio X30 X20 SpecificationsHopefully the move to A73 cores and a 10 nm process will result in better thermal performance than what we saw last year, as many phones with the Helio X20 and X25 effectively disabled their A72 cores, and ran on just the 8 A53 cores in most situations. The A73 is a fantastic core, with ARM slightly shortening their pipeline in order to get better thermal performance, higher clock speeds, wider out-of-order execution, and larger caches, which should continue on the fantastic performance that we saw from the A72 core.

PowerVRThe move from A53 cores to ARM's new A35 cores for the smallest cluster is a fantastic addition. A35 cores use an incredibly low amount of power, and should be a spectacular fit for low-power tasks while the phone is sleeping, and should provide some real differentiation from the A53 middle cores. On the Helio X20 and X25, the small clock speed differences between the two sets of A53 cores brought up serious questions as to how much benefit MediaTek actually sought to gain by adding the extra cores, and how much of it was just about hitting the number 10 for core count for marketing purposes (with phones now actively advertising core count directly on in-store displays).

MediaTek will also be switching away from ARM's Mali GPU series, and back to Imagination Technologies' PowerVR GPU series which was found in the original Helio X10. They will be using the PowerVR Series7XT in either a 4 cluster or 4 thread configuration running at 820 MHz. That would indicate that they are likely using either the GT7200 or GT7400 GPUs, clocking in at either ~105 GFLOPS or ~210 GFLOPS (FP32). While GFLOPS is a fairly poor way to measure performance, that could indicate an improvement over the ~105 GFLOPS Mali-T880 MP4 used in the Helio X20. Unfortunately, it is still quite a ways behind the Mali-T880 MP12 found in the Exynos 8890, and the Adreno 530 found in the Snapdragon 820, let alone what Qualcomm and Samsung will be launching next year to compete with the Helio X30. That being said, the doubling in RAM speed compared to the Helio X20 and X25 should provide a major boost over what we saw this year, as GPUs benefit greatly from faster RAM.

Helio P20Unfortunately, the shift to Imagination Technologies won't help on a development front either (despite MediaTek's recent efforts to be more developer friendly), as PowerVR is currently known for having the worst open source support out of any major GPU vendor, despite being a high priority project at the FSF for years. There have been reports that there is talk internally at PowerVR to follow in AMD's footsteps to fix this issue, however no public comment on their path forward has been made yet, and one of the main champions of the open source driver left the company last month for greener pastures. Unfortunately, there is not much that we can do at this point other than hope for the best.

As part of the launch party, MediaTek also talked a bit about their Helio P20, which recently released for sampling to manufacturers. The P20 will be produced on TSMC's 16 nm FFC node, and will have 8 A53 cores clocked at 2.3 GHz with a Mali-T880 MP2 GPU at 900 MHz, either up to 6 GB of 1600 MHz LPDDR4x RAM or up to 4 GB of 933 MHz LPDDR3 RAM, hardware accelerated HEVC video decode at up to 4k 30 Hz, video encode at 4k 30 Hz in h.264, support for 1920×1080 displays at 60 Hz, 110 db SNR and -95 db THD audio, and category 6 LTE with 2x carrier aggregation with Dual-SIM Dual Standby support.

While MediaTek didn't reveal much about the Helio P25, it is expected to be a higher clocked version of the P20, similar to the differences between the Helio X20 and X25.

What do you think of MediaTek's new chips, and their recent progress in the mobile market? Let us know in the comments below!



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

dimanche 25 septembre 2016

Android Gaming Graphics at a Standstill: What Is Holding Us Back, and the Path Forward

Over the past couple years, we've seen a massive shift in the Android gaming market. Many major companies have shifted away from releasing new original graphically intensive 3D games, and are instead focusing more on either porting games from other platforms, or expanding their current games, often in an attempt to drive microtransactions.

This is fantastic for mid-range and budget devices, as despite their weaker GPUs, they are now starting to be able to play everything and anything out there, but it leaves flagship devices wanting something more. Not every phone is going to have an Adreno 530 (while not a very reliable comparison, at ~500 GFLOPS peak performance, it is twice as fast as an XBox 360's 240 GFLOPS ATI Xenos processor), with the popular Adreno 505 found in entry level processors running at 1/7th the speed. Despite the lack of improvement in dynamic effects, the massive resolution increases that we have seen have resulted in games struggling to run at full native resolution, with OEMs having to develop resolution limiting tools, like Samsung's Game Tools and HTC's Boost+, and many developers deciding to hardcode their games for 30 Hz and lower resolutions (restrictions which are lifted on some devices).

HTC Boost+ Battery LifeThose decisions highlight a stark truth: most Android devices are battery powered (with some exceptions like the Nvidia Shield TV), and developers have to balance quality with power usage (and heat). As you increase the graphical performance, you also increase the amount of processing being done, and the amount of power being used. Too hot, and people won't be able to play for very long (and their hands will be sweating the whole time), certainly not smoothly anyway. Not enough power used, and you won't be able to create the graphical representation that you want.

And those performance goals really are a moving target. Different chipsets and devices will have different levels of performance that they can accomplish without getting too hot, and you have to use the NDK to code for each one if you want to get the most out of the hardware available to you. Some devices are also thermally constrained due to factors outside of the processing package

On the PC side, we've recently seen a shift towards developers and consumers focusing on increasing average frame rates (with a proliferation of 144 Hz displays), reducing microstutter, and preventing frame drops (or at least making them more bearable through technology like Freesync, which itself shares a lot of technology with the panel self refresh found in phones), as graphical improvements have seen diminishing returns. There still is a long way to go in regards to reaching a level where there is no longer any benefit to graphical improvements, but people started discovering that the smoother gameplay that comes with consistently high frame rates is extremely enjoyable.

NFS: No Limits Demo ShotBut who will drive these graphical advancements? We currently have a dearth of premium graphically intensive apps on Android. Many major game series that were previously paid apps are shifting towards a freemium model. Modern Combat and Dungeon Hunter had 4 paid releases before they started shifting towards freemium in the past two years, with Modern Combat 5 even starting out as a paid app before Gameloft switched it over.

EA's Real Racing 3 and NFS: No Limits look fantastic, but they also shifted their respective series from full-price games to freemium. They are absolutely littered with microtransactions (with in-game purchases running from $1.39 to $139.99 per item up here in Canada), including the pay-or-wait mechanics that have become so popular in freemium games, with you having to pay to refill your fuel gauge every couple races (or wait for it to refill). Dead Trigger 2, Assassin's Creed Pirates, and others have followed the same trend. The latest Assassin's Creed game, Identity, had its international launch earlier this year (with a soft launch two years ago) and is a mix of the two, with a full-price purchase, followed by microtransactions in the game.

Hockey Bird (Angry Birds 2012 IIHF Ice Hockey World Championship)Now, that's not to say that all games are shifting towards microtransactions and advertisements. We're still seeing many games like Pixel Dungeon and Square Enix's GO series that are fantastic stand-alone games. These games may not be the most graphically intensive out there, but their focus on solid core gameplay mechanics and pick up and play gameplay have created loyal followings that come back for every update or new release. And that holds true both for full price games and freemium games as well. The Angry Birds empire was built on the back of simple easy-to-learn gameplay, the ability to pick up and put down the game if something pressing is happening around you, and an over the top story-line designed to make you chuckle. All those things came together to create a huge merchandising line (with soft drinks, toys, cookbooks, theme park rides, and even the mascot for the 2012 IIHF Ice Hockey World Championship), and resulted in a highly successful film (pulling in almost 5 times its budget at $346 million in ticket sales).

That ability to pick up and play the game, and drop it on a moment's notice without worry really is major selling factor for many mobile games. Even just short time wasters like Flappy Bird, Crossy Road, Stack, and Nintendo's upcoming one-touch Mario game have huge followings, thanks to the simple mindless fun that they bring.

We've also seen an upswing in games that use carefully planned art direction to create stunning visuals, often without needing the most powerful processors. Games like Monument Valley, Limbo, Duet, and Alto's Adventure that are beautiful to just look at, never mind the gameplay. Games that people not only want to play, but want to watch while they are playing it. Games where you find yourself immersed in the splendour of the game world.

We've also seen an upswing in games that use carefully planned art direction to create stunning visuals, often without needing the most powerful processors.

But while there has been a lull in new graphically intensive 3D games on Android, we have seen a resurgence of them on iOS. Apple's low resolutions, powerful GPUs, and low-level graphics API have resulted in a rich market of graphically intensive games, with flagship titles like Infinity Blade being created to showcase the platform's strengths, and existing games like Asphalt 8 being updated with Metal support, resulting in improved dynamic effects and other graphical enhancements. Enhancements that we haven't seen lately on Android, where all the recent improvements for Asphalt 8 have been about driving microtransactions.

Now, certain developers may be waiting for Android to support Vulkan before pushing those graphical updates, as coding them in for the current OpenGL versions as well may be seen as a pointless duplication of effort by some. The phones, tablets, and set-top boxes that can fully take advantage of the improved effects are the recent flagships, the ones that are likely to get Android 7.0 and Vulkan support.

Vulkan_500px_Mar15Vulkan is a huge deal for Android gaming (and for PC gaming as well). It's a new graphics API being developed by the Khronos Group (the same industry consortium in charge of Android's historical graphics API, OpenGL), that has evolved as a result of AMD donating their Mantle codebase to create an open standard (and an open source Vulkan SDK).

It results in substantially lower power usage and substantially higher performance by giving more direct access to the GPU. It also brings the Android platform to parity with the desktop, as the same version of Vulkan is used on both, whereas with OpenGL many phones used a cut down version known as OpenGL ES.

Could this be part of the reason why Google required support for either Vulkan or OpenGL ES 3.1 in Nougat, resulting in support for devices with the Snapdragon 801 chipset being dropped? Google may be trying to use Android 7.0 Nougat to create a platform for developers to target for graphically intensive games. A platform that is guaranteed to have better support for recent graphics APIs, allowing games to take advantage of the massive performance improvements that Vulkan brings (or even just OpenGL ES 3.1).

WALT_photoThey are doing it publicly to some extent as well with the Daydream platform specification, which is built on the backbone that Google Cardboard laid. The Daydream platform requires Android 7.0, Vulkan support, some special tuning for low latency, and a minimum hardware level. And Google has been pushing to make it easier to test and improve devices in order to ensure that, especially with the launch of their WALT latency timer, which costs $50 instead of the thousands that similar equipment normally would.

So far we've seen only two phones announced with support, the ZTE Axon 7 and the Asus Zenfone 3 Deluxe (with the Nexus 6P not being considered to be representative of Daydream ready due to issues with "thermal performance"), but there are more coming from Samsung, Huawei, HTC, LG, Alcatel, Xiaomi, and others, Now, Daydream is a specification for virtual reality support, but large portions of it carry over to day to day gaming as well.

It will be interesting to see how the arrival of Vulkan causes a shakeup in the market over the next couple years. As games begin to adopt it, we will see improved graphic performance, higher frame rates, and potentially reduced power usage as well. Vulkan is a huge improvement, that will allow us to get more out of the same hardware.

The tech demos using Vulkan on Android, like Epic Games' ProtoStar Unreal Engine 4 demo, are simply beautiful, much like the ones that we've been seeing with Metal on iOS, like Epic Games' Zen Garden demo. It will be amazing to see the games that are released using Vulkan; even if we are not particularly enthusiastic about gaming on our phones, it's always exciting to see just how powerful our devices are getting, and gaming is one of the best ways to make that power tangible to consumers.



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