Connecting Samsung Galaxy Note 3 to adb

I have a non-rooted Samsung Galaxy Note 3. I installed the Android SDK and Android Studio on my Windows 7 PC, but when I attempted to upload an app to my phone it didn’t offer my phone in the list of connected devices. The various sites I found on the ‘net gave various hints, but didn’t give me all I needed.

Here’s what you need to do.

  • Install the Samsung Android USB driver for Windows. Various sites claimed installing KIES was enough, but it wasn’t. Other sites offered drivers, but I’m not keen on installing drivers from random sites on the Internet. Here is the official Samsung Android USB driver for Windows page on
  • Plug in your phone, and wait while it installs the drivers. Wait until this is complete.
  • Enable developer mode on your phone: go to Settings > General > About device, and click on the “Build number” 7 times. This gives you a new menu, “Developer options”.
  • Ensure Developer options is on, and turn on USB debugging.
  • Choose “Revoke USB debugging information” to clear any existing permissions. Turn USB debugging off and on again to ensure this takes effect. (This step may not be necessary.)
  • Accept your computer in the popup that appears on your phone, to authorize it.
  • Run “\platform-tools\adb devices” and confirm that your device appears, and has “device” against it. If it says “unauthorized”, see above.


Précis of Danesfahani and Jeans, Optimisation of modified Mueller and Müller algorithm

This post is a summary of the main content of G. R. Danesfahani and T. G. Jeans, Optimisation of modified Mueller and Müller algorithm, Electronics Letters 31(13), 22nd June 1995, pages 1032-1033 (DOI 10.1049/el:19950711). The original paper is copyright IEE, and is available from IEEE or your local library. The algorithm described in that paper is the one used in GNU Radio‘s gr_clock_recovery_mm block.

The paper first recalls the modified Mueller and Müller algorithm: given

  • data symbols a(i)
  • received signal p(k) with real part p_r(k),
  • the receiver’s decision on the data symbol \hat{a}(k)

then the modified Mueller and Müller algorithm (mM&M) computes an error

\mu_1(k) = (\hat{a}(k-1) - \hat{a}(k+1))p_r(k).

The paper then observes that this algorithm contains a self-noise term which can be cancelled by adding

\mu_2(k) = \hat{a}(k)(p_r(k+1) - p_r(k-1)).

The resulting algorithm, the optimised modified Mueller and Müller algorithm for real symbols (e.g., BPSK), outputs a timing error

\tau = 0.5(\mu_1(k) + \mu_2(k)).

This can be generalised to the complex domain (e.g., for QPSK) as

\mu(k) = {\bf R}((\hat{c}(k) - \hat{c}(k-2))p^*(k-1) + \hat{c}^*(k-1)(p(k)-p(k-2))),


  • \hat{c}(k) is the receiver’s decision on the (complex) data symbol, and
  • p^*(k) is the complex conjugate of p(k).

Figure 1 presents this equation in the form of a block diagram, including a combined filter and interpolator (and presumably sampler) betweeen the input signal and p(k), a decision block between p(k) and \hat{c}(k), and a loop filter driven from the real output of the equation via \beta which influences the filter/interpolator/sampler.

The paper then presents simulation results (using a gain factor of \beta = 0.18) which show that while the mM&M algorithm has fast acquisition it has lots of jitter and some symbol slips; by contrast the optimised mM&M algorithm exhibits much less jitter and no symbol slips, while preserving the same fast acquisition characteristics.

Weather station now live!

I’ve been enjoying the weather page and graphs I put together for a few months now, and I’ve been steadily adding features. So I guess it’s about time I opened it up for everyone else to see too! So here it is: Wallace Brae Weather.

The current observations are at the top: temperature, relative humidity, wind speed (average and gust). This is followed by recent rainfall. Finally, we have the extrema: low and high temperature and highest wind speed over the last day. Then there is the time of the last observation – use this to check the system is still live.

Below this are the graphs: one for the last 24 hours, and one for the last week. Blue is rain (area corresponds to rainfall, and height to rain rate), red is temperature, yellow is humidity, and green is wind speed (dark is average, light is gust). I’m working on the best way to present the scale for the Y axis; for now you’ll have to work it out. The grey horizontal lines mark key points (e.g., 0 and 10 degrees C).

You can read about where it came from and how it works on the weather category on this blog – I haven’t posted much yet, but hopefully there will be more soon.

Enjoy! And do let me know if you like it!

The nearest other weather station I know of is the Polmont weather page, a bit over a mile north-east of here, down the hill.

SDR and weather stations

I’ve been having fun recently learning about software defined radio (SDR). The impetus is this weather station, which Aidan got for Christmas.

We’ve all very much enjoyed the information it provides, and it’s been a great talking point with the receiver on the family dining table.

But when we’re at work or on holiday, wouldn’t it be nice to know what the weather’s like back home? Is it raining? Has the fence blown over? For that reason, in May I bought one of these:


NooElec R820T SDR

The mast transmits the weather data to the display by radio in the 433 MHz band. This NooElec NESDR Mini is a software-controlled digital radio receiver which covers 25MHz to 1750MHz. So it should work!
Since I got it, I’ve been busy learning how to make it go. This has turned out to be more complex than I realised – I finally got it all working in October! – so expect a series of follow-up blog posts.

plink port forwarding works but PuTTy’s doesn’t

Bizarrely, the answer is “fonts”!

Spent ages last night trying to work out why on my new PC forwarding 9418 to localhost port 9418 wasn’t working:


Curiously, X11 forwarding worked, and plink -L 9418:localhost:9418 … worked too – but the above didn’t. Can you see it?

The new PC has lots of pixels and the text was small. I first typed this


but it looked to me like I’d missed the colon, so I added one – see above. Turns out localhost::9418 is not a valid port forwarding destination, but there’s no error. It just silently failed.

Changing it to localhost:9418 (as I originally had it) of course made it work. PEBKAC again 🙁 .