Unofficial TWRP now available for the OnePlus 6

The latest flagship from OnePlus, the OnePlus 6, is a true powerhouse, and it’s finally starting to reach the hands of developers. Custom development for OnePlus devices has always been stellar: Just look at the activity on our OnePlus 3/3T and OnePlus 5/5T forums to see what we’re talking about. We don’t expect anything different from the new OnePlus 6 which, by the way, is both OnePlus’ first phone with Project Treble compatibility and their first phone with A/B partitioning for seamless updates. If you now have your OnePlus 6 in your hands and you want to start tinkering with it, an initial, unofficial TWRP build is now available for the device, meaning that you can now root your phone with Magisk and, in the future, install custom ROMs.

If you are interested in trying out TWRP for your device and root it, be sure to head over to the forum thread linked below. Keep in mind that you’ll first need to unlock the bootloader of your device, which shouldn’t take very long but does require a full data wipe so be sure to do it as soon as you can otherwise the transition from stock to unlocked will be painful!

Download unofficial TWRP for the OnePlus 6

from xda-developers https://ift.tt/2J6mZbg
via IFTTT

Bootloader unlock method has been found for the Verizon Google Pixel/Pixel XL

In the United States, Verizon Wireless is the exclusive carrier of the first generation and second generation Google Pixel devices. Verizon is known to be unfriendly to users modifying their devices, and thus any devices purchased from the carrier cannot have their bootloader unlocked. Unlocking the bootloader of a Verizon Google Pixel device needs either an exploit or a clever bypass, and it looks like another clever bypass has been discovered by XDA Members LeoTheRomRasta and Qu3ntin0 on our forums. So far, members are reporting that it works on the first generation Google Pixel and Pixel XL sold by Verizon.

How to unlock the bootloader of the Verizon Google Pixel/Pixel XL

Credits for the instructions below go to XDA Members Qu3ntin0, which he has posted here. XDA Senior Member burduli re-wrote the instructions and tipped us off on this method earlier today, so we also thank him.

Warning: Unlocking the bootloader will wipe not only any app data on your phone, but ALL data stored in /data/media. Please back up any documents, images, music, and more if you haven’t already.

1. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.
2. Eject sim card from your device.
3. Reset your device. In setup wizard, skip everything, don’t connect to WiFi, don’t add fingerprint or any kind of screen lock.
4. Go to Developer Options and enable USB debugging.
5. Connect your phone to PC.
6. Open CMD in adb directory and type: adb shell pm uninstall --user 0 com.android.phone
7. Restart your device.
8. Connect to WiFi, open Chrome and go to google.com (or any website really).
9. Go to Developer Options and enable OEM unlocking.
10. Reboot into bootloader and via CMD run: fastboot oem unlock OR fastboot flashing unlock
11. Profit

If we could take a guess at what’s happening here, it looks like the phone app (com.android.phone) app checks whether the device shouldn’t have access to OEM Unlocking at first start. However, if you disable Internet access entirely, remove the SIM card, and disable the phone app, then it never gets the chance to perform that check and hence you will have access to unlock the bootloader.

Enjoy this method while it lasts!

from xda-developers https://ift.tt/2LC7Uwm
via IFTTT

LineageOS 15.1 Changelog 18: Reader Mode, “Chrome Home” in Jelly, Per-app network restrictions, and more

On all supported devices, LineageOS 15.1 is released on a weekly basis. It can be hard to keep up with what’s new in the popular AOSP-based custom ROM unless you religiously follow their Gerrit, so the team has put together a changelog to keep you updated on what’s new in the ROM. Today, the team has published their 18th changelog, and there’s a lot of features to cover since their last changelog post on April 1st. Here’s what’s new:

LineageOS Changelog since April 1st

• It’s now possible to restrict WiFi and/or mobile data usage for each app
• LiveDisplay has been rewritten as a binderized HAL
• Dialer can now enable Do Not Disturb during calls to avoid notification sounds while you’re in a call
• Reader mode can now tweak your display to make documents and long texts easier to read
• Trebuchet now has smarter apps suggestions in the drawer. These will change during the day and whenever you plug in the headphones
• Trebuchet can also put legacy app icons into an adaptive icon box
• Jelly has a new “reach mode” that moves the top URL / search bar to the bottom for easier reachability
• Updater has been updated for better reliability and it now supports dark mode through the Styles API
• May security patches have been merged in 15.1
• April and May security patches have been merged in 14.1
• Chromium webview has been updated to version 66.0.3359.139 (both 14.1 and 15.1)
• Keyboard now recognizes incognito text fields and it won’t learn for suggestions when typing in one of them
• FlipFlap now ignores low priority notifications (both 14.1 and 15.1)
• Legacy prebuilt camera HAL 1 support has been re-added
• SSH support has been re-added

Since the custom ROM was first announced back in February, it already had a ton of features for users to enjoy. These changes add to what’s already a feature-packed experience for users.

Current list of supported LineageOS 15.1 devices

We’ve been tracking which devices have received official builds of LineageOS 15.1, so here’s our current list of all supported devices:

• Google Nexus 4 – Download Page – Changelog
• Google Nexus 5X – Download Page – Changelog
• Google Nexus 6 – Download Page – Changelog
• Google Nexus 6P – Download Page – Changelog
• Google Nexus Player – Download Page – Changelog
• Google Pixel C – Download Page – Changelog
• HTC One A9 – Download Page – Changelog
• LeEco Le Max 2 – Download Page – Changelog
• LeEco Le Pro 3 – Download Page – Changelog
• Motorola Moto Z – Download Page – Changelog
• Nvidia Shield Android TV – Download Page – Changelog
• OnePlus 2 – Download Page – Changelog
• OnePlus 3/3T – Download Page – Changelog
• OnePlus 5 – Download Page – Changelog
• OnePlus 5T – Download Page – Changelog
• Samsung Galaxy S9 (Exynos) – Download Page – Changelog
• Samsung Galaxy S9+ (Exynos) – Download Page – Changelog
• Samsung Galaxy Tab S2 8.0 Wi-Fi (2016) – Download Page – Changelog
• Samsung Galaxy Tab S2 9.7 Wi-Fi (2016) – Download Page – Changelog
• Xiaomi Mi 5 – Download Page – Changelog
• Xiaomi Mi 5s – Download Page – Changelog
• Xiaomi Mi 5s Plus – Download Page – Changelog
• Xiaomi Mi 6 – Download Page – Changelog
• Xiaomi Mi Mix 2 – Download Page – Changelog
• Xiaomi Mi Note 2 – Download Page – Changelog
• Xiaomi Redmi Note 4 (Snapdragon) – Download Page – Changelog

The list has grown pretty extensively since the initial release. Currently missing on this list are devices with A/B partitions like the Google Pixel smartphones and the Xiaomi Mi A1. The LineageOS team is working on fixing their addon.d script (the script that backs up GApps and their SU addon) so that it works with A/B devices. Once that is finished, we should start seeing A/B devices get added to the roster.

Miscellaneous Changes

CVE Tracker

The LineageOS Common Vulnerabilities and Exposures (CVE) Tracker was a page where users could see which security vulnerabilities their device had patches merged for. However, that page was often outdated because it required the device maintainer to manually update the status of their device’s patches. Until the team’s auto-patcher is ready, they have made the page private.

Code of Conduct

In an effort to improve their public appearance and promote professionalism among the team, the Project Directors have adopted a Code of Conduct that applies to all members of the team.

Privacy Policy Update

The EU’s GDPR went into effect today, so the team has updated their privacy policy to include information on how their Gerrit collects some personal information.

LineageOS 14.1 Roster Changes

LineageOS 14.1, based on Android 7.1 Nougat, still supports a ton of devices. The requirements for a build to be official back then weren’t as strict as they are now because of the Charter, so many devices will still be on 14.1 for the time being. The Samsung Galaxy S7 and Samsung Galaxy S7 Edge have been removed from the 14.1 build roster, however, due to “licensing issues of the device trees.”

from xda-developers https://ift.tt/2KRQsD0
via IFTTT

ZTE Axon 7’s Android Oreo beta update has been leaked

The ZTE Axon 7‘s Android Oreo update is finally here, although you’ll have to jump through some hoops to get it. A developer on our forums has managed to get their hands on a leaked build of the closed Android Oreo beta for the device, and he is providing it for all users to install.

Screenshots via: XDA Member Victor13f

ZTE Axon 7’s update history:

• The ZTE Axon 7 was released in 2016 with Android Marshmallow. It was a sleeper hit of 2016 thanks to its high-end specifications at a mid-range price, much like the device it competed directly against: the OnePlus 3.
• The device was upgraded to Android 7.0 Nougat, which also happened to bring Daydream VR support thanks to the Axon 7 sporting a Quad HD AMOLED display.
• In December, ZTE promised that the official Android 8.0 Oreo update was “right around the corner.” The update would reportedly feature a UI revamp that takes more cues from stock Android rather than MiFavor, ZTE’s flavor of Android. Later in February, the company opened a beta program in the U.S.
• Behind the scenes, ZTE was quietly working with some developers of LineageOS to give them a head start on bringing up LineageOS 15.1 for the device.
• Last month, the U.S. government barred American companies from exporting prohibited goods to ZTE. This effectively crippled the company, and the future of software support for their existing devices came into question.

An Android Oreo leak to save the day: With ZTE’s business operations effectively dead, it seems like there’s no hope for Axon 7 owners to receive the Android Oreo update they were promised. However, XDA Senior Member NFound, a developer for the AOSP Extended custom ROM, has released the beta Android 8.0 Oreo build for the device. He has provided the update in the form of a TWRP-flashable build, which means you’ll need to unlock the bootloader of the device to flash it. He has also created a video showing off the build, for those of you who want to see what to expect before you go down this path.

Download Android Oreo beta for the ZTE Axon 7

Instructions on how to flash the ROM

from xda-developers https://ift.tt/2J6hvxa
via IFTTT

OxygenOS 5.0.3 for the OnePlus 3/3T brings May security patch and Face Unlock

Last time we checked in on the OnePlus 3 and OnePlus 3T, they were receiving an OxygenOS Open Beta update with a few new features. Today, OnePlus has begun rolling out OxygenOS 5.0.3 to the OnePlus 3 and OnePlus 3T. This is a full stable release for all devices. The update includes Face Unlock, the latest security patch, and a bevy of other features and fixes. Here’s the official changelog.

Launcher

• Refined Shelf UI design
• New design for App shortcuts
• Supported more options when long pressing an icon

Gallery

• Places: a map view of photos by location
• Supported sharing photos to Shot-On-OnePlus
• Added “Recently Deleted” collection

File Manager

• Added “Large files” category

Weather

• Added new widget for Launcher
• Improved the positioning accuracy
• Adjust refresh interval for weather information update

OxygenOS 5.0.3 also includes the May security patch and several optimizations to “improve several key areas.” This is an OTA update that should start appearing on some devices right away, but it will ultimately roll out to everyone over the next few days.

OnePlus promised Face Unlock would be coming to the OnePlus 3/3T back in January. It’s great to see them follow-up on their promise and continue to update a phone that certainly isn’t new anymore. OnePlus has been consistently rolling out OxygenOS beta updates for these devices.

---

Source: OnePlus

from xda-developers https://ift.tt/2LvffxL
via IFTTT

The LG V35 ThinQ shows up on the Wireless Power Consortium

LG is one of a handful of smartphone OEMs that have been having a hard time bringing in a profit. This has caused the company to take a new stance when it comes to releasing yearly flagship smartphones in an attempt to save some money. We have been told that LG likes the idea of keeping their main flagships in the spotlight until they feel the company is ready to release their successors. The company says they will be more inclined to release multiple variants of their current flagship instead of releasing a new one on schedule every year. We’ve already seen this with the LG V series and now we’re able to see what the upcoming LG V35 ThinQ will look like, thanks to the Wireless Power Consortium.

Rumored Specs

• Previous reports have revealed what hardware LG is going with in their upcoming LG V35 ThinQ.
• The FullVision display is said to have a diagonal of 6″ with a Quad HD resolution and P-OLED technology.
• The V35 ThinQ is said to have the same 16MP + 16MP dual camera setup on the back
• Image shows LG is staying away from the notch this time around.

We see a lot of the same design elements in this photo of the LG V35 ThinQ as we’ve seen in the Pixel 2 XL. The side bezels are kept extra slim with what looks like 2.5D glass on top of the display. Instead of opting for the trendy notch design LG seems to be keeping the top and bottom bezels as slim as possible while having enough room for the speaker, sensors, etc. AT&T chose not to sell the LG G7 ThinQ but one rumor from AndroidHeadlines says the wireless carrier will be carrying the LG V35 ThinQ.

---

Source: Wireless Power Consortium Via: @evleaks

from xda-developers https://ift.tt/2krbmxO
via IFTTT

Samsung ordered to pay Apple $539 million for copying their design

As a result of a seven-year-long legal battle, Samsung has been ordered to pay $539 million dollars as a result of patent infringement. They were found liable all the way back in 2012, but disagreements over the amount to be paid caused massive delays. Samsung had already paid $399 million to Apple for infringement of patents.

The devices accused of copying Apple’s design philosophies are Samsung’s mobile phones and tablets released in 2010 and 2011, with the company accused of “slavishly” copying their products. If the verdict is upheld following the appeal, then they will have to pay an additional $140 million on top of the already paid amount.

“We believe deeply in the value of design,” Apple said in a statement. “This case has always been about more than money.”

Samsung’s statement does not say whether they plan to appeal the verdict, but it’s generally assumed that they will.

“Today’s decision flies in the face of a unanimous Supreme Court ruling in favor of Samsung on the scope of design patent damages,” Samsung said in their statement. “We will consider all options to obtain an outcome that does not hinder creativity and fair competition for all companies and consumers.”

The verdict comes after Apple said it was seeking $1 billion in damages. The jury ruled that $533.3 million be paid for violation of design patents, while an additional $5.3 million be paid on utility patent violations. Samsung tried to argue they should only have to pay $28 million, which meant that the patent infringement would be limited only to the infringing components of the devices. This is instead of awarding Apple the full profits from device sales, which is what Apple was attempting to seek.

This isn’t the first time that Samsung has had to pay money to Apple for patent infringement, paying $548 million to them back in 2015. $399 million of that value was for patents included in the ruling made yesterday.

---

Via: Reuters

from xda-developers https://ift.tt/2GOsciJ
via IFTTT