Sometimes my 5" smartphone phone starts quickly and sometimes it takes
at least 3 times as long. very recent version of Android.

Any idea why?

Even when it takes a long time, I get no messages about updating
programs.

I only use the phone for a couple hours every 1 to 3 days, and I turn it
off in between.

micky <NONONOmisc07@fmguy.com> wrote:

> Sometimes my 5" smartphone phone starts quickly and sometimes it takes
> at least 3 times as long. very recent version of Android.
>
> Any idea why?
>
> Even when it takes a long time, I get no messages about updating
> programs.
>
> I only use the phone for a couple hours every 1 to 3 days, and I turn it
> off in between.

So, are you simply sleeping the phone (having it go dark), or are you
always powering it down (using the Power button menu)?

Quickly is how long? Then we'd know what is "3 times as long", too. Is
the phone's battery low when it takes a long time to boot?

5" smartphone is devoid of brand, family series, and model. You thought
only one brand and model has a 5" screen, or is 5" wide, or 5" long, or
whatever 5" refers to? C'mon, Micky, you've been berated before for
being deliberately vague.

In comp.mobile.android, on Wed, 21 Jul 2021 20:09:36 -0500, VanguardLH
<V@nguard.LH> wrote:

>micky <NONONOmisc07@fmguy.com> wrote:
>
>> Sometimes my 5" smartphone phone starts quickly and sometimes it takes
>> at least 3 times as long. very recent version of Android.
>>
>> Any idea why?
>>
>> Even when it takes a long time, I get no messages about updating
>> programs.
>>
>> I only use the phone for a couple hours every 1 to 3 days, and I turn it
>> off in between.
>
>So, are you simply sleeping the phone (having it go dark), or are you
>always powering it down (using the Power button menu)?

I turn it off.

>Quickly is how long? Then we'd know what is "3 times as long", too. Is
>the phone's battery low when it takes a long time to boot?

The battery is almost always more than 80%, but maybe that's related so
I will keep my eye on it for the next times it takes a long time to turn
on.
>
>5" smartphone is devoid of brand, family series, and model. You thought
>only one brand and model has a 5" screen, or is 5" wide, or 5" long, or
>whatever 5" refers to? C'mon, Micky, you've been berated before for
>being deliberately vague.

Only by you. You always ask this type of questions. When I think the
details would matter, I give them before you ask.

Do you actually know details of brands, families, and models so that you
could give a different answer based on those things? I don't think you
or almost anyone does. I don't think anyone outside of the engineering
department of one of the makers knows those things and a tiny number of
others.

micky <NONONOmisc07@fmguy.com> wrote:

> VanguardLH <V@nguard.LH> wrote:
>
>> micky <NONONOmisc07@fmguy.com> wrote:
>>
>>> Sometimes my 5" smartphone phone starts quickly and sometimes it takes
>>> at least 3 times as long. very recent version of Android.
>>>
>>> Any idea why?
>>>
>>> Even when it takes a long time, I get no messages about updating
>>> programs.
>>>
>>> I only use the phone for a couple hours every 1 to 3 days, and I turn it
>>> off in between.
>>
>> C'mon, Micky, you've been berated before for being deliberately vague.
>
> Only by you. You always ask this type of questions. When I think the
> details would matter, I give them before you ask.

Nope, not just me. That has NEVER been your modus operandi, you never
provide details until prodded, and why some think you're a troll.

> Do you actually know details of brands, families, and models so that you
> could give a different answer based on those things? I don't think you
> or almost anyone does. I don't think anyone outside of the engineering
> department of one of the makers knows those things and a tiny number of
> others.

Details can indicate if a brand or model likes to present a startup logo
that does nothing but advertise while wasting boot time. It would also
indicate the age of your phone (when it got released), and which you
don't provide.

The OS is stored on internal storage (NAND/EMMC chip), and even you know
those are self-destructive devices. They degrade with writes. To
compensate, remapping is used, but accessing an address which remaps to
elsewhere adds time. The more remapping as the chip ages the more time
to access the original data redirected to elsewhere. You can try to
install apps (or part of them) on the SD card, if you have one, along
with any frequently accessed data, like offline maps that get updated,
or pics, or videos. However, SD cards degrade over time, too. We don't
know if you added an SD card, and how old it is, and its volume of
writes. Flash storage is self-destructive. The older it gets, the
slower it gets. Wear leveling only works for a while. It does not
eliminate the wear.

Batteries go bad over time, too, and some go bad faster than others. My
phone's battery is a poor design that degrades quickly. When new, I get
just over a day of constant up-time. After a year, I'll start noticing
it's down to about half a day for contant up-time, and it continues to
drop. No matter how the charging cycles are changed trying to save the
battery, the battery just doesn't last. If I leave my phone on, and it
powers off because the battery got down to 3%, it won't restart next
time because there's not enough power in the battery. It might start,
but fails during the boot. If I plug in before booting, it sometimes
starts to boot, gets enough power, and continues okay, but sometimes it
detects the capacity is still too low (not enough time on the charger to
get above 5%), and fails the boot. Not all phones will immediately show
their battery's charge level when booting. Instead of just trying to
power on the phone, leave it off and plug into a charger. The phone's
screen should show the current charge level. Then power on to measure
the boot time. That might indicate if a low battery is causing a slow
boot.

If your phone has a removable battery (again something that could be
researched by responders if you had provided details), remove the back
cover of the phone to check if the battery is swollen. I've had one
phone that split apart due to a battery getting pregnant. On another, I
was having trouble reinstalling an armor case because the phone's back
cover was bulging out due to a swollen battery.

We also don't know what apps are registered for load on startup. Some
may be checking for updates. Even the Play store app checks for
updates. Updating takes CPU cycles. I've never had my phone interrupt
me with messages that an app is updating. Only a few apps I have will
add a notification that they are updating, like Here[WeGo] Maps app when
it is updating its offline maps, and all I see is a notification bar
icon, not a popup message about updating.

We could guess you have cleanup apps, and they trigger sometimes during
boot. Or you could be using an app killer that terminates backgrounded
apps, but you don't realize some are "sticky" apps: if the OS sees they
are unloaded, the OS will reload them. Killer app kills an app, OS
reloads the app.

Instead of just shutting down Android and powering off the phone, power
down but select to restart in safe mode. While powered on, press and
hold the Power button to get the power options appear: Power Off,
Airplane Mode, and Restart. Long-press the Power Off option to get the
"Reboot to safe mode" dialog. When the phone restarts, measure how long
until Android is ready (you didn't mention how you measure "ready").
On Android older than 4.1 (remember, we don't know as those are details
you don't mention), you power off by tapping the Power Off option, but
when you next boot by long-pressing the Power button and releasing it,
wait for the logo to appear to then concurrently press both the Volume
Up and Volume Down buttons to enter safe mode. On some phones, you just
hold the Volume Down button, not both Volume Up and Down, and another
reason to give details!

Safe mode eliminates all those apps you installed, and only loads the
apps that came bundled with the phone. It's less destructive to the use
of your phone and its setup than doing a factory reset. However, if you
don't have many apps installed, a reset might show if startup apps are
causing the erratic boot times. However, to prevent the Play Store app
from reinstalling all your old apps after a reset, clear out all apps
listed in the Library section of the Play Store app; else, the app will
start reinstalling your library of apps. In some phones, you go to
Settings -> Backup [& reset], and uncheck the "automatic restore"
option. Some phones this way, some phones that way, but your
unidentified phone is you doing the research on how to do a reset
*without* automatically restoring the apps you installed (since those
could be causing the erratic boot time).

If you give details, someone that owns the same phone might provide more
accurate details on how to the do the above suggestions. If I, or
anyone else, doesn't have the same phone, best they can do are general
suggestions, and perhaps research the manual and online articles to read
or link those solutions in their replies.

In article <cex13a3vuith$.dlg@v.nguard.lh>, VanguardLH <V@nguard.LH>
wrote:

> >>> Sometimes my 5" smartphone phone starts quickly and sometimes it takes
> >>> at least 3 times as long. very recent version of Android.
> >>>
> >>> Any idea why?

....

> > Do you actually know details of brands, families, and models so that you
> > could give a different answer based on those things? I don't think you
> > or almost anyone does. I don't think anyone outside of the engineering
> > department of one of the makers knows those things and a tiny number of
> > others.
>
> Details can indicate if a brand or model likes to present a startup logo
> that does nothing but advertise while wasting boot time.

displaying a logo does *not* waste boot time. it's there so that the
user knows something is going on while booting continues, plus it looks
nice.

> It would also
> indicate the age of your phone (when it got released), and which you
> don't provide.

the age of the phone has *no* effect on boot time.

> The OS is stored on internal storage (NAND/EMMC chip), and even you know
> those are self-destructive devices. They degrade with writes. To
> compensate, remapping is used, but accessing an address which remaps to
> elsewhere adds time. The more remapping as the chip ages the more time
> to access the original data redirected to elsewhere.

that is completely false. wear leveling, what you call remapping, does
not affect the speed of the storage at all, nor do you understand how
wear leveling even works.

> You can try to
> install apps (or part of them) on the SD card, if you have one, along
> with any frequently accessed data, like offline maps that get updated,
> or pics, or videos. However, SD cards degrade over time, too. We don't
> know if you added an SD card, and how old it is, and its volume of
> writes.

sd cards won't affect boot time.

> Flash storage is self-destructive. The older it gets, the
> slower it gets.

false.

> Wear leveling only works for a while. It does not
> eliminate the wear.

wear leveling does not stop working. what it does is extend the useful
life of the flash storage.

> Batteries go bad over time, too, and some go bad faster than others. My
> phone's battery is a poor design that degrades quickly. When new, I get
> just over a day of constant up-time. After a year, I'll start noticing
> it's down to about half a day for contant up-time, and it continues to
> drop.

that just means your battery is failing quicker than normal, not that
it's a poor design.

> No matter how the charging cycles are changed trying to save the
> battery, the battery just doesn't last. If I leave my phone on, and it
> powers off because the battery got down to 3%, it won't restart next
> time because there's not enough power in the battery. It might start,
> but fails during the boot. If I plug in before booting, it sometimes
> starts to boot, gets enough power, and continues okay, but sometimes it
> detects the capacity is still too low (not enough time on the charger to
> get above 5%), and fails the boot. Not all phones will immediately show
> their battery's charge level when booting. Instead of just trying to
> power on the phone, leave it off and plug into a charger. The phone's
> screen should show the current charge level. Then power on to measure
> the boot time. That might indicate if a low battery is causing a slow
> boot.

battery charge level does not affect boot time, other than possibly
needing to be recharged to a certain level to begin the boot process if
it's extremely low. otherwise, connecting it to a charger will suffice.

> If your phone has a removable battery (again something that could be
> researched by responders if you had provided details), remove the back
> cover of the phone to check if the battery is swollen. I've had one
> phone that split apart due to a battery getting pregnant. On another, I
> was having trouble reinstalling an armor case because the phone's back
> cover was bulging out due to a swollen battery.

that has nothing to do with boot time.

> We also don't know what apps are registered for load on startup. Some
> may be checking for updates. Even the Play store app checks for
> updates. Updating takes CPU cycles. I've never had my phone interrupt
> me with messages that an app is updating. Only a few apps I have will
> add a notification that they are updating, like Here[WeGo] Maps app when
> it is updating its offline maps, and all I see is a notification bar
> icon, not a popup message about updating.

that happens in the background and does not affect boot time.

rest snipped.

VanguardLH wrote on 22.07.2021 08:27
> Nope, not just me. That has NEVER been your modus operandi, you never
> provide details until prodded, and why some think you're a troll.

VanguardLH,

Have you ever seen "micky" post on the home repair newsgroup?
In that newsgroup he said outright he had a god given right to troll.
I suspect most of the oddball nyms on this newsgroup are "micky" trolls.

Anyone who asks dumb questions but then who never gives enough detail to
actually solve them is likely one of the "micky" nyms.

If he ever cared to actually solve them, he'd provide more details.
Why does "micky" troll?

I don't know but look on alt.home.repair and you'll see he's a troll who has
repeatedly said he will troll off topic crap on that ng all he wants.
<https://groups.google.com/g/alt.home.repair>

He told me nobody can stop him, and that's true, but not a good reason.
Since I speak the truth, look here for the evidence:
<https://groups.google.com/g/alt.home.repair/search?q=micky>

Almost _nothing_ "micky" ever posts is even remotely on topic.
Why do these trolls do this?

I don't know why.
They get some kind of thrill out of wasting our valuable time I guess.

On 22/07/2021 12.43, nospam wrote:
> In article <cex13a3vuith$.dlg@v.nguard.lh>, VanguardLH <V@nguard.LH>
> wrote:

....

>> You can try to
>> install apps (or part of them) on the SD card, if you have one, along
>> with any frequently accessed data, like offline maps that get updated,
>> or pics, or videos. However, SD cards degrade over time, too. We don't
>> know if you added an SD card, and how old it is, and its volume of
>> writes.
>
> sd cards won't affect boot time.

Yes, they do. Some applications that start automatically scan the
contents on the storage, for files they should know about, like movies
or photos. And while they do that, the machine is busy and goes slow
about responding to the user.

I have a tablet that when has been sitting idle for days and I pick it
up, that instant it decides to start every background application - like
news apps - and does not respond for a minute or two.

....

>> No matter how the charging cycles are changed trying to save the
>> battery, the battery just doesn't last. If I leave my phone on, and it
>> powers off because the battery got down to 3%, it won't restart next
>> time because there's not enough power in the battery. It might start,
>> but fails during the boot. If I plug in before booting, it sometimes
>> starts to boot, gets enough power, and continues okay, but sometimes it
>> detects the capacity is still too low (not enough time on the charger to
>> get above 5%), and fails the boot. Not all phones will immediately show
>> their battery's charge level when booting. Instead of just trying to
>> power on the phone, leave it off and plug into a charger. The phone's
>> screen should show the current charge level. Then power on to measure
>> the boot time. That might indicate if a low battery is causing a slow
>> boot.
>
> battery charge level does not affect boot time, other than possibly
> needing to be recharged to a certain level to begin the boot process if
> it's extremely low. otherwise, connecting it to a charger will suffice.

You like absolute negations, don't you?

Low battery + a system that can throttle down the machine to conserve
battery when it is low ==> slow machine with low battery.

--
Cheers,
Carlos E.R.

In article <vbaoshxtf1.ln2@minas-tirith.valinor>, Carlos E. R.
<robin_listas@es.invalid> wrote:

> > sd cards won't affect boot time.
>
> Yes, they do. Some applications that start automatically scan the
> contents on the storage, for files they should know about, like movies
> or photos. And while they do that, the machine is busy and goes slow
> about responding to the user.

launching apps happens after the os has booted, and user response time
is a function of the device, not that it's using an sd card.

>
> Low battery + a system that can throttle down the machine to conserve
> battery when it is low ==> slow machine with low battery.

that doesn't affect boot time.

if the battery is dead, it will need to be charged so that the device
can boot, but that is not part of the boot process. any device with a
dead battery is going to need to be recharged.

In comp.mobile.android, on Thu, 22 Jul 2021 16:02:07 +0200, "Carlos E.
R." <robin_listas@es.invalid> wrote:

>
>> battery charge level does not affect boot time, other than possibly
>> needing to be recharged to a certain level to begin the boot process if
>> it's extremely low. otherwise, connecting it to a charger will suffice.

Besides what Carlos said, mabye a charger will suffice, but if no
charger is attached, then it doesn't suffice, and I usually start the
phone when I'm on my way out of the house, or sitting somewhere after
I've left the house. No charger connected.
>
>You like absolute negations, don't you?
>
>Low battery + a system that can throttle down the machine to conserve
>battery when it is low ==> slow machine with low battery.
>
>--
>Cheers,
> Carlos E.R.

In comp.mobile.android, on Thu, 22 Jul 2021 01:27:56 -0500, VanguardLH
<V@nguard.LH> wrote:

>micky <NONONOmisc07@fmguy.com> wrote:
>
>> VanguardLH <V@nguard.LH> wrote:
>>
>>> micky <NONONOmisc07@fmguy.com> wrote:
>>>
>>>> Sometimes my 5" smartphone phone starts quickly and sometimes it takes
>>>> at least 3 times as long. very recent version of Android.
>>>>
>>>> Any idea why?
>>>>
>>>> Even when it takes a long time, I get no messages about updating
>>>> programs.
>>>>
>>>> I only use the phone for a couple hours every 1 to 3 days, and I turn it
>>>> off in between.
>>>
>>> C'mon, Micky, you've been berated before for being deliberately vague.
>>
>> Only by you. You always ask this type of questions. When I think the
>> details would matter, I give them before you ask.
>
>Nope, not just me. That has NEVER been your modus operandi, you never
>provide details until prodded, and why some think you're a troll.
>
>> Do you actually know details of brands, families, and models so that you
>> could give a different answer based on those things? I don't think you
>> or almost anyone does. I don't think anyone outside of the engineering
>> department of one of the makers knows those things and a tiny number of
>> others.
>
>Details can indicate if a brand or model likes to present a startup logo
>that does nothing but advertise while wasting boot time. It would also

If there werre a logo that appeared some of the time but not other
times, a) I would mention it, b) I would already know one reason it
takes longer to boot some of the time.

If there is always a logo, then that is not the reason the boot time
varies.

BTW, there is no logo.

>indicate the age of your phone (when it got released), and which you
>don't provide.

I'd be just as interested in ANY reason ANY phone can take much longer
to boot sometimes than other times.

>The OS is stored on internal storage (NAND/EMMC chip), and even you know
>those are self-destructive devices. They degrade with writes. To
>compensate, remapping is used, but accessing an address which remaps to
>elsewhere adds time. The more remapping as the chip ages the more time
>to access the original data redirected to elsewhere. You can try to
>install apps (or part of them) on the SD card, if you have one, along
>with any frequently accessed data, like offline maps that get updated,

There is ono point to off-loading data from the phone to the SD card.
I'm not trying to shorten the time it takes to boot. I have plenty of
time. I'm only trying to understand why sometimes it would take little
time and sometimes 3 times as much.

>or pics, or videos. However, SD cards degrade over time, too. We don't
>know if you added an SD card, and how old it is, and its volume of
>writes. Flash storage is self-destructive. The older it gets, the
>slower it gets. Wear leveling only works for a while. It does not
>eliminate the wear.

I doubt if any of this matter to me since from one boot to another
there3 is rarely any difference about how much is store on the SD card
or the RAM or anywhere. Even when the phone is on, I rarely use it,
but I will pay more attention if perhaps it takes longer following times
that I take pictures (no more than once a month.) or dl email, maybe 4
times a year. So that would be 16 times a year I change what is stored
in the phone, but around 150 times a year I restart the phone. (Every 3
days, plus about 20 other times a year to look at something for a couple
minutes.) I dont' think the lengthy boot instances have followed any
of the 16 times each year I stored data on the phone.

Making or receiving a phone call stores a little bit of data, but not
enough, I think, to call into play any of thse factors.

>
>Batteries go bad over time, too, and some go bad faster than others. My
>phone's battery is a poor design that degrades quickly. When new, I get

But I'm talking about consecutive boots, fast one time, slow the next,
fast the next. I don't think the battery has changed in that time,
whiether it's 15 minutes or two periods of 3 days each.

>just over a day of constant up-time. After a year, I'll start noticing
>it's down to about half a day for contant up-time, and it continues to
>drop. No matter how the charging cycles are changed trying to save the
>battery, the battery just doesn't last. If I leave my phone on, and it
>powers off because the battery got down to 3%, it won't restart next
>time because there's not enough power in the battery. It might start,
>but fails during the boot. If I plug in before booting, it sometimes
>starts to boot, gets enough power, and continues okay, but sometimes it
>detects the capacity is still too low (not enough time on the charger to
>get above 5%), and fails the boot. Not all phones will immediately show
>their battery's charge level when booting. Instead of just trying to
>power on the phone, leave it off and plug into a charger. The phone's
>screen should show the current charge level. Then power on to measure
>the boot time. That might indicate if a low battery is causing a slow
>boot.
>
>If your phone has a removable battery (again something that could be
>researched by responders if you had provided details), remove the back

I don't want people wasting their time reseaching my phone. I can tell
you I don't have an easily replaceable battery.

>cover of the phone to check if the battery is swollen. I've had one

Nor do I have iirc an easily removeable cover. But it doesn't matter,
because if the battery is swollen, it's not going to unswell 15 mintues
or 3 days later.

>phone that split apart due to a battery getting pregnant. On another, I
>was having trouble reinstalling an armor case because the phone's back
>cover was bulging out due to a swollen battery.
>
>We also don't know what apps are registered for load on startup. Some

It doesn't matter. They are the same every time I start. If there is
some app that starts more slowly some times and not other, I'm
interested in what it is regardless of whether I have it or not.

>may be checking for updates. Even the Play store app checks for
>updates. Updating takes CPU cycles. I've never had my phone interrupt
>me with messages that an app is updating. Only a few apps I have will
>add a notification that they are updating,

No we are getting somewhere. Maybe an app is updating and it wouldn't
tell me if it was. In my OP I said "Even when it takes a long time, I
get no messages about updating programs", but if most apps don't display
such messages, that would account for why it takes so long to boot (if
updating apps is done at boot time, which seems not unreasonable**, and
which you seem to be confirming.

**Although I can imagine that it would be better to make the phone
available as quickly as possible. And do updating later, after the user
has made the phone phone call(s)***, possibly emergency calls, that he
turned the phone on in order to make.

So is app updating really done at boot time?

When it wants to update the operating system, it asks me if now is a
good time.

**It's not a phone, but on the PC, Anvir Task Manager will allow you to
easily delay startup programs to a user-determined time after booting,
so that you can use the computer as soon as possible, and not have to
wait for some inessential programs to load. This seems like an even
more important need for a phone, because people make a lot more
emergency phone calls than they 1) read emergency email, 2) read or post
emergency usenet messages, or 3) read emergency webpages.

> like Here[WeGo] Maps app when
>it is updating its offline maps, and all I see is a notification bar
>icon, not a popup message about updating.

Yes, I think I saw that update message when I drove to an adjoining area
and it needed a new map.
>
>We could guess you have cleanup apps, and they trigger sometimes during
>boot.

That's a good suggestion, becausez indeed, cleanup apps would feel the
need to run sometimes and not on others. However I don't have any. ;-(

>Or you could be using an app killer that terminates backgrounded
>apps, but you don't realize some are "sticky" apps: if the OS sees they
>are unloaded, the OS will reload them. Killer app kills an app, OS
>reloads the app.

That brings up a good point. I installed about 4 weeks ago a pedometer
app that I only intended to use when I took a long walk, but it seemed
to run all the time. So I turned it "off" whatever that means, but it
may load anyhow. If the long start was before I trned it off and quick
start before I installed it or after I turned it off, that might account
for it I thought I had had this long start thing for months and months,
long before the pedomer, but I will pay more attention and do some tests
and see if I can correlate it with turning the pedometer app on or off.
>
>Instead of just shutting down Android and powering off the phone, power
>down but select to restart in safe mode. While powered on, press and
>hold the Power button to get the power options appear: Power Off,
>Airplane Mode, and Restart. Long-press the Power Off option to get the
>"Reboot to safe mode" dialog. When the phone restarts, measure how long
>until Android is ready

Did you yet try safe boot to eliminate loading of non-bundled apps, like
those you've installed since getting the phone? I'd first boot normally
to get an average of the normal boot times, and also to to average the
"3 times longer" boot times, to know what boot times are you looking at.
Then boot into safe mode 10 times, or more, to average the safe boot
times, and compare to the prior two "normal" boot times (short and
long). If safe boot is consistently close on every boot to the average
of them all, you've got a startup app causing the irregularity.

When testing the boot times, make sure the phone is 100% charged, or on
the charger. Low battery power could, for example, exascerbate boot
time by you having a weak cellular or wifi signal strength which could
cause multipe packet retries. You might want to get an app that shows
the real signal strength to whichever tower you're connecting instead of
the rather inaccurate signal strength meter in the notification area. I
use Network Cell Info (just the free adware version) you can get at
https://play.google.com/store/apps/details?id=com.wilysis.cellinfolite.
If you have a startup app that is retrieving data as soon as it loads,
it could take longer to get the data over a weak cellular or wifi
connection (the app may provide a choice of wifi+data or wifi-only modes
on how to get its data, like Here[wego] Maps app that I configure to
download updated maps only over wifi as not to eat up my data quota).

Else, you're stuck trying to use boot-time and app profiling tools from
the Android SDK provided they can also be startup apps to start
profiling immediately upon their load. However, as an app, they can
only start profiling after getting loaded which is after the hardware
and OS have loaded.

https://developer.android.com/studio/profile/android-profiler
https://developer.android.com/studio/profile/cpu-profiler

I suspect any boot-time profiling that starts measuring immediately
after the kernel loads would require a rooted phone. If its a startup
app that varies the boot time, a boot-time profiling app might work. If
its the OS that is varying in its boot time, you'd need a rooted phone
to get a profiler to load just after the kernel loads; however, it's
likely info on the OS components as to when they start loading and how
long they take to load would require detailed expertise in how Android
itself works. You might notice a component that takes 3 times longer to
finish loading or until it is ready, but then you'd have to dig into
what that component does. Never done that, outside my experience, and I
suspect not what you want to dig into.

I've seen mention of bootchart in Android, and some profiling tools can
use it to show OS boot analysis. I'm not qualified to make suggestions
since I've not even gotten into Java programming on Android, and
definitely not intimate with the OS code.

So, how long is "3 times longer"? Is the 3 times longer boot time any
more frustrating than the normal 1 times long boot time when standing at
the dentist's front desk trying to check your calendar to see when to
make the next appointment at the dentist? For me, just the 1-time boot
time duration is too long to make the receptionist wait for me to boot
my phone, and why I leave my phone on all the time, even when charging
overnight. I use my phone every day, so I never power it off unless I'm
doing some troubleshooting. Looks like you use your phone a lot less
often, and power it off for a lot longer, like days at a time. However,
I wouldn't pickup my phone to head out of the door with it unless it was
fully charged, and turned on. I wouldn't afflict others with having to
wait for my phone to boot when it was needed.

On 22/07/2021 20.38, nospam wrote:
> In article <vbaoshxtf1.ln2@minas-tirith.valinor>, Carlos E. R.
> <robin_listas@es.invalid> wrote:
>
>>> sd cards won't affect boot time.
>>
>> Yes, they do. Some applications that start automatically scan the
>> contents on the storage, for files they should know about, like movies
>> or photos. And while they do that, the machine is busy and goes slow
>> about responding to the user.
>
> launching apps happens after the os has booted, and user response time
> is a function of the device, not that it's using an sd card.

It depends on what a person calls "boot". People generally consider boot
all the time till the user can do things on the machine. For them, the
time that the automatically started apps take to load and scan the sd
card, is part of the boot time. All the time till he can tap an
application and it responds.

>> Low battery + a system that can throttle down the machine to conserve
>> battery when it is low ==> slow machine with low battery.
>
> that doesn't affect boot time.
>
> if the battery is dead, it will need to be charged so that the device
> can boot, but that is not part of the boot process. any device with a
> dead battery is going to need to be recharged.

Again, a battery with 15% charge may cause the OS to go into battery
saving mode, throttling the CPU speed down if that is a possibility.

--
Cheers,
Carlos E.R.

In comp.mobile.android, on Thu, 22 Jul 2021 21:46:56 -0500, VanguardLH
<V@nguard.LH> wrote:

>Did you yet try safe boot to eliminate loading of non-bundled apps, like
>those you've installed since getting the phone? I'd first boot normally

No. As I said, my plan is to wait until I'm sitting in a doctor's
waiting room with nothing else to do**. I mean that literally.

>to get an average of the normal boot times, and also to to average the
>"3 times longer" boot times, to know what boot times are you looking at.
>Then boot into safe mode 10 times, or more, to average the safe boot

10 times would take more time than this is worth. I was willing to do
one time, but that's it.

>times, and compare to the prior two "normal" boot times (short and
>long). If safe boot is consistently close on every boot to the average
>of them all, you've got a startup app causing the irregularity.

Yes, but I wouldn't know what it is.

**By golly, only 5 days later I was in a doctor's waiting "room" for
about 20 minutes today. Usually they are quicker. Forgot to bring
something to read, couldn't read or listen to anything on the phone
because it was an interior hall and there was no signal, but I didn't
remember the instructions... And they might come out to get me any
minute anyhow.

Thanks anyhow.

Micky

>When testing the boot times, make sure the phone is 100% charged, or on
>the charger. Low battery power could, for example, exascerbate boot
>time by you having a weak cellular or wifi signal strength which could
>cause multipe packet retries. You might want to get an app that shows
>the real signal strength to whichever tower you're connecting instead of
>the rather inaccurate signal strength meter in the notification area. I
>use Network Cell Info (just the free adware version) you can get at
>https://play.google.com/store/apps/details?id=com.wilysis.cellinfolite.
>If you have a startup app that is retrieving data as soon as it loads,
>it could take longer to get the data over a weak cellular or wifi
>connection (the app may provide a choice of wifi+data or wifi-only modes
>on how to get its data, like Here[wego] Maps app that I configure to
>download updated maps only over wifi as not to eat up my data quota).
>
>Else, you're stuck trying to use boot-time and app profiling tools from
>the Android SDK provided they can also be startup apps to start
>profiling immediately upon their load. However, as an app, they can
>only start profiling after getting loaded which is after the hardware
>and OS have loaded.
>
>https://developer.android.com/studio/profile/android-profiler
>https://developer.android.com/studio/profile/cpu-profiler
>
>I suspect any boot-time profiling that starts measuring immediately
>after the kernel loads would require a rooted phone. If its a startup
>app that varies the boot time, a boot-time profiling app might work. If
>its the OS that is varying in its boot time, you'd need a rooted phone
>to get a profiler to load just after the kernel loads; however, it's
>likely info on the OS components as to when they start loading and how
>long they take to load would require detailed expertise in how Android
>itself works. You might notice a component that takes 3 times longer to
>finish loading or until it is ready, but then you'd have to dig into
>what that component does. Never done that, outside my experience, and I
>suspect not what you want to dig into.
>
>I've seen mention of bootchart in Android, and some profiling tools can
>use it to show OS boot analysis. I'm not qualified to make suggestions
>since I've not even gotten into Java programming on Android, and
>definitely not intimate with the OS code.
>
>So, how long is "3 times longer"? Is the 3 times longer boot time any
>more frustrating than the normal 1 times long boot time when standing at
>the dentist's front desk trying to check your calendar to see when to
>make the next appointment at the dentist? For me, just the 1-time boot
>time duration is too long to make the receptionist wait for me to boot
>my phone, and why I leave my phone on all the time, even when charging
>overnight. I use my phone every day, so I never power it off unless I'm
>doing some troubleshooting. Looks like you use your phone a lot less
>often, and power it off for a lot longer, like days at a time. However,
>I wouldn't pickup my phone to head out of the door with it unless it was
>fully charged, and turned on. I wouldn't afflict others with having to
>wait for my phone to boot when it was needed.