Go Color 7 - slow boot

[MrPaulus]

I've had my Go Color 7 Gen II for a few months. When I first got it, the boot time was reasonable. How it's really slow and taking 2-3 times as long. I don't think there's been a significant software update, and I don't have many apps and books.

Anyone else seen this?

[Renate]

Do you mean from the time:
Power on to animation start?
Length of animation?
Length of "Android is starting"?
The times should be approximately 10, 10, 1 seconds.

[Techbar]

I've had the same thing occur. When I got it the animation would complete in a little over 1 cycle - now it takes at least 4 cycles as well as a much longer overall boot time. It started slowing down a month or two ago and has been getting progressively worse. I don't have many apps on it either.

[Renate]

I don't use skating elephants. I made 0 to 20 (seconds) in the lower right corner.
Usually it hits before 10.

[Techbar]

Originally Posted by Renate

.... I made 0 to 20 (seconds) in the lower right corner.

Ok.... not sure about your reference to the lower right corner - my Go Color 7 Gen II doesn't do anything there during the boot sequence.
However measuring from when the power button is pressed:
at 6 sec: 'BOOX' appears.
at 33 sec: the animations start.
at 1min 08 sec: 'Device Starting' message appears.
at 1min 23 sec: the library screen starts loading.

While a 1 minute 23 seconds boot isn't hugely long it is significantly longer than when it was new and it progressively got worse (more and more animation cycles).

Like MrPaulus I was wondering if others had seen this.

[Renate]

I meant that I put in a custom boot animation that just counts.

Your device is too slow.
Do you have ADB enabled?
At what point in the boot does it become active?
You'll need ADB to dive deeper.

My ADB is custom and it appears at about one second into the boot animation.
I'm sure for stock it starts much later.

[MrPaulus]

I mean it’s taking several minutes to boot from power off.

As above, the loading screen would appear and it cycled through the 6 dots twice, and the screen would light up after the first pass. Now I get a long time with a blank white screen.

I’ve already tried wiping and setting up again from act, but the problem is the same.

[Renate]

Well if you had ADB working and you were rooted:

C:\>adb shell
# stop
# start

You can see how long the Android subsystem takes to start/stop.

You can also look at the logcat and see if something is flailing.
Unfortunately with the state of things there are always massive errors in the logs so it's often hard to differentiate standard incompetence and serious errors.

The same goes for dmesg which should not be showing hardware problems.