Quote:
|
I had the same issues as you (WiFi disconnect/looping/touchscreen issues). Battery calibration (draining) and updating to the latest (9/02) firmware fixed the issue, but I can understand your hesitance.
|
Is there even 9/2 for Lynx? I have 9/2 for original Boox. Lynx haven't updated since June, I believe. All they "fixed" was touchscreen, which is now borderline acceptable. Before that it took me 30 minutes to even enter WiFi password and then into update...
Quote:
|
I won't pay for a device that doesn't work and just hope that it will work someday. For $199 it should work from the start. A few devices out of a large number will always have a problem but to have so many that have numerous defects is just bad business. If it works now after an update they should have delayed production until now.
|
If anyone asked me if they should buy Boox device I would answer "HELL NO". For about the same amount of money you can have Kobo Aura HD, or maybe even H2O. It has whiter screen, much better touchscreen accuracy and no problematic issues. Sure, you can't install your own apps, but if the price to install your own apps is having device that doesn't work on so many levels then I prefer closed system.
[q]I used a simple, time-tested battery calibration technique for getting rid of my boot loops. After flashing a new firmware, I use the T68 until it starts boot looping. Then I let the battery discharge to 0. When the device runs completely out of juice, I then charge it to 100% (not 99%). This isn't good for battery health, but it did get rid of boot loops for me.
It also takes about four or five refills before the problems went away.[/q]
I'm trying to get it to 100% -> drain -> 100%. I'm using an app that generates useless wifi and BT traffic to drain it faster, but it still takes about 10h to get it drained.
I don't know if it means anything, but I noticed that when close to full charge the battery voltage was higher(4500mv if I recall correctly). Now it dropped to 3666mv. Is it normal, or could it be the cause of problems?
Edit: It went down to 9% and started bootloop. Yay for broken piece of awful hardware that pretends to be an ebook reader.