Some history with the phone. I've gone back and forth a few times with this phone. At one point the bootloader was unlocked, I was rooted, etc etc. This was quite a while ago. Since then I have flashed the factory rom, locked the bootloader and ran 100% pure stock until this morning and everything worked just fine. Android Pay worked, etc. Today I decided I'd do a factory reset and not bother restoring data. Prior to doing that, I decided to give Magisk a quick try just for the heck of it. I flashed the current Oreo factory image (With Sept security patches) left the bootloader unlocked, flashed TWRP, installed Magisk via TWRP. Didn't really give it much of a chance but either way, after a quick check safetynet failed. So I figured, whatever no big deal. I flashed the factory image again, then relocked the bootloader, and eventually rebooted and signed back into my account and didn't bother restoring any backup. Let all the stock apps install/update, checked Android Pay.....and it wouldn't allow me to add a card. I checked the Safetynet tests and it fails the CTS Profile match. I'm pretty much at a loss now as to what in the world the problem is. The phone is fresh off of a factory reset and the bootloader is locked. No magisk, no root, nothing.
Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Well I unlocked the bootloader again, flash the August 7.1.2, relocked the bootloader, and after updating apps and Google Play Services, all is well again. Guess I'll just grab the OTA and go from there.
Wow, so sideloading the OTA broke it again.
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
glad someone else is seeing this, sideloaded OTA build 017 and Android Pay stopped working with it failing Safetynet's CTS Profile check
ParadingLunatic said:
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
Click to expand...
Click to collapse
Where is this 019 OTA? I'm having this same problem. I thought I was the Andromeda I tried but I knew that was rootless.
Thanks for shedding light on this.
---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------
Did some more digging. Found it. Gonna see if it works.
Sent from my Nexus 6P using XDA-Developers Legacy app
ParadingLunatic said:
... Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Click to expand...
Click to collapse
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
stevemw said:
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
Click to expand...
Click to collapse
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
ParadingLunatic said:
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
Click to expand...
Click to collapse
Didn't realize it was automatically set in Oreo. I went thru 7 and the preview, so this option was already set. I will be getting the Pixel 2 XL, so it's something for me to check on.
Related
I recently bought a Nexus 6P and I just rooted it a few days ago. I have been reading about how it is less safe now that the bootloader is unlocked, so I figured I could encrypt my phone for more securities! I don't want ro re-lock since unlocking will wipe my data all over again.
So I went into Settings->Encrypt phone and started the encryption process. It first showed a green outline of an Android, then it started the boot animation. It stayed there for about half an hour and it was clearly not encrypting (not getting hot or anything) so I just rebooted (I have a backup, that's why I'm so bold ) and it just normally rebooted to a working phone with nothing encrypted. Tried it again, same result.
I'm running Marshmallow 6.0.1 MMB29M with TWRP, SuperSU (I'm pretty sure it's systemless) and Xposed. I'm not sure what kernel I flashed when I rooted (that is the boot.img, right?).
Is this a bug? Is it a feature? I would like to be able to encrypt my phone; does anyone have any ideas on how to achieve this, now that TWRP can decrypt stuff?
Thanks!
I have the same issue with a HTC One M8 running Marshmallow 6.0 and systemless root. I've had this phone encrypted in the past but that was with standard root. Seems like systemless root and something to do with the modification of the boot image has something to do with encryption breaking.
Glad I made a nandroid before starting also, just incase.
I got it to work
So I just flashed the latest 6.0.1 (MMB29P) system, boot, etc. partitions because of the January security update. I folllowed Heisenberg's guide, point 10. I then had to reflash TWRP and then install SuperSU and Xposed again, because they were gone.
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
What you need to do is to remove any security you set up (just set the lockscreen unlock to "None") and then re-add it. When the phone asks if you want it to require the password at startup, say yes. It will then change the encryption password to your custom one and voila, your phone is now encrypted and uses your password/pin/pattern/whatev.
tudy77 said:
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
Click to expand...
Click to collapse
Question, is the default password: "default_password" lowercase and all? Im on the same boat you were, about to do this just to get encryption back but i want to be 100% sure of the steps lol
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
tudy77 said:
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
so i dont type anything just hit enter?
I was not prompted to type anything
Sent from my Nexus 6P using Tapatalk
Hello guys,
I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization.
I formatted the phone after receiving the Oreo OTA and the phone is full stock.
Anyone know how to fix this issue?
Thanks!
VSTOLL said:
Hello guys, I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization. I formatted the phone after receiving the Oreo OTA and the phone is full stock. Anyone know how to fix this issue? Thanks!
Click to expand...
Click to collapse
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
v12xke said:
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
Click to expand...
Click to collapse
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates.
My build number ends with .019
VSTOLL said:
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates. My build number ends with .019
Click to expand...
Click to collapse
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
v12xke said:
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
Click to expand...
Click to collapse
There was no failed or hung syncs but I removed and added my account again anyway.
I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events.
My bootloader is locked.
VSTOLL said:
There was no failed or hung syncs but I removed and added my account again anyway. I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events. My bootloader is locked.
Click to expand...
Click to collapse
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
v12xke said:
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
Click to expand...
Click to collapse
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?
I found this post: https://productforums.google.com/fo...utm_source=footer#!topic/calendar/FzD9Y6ojci4
Theres a reply by Mikel Rodriguez that says:
"The cause of the calendar notifications failure is a change in the architecture of the calendar provider module. It is a content provider located at the application framework layer. Supposedly they changed the architecture of the module because it wasn't compatible with the doze feature of Marshmallow. So, all phones running Marshmallow or higher are fully affected by the failure. The only solution is to root, install titanium backup, make a backup of package com.android.providers.calendar, then uninstall it, then download and install the same package for version 5.1.1 (Lollipop). Because that version is not compatible with doze, it is necessary to remove it completely. Download "Boeffla Doze Control", open it and turn on "disable doze at start up" and "show toast message", then reboot, then open it again and check that doze status is off. That means that doze is not working. Calendar notifications will work again if you follow all the steps."
I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
VSTOLL said:
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?....... I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
Click to expand...
Click to collapse
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
v12xke said:
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
Click to expand...
Click to collapse
I'll wait for the next OTA then, and if it doesn't fix I'll try formatting and restore it with the Google tool you said.
By the way, I didn't received a incremental OTA. I live in Brazil, so the update arrived later here, I received it 2 weeks ago and was a 1GB download and I haven't received any security or incremental updates since that day.
I set an event and it'll remind me in 2 hours, I'll let my phone down and will not use it to see if the nofication will work, if it doesn't, I'll try this app: https://play.google.com/store/apps/details?id=com.github.quarck.calnotify&hl=en
Hey Folks!
Hope someone can help me out here. I've read a whole bunch of forums and have tried a number of potential solutions to no avail. I have Magisk 15.2 installed and am running Lineage OS 14.2. Multiple apps confirm I pass Safetynet and I can successfully add a card to Android Pay. However, when I try to pay at a terminal, nothing happens. I have tried multiple terminals with no success. Nfc is enabled and android beam works.
Thanks!!!
Try enabling Core Only Mode in Magisk settings, try disabling systemless BusyBox, or try uninstalling your version of Magisk and trying the latest beta. SafetyNet is a nightmare to keep up with. Every time it updates, Magisk gets broken and we have to wait for a new update. Unfortunately, the only real solution is to stop using SafetyNet-dependent apps or keep a locked bootloader/unrooted phone. Or perhaps have one phone for custom ROM stuff and another one for SafetyNet stuff. :/ This is why I'm so vocal about ROMs passing SafetyNet. Hopefully you'll find a fix.
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
lastconfederate2 said:
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
Click to expand...
Click to collapse
You don't get an error message or anything? Sorry, I missed that. Not sure what the issue is, then. I assume by the other apps, you mean legit apps that actually check for SafetyNet, like downloads in Netflix, a game like Fire Emblem Heroes or a banking app like RBS. If you're able to use those apps or use all of the features perfectly, the issue might just be Android Pay, which probably now detects Magisk(?). Anyway, unless you're actually able to use an app that uses SafetyNet, those SafetyNet checkers don't count for much.
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
lastconfederate2 said:
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
Click to expand...
Click to collapse
I am experiencing the same issue but with Omni 7.1 and Magisk 15.2.
Card was added but giving "Card read error" at payment terminal.
If changing the settings or flashing a beta build doesn't get it to work, then I'm not sure what will. If you're able to, backup your existing ROM and factory reset it. If your Pro3 variant has an official LeEco ROM that passes SafetyNet natively, flash that and lock the bootloader and set up Android Pay to see if it works. Can't offer much else to help you, sorry.
Might be nothing to do with your problem, but i noticed when using nfc to add contacts with other nfc phones etc, that this phone has its nfc chip at the bottom/middle of the phone (it was a while ago, hope I've not remembered incorrectly). Until i realised this i had problems getting it to work.
Edit.. my memory is so bad in now thinking it was the very very top of the phone. Try both.
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
lastconfederate2 said:
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
Click to expand...
Click to collapse
Are you still able to get it to work like this? What was the last update you installed? I am trying to do some research to figure out why this happens on many different devices with different roms and such. Most seem to have the ability to get Pay to work and load cards into it, but using at stores and tapping the terminals does nothing(currently my issue).
So what is you setup as of now? Magisk ver, universal safetynet fix(if you're using that) ver, OS ver/date, and what security patch?
If you can provide those things it would be helpful.
Thank you.
Yes, that is still how it works, though I've found over time that it works more like 25% of the time. The last LOS update I have installed is February 10th. I'm using Magisk 15.3, running Android 7.1.2, and last security patch is 1/05/18.
Thanks!
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
wkwk said:
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
Click to expand...
Click to collapse
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
tsongming said:
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
Click to expand...
Click to collapse
Yes same issue.
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
lastconfederate2 said:
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
Click to expand...
Click to collapse
It will probably work in Lineage 14.1 once its been updated for the newer api.
It's been a while since I've flashed a ROM, and I've forgotten a couple of things. I'm thinking of trying preview #2 of Android P on my PH-1.
After I've played around with Android P, I expect I'll want to return to where I am now on Oreo 8.1. I know I'll need to reload 8.1 from an official image file and that my data and (most) apps will have skedaddled.
Question: What's the best way to (1) back up and (2) restore my Oreo 8.1 system exactly as I have it?
I'm not planning to root this phone, though I've rooted several in the past. Can I back up and restore without rooting?
Thanks.
If you use stock launcher and without root, I don't see how you can get everything exactly as it was. But you can get almost everything except the actual placement of apps on screen with the default Google back up. You get all your apps, call history, sms, network configuration, etc.
---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------
By the way, I've been using P for three days. So far, I find no good reason to go back. My only bug is that Google Pay doesn't work.
Thanks, pmicho. I'll probably go ahead with the preview.
pmicho said:
If you use stock launcher and without root, I don't see how you can get everything exactly as it was. But you can get almost everything except the actual placement of apps on screen with the default Google back up. You get all your apps, call history, sms, network configuration, etc.
---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------
By the way, I've been using P for three days. So far, I find no good reason to go back. My only bug is that Google Pay doesn't work.
Click to expand...
Click to collapse
Just in case if you want Google Pay to start working, flash magisk 16.4 and reboot twice until the safety net starts passing.
mikamika83 said:
Just in case if you want Google Pay to start working, flash magisk 16.4 and reboot twice until the safety net starts passing.
Click to expand...
Click to collapse
P preview #2 passes safety net ?
Thanks, guys. I sideloaded the P preview 2 just now and it went fine.
Last night I had tried the fastboot method and my results weren't as good. Wifi didn't work, for some reason. Anyway, after two failed fastboot attempts, I re-flashed stock 8.1 and used Google's backup to restore most data and apps.
Then this morning I decided to use the sideload method, which was far easier and which didn't touch my data. Why doesn't Essential recommend this method instead of providing detailed instructions for the fastboot flashing method?
To use magisk you need a custom recovery and unlocked bootloader. I feel I don't need root so I keep my bootloader locked. Wit a locked bootloader there shouldn't be safety net issues. In fact, I think its not safety net issue that causes Pay to not work.4
pmicho said:
To use magisk you need a custom recovery and unlocked bootloader. I feel I don't need root so I keep my bootloader locked. Wit a locked bootloader there shouldn't be safety net issues. In fact, I think its not safety net issue that causes Pay to not work.4
Click to expand...
Click to collapse
Magisk passes SafetyNet. That's why Pay, Snapchat, etc, have worked previously. I believe Pay just isn't working with P at the moment.
spotmark said:
Magisk passes SafetyNet. That's why Pay, Snapchat, etc, have worked previously. I believe Pay just isn't working with P at the moment.
Click to expand...
Click to collapse
Isn't working on P for Essential I guess. On P on a Pixel 2 Pay works.....lots of P.
pmicho said:
lots of P.
Click to expand...
Click to collapse
Ewwww.
P preview 2 definitely did not pass the safety net for me, I'm assuming that's why it caused Google pay to stop working. After rooting with magisk, Google Pay started working just fine.
So I have update notice for DP5, as I am rooted, I am trying to find info on anyone that has been using this on Pixel XL. Bit of a process to be able to install OTA manually and then be able to use Google Pay again. Just wanting to hear from those that have been using it if it is stable enough at this point to use and still have all my functionality. DP4 was kinda borked to start with, so I waited a little bit to move to it.
And and to help out those that havent been informed of an OTA, files can be found right here: https://developer.android.com/preview/download-ota
Both dp4 and dp5 have been fine for me. I got dp5 via ota so it should eventually release to everyone. I haven't wiped since 8.1 and it's been ok so far. Only issue is Bluetooth track data acts wonky sometimes but that's been the case since 8.0.
Updated using flash-all.bat , removed -w
Reinstalled Twrp and rooted.
Passing security checks. Running smooth.
TWRP won't decrypt DP5
TWRP 3.2.2 won't decrypt DP5.
Am I using a fake DP 5
fastboot flashed the full image over dp4, now the navigation key differs from those previous.
Have tried factory reset, safe mode, end up no luck.
Can someone please help figure out? 1st pixel phone, rooted.
bush911 said:
fastboot flashed the full image over dp4, now the navigation key differs from those previous.
Have tried factory reset, safe mode, end up no luck.
Can someone please help figure out? 1st pixel phone, rooted.
Click to expand...
Click to collapse
Have to turn on swipe navigation in Settings, System, Gestures, Swipe up on Home Button
Thank you dude, I am so stupid
jaytv said:
Have to turn on swipe navigation in Settings, System, Gestures, Swipe up on Home Button
Click to expand...
Click to collapse
bush911 said:
Thank you dude, I am so stupid
Click to expand...
Click to collapse
Nah, we all just forget sometimes...that's what XDA is for!
tweaked said:
Updated using flash-all.bat , removed -w
Reinstalled Twrp and rooted.
Passing security checks. Running smooth.
Click to expand...
Click to collapse
Awesome, I just wanted to make sure SafetyNet was passing. I use Google Pay often, so that was a big deal for me lol. Ill be updating in a little.
I removed screen security, sideloaded the OTA install, Temp TWRP, flashed Magisk. Rebooted and passed SafetyNet. Now reapplying Security and PROFIT.
Anyone able to apply substratum themes on DP5? Worked fine on DP4, now the overlays wont build.
Far as I knew that was gonna be dead in Android P, hence the huge ticket on the topic. They were removing the engine that supported it. So I hadnt even tried to use that in Beta.
DP4 broke my Bluetooth phone audio and auto rotate. DP5 did not fix either for me. Factory reset and both were still broken for me. I exited beta and went back to Oreo to fix. Hopefully it was just an app compatibility issue or something easily fixed. I'll probably try the next round of beta and see what happens. Unfortunately phone backup does not work when going from P back to Oreo.
Is anyone else getting slow brightness changes from wake? I can count a full 2 seconds sometimes from wake to appropriate brightness being set.