Vendor Security Patch Question: - OnePlus 6T Questions & Answers

I am very confused about the Vendor Security patch for Open Beta 17. I am currently on a Custom ROM and Custom Kernel and when I go to settings>About Phone>Android 9, I get a detail overview of the phone and one of those details is Vendor Security Patch Level and for me it states it's September 5th 2018 while Android Security Patch is September 5th 2019.
My question to those of you reading this is, What should Open Beta 17's Vendor Patch be on ? I find it incredibly hard to believe that the Vendor level hasn't been updated since September 5th of 2018. Please send me a screenshot of your current Vendor Security patch or at the very least tell what the date for Open Beta 17's Vendor Security Patch Level should be. I went ahead and looked with root explorer at the Vendor build.prop and it says the build date of the Vendor is August 30th of 2019 while the security level is September 5th of 2018. To me, this seems like a mistake because I don't think the Vendor Security should be a WHOLE YEAR BEHIND the Android Security Patch.
I know it shouldn't matter and I'm not a big "Security freak" but I like consistency and the screenshot below is my problem. I was told it was OnePlus's fault and there isn't anything we can do about that.
Down below I am leaving two screenshots, One is of the settings>About Phone and the other is the Vendor build.prop.
I would appreciate it if someone told me this is correct and provided me a screenshot or to let me know if it's a mistake done by OnePlus and don't worry about it .Thanks in advance for anyone who replies helping me out with this. Greatly appreciate it.

As you said:
a mistake done by OnePlus and don't worry about it
Click to expand...
Click to collapse
That prop is just a string, OnePlus/custom rom developer can make changes in /vendor daily, but if they don't change that text, it will continue to show an old date, it can also happen in the opposite way.

onliner said:
As you said:
That prop is just a string, OnePlus/custom rom developer can make changes in /vendor daily, but if they don't change that text, it will continue to show an old date, it can also happen in the opposite way.
Click to expand...
Click to collapse
So do I just change the date or is it really September 5th 2018. The build date of the Vendor is August 30th 2019 but the security is September 5th 2018. Should I just change it to August 30th 2019 or leave it alone ?
Edit: I can change it to August 30th 2019 but I don't want it to be false.

Sadistic_Loser said:
So do I just change the date or is it really September 5th 2018. The build date of the Vendor is August 30th 2019 but the security is September 5th 2018. Should I just change it to August 30th 2019 or leave it alone ?
Edit: I can change it to August 30th 2019 but I don't want it to be false.
Click to expand...
Click to collapse
Change it? That wouldn't change anything, it's just text.

onliner said:
Change it? That wouldn't change anything, it's just text.
Click to expand...
Click to collapse
Well it changes the date of the Vendor Security Patch and if the build date for the Vendor is August 30th then maybe they forgot to change the Vendor Date. I don't know how the vendor partition works but it's literally a whole year apart from the Android Security Patch and it doesn't make any sense.
Here the after result of changing the date. I have no way of knowing if the security part of the vendor partition is August 30th 2019 but I've seen other people show me screenshots of the vendor higher than September 5th 2018.
What version of OOS are you on and what is your vendor date, and if you're on a Custom ROM then could you show me a screenshot of the date your vendor is on ?

Well I looked on my device, currently T-Mobile Stock Firmware locked. I dont have the ability to see the Vender partition info like RR shows you.
However, as long as you flash the latest beta and or stable, you will have the latest update for the vendor partition.
I wouldn't worry about the text of the matter. Like the other guy was saying before me. The edits you made don't change anything except what is displayed on that one specific screen. It doesn't change anything in the vendor partition.

Scott said:
Well I looked on my device, currently T-Mobile Stock Firmware locked. I dont have the ability to see the Vender partition info like RR shows you.
However, as long as you flash the latest beta and or stable, you will have the latest update for the vendor partition.
I wouldn't worry about the text of the matter. Like the other guy was saying before me. The edits you made don't change anything except what is displayed on that one specific screen. It doesn't change anything in the vendor partition.
Click to expand...
Click to collapse
Well first off I just want to thank you and the other person as well for replying, seems like anytime I ask this kind of question it gets ignored and probably for a good reason. I do know that changing the text will only change what is displayed but my confusion is that I under the impression they forgot to update the date of the Vendor Security Patch Level. It is the latest Beta (Technically 16 is since they apparently pulled Beta 17 away because of an issue.) and so I have no reason to care about it but it just throws me off because it says September 5th 2018. I'll leave it be and wait for Android 10 firmware to release next month (Hopefully).

Related

Best ROM for non-techsavvy individual?

I passed down my Nexus 10 to my father a few months ago, and the current ROM has got some corruption and so I'd like to flash something else.
He's essentially not techsavvy at all. I'm just looking for something rather stable for the moment that's moderately up to date for security reasons.
Once LineageOS starts building snapshots for the Nexus 10 I'll regularly update that with OTAs.
Any suggestions?
If you are ging for security a nougat rom is the best since it has the january security Update. But if you need a fully working rom you should Go for marshmallow. In this case the Last cm Release is fine. But it has only the december security Update in it.
XxM4tzexX said:
If you are ging for security a nougat rom is the best since it has the january security Update. But if you need a fully working rom you should Go for marshmallow. In this case the Last cm Release is fine. But it has only the december security Update in it.
Click to expand...
Click to collapse
Any idea where official cm13 is hosted/archived? I'll take your suggestion and install the last stable build of it. Then update his tablet to lineage once their stable builds start.

How can I update Android security level on a custom ROM?

Hi, I have a Nexus 6P with a "MegaPixel" rom running on v7.1.1 and the security patch is at Dec 5, 2016
I just got a notification of an update. I tapped install and it just restarted the phone to recovery (TWRP). I rebooted back to system and the notification disappeared.
I tried to check for update but it showed nothing, and the Security patch is still at Dec 5, 2016.
The kernel I am currently running is ElementalX kernel. And yes, it updated to support Feb 2017 security patch.
On another topic, my battery life is ****, and this is the main reason I changed ROM and kernel but it didn't help by much(I am talking about 2.5 screen on time with 50%-70% brightness)
Thanks from advanced
Hi... Just look in the thread of MegaPixel... But it seems like last update was released in December 2016. You can't get last security patch if the dev doesn't update his ROM. You'll have to wait for an update or switch to another one.
As for battery life. It really depends on how you use use your phone. There are a lot of threads which aim to help with battery. I invite you to start reading the forum a little bit, I'm sure you'll find some tweaks to improve it.

Latest security patch is Jan 2017?

Security patches for both my stock Pro3 and S3, US versions, are woefully out of date.
Any update in the works? My old Note 4's are still getting them!
Latest Chinese 26s' security patch is still October 2016...
voidcomp said:
Security patches for both my stock Pro3 and S3, US versions, are woefully out of date.
Any update in the works? My old Note 4's are still getting them!
Click to expand...
Click to collapse
LeEco is going through tough times, and their US staff was affected. Vizio is demanding money, they sold their US HQ, etc. I don't think fast updates is a priority for them right now, especially if they're in debt.
http://www.androidpolice.com/tags/leeco/
The latest update for the US variant is 21s, which includes the January patch. If you want the July patch you'll have to use a custom ROM, because no one knows what the future holds for LeEco's US branch.
Ace42 said:
LeEco is going through tough times, and their US staff was affected. Vizio is demanding money, they sold their US HQ, etc. I don't think fast updates is a priority for them right now, especially if they're in debt.
http://www.androidpolice.com/tags/leeco/
The latest update for the US variant is 21s, which includes the January patch. If you want the July patch you'll have to use a custom ROM, because no one knows what the future holds for LeEco's US branch.
Click to expand...
Click to collapse
So a custom ROM would allow me to somehow manually patch a security update or the ROM developer releases updates which include the patch?
Custom rom has the latest security patch
Sent from my LEX727 using XDA-Developers Legacy app

Need help.

Hi i'm minicm.
Hi guys, I have a question.
There is still some rom that is 6.0 or 7.0 (not 7.1) that has the security patch before March 2017, probably you ask yourself What for? It's because from the patch of March the simulated Locations no longer work and it helps me a lot.
Someone still has one of these roms with patch February 2017 or earlier as a LineageOs 14 (7.0) Cm (6.0) or some other that meets these requirements although I already pored Omnirom, Pac-rom and did not convince me much.
If you still have them, could you host them and pass them to me? Please and thank you.
minicm94123 said:
Hi i'm minicm.
Hi guys, I have a question.
There is still some rom that is 6.0 or 7.0 (not 7.1) that has the security patch before March 2017, probably you ask yourself What for? It's because from the patch of March the simulated Locations no longer work and it helps me a lot.
Someone still has one of these roms with patch February 2017 or earlier as a LineageOs 14 (7.0) Cm (6.0) or some other that meets these requirements although I already pored Omnirom, Pac-rom and did not convince me much.
If you still have them, could you host them and pass them to me? Please and thank you.
Click to expand...
Click to collapse
Check my CyanogenMod 13, it has security patches from December 2016.
XTutorials said:
Check my CyanogenMod 13, it has security patches from December 2016.
Click to expand...
Click to collapse
HAHA,lol thanks, i will try it, and there's no a LOS14.0 with those security patchs?
I'm going to try the Cm13.
minicm94123 said:
HAHA,lol thanks, i will try it, and there's no a LOS14.0 with those security patchs?
I'm going to try the Cm13.
Click to expand...
Click to collapse
No, there is no los 14.0 with old security patches.

Strange: System is up to date - Android 8.1.0!

I realized that my A1 did not ask me to update for a couple of weeks, maybe even 2 months.
As was busy, it did not bother me ...
When checking for updates now, I see:
Your System is up to date
Android 8.1.0,
Security Patch level: 5 January 2019
Any I idea why I am no longer offered to update?
Tiemichael said:
I realized that my A1 did not ask me to update for a couple of weeks, maybe even 2 months.
As was busy, it did not bother me ...
When checking for updates now, I see:
Your System is up to date
Android 8.1.0,
Security Patch level: 5 January 2019
Any I idea why I am no longer offered to update?
Click to expand...
Click to collapse
It could be because of any modifications made to your device, however you can still flash new Android 9 (Pie) with Miflash. Many people also say it is better to stay on Oreo because of stability and camera quality.
Another solution to get Pie update is to use VPN and clear data of some applications (I don't remember which ones).
That's the reason (cmaera, xposed ..) I decided to stay with Android 8.1.
Besides Magisk there are no modifications ...
Thanks!
That's wierd. The last Oreo version for Mi A1 is on November security patch.
Well, in any case, would be enough with cleaning "Google Play Services' cache.
All times I got a delay in software updates from Xiaomi for MiA1, this solved the problem (happened to me twice).
Just to be clear, this isn't related to Google Play apps.
KaaMyA said:
Well, in any case, would be enough with cleaning "Google Play Services' cache.
All times I got a delay in software updates from Xiaomi for MiA1, this solved the problem (happened to me twice).
Just to be clear, this isn't related to Google Play apps.
Click to expand...
Click to collapse
Clearing the Google Play Services cache did not change anything
Thanks!
Tiemichael said:
Clearing the Google Play Services cache did not change anything
Thanks!
Click to expand...
Click to collapse
Did you restarted device after that?
You remind me that I had to reboot after cleaning GP Services, then searched for update manually. I forgot to mention that, my fault.
If that doesn't solve your problem, I feel this is related to a completely different reason. Just in case, check time and date/location to be set by provider instead of manual.
However, the procedure I recommended to you usually works and I found it in another thread around here, perhaps there are other methods to reach software update correctly.
KaaMyA said:
Did you restarted device after that?
You remind me that I had to reboot after cleaning GP Services, then searched for update manually. I forgot to mention that, my fault.
If that doesn't solve your problem, I feel this is related to a completely different reason. Just in case, check time and date/location to be set by provider instead of manual.
However, the procedure I recommended to you usually works and I found it in another thread around here, perhaps there are other methods to reach software update correctly.
Click to expand...
Click to collapse
Thanks!
Even GP-Services Clear Data and reboot does not change anything!
In general the phone is working fine ...
After all you have done I have to ask you this: are you sure you are holding a Mi A1? Because the January 2019 security patch comes with Pie not Oreo, the last patch for Oreo is on November 5 2018.
Never_Sm1le said:
After all you have done I have to ask you this: are you sure you are holding a Mi A1? Because the January 2019 security patch comes with Pie not Oreo, the last patch for Oreo is on November 5 2018.
Click to expand...
Click to collapse
Yes! I am talking about my Xiaomi A1.
The Build Number is: OPM1.171019.026.V9.6.8.0.ODHMIFE and
the Android Security Patch level: 5 January 2019
I am aware that it does not match ...
The last update I did was on Jan 10th, using XiaomiFlash.
The image I used was: tissot_images_V9.6.8.0.ODHMIFE_20181031.0000.00_8.0_9ea450fe98
Tiemichael said:
Yes! I am talking about my Xiaomi A1.
The Build Number is: OPM1.171019.026.V9.6.8.0.ODHMIFE and
the Android Security Patch level: 5 January 2019
I am aware that it does not match ...
The last update I did was on Jan 10th, using XiaomiFlash.
The image I used was: tissot_images_V9.6.8.0.ODHMIFE_20181031.0000.00_8.0_9ea450fe98
Click to expand...
Click to collapse
Whoah, that's strange. In your case I would make a clean flash of stock oreo ROM and it should fix it.
Tiemichael said:
Yes! I am talking about my Xiaomi A1.
The Build Number is: OPM1.171019.026.V9.6.8.0.ODHMIFE and
the Android Security Patch level: 5 January 2019
I am aware that it does not match ...
The last update I did was on Jan 10th, using XiaomiFlash.
The image I used was: tissot_images_V9.6.8.0.ODHMIFE_20181031.0000.00_8.0_9ea450fe98
Click to expand...
Click to collapse
Maybe something has altered the security patch date and cause the update engine to go haywire, because that build number is definitely from the November security patch.
Agreed, a clean flash with should fix it .
Not sure if Oreo or Pie is better for me (camera, xposed, tasker ...)
Still it remains a mystery what happened ...
Tiemichael said:
Agreed, a clean flash with should fix it .
Not sure if Oreo or Pie is better for me (camera, xposed, tasker ...)
Still it remains a mystery what happened ...
Click to expand...
Click to collapse
If youre talking about stock experience - Oreo is better, but I tried Gcam on stock Pie and got incredible results. Also installed Magisk with one module which enables 1080p 60 FPS.
Which camera for PIE are you using? Does it support all the 3 lenses?
Currently I am using https://f.celsoazevedo.com/file/cfiles/gcm1/GoogleCamera_5.2.025-Final_fu24-18d1.apk. which supports all 3 ...

Resources