Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > PocketBook

Notices

Reply
 
Thread Tools Search this Thread
Old 12-16-2010, 08:34 AM   #16
fjtorres
Grand Sorcerer
fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.fjtorres ought to be getting tired of karma fortunes by now.
 
Posts: 11,732
Karma: 128354696
Join Date: May 2009
Location: 26 kly from Sgr A*
Device: T100TA,PW2,PRS-T1,KT,FireHD 8.9,K2, PB360,BeBook One,Axim51v,TC1000
Quote:
Originally Posted by syoggy View Post
It is based on linux and has superior memory management compared to most of the operating systems available.
Alas, it is *not* that simple.
Yes, Android is based on Linux, but Android apps don't *run* on LINUX. Only the Android Runtime environment does.
Android Apps have access to the resources the Runtime makes available.
This is exactly how Java Apps run on, say, a Macintosh; they never see the underlying OS, only the Java Runtime Environment (JRE).
That Android runs on LINUX means simply that the base OS doesn't bring the entire stack down and that you don't get a hardware reboot when an App or the Runtime crashes.
(By contrast, the eInk readers run raw LINUX (with mods) and it is possible, on those rare occasions when one of the reader apps crashes to have it take the entire system down and either lockup the hardware or force a full hardware reboot.)

The problems with memory management on Android are problems with the way the Runtime is architected. Not with LINUX. It is the Runtime that commingles application storage and runtime resources so that installing an extra app can cause an app that was previously stable to become unusable.

And, yes, Android was designed for smartphones, but that kind of behavior is inexcusable in a phone as well as a tablet. And you don't see that on Blackberries or iOS or Symbian or WebOS or WinMo. Those companies know how to architect a proper OS. 10-year old WinCE is a way better OS than Android is likely to ever be. But Android has the apps and CE doesn't. (Except in asia). Android runtime memory management is just plain B-A-D, bad. Amateur hour, really.

Now, understand; bad doesn't mean useless. Or value-less.
It is just that the value proposition of Android tablets in general, and the IQ in particular depends on the user's skill and resourcefulness.

At its given pricepoint, the IQ is a very good value if you know what you're doing or are willing to ignore the Android issues because of the quality of the hardware and the availability of apps. It can be a lot of fun to play with.

But to be honest, it is not *currently* a very good reader for anything but... Kindle. (shrug). It is a good enough webpad and casual gaming slate. It is not a bad reader. But the ePub reading Apps all have issues and glitches that get in the way of a seamless reading experience like the eInk readers offer.

That is what makes the IQ vs 602 (or 902, in this case) such a quandary.
There is clearly two separate markets here.
At least until the IQ's PB Reader app can start matching the functionality of its eInk counterparts.

Now, if I were the GIK, I would be looking into bypassing the Android runtime altogether and going straight to the underlying Linux to see if I could port the existing eInk apps. But, odds are, the IQ effort is being done by a separate team and anyway, Pocketbook has its hands full supporting the installed base, launching the Pro Readers, and prepping the upcoming 511. So what we see is what we'll get for a while: a solid, useful, but inherently flawed Android webpad at a good price.

If you know what you're doing, you'll be satisfied.
But you should know that there be dragons there.

Last edited by fjtorres; 12-16-2010 at 08:40 AM.
fjtorres is offline   Reply With Quote
Old 12-16-2010, 02:22 PM   #17
speedtouch
eBook Newbie
speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.speedtouch once ate a cherry pie in a record 7 seconds.
 
Posts: 373
Karma: 1724
Join Date: Jun 2010
Device: Kobo Clara HD
Quote:
Originally Posted by Logseman View Post
Thanks for all the input, in particular to speedtouch, who even volunteered to test the manga apps! I think I'm going for the IQ. I've seen videos of PDF reading on resistive tablets, and it seems just fine. Plus, I have already a Samsung Galaxy S from which I can take some apps and improve a bit the value of the device.
You're very welcome. 'Twas no trouble at all. The IQ is not the greatest tablet ever, but it gets the job done and I enjoy it. I haven't had any trouble with PDFs yet. Good luck! I hope you enjoy the IQ.
speedtouch is offline   Reply With Quote
Advert
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
PocketBook 902/903 pj123 PocketBook 23 12-06-2010 07:35 AM
Pocketbook 902 Roos Calibre 6 12-01-2010 01:32 PM
Pocketbook 902 Probleme Roos PocketBook 4 11-28-2010 12:11 PM
About Pocketbook 902 and 903 faba PocketBook 6 11-21-2010 03:19 PM
Pocketbook 902 DDHarriman PocketBook 5 11-05-2010 01:06 PM


All times are GMT -4. The time now is 06:32 PM.


MobileRead.com is a privately owned, operated and funded community.