Hi......
Posted: February 24th, 2011, 10:25 am
Mornin' all.
First post on what I suspect is going to be a well used forum!
Picked up a new Scroll 7" yesterday and finally sat down last night to have a play with it. I have good experience of PC's and also iPhones but Android is something completely new for me and therefore I'm keen to start finding out about it.
I'm well aware of the "search before you post!" - and I'm quite happy to have a poke around and try things out before I get well and truly confused (highly likely!!) - so if someone could just confirm I'm heading in the right direction I'd be grateful!
I've experienced the infamous marketplace app error already. Appeared to work initially on the first attempt (downloaded Adobe PDF reader fine) but subsequent attempts just show an error screen. After an hour or so of headscratching and factory resetting it appears this is pretty much a given with these Scroll devices now. Am I right in assuming the way to fix it is explained in the post by Detection regarding the Market Fix?
The Scroll came loaded with FW version 0.94. Part of the process I took to try to resolve the marketplace app error (before I realised it's a known issue) was to upgrade the FW to 1.02. Only did it earlier this morning before heading into work so haven't had chance to see what effect it's had (if any) on the market app error. Was it a wise move?! Were there any benefits to doing this??
Battery life didn't seem great (and yes, I charged it fully before using it and have read somewhere that it's recommended to charge/run down to 0%/charge at least 3 times to get the battery working optimally!) but appears that there's some stuff running in the background related to the Android phones that drains the battery on the Scrolls faster than normal. Following some reading on here it seems it's worth uninstalling this and in order to do so I need to "root" the device? Again, is this the right assumption or have I latched on to something completely different?!?
Think that should keep me busy for now! I've also read about ways to improve the general performance of these devices on here (installing build.prop?!) but I'll just concentrate on getting it working properly first!
Si
First post on what I suspect is going to be a well used forum!
Picked up a new Scroll 7" yesterday and finally sat down last night to have a play with it. I have good experience of PC's and also iPhones but Android is something completely new for me and therefore I'm keen to start finding out about it.
I'm well aware of the "search before you post!" - and I'm quite happy to have a poke around and try things out before I get well and truly confused (highly likely!!) - so if someone could just confirm I'm heading in the right direction I'd be grateful!
I've experienced the infamous marketplace app error already. Appeared to work initially on the first attempt (downloaded Adobe PDF reader fine) but subsequent attempts just show an error screen. After an hour or so of headscratching and factory resetting it appears this is pretty much a given with these Scroll devices now. Am I right in assuming the way to fix it is explained in the post by Detection regarding the Market Fix?
The Scroll came loaded with FW version 0.94. Part of the process I took to try to resolve the marketplace app error (before I realised it's a known issue) was to upgrade the FW to 1.02. Only did it earlier this morning before heading into work so haven't had chance to see what effect it's had (if any) on the market app error. Was it a wise move?! Were there any benefits to doing this??
Battery life didn't seem great (and yes, I charged it fully before using it and have read somewhere that it's recommended to charge/run down to 0%/charge at least 3 times to get the battery working optimally!) but appears that there's some stuff running in the background related to the Android phones that drains the battery on the Scrolls faster than normal. Following some reading on here it seems it's worth uninstalling this and in order to do so I need to "root" the device? Again, is this the right assumption or have I latched on to something completely different?!?
Think that should keep me busy for now! I've also read about ways to improve the general performance of these devices on here (installing build.prop?!) but I'll just concentrate on getting it working properly first!
Si