[Nexus 5X Original Android Development] 3ndymion:
Hi. Everything Adai0 said is absolutely correct. I think the small detail you are asking about is the same issue that I posted about in my long post above, so I'll explain my reasoning. Perhaps it will help to answer what you are asking about. Anybody please correct me if I'm wrong. I've been away for some years & I'm still catching up on all this...

My issue was that I wanted my phone to be seen as a certified device in Google Play. I flashed this ROM as a fresh new build, along with OpenGApps, & Magisk. When I tried the SafetyNet check in Magisk, it said that the basic integrity of the SafetyNet passed, but the ctsProfile failed. With that, Play said that the device is not certified.

After much searching, I found that the fingerprint in the build.prop file is one of the main things being checked for certification, and the security patch date is another one. When I took the build.prop file out from the stock Google ROM, I noticed that the ro.build.fingerprint value is exactly the same as the one in the build.prop file from Lineage. However, I also noticed that the ro.build.version.security_patch value is different. In Google's build.prop file, the ro.build.version.security_patch value matched the date shown in the fingerprint, while the one in the build.prop file from Lineage did not. Initially, I thought that was a problem, but, as Adai0 explained, it is definitely correct.

So, according to my limited knowledge (might not be totally correct), the situation here is this: Google releases their security updates for every vendor to merge into their ROMs. The vendor will merge the security updates into their ROM, & then update the build.prop file with the new info & dates. Before releasing the update to the public, they will go back to Google with their new build.prop file & whatever else so Google can check everything & certify it. Once Google gives them certification, the vendor releases the update to the public. Then, after the person updates their phone, Google Play will check the values in the build.prop file to make sure the ROM has been certified by Google. Since the vendor already went to Google for certification before releasing the update, Play will see the matching values in their certified list, & label the device as certified.

Now, the issue here is that Lineage is a custom ROM built for many different devices. They are not going to Google to have their ROM certified every time they merge in a new security update. So, in the case of our Nexus 5X, the latest (& probably last) official ROM update was from 2018-12-05, the same date as their security update. That can be seen in the official build.prop file as well. Since Google themselves created the ROM, it is already certified. In December, Lineage had these matching values, so when you go to the Play store, it checks the values in the build.prop file, sees the matching values in their certified ROM list, & the device is labeled as certified.

When I came along, the January security update had already been released. Lineage already merged it into their ROM & updated the values in the build.prop file to match. So when I went to the Google Play store, it checked the build.prop values from my phone & saw that the fingerprint & security patch date values do not match anything on their certified ROM list. Google did not release a ROM update in January. Their last ROM update was in 2018-12-05, & that one has a security date with the same date. That's what Play is checking for, & did not find it. So, using a Magisk module, I was able to change the security patch date from the build.prop file to match the last official release. That way, when Play checks the build.prop file values from my phone, they see the same fingerprint & security patch date as the build.prop values that they have on their certified ROM list. Therefore, my phone is now labeled as certified.

So, to answer your question "Will it be resolved?", I believe the answer is no. Since Lineage is a custom ROM that is being built for many different devices, it can't really be brought to Google for official certification. That is something that we end users will have to take care of on our own, if we care about such things as Play certification. In this new day & age of Google locking things down extra hard, Magisk seems to be the answer. As long as any person, using any device from any manufacturer, can manage to get their ROM's build.prop values to match something that Google has on their officially certified ROM list, then they should be able to have their device listed as certified. Of course, there are other things involved too, such as hiding root user permissions if you have them, which is why I mention Magisk.

Again, anybody please correct me if I'm wrong on any of this.

Well I hope this helps a little. :angel: