The Moto G4 Plus will get Android Oreo after all

The Moto G4 Plus will be upgraded to Android Oreo despite indications to the opposite. Check out Motorola’s statement and how long the update will take.

Motorola has taken to its blog to share news about the Android Oreo update for the Moto G4 Plus. An issue popped when Motorola published the list of phones it planned to upgrade and there was no mention of the Moto G4 Plus. Owners were promised upgrades to both Android N and O in promotional material and were understandably pretty annoyed. Motorola has removed any mention of Android O from the G4 Plus’ page, but it seems like it’ll be updated anyway.

instagram hack app

Added at the end of its blog post is the following statement:

Since the time of posting this, we have learned of some errors in our marketing materials around Android O upgrades for moto g4 Plus. It’s our general practice for the moto g family to get one major OS upgrade per device, so it wasn’t originally planned for Android O. But it’s important to us we keep our promises, so in addition to the N upgrade it has already received, we will be upgrading moto g4 Plus to Android O. Because this is an unplanned upgrade, it will take some time to fit into our schedule, we’ll update our software upgrade page when we have more info.

Motorola is claiming that the inclusion of Android O was a mistake, but it’s going to update it anyway. This is a fantastic move by Motorola. Even if it’ll take longer for the G4 Plus to be updated than its siblings, an update is coming and that’s a win. While many don’t expect multiple years of software updates for cheaper devices, it’s rare to actually hear a manufacturer say that.

See also:
Android 8 review: Oreo is for everyone

Android 8 review: Oreo is for everyone

4 weeks ago

September security update for Pixel and Nexus devices finally starts to roll out

Were you stuck on the August security update when you updated to Oreo? You’re not alone. Here’s the confusing tale of the September security update.


instagram hack app

Last week we brought you news of the impending September security update for Nexus and Pixel devices. Interestingly enough, Google released the details of the security update but didn’t upload the images to its developer site. In its notes, Google indicated that the September patch would be incorporated with the Oreo update for Pixel and Nexus devices. But after updating, users have still been stuck on the August security patch.

No one knows exactly what’s going on, but it does seem like the update is now starting to trickle out. Verizon posted support documents regarding its update for the Pixel and Pixel XL that contains the September patch. The build number is listed as OPR3.170623.007 with an Android security patch level of 2017-09-01. Google split the September update in two, with 30 issues fixed in the September 1 patch and another 51 bugs fixed in the September 5 patch. If we take Verizon’s update at face value, it appears to only have half of the September security update.

See also:
Latest Android Oreo bug disables mobile data on some Pixel and Nexus devices

Latest Android Oreo bug disables mobile data on some Pixel and Nexus devices

13 hours ago

To add to the confusion, some users are reporting incorrectly labeled updates. Regardless of being on Android 8.0 Oreo, users are getting notifications for an Android 7.1.2 update. The 50 MB download keeps the user on Android 8.0 but updates them to the September security update. This seems like a minor labeling screw up, but when you add it to all of the miscommunication so far, things get pretty confusing.

Android Oreo will let apps launch Google Assistant

The initial list of apps with Google Assistant integration is likely to be small, though it should continue to grow as time passes.

hack someones instagram

Google Assistant might be ahead of its competitors when it comes to certain tasks, but third-party integration is not one of those tasks. That looks to significantly change with Android Oreo, though there are a few things to consider.

Thanks to code found on the Android Developers website by XDA Developers, we have learned of the capability for an app to create a new task in Android’s activity manager. In other words, developers can open and run Google Assistant within their apps without the need for folks to leave the apps.

Not only would the feature keep folks within apps, but allows developers to harness Google Assistant’s capabilities. This would also allow Google to buff up its AI assistant quite a bit, since Google wants folks to utilize Google Assistant as much as possible in order to grow even more.

See also:
Some folks have reported Bluetooth issues with Android Oreo

Some folks have reported Bluetooth issues with Android Oreo

5 days ago

Finally, keep in mind that you can set other virtual assistants as the default. This means that developers can use Google’s AI to integrate the likes of Microsoft’s Cortana and Amazon’s Alexa into their apps.

There are a few caveats, the biggest being that you will need to be on a device that runs Oreo. Furthermore, the app itself must support Oreo, which means the initial list of apps that integrates Google Assistant is likely to be small.

5 Android apps you shouldn’t miss this week – Android Apps Weekly!

The 206th Android Apps Weekly is out! This week it’s about depression, Final Fantasy XV: Pocket Edition, no root theming, and more Android apps news!

Android Apps Weekly featured image
Welcome to the 206th Android Apps Weekly! Here are the the headlines from the last week:

  • Android Oreo will get non-root theming. A third party app called Substratum will include the feature. There are some caveats. You have to use a computer to make it work. It also breaks a bit of basic functionality. It’s nothing serious, though. It’s a bit unconventional. However, it’s one step closer to native theming on Android. Plus, Substratum is a fairly excellent app on its own.
  • Telltale Games launched a huge summer sale this week. Included are four The Walking Dead games, both Minecraft: Story Mode titles, The Wolf Among Us, Game of Thrones, Guardians of the Galaxy, and others. The sale includes the base game as well as the season pass for those titles. That means you can get the whole game at a discount. It might be worth it for adventure game fans.
  • Google is trying to help depressed people. They’re working with the National Alliance of Mental Illness to get people help. Google Searching the right keywords now enables you to take a PHQ-9 test. The results of the test can help determine how depressed one is. It’s not a diagnosis and people should seek a physician if they have bad symptoms. However, it could push people in the right direction and that’s a good thing.
  • Square Enix announced Final Fantasy XV: Pocket Edition this week. It’s essentially a remake of the original game. It has simpler graphics, touch controls, and more. It tells most of the same story as the console version. They appear as episodes similar to Telltale Games titles. There are ten episodes. The first one will be free to download on mobile. The other nine will likely be in-app purchases. Final Fantasy XV proper is coming to PC later this year as well.
  • Android Instant Apps rolled out to 500 million Android devices. Instant Apps are lightweight versions of the full apps. You can use them without downloading the full app. They’re mostly for quick tasks. That way you don’t use up all your storage on apps that you would only use once or twice. In any case, it’s out now. You can check around your Google Play settings to see if you have it.

For even more Android apps and games news, updates, releases, and more, check out this week’s newsletter by clicking here! You can sign up for the newsletter using the form below if you want. You can also click here to check out the Android Authority app for even faster updates!

Android Apps Weekly newsletter!
Subscribe to the Apps Weekly newsletter.


Bola

Price: Free / $3.49
DOWNLOAD ON GOOGLE PLAY
Bola is a new budget manager app. It’s also rather simple. You track your paychecks, expenses, and budget. The goal is to keep yourself appraised of your own spending habits. It also supports multiple currencies, multiple budgets, and cloud syncing. There aren’t a ton of bells and whistles. It does do the basics very right, though. Those who need hardcore expense reports will need to look elsewhere. You can get into the door for free. The full version costs $3.49.
DOWNLOAD ON GOOGLE PLAY

Cavefall

Price: Free / Up to $9.49
DOWNLOAD ON GOOGLE PLAY
Cavefall is a new infinite runner. You won’t run in a straight line, though. The player falls infinitely through a cave instead. You tap the screen to jump from side to side. The goal is to get items, avoid obstacles, and kill bad guys for as long as possible. It also includes hidden levels, power-ups, daily challenges, achievements, and leaderboards. It is a freemium game but it won’t ask you to make $99.99 purchases either. It’s not bad for what it is.
DOWNLOAD ON GOOGLE PLAY

Style Music

Price: Free
DOWNLOAD ON GOOGLE PLAY
Style Music is an interesting new music app. It does the basic music app stuff. That includes showing you music. It comes with a traditional media player view as well as a folder view. Some other features include Chromecast support, 24-bit FLAC support, and more. The most interesting feature is the ability to stream one of the 50,000 radio stations. This is definitely one of the better apps that can do both radio stations and your library. It’s a bit rough around the edges, though.
DOWNLOAD ON GOOGLE PLAY
Style Music

Combat 

Combat Squad

Price: Free with in-app purchases
DOWNLOAD ON GOOGLE PLAY
Combat Squad is a new FPS game. It’s about as standard as an FPS title gets on mobile. It comes with a variety of multiplayer modes, including one vs one, five vs five, and seven total game types to play. The graphics use Unreal Engine 4. The game also boasts advanced tactical AI, but we’re sure that’s probably mostly marketing talk. FPS fans should be able to enjoy this one for at least a little while if not longer.
DOWNLOAD ON GOOGLE PLAY

hack instagram password


WallR

Price: Free / $1.99
DOWNLOAD ON GOOGLE PLAY
WallR is a new HD wallpaper app. It boasts a massive collection of over 100,000 wallpapers. It can also auto-set wallpapers periodically, download wallpapers, and more. You can also have any wallpaper crystallized into a low-poly image for even more options. The free version does little more than let you wander around the app. You have to dish out for the full version in order to play with most of the app’s features.
DOWNLOAD ON GOOGLE PLAY
WallR

Android 8 review: Oreo is for everyone

In our definitive Android 8.0 Oreo review, we analyze all the new features in Android 8 Oreo and all the small improvements that Google baked into our favorite operating system.

hack someones instagram

Three years ago Google introduced us to its new design language called Material Design. It was flat, graphical and colorful. It was the visual change that ushered in the beginning of a new age for Android, one that focused less on the rapid expansion of Android’s feature set, and more on refining what already existed and paving the way for the future.

In many cases, Android’s maturation period included absorbing popular features that debuted elsewhere, whether in manufacturer skins, alternate launchers or via the custom ROM scene. More and more attention was placed on battery life, security, performance stability and fine-grained user-facing control. Not as sexy as a complete visual overhaul, perhaps, but vastly more significant.

See also:
Android 8.0 update: when will you get it?

Android 8.0 update: when will you get it?

3 days ago

Android 8.0 represents the current pinnacle of that effort, the very tip of the spear, fresh from Google’s workshop. Android 8.0 Oreo is as comprehensive a version of Android as there has ever been, and it is as stable, feature-rich and functional as ever. While on the surface it may lack grand visual changes, what lies beneath is stacked with usability improvements and polish.

This is the Android Authority Android 8.0 review.

Note: The software version I will be referencing in this Android Oreo review is the first iteration of Android Oreo found on the Google Pixel, which I’ve been using for the better part of a week now. Note that supported Nexus devices will have a slightly different experience, as will devices by other manufacturers when they get the Oreo update. So while your Oreo experience may look a little different, the underlying features described here will be fundamentally the same.

TL;DR

Android 8.0 Oreo is the most palatable mainstream Android version yet. It is visually consistent, simplified, feature-rich and polished. Oreo is clearly designed to appeal to as wide an audience as possible, from satisfying the die-hard Android fan with its comprehensive feature set and advanced customization potential, to accommodating the iPhone switcher or tech debutante with its simplified layout and intuitive user experience. OEMs are even on that list, and we’ve seen increasingly more of them give up the manufacturer skin game in favor of what Google serves up. Oreo is for everybody.

The review that follows will be broken up into four key sections. The first will focus on the visual aspects of Oreo, the second section will look at those features offering greater control, the third will explore the ‘rapid access’ side of Android 8.0 and the last part will cover the smarter side of Oreo. If you want to see the development history of Oreo, take a look down memory lane with our Android O developer preview feature tracker.

1. Looking good

Between Android Nougat and Android Oreo there are no major visual changes, but those that exist have primarily been made to improve usability, increase consistency or add a layer of future-proofing to everybody’s favorite mobile OS.

The Settings menu is the most obvious place to start, as it has been further refined from what we saw last year. Most notably, the Settings menu in Oreo has been greatly reduced in size from previous versions of Android, with a lot more nesting of options under larger categories. For example, Network and Internet covers everything under that umbrella: Wi-Fi, mobile network, data usage, hotspot and tethering, VPN and airplane mode.

The Settings menu in Oreo has been greatly reduced in size, with a lot more nesting of options under larger categories.

The upshot of this is that the Settings menu is much shorter – just a page and a half on the Pixel – and is arguably more logical, even if it does require more taps now to access key settings like Wi-Fi or Bluetooth (both of which are, of course, easily accessible in the Quick Settings and at the top of the notifications shade).

The downside of this change is that in some cases the useful information shown below the main heading in Nougat, like, for example, the Wi-Fi access point or Bluetooth devices you are currently connected to, has been replaced with a brief summary of the settings within that category. Some Settings categories, however, like battery and storage, do still show that critical information.




Even within those categories things are kept simple. What Google considers to be more advanced options appear in a drop down menu. In the Display settings for example, you’ll only see four options up front: brightness, Night Light, adaptive brightness and wallpaper – the kinds of settings a casual Android user would need. Tap the caret next to Advanced though, and you’ll see the full gamut of display settings: display timeout, screen rotation, font and display size, screen saver, ambient display and so on.

For the most part, Oreo’s Settings look like Nougat (minus the slide-out hamburger menu): a largely monochrome affair on a light background with a few touches of a single color to draw your attention to key information, like Google’s Suggestions, which occasionally appear at the top of the Settings menu, or important features that have been activated, like Airplane Mode, Do Not Disturb or Data Saver.

The same lightening up of the UI can also be felt in the Quick Settings and notifications area. Swipe down once for the notifications shade and at the top you’ll see the six on/off toggles on a light gray ground, to keep things more visually consistent with the white notification cards below them. Above the toggles you’ll now see carrier info, status bar icons, battery info and the time, while the date is now found below the toggles in a more legible font.

Swipe down again and you’ll see the full Quick Settings area, which is tabbed if you have more than nine settings visible. As with Nougat, several toggles here simply activate and deactivate a setting, like the flashlight, Battery Saver or Airplane Mode. But others, including Wi-Fi, Bluetooth and Do Not Disturb, provide access to a mini menu so you can make minor changes without leaving the Quick Settings area.

You can rearrange the order of the Quick Settings, which will be reflected in the on/off toggles at the top of the notifications shade, and long-pressing an icon still takes you to the full Settings menu for that feature. You’ll also note that the User, Edit and Settings icons have now migrated to the bottom of the Quick Settings area for easier access on large-screened devices. Note: long-pressing the Settings icon here will still enable the System UI Tuner in the Settings, but it still only features toggles for status bar icons and some settings for Do Not Disturb mode.

Google has also streamlined the notification cards. If you have more notification cards than can fit on the screen, at the very bottom you’ll see a series of app icons indicating the remaining notifications. As you expand and contract the notifications list you’ll see those icons pop up into full notification cards or pop back down to the little icon tray.

Persistent notifications, like for apps running in the background (password managers, weather, Tasker and the like), will appear in more condensed notification cards, which you can expand for more information. Multiple notifications from the same app will still be bundled together as in Nougat, and Quick Reply for supported apps is still on board. For fans of Google Play Music, the media controls in the notification shade will now adopt the color palette of the album artwork, and this will be reflected in the lock screen background as well.

The launcher experience (at least on the Pixel) is much the same, but when you launch the app drawer, accessible simply by swiping up anywhere on the home screen, you’ll see the navigation buttons at the bottom of the screen switch from white to black for better visibility. Long pressing the home screen will bring up options for changing the wallpaper, adding widgets or accessing the home screen settings.

In the home screen settings you can enable or disable the app suggestions at the top of the app drawer, toggle what we used to call Google Now on or off, enable home screen rotation, decide whether you want new app installs to add an icon to your home screen and get access to two new Oreo settings: adaptive icons and notification dots (we’ll cover the latter a little further down).

Adaptive icons are one of the simplest ways Google has come up with to increase the consistency of the Android experience across devices from multiple OEMs, many of which use different shapes to Google.

Developers simply create a larger than necessary background for their app icon, which can then be masked with various shapes to create a more consistent look to the app icons on your phone.

The best part is that Oreo lets you decide which shape you like best: system default, square, round, rounded square, squircle or teardrop (like the Allo and Duo icons). Of course, not every app developer has jumped on board yet, but Android Studio has a simple wizard to guide devs through the process so it shouldn’t take long to catch on. If you want to know more about adaptive icons, read Gary’s excellent explainer on downloadable fonts and adaptive icons.

In terms of future-proofing the visual side of Android, Oreo has also included a couple of new features to keep up with the times. In previous Android versions, there was a maximum screen aspect ratio of 1.86:1, which is basically the widescreen cinematic standard. With the emergence of taller and narrower aspect ratios including 18.5:9 on the Galaxy S8 and Note 8, and 2:1 on the LG G6, Oreo no longer has a default maximum aspect ratio – it is simply the default aspect ratio of the device. Now we just need to get app developers on board to properly adapt their apps to the new formats.

Oreo also has built-in support for wide color gamut apps, essentially meaning that on devices with the requisite HDR display technology, apps can display a much larger range of colors. There aren’t a lot of phones out there with the necessary display hardware to take advantage of this yet, but that number will increase greatly as Android 8.0 Oreo continues to roll out next year.

And finally, everybody’s favorite: the Android Easter Egg and emoji. As discovered in the final Android O developer preview, the Android Oreo Easter Egg is an…octopus. He floats around the screen, changes sizes when you rotate your device and can be dragged around the screen. And…that seems to be about it.

Android 8.0 Oreo also officially delivers the new circular emoji at the expense of the blob emoji that were loved and hated in equal measure. We’ve written about this elsewhere on the site, including Google’s reasoning for making the change, so I’ll leave you to your brooding.

What I hope has been apparent in this section is that Google is finally paying attention to the small stuff. Lightening up the UI, introducing adaptive icons and new emoji may not seem like a big deal, but they make the Oreo experience more consistent. Condensing the Settings menus, moving icons around and collapsing persistent notifications make Oreo more usable. And adding full color gamut support while removing maximum aspect ratios ensures Android 8.0 will look great on devices that aren’t even out yet.

2. Taking control

Android 8.0 is also more about assuming control than any previous version of Android. Whether it’s Google putting the brakes on rampant resource-hungry app processes or users having more power to limit what apps can access and how notifications are handled, Oreo has it in droves.

New in Oreo is the ability to snooze notifications. Partially swipe a notification away and you’ll now see two icons: one leading to the notification channel settings for that app and another that sets a timer before the notification reappears. By default it’s one hour, but you can also choose from 15 minutes, 30 minutes or two hours.

Another key part of Oreo’s notification handling is the introduction of notification channels. Apps that target Oreo’s API 26 must include notification channels (while apps that don’t will continue to behave as they currently do). App developers then identify as many different types of notifications in their app as they like and Oreo lets users decide which app notification channels they want to be alerted to, and how.

Once you’re in the notifications settings for a particular app, you’ll see several options. You can disable notifications entirely, allow notification dots (more on this in the next section), or flip a switch for each kind of notification channel the app developer has identified. Some apps will have very few, but others, like the Google app, can have more than a dozen.



Each notification channel gives you three basic choices: disable it entirely, take it as is, or fine-tune it the way you like. For the first two, simply flip the switch to the on or off position. For the latter, tap the channel name and you’ll see various options including setting the importance for that notification channel (including the Urgent setting which makes use of a universal and thus, more consistent, app overlay alert type), changing the notification sound associated with it, enabling or disabling vibration, and so on.

Benefiting from notification channels is a gradual process – start with the defaults and limit particular notification types as they annoy you.

To do this for each and every notification channel in each and every app on your phone would be a herculean task, but what matters is the fact that it exists and you have complete control over it. Benefiting from notification channels is a gradual process: start with the defaults and limit particular notification types as they annoy you. Power users may want to devote their first weekend with Oreo to customizing every single notification on their phone, but everyone else can either ignore them or cherry pick as necessary.

Picture-in-Picture mode (PiP) is one of Android 8.0’s flagship features, previously available on Android TV, but not mobile. Primarily for video players and apps in which you watch content like Chrome, PiP lets you keep watching what you’re doing in a small floating window while otherwise going about your Android business – it’s a little like a free-form video version of split-screen, which also returns in Android 8.0.

In supported apps, hitting the home button will keep your video playing in a movable window in the bottom right of the screen. You can drag it around the screen and tap it to access playback controls or make it full screen. Of course, you can also disable this feature on an app by app basis if you don’t like it. Simply go to the App Info page for the app in question, or visit the Special app access section in Apps and Notifications to see all apps with support for PiP.

Background execution limits are one way Google has devised to throttle the amount of resources used by background processes. As you know, many apps like to keep various processes running in the background, whether to more quickly serve you notifications or to keep track of where you are. But you know what they say about giving someone enough rope, so with Oreo, Google has said enough is enough.

In Android 8.0, rather than allow apps to run rampant with your battery life in the background, Oreo limits their requests to scheduled windows of activity. Gary has covered how this all works in a great background execution limits explainer, but what it all means is better battery life for you and less strain on your device. By default, these limits only apply by default to apps targeting Android O, but you can enable them for any app by going to the Battery usage section in the App Info page and turning the toggle for Background activity off.

A couple of other features available prior to Android 8.0 Oreo are also aimed squarely at keeping you in the driver’s seat where your device security is concerned. Google Play Protect lets you know even before you install an app that it has been certified safe by the Google Play team. Then, Play Protect scans billions of apps in Google’s marketplace daily to ensure things stay on the up and up.

As in Nougat, Oreo makes a note on the App Info page of where each app was installed from. Previously, enabling Unknown Sources used to be a blanket action, but now each app that wants to download another from anywhere but Google Play must have permission granted on a case-by-case basis. This access can, of course, be revoked at any time.

Android Device Manager is now known as Find My Device, a much easier to understand method for tracking, locking down or remotely wiping a lost device. Both Google Play Protect and Find My Phone can be accessed either via the Security and Location section or by going to Settings > Google > Security.

You still have granular control over the app permissions granted to each app on your phone, either by permission category or on a per-app basis. But you can now also monitor special app access settings, like the ability to display over other apps, have unrestricted data access, use PiP mode or modify system settings. Again, these settings will not appeal to everybody, but as with everything else in Oreo, it’s a power user feature safely tucked away where it’s accessible but not confusing to the casual user.

Which brings us to Vitals. Announced earlier this year, Vitals is another initiative by Google to improve system performance and stability. It includes security tools, OS optimizations and various tools for developers to monitor their app’s usage on your device. Again, what all this analytics means is that app developers can optimize their apps for your device, giving you better battery life and app performance.

And finally, Android’s Accessibility options get a nifty new Settings menu area where you can enable an accessibility shortcut – including from the lock screen. Simply choose your preferred accessibility service, either Talkback, Select to Speak or Switch Access, and press and hold both volume buttons to activate and deactivate the service. You can even add a preset accessibility button to the on-screen navigation area.

The new settings have been kept largely out of sight to avoid cluttering up what has traditionally been a daunting OS for beginners

Like most of the other settings we’ve seen so far, Oreo still provides power users with the advanced tools and options they’ve come to expect from Android. But they are again kept largely out of sight to avoid cluttering up what has traditionally been a daunting OS for beginners. Google has also added a lot of stuff in the background to get you better battery life and performance than ever before, and that’s always a welcome addition.

3. Quicker access

From Google Now to Google Assistant, Google wants to deliver the most pertinent information when it is needed, if not just before. Each successive Android iteration has become more intuitive, with increasingly greater attention paid to helping you get things done faster. Nowhere is that more evident than in Android Oreo.

We’ll start with notification dots. Notification dots are Google’s answer to unread badges. A small dot, with a color matched to the app icon on which it appears, will alert you to any notifications you may have missed. Dots are visible in both the app drawer and on the home screen, and a long press of the app icon will reveal a condensed version of the available notifications. These can swiped away as per normal or opened up for action.

Notification dots are Google’s answer to unread badges, nicely paired with app-specific launcher shortcuts.

When you long-press an app icon anywhere in Android 8.0, you’ll also get app-specific launcher shortcuts for each app. These are available whether or not a notification dot is present and can jump you straight into a variety of common actions.

For Twitter it might be search, post a tweet or send a DM. For Gmail you can compose an email or jump straight into one of your accounts and Photos will offer to free up space or take you to the search results for a particular set of your photos. Long pressing an app icon is also the quickest way to access the App Info page for each app or to add a widget.

Another speedy Oreo feature is smart text selection. This will be pretty familiar to anyone that regularly translates foreign words in Marshmallow or Nougat, but in Oreo it’s even smarter. Whereas Translate and Web Search were previously relegated to the overflow menu when you highlighted a section of text, Android 8.0 will not only anticipate the phrase you’re trying to highlight, but it will also predict which app you’re likely to want to use next and put it at the front of the copy/paste menu.

Following on from this, Oreo can learn your sharing habits too. On a basic level, Smart sharing connects apps with activities. So, for example, it will know to pair a photo of a receipt with an expense app or a selfie with messenger and social media apps. But Smart sharing will also begin to learn your habits and adapt to the apps with which you typically share specific types of content. It works with images, video, audio and text.

Android Oreo also introduces an improved Ambient Display. The familiar time and notification icons still ‘breathe’ on screen when you lift your device up, but now you’ll get larger notifications when a notification first comes in. Sadly, the ability to customize the lock screen shortcuts, present in the first developer preview, didn’t make it in the final build.

Further adding to the time-saving aspects of Android 8.0 is the new Autofill API, which promises to save you bucketloads of time on the web. Simply grant a service like Google’s Autofill or a password manager like LastPass permission to collect your passwords, credit card information and personal details and Oreo can offer to automatically complete web forms and log you into various accounts in future. Obviously, keeping your device safe and lock screen protected is essential here, but it’s a huge time saver.

One of the least touted features of Android Vitals is faster boot times. On the Pixel the boot up process is noticeably faster – twice as fast in fact. What used to take ages is now done in seconds, complete with a ‘powered by Android’ logo.

Whether it’s through home shortcuts to popular app functions, smarter text selection, autofilling forms or simply booting your phone up twice as fast, Oreo will have you doing what you need to do in record time.

Meanwhile, Project Treble, which separates the vendor implementation from the Android OS framework, allows each to be updated independently. This means that OEMs can simply update the Android part of their phones without requiring anything from silicon vendors, which theoretically means you’ll get updates faster (I’ll believe it when I see it). Treble will be a part of all new devices launching with Oreo, although current Pixel phones are also supported.

As with other recent Android versions, Oreo wants to help you get to the things that matter quickly. Whether it’s through home shortcuts to popular app functions, smarter text selection, autofilling forms or simply booting your phone up twice as fast, Oreo will have you doing what you need to do in record time.

4. Being smarter

Android 8.0 is also the smartest of all Android versions, benefiting from the impressive Google Assistant and all the machine learning Google’s software has done over the last years. But there’s still room for some good old-fashioned man-made improvements too. Here are a few of the smarter decisions Google has made with Android Oreo.

High performance Bluetooth audio was one of the first Oreo features to capture the attention of the Android masses. Sony donated its LDAC codec to Google for inclusion in Oreo, opening up the mobile OS to superior audio connections on supported hardware. I won’t go into detail here, as Rob’s LDAC explainer and Oreo audio feature articles do the topic much better justice, but suffice to say Oreo supports audio quality that surpasses both what the human ear can discern or what the vast majority of high-end audio equipment can even reproduce.

High performance Bluetooth audio was one of the first Oreo features to capture the attention of the Android masses.

Bluetooth 5 support is another well-publicized feature of Android 8.0. Offering such enticing benefits as double the data throughput over short distances or quadruple the range with less throughput, Bluetooth 5 is a big deal.

There has been a lot of confusion surrounding the tech though, so much so that our very own Gary Sims has published several articles outlining what Bluetooth 5 does (hint: it has nothing to do with streaming audio), how effective it is and how many devices can make use of it yet (hint: close to none). Like HDR display support for full gamut color apps, Bluetooth 5 is an investment in the future. Fortunately, the first devices to launch with Bluetooth 5 hardware and Oreo out of the box are very likely right around the corner.

Oreo also delivers a new multi-display mode, which allows you to pick up on a large screen whatever you were just doing on the small screen. Your phone will also be able to detect which display it should be running on and switch back and forth seamlessly. TextView auto-sizing will allow app developers to let Oreo automatically resize the text in their apps according to the available screen real estate.

Mouse pointer capture is another forward-thinking addition in Android 8.0, which opens up Android-powered devices like Chromebooks and others to mouse input (physical keyboard support, including for navigation, has also been added). I tried it on the Pixel and it absolutely works as advertised but as you can probably imagine, it’s super weird to use a mouse with a smartphone.

Android Instant Apps are another new introduction we’ve covered in greater detail elsewhere, but the ability to use select functionality of apps you don’t actually install on your phone is a revolutionary idea. AIA will massively reduce the need for keeping those occasional-use apps on your device, freeing up storage space for things you want, like photos or music, while still allowing you to access all the benefits of app-based activities. Check out Adam’s great video on the significance of AIA.

Downloadable fonts are yet another under-the-radar Oreo feature that most people will never think about twice. The short version is that 800 Google supported font libraries can now be accessed via a ‘provider’ app. This means that rather than every app on your phone requiring its own font library, naturally resulting in duplicates, apps can now simply call upon a shared library in the provider app, further reducing app file sizes. The best news is that this feature has been back-ported to API 14 (Android 4.0). Upgradable graphics drivers also make their debut on devices that ship with Android 8.0 Oreo out of the box.

Pushing the memory management in a different direction now, Android 8.0 includes disk space limits for cached data too. Under this new system, each app on your phone gets a certain amount of storage space for cached data. But whenever the system needs to free up disk space, any cached files above that per-app threshold will be purged. The good news for users is smaller cached file sizes overall.

Android 8.0 Oreo expands the capabilities of the OS by baking in additions like Bluetooth 5 and Wi-Fi Aware – neither of which are even supported by any hardware yet.

On the Wi-Fi front, Oreo makes use of a service called Wi-Fi Aware, also known as Neighbor Awareness Networking. Wi-Fi Aware basically lets you create micro Wi-Fi networks with other devices around you without using a traditional internet access points. Apps will be able to communicate in both directions between connected devices, although at this moment no supported hardware is available, so stay tuned.

Android 8.0’s Wi-Fi Assistant allows you to enable the Assistant to automatically connect you to high quality public wireless networks. The setting is disabled by default but it can be flipped with a switch, accessible via your Wi-Fi preferences in Settings.

While some of these Oreo features are more behind the scenes, niche-level stuff, like Sony’s LDAC codec for high quality Bluetooth audio connections, others, like Android Instant Apps, have the potential to dramatically change the way we think about apps. At the same time, Android 8.0 Oreo expands the capabilities of the OS by baking in additions like Bluetooth 5 and Wi-Fi Aware – neither of which are even supported by any hardware yet.

Android Oreo features: final thoughts

I can confidently say that I’ve never been as impressed with a new Android version as I am with Android Oreo. Even the bugs that typically plague a new update in the days immediately following its release haven’t settled on my trusty Pixel. Unlike some, I even managed to get through the developer previews with barely a hiccup, certainly an encouraging experience for the now-public version I’ve been enjoying these past few days.

A lot of features first introduced in Android Nougat and before have found their true home in Oreo, which finally seems to get everything right. It will surely have its detractors, but even they will have to admit this is easily the most polished and reliable version of Android Google has ever released.

Like its namesake, Oreo very much strives to be the OS for everybody, and Android finally seems to get everything right.

As we mentioned at the beginning, and like its namesake, Oreo very much strives to be the OS for everybody. I can easily see how an iPhone user could pick it up and run with it, just as easily as I can see Android fans adoring all the new advanced features and customization options.

Some folks have reported Bluetooth issues with Android Oreo

Some of these issues have been around since Android Oreo’s first developer preview, but at least Google is listening to feedback.

One of the improvements that folks were looking forward to in Android Oreo is Bluetooth connectivity improvements, particularly since Android Nougat and Pixel devices had their issues. Unfortunately for some people, those improvements were not made with the new update, though at least Google wants feedback about what exactly is wrong.

hack someones instagram

Taking a peek at the Nexus and Pixel forums, folks have reported a variety of Bluetooth issues, such as audio briefly cutting out every five to 20 seconds and skipping sounds that resemble the sound a “scratched CD” gives. Another problem is with Bluetooth automatically turning off almost as soon as it is turned on, something that also occurred in Nougat.

See also:
Everything new in Android 8.0 Oreo: features and changes

Everything new in Android 8.0 Oreo: features and changes

2 days ago

Most of the reported Bluetooth bugs seem to center around Android Auto, with four particular problems including music being played before breaking, outgoing calls using a phone’s speakers instead of the car, media content not being displayed correctly, and the phone not playing audio despite being paired over Bluetooth.

Some people who have experienced the aforementioned issues said those problems have been there since Oreo’s first developer preview, which was released in April. As such, they are rather irked that these Bluetooth bugs still exist, but at least Google is listening – the search giant wants folks to report any Bluetooth-related bugs as the following:

  • Car/Auto
    • Year/make/model of your car
    • Issue/symptoms
  • Headphones
    • Brand of headphones
    • Issue/symptoms
  • Bluetooth Speakers
    • Speaker brand
    • Issue/symptoms

How Oreo is better than Nougat: Notifications

Notifications have received three major updates in Android 8.0 including notification dots and notification channels. See how it improves the Android platform.

hack someones instagram

Notifications have received three major changes with Android 8.0 Oreo compared to Android 7.x Nougat. First, the handling in the notification shade has been improved, with extra actions now available. Second, there are notification dots. Thirdly, Android O adds notification channels, a unified system to help users manage notifications.

The notification shade has received a number of improvements, some visual, some practical. On the visual side the media controls have been given a color tweak. Previously the media controls in the notification shade displayed the album cover image, very nice. But now with Android 8.0 the background of the media control changes color according to the album artwork. The color also fades into the actual album artwork in the media controls.

Also in Android Oreo, when you partly swipe a notification to the side, you will be provided with options to snooze it for 15 minutes, 30 minutes, an hour, or two hours; tap any one of these to snooze that notification for the specified time. The partial swipe will also give you access to the notification settings for that app where you can disable the notifications as well as configure other behaviors like enabling the notification dot.

Notification dot? What is that? The notification dots appear on an app’s icon in the launcher (both on the home screen and in the app drawer) to let you know that you have an unread notification for that app. Long pressing on the app icon will show you the notification. The long press also reveals several app shortcuts specific to that app.

However, the biggest notification related change comes in the form of notification channels. Notifications are great, but if you are like me then after a few hours of not looking at my phone, I have too many notifications pending. To help combat this and to help users manage notifications more efficiently, Android 8.0 Oreo introduces notification channels for a more unified approach.

Apps written for Android 8 or later must implement one or more notification channels to display notifications to your users. Apps written for Android 7.x or lower will continue to behave the same as they do now, even on a device running Android Oreo.

The idea is that developers create a notification channel for each distinct type of notification that an app can send. For example, a messaging app could setup separate notification channels for each conversation group created by the user.

When a user modifies the behavior for any of the following characteristics, it applies to the whole notification channel, so all notifications posted to that channel behave the same:

  • Importance
  • Sound
  • Lights
  • Vibration
  • Show on lock screen
  • Override do not disturb

Wrap-up

Notifications are one of the key ways we interact with apps on our smartphones and any changes that streamline or improve that interaction are very welcome. Notification channels are a great idea, but it will be a while before we see both apps which support them and enough devices running Android 8.0 to make them mainstream.

What do you think about the notification changes in Android 8.0 Oreo? Are you looking forward to mainstream support for notification channels? Please let me know in the comments below.

How Oreo is better than Nougat: Background Execution Limits

Background tasks can be insidious, as the user has no knowledge of how much they are killing the battery. Android 8.0 Oreo has a plan to remedy that.

Broadly speaking, a runnable app (meaning one that has been loaded into memory and can be executed) can be in one of two states on an Android device: it is either a foreground app, which is currently being executed and is interacting with the user; or it can be a background app, an app which is not interacting with the user.

Foreground apps can be battery killers, but that is OK, as the user has made a conscious choice to play a 3D game or watch a movie and is expecting a related drop in the battery level. However background tasks can be more insidious. Since they are not interacting with the user, the user has little or no knowledge of what these apps are doing and how much they are draining the battery.

Don’t miss: Our comprehensive video overview of Android Oreo

To try to limit the damage that background apps can do to the battery level, Android 8.0 Oreo implements background execution limits, a mechanism which limits certain behaviors by apps that are not running in the foreground.

At this point it is worth mentioning that the terms “foreground” and “background” here take on slightly different meanings compared to the more traditional definitions used by the memory management systems in Android.

An app is considered to be in the foreground if it has a visible activity (started or paused), if it has a foreground service, or if another foreground app is connected to the app, either by binding to one of its services or by making use of one of its content providers. This means that a music player is considered a foreground app since it will have a foreground service (with a notification for the status bar, placed under the Ongoing heading) even though the main UI is not in the foreground and isn’t interacting with the user.

When an app is in the foreground, it can create and run both foreground and background services freely. When an app goes into the background, it is given several minutes in which it can still create and use services. At the end of that time slot, the app is considered to be idle and Android will stop the app’s background services.

What all this means is that if an app, say a social media app, wants to check whether there are new posts available, even if it isn’t running in the foreground, then it can no longer just use a background service which checks with the cloud, as this background service will be stopped under the background execution limits mechanism. Instead the app should replace the background service with a scheduled job, which is launched periodically, queries the cloud, and then quits.

Apps should replace the background service with a scheduled job, which is launched periodically and then quits.

Job Scheduler

Android Oreo introduces a number of improvements to the JobScheduler, which are designed to help apps move from using background services to scheduled jobs. The JobScheduler is an API for scheduling various types of jobs that will be executed in your application’s own process.

The biggest change in Android 8.0 to the JobScheduler is the inclusion of a new work queue. When a job is running, it can take pending work off the queue and process it. This functionality handles many of the use cases where previously an app would have used a background service.

Many apps with background services would have used IntentService, a class based on background services that handle asynchronous requests on demand. Now with the Android Support Library 26.0.0, a new JobIntentService class has been introduced, which provides the same functionality as IntentService but uses jobs rather than background services when running on Android Oreo.

Finally, scheduled jobs now support several new constraints including isRequireStorageNotLow(), which ensures that a job does not run if the device’s available storage is low; and isRequireBatteryNotLow(), which stops a job from running if the battery level is low.

By default Background Execution Limits only apply to apps that target Android 8.0, but users can enable these restrictions for any app from the Settings.

Wrap up

The reasoning behind these changes is to stop over zealous apps taking up too many system resources while in the background. What is interesting is that by default Background Execution Limits only apply to apps that target Android 8.0. However, users can enable these restrictions for any app from the Settings, even if the app was built for a version of Android prior to 8.0.

The result of this is that Google is essentially forcing developers to abandon background services and instead use the more “smart” and controlled JobScheduler.
instagram hack app

What you need to know about Sony’s LDAC

Sony’s LDAC Bluetooth codec boasts three times the speed of SBC, while supporting 24-bit 96 kHz Hi-Res music files. Here’s how Sony is doing it.

hack instagram password

We’ve been talking a fair bit about Bluetooth audio lately, mostly because consumers and high-end audio companies are making more noise about it than ever before. Be it wireless headsets, hands-free ear pieces, automotive, or the connected home, there’s a growing number of use cases for good quality Bluetooth audio. Fortunately, a number of companies have us covered with solutions that exceed the so-so performance of out-of-the-box Bluetooth solutions.

Qualcomm’s aptX already has a ton of Android phones covered, but multimedia-giant Sony has its own high-end solution called LDAC. This technology had previously only been available on Sony’s Xperia range of handsets, but with the roll-out of Android 8.0 Oreo the Bluetooth codec will be available as part of the core AOSP code for other OEMS to implement, if they wish.

So here’s everything that you need to know about Sony’s LDAC Bluetooth codec.

Higher quality Bluetooth audio

 

At the most basic level, LDAC supports the transfer of 24-bit, 96 kHz (Hi-Res) audio files over the air via Bluetooth. The closest competing codec is Qualcomm’s aptX HD, which supports 24-bit, 48 kHz audio data.

What’s interesting about LDAC is that it comes with three different types of connection mode – quality priority, normal, and connection priority. Each of these offers a different bitrate, weighing in at 990, 660, and 330 kbps respectively. So, depending on the type of connection available or the option you pick, there are varying levels of quality. It’s clear that the slower bitrates aren’t going to give the full 24-bit, 96 kHz quality that LDAC boasts though, so keep that in mind.

LDAC supports the transfer of 24-bit, 96 kHz (Hi-Res) audio files over the air via Bluetooth, with three quality settings to choose from.

Comparing bitrates is a questionable science, but it does give us a good idea about how much audio data each codec sends per second. High quality standard low-complexity subband codec (SBC) clocks in at a maximum of 328 kbps, Qualcomm’s aptX at 352 kbps, and aptX HD is 576 kbps. On paper then, 990 kbps LDAC transmits a lot more data than any other Bluetooth codec out there. And even the low end connection priority setting competes with SBC and aptX, which will cater for those who stream music from the most popular services.

Jargon Buster:

Sample rate (Hz): the number of points of data per second in an audio file. You need two samples to accurately capture any frequency, so audio is sampled at at least twice the limits of human hearing (approximately 20 kHz). Higher resolution file formats tend to be exported at 96 kHz or greater.

Bit-depth (-bit): the number of bits saved for each audio sample. A higher bit depth records a signal more accurately. CD quality is 16-bits, but high resolution files extend this to 24-bits.

Bit-rate (kbps): usually measured in kbps or mbps. This is the amount of audio data transferred per second over Bluetooth. For uncompressed files, this is calculated by multiplying the sample rate by the bit-depth.

Sony is keen to make it clear that LDAC transmits up to 3x more data than SBC. However, that’s only with the Quality preset, and bit-rates are only part of the picture. The bigger question is how is this data being optimized.

However, it’s impossible to say exactly how good LDAC is based on this data alone. Sony is keeping its LDAC secret sauce closely under wraps, but to properly put these numbers into context we need to know how the technology works on a lower level. So far, we can only say that, at it’s best, LDAC transmits a lot more data than other Bluetooth codecs.

Increasing the transfer rate

Unfortunately, Sony hasn’t published much in the way of in depth materials for how LDAC works. But scouring some older Japanese sources has yielded some details about what Sony is aiming to accomplish with LDAC, at least at its highest bit depth.

There are two major parts to Sony’s LDAC. First is achieving a high enough Bluetooth transfer speed to reach 990 kbps, and the second is squeezing high resolution audio data into this bandwidth with a minimal loss in quality.

LDAC makes use of Bluetooth’s optional Enhanced Data Rate (EDR) technology to boost data speeds outside of the usual A2DP profile limits. But this is hardware dependant.

The first stage is accomplished by using Bluetooth’s in-house Enhanced Data Rate (EDR) option, which was introduced all the way back with Bluetooth 2.0 to increase maximum speeds. EDR speeds are not usually used by A2DP audio profiles, but the spec is rated up to 3 Mbps. Although in reality, 1.4 Mbps is mostly achievable, with 1 Mbps being considered the minimum stable connection. Hence why Sony’s LDAC sits just under this threshold at 990 kbps.

I should point out that EDR is an optional part of even newer Bluetooth 4.x devices, as the focus has been on decreasing power consumption for the most part. So not every chip, and therefore not every phone, will necessarily support Sony’s LDAC at the highest quality setting. Bluetooth 5 supports 2 Mbps low energy speeds out of the box, and is also backward compatible with EDR versions of Bluetooth, but again this higher speed is optional.

LDAC, SBC, and aptX share a common idea?

Now for LDAC’s compression technology, which appears to be an intelligent combination of lossless and lossy techniques to maximise sound quality at 990 kbps. And it’s all to do with varying the bit-depth at different frequencies, which preserves significantly more data than psycho-acoustic compression algorithms, such as those used by MP3.

Those who are familiar with the human auditory system will be aware that hearing sensitivity begins to quickly fall off after 16 kHz, meaning that a lot of the data transferred in a 96 kHz file (48 kHz of audible data per Nyquist Theory) is incredibly difficult, if not impossible to hear. Furthermore, we also know that 24-bits of data is more than can be physically reproduced by the best audio hardware, so these large files are carting around tons of extra data we simply can’t hear.

Sony’s LDAC doesn’t go so far as to just chop out these very high frequencies, but it does reduce their bit-depth at the quantization stage. In other words, there’s more noise present at very high frequencies, but that’s not a problem once we take into account the limitations of human hearing and the fact that we don’t need anywhere near like as much detail at these very high frequencies.

Normal PCM files have a set bit-rate across all frequencies. But files can be compressed by reducing the bit-depth at higher frequencies, with minimal impact on audio quality.

Human hearing is most sensitive around 3 kHz, so reducing the level of detail at higher frequencies is an intelligent way to save on data size. The above basic example removes one bit of accuracy for each 6dB loss in sensitivity, which would be imperceivable.

How does Sony go about doing this? Well this translation from the article mentioned above is quite revealing – “LDAC does not divide the subband (partial band) but goes directly to frequency conversion”. So, LDAC appears to be using a somewhat similar technique to Qualcomm’s aptX and even the standard SBC, where the original PCM audio file is split up into multiple frequency bands each with different bit-depths. Again, the higher frequencies use smaller bit depth and therefore suffer from more noise, so technically this is somewhat lossy. However, this is a worthwhile data saving as it doesn’t affect listening quality nearly as much as culling data using psychoacoustic techniques.

Sub-band coding is used in a variety of codecs, including SBC, MP3, AAC, aptX, and LDAC. Many codecs use this for psychoacoustic masking, but aptX and LDAC only adjust the bit-depth in line with hearing sensitivity.

There are some notable differences between LDAC and aptX though. While aptX has just four sub-bands, LDAC appears to max out at 16, according to the AOSP library’s header file. This has the benefit of adding in extra steps and therefore smoothing out the noise transition between each band. What isn’t clear is whether LDAC is using a differential transmission to save on data size though, like Qualcomm does.

Some quick math suggests that you could fit in an average of just over 5 bits at 96 kHz into a 990 kbps data stream, without any additional compression. Clearly, that’s a long way off sending a full Hi-Res file, but remember that LDAC reserves the bulk of the bits for the audible frequency range.

Jargon Buster:

Bit-depth & noise: As we know that a higher bit-depth allows us to more accurately record audio data, the other side of the coin means that a lower bit-depth reduces accuracy. Put another way, a lack of accuracy introduces more random noise into the signal.

Split-band encoding: While audio data is normal encoded in the time domain, processing data in the frequency domain makes it possible to quickly filter a signal by its frequency. Using a series of overlapping filters, it’s possible to split a signal into multiple parts, process it, and recombine it later.

Huffman encoding: Used in a range of data compression tasks, Huffman encoding shrinks data sizes by assigning the smallest code to the most commonly used data and larger code to uncommon data.

A conceptual diagram of the variable bit allocation method in LDAC compared to lossless audio.

A trawl through the AOSP libldac library also suggests that Sony’s codec is using some form of lossless Huffman coding in conjunction with re-quantization to slim down file sizes. This means that additional lossless compression is used to trim the file down further, in a similar vein to FLAC and even part of the MP3’s encoding pipeline. This is likely also what’s helping to shrink down Sony’s transmission size further.

Now, one of the benefits of this type of encoding is that smaller file sizes can be passed with even less compression. Sony also says that LDAC optimizes its sub-bands dynamically based on the source material, so presumably the codec can identify file types and quality ahead of time to optimize its packet size and bit-depth accordingly. So a 44kHz CD quality track, for example, can be split into the same number of bands but be sent with a larger bit-depth over its smaller frequency range. The LDAC library actually specifies that 44.1 kHz and 88.2 kHz files are sent at 909 kbps max, while 48 and 96 kHz tracks use the full 990 kbps, so it’s clearly content aware.

Based on that and the graphic above, it appears that a 16 bit, 44.1 kHz CD quality file would pass through the codec unaltered, as the available bit-depth more than exceeds the require 16-bits. This is also backed up by Sony’s marketing material claims, which shows that the output of its compression provides “the same as CD quality”.

Sony claims that LDAC can pass 16 bit, 44.1 kHz files without losing any quality (although note it says “same as” CD quality) over a 990 kbps Bluetooth connection, but there is definitely some loss with Hi-Res sized files.

Unlike aptX, LDAC is variable bitrate. So quality will vary based on the Bluetooth connection and hardware, just like SBC often does.

Another difference between Sony and Qualcomm’s technology is that while aptX is a constant bandwidth codec, LDAC is variable and works at a variety of bitrates, depending on the available hardware, connection speed, and connection strength. So as Sony’s bit depth decreases, the amount of compression and noise increases, whereas aptX is set to always work at the same constant bitrate. While Sony’s option is more flexible, it will add some workload to the encoding and decoding stage and makes it a little harder for consumers to know exactly what they’re getting at all times.

LDAC uses the same sub-band techniques at its 300 and 600 kbps settings, however Sony is simply able to change the quantization stage to reduce the bit-depth of its different frequency bands further. The company’s 300 kbps setting will certainly send files at lower than CD quality, but it will be interesting to hear if this compression technique is better than MP3 or AAC. This is because even at low bitrates, there’s no major hacking up of the signal, simply the introduction of extra low level noise.

Sony’s DSEE HX upscaling tech is making its way into wireless audio products, and could be a powerful tool when used in conjunction with LDAC.

There’s also another interesting Sony technology that’s worth mentioning, especially as we’re talking about high frequency content. Sony’s audio products now come with its DSEE HX upscaling technology built in, and it’s even included in some of the company’s wireless headphones and speakers.

Sony’s DSEE HX is a signal processing technology that attempts to restore lossy files, like an MP3 or a Bluetooth data stream, to reproduce high resolution content that’s been lost during compression. There’s some software trickery going on based on data collection from real world audio samples, but obviously it’s impossible to completely accurately reproduce lost data. Still, remember that even though LDAC is lossy it still retains some high frequency data, albeit at lower detail. But using this extra data that isn’t available in more heavily compressed file types should empower Sony’s DSEE HX upscales to achieve even better results than when using an MP3, etc. So it might be something to consider when picking out any LDAC products.

Sony’s engineers claim they can’t detect a difference between Hi-Res audio files and LDAC DSEE HX upsampling. But obviously we’ll have to check that for ourselves.

See also:
Everything you want to know about Qualcomm’s aptX Bluetooth codec

Everything you want to know about Qualcomm’s aptX Bluetooth codec

July 17, 2017

LDAC and Android Oreo

One of the interesting discoveries with the unveiling of Android O was how much input Sony had in helping improve stock Android, along with a number of other OEMs. The company contributed some 250 bug fixes and 30 new features, one of which is its LDAC. Google confirmed LDAC is now part of the Android AOSP base code, which means that it’s free for all OEMs to integrate into their smartphones if they wish.

Third party hardware manufacturers require a LDAC license, and even those looking to use Sony’s AOSP code need to pass certification.

The only detail we’re not sure of if is there’s a licensing cost that OEMs will have to sign up for, as there is with Qualcomm’s aptX which is also supported in Android Oreo’s Bluetooth codec settings. From the support page, we can see that corporate users will need to contact Sony to license the technology, and phone and tablet manufacturers looking to the AOSP code are required to pass a certification process, but any costs involved are hidden.

Now of course, just like Qualcomm’s aptX, you’re going to need a set of LDAC compatible headphones or speakers to connect your handset up to as well. Unfortunately, LDAC equipped pieces of audio gear are a little hard to come by. The technology is currently only found inside Sony’s own range of audio gear, although this does extend to its home cinema range, Walkman products and speakers, as well as the company’s wireless headphones.

See also:
Everything new in Android Oreo: features and changes

Everything new in Android Oreo: features and changes

1 day ago

For Sony, the offer to support LDAC as part of Android Oreo makes a lot of business sense. If more customers become familiar with its codec across a wider range of phones, then they’re more likely to consider buying LDAC compatible audio products. We’ll just have to see how this all plays out once OEMs start rolling out their own versions of Android Oreo.

A word on quality

As always with these audio articles, I like to end by putting all of this into perspective in terms of your music collection and hardware. As always, LDAC is not a cure to instantly boost audio quality, as much of the final result ultimately depends on your source material and the quality of your headphones or speakers.

LDAC isn’t going to make a huge difference when streaming music from so-so quality services such as Spotify or Pandora, and it can’t suddenly make a sub-$99 headset sound like a more expensive piece of kit. As with aptX, it does offer better connection quality than SBC regardless of what you’re listening to. LDAC goes further by catering to a range of listeners with its variable bitrates, ranging from those listening to FLAC and Tidal to those who prefer the convenience of free lossy streaming services.

Android 8.0 update: when will you get it?

The Android 8.0 Oreo update is rolling out – find out when you can expect to see the Android Oreo update on your device!

The Android 8.0 Oreo update will deliver the next major version of Android to our devices, beginning on August 21 for supported Pixel and Nexus devices and taking anywhere from a couple of months to more than half a year to appear on phones by the likes of HTC, Samsung, LG, Sony and Motorola.

How soon your phone will get the update depends on a variety of factors: your phone manufacturer’s update track record, how new (and expensive) your phone is, whether your phone is unlocked or carrier-branded, your region, and so on. But, given past performance, we can draw some fairly accurate predictions of when you can expect to get the Android Oreo update on your phone.

What follows is broken down into Android OEMs, based on how fast they got both Nougat and Marshmallow out, so just jump to the relevant section to see when the first Android 8.0 update should hit that company’s devices. (Note: As OEMs publicly announce Oreo support details, we’ll update this article).

Android Oreo update schedule

Google Pixel/Nexus Android Oreo update

  • March 21: Android O developer preview 1 (alpha)
  • May 17: Android O developer preview 2 (beta) – Android O beta program starts
  • June 8: Android O developer preview 3 (beta) – final APIs and official SDK
  • July 24: Android O developer preview 4 (final beta)
  • August 21: Final Android 8.0 Oreo release

Google eventually confirmed the final build of Android O would roll out on August 21, when it was also announced it would be called Android 8.0 Oreo, as long suspected. The Android Oreo update rolled out first for the Pixel and Pixel XL, as well as the Nexus 6P, Nexus 5X, Nexus Player and Pixel C. System images are available on the Android Developers website and if you need any help flashing the image, follow our straightforward guide to installing Android Oreo manually.

Android 8.0 update: when will I get it?

For all non-Google devices, you’ll have to wait until well after the official launch of Android 8.0 to see Android Oreo on your device – somewhere between three months and a year depending on your handset manufacturer and carrier.

We previously shared details of the fastest OEMs and carriers to update to Android Nougat and we also took a second, mid-rollout look at OEM update performance. Perhaps not too surprisingly, the podium finishes for the first update aren’t always backed up by update performance over time. Updating mid-range and budget devices is never a particularly appealing prospect for device manufacturers or carriers, unfortunately.

As always, we encourage you to do a little homework when planning your next Android purchase, especially if rapid updates are important to you. Some manufacturer and carrier combinations are more responsive than others, and the upcoming Google Pixel 2 will be at the top of the pile for the next two years. With that said, here are our predictions on when your device is likely to get Android 8.0 based on historical performance.


Samsung Android 8.0 update

Samsung isn’t exactly speedy when it comes to rolling out Android updates, and we sadly don’t expect that to change significantly with the Android Oreo update. In our mid-rollout assessment for Nougat, Samsung is near the bottom of the score sheet. Yes, the company has near limitless resources, but it also has the largest product portfolio by far and countless carrier agreements spanning the globe to slow it down.

Flagships come first and the Galaxy S8 and S8 Plus will be on the top of the update list alongside the Galaxy Note 8, officially unveiled on August 23.

Looking at Nougat, Samsung got the first updates out to the Galaxy S7 and S7 Edge in China and the UK 143 days after Google released Android 7.0. The update took a grand total of 180 days to reach US shores, landing first on T-Mobile, followed by AT&T the day after and Sprint two days after that. Verizon hobbled across the finish line a couple of weeks later.

But what about the year before? For the Marshmallow update, Verizon actually got there first, delivering Android 6.0 to the Galaxy Note 5 after 156 days. Carrier performance can fluctuate year to year and device to device, but based on these two efforts, we can expect the first update to Android 8.0 for the Galaxy S8 and S8 Plus to arrive between 5-6 months after it is released by Google – around January or February 2018.

Korean S8 owners will likely get it at least a month earlier than the US, and of course, both Samsung and its carrier partners could either speed things up this year, or slow them down even further. But a 2017 Samsung Android 8.0 update looks unlikely unless Samsung has suddenly decided that updates are, you know, important.

Best case scenario: 5-6 months after Android 8.0 arrives (January/February 2018)


LG Android 8.0 update

LG managed to launch the V20 last year with Android Nougat pre-installed – the first phone to arrive with the latest version of Android out of the box. We might see a similar thing happen this year with the upcoming LG V30, which is due to be unveiled on August 31, just a few days after the Galaxy Note 8.

LG managed to swing this last year largely thanks to its tight relationship with Google on various Nexus partnerships, but we wouldn’t be surprised if this year Samsung hasn’t tried to wrestle that special benefit from its South Korean competition’s hands. Regardless of whether LG manages a repeat of last year’s pre-installed magic trick, LG has a bit of work to do with the rest of its device updates.

With Nougat, LG got the first update out to the LG G5 on Sprint after 91 days, just two weeks after the very first update hit South Korean devices. T-Mobile followed a little over a week later, followed by Verizon immediately afterward. AT&T dropped the ball big-time, taking double the length of time it took Sprint to get Nougat out: an eye-watering 182 days (which, for comparison’s sake is the same amount of time it took for the very first Samsung device to get updated to Nougat).

For the Marshmallow update, LG was similarly speedy, taking less than two months to get it out in South Korea and just 75 days for the US, on the Sprint LG G4. Non-flagship devices have always been LG’s weak point, so being first with an update for one device isn’t exactly helpful if you don’t own the latest and greatest.

Either way, we should see the LG Android 8.0 update roll out for the LG G6 somewhere between two and a half months to three months after Google releases it. As per usual, South Korea will likely get it about two weeks earlier. That puts the first US update around October or November. As mentioned above, the V30 might well arrive with Oreo pre-installed.

Best case scenario: 2.5-3 months after Android 8.0 arrives (October/November 2017)


Sony Android 8.0 update

Sony’s decision to cancel its Concept for Android program is disappointing, but previews aside, Sony is actually getting better at updating its devices to new versions of Android, which is especially noteworthy because there are still a lot of them.

For the Sony Android 8.0 update we’d expect the Xperia XZ Premium to be at the top of the list. There’s a very real possibility that Sony could have a new flagship in time for IFA, just like LG and Samsung, but it’s pretty unlikely it would ship with Android Oreo on board.

The Sony Nougat update first landed on the Xperia X Performance 99 days after Google released it, with the Xperia XZ update coming one day later. What’s perhaps more important though, is that Sony then pushed the Nougat update to even more current devices in the coming weeks, something that can’t be said of all OEMs after they get their first device over the line.

This a vast improvement over the Marshmallow update, which took five months to arrive for the Xperia Z5, Z4 Tablet and Z3 . Sony was admittedly going through a tough period at the time, so lets’ hope the company’s Nougat performance is more indicative of the new Sony approach to updates.

With this in mind, we could see the first Sony Android 8.0 update a little over three months following its official release. That puts it somewhere in the vicinity of November or December. One thing to keep in mind here is that Sony isn’t as weighed down by carrier delays as other manufacturers in the US – unfortunately because none of them seem to want to have anything to do with Sony.

Best case scenario: 3-3.5 months after Android 8.0 arrives (November/December 2017)


Motorola Android 8.0 update

Motorola has also been through a pretty tumultuous time of late, exchanging hands between Google and Lenovo, having its legendary moniker stripped and later reinstated and generally not seeming to know whether its coming or going. Some good things have managed to stay in place though, primarily the company’s ability to get out rapid updates.

Besides Motorola’s relationship with Verizon on the Droid range in the US, Moto phones typically get bought outright, meaning there’s no lengthy carrier delay for a lot of owners. But even with its carrier dependent Droid phones, Motorola still manages to get updates out quickly, a handy leftover from its time under Google’s wing and pared-back interface.

Motorola was the first OEM to get the Nougat update out in the US, delivering it to the Moto Z and Moto Z Force (including the Droid versions) after just 88 days. The international unlocked update rolled out a couple of days later, putting Moto well ahead of the competition.

The Marshmallow update was a similar story, with the Moto X Pure Edition getting it in just two months. Pure Editions are no longer a thing, but Motorola has shown it can get an Android update out within two to three months of Google. Giving the company the benefit of the doubt means the first Motorola Android 8.0 update could land in October, but we’re leaning a little more towards November.

Best case scenario: 2-3 months after Android 8.0 arrives (October/November 2017)


HTC Android 8.0 update

HTC has a pretty good comeback phone on its hands with the U11, even if its massive size and large bezels stick out a little in today’s skinny bezel-less landscape. The company was one of the first to start stripping away core features and moving them into Google Play, where they could be updated independently of a major firmware update.

HTC has proven itself to be one of the more forward-thinking Android manufacturers where updates are concerned, but being adventurous sometimes leads to issues. HTC was one of a few OEMs to temporarily shut down their Nougat update due to issues that only became apparent after the rollout had begun.

Bugs notwithstanding on the Nougat rollout, HTC got it out internationally after just 95 days, with it landing on the T-Mobile HTC 10 after 138 days. T-Mobile was also the first in the US to get Nougat out to the HTC One M9, taking another two and a half months to deliver that update.

By comparison, the Marshmallow update was all over the place (if generally very promising): the HTC One M8 Google Play edition was naturally very quick out the gate, followed a few weeks later by the Developer Edition of the HTC One M9 in December. Unlocked versions of the One M9 and A9 also got updated (to Android 6.0.1 rather than 6.0) in December and most carrier-branded versions in early January.

Times have obviously changed since the good old days of Google Play and Developer Editions, meaning HTC’s Oreo performance is probably more likely to match Nougat than Marshmallow. That gives us a date of around four and a half months for the HTC Android 8.0 update, putting it somewhere around December or January.

Best case scenario: 4-5 months after Android 8.0 arrives (December 2017/January 2018)


Huawei Android 8.0 update

Huawei, like LG, sits a little outside the normal scope of Android updates because the company typically releases a device at the end of the year with the latest version of Android pre-installed. The Huawei Mate 8 had Marshmallow out of the box and the Mate 9 had Nougat on board, so we’d expect the Huawei Mate 10 to do the same.

Huawei also doesn’t have any carrier agreements in the US, selling its phones in the country unlocked. While that means there are no carrier delays imposed on Huawei’s update rollouts, the company doesn’t have the best track record where pushing updates to its US devices are concerned.

The first Nougat update pushed out by Huawei was to the Huawei Mate 8 and P9 in China, coming three and a half months after Google released it. The first US update, as far as I can tell, came to the Huawei P9 Lite in mid-January, five months after Nougat appeared, with the Mate 9 getting a patch in early March followed by the Amazon Alexa update a couple of weeks later.

It’s impossible to judge a timeline for the Huawei Android 8.0 update due to the company’s lack of focus on the US market, its habit of releasing updates for select international regions (but not all), dropping early access betas and promising updates that never arrive. The Huawei Mate 10 should arrive with Oreo on board, but that’s about as accurate a prediction as we can make.

Best case scenario: Your guess is as good as ours
hack instagram app