Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #153630
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Security updates in the EU. |
| Date | 2026-04-24 11:25 +0200 |
| Message-ID | <jhprbmx0oh.ln2@Telcontar.valinor> (permalink) |
| References | <50dqbmxkcq.ln2@Telcontar.valinor> <1ln5rvqmq9ebq$.dlg@v.nguard.lh> <4lqqbmx00p.ln2@Telcontar.valinor> <10h4cdqbgma6w.dlg@v.nguard.lh> |
On 2026-04-24 08:40, VanguardLH wrote: > "Carlos E.R." <robin_listas@es.invalid> wrote: > >> On 2026-04-24 00:27, VanguardLH wrote: >>> "Carlos E.R." <robin_listas@es.invalid> wrote: >>> >>>> <https://www.theolivepress.es/spain-news/2026/04/20/eu-to-force-replaceable-batteries-in-phones-and-tablets-from-2027/> >>>> >>>> The article is about batteries: >>>> >>>> *Brussels will require all phones sold in the EU to have replaceable >>>> batteries from 2027 – and use USB-C chargers* >>>> >>>> But there is also this paragraph inside: >>>> >>>> «Since 2025, system updates must be available for at least five years >>>> from the date the last unit model is sold, according to the same >>>> regulation.» >>>> >>>> WOW! >>>> >>>> But that "law" is not being enforced :-( >>> >>> How does the manufacturer who provides the updates know when was the >>> last date of purchase for a model? They don't sell the phones. They >>> just make them. A phone could sit in storage for an indefinite term, >>> like many many years. I bought a phone that was introduced in 2016, but >>> I bought it in 2019. I'm sure there are other phones that have sit in >>> storage a lot longer. >> >> It would read as when they sold the last one to sellers. > > But that could be years, many years, after the manufacturer sold off the > last lot of a model. The law may read system updates must be available > for 5 years after last sale from mfr, but lots of users may not buy the > stocked phones for many years later, so the requirement has expired. > They'd still not get updates. No, I mean 5 years since the manufacturer sells the last batch. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar
Security updates in the EU. "Carlos E.R." <robin_listas@es.invalid> - 2026-04-23 22:45 +0200
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-23 16:01 -0600
Re: Security updates in the EU. VanguardLH <V@nguard.LH> - 2026-04-23 17:27 -0500
Re: Security updates in the EU. "Carlos E.R." <robin_listas@es.invalid> - 2026-04-24 02:38 +0200
Re: Security updates in the EU. Chris in Makati <mail@nospam.com> - 2026-04-24 09:00 +0800
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-23 22:55 -0600
Re: Security updates in the EU. VanguardLH <V@nguard.LH> - 2026-04-24 01:41 -0500
Re: Security updates in the EU. Chris <ithinkiam@gmail.com> - 2026-04-24 08:14 +0000
Re: Security updates in the EU. Andy Burns <usenet@andyburns.uk> - 2026-04-24 09:29 +0100
Re: Security updates in the EU. Jörg Lorenz <hugybear@gmx.net> - 2026-04-24 16:09 +0200
Re: Security updates in the EU. Chris <ithinkiam@gmail.com> - 2026-04-24 17:03 +0000
Re: Security updates in the EU. Jörg Lorenz <hugybear@gmx.net> - 2026-04-24 19:08 +0200
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-24 17:59 -0600
Re: Security updates in the EU. AJL <noemail@none.com> - 2026-04-25 02:19 +0000
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-24 22:13 -0600
Re: Security updates in the EU. Chris <ithinkiam@gmail.com> - 2026-04-25 09:02 +0000
Re: Security updates in the EU. "Carlos E.R." <robin_listas@es.invalid> - 2026-04-25 14:22 +0200
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-25 08:24 -0600
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-25 08:15 -0600
Re: Security updates in the EU. Andy Burns <usenet@andyburns.uk> - 2026-04-24 08:43 +0100
Re: Security updates in the EU. Chris <ithinkiam@gmail.com> - 2026-04-24 08:14 +0000
Re: Security updates in the EU. Richmond <dnomhcir@gmx.com> - 2026-04-25 11:34 +0100
Re: Security updates in the EU. VanguardLH <V@nguard.LH> - 2026-04-24 01:40 -0500
Re: Security updates in the EU. Andy Burns <usenet@andyburns.uk> - 2026-04-24 08:45 +0100
Re: Security updates in the EU. "Carlos E.R." <robin_listas@es.invalid> - 2026-04-24 11:25 +0200
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-24 10:07 -0600
Re: Security updates in the EU. Andy Burns <usenet@andyburns.uk> - 2026-04-24 08:42 +0100
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-24 10:11 -0600
Re: Security updates in the EU. Chris <ithinkiam@gmail.com> - 2026-04-24 16:26 +0000
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-24 10:46 -0600
Re: Security updates in the EU. Andy Burns <usenet@andyburns.uk> - 2026-04-24 17:48 +0100
Re: Security updates in the EU. Jörg Lorenz <hugybear@gmx.net> - 2026-04-24 18:52 +0200
Re: Security updates in the EU. Frank Slootweg <this@ddress.is.invalid> - 2026-04-24 18:08 +0000
Re: Security updates in the EU. "Carlos E.R." <robin_listas@es.invalid> - 2026-04-25 14:27 +0200
Re: Security updates in the EU. Chris <ithinkiam@gmail.com> - 2026-04-25 19:39 +0000
Re: Security updates in the EU. Jörg Lorenz <hugybear@gmx.net> - 2026-04-24 09:24 +0200
Re: Security updates in the EU. "Carlos E.R." <robin_listas@es.invalid> - 2026-04-24 11:39 +0200
Re: Security updates in the EU. Maria Sophia <mariasophia@comprehension.com> - 2026-04-24 10:16 -0600
Re: Security updates in the EU. "s|b" <me@privacy.invalid> - 2026-04-24 16:06 +0200
Re: Security updates in the EU. Jörg Lorenz <hugybear@gmx.net> - 2026-04-24 16:10 +0200
Re: Security updates in the EU. Frank Slootweg <this@ddress.is.invalid> - 2026-04-24 15:31 +0000
csiph-web