6/23/2023 0 Comments Inkbook classic 2 play store![]() Yes, some of these opinions are idiosyncratic, but I was stating my personal reaction to my new eReader. ![]() Needless to say, I will spend as little time as possible in it, and use it solely as a means to move between AlreaderX & SyncMe (I'll use AlreaderX's internal 'Open File' option to navigate to the next book to read). And the menu it opens has most of it taken up by sliders for the Frontlight (which I never used on my last 2 eReaders) and sound volume (in spite of the fact that it is only able to play audio if connected to a Bluetooth device - which I have no intention of doing). I turned it off, as soon as I realised I could access "Back" & "Home" through the Status Bar.ĥ) The Status Bar is only slightly less clumsy. They should have the Library use either folder-hierarchy, book metadata, or similar to automatically create a navigable structure to your book collection.Ĥ) The NavBall is, in my opinion an abomination - clumsy, a visual distraction and frequently in the way. Yes, I could move the books one at a time into the "Bookshelves" (which is unclear whether they are the same thing as the "Sub-libraries" mentioned in the manual), but it really isn't worth the trouble, particularly as I prefer a two-level hierarchy (Author then Series). "Total:Bookshelves(0) / Books(663)" yields an un-navigable mess. Apart from easier access to WiFi in the P2, I prefer the Android layout on the Kepler Pro and Monte Cristo 4.ģ) In spite of the fact that Boox apparently has spent some time on further development of the 'Library', it is still, to my mind, unusable. ![]() If not done in this less-than-obvious order, it requires a reboot and potentially a "6-24 hours" wait for this error to go away (and I only found this out after a query to Boox).Ģ) The Android implementation is neither sufficiently similar to vanilla Android as to allow previous experience with that to guide you, nor sufficiently pared down that it is easy to find everything. I'd be especially interested in anybody who has first-hand experience with both of them (so can do a direct comparison).ġ) The Google Play Store implementation is half-baked, leading to a 'device is not Play Protect certified' error if you open Google Play Store (which the 'Enable Google Play' option does automatically), if you don't select an obscure Settings option to "bind the device to your Google Account" first.
0 Comments
Leave a Reply. |