It’s time to get real.
Previously I’ve used Success: A Novel (catch up here) as my Google Books test PDF. Most mainstream devices can now do that. So it’s time to up the ante to the full Monty of what I need a device to do.
I’ve already tried this twice:
I wanted to use the same PDF but problems erupted. I had to use a different issue of The American Magazine. The one in those first two tests was 203MBs. The one in these tests is a whopping 290MBs. How’s that for going nuclear?
I will repeat this introduction on all four posts in this series since I doubt people will read all of them.
Now onto the Samsung Galaxy Note 8.0.
My overall impression of the Note 8.0 is here: Nano-Fondle: Samsung Galaxy Note 8.0
This is turning into a battle between Android and iOS. With Android winning. So far. Can it do it again?
The Samsung Galaxy Note 8.0 has a quad-core Exynos 4412 CPU running at 1.6GHz. AnTuTu has it at 17,708. That explains the Wow! I experienced in my fondle post. It might also bode well for those interested in the iPad Mini clone Chuwi V88, if a quad-core Rockchip CPU can reasonably be compared to an Exynos.
Let’s get to it. As usual, ignore the “grit” in the photos. That’s a result of the camera sensor interfering with the screen’s grid. I didn’t apply any filters to the photos to get rid of it.
I’m logged into my Google Books account to view the file under Recently Viewed, which I tap to select:
Selected and tapped on again:
And opened in Chrome:
Tapping on that PDF with the down arrow will download the PDF:
I will cut to the chase. While I was downloading, the Note was also updating some software! Anyway, my download began at 3:50 PM and …
… ended at 4:24PM. Yes, I hogged the Note all that time. For Science!
And hello! The Galaxy Note 8.0 could download a PDF the iPad Mini could not.
Tapping gave me this choice of bad or worse:
I already knew the Kindle app wouldn’t work, so it was again time to submit myself to the torment of Polaris Office.
This page means nothing but those streaks underneath it are trouble ahead:
Typical for Polaris Office with Google Books PDFs:
But it got interesting here, with part of the magazine showing:
And here we are, with Polaris’ maddening habit of treating photos and illustrations as different than text — yet they’re all images in the PDF!
The page above is this one on the Nook HD+.
No lag as bad as the Nook HD+.
The above page is this one on the Nook HD+.
I discovered that if instead of scrolling I used those arrows stupidly placed near the top of the screen instead of the bottom, paging went quickly. Unlike on the Nook HD+.
So, here we are.
Two Android devices versus two iOS devices, and Android — even with the crap display of Polaris Office — wins. Android devices could download the file and at least try to display it. The iPad Mini could not download the file at all. The iPad 4 claimed to have downloaded it but couldn’t display it in iBooks.
This is not good for Apple.
It also makes me wonder what else Android can do at the limits that iOS can’t.
So when it comes to reading massive Google Books PDFs, it seems there’s just no other choice than Android. The iPad Mini is worthless. And if the iPad 4 actually can download the file, maybe it can be opened in special third-party PDF software. But even so, the iPad 4 is big and heavy.
Frankly, all of this surprised me. I didn’t think I’d have the problems that I experienced with both iPads. All of this goes against the grain of the iPad’s image.
And that is why I test.
The Google Books PDF Death Match series of posts: