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

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

"Downloading en-US"

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

Contents

  "Downloading en-US" Stan Brown <the_stan_brown@fastmail.fm> - 2024-12-05 14:15 -0800
    Re: "Downloading en-US" Andy Burns <usenet@andyburns.uk> - 2024-12-05 22:22 +0000
      Re: "Downloading en-US" Stan Brown <the_stan_brown@fastmail.fm> - 2024-12-05 16:56 -0800
        Re: "Downloading en-US" Andy Burns <usenet@andyburns.uk> - 2024-12-06 13:50 +0000
          Re: "Downloading en-US" Frank Slootweg <this@ddress.is.invalid> - 2024-12-06 18:34 +0000
            Re: "Downloading en-US" Andy Burns <usenet@andyburns.uk> - 2024-12-06 18:51 +0000
              Re: "Downloading en-US" Stan Brown <the_stan_brown@fastmail.fm> - 2024-12-06 18:21 -0800
                Re: "Downloading en-US" Andy Burns <usenet@andyburns.uk> - 2024-12-07 08:53 +0000
                  Re: "Downloading en-US" Stan Brown <the_stan_brown@fastmail.fm> - 2024-12-07 10:00 -0800
                    Re: "Downloading en-US" Andy Burns <usenet@andyburns.uk> - 2024-12-07 18:11 +0000
                      Re: "Downloading en-US" micky <NONONOmisc07@fmguy.com> - 2024-12-07 21:30 -0500
                      Re: "Downloading en-US" Stan Brown <the_stan_brown@fastmail.fm> - 2024-12-08 06:59 -0800
                        Re: "Downloading en-US" Stan Brown <the_stan_brown@fastmail.fm> - 2024-12-08 07:41 -0800
            Re: "Downloading en-US" AJL <noemail@none.com> - 2024-12-06 19:00 +0000
              Re: "Downloading en-US" Frank Slootweg <this@ddress.is.invalid> - 2024-12-06 19:09 +0000
                Re: "Downloading en-US" AJL <noemail@none.com> - 2024-12-06 19:47 +0000
                  Re: "Downloading en-US" Chris Green <cl@isbd.net> - 2024-12-07 09:46 +0000
                Re: "Downloading en-US" micky <NONONOmisc07@fmguy.com> - 2024-12-07 12:23 -0500
                  Re: "Downloading en-US" Frank Slootweg <this@ddress.is.invalid> - 2024-12-07 18:52 +0000
                    Re: "Downloading en-US" micky <NONONOmisc07@fmguy.com> - 2024-12-07 18:32 -0500
                      Re: "Downloading en-US" Frank Slootweg <this@ddress.is.invalid> - 2024-12-08 10:10 +0000
                        Re: "Downloading en-US" micky <NONONOmisc07@fmguy.com> - 2024-12-08 09:03 -0500
                          Re: "Downloading en-US" Frank Slootweg <this@ddress.is.invalid> - 2024-12-08 18:42 +0000

Page 1 of 2  [1] 2  Next page →

#144956 — "Downloading en-US"

Google Pixel 8a, Android 14

In the settings for the default Phone app, I clicked "Call Screen ". 
That took me to a screen headed "Call Screen", as expected, but about 
the top third of the screen is now taken up by a white window with an 
orange bar containing the text "downloading en-US". The setting for 
"Automatically screen calls" is grayed out, as are its sub-settings 
"Maximum protection", "Medium protection", and "Basic protection".

It's been like that for an hour so far.

I assume it's downloading some sort of language pack, but should that 
be taking so long? If not, any suggestions for troubleshooting?

(I did try googling, but the search terms I could think of didn't 
lead anywhere useful.)

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

[toc] | [next] | [standalone]

#144957

Stan Brown wrote:

> Google Pixel 8a, Android 14

Not 15?

> In the settings for the default Phone app, I clicked "Call Screen ".
> That took me to a screen headed "Call Screen", as expected, but about
> the top third of the screen is now taken up by a white window with an
> orange bar containing the text "downloading en-US". The setting for
> "Automatically screen calls" is grayed out, as are its sub-settings
> "Maximum protection", "Medium protection", and "Basic protection".
> 
> It's been like that for an hour so far.

I don't remember a huge download to enable screening, maybe I already 
had the language stuff?  I don't use the screening on real human 
callers, but when I've been put on hold i have no qualms using it.

> I assume it's downloading some sort of language pack, but should that
> be taking so long? If not, any suggestions for troubleshooting?
> 
> (I did try googling, but the search terms I could think of didn't
> lead anywhere useful.)

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

#144963

Just while I was typing this followup below, the "en-US" download 
finished, about 3½ hours after it started. AT 25 MB/second, that 
would make it 315 GB, which seems absurd, so something else must have 
been going on. Maybe Google uses a dedicated server for these 
language packs, and it's really slow?

On Thu, 5 Dec 2024 22:22:22 +0000, Andy Burns wrote:
> Stan Brown wrote:
> 
> > Google Pixel 8a, Android 14
> 
> Not 15?

Nope, I checked. The phone is new as of Tuesday, and it did an update 
then, but that must have been an update to 14. I didn't really pay 
attention. 

I got a text an hour ago from "Silent": "Get Android 15 now. Tap to 
learn more and download."  No, that's not sketchy at all, at all. :-)
I'll check Settings » System. Yup, there's an update to Android 15 
pending. I tapped "Download and Install".

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

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

#144989

Stan Brown wrote:

> Yup, there's an update to Android 15
> pending. I tapped "Download and Install".

You should have the option to limit battery charge to 80% now.

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

#144996

Andy Burns <usenet@andyburns.uk> wrote:
> Stan Brown wrote:
> 
> > Yup, there's an update to Android 15
> > pending. I tapped "Download and Install".
> 
> You should have the option to limit battery charge to 80% now.

  Hmm, you mean that Pixels did not have that before? Samsungs got that
(in Samsung's case 85%) with Android 12 in April 2022.

  But indeed, my archive for this group has a post mine of June 14 2022,
refering a post from John McGaw (<iyNpK.140772$vAW9.139164@fx10.iad>)
saying:
  
> No such thing on my "pure Android" Pixel 6 Pro which leads me to believe
> that the option is something that Samsung added for their devices."

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

#144998

Frank Slootweg wrote:

> Andy Burns wrote:
>
>> You should have the option to limit battery charge to 80% now.
> 
>    Hmm, you mean that Pixels did not have that before? 

That's right, before now they either had charge fast to 100%
or charge slow to 100% in time for your morning alarm, now they can stop 
at 80% as a third option.

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

#145014

On Fri, 6 Dec 2024 18:51:18 +0000, Andy Burns wrote:
> 
> Frank Slootweg wrote:
> 
> > Andy Burns wrote:
> >
> >> You should have the option to limit battery charge to 80% now.
> > 
> >    Hmm, you mean that Pixels did not have that before? 
> 
> That's right, before now they either had charge fast to 100%
> or charge slow to 100% in time for your morning alarm, now they can stop 
> at 80% as a third option.

Where is that in Settings?

I _am_ on Android 15 now, but I don't see the setting for stopping 
charging at 80%. I did Settings searches for "charge" and "charging" 
but the few hits didn't include that.

Hmm ... I googled after writing that paragraph, and it looks like the 
80% is not an option but a limit on all Android 15 Pixel 8a phones 
(and, I assume, a list of other models).

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

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

#145021

Stan Brown wrote:

> Andy Burns wrote:
>
>> That's right, before now they either had charge fast to 100%
>> or charge slow to 100% in time for your morning alarm, now they can stop
>> at 80% as a third option.
> 
> Where is that in Settings?

settings, battery, charge optimisation

> I _am_ on Android 15 now, but I don't see the setting for stopping
> charging at 80%. I did Settings searches for "charge" and "charging"
> but the few hits didn't include that.
> 
> Hmm ... I googled after writing that paragraph, and it looks like the
> 80% is not an option but a limit on all Android 15 Pixel 8a phones
> (and, I assume, a list of other models).

You did say you have an 8a, right?

Given you were over a month "late" getting android 15, have  you tried 
checking for another upgrade to get the december feature drop version 
(AP4A.241205.013)

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

#145035

On Sat, 7 Dec 2024 08:53:23 +0000, Andy Burns wrote:
> 
> Stan Brown wrote:
> 
> > Andy Burns wrote:
> >
> >> That's right, before now they either had charge fast to 100%
> >> or charge slow to 100% in time for your morning alarm, now they can stop
> >> at 80% as a third option.
> > 
> > Where is that in Settings?
> 
> settings, battery, charge optimisation

Thank you. I don't have that item. Predictable since a search for 
"charge" didn't return it as a result, but I've looked directly to 
confirm.
 
> > I _am_ on Android 15 now, but I don't see the setting for stopping
> > charging at 80%. I did Settings searches for "charge" and "charging"
> > but the few hits didn't include that.
> > 
> > Hmm ... I googled after writing that paragraph, and it looks like the
> > 80% is not an option but a limit on all Android 15 Pixel 8a phones
> > (and, I assume, a list of other models).
> 
> You did say you have an 8a, right?

Yes, brand new this past Tuesday after my Samsung A54 was stolen in a 
smash-and-grab.

> Given you were over a month "late" getting android 15, have  you tried 
> checking for another upgrade to get the december feature drop version 
> (AP4A.241205.013)

System » Software updates said "your Pixel is up to date". I don't 
really understand the structure of Android updates or where to search 
for them manually and how to apply one that I want.

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

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

#145036

Stan Brown wrote:

> System » Software updates said "your Pixel is up to date".

Sometimes it lies, then if you do "Check for update" it acts surprised 
and admits there is an update after all.

> I don't really understand the structure of Android updates or where
> to search for them manually and how to apply one that I want.

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

#145061

In comp.mobile.android, on Sat, 7 Dec 2024 18:11:31 +0000, Andy Burns
<usenet@andyburns.uk> wrote:

>
>Stan Brown wrote:
>
>> System » Software updates said "your Pixel is up to date".
>
>Sometimes it lies, then if you do "Check for update" it acts surprised 
>and admits there is an update after all.

Some say that Android had an abusive childhood, when it learned to lie
to its parents.  Even now that it's famous, it can't seem to stop. 
>
>> I don't really understand the structure of Android updates or where
>> to search for them manually and how to apply one that I want.

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

#145068

On Sat, 7 Dec 2024 18:11:31 +0000, Andy Burns wrote:
> Stan Brown wrote:
> 
> > System » Software updates said "your Pixel is up to date".
> 
> Sometimes it lies, then if you do "Check for update" it acts surprised 
> and admits there is an update after all.

Thanks for the tip. This was one of those times, but I would never 
have guessed without your prompt.

It's a 774 MB feature update, in progress now, and I'll bet dollars 
to donuts it contains the battery 80% setting.

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

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

#145071

On Sun, 8 Dec 2024 06:59:43 -0800, Stan Brown wrote:
> On Sat, 7 Dec 2024 18:11:31 +0000, Andy Burns wrote:

> > Sometimes it lies, then if you do "Check for update" it acts surprised 
> > and admits there is an update after all.
> 
> Thanks for the tip. This was one of those times, but I would never 
> have guessed without your prompt.
> 
> It's a 774 MB feature update, in progress now, and I'll bet dollars 
> to donuts it contains the battery 80% setting.

And it did. After the update finished, I found that Battery » Charge 
Optimization is now part of Settings, and I set it to charge only to 
80%.

-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

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

#145000

On 12/6/24 11:34 AM, Frank Slootweg wrote:
>Andy Burns <usenet@andyburns.uk> wrote:
>> Stan Brown wrote:
>> 
>> > Yup, there's an update to Android 15
>> > pending. I tapped "Download and Install".
>> 
>> You should have the option to limit battery charge to 80% now.
>
>  Hmm, you mean that Pixels did not have that before? Samsungs got that
>(in Samsung's case 85%) with Android 12 in April 2022.
>
>  But indeed, my archive for this group has a post mine of June 14 2022,
>refering a post from John McGaw (<iyNpK.140772$vAW9.139164@fx10.iad>)
>saying:
>  
>> No such thing on my "pure Android" Pixel 6 Pro which leads me to believe
>> that the option is something that Samsung added for their devices."

The capability may be overrated. I've always charged my Samsung Galaxy S10+
 to 100% and it just passed 5 years with no 'noticeable' battery degradation
 for 'my' use. A survey of one of course and as always YMMV...

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

#145001

AJL <noemail@none.com> wrote:
> On 12/6/24 11:34 AM, Frank Slootweg wrote:
> >Andy Burns <usenet@andyburns.uk> wrote:
> >> Stan Brown wrote:
> >> 
> >> > Yup, there's an update to Android 15
> >> > pending. I tapped "Download and Install".
> >> 
> >> You should have the option to limit battery charge to 80% now.
> >
> >  Hmm, you mean that Pixels did not have that before? Samsungs got that
> >(in Samsung's case 85%) with Android 12 in April 2022.
> >
> >  But indeed, my archive for this group has a post mine of June 14 2022,
> >refering a post from John McGaw (<iyNpK.140772$vAW9.139164@fx10.iad>)
> >saying:
> >  
> >> No such thing on my "pure Android" Pixel 6 Pro which leads me to believe
> >> that the option is something that Samsung added for their devices."
> 
> The capability may be overrated. I've always charged my Samsung Galaxy S10+
>  to 100% and it just passed 5 years with no 'noticeable' battery degradation
>  for 'my' use. A survey of one of course and as always YMMV...

  After having ruined, or seen ruined, my share of batteries (mostly
laptop and several small 'gadgets'), I'd rather be safe than sorry. Our
Samsung Galaxy A51 phones are a bit over 4 years old and we hope to have
some more years life in them. But, as you say, a survey of one and a
sample of only a few, so YMMV/YMWV.

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

#145002

On 12/6/24 12:09 PM, Frank Slootweg wrote:
>AJL <noemail@none.com> wrote:
>> On 12/6/24 11:34 AM, Frank Slootweg wrote:
>> >Andy Burns <usenet@andyburns.uk> wrote:
>> >> Stan Brown wrote:
>> >> 
>> >> > Yup, there's an update to Android 15
>> >> > pending. I tapped "Download and Install".
>> >> 
>> >> You should have the option to limit battery charge to 80% now.
>> >
>> >  Hmm, you mean that Pixels did not have that before? Samsungs got that
>> >(in Samsung's case 85%) with Android 12 in April 2022.
>> >
>> >  But indeed, my archive for this group has a post mine of June 14 2022,
>> >refering a post from John McGaw (<iyNpK.140772$vAW9.139164@fx10.iad>)
>> >saying:
>> >  
>> >> No such thing on my "pure Android" Pixel 6 Pro which leads me to believe
>> >> that the option is something that Samsung added for their devices."
>> 
>> The capability may be overrated. I've always charged my Samsung Galaxy S10+
>>  to 100% and it just passed 5 years with no 'noticeable' battery degradation
>>  for 'my' use. A survey of one of course and as always YMMV...
>
>  After having ruined, or seen ruined, my share of batteries (mostly
>laptop and several small 'gadgets'), I'd rather be safe than sorry. 

Like Micky my LTs all stay plugged in most of the time, often even when
 using them. So I guess I wouldn't notice a battery problem until the
 software complained. As long as one holds a charge through a long crap I'm
 happy.

>Our
>Samsung Galaxy A51 phones are a bit over 4 years old and we hope to have
>some more years life in them. But, as you say, a survey of one and a
>sample of only a few, so YMMV/YMWV.

Like most of my toys I get tired of them and want to try something new so
 don't keep them as long as you do. My grandkids have never complained of
 the donations. Win-win. Dunno why I've kept the phone so long...

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

#145022

AJL <noemail@none.com> wrote:
> >  After having ruined, or seen ruined, my share of batteries (mostly
> >laptop and several small 'gadgets'), I'd rather be safe than sorry. 
> 
> Like Micky my LTs all stay plugged in most of the time, often even when
> using them. So I guess I wouldn't notice a battery problem until the
> software complained. As long as one holds a charge through a long crap I'm
> happy.
> 
That makes a bit of a nonsense of a 'mobile' phone doesn't it! :-)

-- 
Chris Green
·

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

#145034

In comp.mobile.android, on 6 Dec 2024 19:09:19 GMT, Frank Slootweg
<this@ddress.is.invalid> wrote:

>AJL <noemail@none.com> wrote:
>> On 12/6/24 11:34 AM, Frank Slootweg wrote:
>> >Andy Burns <usenet@andyburns.uk> wrote:
>> >> Stan Brown wrote:
>> >> 
>> >> > Yup, there's an update to Android 15
>> >> > pending. I tapped "Download and Install".
>> >> 
>> >> You should have the option to limit battery charge to 80% now.
>> >
>> >  Hmm, you mean that Pixels did not have that before? Samsungs got that
>> >(in Samsung's case 85%) with Android 12 in April 2022.
>> >
>> >  But indeed, my archive for this group has a post mine of June 14 2022,
>> >refering a post from John McGaw (<iyNpK.140772$vAW9.139164@fx10.iad>)
>> >saying:
>> >  
>> >> No such thing on my "pure Android" Pixel 6 Pro which leads me to believe
>> >> that the option is something that Samsung added for their devices."
>> 
>> The capability may be overrated. I've always charged my Samsung Galaxy S10+
>>  to 100% and it just passed 5 years with no 'noticeable' battery degradation
>>  for 'my' use. A survey of one of course and as always YMMV...
>
>  After having ruined, or seen ruined, my share of batteries (mostly
>laptop and several small 'gadgets'), I'd rather be safe than sorry. Our
>Samsung Galaxy A51 phones are a bit over 4 years old and we hope to have
>some more years life in them. But, as you say, a survey of one and a
>sample of only a few, so YMMV/YMWV.

No battery stories with phones but with a laptop, every time I'd run the
battery to near zero** (because the charger came unplugged and I didn't
notice it, after re-charging, going by Nirsoft's free BatteryInfoView,
I'd have lost 10% from Battery Health.  Other than those times, it
didn't go down, but 3 or 4 times down to near zero and the battery
wouldn't take a charge, wouldn't start the laptop.  Coudn't find for
sale a battery as big as the original, maybe only 80%, but it's now at
100% battery health of that 80%.  

**Hmmm.  Oops, I guess this is the opposite issue of only charging to
80%.  

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

#145038

micky <NONONOmisc07@fmguy.com> wrote:
[...]

> No battery stories with phones but with a laptop, every time I'd run the
> battery to near zero** (because the charger came unplugged and I didn't
> notice it, after re-charging, going by Nirsoft's free BatteryInfoView,
> I'd have lost 10% from Battery Health.  Other than those times, it
> didn't go down, but 3 or 4 times down to near zero and the battery
> wouldn't take a charge, wouldn't start the laptop.  Coudn't find for
> sale a battery as big as the original, maybe only 80%, but it's now at
> 100% battery health of that 80%.  

  Note that, as I've mentioned before, general purpose utilities like
BatteryInfoView don't tell the truth (read: cannot tell the truth). So
always try to also use a utility from the manufacturer of the laptop.

  For example, for my laptop, BatteryInfoView says:

"Full Charged Capacity	38,397 mWh
 Designed Capacity	38,397 mWh
 Battery Health		100.0%"

  So I might think "Great, still 100% of designed capacity!", but that
can't be, because the laptop is 2 years and 3 months old.

  And indeed, it can't be correct, because the official specs say "41
Wh", so it's 93.7% of designed capacity, not 100%. Not bad, but not
100%.

  Now if I run the "HP Battery Check" utility, i.e. the utility which
came with the laptop and is designed for the laptop, it says:

"Design Capacity:	41 WHr
 Full Charge Capacity:	38 WHr (93%)"
  
  So it gives the same Full Charge Capacity as BatteryInfoView (rounded
down to the nearest integer), but gives the *real* Design Capacity of 41
WHr, instead of the fake/wrong one which BatteryInfoView gave and the
correct battery health of 93%.

  Moral: I use both BatteryInfoView *and* the HP Battery Check utility.
BatteryInfoView gives me more information - for example the Battery Log
over time -, but the limited information which the HP Battery Check
utility gives, is more_reliable/correct.

> **Hmmm.  Oops, I guess this is the opposite issue of only charging to
> 80%.  

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

#145047

In comp.mobile.android, on 7 Dec 2024 18:52:57 GMT, Frank Slootweg
<this@ddress.is.invalid> wrote:

>micky <NONONOmisc07@fmguy.com> wrote:
>[...]
>
>> No battery stories with phones but with a laptop, every time I'd run the
>> battery to near zero** (because the charger came unplugged and I didn't
>> notice it, after re-charging, going by Nirsoft's free BatteryInfoView,
>> I'd have lost 10% from Battery Health.  Other than those times, it
>> didn't go down, but 3 or 4 times down to near zero and the battery
>> wouldn't take a charge, wouldn't start the laptop.  Coudn't find for
>> sale a battery as big as the original, maybe only 80%, but it's now at
>> 100% battery health of that 80%.  
>
>  Note that, as I've mentioned before, general purpose utilities like
>BatteryInfoView don't tell the truth (read: cannot tell the truth). So
>always try to also use a utility from the manufacturer of the laptop.

Checking, I see that Acer does have a way to check, so I ran it, and it
wrote a file, and going to see the file, I saw another similar file from
last June.  I see that I also did this last June, probably to decide if
I needed a new battery.  Who remembers these things. But I did need one.
My old battery had gone from 
Battery capacity history 
PERIOD	                FULL CHARGE CAPACITY 	DESIGN CAPACITY 
2021-03-18 - 2021-03-30	34,425 mWh       	37,000 mWh 
to (with many readings in between)
2024-06-18	        25,500 mWh 	        37,000 mWh 

I might have gotten the laptop at that first data, 3/18/21.  It seems
longer but that the trip I know I took it on.  So I only had it 3.5
years. It seems longer. 

>  For example, for my laptop, BatteryInfoView says:
>
>"Full Charged Capacity	38,397 mWh
> Designed Capacity	38,397 mWh
> Battery Health		100.0%"
>
>  So I might think "Great, still 100% of designed capacity!", but that
>can't be, because the laptop is 2 years and 3 months old.
>
>  And indeed, it can't be correct, because the official specs say "41
>Wh", so it's 93.7% of designed capacity, not 100%. Not bad, but not
>100%.
>
>  Now if I run the "HP Battery Check" utility, i.e. the utility which
>came with the laptop and is designed for the laptop, it says:
>
>"Design Capacity:	41 WHr
> Full Charge Capacity:	38 WHr (93%)"
>  
>  So it gives the same Full Charge Capacity as BatteryInfoView (rounded
>down to the nearest integer), but gives the *real* Design Capacity of 41
>WHr, instead of the fake/wrong one which BatteryInfoView gave and the
>correct battery health of 93%.
>
>  Moral: I use both BatteryInfoView *and* the HP Battery Check utility.
>BatteryInfoView gives me more information - for example the Battery Log
>over time -, but the limited information which the HP Battery Check
>utility gives, is more_reliable/correct.

thanks. 

>> **Hmmm.  Oops, I guess this is the opposite issue of only charging to
>> 80%.  

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web