Re: Planned Obsolescence

[johnny saylor]

hola

on an original pixel (sailfish) but now running stock android 10 
(yeech!). i was running lineage 17.1 (?) but at some point the phone 
began behaving badly. once a call came in, screen went blank and did not 
resond to touches (could not answer phone nor navigate voice mail tree[s]).

as i (obliquely) mention, the roll back did nothing to fix this problem. 
but now that it's google all the way down (stock android), i am less 
likely to pick up my phone for amusement (a good thing).

if anyone knows anything about fixing this (screen completely off during 
phone call), i'd be most grateful. otherwise, i'll prolly just buy a new 
(to me) phone (most likely samsung something or other) for the $200. 
price point i like.

happy christmas (war is over if you want it)

On 12/14/20 1:34 PM, Aaron Wolf wrote:
> I'm still on a Pixel (original) running LineageOS, so I still get
> security updates. I'm quite sure the Pixel 2 is supported by LineageOS
> fully.
>
> Side-note: I used to be hesitant to admit to even having a cell phone.
> Very ironically, I got my first cell phone ever in 2014 as part of
> attending LibrePlanet for the first time and having more and more
> hassles with trying to connect to accommodations and such via finding
> wifi spot to use my laptop (and payphones were mostly all gone). I've
> never had a phone with Google Apps though.
>
> But yeah, the whole idea that it's a weird community hack to keep
> devices updates is a travesty (as is the other compromised aspects of
> these devices).
>
> On 2020-12-11 9:16 a.m., Eric Schultz wrote:
> >     Android phone makers in particular are known for refusing to update
> >     their phones for more than a minimal amount of time. I literally just
> >     had to buy a new phone because my Pixel 2, which was working fine, is
> >     no longer receiving security updates. Allegedly one of the main reasons
> >     phone makers don't update phones is that the processor, chipset and
> >     modem makers don't provide long term support for their firmware blobs
> >     and a mix of free and proprietary build tools.
> >     Eric
> >
> >     On Thu, Dec 10, 2020 at 7:14 PM Jason Self <[1]jself@gnu.org> wrote:
> >
> >       We're looking for articles describing specific instances of planned
> >       obsolescence in computing which relate somehow to nonfree software.
> >       If you know of an example which is not listed in
> >       [2]https://gnu.org/malware/proprietary-obsolescence.html please mail
> >       the
> >       URL to [3]webmasters@gnu.org so we can list it there.
> >       _______________________________________________
> >       libreplanet-discuss mailing list
> >       [4]libreplanet-discuss@libreplanet.org
> >       [5]https://lists.libreplanet.org/mailman/listinfo/libreplanet-discus
> >       s
> >
> >     --
> >
> >     Eric Schultz, Developer and FOSS Advocate
> >     [6]wwahammy.com
> >     [7]eric@wwahammy.com
> >     @wwahammy
> >     Pronouns: He/his/him
> >
> > References
> >
> >     1. mailto:jself@gnu.org
> >     2. https://gnu.org/malware/proprietary-obsolescence.html
> >     3. mailto:webmasters@gnu.org
> >     4. mailto:libreplanet-discuss@libreplanet.org
> >     5. https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
> >     6. http://wwahammy.com/
> >     7. mailto:eric@wwahammy.com
> >
> >
> > _______________________________________________
> > libreplanet-discuss mailing list
> > libreplanet-discuss@libreplanet.org
> > https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss