This tablet was super fast when I got it but now it lags and drives me nuts. I’d seen someone post on Reddit that flashing the factory image helped so I gave it a go.
Factory images are available here along with good, clear instructions. One caveat, Arch needs super user for fastboot otherwise you get “< Waiting for device >”. For the same reason run flash-all.sh with sudo too.
As to whether or not it helped, it is hard to say but I feel it has. How do you measure something that is entirely subjective?
Edit. Its been a few days now and it is faster. Much faster and without lag. I’m unclear why though. I’m not completely familiar with Android’s architecture but wonder if it’s a combination of multiple updates being applied (this was I think Android 5.0 when bought) and accumulated futz.
It’s been a mixed start to the new year. Watching what I eat for the rest of January, damn you Christmas. Back at work after three weeks off, achieved nothing and left by eleven. My ego got the better of me and I went for a run despite having a cold, so am now suffering. Need to shift it with the first cross country league race on Wednesday. I can’t help wondering why generic medicines are so much cheaper than brand names.
Finally got around to ordering a replacement Acer V3-112P screen. Replacement was straight forward. Like most avionics technicians, I breathed a sigh of relief when the LED panel lit up proving the fault. The old girl is now sitting running a million updates courtesy of Microsoft.
While many Linux advocates eschew Microsoft, I prefer Office (Home Use Program). Like current, I take the path of least resistance and I use Word and Excel so often I know them inside out. Linux is an outstanding development platform, I’m using it for TM470.
TM470 project preparation continues, reviewing both TM353 and TM354. FutureLearn is a fantastic resource with a course on Secure Android Development. Delivered by the University of Southampton, it started last week. I haven’t decided the tool chain yet, particularly versioning. I have used SVN and Bazaar, which I prefer as it integrates well with Launch Pad. I won’t be using LP though so should investigate Mercurial and Git.
Read Original Sin too – best Marvel I’ve read in ages. Like Murder She Wrote in space. A real page turner, I read it in one sitting.
Something that didn’t grip me was the Assassin’s Creed movie. It starts off quite well, with a similar story to the games. It suffers the same problem as earlier games though – the present interrupts more interesting stories in the past. What I don’t get though is why option a game as a property then try not to appeal to that market?
What I haven’t made time for though is the Nintendo Classic Mini. I played a little Ghosts ‘n Goblins – damn I forgot how hard games were then. I always thought as a kid that I’d somehow be better at them as an adult but I guess I didn’t factor in reactions.
I removed Ubuntu from a Samsung NC10 yesterday, now the F4 recovery option doesn’t work. Please excuse the lack of screen shots on this Howto but I couldn’t think how to capture from the recovery manager and camera shots look rubbish.
It would appear that Samsung uses a custom Master Boot Record (MBR) – so for Grub all is well because you can choose to boot into the recovery partition and away you go. However if you have followed any of the usual guides to removing grub (such as running an XP CD to a recovery console and typing fixmbr) F4 will not launch the restore tool.
System Rescue CD is a great tool to have handy on a USB key. You can, so booting into it run this command:
Now pressing “p” should show you that the recovery partition is 1, so type “a” then “2”, “a” then “1” to make it bootable. Now write the partition table by typing “w” then reboot. At this point you will boot into the recovery manager and be able to recover but the F4 key will not still not be available at boot and of course trying to create a backup will not work either (as Windows will be booted on restart).
Once Samsung Recovery Manager III has loaded up, press Ctrl+Alt+F10 – I had no idea there was a management mode until I read this page (French) but be aware its only available from the recovery partition. It asks for a password – “secos” (without the quotes). Once in management mode, click the “Image” tab and select “Export” then “Select Location”, I used “D:”. Click “Start” and accept the dialogue box that comes up. This is a backup of the recovery partition.
Once this stage is finished, select the “Tools” tab, insert a spare USB stick and click “Admin Tool USB”. It will format the USB stick and then install some utilities. It takes a couple of minutes. Once finished click the close button in the top right and it’ll ask if the computer should be turned off – say yes.
Boot with the USB key we just made, bringing you to a completely different recovery menu. Click “MBR Fix” and then close the application.
Now when you reboot you’ll notice that the MBR has been repaired and F4 once again boots into Recovery Manager III.