Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader

Notices

Reply
 
Thread Tools Search this Thread
Old 10-13-2012, 10:28 PM   #16
Solicitous
Wizard
Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.Solicitous ought to be getting tired of karma fortunes by now.
 
Posts: 1,413
Karma: 1137946
Join Date: Aug 2009
Location: TAS, Australia
Device: Astak Pocket Pro (Black), 2 x Kindle WiFi (Graphite), iPod Touch 4G
Quote:
Originally Posted by roycymru View Post
Thanks for pointing out the "official" announcement I had missed that, perhaps someone should make it a sticky!

However, although we have had this anouncement liitle seems to have happened. I think some people in Canada have had it (?), certanly no sign of an imminent release in the UK.

The statement "WARNING: Going forward we are distributing specific upgrade packages to devices based on various criteria which makes the upgrades incompatible between some devices". Is also less than re-assuring and not clear in what this will mean to end users in practice.
Does the last paragraph make people think that this could be the last touch firmware update? I ask as if they are having to make multiple releases of the same firmware version due to slight differences between the touches, will Kobo say "this is too much" and just concentrate on the Glo/Mini where they can just make one firmware and release it?
Solicitous is offline   Reply With Quote
Old 10-13-2012, 10:36 PM   #17
murg
No Comment
murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.
 
Posts: 1,545
Karma: 4082900
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
Quote:
Originally Posted by Solicitous View Post
Does the last paragraph make people think that this could be the last touch firmware update?
The actual differences between the devices is fairly small.

Touch has a Home button. Glo has no home button, a light button and lights. Mini has no home button and no SD slot.

The hardware differences can be dealt with fairly simply in the firmware.

Usually, it is much simpler to keep track of one firmware software set rather then 3. However, I really can't guess how Kobo is going to come down on this issue.

Hopefully, they won't pull updates for the Touch, because doing so will get them a reputation of not supporting their devices beyond a year or two.
murg is online now   Reply With Quote
Old 10-13-2012, 10:40 PM   #18
nogle
Gangnam style!
nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.nogle ought to be getting tired of karma fortunes by now.
 
Posts: 373
Karma: 3646106
Join Date: Aug 2011
Device: Kobo
Quote:
Originally Posted by Solicitous View Post
Does the last paragraph make people think that this could be the last touch firmware update? I ask as if they are having to make multiple releases of the same firmware version due to slight differences between the touches, will Kobo say "this is too much" and just concentrate on the Glo/Mini where they can just make one firmware and release it?
Until some component of the glo and/or mini ceases production and is replaced by a very similar, but ever so slightly different component...

Or they can just keep designing new products and producing one large batch to be sold until exhausted then replaced by the next generation...
nogle is offline   Reply With Quote
Old 10-15-2012, 02:22 AM   #19
TechniSol
GranPohbah-Fezzes r cool!
TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.
 
TechniSol's Avatar
 
Posts: 1,008
Karma: 3088870
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
It usually makes a lot more sense to keep one base firmware and simply allow/disallow or ignore certain things based on switches in the code that correspond to what hardware the code is running on and enable or process sections of code only if allowed. It's a lot easier to maintain one and not have to update code in several versions and track in each which updates or revisions have been applied...

However, if codespace is an issue, or hardware versions diverge too radically then separate firmwares make more sense. No one really likes to branch unless necessary, because of the extra work of having to apply any new updates to multiple versions of base code and test them separately.

All that said, near as I can figure from posts I've read is that there exists either a hardware difference on some readers or software difference in firmware 2.0.0(there were apparently 3 versions, A, B, C) that forced Kobo to produce a 2.0.4 necessary to allow an update to 2.1.4 on some range of devices... Seems to be the Aussies mostly, so maybe their version was different due to a wireless hardware issue due to different frequencies being used or something along those lines(pure conjecture.) This has apparently been compounded by finding problems with readers with side loaded content on SDHC and is causing the delay in further rollout of the current 2.1.4 firmware, or so I gather.

Frankly, I think someone at Kobo needs to beg, borrow, steal or quietly buy back some affected units so they have in house at least one of every model that ever differed in any way for future testing and clearance of any revised code and basically get all their sh-t in one sock before they look like bigger bozos. I greatly admire that they aren't abandoning older devices as they roll out newer, but they have to get hold of this tiger's tail and stop releasing firmware that is found to be buggy or lacking almost overnight. That is just plain sloppy. TESTING - there is no substitute!

On the upswing side of things, I have 2.1.4 via wireless update and it works great near as I can tell, but I am not yet using an SDHC card nor am I actively pursuing how it might fail, I am merely enjoying reading with it and the bonus of faster page turns. I think we just need to be patient and give them time to resolve the issue before they continue the upgrades. I updated from 2.0.0 and I still have no idea what people were complaining about with that version, unless it was as petty an issue as pages turning more slowly. I think ultimately, we need to remain grateful that they are bothering to continue updating firmware on products that have been superseded by newer versions. To the Kobo developers, all I'd say, is that you guys need to worry less about when updates occur and more about them being ABSOLUTELY bulletproof before announcement, let alone release. Best of luck and try harder.
TechniSol is offline   Reply With Quote
Old 10-15-2012, 03:37 AM   #20
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 6,090
Karma: 6238033
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo Touch, Kobo Glo
Quote:
Originally Posted by TechniSol View Post
It usually makes a lot more sense to keep one base firmware and simply allow/disallow or ignore certain things based on switches in the code that correspond to what hardware the code is running on and enable or process sections of code only if allowed. It's a lot easier to maintain one and not have to update code in several versions and track in each which updates or revisions have been applied...
They are sharing a
Quote:
However, if codespace is an issue, or hardware versions diverge too radically then separate firmwares make more sense. No one really likes to branch unless necessary, because of the extra work of having to apply any new updates to multiple versions of base code and test them separately.
They are sharing a code base between the Touch, Glo and Mini. At the moment it is a single firmware file for all. But, it might change.
Quote:

All that said, near as I can figure from posts I've read is that there exists either a hardware difference on some readers or software difference in firmware 2.0.0(there were apparently 3 versions, A, B, C) that forced Kobo to produce a 2.0.4 necessary to allow an update to 2.1.4 on some range of devices... Seems to be the Aussies mostly, so maybe their version was different due to a wireless hardware issue due to different frequencies being used or something along those lines(pure conjecture.)
This wasn't a hardware problem, but a combination of the factory installed firmware version and some freebies in the firmware. I think the combination meant the install of post 2.0.0 firmware failed. And yes, 2.0.4 is a workaround to prepare the devices for 2.1.4 and later.
Quote:
This has apparently been compounded by finding problems with readers with side loaded content on SDHC and is causing the delay in further rollout of the current 2.1.4 firmware, or so I gather.
Yes, the found a bug that caused a reboot. They decided to stop the rollout and fix it.
Quote:

Frankly, I think someone at Kobo needs to beg, borrow, steal or quietly buy back some affected units so they have in house at least one of every model that ever differed in any way for future testing and clearance of any revised code and basically get all their sh-t in one sock before they look like bigger bozos. I greatly admire that they aren't abandoning older devices as they roll out newer, but they have to get hold of this tiger's tail and stop releasing firmware that is found to be buggy or lacking almost overnight. That is just plain sloppy. TESTING - there is no substitute!
I am told they at least one of every version. Plus they have an active beta testing program with real users. Of course, this missed this problem, but I don't know if it was last minute fix or just a fluke that no-one tried it.
Quote:
On the upswing side of things, I have 2.1.4 via wireless update and it works great near as I can tell, but I am not yet using an SDHC card nor am I actively pursuing how it might fail, I am merely enjoying reading with it and the bonus of faster page turns. I think we just need to be patient and give them time to resolve the issue before they continue the upgrades. I updated from 2.0.0 and I still have no idea what people were complaining about with that version, unless it was as petty an issue as pages turning more slowly. I think ultimately, we need to remain grateful that they are bothering to continue updating firmware on products that have been superseded by newer versions. To the Kobo developers, all I'd say, is that you guys need to worry less about when updates occur and more about them being ABSOLUTELY bulletproof before announcement, let alone release. Best of luck and try harder.
I think the developers already did this. I am sure from comments made by them that this firmware was planned for a lot earlier. But, there eventually gets a point with development projects where the release timing gets taken out of their hands. And frequently the team gets told they must put a particular fix or feature in but then don't get the chance to test it.
davidfor is offline   Reply With Quote
Old 10-15-2012, 05:17 AM   #21
jusmee
Guru
jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.
 
Posts: 978
Karma: 203682
Join Date: Oct 2009
Device: Kobo Touch / Astak Pocket Pro
Quote:
Originally Posted by davidfor View Post
But, there eventually gets a point with development projects where the release timing gets taken out of their hands. And frequently the team gets told they must put a particular fix or feature in but then don't get the chance to test it.
There's your root cause for the problems then! Crazy stuff. It also means there was a failure earlier in the process during the planning and specification of the the release.
jusmee is offline   Reply With Quote
Old 10-15-2012, 07:23 AM   #22
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 6,090
Karma: 6238033
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo Touch, Kobo Glo
Quote:
Originally Posted by jusmee View Post
There's your root cause for the problems then! Crazy stuff. It also means there was a failure earlier in the process during the planning and specification of the the release.
Unfortunately, there is always change after the project is started. Sometimes something is added, sometime taken out. We (us developers) just have to hope that the powers-that-be allow us time to make up for the changes. Generally they don't.
davidfor is offline   Reply With Quote
Old 10-15-2012, 08:55 AM   #23
jusmee
Guru
jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.
 
Posts: 978
Karma: 203682
Join Date: Oct 2009
Device: Kobo Touch / Astak Pocket Pro
Quote:
Originally Posted by davidfor View Post
Unfortunately, there is always change after the project is started. Sometimes something is added, sometime taken out. We (us developers) just have to hope that the powers-that-be allow us time to make up for the changes. Generally they don't.

Probably getting too deep into project management, but, one of the first tasks of a project is to get signoff, by the stakeholders, on the project deliverables. If they wish to vary/increase what the project is tasked to deliver, then they need to allow more resources and/or time. The project owner should be empowered to say no, if agreement cannot be reached. If this doesn't happen, then they are not running projects properly. IMHO I must add.
jusmee is offline   Reply With Quote
Old 10-15-2012, 09:23 AM   #24
SeigneurAo
Connoisseur
SeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the endSeigneurAo knows the complete value of PI to the end
 
SeigneurAo's Avatar
 
Posts: 62
Karma: 31414
Join Date: Sep 2012
Location: France
Device: Kobo Glo
Quote:
Originally Posted by jusmee View Post
If this doesn't happen, then they are not running projects properly. IMHO I must add.
Which must be the case in what, 90% of IT projects in my short experience ?
SeigneurAo is offline   Reply With Quote
Old 10-15-2012, 09:27 AM   #25
jusmee
Guru
jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.
 
Posts: 978
Karma: 203682
Join Date: Oct 2009
Device: Kobo Touch / Astak Pocket Pro
Quote:
Originally Posted by SeigneurAo View Post
Which must be the case in what, 90% of IT projects in my short experience ?

most likely, given the evidence we have of the quality of the results!
jusmee is offline   Reply With Quote
Old 10-15-2012, 09:33 AM   #26
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 6,090
Karma: 6238033
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo Touch, Kobo Glo
Quote:
Originally Posted by jusmee View Post
Probably getting too deep into project management, but, one of the first tasks of a project is to get signoff, by the stakeholders, on the project deliverables. If they wish to vary/increase what the project is tasked to deliver, then they need to allow more resources and/or time. The project owner should be empowered to say no, if agreement cannot be reached. If this doesn't happen, then they are not running projects properly. IMHO I must add.
Yep, that's how it is supposed to be done. But, from my experience, it never is. The stakeholders will manage to add things without adding time. Sometime they allow something to be remove. When doing this, you start to move away from the ideal that was originally envisioned. Hence bugs, bad design, missing features creep in. Then there is the problem that all this was based on someones estimates. And stuff gets cut to allow the project to meet the targets. And testing is one of the favorite things to get reduced. After all, we programmers write bug free code, don't we?

But, I think we are getting off the topic.
davidfor is offline   Reply With Quote
Old 10-15-2012, 09:37 AM   #27
TongueTied
Zealot
TongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic somethingTongueTied has a certain pleonastic something
 
Posts: 127
Karma: 18512
Join Date: Jun 2011
Location: Buderim, Australia
Device: Kobo Touch, Kobo Glo
Quote:
Originally Posted by davidfor View Post
Yep, that's how it is supposed to be done. But, from my experience, it never is. The stakeholders will manage to add things without adding time. Sometime they allow something to be remove. When doing this, you start to move away from the ideal that was originally envisioned. Hence bugs, bad design, missing features creep in. Then there is the problem that all this was based on someones estimates. And stuff gets cut to allow the project to meet the targets. And testing is one of the favorite things to get reduced. After all, we programmers write bug free code, don't we?

But, I think we are getting off the topic.
... And then they decide that Marketing should be one of the stakeholder and we are no longer talking scope creep but scope explosion.
TongueTied is offline   Reply With Quote
Old 10-15-2012, 11:52 AM   #28
Thasaidon
Hedge Wizard
Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.Thasaidon ought to be getting tired of karma fortunes by now.
 
Thasaidon's Avatar
 
Posts: 110
Karma: 1124406
Join Date: May 2011
Location: Doncaster UK
Device: Kobo Touch, Nook Simple
Old programmer's saying

"they never give you enough time to write it correctly but they always give you time to do a rewrite"

Quote:
Originally Posted by davidfor View Post
Unfortunately, there is always change after the project is started. Sometimes something is added, sometime taken out. We (us developers) just have to hope that the powers-that-be allow us time to make up for the changes. Generally they don't.
Thasaidon is offline   Reply With Quote
Old 10-16-2012, 02:53 PM   #29
Terisa de morgan
Wizard
Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.Terisa de morgan ought to be getting tired of karma fortunes by now.
 
Terisa de morgan's Avatar
 
Posts: 2,411
Karma: 2236104
Join Date: Jun 2009
Location: Madrid, Spain
Device: Kobo Aura, Kobo Mini, Kobo Aura HD, iPhone, iPad, Galaxy Tab3 8
Quote:
Originally Posted by jusmee View Post
Probably getting too deep into project management, but, one of the first tasks of a project is to get signoff, by the stakeholders, on the project deliverables. If they wish to vary/increase what the project is tasked to deliver, then they need to allow more resources and/or time. The project owner should be empowered to say no, if agreement cannot be reached. If this doesn't happen, then they are not running projects properly. IMHO I must add.
(from an IT Project Manager)
Terisa de morgan is online now   Reply With Quote
Old 10-16-2012, 03:10 PM   #30
rjmac
Connoisseur
rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.rjmac ought to be getting tired of karma fortunes by now.
 
Posts: 54
Karma: 574506
Join Date: Apr 2012
Device: Kobo Touch
Quote:
Originally Posted by davidfor View Post
2.1.4 has definitely been pulled to fix this problem. It is unfortunate that Kobo haven't announced it officially.
Does anyone have any update on this?

My desktop has updated but not my Touch. Is 2.1.4 available or not in the UK??
rjmac is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
$25 gift card w. purchase of Kobo Touch or Kobo Vox at Frys sufue Deals, Freebies, and Resources (No Self-Promotion) 0 07-15-2012 11:39 AM
Touch Kobo Touch defective after 3 months and Kobo Customer Support useless shaf Kobo Reader 5 12-04-2011 06:10 PM
Exciting Kobo Announcement (09/22/11 2:30 EST) G0AT Kobo Reader 67 09-30-2011 03:04 PM
Touch Kobo Touch not ejecting cleanly with Calibre OR Kobo Desktop - Windows 7 JBlyth Kobo Reader 11 08-03-2011 06:38 PM
Kobo Touch not disconnecting properly from Calibre OR Kobo Desktop - Windows 7 JBlyth Devices 1 08-03-2011 07:50 AM


All times are GMT -4. The time now is 05:25 PM.


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