Phone problems (random restarts, apps crashing)

To be honest, it sounds like your phone is full, ie. you have too many apps on it.

This can also be caused by having too many pictures, videos, documents, etc.

Your SD card is where all your personal files should be stored.
This leaves the device memory to handle the system and any apps that you install.

A good rule of thumb is to only use 70% of the internal memory, leaving the rest available for apps that you use- because they have caches that fill and empty as the apps are used.

If you desire to keep a close tab on how much memory you are using,and many other things about your device, there is a great, simple to use app called CPU Info.

https://f-droid.org/en/packages/com.kgurgul.cpuinfo/

 

Slide through the options until you get to the storage information.

There will likely be three separate ones, the first two are the internal and are the same.

This would be the one that is best to maintain at or below 70%, for the reasons mentioned before.

It is also not a good idea to overfill your SD card, either.

 

Also, you mention that you have only added '8 apps or so' since the reset.

Remember that it is not the number of apps, but the size of the apps that makes the difference.

Some apps are very small when first installed, only to become enormous in a short while.

If any of the apps you are speaking of are social media apps (Facebook, Instagram, etc.), I would highly suggest ditching those altogether and just using your browser and bookmarking your login page.
If cookies are saved in your browser, a simple tap of the bookmark should bring you right to your feed on the site.

This act alone cane save huge amounts of space on a memory strapped device.

The same thing can be done for shopping apps, and any other app that is simply a wrapper for an online site.

 

When you say 'both', do you not have and SD card in the device?

Because if you do, and it is not formatted as internal memory, there should be 3 separate memories listed- and the first two are one and the same.

 

So the two shown are both the internal memory.

 

That app is telling you how much of the space available to you is being used.

The phone is telling you how much of the total memory is being used, which also includes space that you cannot use for yourself.

 

Have you kept track of the behavior as you have been installing apps?
This could narrow it down, and identify the app(s) causing the problem- if that is indeed what is going on.

Besides the space that an app takes up, there is also the issue of how much memory an app uses when it is active.
So it is quite possible that you have the 'physical' space for an app, but still not have enough RAM to properly run it.
Keep in mind that the OS must run at the same time as well, usually along with other apps, too.

How is the battery?
It may seem fine, then when a load is applied it may give out, and the device will crash.
Does the device have the same behavior if it is plugged into a charger as it does when not plugged in?
This is not a foolproof test, because a device runs off of the battery even when plugged into a charger.

Have you accessed the developers options?
In there, you can find a section that allows you to view all running apps.
Check this before and immediately after the behavior, and compare the differences.

 

As much as I like that app, it is like all battery apps, inaccurate.

An app cannot tell you if a battery is actually in good health.

I have had that app on all of my devices, and even when the battery expanded so much that I had to hold the back of the device on- battery health was 'good'.

The main point of it is for the storage percentages.

Now, it does have a section that you can use, where it shows how much CPU is being used, and what the threshold is.

Basically, the threshold is where you will run into issues such as what you are describing.

In fact, now that you mention the fact that it happens wether olugged in or not- can you see the battery if you remove the back of the device?

They can expand so much as to jepordize the connections that power the phone.

 

Another thing to try is to go into developers options and scroll to near the bottom.

Look for background processes.

These are apps that run in the background, even when you are not using them.

When you select, you have multiple choices available.

First, try no background services.

This will, however, usually break anything you are doing if you switch to another app.

Just see if the problem persists.

If not, then allow one background process, etc. untill the problem resurfaces.

 

FireFox has its own webview, so you do not need to have Android System Webview for that.
ASW will, however, be used by other apps.

Personally, I use browsers that utilize the built in ASW.
They are faster, and smaller.

 

Chrome is a massive piece of junk.

Depending on the OS, it can have or may not have its own webview.
On some OS, ASW was disabled unless you disabled Chrome.
Some OS were like this, and did not allow you to disable Chrome, so you could not use ASW at all.

That means that Chrome was doing webview duty instead- for all the other apps that need webview!

What a sneeky, underhanded way for Google to spy!