Goal: 8K @ 7:53 pace

Achieved: 4.84K @ 6:03 pace

Dilbert Comic Strip on 2015-02-22 | Dilbert by Scott Adams.

Goal: 2.3K @ 7:53 min/km pace

Goal: 4.4km at 7:53 min/km pace

Achieved: 4.84km 6:18 min/km pace

Why you should never swear at strangers on the train http://telegraph.feedsportal.com/c/32726/f/568330/s/4392a07e/sc/7/l/0L0Stelegraph0O0Cnews0Cnewstopics0Chowaboutthat0C114242260CWhy0Eyou0Eshould0Enever0Eswear0Eat0Estrangers0Eon0Ethe0Etrain0Bhtml/story01.htm

I am a Ram :D

Cooper Test today. To see how far I can run in 12 minutes. Answer? 2.18 km. My personal best for a Cooper Test is 2.8km, so I am about 0.7km slower. Not too bad, but it does prove my fitness has dropped since my peak fitness.

Next run on Friday (4.4km @ 7:53min/km target pace)

Goal: Long Run 8K @ 7:16 min/km pace.

Achieved 4.58k @ 6:53 min/km pace. Fell way short of my target, but it is still early in the plan. I must really up my game (and mileage)

(Day 2 missed due to weather)

Goal: Easy 2.3k run at 7:16 min/km pace.

Achieved 2.38k at 6:11min/km ave pace

Me included….

Target: 4.3km run at 7:16 min/km pace. Achieved 4.69km @ 6:44 min/km pace.

Next run on Friday, 4.4km run, easy pace at 7:16 min/km. Today’s run was a toughie (haven’t run in excess of 3K for a while).

Who comes up with these ideas?!

My plan has been setup and starts this week. First run is on Wednesday and is a 4.3 km run with a 7:16 min/km target pace.

In true Final Fantasy tradition, there is concept artwork, this is an amazing design:

I have got a place in the Royal Parks Half Marathon. Now waiting for my race pack to arrive. In the meantime, I will be adjusting my training plan.

The sports apparel company has agreed to buy MyFitnessPal, a popular diet-tracking app, for $475 million. Under Armour announced the MyFitnessPal acquisition, as well as the comparatively smaller $85 million purchase of running app Endomondo, alongside its quarterly earnings report Tuesday afternoon.

Heck, I use both apps…. ^_^;

Under Armour buys MyFitnessPal for $475 million.

The name may not mean much to some people, but to some, he is a well-known game animator, producing hugely popular shorts and series such as RWBY and my favourite, Dead Fantasy – a cross between Dead or Alive and Final Fantasy. It has been reported that he has passed away due to an allergic reaction during a medical procedure that put him in a coma.

Here is the blog entry detailing the news: roosterteeth.com/members/j…

And in case you haven’t seen his work, here is Dead Fantasy (all the parts spliced together)

www.youtube.com/watch

As you’re probably aware, I love to tinker with phones, especially Android ones, having been able to root several:

• HTC Wildfire
• HTC Sensation
• Asus Transformer TF101
• Samsung Galaxy S5

However, when trying to tinker with my dad’s S5, some really weird behaviour occurred. I first unlocked it using a SIM unlock code, and it started to randomly reboot. Regardless of whether or not you use an EE SIM or not (we tried EE, Virgin and Three SIMs – all were subject to the rebooting behaviour). So, I decided to take a change and rooted it and flashed Bobcat ROM (a ROM which I was running successfully on my own S5, which is the same model as my dad’s with the only difference being the network provider – I’m on Three, he’s on EE.)

The phone still randomly rebooted, so I turned on Logcat and tried to see if it recorded anything. No such luck.

So I tried a few different ROMs – Stock Samsung (Lollipop), Bobcat ROM, and Phoenix ROM. All still rebooted. So I took it to Samsung for their opinion. They said they couldn’t flash it because Knox was void (Knox is a warranty flag on Samsung devices which indicates whether you have custom flashed the device or not – I obviously have.) But they were nice enough to tell me that the behaviour described usually indicates the Firmware is wrong (which is something I didn’t flash).

So, since this behaviour started before I even did a deep-level tinker with the device (before I flashed anything), I can only assume EE either flashed an incorrect firmware, or did not flash the correct firmware - or maybe did not flash the firmware properly. I now need to find an S5 firmware to flash onto the device. Since my own S5 is working, I can check that firmware and try to find the same one.