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

Groups > comp.mobile.android > #57846

Re: charging policy

From 123456789 <12345@12345.com>
Newsgroups comp.mobile.android
Subject Re: charging policy
Date 2018-11-24 13:07 -0700
Organization A noiseless patient Spider
Message-ID <ptcb2n$kas$1@dont-email.me> (permalink)
References (11 earlier) <231120181640378302%nospam@nospam.invalid> <E2lB6K4YWH+bFwUs@255soft.uk> <ptbv8a.dbk.1@ID-201911.user.individual.net> <ptc05h$qn$1@dont-email.me> <241120181255005123%nospam@nospam.invalid>

Show all headers | View raw

On 11/24/2018 10:55 AM, nospam wrote:
> 123456789 <12345@12345.com> wrote:

>> And if the battery does manage to live too long a life, the (no
>> longer updated) OS gets out of date...

> for android, that's true.

Well...this IS an Android group after all. But you Apple fanbois are
still (somewhat?) welcome... ;)

> 5 year old iphones are still getting software updates.

Yes. Apple was a little more sneaky. Their updates actually made some of
those old phones slower so people would buy new ones. Course they didn't
tell anyone. When they finally got caught they made up that old battery
problem nonsense and put out an update to fix the update...

https://www.cnbc.com/2018/01/30/us-probing-apple-over-updates-that-slow-older-phones-bloomberg-report.html

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

charging policy "Linea Recta" <bleep.bleep@bleep.invalid> - 2018-11-21 18:24 +0100
  Re: charging policy Andy Burns <usenet@andyburns.uk> - 2018-11-21 17:36 +0000
    Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-21 19:02 +0100
      Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
  Re:charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-21 18:53 +0100
    Re: Re:charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-21 18:42 +0000
    Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
      Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-22 07:13 +0100
        Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 01:50 -0500
          Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-22 09:15 +0100
            Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 16:09 +0000
            Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 11:57 -0500
          Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 16:18 +0000
            Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 11:57 -0500
              Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 17:26 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 12:54 -0500
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 21:26 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 01:14 -0500
                Re: charging policy Andy Burns <usenet@andyburns.uk> - 2018-11-23 09:28 +0000
                "tl; dr" (was: Re: charging policy) "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 15:28 +0000
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
            Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 10:22 -0700
              Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-22 18:45 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 13:47 -0500
                Re: charging policy "NY" <me@privacy.net> - 2018-11-22 20:40 +0000
                Re: charging policy David Higton <dave@davehigton.me.uk> - 2018-11-22 21:29 +0000
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 21:30 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 01:14 -0500
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 15:26 +0000
                Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 16:13 +0000
                Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 19:52 +0000
                Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 21:29 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 16:40 -0500
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 21:48 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 17:06 -0500
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 22:09 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 17:23 -0500
                Re: charging policy The Real Bev <bashley101@gmail.com> - 2018-11-23 21:00 -0800
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 09:05 -0500
                Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-24 15:46 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 10:51 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 10:01 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 12:55 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 13:07 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 16:33 -0400
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 18:52 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 00:42 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 11:33 -0700
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-25 19:06 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 14:46 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 19:37 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 22:07 -0500
                Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-26 04:46 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 00:32 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 22:37 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 14:46 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 19:37 -0700
                Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-26 15:45 +0000
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 10:49 -0500
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-26 16:04 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 19:11 -0500
                Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-24 20:14 +0000
                Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 18:52 -0700
                Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 00:42 -0500
    Re: charging policy Anssi Saari <as@sci.fi> - 2018-11-26 10:36 +0200
      Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-26 16:37 +0000
  Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
  Re: charging policy 123456789 <12345@12345.com> - 2018-11-21 15:01 -0700

csiph-web