OnePlus 5 to Receive an Official Build of LineageOS 14.1 Next Week

The OnePlus 3 and OnePlus 3T was and still is an incredibly popular smartphone here in the XDA forums. With Google dropping the Nexus series last year, it seemed as if the latest from OnePlus was able to step up and fill that role for the enthusiast community. The company had a bit of a bumpy launch with the OnePlus 5 but things have smoothed out since then and now we are a week away from an official build of LineageOS 14.1 available for the community.

Many of us are likely already looking forward to Oreo for the next custom ROM that we flash, and official builds from the popular custom ROMs are currently being worked on. This takes time though so you'll need to look for a Nougat ROM for the OnePlus 5 if you're anxious to flash something right now. This build of LineageOS 14.1 is becoming available thanks to XDA Recognized Developer linuxxxx, XDA Senior Recognized Developer codeworkx, xingrz, amartinz, and jumoog.

As with other builds of LineageOS 14.1 right now, it is considered a Nightly, but there shouldn't be any major bugs when it's released. For those who are currently on the unofficial build of LineageOS 14.1, you will need to perform a factory reset and then do a clean install of this. We're told the developers missed the cutoff point to get a build pushed out this week, so we'll have to wait until the build server creates one for the OnePlus 5 next week.

When available, you'll find the downloads on the LineageOS website here, and you can keep track of the changes happening right on their changelog page as well. You can find a GApps package on the LineageOS Wiki just in case you wanted to download it ahead of time.

Are you excited about LineageOS 14.1 for the OnePlus 5 or would you rather stick with OxygenOS (or even a different custom ROM)?

---

Check out LineageOS 14.1 in our OnePlus 5 forum

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

Latest L Speed Mod Now Compatible with Android Oreo

L Speed is one of the XDA's most popular mods. The application combines many tweaks to improve a device's performance and it's been available for rooted phones since early 2015.

XDA Recognized Developer and Contributor Paget96 has recently released the Android Oreo compatible version of the mod. The developer is actively seeking for Android O users to test some features, so if you are running the latest Android revision, give it a spin!

You can join the beta channel in Play Store to get the latest version, and you can also check out L Speed's forum on XDA.

---

Test out the beta

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

Honor 9 Kernel Source Released

Big news for the Honor 9 Development community: The Kernel source has been released! The Honor 9 has already seen a bit of success with development, while the community has put out some custom ROMs and mods that work on the device. Now that the kernel source has been released, you can expect that to turbo-charge development for this phone.

The Honor 9 was released in June of 2017

The unique light-catching design on the Honor 9 makes it one of the most stylish phones available.

In the XDA Forums you'll find that the community has put together a RROS ROM, a LineageOS ROM, a TWRP recovery and several other mods.

Grab the source code from the link down below and be sure to check out the XDA Forums for the Honor 9, where you can find more development-related threads.

Get the Kernel Source Here Honor 9 Forums

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

Playback Audio Won’t Pause for Notifications in Apps Built for Android 8.0

Audio ducking on Android refers to the volume of audio decreasing when another audio source (usually notifications) starts playing. When a notification ducks the audio of the already playing audio source, it's taking the audio focus away from the app, just like Pokemon Go does you start it up while music is already playing. A way to fix that was detailed here, by the way. Apps do have the choice to duck audio or even entirely stop playback; for example, if you play a song on Spotify then open a YouTube video, Spotify stops music playback entirely. However, for any apps that target Android Oreo (SDK level 26), that will be changing as playback audio will no longer pause for incoming notifications.

---

Android Oreo has Changed the Way Playback Audio Respond to Notifications

Now with Android Oreo, apps targeting the latest release will no longer stop playback whenever another app, or a notification, takes audio focus. Instead, these apps will simply duck the audio by default. For example, the Podcast Addict application will stop media playback briefly whenever a new notification comes in, then resume playback afterwards. If Podcast Addict instead is updated to target SDK level 26 (AKA Android 8.0 Oreo), then it's volume will be lowered (audio ducking) rather than completely paused when a notification is received.

This among other changes such as Rescue Party and Project Treble are showing how Android Oreo is more about optimization and behind-the-scenes improvements, rather than large scale changes. It's great to see Google making improvements in smaller areas and paying attention to the little parts of the operating system. The smaller bugs of Android have been the subject of criticism for years.

We'll continue looking for other changes that have been made. Stay tuned to the XDA Portal using our XDA Labs app to keep up to date with all of the latest Android 8.0 and other Android related news.

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

Android Oreo Adds a Splash Screen API so Developers can Easily Build App Loading Screens

Most developers have mixed opinions when it comes to splash screens. Some advocate for the use of it to hide the app loading in the background and then transition to it seamlessly. On the other hand, some consider splash screens a waste of time both for the user and the developer. Google's stance on this is mixed, having previously not promoting their use but have since started using splash screens themselves in many applications. And with Android Oreo, Google wants to make building a simple splash screen a way easier task for developers.

Google has introduced a "splash screen API" in Android 8.0. This API allows developers to easily set a drawable resource as an app loading screen. You can also set a splash screen between heavy activities inside your app. Before Android Oreo, there were many different approaches to building a splash screen, the most common one being creating a drawable, a custom theme, and a SplashActivity. Google wants to streamline and make the process easier for developers by having them take advantage of this new API.

This change isn't currently documented in the Android Developers site. The commit was added on April 13th to AOSP, right between the first and second Android O Developer Previews were officially released. As such, in order to learn how to use it, you'll need to reference the AOSP commit and check out the changes made since then. We do expect the official Google documentation for this API to be uploaded eventually in order to make things easier.

This isn't the only change included for developers in Android Oreo though, as Google has introduced lots of new, useful APIs and developer features. We've done a lot of digging to find these changes, but to see more, you'll need to dig into the Android Open Source Project yourself!

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

Win an Honor 9! [Open to All Countries]

We're giving away a shiny new Honor 9, a phone which we found to have stellar gaming performance and a terrific camera. This phone is hard to come by currently as it is sold out in many places, so enter the contest below for your chance to win one of these beautiful phones!

Win an Honor 9 [Open to All Countries]

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

How to Sync Do Not Disturb Mode Between Android Wear and Your Phone

Android Wear 2.0 has been a much-awaited update, with watches such as the Moto 360 Sport only now getting it while the update came out in May for the Huawei Watch. With the Wear 2.0 update came many improvements, including the device now being able to install applications directly on your watch and a keyboard to reply to messages. One of the downsides of the update is that do not disturb mode no longer synchronizes between your smartwatch and your phone. In this tutorial, we'll show you how to sync do not disturb mode between your two devices. We gave a shout out to this application back in May, and today we'll show you how to set it up!

---

Do Not Disturb Sync for Android Wear 2.0

We will be setting up this application on our phone and our watch. You will need to set up adb on your watch. The steps are largely the same for Android Wear, but screenshots of the process are shown below.

You don't actually have to debug over Wi-Fi, but I find it most convenient. Once done, connect your watch to your computer using the following command.

  adb connect 192.168.1.100:5555  

The IP you connect to depends on the address your device shows under "Debug over Wi-Fi". A prompt should appear once your computer connects, allow your watch to be debugged. Once you have connected, you are ready to begin. No commands for initial setup are required if you are not using Wi-Fi.

Setting Up the Phone

To set up the phone, first download the application "DND Sync for Wear" below from the Google Play Store.

DND Sync for Wear (Free, Google Play) →

Now that you have installed it, open the application and enable the "Do not disturb" permission from within the app. You are now finished on the phone side of things.

Setting Up the Watch

Once you have installed the "DND Sync for Wear" on your phone, your Android Wear watch should notify you to suggest installing the application on the watch too. Tap the notification and install it. If you are not notified, open the Google Play Store and scroll down to "Apps on your phone". If you still can't see it, search for it yourself. You can simply search the package name "rkr.weardndsync" on the Google Play Store to find the application on your watch.

Once you have installed it, open the connected adb and run the following command.

  adb shell settings put secure enabled_notification_listeners http://ift.tt/2xHzEbi  

And then you're done! Changing to "do not disturb" on your phone should now change to "do not disturb" on the watch. This may prove useful to those of you bothered by the separation of device and phone as regards do not disturb with Android Wear 2.0.

---

Explanation

The application that is installed is simply for communicating the current state of "do not disturb" to the watch. The command we ran via adb for the watch is doing the exact same thing as the toggle above, except on Android Wear there is no GUI for enabling notification listeners (which is required to manage Do Not Disturb mode). This is why we require adb for the watch and not the phone. If we enabled the notification listener on the phone but not the watch, disabling do not disturb on the watch would disable it on the phone but not vice versa.

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