I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
My wife uses 3-button navigation (I use gestures). She's unrooted and using Nova Launcher. She said she hasn't had that issue.
swieder711 said:
I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
Click to expand...
Click to collapse
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
almahix said:
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
Click to expand...
Click to collapse
Are you running any magisk modules? I thought that might be related to what I am seeing.
swieder711 said:
Are you running any magisk modules? I thought that might be related to what I am seeing.
Click to expand...
Click to collapse
Magisk for root but no other modules
I think it's not magisk related
And I'm also experiencing this on gestures
Swiping up sometimes just does nothing and is really annoying
Edit: stock on Jan update
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
superman25 said:
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
Click to expand...
Click to collapse
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
almahix said:
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
Click to expand...
Click to collapse
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
roirraW edor ehT said:
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
Click to expand...
Click to collapse
I'll try that way next time I can't update.
My 6 will do that. They just stop responding. Myself I don't need to reboot though. Either I can wait for a few seconds and they'll start working again, or at most lock then unlock the phone.
I had the same issue all the time on December update. A reboot would fix it but I have not seen it all on January update..
I had that problem with December's build, but so far it hasn't happened with January's.
Using 3 button myself on Jan update. Also use Nova and have had no issues. It was a clean install though.
I have a OP8 with a custom a11 ROM on it that 3 button navigation has worked flawlessly on. I upgraded it to 12 over the weekend and have had the buttons lock up a couple of times since. So it would appear to be a a12 thing, and not just a a12 on Pixel issue.
Related
"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.
I didn't get this "comp patch" as an individual update. Last week, I got the update with the security patches from July 1 (German G4, no branding), and it looks like that this patch was included. It now shows in the list of installed LG applications, where it didn't appear before. My wife (LG G3) got this patch as a single install (~1 week ago).
I have got this compatibility patch too, and in description of this app is 20160809 so it is 1 week old. But what was going about in that "fix"... :/
I've got the patch today too. But haven't rebooted yet.
U talking about this one? What is that supposed to do?
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
If you have the encryption on then turn it off and reboot. That should resolve the issue and then you can turn it back on. Hope it works for you.
akarshad said:
I have got this update and now it keep asking to reboot in notification bar. I have done restart many times but no luck.
Click to expand...
Click to collapse
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.
Problem with the Patch
I got the same patch on my LG V10. Thinking nothing of it I agreed to install and reboot. Once I had done so, I now have the Yellow Boot Warning at every boot. And also a bunch of my system apps stopped working. Camera, Phone, Music. I don't remember ever flashing a ROM that would trigger the warning seeing as how I got the update to 6.0.1 a few days before and hadn't done anything since. So I flashed back to stock with LGUP and the problems still persist. This is my first post ever, any advice. I apologize as I know this is a LGG4 thread.
If you did anything to the system image, you may have issues applying the OTA. @SixTheAmateur: did you modify in any way your V10? Did you flash a KDZ not officially available to your V10?
Index100 said:
Hi Akarshad, I've got exactly the same issue. Installed, rebooted multiple times and the notification to reboot is still there telling me to reboot to finalise the install.
Click to expand...
Click to collapse
Yes that was the problem. Solved after disabling encryption
Guys the compatibility patch dissappeared??? Help yesterday it showed up Today nothing
Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?
Copperwolf said:
Ok now i'm getting this on my g4 as well... Anyone ever figure out if this is a worthwhile update fir a non-rooted phone or if it's just LG crapware?
Click to expand...
Click to collapse
I've had massive compatibility issues with my g4 and apps I like to use. I noticed this today and definitely installed it. I have been able to use the apps I hadn't been able to use.
It seems to be going well so far. I'd say do it.
It seems to be frozen/disabled after installing, odd.
Sent from my LG-H811 using XDA Labs
Press and hold on notifications to see which app is giving them
Compatibility Patch Mystery to T-Mobile and LG
I got a notice for a compatibility patch several weeks ago.
Rather than click I contacted LG, who knew nothing of it.
So I contacted T-Mobile, my carrier, and they knew nothing of it and suggested I don't down load it.
It popped up again today and I'm going to ignore it until I understand what it will do.
Good Luck!
Similar experience. I had issues with my phone afterward and had to get a new one.
Similar experience. I had issues with my phone afterward and had to get a new one.
nikooe said:
"Compatibility patch" update showed up in my notification area. When I clicked on it, it took me to the LG software update section and said that this file is needed to fix some issues with app compatibility.
After installing the program asks to reboot the phone. Once the notification is clicked on, the phone reboots.
Phone is not rooted. It seemed a little sketchy since there's really no other information anywhere else on the net. It seems a bunch of other people have got this but no real info.
Just wondering if anybody else has got this update.
Thanx.
Click to expand...
Click to collapse
It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
sliding_billy said:
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
Click to expand...
Click to collapse
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
bcradu69 said:
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
Click to expand...
Click to collapse
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
ndd53 said:
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
Click to expand...
Click to collapse
I don't, but to make sure... I am using 16.0 of Magisk.
ndd53 said:
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
Click to expand...
Click to collapse
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
bcradu69 said:
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
Click to expand...
Click to collapse
that was it! I turned off Crossbreeder lite (didn't have Greenify) and now bluetooth is working again. thanks!
Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
djy said:
Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
Click to expand...
Click to collapse
The SafetyNet issue had nothing to do with March update and occurred Thursday night into Friday morning on devices of all varieties and versions. There are plenty of other conversations going on including on the thread you linked. Looks like Google is finding unlocked BL again, and Play Store fails certification on reinstall even dirty from what I have seen. You can't flash back to Feb dirty. Going back to previous updates requires a full device reset as far as I know.
I just went in to magisk manager and saw that I also failed cts. I am on the lastest patch, patched with magisk; on beta. It was fine when I was on February
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
TonikJDK said:
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
Click to expand...
Click to collapse
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
I personally had to factory reset my Pixel 3 XL and root it again. I'm passing SafetyNet but the Play store is not certified.
TonikJDK said:
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
Click to expand...
Click to collapse
I paid with GPay at two vendors this morning with filed CTS and "not certified" Play Store. Of course that did not include adding a card, but can't be certified since a couple of dirty flashes this week.,
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
fonixmunkee said:
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
Click to expand...
Click to collapse
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
sliding_billy said:
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
Click to expand...
Click to collapse
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Nope, stock kernel, rooted. Still fails.
Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Again, this did not happen as a result of anything March update related. Tons of devices that were not updated (including two of mine that haven't seen an update in almost a year and a half) started failing CTS as something that Google pushed automatically like Play services or whatever. Nothing to do with Magisk or able to be fixed with Magisk right now. Looks like they are searching for unlocked BL, and nothing is able to obscure it or know what exactly it is looking at yet (kernel, Magisk).
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Exokan said:
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
Click to expand...
Click to collapse
bobby janow said:
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Click to expand...
Click to collapse
I was just posting this because I saw it a lot earlier than others and was trying to quash any more threads about CTS failing. I find the whole thing funny how Google tries to placate app vendors who don't really want fake security but want ad revenue (IMO of course).
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
djy said:
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
Click to expand...
Click to collapse
This is odd. I flashed my 3 XL also with the April update, patched boot.img with Magisk 20.4 last night. Safety Net failed until I deleted the Safety Patch module. I rebooted and was able to have Google Pay working again (used it this morning to make sure). I'm thankful it's working again. Now I can't update MagiskHide Props Config in Magisk. And if I remember correctly, the quick access to GPay with the power button was a feature drop a while ago.
My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?
Yes
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?
old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?
old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.
Do I need to root my phone before manually updating using the OTA file?
speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No
Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal
From Orange France is 036, from Google store is 037
Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine