david

That's interesting. Did he say whether the one waiting for certification is a full update or incremental? If incremental, then they have to maintain 2 incrementals going forward, 2 certifications, etc, until they go with a full. It also means a different person would need to supply the boot image for each path, since it won't work for someone on the other path.

Sounds right to me. The only thing I would add is that Titanium Backup doesn't work on new apps that use split APKs. Swift Backup might work for those. And if you have any media, you would want to copy off that too. If your backups go to the internal storage, you'll want to copy them off. Swift Backup states that it will wipe backups on the SD card too, if you uninstall it. No idea what happens if you reinstall SB in LOS and it finds a backup on the SD card, so copying off is a good idea there too.

Are the system properties for stock not available to copy, or is this a case of replacement open source code that has different properties than the stock code it replaces? Thanks for explaining which pieces might behave differently. For those people with 2 phones, it would be nice to test signal strength of stock and LOS of wifi at different locations and with different access points. Sounds like such a test isn't needed for cellular, other than if there are system properties involved. Same type of test with GPS, side by side. I could flash one and then the other, but that isn't a

This is what I have been waiting for, is someone who can get it to print in TPU. I would love a TPU cover that has extra bumpers at the corners, with possible air between the inner case and the extra bumper material.

Question about LOS code for the Pro1... With my old phone, when I went to Cyanogenmod from Samsung code, the Camera took poorer images and the GPS didn't work as well as it did before the switch. I believe the camera issues were due to the way things were architected in the past, where too much relied on vendor specific code, and an equivalent open source version of that code didn't exist. Is that true -- should a photo taken with the Pro1 in stock mode end up identical to a photo taken with LOS, assuming the same camera app is used in both cases? Or is there some library in between th

I'm not saying any of this as fact. Just some things some of the experts have shared that I found interesting. They could be wrong, of course. - I believe that they believe the reason this spreads faster than other infectious diseases, is because people *might* be contagious almost immediately after exposure and before they get sick (which is 4+ days after exposure). And, at a minimum, I believe they have shown that people are very contagious even when they are first getting sick (showing symptoms). And by sick, I mean mildly, as well as deadly sick, depending on their immune system.

My preferred method is to try to slide my thumbs between the screen and the bottom half, leading with my thumbnails. Nudging the two halves apart this way will lift up on the screen, while pushing it forward, which will cause it to pop open. It also seems like it puts less stress on the hinge mechanism than trying to force it open by pushing down and forward.

Are you saying you were able have your phone be both a wifi client and wifi hotspot at the same time? I didn't even know that was possible. I thought the radio couldn't function in both capacities simultaneously. It has never allowed that for me on my past phones. I just tried it on a spare Pixel 1 (no sim card) with Android 10, and it acts the same as my older phones -- when the hotspot is turned on, the wifi turns off.

What does official Lineage support mean? Does that mean more developers will be adding things, or does it mean new features will come in from the official Lineage code base? I'm only vaguely familiar with that being another 3rd party ROM. I just googled and it seems it is back on Oreo?? What would the advantage be of that firmware?

I used to have that on my Relay 4G on Cyanogenmod, with pattern unlock.

That was me. I don't know if this will help you, but it is an easy thing to test if you have someone else to send a WhatsApp message to. I just sent someone a 10 second "testing 1 2 3" type message. It crackles at certain points in the audio. However, if I cover the proximity sensor, then the screen goes off and the audio is paused at its current location. After uncovering the sensor, the screen comes back and *usually* I can hit play to resume the audio and the audio crackling is gone. It remains gone for that and other audio messages. What is also interesting is that if it

There is a chance, if the next OTA is a full update instead of an incremental, that it will let you. I don't know if they still check for changes or if they figure since everything will be overwritten, that it doesn't matter.

Thanks for sharing. 😉

Well, the non-black stickers just arrived from Japan. So if anyone else from the USA wants to order the wrong stickers, plan on 15 days delivery time. :-)

Seems to be how Nexus phones work (second answer): https://support.google.com/nexus/forum/AAAANseOu18wlLDZeHVZFU/?hl=iw

I believe that might be the lock screen lock. If you have it set to swipe, then it shows unlocked and if you have it set to a pattern, pin, etc., you get a locked lock. That is the only lock I have when I boot.

It seems like there are different ways for them to do it: 1) Provide another incremental update that will fix 20200304, and re-release the 20200304 and new update. This would mean people who did not take 20200304 would need to do 2 OTA updates. 2) Provide a full update, not an incremental. Everyone can apply this regardless of what they currently have on their phones. 3) They provide a new update that is only for people who have 20200106. Those people would get the keyboard fixes and not have SafetyNet issues. The people who have 20200304 would need to wait for the next O

I think this might just be a matter of measuring MB as a power of 10 versus a power of 2.

Good find. I can't access that twitter link. What is it? It just spins for me.

On a possible related note, can someone else see if their backup to google drive has been affected by this OTA? I could have messed it up with deleting data and cache from some of the google apps and other things I did. I noticed that even though I had "Back up to Google Drive" enabled and an account configured, the "Back up now" button was disabled and it said something about waiting to backup. It *might* have been that it had been too recent since the last backup was done too. Either way, I forced it through some ADB commands and the button came back, but I was just curious if anyone

So now if we can get @rkjnsn to check their bootloader screen to see if secure boot states yes or no, that might help narrow it down. We might all have secure boot "no" no matter what, but if their's has "yes", then that could be the difference here.

That is when I got mine too. It was locked and I unlocked it. I don't get that notification on the Pro1 either. The Pixel 4 XL phones in my household do have that notification during boot. You can compare with @EskeRahn's checks here: https://community.fxtec.com/topic/2849-new-ota-update-stamped-2020-03-04/?do=findComment&comment=46436 I just tried a number of things to see if it would get around the issue on my Pro1 (after disabling the Magisk SafetyPatch module). - Disabled Magisk Hide and re-enabled it. Both without and with a reboot. - Checked all it

So you were in a newer batch of phones where the bootloader was locked when you got it?

At the bottom of the failed result in the SafetyNet Evaluation app, it states: I believe it is listing those as 2 separate options. Difficult to tell with the cryptic grammar. Many of us had unlocked bootloaders before and that didn't cause us to fail SafetyNet. Maybe something changed in google's end of things that makes that no longer acceptable to them? Or... With the second option, some sort of certification code/files wasn't handled right in the preparation of the latest OTA? But that wouldn't account for @rkjnsn passing SafetyNet. I guess the question might b

Good extra data points. Is there anyone who is not rooted and who installed the OTA through the normal OTA process (not by downloading the file and installing it from the SD card), and who is not passing SafetyNet now? Now that I think about it, I guess I'm not sure I know who was running what. Let's see if we can fill in the blanks: - Unlocked, rooted, updated via the normal OTA process = failed safetynet - Never unlocked, never rooted, updated via the normal OTA process = passes safetynet - But does everyone pass safetynet who matches this? - Unlocked, relocked, ne