Saturday, August 18, 2018

How to enable the new, faster Snapchat Alpha [Root]


Snapchat, one of the most widely used social platforms in the world, is preparing to launch a new, faster version of its Android application. In February of last year, the company's executives internally committed to bettering the experience for Android users. In November, the company made its intentions public: Snapchat will be rebuilt from the ground up to "provide a more performant product experience" and "to make it easier to use." At the time, the company did not provide a timeline for when the redesigned Snapchat application would roll out, but it appears that the latest beta releases of the app now have a mostly-functional version of the speedier design. We enabled this redesign to show off what it looks like and how it performs, and now we'll show you how to enable it too.

Snapchat Alpha was first discovered by Jane Manchun Wong (@wongmjane) but was subsequently independently enabled by XDA Recognized Developer Quinny899, Kieron Quinn of Mighty Quinn Apps.

How to Enable Snapchat Alpha


Before we begin, you'll need to be on the latest version of the Snapchat app—either 10.39 or 10.39.1 beta. You can download the app from the Google Play Store, but if the latest version isn't available for you then you can also grab the APK from APKMirror.

Snapchat (Free+, Google Play) →

Download  the latest Snapchat Beta release from APKMirror

Now, follow these step-by-step instructions to get Snapchat Alpha up and running!

  1. Download a root-enabled file explorer like FX File Explorer or MiXplorer. I'm going to be using MiXplorer for this tutorial.
  2. Open MiXplorer and expand the sidebar to the left. Tap "Root."
  3. If this is your first time using MiXplorer, it'll ask you for root access. Grant it.
  4. Go to "data"
  5. Scroll down and enter "data" again.
  6. Find ""
  7. Open "shared_prefs"
  8. Open "dynamicAppConfig.xml"How to enable new, faster Snapchat Alpha
  9. Look for the "appFamily" string and change the "snapchat" value to "mushroom"How to enable new, faster Snapchat Alpha
  10. Save the file and exit.
  11. Long-press on the Snapchat app icon in your launcher and go to its App Info page.
  12. Force close Snapchat.
  13. Connect your phone to your PC and enable USB Debugging in Developer Options if you haven't already.
  14. Download and install the latest ADB binaries on your PC according to this guide if you haven't already.
  15. Open up a command prompt on your computer in the same directory where you saved the ADB binaries and enter the following command to enter ADB shell:
    Windows Command Prompt:adb shell
    Windows PowerShell:.\adb shell
    macOS/Linux Terminal:./adb shell
  16. Now, enter the following 4 commands one-by-one (after entering 'su' it'll ask you to grant root access):
      su  pm enable  pm enable  pm disable to enable new, faster Snapchat Alpha  
  17. Open up the Snapchat app and you should be greeted by the new, faster Snapchat Alpha redesign!

Here's a video tutorial by XDA Recognized Developer Quinny899 to help you out in case you're stuck on any part of this guide.

If anything changes during development of this new alpha user interface, we'll let you all know. Until then, stay tuned to the XDA Portal for more tutorials like this!

from xda-developers

[Hands on] Snapchat Alpha is a faster, cleaner version of Snapchat


Last November, Snap announced that Snapchat for Android was going to be rebuilt with a focus on performance and ease of use. It has been close to a year since they announced this redesign and we have yet to hear anything about it, until now. We have managed to enable the new design to showcase what it looks like, and we also have a video comparing the old and new versions to show how much better the new Snapchat Alpha performs.

Snapchat Alpha was first discovered by Jane Manchun Wong (@wongmjane) but was subsequently independently enabled by XDA Recognized Developer Quinny899Kieron Quinn of Mighty Quinn Apps.

Snapchat Alpha – A Cleaner Snapchat

While playing around in the app, the first thing you'll immediately notice is how much faster it is. The screenshots below won't show how much smoother the app is, but the video at the end of the article will definitely show how much better it performs. As for the design, the settings menu is more simple, and the stories menu now looks very similar to the Instagram Stories menu. At first glance, the friend's list looks almost exactly the same, but at the bottom, the navigation bar is black instead of transparent and the icons are a bit more noticeable. This isn't a big update, but it does make the app feel a bit cleaner.

The new profile page removes Snapcodes, though this will probably be added back soon, and removes the trophies and share menu. It has an all-around cleaner look, similar to what Google is trying to do with the newest Material Theme guidelines without following the same style. In the Stories UI, the only change I noticed is when you go check to the stats of your post, it shows in an Instagram Stories-style interface with a preview and a search bar. In the messages UI, the bottom bar has been redesigned by removing the calling and video calling buttons but that may be added back by the time this new design is officially completed. In addition, the new messages UI also moves the icons to the side and puts the bar in the middle.

I'm a fan of what Snap is doing with this new Snapchat Alpha update. It is noticeably faster than it was before, which is already enough to justify the new update. But it also has some nice user interface updates to make the app easier to use. These first set of screenshots are just a few things that I noticed when playing around with the app. There could be more that I am missing—if I am missing anything, let me know in the comments below.

Snapchat Alpha – A Faster Snapchat

And here's a video showing off the old Snapchat versus the new Snapchat Alpha. You can clearly see that the new version is faster.

How to enable Snapchat Alpha

If you are interested in enabling the new Snapchat Alpha redesign, you can learn how to do so in this guide.

from xda-developers

Essential Phone’s notch settings may return in future Android Pie update

Essential Phone

Following the release of Android Pie for the Essential Phone, there was one specific, highly used setting that was missing: notch settings. The Essential Phone's notch may have been its most controversial design aspect, but it was possible to customize how each app uses the status bar/notch area. The notch settings were present in Android Oreo but weren't brought back with the official Android Pie release. Even though Android Pie officially brings support for notches, it's up to developers to update their apps to take advantage of this space—which means most users would have to wait for their favorite apps to support the notch. According to a representative of Essential posting on Reddit's monthly Ask Me Anything, the built-in notch settings may be brought back in a future update.

We have discussed this internally and now that P has launched, it is very apparent from our community that you guys want this back in. It will take a bit of work since it is not a 1:1 code transfer from 8.1 to 9.0 given google changed the notch logic so a portion of the code will have to be re-written. But for time frame on implementation it will likely not be in the next security release given it will all need to be re-tested for stability. Thanks for pushing though…. We literally quote these comments when in roadmap planning meetings when we discuss notch settings.. – Marcus

The company has done a great job at keeping device owners happy since the Essential Phone's release. With new modifications, consistent software updates and timely beta releases, they've done a great job at dispelling the notion that the company is in dire straits. Although, it doesn't seem like there will be an Essential Phone 2 unless the company finds more success.

Essential has run their monthly AMA on Reddit for a while now, and we've gotten to learn more about the internal workings of the company as a result. We already know that they intend to bring ARCore support in a future update and now we know about their plans for the notch as well. Not only that, but their response about the notch settings shows that they are adding it back purely based on community feedback. The Essential Phone has been a very well supported phone so far, and we're hopeful that despite earlier reports that we may see a successor.

from xda-developers

Friday, August 17, 2018

Xiaomi Mi 8 reportedly launching soon in India, priced under Rs. 30,000

MIUI 9.5 for the Xiaomi Mi 8

Xiaomi is one of the largest phone manufacturers in the world and is even bigger in India. As a result, the company will be launching their new brand, Poco, first in the region with the Pocophone F1. It's basically a slightly different Xiaomi Mi 8, which may explain why that particular device didn't launch in India. Surprisingly, according to a report from 91Mobiles, we may actually be seeing it launch in India in the next few weeks – possibly right after the Pocophone F1 as well. Three separate phone sellers confirmed this information to 91Mobiles.

The Xiaomi Mi 8 is one of the company's latest flagships and features a number of iterative upgrades over its predecessors. The Qualcomm Snapdragon 845 system-on-chip is present alongside 6GB or 8GB of RAM. A 3,400mAh battery supporting Quick Charge 4.0+ is present to help charge your phone faster in order to power the 6.21-inch panel. It's a pretty beefy phone all things considered and has a few other tricks up its sleeve as well. The device coming to India will directly pit it against other flagships such as the OnePlus 6.

And how much will the Xiaomi Mi 8 cost in India, anyway? Phone sellers are putting it at under Rs 30,000 (~$428), which would possibly have it directly competing against the Xiaomi Pocophone F1. It's unknown which variant will be launched in the region, as the company only recently released an 8GB RAM/128GB storage model.

Specifications Xiaomi Mi 8
Dimensions and weight 154.9 x 74.8 x 7.6 mm, 175g
Software MIUI 9.5 on top of Android 8.1 Oreo
SoC Octa-core Qualcomm Snapdragon 845 (4x 2.8GHz Kryo 385 Gold + 4x 1.8GHz Kryo 385 Silver cores); Adreno 630 GPU
RAM and storage 6GB of RAM with 64GB/128GB/256GB of storage / 8GB of RAM with 128GB of storage
Battery 3,400mAh, Quick Charge 4.0+ (Quick Charge 3 adapter bundled in the box)
Display 6.21-inch Full HD+ (2248×1080) AMOLED, 600 nits brightness, HDR10 support, DCI-P3 gamut
Connectivity Wi-Fi 802.11ac, Bluetooth 5.0
Ports USB Type-C port, dual nano SIM slots
Bands GSM: 850/900/1800/1900MHz
WCDMA: 850/900/1700/1900/2100MHz
FDD-LTE: Bands 1/2/3/4/5/7/8/12/17/20
TDD-LTE: Bands 34/38/39/40/41
Rear camera 12MP primary camera with 1.4μm pixels, f/1.8 aperture, Dual Pixel autofocus, 4-axis OIS
12MP telephoto camera with f/2.4 aperture, 2x optical zoom
Video recording up to 4K, Slow motion at 1080p@240fps
Front-facing camera 20MP with f/1.8 aperture, uses pixel binning to simulate 1.8μm pixels

Source: 91Mobiles

from xda-developers

Vivo Y83 Pro reportedly launching in India with 6.22″ notched display

vivo y83 pro android oreo

The Vivo Y83 Pro will soon be launching in India with a 6.22-inch notched display, according to a report from 91Mobiles. It will be released as a successor to the Vivo Y81 that launched in the region earlier this year. We don't know a lot about its exact specifications such as the SoC, but we do know that it will likely be a MediaTek SoC of some kind.

Other notable features include the 6.22-inch notched FullView 2.0 display. The notch houses all of the device's major sensors, including the ambient light sensor, proximity sensor, earpiece, and 8MP selfie camera. The back of the device will feature a dual camera setup comprised of a 13MP shooter and a 2MP secondary shooter. On top of that, the Vivo Y83 Pro will come with 4GB of RAM and 64GB of storage expandable via a microSD card. Software-wise, it'll run the company's latest Funtouch OS 4.0 based on Android 8.1 Oreo. A 3,260 mAh battery is present as well, though there's no mention of any kind of fast charging standard present. According to a source close to 91Mobiles, it will also be about 7.7mm thick. That puts it at about an average thickness of smartphones being released today.

But when can we expect to see the Vivo Y83 Pro? According to the report, a release is imminent and expected within the next few weeks in India. No exact pricing is confirmed, but it will sell for around Rs 16,000 (~$228). We don't know where else it will be available either or if it will be released outside of India. The Vivo Y83 came out in May this year and appears to have been somewhat successful. We'll be sure to keep an eye on this device to see if it has anything else to bring to the table, or whether it's simply just another budget phone.

Source: 91Mobiles

from xda-developers

Pixel Experience based on Android 9 Pie released for Xiaomi Redmi Note 5 Pro

Xiaomi Redmi Note 5 Pro Android Oreo update

The codebase of Android 9 Pie has been released to the public and this has resulted in a lot of devices receiving new and updated custom ROMs based on the new update. Yesterday, we saw a slew of ROMs based on Android 9 Pie released for some older OnePlus smartphones and one was released for the Xiaomi Redmi Note 5 Pro as well. The Redmi Note 5 Pro has been an incredibly popular smartphone since its release so it makes sense that it receiving an updated version of the Pixel Experience custom ROM has garnered so much attention.

This particular build has been brought to us by XDA Senior Member jhenrique09, who has done a lot of work for the community. It is said to work on Xiaomi's smartphones with the codename whyred, which includes the Xiaomi Redmi Note 5 and the Redmi Note 5 Pro. As this is an early release, there are some bugs to be expected. Here is a list of what the developer says works and the current known issues.

Whats working:

  • Wifi
  • RIL
  • Mobile data
  • GPS
  • Camera
  • Flashlight
  • Camcorder
  • Bluetooth
  • FMRadio
  • Fingerprint reader
  • IR
  • Lights
  • Sound / vibration
  • Facelock

Known issues:

  • Hardware encryption
  • Miracast/wifi display

The developer also says you don't need to flash a Gapps package as they are already included in this build.

Check out this Android 9 Pie custom ROM in our Redmi Note 5 Pro forum

from xda-developers

Moto Camera 6.2 brings Google Lens/YouTube Live to many Motorola phones

Motorola released an update to their Moto Camera application just a couple months ago that redesigned the user interface and even added in Google Photos integration. This update also came with Google Lens, YouTube Live, and some changes to the user experience (such as sliding a single finger up or down to zoom in and out). This release was said to be for Motorola's 2018 smartphones, but the APK has been extracted and has shown to work on older Motorola smartphones as well.

The APK was uploaded to the Moto Z themes, apps and mods forum by XDA Senior Member hudfer. The title of the thread indicates that it works on 2016 Motorola smartphones including the Moto Z, Moto Z Play, Moto Z Force, and the Moto Z2 Play. But it should be noted that someone in the XDA Telegram chat group tried it on their Motorola Moto G3 and told us that it worked on their device as well.

Download the updated Moto Camera APK in our Moto Z forums

from xda-developers

Xiaomi Mi 8 SE forums are now open

Xiaomi Mi 8 SE

Releasing variations of smartphones to the market has become quite the popular OEM technique these days. This comes in different forms with some re-releasing a phone in another country while giving it a different name. Xiaomi, in particular, originally had the Xiaomi Redmi 5 Plus and then ended up re-releasing under the name  Xiaomi Redmi Note 5 at a later point in time. Xiaomi has also made changes to currently available devices and then ended up selling a variant of said device under a different name. We saw this with the original release of the Xiaomi Mi Mix 2, which then received a variant model called the Xiaomi Mi Mix 2s.

But many OEMs release two variants of the same device right when they release them to be public. This is what happened with the Xiaomi Mi 8 and the Xiaomi Mi 8 SE. Both were released in June of this year with the SE variant being the more affordable option with slightly slower hardware and different camera sensors. We have previously created forums here on XDA for the Xiaomi Mi 8 but now Mi 8 SE owners have their own dedicated forum as well.

Join the discussion with us in the Xiaomi Mi 8 SE forum

from xda-developers

Does Android’s volume dialog take 20 seconds to dismiss? Here’s why that happens.

Android Volume Dialog

Have you noticed that the volume dialog that appears when you press the volume buttons takes a bit too long to disappear on its own? When you first got your Android phone, the volume dialog would automatically dismiss after a few seconds without your intervention. Then, sometime in the past few days, weeks, or months, it would take a long time to go away unless you tapped on your screen. If you're experiencing this problem and it infuriates you, you're not alone.

In this article, we're going to explain what's going on and why it happens so you can either fix the problem yourself or send this article to a developer so they can get it fixed. Let's first describe exactly what the problem is so it's clear we're referring to the same problem you're facing.

The Problem

You press the volume button on your Android smartphone or tablet to change the volume, but the volume dialog that appears takes a long time to go away on its own unless you tap on the screen to make it disappear. How long does the volume dialog stay up on its own? Exactly 20 seconds.

Credits: /u/ConeCandy

A popular thread over on Reddit's /r/GooglePixel subreddit had many users chiming in that they were facing this problem. However, not everyone was having this problem. Some users stated that their volume dialogs remained on screen for only 3 seconds, which is the normal behavior. So what was causing this issue? For most users in that thread, it turns out the reason was an app called Signal Spy – though some users in that thread said that other apps were causing this behavior too.

Signal Spy - Monitor Signal Strength & Data Usage (Free+, Google Play) →

Signal Spy is an app that's popular among subscribers to Google's Project Fi service. Project Fi users love the app because it supports analyzing your current network connectivity and supports automatic switching between Sprint and T-Mobile's towers. The best part? It doesn't need root access to switch between the networks. Signal Spy uses an Accessibility Service (a service that uses Android's Accessibility APIs which are normally used for assisting users with disabilities but are also regularly used in hundreds of apps not targeted towards users with disabilities) to automatically switch between carriers by inputting dialer code shortcuts.

Signal Spy's ability to automatically switch between carriers on Project Fi is incredibly useful, but it's also the reason Android's volume dialog issue is happening. The one commonality between Signal Spy and the other apps like LastPass, Fingerprint Gestures, Zoho Vault, Amazon Assistant, and other apps which cause this problem to occur is that they employ an Accessibility Service. Going to Settings –> Accessibility and turning off each Accessibility Service one-by-one until the volume dialog issue is fixed is one way to solve this problem. Why, then, do only some apps' Accessibility Services cause this to happen? Tasker, for instance, does not face this issue and neither does our very own Navigation Gestures app. You and many others on the Google Issue Tracker may think it's a bug, but it's actually not – it's entirely by design.

The Explanation

As we discovered during development of the Navigation Gestures app, the problem arises when an Accessibility Service has the accessibilityFeedbackType set to anything other than FEEDBACK_GENERIC. When we set our Accessibility Service to use FEEDBACK_HAPTIC, the volume dialog would stay on-screen for 20 seconds. When we set it to FEEDBACK_GENERIC, the volume dialog stays on-screen for 3 seconds.

The reason this occurs is because of two methods in the volume dialog implementation in AOSP. The first method called computeFeedbackEnabled checks to see if there are any enabled Accessibility Services that are "non-generic." If true, then the boolean mFeedbackEnabled is set to true. In the second method, computeTimeoutH, is mFeedbackEnabled returns true then the volume dialog's timeout is set to 20 seconds, otherwise it is set to 3 seconds.

Android Volume Dialog

These methods were added in the Android 6.0 Marshmallow release and thus this volume dialog issue affects all Android releases since Android Marshmallow including Android Nougat, Android Oreo, and Android Pie. We're not entirely sure why these methods were added as the commit descriptions weren't clear. Regardless, it's clear that this issue is not a bug but is rather entirely by design. Unfortunately, that means there's no "fix" for the issue outside of either persuading Google to alter this decision or convince app developers to not use non-generic feedback types in their Accessibility Services.

The developers of Signal Spy have already confirmed that they have fixed the issue in their next beta release, so if you experience the issue and want to see if fixed, you should point app developers towards this article so they're aware of the problem (as many are not aware.) If a future version of Android changes this behavior, we'll let you all know. At least you're now aware of this issue and what causes it, so you figure out which apps are causing this issue for you.

from xda-developers

Google’s updated Chromecast with Bluetooth also has better 5GHz Wi-Fi

Google Chromecast

The Chromecast has undoubtedly been Google's biggest hardware success. For $35-70 you get a cute little dongle that plugs into the back of your TV and turns it into a Smart TV. The only remote you need is a smartphone. It's a simple concept executed very well, and now almost every home has one. A few months ago we wrote about the upcoming Chromecast with Bluetooth, and now we know more details.

Back in May, we spotted a request that Google filed with the FCC to certify a new version of the 2nd-gen Chromecast. It has the same basic hardware as the original, but with an added Bluetooth chip. The existing 2nd-gen Chromecast supports Bluetooth 2.4GHz Low Energy, but this would be for standard Bluetooth 2.4GHz. It's possible that this would be for connecting peripherals like keyboards and gaming controllers.

The new information is also from an FCC filing. Google appears to be adding tweaking the antenna to add stronger Wi-Fi for 5GHz connections. The Chromecast already supports 5GHz Wi-Fi, but this would increase the antenna gain and hopefully make for stronger connections. If you find your device disconnecting from Wi-Fi frequently, this could be a big improvement.

Google's big hardware event is tentatively scheduled for October 4th. We may see this upgraded streaming dongle along with the Pixel 3 XL, Pixel 3, and Pixel Watch. We're in for an exciting Fall.

Source: Variety

from xda-developers

Qualcomm Snapdragon 855 could launch with a dedicated NPU

Snapdragon 845

The last time we heard news on the upcoming Qualcomm Snapdragon 855 was back in March, when Roland Quandt from WinFuture found that the SoC would be branded the Snapdragon 855 Fusion Platform and would come with the SDX50 5G modem. Previous reports have stated that TSMC would be manufacturing the SoC on its 7nm process. Now, Mr. Quandt is back with a series of leaks about the Snapdragon 855, which may even end up being called a different name. Let us go through them one-by-one:

A dedicated Neural Processing Unit (NPU)

Firstly, the Snapdragon 855 will probably come into the market as the Snapdragon 8150 (more on this below). It will have a dedicated Neural Processing Unit (NPU). This is said to be similar to the NPU that is included in Huawei's HiSilicon Kirin 970, which was announced at IFA last year.

The Kirin 970's NPU has shown itself to be significantly faster than the Qualcomm Snapdragon 835 with its Hexagon DSP for performing AI operations. In the real world, its potential hasn't been used to its full extent, apart from features such as accelerated offline translation, AI scene detection in the camera app, and more. WinFuture states that Qualcomm will use a NPU for the first time in one of its chips.

The LinkedIn profiles of Qualcomm employees show that the employees have continued to fine-tune the hardware design of Qualcomm's upcoming flagship chip. The employees' statements demonstrate that this is a separate part of the system-on-chip. According to the statements, the employees have worked on routing the data streams between the CPU, NPU, and main memory.

WinFuture states that the Neural Processing Unit should help to relieve the CPU and other parts of the SoC when processing AI data. The analysis of image information or voice queries that is currently done by the CPU or the DSP will be shifted to the NPU for better performance. The exact range of functions implemented on this basis is undetermined, but it's likely that it will be in the usual range of other neural processing units.

Snapdragon 855 automotive version

The second part of today's leak is that Qualcomm apparently wants to offer the Snapdragon 855/8150 for the first time in years in a special variant for years. WinFuture found references to a "SDM855AU," which points to use in the automotive field. The production will be at 7nm. It's the first time that Qualcomm will rel-launch a dedicated SoC for automaker integration after the launch of the Snapdragon 820 Automotive. WinFuture notes that this is a logical step considering the importance of AI and upcoming 5G technologies.

Qualcomm Snapdragon 855 to be named the Qualcomm Snapdragon 8150

Qualcomm will unveil the Snapdragon 855 and the Snapdragon 1000 in December as part of its annual Tech Summit. The Snapdragon 855 will be intended for smartphones, while the Snapdragon 1000 will be intended for Windows laptops and tablets. However, according to WinFuture, both platforms will actually come to market under different names.

The Snapdragon 855 ("Hana") is being developed internally under the name SDM855, but its name has changed since several months according to third-party documents seen by WinFuture. The chip is now known as the SDM8150–meaning that it will come to market as the Qualcomm Snapdragon 8150—but it still has the same "Hana" code-name. Qualcomm is apparently switching to a new naming scheme. A possible reason for this may be to make it easier to distinguish smartphone SoCS from those that are intended for laptops and other Windows 10 and Chrome OS PC systems.

According to WinFuture, the evidence for this naming change can be found in import/export databases as well as on the LinkedIn profiles of some Qualcomm employees. In the latter case, the Snapdragon 855 appears under its new name in direct succession to the current Snapdragon 845 (SDM845) chip.

It is a 12.4×12.4 mm SoC, and it probably comes without an integrated 5G modem. Instead, it will have the integrated Snapdragon X24 modem that supports Cat.20 LTE in order to reach 2Gbps down link speeds. The 5G-enabled Snapdragon X50 modem will probably be installed separately on 5G devices.

Similarly, the change in naming also affects the ARM-based laptop processor that was being developed as the SDM1000 "Poipu." This will be 20×15 mm significantly larger than smartphone SoCs, which indicates a higher core count. The overall package of the SoC will work with a maximum TDP of 12W.

The Snapdragon 1000 is listed in recent documents as the "SCX8180" while having the same code-name and retaining the same components. Qualcomm's test platforms continue to have up to 16GB of RAM and 256GB of UFS 2.1 storage on board, and Asus has been working with Qualcomm on these platforms.

The Snapdragon SDM8150 for smartphones and the Qualcomm SCX8180 for PCs running Windows 10 on ARM will both be manufactured by TSMC at its 7nm process. This is confirmed by several LinkedIn profiles of Qualcomm employees.

WinFuture notes that the final name of the new SoCs may not be determined yet, as these names may still be internal designations. The publication speculates that the "SM" in SM8150 stands for Snapdragon Mobile, while the SCX in SCX8180 could stand for Snapdragon Computing.

Qualcomm is also planning to implement the new naming scheme for its lower-tier processors. WinFuture found several mentions of chips with internal model numbers SM7150 and SM750, which will used by OPPO (among other manufacturers). OPPO will also be making a Snapdragon 855/Snapdragon 8150 device. It's not unknown whether the SM7150 and SM7250 are re-brands of existing SoCs such as the Snapdragon 670 and the Snapdragon 710, but according to WinFuture, it's quite likely.

So there we have it: a fairly massive leak on Qualcomm's upcoming flagship chipset. It should be noted that none of this is officially confirmed information so it's always possible that any of the leaks could turn out wrong, but with Mr. Quandt's track record on leaks, we have no reason to doubt that they are legit. We expect to learn more about Qualcomm's new chips in the coming months.

Source 1: WinFuture

Source 2: WinFuture

from xda-developers

Android Pie ported to the Honor View 10, Huawei Mate 10 Pro, and more

Android 9 Pie for the Honor View 10, Huawei Mate 10 Pro

Android Pie is the hottest topic in the Android community right now. After releasing on the Google Pixel and Pixel 2, Essential PH-1, independent developers on our forums have been hard at work porting the latest Android release from AOSP to their devices. We've already seen the Xiaomi Redmi Note 4, Mi 3, Mi 4, Redmi 4X, ZenFone Max Pro M1, and the OnePlus 2/3/3T/X receive unofficial ports of Android 9 Pie, and now the Honor View 10 and Huawei Mate 10 Pro are joining the short list of devices with ported Android 9 releases.

Honor View 10 Android Pie Honor View 10 Android Pie

This is possible thanks to the efforts of XDA Forum Moderator/Recognized Developer flex1911 and XDA Recognized Developer LuK1337. The developers ported the latest release of Android from source and managed to boot it up barely a week after the public release of Android Pie. We should note that the developers only officially support the Honor View 10 with this build of AOSP, but other Project Treble-enabled Huawei and Honor devices can boot the same build of AOSP too. Some devices needed a patch to the surfaceflinger binary and libsurfaceflinger shared object library, while others worked just as well as the View 10 without any additional patches. (The developer's latest release implements this patch so you don't need to manually overwrite the files like I had to.) Since this is an early build, there are going to be some bugs. Here's the current list of bugs:

What doesn't work:

  • MTP USB doesn't work on BKL-L04 (U.S. version)
  • The camcorder is buggy on BKL-L09 (and other variants that use Android 8.0 Oreo vendor image)
  • Wi-Fi Hotspot doesn't work
  • Known issues from the LineageOS 15.1 release

Before we show you the list of compatible devices and link the thread, let's address the obvious: You will need an unlocked bootloader to install this ROM. This may seem obvious to many, but we have to address this since it's no longer possible for any user to generate new bootloader unlock codes. If your bootloader isn't already unlocked, you can't unlock your bootloader now to install this, or any future, custom ROM. The decision by Huawei to close down the bootloader unlock form saddens us because, without an unlocked bootloader, it isn't possible to install early releases of the next Android release. It could take months for any of these devices to receive an official Android Pie update, and some of them might not receive the update at all.

Install unofficial Android 9 Pie for the Honor View 10, Huawei Mate 10 Pro, and more

Simply follow the instructions in the thread linked below to install this release of Android 9 Pie on your device. Here's the current compatibility list, as provided by the developers:

Download Android 9 Pie ported to the Honor View 10 and Huawei Mate 10 Pro

Tips and tricks for Huawei/Honor users with unlocked bootloaders

Since the number of new Huawei/Honor users with unlocked bootloaders will eventually dwindle, there aren't going to be very many new guides for Huawei/Honor devices being made. For those of you who are new to modding Huawei/Honor devices and grabbed a bootloader unlock code at the last-minute just so you could install custom ROMs like these, here's a few important things for you to learn about your device.

Learn your button combinations

  • Hold volume down and the power button when booting and connected via USB to PC/power and you will boot into the bootloader mode.
  • Hold volume up and the power button when booting and disconnected from USB and you will boot into the phone's installed recovery (stock or TWRP).
  • Hold volume up and the power button when booting and connected via USB to PC/power and you will boot into Huawei's eRecovery* mode.

*eRecovery is a special recovery on Huawei and Honor devices that lets you fully factory restore your device over Wi-Fi. eRecovery is pretty unreliable for users outside of China, so unless you are using a special DNS/proxy service like, the Wi-Fi restore method will probably be useless for you. Still, eRecovery is one of your absolute last resorts to unbrick your device, so you should NEVER modify any eRecovery partition.

Learn your partitions

Interested in installing TWRP or rooting your phone with Magisk? That's cool, but save yourself some headaches by learning what partitions TWRP/Magisk modifies on Huawei/Honor devices.

  • TWRP is installed to the recovery_ramdisk partition. (No Huawei/Honor devices support A/B partitions just yet, so there's still a dedicated recovery partition here.)
  • Magisk is installed to the ramdisk partition. (Unlike most other devices where the ramdisk is packed in the boot partition, Huawei/Honor devices split the boot partition into dedicated ramdisk and kernel partitions.)

Get a backup of stock partitions

If you install TWRP, you can make a backup of any partition you're going to modify like system, ramdisk, and vendor. After installing TWRP, you should backup oeminfo. This partition includes important data like your IMEI and device branding. You won't (or shouldn't) ever touch this partition if you flash custom ROMs, but if you ever plan on re-branding your phone, you'll definitely want a copy of this partition just to be safe.

Lastly, if you want to be extra safe, download the latest version of your stock firmware ("full OTA") from Firmware Finder and extract the partitions from the file using this guide. Keep them around for when you can only access the bootloader and need to flash images via fastboot. (Since installing TWRP requires modifying the recovery_ramdisk partition, this is actually the only way to get a backup of that partition too.) You'll want to be intimately familiar with flashing images via fastboot anyways if you plan on flashing a Project Treble Generic System Image (GSI).

Enjoy custom ROMs on your Honor or Huawei device while they last! I learned all the above via trial-and-error while experimenting with GSIs on the Huawei Mate 10 Pro. I hope this knowledge helps you save some time by not having to beg the XDA forums or Discord/Telegram chats for help if something goes wrong.

from xda-developers

Motorola may launch a Google Home Mini/Amazon Echo Dot competitor

Moto Smart Speaker

The virtual assistant devices have become quite popular for those who want more out of their connected devices. These virtual assistants, such as Siri and Google Assistant, originated on iOS and Android respectively. But Amazon created an entire hardware market for these virtual assistant services with the Amazon Echo. The Echo was quite a successful device for the company and it was one that spawned Google's competition to create devices like these of their own. Google has the Google Home and Google Home Mini, Samsung has the Bixby Speaker, and even Apple has the HomePod. However, a new leak published today claims that Motorola wants in on this market as well and could end up releasing a competitor to the Google Home Mini and Amazon Echo Dot.

Some would say that the Motorola brand has been floundering since they were brought under the Lenovo umbrella. There's no doubt that the entire company has gone through a restructuring strategy since that acquisition was made official. Lenovo themselves have already released one of these virtual assistant products that they ended up calling the Lenovo Smart Display. It looks more like a tablet embedded into an enclosure that makes it easy to place on your nightstand, kitchen table, etc.

Not everyone is a fan of these "smart display" products though, which makes sense that they have possibly had Motorola working on a regular smart speaker. The rumor comes to us from AndroidPure, yet details of the name of the device have yet to be revealed. It's currently being referred to as the Motorola Smart AI assistant speaker and some leaked press images give us a look at what the company has possibly been working on. It's also unclear what software will be running on the speaker.

Lenovo's Smart Display had Alexa as its AI companion and Motorola ended up releasing a Moto Mod that also included Alexa as well. The leak did give us some information about the hardware inside the smart speaker, which includes an ARM 53 Cortex CPU, Bluetooth, WiFi connectivity, a weight of 280 grams, and a diameter of 90mm. The marketing material even talks about integration with other products from companies including LifeSmart, BroadLink, Tuya, Haier, Orvibo, and others.

Moto Smart Speaker
Source: AndroidPure

from xda-developers

China’s first homegrown web browser is allegedly repackaged Google Chrome

google chrome quick reply

Google Chrome is now the world's most popular web browser, with some websites seeing 80% of their visitors using the software. Chrome is based on the open source project that Google calls Chromium, which means anyone is able to build a web browser from its codebase and release it to the world. Interestingly enough, that's exactly what AllMobilize's (now known as Redcore Times Technology Ltd.) co-founder and chief operating officer, Gao Jing, did. It's been renamed to Redcore Browser and is being marketed as China's first homegrown web browser.

The company, Redcore Times Technology, recently raised $36 million from investors, including IDG Capital and Morningside Ventures. This investment was based on the idea that Redcore Times Technology would build a "web browser with a secure kernel," which would then hold the title as "China's first self-researched and self-developed web browser." They ended up naming this web browser after their company, calling it the Redcore Browser and released it to China's citizens.

This release received a lot of press because of those claims that it would be China's first homegrown web browser. There are a number of popular web browsers in China already, but they have all been based on a pre-existing project. So when Chinese programmers started digging into the code of the Redcore browser, claims of it simply being a Chrome shell browser started to circulate the news outlets. Getting $36 million just to create a Chrome shell browser is a bit deceptive, but Redcore Times Technology's CEO disagrees.

In a response to Chinese news website BJNews, the co-founder and COO Gao Jing admitted that the Redcore browser does "include Chrome inside," just as the critics have said. However, since it is based on the open source project Chromium, they haven't stolen any intellectual property. He goes on to defend the release of Redcore by saying they have simply "innovated by standing on the shoulders of giants." Gao claims they never misled anyone by using the banner of "domestic innovation."

Still, the company's Weibo account has been flooded by enthusiasts mocking them as they did say the Redcore browser would be "independently developed."

Via: China Money Network Via: Sixth Tone

from xda-developers

The OnePlus 6T may launch on T-Mobile in October

t-mobile logo

OnePlus phones are popular among the Android enthusiast community, but most "normal" people don't know much about the company. That has slowly changed over the years, but OnePlus remains to be fairly unknown in the mass market. According to a new report, that is about to change as the OnePlus 6T will be launching on T-Mobile this Fall.

OnePlus devices have been compatible with US carriers from the start, but there has never been an official US carrier launch. CNET claims T-Mobile will be the exclusive US carrier partner for the OnePlus 6T when it launches in October. There will be a special version of the phone that will be optimized for T-Mobile's network, including the new 600 MHz band of spectrum. Of course, there will also be the typical unlocked model that works with AT&T and other networks across the globe. Pricing is tentatively set for $550.

OnePlus is currently going through the process of getting "technical approval" at the carrier, which could potentially delay the launch. Android enthusiasts love OnePlus devices for a lot of reasons. There's a lot to love for the average consumer as well. Getting the OnePlus 6T on store shelves will put it in front of many more eyeballs. That's something that OnePlus has never been able to do, despite their creative marketing stunts.

We don't know much about the actual phone at this time. The "T" variant is usually a minor upgrade. Many people have been speculating that the upcoming Oppo R17 is a peek at what the OnePlus 6T will look like. If that happens to be true, T-Mobile customers will be seeing a very attractive device. There is still a lot to learn about this news, but this is a very exciting development.

Source: CNET

from xda-developers

[Update: Pichai responds] Google plans to relaunch Search in China with censored results

Google Search China

Update 8/17: Google CEO Sundar Pichai and Alphabet president Sergey Brin have responded to these claims. Statements below.

Google and China haven't always been on the best of terms. China is very protective of the information they let into their country and will do whatever they can to block what they don't want in. On the other hand, Google feels that information should be free and that everyone should have access to as much as we can collect. YouTube, Twitter, and Facebook were blocked in China as early as 2009, and Google Search was actually allowed to maintain a highly censored version in China between 2006 and 2010. After pressure from the House International Relations Committee, Google removed their web search feature from the country, but leaked documents indicate Google will be bringing their web search back in the near future.

The removal of Google Search from China is rather interesting. Besides the fact that Google wasn't a fan of providing a censored version of its service, it was pressure from the United States that was the last straw. From 2006 to around 2010 there were a number of congressional hearings for American companies who were providing services within China. It was the House International Relations Committee who ended up calling Google a "functionary of the Chinese government" and accused it of "abhorrent actions" for participating in censorship.

Google knows how important the country of China is for their bottom line, so they have slowly been working their way back. They recently increased their manpower in the hardware operations division and then announced an artificial intelligence center within the country as well. Now, a leaked document claims the tech giant is planning on getting their search engine back into China with the project being called "Dragonfly." Naturally, it will be a censored version. Websites and search terms about human rights, democracy, religion, and peaceful protests will not be allowed.

The engineers at Google have gone as far as to create two different applications, one called "Maotai" and the other called "Longfei." These applications are Google's attempt to demonstrate what it can bring to the country of China. Estimates say that finalized versions of these applications could be launched in the next 6 to 9 months. Thanks to the new president of the United States, relationships with foreign countries have been on a downslide, but we will have to wait and see if the Mountain View tech giant and China can end up coming to an agreement here.

Update: Sundar and Sergey respond

The WSJ reports that Sundar Pichai addressed these claims at a weekly all-hands meeting. He said the company is "not close to launching a search product" in China. Sergey Brin also spoke at the meeting, saying the progress in the country is "slow-going and complicated." He also said launching projects in China requires "a certain set of trade-offs."

Source: The Intercept

from xda-developers

Google allegedly making a smart home display to take on the Amazon Echo Show


The smart speaker market is dominated by Amazon and Google. Amazon is currently in first place with the company's Echo line of smart speakers, with the Google Assistant-enabled Google Home lineup a close second. Earlier this year at CES 2018, the first display-equipped smart speakers were launched in the market. Now, a Nikkei Asian Review report states that Google is preparing to release a smart speaker equipped with a display for 2018's holiday season, a move likely to increase competition with Amazon and Alibaba Group.

The new product is likely to be similar to the Amazon Echo Show, and it will round out the Google Home range of smart speakers that are powered by the Google Assistant. An unnamed industry source told Nikkei Asian Review that Google is targeting to ship three million units for the first batch of the new display-equipped smart speaker. The source commented that it's an aggressive plan.

The report notes that according to research company Canalys, Amazon shipped only 315,000 units of the Echo Show in 2017. At CES, Google introduced its new smart display platform to partners such as Lenovo Group, JBL, LG Electronics, and Sony, which enabled the partners to build Echo Show-like devices. However, the company is yet to release its own product in this category.

Its smart speaker lineup currently includes the standard Google Home, low-cost Google Home Mini, and the high-end Google Home Max. The Home and the Home Mini are intended to be competitors for Amazon's Echo and Echo Dot, while the Home Max competes with Apple's HomePod, which is powered by Siri.

Nikkei Asian Review states that Google's upcoming display-equipped speaker will still probably rely on voice commands. The presence of a display will mean that users will be able to play YouTube videos, check calendars, view maps, etc. Some industry executives are predicting that more display-equipped smart speakers will arrive soon as image and video recognition features become more mainstream.

The smart speaker is mostly a duopoly, according to data from Canalys. 35 million smart speakers were shipped worldwide in 2017, with Amazon taking the top market share with 63% share of the market, while Google took 32%. Other players were marginal.

For the January-March period, Google accounted for 36% of around nine million units shipped, with Amazon's share having fallen to 28%. The company has also increased with the likes of Alibaba, Xiaomi, Apple, and others entering the market. Demand for the smart speaker market remains high as the number of installed smart speakers is expected to exceed 100 million devices in 2018, a figure which is nearly 2.5 times more than the figure at the end of 2017, according to a Canalys report.

The report notes that Apple initially planned to ship six million HomePods this year, but it later cut the figure to about five million as users are complaining that Siri is not as powerful as Google Assistant or Alexa.

Google's hardware operations are linked with Taiwan's technology industry. The company purchased half of HTC's smartphone division last year. Most of the Google Home lineup is produced by Quanta Computer (a key builder of Apple's MacBooks), and an unnamed source told the publication that Quanta is also working with Google on a tablet to be unveiled this year. The display-equipped speaker will be made by Pegatron, however. Pegatron is a smaller rival to Foxconn.

Compal Electronics, an iPad supplier, is also engaging with Google to grab a share of the smart speaker market. Foxconn, on the other hand, will help manufacture new Pixel phones that will likely launch in October.

Google has teamed up with chip designer Broadcom for its tensor processing unit (TPU) for mega data centers looking to accelerate computing of customized AI algorithms to help recognize and analyze images, languages, text and videos in the cloud. TSMC, the world's biggest contract chip maker, is handling production of TPUs.

The publication stated that Google declined to comment on the new hardware products plan report.

Source: Nikkei Asian Review

from xda-developers

Thursday, August 16, 2018

Google Camera vs. OxygenOS Camera: Which is better on the OnePlus 6?

oneplus 6 gcam google camera

The OnePlus 6 is one of the standout devices of 2018. Like many of its predecessors, it offers a compelling flagship level performance package at a good value, at least when compared to what other offerings are available. Outside of discounted flagships, or older devices at an unexpectedly lower cost – like the Pixel 2 – it is hard to find much around this price point that can compete. That said, the Achilles heel of OnePlus, outside of their early marketing efforts, has traditionally been their cameras. While their camera game has stepped up significantly in recent years, inching closer to flagship levels, the camera is still lacking, especially in the processing of photos. As such, and being that the OnePlus brand usually brings out the abandoned Nexus warriors, the GCam mod has become near essential on prior OnePlus flagships.

GCam stands for Google Camera mod, and it refers to particular applications modded off those found on the Pixel devices and older Nexus models. For the past few years, developers have worked to port this application to various phones, and since all phones are not created equally, this hasn't always been an easy task. This particular mod for the OnePlus 6 brings over some of the features specific to the Pixel, like Rear & Front HDR+, Lens Blur, Panorama, PhotoSphere, and Google Lens. Since the initial post at the end of May, many bugs have been fixed, like phones taking black and white photos, camera tint, application crashes, and more. In its current state, it is certainly a very usable application. The question, though, is whether this mod still improves upon the current OnePlus flagship's camera like it did for prior ones like the OnePlus 3, which has greatly benefited from this work. So let us compare the stock camera vs the GCam mod and see if you should make the switch.

Want to try the Google Camera Mod on your device? The Google Camera Port Hub is a centralized location where you can go to find a working port for your device. Currently, the hub has over 40 devices listed, including the Samsung Galaxy S9, Samsung Galaxy S8, LG G7 ThinQ, Essential Phone, OnePlus 6, Xiaomi Mi 8, and many more. Each device has at least one port that should work for that device. It's important to note that most Google Camera ports are not perfect. They all have their pros and cons. We tried to find the ports that have been endorsed by users on our forums. You may be able to find a better port on the forum for your device, but our hub is a good place to start.

Google Camera Port Hub

Disclaimers: The particular version of the Google Camera was the OP6_test_1.2.2_GCam_5.3.015-PixelMod which was the newest 'stable' version at the time of my testing. I used it on the newest firmware at the time from OnePlus – 5.1.9 and the camera software matched. These are my opinions of these photos and every one of us will see them slightly differently. While I will offer my opinion on the shots, you are free to disagree. I am not always right. Even if you disagree with my assessment, I hope you find the images in this comparison valuable and that they help you arrive to your own conclusion. We are using Flickr today instead of our normal built-in gallery to preserve the image quality.

The first photo is always the GCam photo, just hit the arrow to see the photo or toggle through them.

Test #1 – Mid-Late Afternoon


Superficially, looking at these two photos, they are very similar. However, if you look closer, you will start to see some things that trend through all of our photos: GCam tends to favor less exposed shots that give it a moody feel while trending blue in hue, and the stock camera trends more reddish orange. Here the GCam did a much better job on the grass, giving it a subdued feel, whereas the stock camera punched the colors up a little too much. That changes when you get to the trees in the back of the shot and the clouds. I feel GCam did a poor job punching the shadows around these subjects and making them stand out far more than they should have. Also, the tree leaves on the left and right of the image are a dark sickly blue-grey color on the GCam version, where they are more accurate on the stock software, and brighter to boot.

Test #2 – Dusk Parking Lot


This photo really shows the blue hue the GCam mod loves. Neither of them are particularly great shots, but the GCam picture is just wrong as it doesn't quite match the scene it's trying to depict. I think thanks to the GCam's tendency to punch up the HDR on photos it got a little more detail, but overall they are both decent photos in a bad situation.

Test #3 – Lit Sign


Here the photos are quite different again. If you focus on the colors of the sign, in particular, the T and S letters, you can see they vary wildly between shots. I am not quite sure what the GCam was doing here, but those colors are not lifelike. However, the stock camera did a very poor job on the bottom of the shot. I have no idea where that light source is because in person it was nowhere near as bright or scene-changing. The GCam overall did a better job here but really altered the colors on the sign making them look unnatural.

Test #4 – Early Morning Direct Sun


This is a shot I love to do with my camera tests. It has a lot of different colors, subject depths, and is interesting to see how different devices handle the scenario. My preference is to go ahead and overexpose a background subject that is already very bright to bring out the highlights in other more prominent subjects, but not everyone agrees and this is a perfect example. On the stock camera, the leaves of the bush and the tree are very bright and a very good representation of what the lighting was like. The GCam photo brought the exposure down a bit due to the fence in the back and thus produced a more dramatic photo. Personally, I prefer the stock camera, but neither are bad and they both do a solid job here.

Test #5 – Early Morning Direct Sun – Leaves


The GCam shot is quite terrible and showcases something I frankly do not tend to like about the Pixel camera, as that blue hue leaves a lot to be desired. In contrast, the stock camera did a great job on this photo. The color balance is warm and natural and although the top right corner does show some weird coloring, there is a lot of detail, exposure is proper on the subject, and nothing is really unsightly.

Test #6 – Mid-Afternoon Parking Lot


This one, like test #4 is a toss-up. It all comes down to your preference in terms of the white balance. I think the GCam did a better job making the photo look appealing and the stock camera is more realistic. Neither is wrong, both did a good job.

Test #7 – Crosswalk Sign


Again like #4 and #6, they both do a good job. Personally, I think the stock camera did a better job here preserving details and exposure on the left side of the frame and on the grass, where the GCam went for a more flat photo that lost some of the finer details. In terms of the color though, the GCam did a better job as the stock camera pushed things a little outside of what was realistic.

Test #8 – No Parking Sign


This is a very weird shot and neither are bad, they are just different. The stock camera has unrealistic greens and blues, but the red on the GCam mod is not correct whereas the background is. The OnePlus camera also tended to preserve a little more detail in this shot on the post. Again though, neither is a bad shot, they are both fairly good.

Test #9 – Unknown Spaceship


I am sorry for the different setup in this shot. Unfortunately, the GCam would not take the shot without using the flash, so I had to toggle it off manually and shifted slightly without realizing it. That being said, they show the same things we have seen before, GCam is blue, the stock is red. Otherwise, I think they both did a good job balancing this shot out and I think the stock camera kept a little more of the details on the ship.

Conclusion Time

Would I recommend you going and switching over to the Pixel cam mod today? No, for a lot of reasons. However, that is not to say you should never use the Pixel camera and having it installed for certain scenarios is beneficial. OnePlus just pushed a massive camera update a few months ago and one of the larger changes was that they were doing significantly less post-processing on their images. This generally leaves a lot of detail and really solid exposure, which we have seen. Unfortunately, though, there is a nasty side effect of this and I am not sure why it exists, maybe some further tuning is required.

If we punch in on the first shot (and this occurs in nearly every shot) you can see a texture on the image, almost like the raised effect you get from paints on a canvas or printing lines. It distorts nearly all the fine line detail, whereas the GCam mod smooths it out a bit. While looking at the photos at 100% you hardly notice it, the second you go to 150% or 200% it becomes clearly visible as they follow horizontal alignment, something that is unnatural in most photos. I also cannot imagine that this would be good for printing. I hope this is something OnePlus can address as it stands out in quite a number of shots the moment you zoom in.

Back to the GCam though, there are a few other reasons I would not recommend it at this time. The focus is abysmal and cannot really be trusted. It is something that the developers are working on, but currently, I could not recommend either of the three versions as they all were fairly slow to focus, something the stock software has no issue with. Also in tandem with this focus issue is the shot delay. Typically there is a solid second or two before the shot actually fires off, sometimes with me wondering if the shot had already been taken, often right as the screen flashes letting me know it just had. That said, the developers are actively working on this mod for the OnePlus 6 and improvements are coming on a regular basis. I think within a few months it could be on par with the stock camera in terms of reliability. It is a major accolade to the developers working on this mod as it has brought major improvements and usability to so many older devices such as the OnePlus 3.

It also could be a major testament to OnePlus developers who have done a fairly good job with their post-processing outside of that issue I mentioned earlier. Despite the problem with the textured noise or over-sharpening, it is still a large improvement over the overly-smoothed effect the prior versions had or the oil painting effect the OnePlus 5 had been known for. OnePlus got most of the things that are required to take a good photo quite right, at last. The colors are accurate, shots are properly exposed, details are not smoothed out, and none of the shots I took with the stock software were bad — that has pretty much been my experience since the 5.1.9 update. Either way, if you choose to mod or to not mod, the OnePlus 6 is continuing to shape up to be a very competitive package, camera included.

You can grab the GCam mod for the OnePlus 6 or follow along on its progress here!

from xda-developers