Not far into my New Forest Marathon training and I’ve hit a slight problem, in that I’ve gone and sprained my left ankle. A simple Sunday evening job in the garden turned into a visit to A&E in the early hours of Sunday morning (Recommended time to go by the way – I was the only one there!).

I was sure I had broken my ankle – I turned on the ball of my left foot, managing to find a ditch in our lawn, lost my balance and rolled my foot inwards, putting my whole weight on my twisted ankle – I heard and felt a definite ‘snap’ as I went down. The pain wasn’t terrible afterwards, but was much much worse when I woke at 2am this morning – Hence the visit to A&E to check it wasn’t broken.

So – What next? 2 weeks rest minimum, then back to gentle running – Although I may be tempted to try earlier that this – If there is no pain after a week, I’ll try some skipping, then move onto a short (1-2 miles) run.

There is still a small possibility that I can get Marathon fit by 25th September – Its going to take some intense training, to the point of having to sacrifice even more time normally spent doing other stuff.

I’ve just found a solution to a problem that I’ve spent the best part of three evenings working on – Getng the ADB (Android Debug Bridge) working for my shiny new Samsung Galaxy S2 (i9100).

Heres what I to finally get this working:

  1. Disconnected my phone from USB
  2. Using USBDeview, I deinstalled all previously installed drivers relating to the phone (Careful here!)
  3. Installed Samsung Kies, and loaded it
  4. From Samsung Kies, I selected Tools > Install Driver (This step took a while, and it seemed like it had stalled – Be patient!)
  5. Connected my phone to USB
  6. The devices installed – Windows then gave me an error regarding missing drivers, however, when I checked device manager, I could see ‘Samsung Android Phone’ under which was ‘Samsung Android ADB Device’
  7. I then ran ‘adb.exe devices’ (From a command prompt – adb.exe lives in the android-sdk folder) – This listed my device! Hoorah!

Whats this all about then?
Well, in the main, its about Android app development. Whilst it is possible to develop apps using an emulator, you can also develop and debug using a hardware device (i.e. a Real phone). In order to do this, ADB (Android Debug Bridge) needs to be able to see the device. It seems alot of people have problems getting this working, so hopefully this will be helpful. If so, please drop me a comment!

Follow

Get every new post delivered to your Inbox.

Join 30 other followers