MobileRead Forums - View Single Post - T68 bootloops

dnastase · 08-06-2014, 09:55 PM

I played with mine today, testing.

As a reminder: first day I had it it just froze at around 45% battery and it had to stay charging for a couple of hours until it came back to life.

Today I had it:
- maximum backlight
- wifi on
- bluetooth on
- running a ping continuously so there is some activity and also the wifi doesn't turn off

It discharged from 60% to 8% without an issue.
I don't know what to believe... probably I'm going to run more tests until I have a better idea.

The rate of discharge was ~15% per hour. I'm not sure if that's a lot or not. My feeling is that it loses power more rapidly than my NSTG.

Another observation is that the discharge (or the reporting of it) is not linear. There are sometimes jumps of up to 5% ! That makes analysis a little bit harder.

From the symptoms that I had the first time I would have said that there is an issue with the battery where, at certain levels, it cannot power the screen sufficiently. Now I'm not so sure. I am hoping it's a firmware issue (so that it can actually be fixed).

08-06-2014, 09:55 PM	#40
dnastase Addict Posts: 257 Karma: 432 Join Date: May 2014 Location: New York, NY Device: NG,NSTG,NST,AuraHD,OnyxT68,Lynx, BoyueT62,NGP,Aura1,Oasis,Mars	I played with mine today, testing. As a reminder: first day I had it it just froze at around 45% battery and it had to stay charging for a couple of hours until it came back to life. Today I had it: - maximum backlight - wifi on - bluetooth on - running a ping continuously so there is some activity and also the wifi doesn't turn off It discharged from 60% to 8% without an issue. I don't know what to believe... probably I'm going to run more tests until I have a better idea. The rate of discharge was ~15% per hour. I'm not sure if that's a lot or not. My feeling is that it loses power more rapidly than my NSTG. Another observation is that the discharge (or the reporting of it) is not linear. There are sometimes jumps of up to 5% ! That makes analysis a little bit harder. From the symptoms that I had the first time I would have said that there is an issue with the battery where, at certain levels, it cannot power the screen sufficiently. Now I'm not so sure. I am hoping it's a firmware issue (so that it can actually be fixed).