• What is the history of Galaxy S-series & Pixel full support?

    From Maria Sophia@[email protected] to comp.mobile.android on Fri Apr 17 13:09:32 2026
    From Newsgroup: comp.mobile.android

    This was posted to the Apple newsgroup way back in March because the Apple posters wanted to compare Apple's full support to that of Pixel/Galaxy S.

    Newsgroups: misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system
    Subject: Re: [Correction] Apple's iOS full support is exactly as long as expected.
    Date: Thu, 26 Mar 2026 02:18:24 -0400
    Message-ID: <10q2j3g$2v5d$[email protected]>

    Please correct or improve where I err or omit as this type of data is very
    hard to obtain in one place on the Internet so it's a lot of work to get.

    (verbatim)

    Here's my first pass at the data that Tom Elam & Chris just asked me for. (Please check it out to see if I made any errors as this is my 1st look.)

    1. Samsung Galaxy S (The Original)
    Shipped for retail sale on June 4, 2010.
    Last Full-Parity release: Android 2.3.6 in Jan 2012.
    585 days / 365 = 1.60 years for full support.

    2. Samsung Galaxy S II
    Shipped for retail sale on May 2, 2011.
    Last Full-Parity release: Android 4.1.2 in April 2013.
    708 days / 365 = 1.94 years for full support.

    3. Samsung Galaxy S III
    Shipped for retail sale on May 29, 2012.
    Last Full-Parity release: Android 4.3 in Dec 2013.
    560 days / 365 = 1.53 years for full support.

    4. Samsung Galaxy S4
    Shipped for retail sale on April 27, 2013.
    Last Full-Parity release: Android 5.0.1 in April 2015.
    730 days / 365 = 2.00 years for full support.

    5. Samsung Galaxy S5
    Shipped for retail sale on April 11, 2014.
    Last Full-Parity release: Android 6.0.1 in April 2016.
    731 days / 365 = 2.00 years for full support.

    6. Samsung Galaxy S6 / S6 Edge
    Shipped for retail sale on April 10, 2015.
    Last Full-Parity release: Android 7.0 in Feb 2017.
    672 days / 365 = 1.84 years for full support.

    7. Samsung Galaxy S7 / S7 Edge
    Shipped for retail sale on March 11, 2016.
    Last Full-Parity release: Android 8.0 in May 2018.
    791 days / 365 = 2.17 years for full support.

    8. Samsung Galaxy S8 / S8+
    Shipped for retail sale on April 21, 2017.
    Last Full-Parity release: Android 9.0 in Feb 2019.
    651 days / 365 = 1.78 years for full support.

    9. Samsung Galaxy S9 / S9+
    Shipped for retail sale on March 11, 2018.
    Last Full-Parity release: Android 10 in Jan 2020.
    671 days / 365 = 1.84 years for full support.

    10. Samsung Galaxy S10 / S10+ / S10e
    Shipped for retail sale on March 8, 2019.
    Last Full-Parity release: Android 12 in Dec 2021.
    1,018 days / 365 = 2.79 years for full support.

    11. Samsung Galaxy S20 Series
    Shipped for retail sale on March 6, 2020.
    Last Full-Parity release: Android 13 in Nov 2022.
    999 days / 365 = 2.74 years for full support.

    12. Samsung Galaxy S21 / S21+ / S21 Ultra
    Shipped for retail sale on Jan 29, 2021.
    Last Full-Parity release: Jan 2026 Security Update.
    1,831 days / 365 = 5.02 years for full support.
    (Note: Completely abandoned by Samsung on Feb 3, 2026).

    13. Samsung Galaxy S22 / S22+ / S22 Ultra
    Shipped for retail sale on Feb 25, 2022.
    Lost Full-Parity: Feb 3, 2026.
    1,439 days / 365 = 3.94 years for full support (now quarterly).

    If the data above is correct, the average Samsung main competitor to the
    iPhone between 2010 and 2020 appears to have 2.48 years of FULL support.

    That 2.48 years sucks compared to the iOS full support of 4.89 years.
    But please check my math as I'm trying to apply the same rules to Samsung's iPhone competitive phones as I did to the iPhone itse4lf (Apple's rules).
    a. Either a phone is fully patched with all known CVE's,
    b. Or it's not.

    Since Tom Elam & Chris asked for the Pixel, here's my first pass at that.

    1. Google Pixel / Pixel XL
    Shipped for retail sale on Oct 20, 2016.
    Last Full-Parity release: Dec 2019 Security Patch.
    1,137 days / 365 = 3.12 years for full support.

    2. Google Pixel 2 / 2 XL
    Shipped for retail sale on Oct 19, 2017.
    Last Full-Parity release: Dec 2020 Security Patch.
    1,168 days / 365 = 3.20 years for full support.

    3. Google Pixel 3 / 3 XL
    Shipped for retail sale on Oct 18, 2018.
    Last Full-Parity release: Feb 2022 Security Patch.
    1,208 days / 365 = 3.31 years for full support.

    4. Google Pixel 4 / 4 XL
    Shipped for retail sale on Oct 24, 2019.
    Last Full-Parity release: Oct 2022 Security Patch.
    1,096 days / 365 = 3.00 years for full support.

    5. Google Pixel 5
    Shipped for retail sale on Oct 15, 2020.
    Last Full-Parity release: Feb 2024 Security Patch.
    1,213 days / 365 = 3.32 years for full support.

    6. Google Pixel 6 / 6 Pro
    Shipped for retail sale on Oct 28, 2021.
    Lost Full-Parity: July 2025 (Demoted to Quarterly Updates).
    1,341 days / 365 = 3.67 years for full support.
    (Note: Currently missing 66 March 2026 CVE fixes).

    7. Google Pixel 7 / 7 Pro
    Shipped for retail sale on Oct 13, 2022.
    Lost Full-Parity: Feb 2026 (Demoted to Quarterly Updates).
    1,208 days / 365 = 3.31 years for full support.
    (Note: Currently missing 66 March 2026 CVE fixes).

    Did I miss any?

    If the data above is correct, the average Samsung main competitor to the
    iPhone between 2016 and 2022 appears to have 3.28 years of FULL support.

    Both Tom Elam and Chris (and everyone else) should note that I don't
    care what the answer is, since all I care about are the facts.

    It doesn't matter to me if Apple comes out ahead or not.
    I just want to know what the answer is.

    Apparently, all iPhones averaged 4.89 years of FULL support.
    All Samsung iPhone competitors averaged much less, at 2.48 years.
    The Pixel competition to the iPhone was in the middle, at 3.28 years.

    Please remember I'm nothing like most of you who post to the Apple
    newsgroups in that I don't defend any company to the death, no matter what.

    I simply care about knowing what the correct answer is.
    My assessment?
    a. Apple full iOS support used to be much better than Android was.
    b. But moving forward from today, Apple full iOS support is not.
    --
    I only care about the facts. I don't defend any OEM mothership.
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From AJL@[email protected] to comp.mobile.android on Fri Apr 17 21:32:28 2026
    From Newsgroup: comp.mobile.android

    On 4/17/26 12:09 PM, Maria Sophia wrote:

    Newsgroups: misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system

    I'm posting this with my Chromebook so this reply will likely only be seen
    in the Android group as this PhoNews newsreader has a
    post-to-one-group-only bug (though some might call it a feature since it
    does avoid the phone (brand) wars)...

    Please correct or improve where I err or omit as this type of data is very >hard to obtain in one place on the Internet so it's a lot of work to get.

    10. Samsung Galaxy S10 / S10+ / S10e

    Mine is a Samsung Galaxy S10+ SM-G975U.

    Shipped for retail sale on March 8, 2019.

    I bought mine in September 2019

    Last Full-Parity release: Android 12

    Mine is on Android 12.

    in Dec 2021.

    My phone says its last update was June 1, 2024 at 7:29AM. In Software info
    it says "You're all set!" with a green checkmark. Further "Your phone has
    been updated to the latest software version." When I push the "System
    update" button it rotates for several seconds then says "Your SAMSUNG
    SM-G975U is up to date. No update is necessary at this time." And another
    green arrow pops up. Everything must be great, huh.

    I'm kinda surprised it doesn't say: "Hey dip**** your phone is really old
    and out of date and needs to be replaced! They might actually sell more
    phones that way.

    1,018 days / 365 = 2.79 years for full support.

    But then there's good old Google. Last updated my phone last month with a
    bunch of what's new stuff to try. Love that Google...

    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Frank Slootweg@[email protected] to comp.mobile.android on Sat Apr 18 15:27:39 2026
    From Newsgroup: comp.mobile.android

    AJL <[email protected]> wrote:
    On 4/17/26 12:09 PM, Maria Sophia wrote:

    Newsgroups: misc.phone.mobile.iphone,comp.sys.mac.advocacy,comp.sys.mac.system

    I'm posting this with my Chromebook so this reply will likely only be seen
    in the Android group as this PhoNews newsreader has a
    post-to-one-group-only bug (though some might call it a feature since it
    does avoid the phone (brand) wars)...

    Please correct or improve where I err or omit as this type of data is very >hard to obtain in one place on the Internet so it's a lot of work to get.

    10. Samsung Galaxy S10 / S10+ / S10e

    Mine is a Samsung Galaxy S10+ SM-G975U.

    Shipped for retail sale on March 8, 2019.

    I bought mine in September 2019

    Last Full-Parity release: Android 12

    Mine is on Android 12.

    in Dec 2021.

    My phone says its last update was June 1, 2024 at 7:29AM. In Software info
    it says "You're all set!" with a green checkmark. Further "Your phone has
    been updated to the latest software version." When I push the "System
    update" button it rotates for several seconds then says "Your SAMSUNG
    SM-G975U is up to date. No update is necessary at this time." And another
    green arrow pops up. Everything must be great, huh.

    Please go to Settings -> About phone (at the bottom) -> Software
    Information -> Android security patch level (at the bottom)

    Report the date listed below 'Android security patch level'.

    Anything else is irrelevant, because it might just be the date of some 'Google Play system update', which, as you mention below, could be as
    new as February/March of this year. (Which is the case for our Samsung
    Galaxy A51 phones (Android 13).)

    I'm kinda surprised it doesn't say: "Hey dip**** your phone is really old
    and out of date and needs to be replaced! They might actually sell more
    phones that way.

    1,018 days / 365 = 2.79 years for full support.

    But then there's good old Google. Last updated my phone last month with a
    bunch of what's new stuff to try. Love that Google...
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From AJL@[email protected] to comp.mobile.android on Sat Apr 18 16:35:24 2026
    From Newsgroup: comp.mobile.android

    On 4/18/26 8:27 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:

    My phone says "You're all set!" with a green checkmark. Further "Your phone has
    been updated to the latest software version." When I push the "System
    update" button it rotates for several seconds then says "Your SAMSUNG
    SM-G975U is up to date. No update is necessary at this time." And another >> green arrow pops up. Everything must be great, huh.

    I was trying to be sarcastic about the Samsung my phone being up to date
    wording here. Perhaps lost in translation?

    Please go to Settings -> About phone (at the bottom) -> Software
    Information -> Android security patch level (at the bottom)

    Report the date listed below 'Android security patch level'.

    There's no 'Android security patch level' there. There is an 'SE for Android
    status' though and its entry is quoted below. Not sure what enforcing means
    but the date is likely what you're looking for?

    Enforcing
    SEPF_SM-G975U_12_0001
    Thu May 09 16:27:08 2004

    Anything else is irrelevant, because it might just be the date of some
    'Google Play system update', which, as you mention below, could be as
    new as February/March of this year. (Which is the case for our Samsung
    Galaxy A51 phones (Android 13).)

    Yup. 4 lines up is 'Google Play system update' which says March 1, 2026.

    I'm kinda surprised it doesn't say: "Hey dip**** your phone is really old
    and out of date and needs to be replaced! They might actually sell more
    phones that way.

    But then there's good old Google. Last updated my phone last month with a
    bunch of what's new stuff to try. Love that Google...


    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Frank Slootweg@[email protected] to comp.mobile.android on Sat Apr 18 18:09:14 2026
    From Newsgroup: comp.mobile.android

    AJL <[email protected]> wrote:
    On 4/18/26 8:27 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:

    My phone says "You're all set!" with a green checkmark. Further "Your phone has
    been updated to the latest software version." When I push the "System
    update" button it rotates for several seconds then says "Your SAMSUNG
    SM-G975U is up to date. No update is necessary at this time." And another >> green arrow pops up. Everything must be great, huh.

    I was trying to be sarcastic about the Samsung my phone being up to date
    wording here. Perhaps lost in translation?

    Yes, I got that (sarcastic) bit, but I was referring to the date you mentioned in your (now snipped) part:

    <you>
    My phone says its last update was June 1, 2024 at 7:29AM.
    </you>

    Please go to Settings -> About phone (at the bottom) -> Software
    Information -> Android security patch level (at the bottom)

    Report the date listed below 'Android security patch level'.

    There's no 'Android security patch level' there. There is an 'SE for Android
    status' though and its entry is quoted below. Not sure what enforcing means
    but the date is likely what you're looking for?

    Enforcing
    SEPF_SM-G975U_12_0001
    Thu May 09 16:27:08 2004

    [I assume that's 2024. 2004 is a tad old! :-)]

    Strange that there is no 'Android security patch level' there. AFAIR,
    it has been there at least since Android 10.

    Anyway, the SE date is normally close to the 'Android security patch
    level' date. The 'Kernel version' date is also close to that. On my
    current A56, they're only off by 1 day.

    Still strange that there's nearly a month between your SE date and
    your "My phone says ..." date.

    Anything else is irrelevant, because it might just be the date of some
    'Google Play system update', which, as you mention below, could be as
    new as February/March of this year. (Which is the case for our Samsung >Galaxy A51 phones (Android 13).)

    Yup. 4 lines up is 'Google Play system update' which says March 1, 2026.

    Good! Way to go, Google! :-)

    I'm kinda surprised it doesn't say: "Hey dip**** your phone is really old >> and out of date and needs to be replaced! They might actually sell more >> phones that way.
    ^M
    But then there's good old Google. Last updated my phone last month with a >> bunch of what's new stuff to try. Love that Google...
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From AJL@[email protected] to comp.mobile.android on Sat Apr 18 19:21:53 2026
    From Newsgroup: comp.mobile.android

    On 4/18/26 11:09 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:
    On 4/18/26 8:27 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:

    My phone says "You're all set!" with a green checkmark. Further "Your phone has
    been updated to the latest software version." When I push the "System
    update" button it rotates for several seconds then says "Your SAMSUNG
    SM-G975U is up to date. No update is necessary at this time." And another
    green arrow pops up. Everything must be great, huh.

    I was trying to be sarcastic about the Samsung my phone being up to date
    wording here. Perhaps lost in translation?

    Yes, I got that (sarcastic) bit, but I was referring to the date you
    mentioned in your (now snipped) part:

    Sorry, I forgot snipping pisses you off...

    <you>
    My phone says its last update was June 1, 2024 at 7:29AM.
    </you>

    Correct. My phone: Settings/Software update/Applied: "June 1, 2024 at 7:29
    AM"

    Please go to Settings -> About phone (at the bottom) -> Software
    Information -> Android security patch level (at the bottom)

    Report the date listed below 'Android security patch level'.

    There's no 'Android security patch level' there. There is an 'SE for Android >> status' though and its entry is quoted below. Not sure what enforcing means >> but the date is likely what you're looking for?

    Enforcing
    SEPF_SM-G975U_12_0001
    Thu May 09 16:27:08 2004

    [I assume that's 2024. 2004 is a tad old! :-)]

    Yup. A Typo (finger-O?). Should be 2024.

    Strange that there is no 'Android security patch level' there. AFAIR,
    it has been there at least since Android 10.

    Actually there is. Turns out my scrolling finger was disconnected earlier. Settings/Software info/Android security patch level: March 1, 2023

    Anyway, the SE date is normally close to the 'Android security patch
    level' date. The 'Kernel version' date is also close to that. On my
    current A56, they're only off by 1 day.

    Still strange that there's nearly a month between your SE date and
    your "My phone says ..." date.

    Anything else is irrelevant, because it might just be the date of some
    'Google Play system update', which, as you mention below, could be as
    new as February/March of this year. (Which is the case for our Samsung
    Galaxy A51 phones (Android 13).)

    Yup. 4 lines up is 'Google Play system update' which says March 1, 2026.

    Good! Way to go, Google! :-)

    I'm kinda surprised it doesn't say: "Hey dip**** your phone is really old >> >> and out of date and needs to be replaced! They might actually sell more >> >> phones that way.
    ^M
    But then there's good old Google. Last updated my phone last month with a >> >> bunch of what's new stuff to try. Love that Google...


    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Theo@[email protected] to comp.mobile.android on Sat Apr 18 20:34:06 2026
    From Newsgroup: comp.mobile.android

    AJL <[email protected]> wrote:
    There's no 'Android security patch level' there. There is an 'SE for Android
    status' though and its entry is quoted below. Not sure what enforcing means
    but the date is likely what you're looking for?

    Enforcing
    SEPF_SM-G975U_12_0001
    Thu May 09 16:27:08 2004

    I think this relates to the firmware of the Secure Enclave. 'Enforcing' perhaps means that the enclave is in full operation, whereas there may be
    some kind of 'relaxed' or developer mode where, eg, it doesn't do some
    checks.

    Theo
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Frank Slootweg@[email protected] to comp.mobile.android on Sat Apr 18 20:15:17 2026
    From Newsgroup: comp.mobile.android

    AJL <[email protected]> wrote:
    On 4/18/26 11:09 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:
    On 4/18/26 8:27 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:

    My phone says "You're all set!" with a green checkmark. Further "Your phone has
    been updated to the latest software version." When I push the "System >> >> update" button it rotates for several seconds then says "Your SAMSUNG >> >> SM-G975U is up to date. No update is necessary at this time." And another
    green arrow pops up. Everything must be great, huh.

    I was trying to be sarcastic about the Samsung my phone being up to date >> wording here. Perhaps lost in translation?

    Yes, I got that (sarcastic) bit, but I was referring to the date you
    mentioned in your (now snipped) part:

    Sorry, I forgot snipping pisses you off...

    Snipping relevant stuff indeed annoys me, but in this case your
    snipping made *you* draw the wrong conclusion, so there you go! :-)

    <you>
    My phone says its last update was June 1, 2024 at 7:29AM.
    </you>

    Correct. My phone: Settings/Software update/Applied: "June 1, 2024 at 7:29
    AM"

    [...]

    Strange that there is no 'Android security patch level' there. AFAIR,
    it has been there at least since Android 10.

    Actually there is. Turns out my scrolling finger was disconnected earlier. Settings/Software info/Android security patch level: March 1, 2023

    Strange that there was no security patch between March 1, 2023 and

    [Rewind/repeat:]

    Correct. My phone: Settings/Software update/Applied: "June 1, 2024 at 7:29
    AM"

    [End repeat.]

    So a security patch dated March 1, 2023 and then 'something' was
    'Applied' on June 1, 2024.

    Normally every (Android system) 'Software update' includes a security
    patch.

    [...]
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From AJL@[email protected] to comp.mobile.android on Sat Apr 18 21:07:51 2026
    From Newsgroup: comp.mobile.android

    On 4/18/26 1:15 PM, Frank Slootweg wrote:

    yoursnipping made *you* draw the wrong conclusion

    Nope. My conclusion for several years now has been that my 6 year old
    phone's security is very outdated. I certainly didn't need to rummage
    around in various parts of settings to figure that out...

    BTW how did I do with my snipping this time... ;)


    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Maria Sophia@[email protected] to comp.mobile.android on Sat Apr 18 19:37:12 2026
    From Newsgroup: comp.mobile.android

    Theo wrote:
    AJL <[email protected]> wrote:
    There's no 'Android security patch level' there. There is an 'SE for Android >> status' though and its entry is quoted below. Not sure what enforcing means >> but the date is likely what you're looking for?

    Enforcing
    SEPF_SM-G975U_12_0001
    Thu May 09 16:27:08 2004

    I think this relates to the firmware of the Secure Enclave. 'Enforcing' perhaps means that the enclave is in full operation, whereas there may be some kind of 'relaxed' or developer mode where, eg, it doesn't do some checks.

    Dunno if non-Samsung devices have this, but at least Samsung adds SEPF
    (Samsung Enhanced Policy Files) on top of the Android base SELinux.

    Never thought about "enforcing" prior, but a google search implies
    Enforcing means that SELinux (Security-Enhanced Linux) is actively
    enforcing security rules during which time if an app or process tries to do something not allowed, the system blocks it.

    SEPF_SM-G975U_12_0001 is apparently Samsung's security policy file for your AJL's specific model, presumably an (SM-G975U = Galaxy S10+), Android 12
    (but see below about the Android 12 ambiguity).

    Date is apparently the build date of that specific security policy file.

    For the record, my Galaxy A32-5G (which is no longer on full support) says:
    SE for Android status
    Enforcing
    SEPF_SM-A326U_12_0001
    Wed Feb 19 18:52:36 2025

    Indicating, similarly that SELinux is active and enforcing rules, not just logging them so any app or process that tries to do something outside the allowed security policy gets blocked.

    Apparently, the opposite would be "permissive", as far as I can tell.

    In my case, the version of the security file is
    a. SEPF meaning Samsung Enhanced Policy File
    b. SM-A326U indicating my device model (Galaxy A32 5G, U.S. variant)
    c. 12 oddly indicating Android 12 but I'm really on Android 13
    d. 0001 is apparently the policy revision number
    e. Wed Feb 19 18:52:36 2025 is the build date of the security policy file

    Note that apparently, Samsung did not update the SELinux policy file name
    when upgrading my device from Android 12 to Android 13.

    We could cover this one topic forever with the amount of data on it I see,
    so I'll stop there, but it's not Secure Enclave so much as Secure Enhanced.
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From AJL@[email protected] to comp.mobile.android on Sun Apr 19 05:33:34 2026
    From Newsgroup: comp.mobile.android

    On 4/18/26 6:37 PM, Maria Sophia wrote:
    Theo wrote:
    AJL <[email protected]> wrote:
    There's no 'Android security patch level' there. There is an 'SE for Android
    status' though and its entry is quoted below. Not sure what enforcing means
    but the date is likely what you're looking for?

    Enforcing
    SEPF_SM-G975U_12_0001
    Thu May 09 16:27:08 2004

    I think this relates to the firmware of the Secure Enclave. 'Enforcing'
    perhaps means that the enclave is in full operation, whereas there may be
    some kind of 'relaxed' or developer mode where, eg, it doesn't do some
    checks.

    Dunno if non-Samsung devices have this, but at least Samsung adds SEPF >(Samsung Enhanced Policy Files) on top of the Android base SELinux.

    Never thought about "enforcing" prior, but a google search implies
    Enforcing means that SELinux (Security-Enhanced Linux) is actively
    enforcing security rules during which time if an app or process tries to do >something not allowed, the system blocks it.

    SEPF_SM-G975U_12_0001 is apparently Samsung's security policy file for your >AJL's specific model, presumably an (SM-G975U = Galaxy S10+), Android 12 >(but see below about the Android 12 ambiguity).

    Date is apparently the build date of that specific security policy file.

    For the record, my Galaxy A32-5G (which is no longer on full support) says:
    SE for Android status
    Enforcing
    SEPF_SM-A326U_12_0001
    Wed Feb 19 18:52:36 2025

    Indicating, similarly that SELinux is active and enforcing rules, not just >logging them so any app or process that tries to do something outside the >allowed security policy gets blocked.

    Apparently, the opposite would be "permissive", as far as I can tell.

    In my case, the version of the security file is
    a. SEPF meaning Samsung Enhanced Policy File
    b. SM-A326U indicating my device model (Galaxy A32 5G, U.S. variant)
    c. 12 oddly indicating Android 12 but I'm really on Android 13
    d. 0001 is apparently the policy revision number
    e. Wed Feb 19 18:52:36 2025 is the build date of the security policy file

    Note that apparently, Samsung did not update the SELinux policy file name >when upgrading my device from Android 12 to Android 13.

    We could cover this one topic forever with the amount of data on it I see,
    so I'll stop there, but it's not Secure Enclave so much as Secure Enhanced.

    Much above is Greek to me. But thanks both for the info. Most all I use my
    old phone for is calls and text and both are low security jabbering at
    that. Course a phone's Google account/apps breach would be bad but it
    appears the big 'G' has me covered there.

    I used to kinda wonder about my side loaded Google stuff on this Amazon Fire
    Tablet but G does regular updates on it too. It's a common Fire OS mod and
    so far I've seen no security complaints.

    My Chromebook toy doesn't ask. It just updates in the background and then
    sticks a reboot button on the screen. My W11 LT is the other way. It says
    I'm up to date but then when I push the check for updates button about half
    the time it has one. IMO my safest toy is the Chromebook. But I only have 5
    years left on mine before AUE and by then the Chrome OS may be gone. The
    new Google Aluminum OS is reported to be based on Android. See I'm back on
    topic...




    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Frank Slootweg@[email protected] to comp.mobile.android on Sun Apr 19 13:32:01 2026
    From Newsgroup: comp.mobile.android

    AJL <[email protected]> wrote:
    On 4/18/26 1:15 PM, Frank Slootweg wrote:

    your^Msnipping made *you* draw the wrong conclusion

    Nope. My conclusion for several years now has been that my 6 year old
    phone's security is very outdated. I certainly didn't need to rummage
    around in various parts of settings to figure that out...

    That was not the (wrong) conclusion I was referring to, so you *again*
    drew the wrong conclusion! :-)

    BTW how did I do with my snipping this time... ;)

    Fine, it was even more rigorous than mine! :-)

    BTW, I don't think that a 6 year old phone without recent security
    updates is a (security) problem per se. My wife's A51 is similar at
    5 2/3 year. And I would still be using my A51 if it didn't break
    hardware wise (too frequent hardware caused crashes).

    I consider the security of my 'sensitive' (i.e. banking, etc.) *apps*
    the deciding factor, not the security of the underlying OS (i.e.
    Android). As long as the app developers (i.e. the banks, etc.) support
    the 'old' Android version, that's fine by me.
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Maria Sophia@[email protected] to comp.mobile.android on Sun Apr 19 10:51:36 2026
    From Newsgroup: comp.mobile.android

    AJL wrote:
    Most all I use my
    old phone for is calls and text and both are low security jabbering at
    that. Course a phone's Google account/apps breach would be bad but it
    appears the big 'G' has me covered there.

    Neither you nor I (nor Frank it seems) is all that worried about security.
    As you noted, phone calls aren't much of a security hazard (AFAICT).
    Texting isn't either (as long as you don't download strange docs).'

    I'm NOT an expert in security, so what I say below to concur is hearsay.

    I think "most" of the security happens in the web, but, luckily for me, my
    eyes are so old, I (almost) never use a web browser on a phone anyway.

    And my web browsers are security-focused to start with and I have all that "automatic link" stuff (which I don't understand anyway), turned off too.

    Not having a Google Account also might help with my security.
    And, of course, I don't use any app which requires logging into it.

    I think if I logged into a mothership account, like most iPhone and Android users do, the security aspect might be greater but I don't know that for
    sure.

    But, like you and Frank, I'm not worried (sometimes ignorance is bliss, but sometimes not worrying about what won't happen is just as much that bliss).
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From AJL@[email protected] to comp.mobile.android on Sun Apr 19 18:11:40 2026
    From Newsgroup: comp.mobile.android

    On 4/19/26 6:32 AM, Frank Slootweg wrote:
    AJL <[email protected]> wrote:

    My conclusion for several years now has been that my 6 year old
    phone's security is very outdated.

    I don't think that a 6 year old phone without recent security
    updates is a (security) problem per se. My wife's A51 is similar at
    5 2/3 year. And I would still be using my A51 if it didn't break
    hardware wise (too frequent hardware caused crashes).

    For me its a paranoia thing. I don't NEED my sensitive apps on my low
    security phone so why take a chance when I can easily take care of business
    on a much more secure up to date device. And then there's paranoia #2 if my
    lower security sensitive app loaded phone were to be lost or stolen.

    I consider the security of my 'sensitive' (i.e. banking, etc.) *apps*
    the deciding factor, not the security of the underlying OS (i.e.
    Android). As long as the app developers (i.e. the banks, etc.) support
    the 'old' Android version, that's fine by me.

    Since I don't NEED those apps on my phone I don't have to worry about an app
    developers capability and/or my low security device. My life could change
    drastically if my bank/investment/retirement accounts were broken into.
    Paranoia (my favorite word) in spades...

    YMMV as always...







    --- Synchronet 3.21f-Linux NewsLink 1.2