Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #148749 > unrolled thread

Alternate OS for LG V20?

Back to article view | Back to comp.mobile.android

Contents

  Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-11 02:53 -0500
    Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-11 11:22 +0100
      Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-11 08:46 -0500
        Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-11 15:27 +0000
        Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-12 10:20 +0200
          Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-12 17:27 +0000
          Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-12 13:58 -0500
            Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 01:06 +0200
              Re: Alternate OS for LG V20? AJL <noemail@none.com> - 2025-06-13 00:57 +0000
                Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-13 02:09 +0000
                  Re: Alternate OS for LG V20? AJL <noemail@none.com> - 2025-06-13 02:44 +0000
                    Re: Alternate OS for LG V20? Andy Burns <usenet@andyburns.uk> - 2025-06-13 08:29 +0100
                      Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-13 13:51 +0000
              Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-12 20:42 -0500
              Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-12 21:28 -0500
                Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 13:26 +0200
              Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-13 02:35 +0000
            Re: Alternate OS for LG V20? Gelato <gelato@.is.invalid> - 2025-06-12 22:14 -0400
              Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-13 04:21 -0500
                Re: Alternate OS for LG V20? Andy Burns <usenet@andyburns.uk> - 2025-06-13 11:18 +0100
                  Re: Alternate OS for LG V20? Gelato <gelato@.is.invalid> - 2025-06-13 10:06 -0400
                    Re: Alternate OS for LG V20? Andy Burns <usenet@andyburns.uk> - 2025-06-13 15:17 +0100
                      Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-13 11:43 -0500
                        Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 20:55 +0200
                          Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-15 03:50 +0000
                            Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-16 19:54 +0200
                        Re: Alternate OS for LG V20? Andy Burns <usenet@andyburns.uk> - 2025-06-13 20:46 +0100
                          Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-15 03:53 +0000
                        Re: Alternate OS for LG V20? Jörg Lorenz <hugybear@gmx.net> - 2025-06-16 08:50 +0200
                    Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-13 11:01 -0500
                      Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-13 17:18 +0100
                    Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-13 20:57 +0200
                      Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-15 03:59 +0000
                        Re: Alternate OS for LG V20? Andy Burns <usenet@andyburns.uk> - 2025-06-15 07:23 +0100
                          Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-15 16:18 +0000
                            Re: Alternate OS for LG V20? "Carlos E.R." <robin_listas@es.invalid> - 2025-06-16 19:58 +0200
            Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-13 16:48 +0100
              Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-13 12:00 -0500
                Re: Alternate OS for LG V20? AJL <noemail@none.com> - 2025-06-13 17:40 +0000
                  Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-13 18:13 +0000
              Re: Alternate OS for LG V20? Wolf Greenblatt <wolf@greenblatt.net> - 2025-06-13 14:07 -0400
      Re: Alternate OS for LG V20? Marion <marion@facts.com> - 2025-06-11 15:07 +0000
    Re: Alternate OS for LG V20? Andy Burns <usenet@andyburns.uk> - 2025-06-11 11:35 +0100
      Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-11 11:43 +0100
        Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-11 09:07 -0500
          Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-11 15:31 +0100
            Re: Alternate OS for LG V20? Oscar <oscar@invalid.net> - 2025-06-11 11:11 -0400
              Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-11 22:02 +0100
                Re: Alternate OS for LG V20? Oscar <oscar@invalid.net> - 2025-06-12 14:51 -0400
                  Re: Alternate OS for LG V20? Theo <theom+news@chiark.greenend.org.uk> - 2025-06-13 16:59 +0100
            Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-12 14:10 -0500
              Re: Alternate OS for LG V20? AJL <noemail@none.com> - 2025-06-12 21:48 +0000
                Re: Alternate OS for LG V20? VanguardLH <V@nguard.LH> - 2025-06-12 18:08 -0500
                  Re: Alternate OS for LG V20? AJL <noemail@none.com> - 2025-06-13 00:42 +0000

Page 3 of 3 — ← Prev page 1 2 [3]

#148820

On 13 Jun 2025 16:48:36 +0100 (BST), Theo wrote:

> The trouble with user replaceable batteries that for most phones, by the
> time the battery needs replacing, OEM batteries are unavailable.

When I read the EU regulations years ago, I remember the manufacturers MUST
make the parts (including tools) available for a certain number of years
AFTER the last sale.

Do you disagree?

[toc] | [prev] | [next] | [standalone]

#148760

On 11 Jun 2025 11:22:31 +0100 (BST), Theo wrote :


> In general, for any phone, your best bet is to search XDA Forums and see who
> has done a third party OS for your specific model number (and I mean number,
> ie not just the marketing name Samsung Galaxy Note N, but the number
> SM-GT1234).

My suggestion to the OP is to make clear note of the baseband version.

For those lurking, Theo is correct but it goes even further than the Model
Number because in my case, the baseband *version* is also critical.

As far as XDA Developers forums are aware, only some baseband versions of
my model number are rootable (apparently because Samsung removed the OEM
unlock option in the US models but only in the later baseband versions).

<https://xdaforums.com/t/is-my-almost-3-year-old-t-mobile-network-unlocked-samsung-galaxy-sm-a326u-bootloader-still-unlockable-and-hence-is-my-sm-a326u-still-unrootable.4638955/>

[toc] | [prev] | [next] | [standalone]

#148753

VanguardLH wrote:

> After rooting my unlocked LG V20 (AT&T model H-910), I'd like to get
> something newer than the Android 8.0.0 that is on it now.  [...] 
> What other Android replacements (maybe getting me to v15) could I put on
> this phone? 
I'd be surprised if a snapdragon 820 has the horsepower to run v13/14/15 
acceptably?

[toc] | [prev] | [next] | [standalone]

#148754

Andy Burns <usenet@andyburns.uk> wrote:
> VanguardLH wrote:
> 
> > After rooting my unlocked LG V20 (AT&T model H-910), I'd like to get
> > something newer than the Android 8.0.0 that is on it now.  [...] 
> > What other Android replacements (maybe getting me to v15) could I put on
> > this phone? 
> I'd be surprised if a snapdragon 820 has the horsepower to run v13/14/15 
> acceptably?

What extra does v13-15 need in terms of horsepower?
(other than the AI stuff, which you won't get on an AOSP OS anyway)

4GB of RAM is likely to be more of a limiting factor.

Theo

[toc] | [prev] | [next] | [standalone]

#148758

Theo <theom+news@chiark.greenend.org.uk> wrote:

> Andy Burns <usenet@andyburns.uk> wrote:
>
>> VanguardLH wrote:
>> 
>>> After rooting my unlocked LG V20 (AT&T model H-910), I'd like to get
>>> something newer than the Android 8.0.0 that is on it now.  [...]
>>> What other Android replacements (maybe getting me to v15) could I
>>> put on this phone? 
>>
>> I'd be surprised if a snapdragon 820 has the horsepower to run v13/14/15 
>> acceptably?
> 
> What extra does v13-15 need in terms of horsepower?
> (other than the AI stuff, which you won't get on an AOSP OS anyway)

If disable-able, AI is a "feature" that I get rid of as soon as
possible.  I'm too old to want any handholding telling me what to do, or
where to look.  AI just slows me down, and always in the way.

Android 8.0 was released in Aug 2017.  Even getting to Android 12
released in Oct 2021 might get me another 4 years lifespan before apps
moved past v12 as a minimum requirement.

> 4GB of RAM is likely to be more of a limiting factor.

https://wiki.lineageos.org/devices/joan/variant1/

That targets the LG V30 that also had 4 GB of RAM.

Now that I reread the specs for my phone, I realized that I may not want
to bother with rooting it to then get a later OS on it.  This phone does
not support 5G (4G LTE), and 4G is already a bit slow for me.  I have
apps that are heavily network dependent, like the Weight Watchers app
where every lookup and database check is an online lookup.  If their
server is slow, or down, the WW app is a pain to use, or unusable.  They
don't cache anything on the phone despite it has a 128GB uSD card.
Other highly network-centric apps are similarly slower on my old phone
that I've seen on phones for my friends with newer phones (faster CPU,
faster network).  Envy is infectious.

I don't want the network hardware in the phone slowing me down more, so
I just might start looking at new phones again.  Or, even wait until 6G
becomes mainstream with its higher frequencies which means high
bandwidth and much lower latency.  Alas, I don't know if I can stand
using my old phone for another 5 years, or more.  Rooting and a new OS
aren't going to change cellular radio hardware, or make faster the CPU.
I could be beating a nearly dead horse trying to mend my old phone.

[toc] | [prev] | [next] | [standalone]

#148759

VanguardLH <V@nguard.lh> wrote:
> I don't want the network hardware in the phone slowing me down more, so
> I just might start looking at new phones again.  Or, even wait until 6G
> becomes mainstream with its higher frequencies which means high
> bandwidth and much lower latency.  Alas, I don't know if I can stand
> using my old phone for another 5 years, or more.  Rooting and a new OS
> aren't going to change cellular radio hardware, or make faster the CPU.
> I could be beating a nearly dead horse trying to mend my old phone.

Yes, I think that's the way to approach it - you can put effort into making
the software new but if the hardware is getting old then it won't help.  I'd
suggest looking for new/used/refurbished phones that are a year or two old -
with 7 years of support that only drops you down to 5 or 6 years, but the
price can be cut in half or more.

The main issue is if the old phone has some hardware feature you love but
doesn't exist on newer phones - then it's harder to 'upgrade' to something
that's worse than what you had before.  But eventually the pain of trying to
keep the old going outweighs the draw of the old hardware.

Theo

[toc] | [prev] | [next] | [standalone]

#148761

On 11 Jun 2025 15:31:52 +0100 (BST), Theo
<theom+news@chiark.greenend.org.uk> wrote 

> I'd
> suggest looking for new/used/refurbished phones that are a year or two old -
> with 7 years of support that only drops you down to 5 or 6 years, but the
> price can be cut in half or more.

Which android brand or model is the most rootable, historically?

[toc] | [prev] | [next] | [standalone]

#148772

Oscar <oscar@invalid.net> wrote:
> On 11 Jun 2025 15:31:52 +0100 (BST), Theo
> <theom+news@chiark.greenend.org.uk> wrote 
> 
> > I'd
> > suggest looking for new/used/refurbished phones that are a year or two old -
> > with 7 years of support that only drops you down to 5 or 6 years, but the
> > price can be cut in half or more.
> 
> Which android brand or model is the most rootable, historically?

Pixel.  They have the best support for aftermarket OSes, meaning that
there's more choice for Pixel than for other brands.  It's why OSes like
GrapheneOS only support Pixels.

(but US carriers can still lock bootloaders if they want to, so if you get a
carrier Pixel best to check it isn't bootloader locked)

Theo

[toc] | [prev] | [next] | [standalone]

#148781

On 11 Jun 2025 22:02:38 +0100 (BST), Theo
<theom+news@chiark.greenend.org.uk> wrote 

>> Which android brand or model is the most rootable, historically?
> 
> Pixel.  They have the best support for aftermarket OSes, meaning that
> there's more choice for Pixel than for other brands.  It's why OSes like
> GrapheneOS only support Pixels.
> 
> (but US carriers can still lock bootloaders if they want to, so if you get a
> carrier Pixel best to check it isn't bootloader locked)

Does the news Google no longer supports a Pixel AOSP make a difference?

[toc] | [prev] | [next] | [standalone]

#148812

Oscar <oscar@invalid.net> wrote:
> On 11 Jun 2025 22:02:38 +0100 (BST), Theo
> <theom+news@chiark.greenend.org.uk> wrote 
> 
> >> Which android brand or model is the most rootable, historically?
> > 
> > Pixel.  They have the best support for aftermarket OSes, meaning that
> > there's more choice for Pixel than for other brands.  It's why OSes like
> > GrapheneOS only support Pixels.
> > 
> > (but US carriers can still lock bootloaders if they want to, so if you get a
> > carrier Pixel best to check it isn't bootloader locked)
> 
> Does the news Google no longer supports a Pixel AOSP make a difference?

They still do.  What they don't do is release AOSP commits ahead of time, it
comes all together at release time.  That means custom OSes can't do work
ahead of the release date, so they'll take longer.

There's another issue about not releasing Pixel device trees surfaced
yesterday, but not sure how that will pan out - maybe they can be extracted
from the stock OS.  Looks like GrapheneOS are on the case, although hampered
by other things going on in the world right now:
https://grapheneos.social/@GrapheneOS/114670995130379882

Theo

[toc] | [prev] | [next] | [standalone]

#148783

Theo <theom+news@chiark.greenend.org.uk> wrote:

> VanguardLH <V@nguard.lh> wrote:
>> I don't want the network hardware in the phone slowing me down more, so
>> I just might start looking at new phones again.  Or, even wait until 6G
>> becomes mainstream with its higher frequencies which means high
>> bandwidth and much lower latency.  Alas, I don't know if I can stand
>> using my old phone for another 5 years, or more.  Rooting and a new OS
>> aren't going to change cellular radio hardware, or make faster the CPU.
>> I could be beating a nearly dead horse trying to mend my old phone.
> 
> Yes, I think that's the way to approach it - you can put effort into making
> the software new but if the hardware is getting old then it won't help.  I'd
> suggest looking for new/used/refurbished phones that are a year or two old -
> with 7 years of support that only drops you down to 5 or 6 years, but the
> price can be cut in half or more.

A problem I've read about with "renewed" or "restored" phones is the
buyer ends up with a bricked phone after a couple months.  They are told
that the phone was reported lost or stolen, or somehow the prior owner
reported a loss of their phone.  The phone got on some "bad" list, so it
got disabled.  The new owner gets screwed.  Neither the seller nor the
phone maker will resolve the issue.  Also, used is too often abused.

> The main issue is if the old phone has some hardware feature you love but
> doesn't exist on newer phones - then it's harder to 'upgrade' to something
> that's worse than what you had before.  But eventually the pain of trying to
> keep the old going outweighs the draw of the old hardware.

I love that the batteries in the LG V20 are user serviceable.  Batteries
are chemical, so they wane in capacity over time, and then become
unusable or dead.  Not when you can replace them.  There are no new
phones with replaceable batteries.  You can crack open the case to
unsolder the old battery to insert a new one, but that voids the
warranty as well as the seal, and you risk the phone in the surgery.

Lithium batteries have a lifespan of 3 to 10 years.  There are always
manufacturing defects.  The phone makers want you buying more phones.
Replaceable batteries eliminates the only self-degrading consumable of
the product.  Well, other than the OS itself as updated or newer apps
demand later versions of it.

[toc] | [prev] | [next] | [standalone]

#148784

On 6/12/25 12:10 PM, VanguardLH wrote:
>Theo <theom+news@chiark.greenend.org.uk> wrote:
>
>> VanguardLH <V@nguard.lh> wrote:
>>> I don't want the network hardware in the phone slowing me down more, so
>>> I just might start looking at new phones again.  Or, even wait until 6G
>>> becomes mainstream with its higher frequencies which means high
>>> bandwidth and much lower latency.  Alas, I don't know if I can stand
>>> using my old phone for another 5 years, or more.  Rooting and a new OS
>>> aren't going to change cellular radio hardware, or make faster the CPU.
>>> I could be beating a nearly dead horse trying to mend my old phone.
>> 
>> Yes, I think that's the way to approach it - you can put effort into making
>> the software new but if the hardware is getting old then it won't help.  I'd
>> suggest looking for new/used/refurbished phones that are a year or two old -
>> with 7 years of support that only drops you down to 5 or 6 years, but the
>> price can be cut in half or more.

I've had a few renewed (used-refurb) tablets over the years and have had
 good luck with them. I was mainly worried about getting one with a worn
 battery but never had a problem. My latest toy, a renewed Lenovo Chrome
 tablet, has a diagnostics screen built into the OS and reports the battery
 health at 97% with the cycle count at 11 so it appears I've perhaps once
 more lucked out.

>A problem I've read about with "renewed" or "restored" phones is the
>buyer ends up with a bricked phone after a couple months.  They are told
>that the phone was reported lost or stolen, or somehow the prior owner
>reported a loss of their phone.  The phone got on some "bad" list, so it
>got disabled.  The new owner gets screwed.  Neither the seller nor the
>phone maker will resolve the issue.  Also, used is too often abused.

>> The main issue is if the old phone has some hardware feature you love but
>> doesn't exist on newer phones - then it's harder to 'upgrade' to something
>> that's worse than what you had before.  But eventually the pain of trying to
>> keep the old going outweighs the draw of the old hardware.

>I love that the batteries in the LG V20 are user serviceable.  Batteries
>are chemical, so they wane in capacity over time, and then become
>unusable or dead.  Not when you can replace them.  There are no new
>phones with replaceable batteries.  You can crack open the case to
>unsolder the old battery to insert a new one, but that voids the
>warranty as well as the seal, and you risk the phone in the surgery.

All the phone and tablet replacement batteries I've installed over the years
 came with plugs. No soldering needed. Unsticking the glue was the main
 problem. My current Galaxy S10+ phone is 5+ years old and the original
 battery is still working fine for my light use. I could get a replacement
 battery including installation tools for under $20US (Amazon) when it
 fails, but since the phone's last update was a year ago and it still claims
 the software is up to date, I may pass...


>Lithium batteries have a lifespan of 3 to 10 years.  There are always
>manufacturing defects.  The phone makers want you buying more phones.
>Replaceable batteries eliminates the only self-degrading consumable of
>the product.  Well, other than the OS itself as updated or newer apps
>demand later versions of it.

I don't miss my phone breaking into 3 pieces (battery, battery cover, phone)
 when dropped so really don't mind having an internal battery. And I think
 for many folks when the battery fails the phone is obsolete anyway. It
 certainly will be so in my case...

[toc] | [prev] | [next] | [standalone]

#148786

AJL <noemail@none.com> wrote:

> I don't miss my phone breaking into 3 pieces (battery, battery cover, phone)
>  when dropped so really don't mind having an internal battery. 

I've always had a case on my phones.  Not those thin decorative tin foil
covers, but a carbon-fiber back and TPU liner to survive falls.  Unless
the phone managed to pop out of the armor case on a fall, it would be
impossible to fall into pieces.  However, one issue I've run into
lithium batteries in phones is them getting pregnant.  They outgas, and
sometimes that makes the lithium battery swell.  I'll notice capacity
(up time) has diminished, remove the phone from the armor case, open the
back (which I notice is already bulging out), and find a pregnant
battery.  An easy test if not visually apparent is to put the battery on
a flat table to see if you can spin it.  If it spins, it is bulging.  Go
buy a replacement battery.  Easy to swap.  Put back in the armor case.

In addition, an armor case provide much better tactile retention of the
phone.  They have been making smart phones more slick, like using glass
instead of metal, and thinner.  They are getting easier to slip out of
your grip.  Almost every delivery person I see come to my door has a
cracked screen where I see their screen as their punching in and taking
a photo on making the delivery, or have me sign on their phone.  I
haven't had any cracked screens ever although I admit to occasionally
whacking the phone on a table when I got severely pissed.  

I've been quite surprised the screen has not cracked from all those
smacks.  After 7 years of my abuse, the only damage to my old phone is a
bent back plate, but I just bought a replacement ($10) which will better
attach to the phone with no gaps or bent-out edges to snag.  No matter
how much I bent the old one, I couldn't get the back plate to form
correctly and perfectly flat to the phone.  It would attach, but too
easily pop off (and the battery drop out) on a drop.  However, while
inside the armor case, nothing came apart on a drop or smack.  I don't
use those decorative cases, or the ones that are just silicone, but the
type that has a rigid back half, the silicone TPU, and a front bezel
that snaps onto the back half.  Without the armor case, I have fumbled
the shiny, smooth, slippery bare phone too often.  Maybe my dexterity
has deteriorated with age, and the armor case helps to grab the phone.

> And I think for many folks when the battery fails the phone is
> obsolete anyway. It certainly will be so in my case...

That was the phrase I couldn't remember: planned obsolescence.  Yeah,
lots of users don't even buy phones, or get them very cheap, but
bundling the deal with a carrier.  So, they're used to swapping out or
trading in their phones about every 3 years, on average.  I'm not
average.  I'm also not nomophobic.  All this 2FA security theater is
premised on smart phone dependency, like the thing is grafted to its
owner.

Only because my old Android 8 is getting abandoned by apps with higher
minimal OS requirements am I now considering replacing my 7 year phone
(which was released 9 years ago).  I could manage without 5G, and
survive on just 4G (not even 4G LTE).  Twould be nice to have a faster
chipset and CPU, and more RAM, but then I don't leave apps running nor
run many at the same time.  I use web browsers that actually have an
Exit (unload) option instead of left loaded in memory in the background
awaiting for whenever the OS decides it needs the memory for a newly
loaded app (Android is just so rude regarding unloads all to pretend the
platform is faster than it really is), but then I don't leave the web
browser, or any other program, running on my desktop, either.  There is
64 GB internal storage, and I added a 128 GB uSD card, yet over the 7
years only used half the internal RAM, and nothing on the uSD card.  I
had offline maps stored on the uSD for awhile (for the Here[WeGo] map
app), which ate up 60 GB, but even then I had lots of storage space left
over.  In looking at new phones, I'm not sure I want to pay the extra
$150+ to go from 256 GB to 512 GB.  While I use a smart phone, I'm not
an avid fan of them.  Seems more of technology trying to create a void
to then fill it rather than of it filling an existing void.

If I could get Android 12, or up, on my old smart phone, I wouldn't be
looking at a replacement.  However, the likelihood of that happening,
and having full support of all hardware with no conflicts or newly
created deficiencies, seems dismal.  I'm also getting old enough where I
shy away from doing it all myself.  I stopped changing my engine oil and
filter eons ago, and instead pay someone else to do that drudge work
hence why I'm likely to look at getting a new phone instead of trying to
beat the old phone on an anvil to reshape it.  And I'll be putting an
armor case on the new phone, too, but not a screen protector (I found
those have more friction, even the glass ones, than the glass screen on
the phone, and there are still some apps you have to swipe in from the
side to get at their menu, but screen protectors don't go to the very
edge of screens, or a wee bit beyond, so they interfere with side
swiping).

[toc] | [prev] | [next] | [standalone]

#148787

On 6/12/25 4:08 PM, VanguardLH wrote:
>AJL <noemail@none.com> wrote:
>
>> I don't miss my phone breaking into 3 pieces (battery, battery cover, phone)
>>  when dropped so really don't mind having an internal battery. 
>
>I've always had a case on my phones.  Not those thin decorative tin foil
>covers, but a carbon-fiber back and TPU liner to survive falls.  Unless
>the phone managed to pop out of the armor case on a fall, it would be
>impossible to fall into pieces.  

>However, one issue I've run into
>lithium batteries in phones is them getting pregnant.  They outgas, and
>sometimes that makes the lithium battery swell.  I'll notice capacity
>(up time) has diminished, remove the phone from the armor case, open the
>back (which I notice is already bulging out), and find a pregnant
>battery.

The wife's iPhone's battery swelled up and popped open its case one time.
 There was no apparent external reason. Funny thing was that the phone still
 worked and was useable if you were careful. So I left it running and kept
 it on a metal cookie platter (in case of fire) until the new battery
 arrived in the mail.

>An easy test if not visually apparent is to put the battery on
>a flat table to see if you can spin it.  If it spins, it is bulging.  Go
>buy a replacement battery.  Easy to swap.  Put back in the armor case.
>
>In addition, an armor case provide much better tactile retention of the
>phone.  They have been making smart phones more slick, like using glass
>instead of metal, and thinner.

Yup. That's my phone. Slick slippery thin case. I also keep a cover on mine
 for a better grip. Also when dropped on flat surfaces the case keeps the
 screen from contact. Saved my butt many times I'm sure...

>They are getting easier to slip out of
>your grip.  Almost every delivery person I see come to my door has a
>cracked screen where I see their screen as their punching in and taking
>a photo on making the delivery, or have me sign on their phone.  I
>haven't had any cracked screens ever although I admit to occasionally
>whacking the phone on a table when I got severely pissed.  
>
>I've been quite surprised the screen has not cracked from all those
>smacks.  After 7 years of my abuse, the only damage to my old phone is a
>bent back plate, but I just bought a replacement ($10) which will better
>attach to the phone with no gaps or bent-out edges to snag.  No matter
>how much I bent the old one, I couldn't get the back plate to form
>correctly and perfectly flat to the phone.  It would attach, but too
>easily pop off (and the battery drop out) on a drop.  However, while
>inside the armor case, nothing came apart on a drop or smack.  I don't
>use those decorative cases, or the ones that are just silicone, but the
>type that has a rigid back half, the silicone TPU, and a front bezel
>that snaps onto the back half.  Without the armor case, I have fumbled
>the shiny, smooth, slippery bare phone too often.  Maybe my dexterity
>has deteriorated with age, and the armor case helps to grab the phone.
>
>> And I think for many folks when the battery fails the phone is
>> obsolete anyway. It certainly will be so in my case...
>
>That was the phrase I couldn't remember: planned obsolescence.  Yeah,
>lots of users don't even buy phones, or get them very cheap, but
>bundling the deal with a carrier.  So, they're used to swapping out or
>trading in their phones about every 3 years, on average.  I'm not
>average.  I'm also not nomophobic.  All this 2FA security theater is
>premised on smart phone dependency, like the thing is grafted to its
>owner.

If I get a 2FA request I didn't make I know someone has my password and is
 trying it out and I should change things quick. That's another advantage of
 2FA I forgot to mention to micky. 

>Only because my old Android 8 is getting abandoned by apps with higher
>minimal OS requirements am I now considering replacing my 7 year phone
>(which was released 9 years ago).  I could manage without 5G, and
>survive on just 4G (not even 4G LTE).  Twould be nice to have a faster
>chipset and CPU, and more RAM, but then I don't leave apps running nor
>run many at the same time.  I use web browsers that actually have an
>Exit (unload) option instead of left loaded in memory in the background
>awaiting for whenever the OS decides it needs the memory for a newly
>loaded app (Android is just so rude regarding unloads all to pretend the
>platform is faster than it really is), but then I don't leave the web
>browser, or any other program, running on my desktop, either.  There is
>64 GB internal storage, and I added a 128 GB uSD card, yet over the 7
>years only used half the internal RAM, and nothing on the uSD card.  I
>had offline maps stored on the uSD for awhile (for the Here[WeGo] map
>app), which ate up 60 GB, but even then I had lots of storage space left
>over.  In looking at new phones, I'm not sure I want to pay the extra
>$150+ to go from 256 GB to 512 GB.  While I use a smart phone, I'm not
>an avid fan of them.  Seems more of technology trying to create a void
>to then fill it rather than of it filling an existing void.

I find the stuff on my phone very handy. I'm going to a grandkid's birthday
 party at an address I don't know. The phone takes me there. Text access to
 45 grandkids around the country. Want to know something? Ask it. Want to
 know where the wife is? Map shows me. Want to know what I'm doing next
 week? Check the wife's calender. Great local music with earphones.
 Worldwide internet radio station access. Etc etc etc...

I got my ham ticket in 1956 and am fluent in morse code. To think I used to
 impress people by talking to someone in Europe. 

>If I could get Android 12, or up, on my old smart phone, I wouldn't be
>looking at a replacement.  However, the likelihood of that happening,
>and having full support of all hardware with no conflicts or newly
>created deficiencies, seems dismal.  I'm also getting old enough where I
>shy away from doing it all myself.  I stopped changing my engine oil and
>filter eons ago, and instead pay someone else to do that drudge work
>hence why I'm likely to look at getting a new phone instead of trying to
>beat the old phone on an anvil to reshape it.  And I'll be putting an
>armor case on the new phone, too, but not a screen protector (I found
>those have more friction, even the glass ones, than the glass screen on
>the phone, and there are still some apps you have to swipe in from the
>side to get at their menu, but screen protectors don't go to the very
>edge of screens, or a wee bit beyond, so they interfere with side
>swiping).

Yup. I think a new phone is in my near future too...

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.mobile.android

csiph-web