From: this@ddress.is.invalid   
      
   Carlos E.R.  wrote:   
   > On 2026-01-20 20:08, Frank Slootweg wrote:   
   > > VanguardLH  wrote:   
   > >> Frank Slootweg  wrote:   
   >   
   > ...   
   >   
   > >>   
   > >> Android 16 was *released* in June 2025.   
   > >>   
   > >> Samsung Galaxy A36 was released in March 2025 -- way to close to the   
   > >> Android 16 release date.   
   > >>   
   > >> Obviously phones sitting in boxes in storage aren't going to get   
   > >> updated.  Takes time to deploy a new OS to in-stock phones.   
   > >   
   > >    Yes, that's what I meant with 'out-of-date'. Not blaming anybody.   
   > >   
   > >    BTW, release time - of the phone versus the Android version - is not   
   > > what matters, but when *your* phone was *manufactured*. If your phone   
   > > was manufactured a reasonable time after June 2025, it should have   
   > > Android 16.   
   >   
   > That should be "designed". I have seen phones sold with Android versions   
   > one or two year old. Samsung.   
      
     No, it should be "manufactured". It's quite possible that an already   
   designed phone gets a new Android version during it's lifetime, i.e.   
   multiple manufacturing batches, often at multiple manufacturing   
   locations [1].   
      
     Note that I said it *should* have Android 16. Should, not must, as, as   
   you say, this preferred practice is not always followed.   
      
     BTW, it's the same with Windows PCs. When you get them, the Windows   
   version is often out-of-date, i.e. Windows 11 24H2 instead of 25H2 and   
   missing  a number of monthly updates.   
      
   [1] We had two Samsung Galaxy A51 phones, which were bought at the same   
   time, but manufactured at different locations/countries. Their firmware   
   was slightly different.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)