Worth Checking Out: The Survival Podcast

Posted by on December 30, 2012 No comments

The last couple of weeks I’ve been listening to a podcast called The Survival Podcast.

Unlike most Survival/Prep podcasts I’ve ran into that seem to either focused on disaster survival with no awareness that day-to-day issues exist (read: The Walking Dead) or podcasts that feel the next logical step is living in the wilderness with none of the amenities of life before (read: Grizzly Adams), TSP knows that we have a regular life and as the host states every episode “Helping you live a better life if times get tough, or even if they don’t.”

TSP does a great job of keeping perspective that your biggest challenge isn’t likely to be the end of the world but more likely to be the loss of a job, loss of a home, inflation, robbery, storm or many other items, which might threaten your comfort on a day-to-day basis more than nuclear war or immediate government collapse.

The host, Jack, occasionally gets very emotional about topics but as long as you understand that it is because he cares and has an opinion, it is good stuff. It fits my need for “how stuff works” type of knowledge along with a solid dose of practical application; I can’t wait to build a battery backup system. As part of his (their?) desire to build a community-driven website for developing new skills they have introduced a new website called 13Skills, which I’m looking forward to trying out.

Samsung Galaxy Note II (GT-N7100) Impressions, Mods and Essential Apps

Posted by on November 15, 2012 No comments

I’ve been using the Samsung Galaxy Note II for about three weeks now. There are lots of reviews talking through the entire pros/cons list for the phone so I’ll focus on my specific observations rather than attempting to review the phone. As with most Android devices, XDA-Developers is an awesome forum and should be your go-to source for information if you want to dig into the guts of the system.

The questions that come up over and over:

  1. Does it fit in a pocket? Unless you wear skinny jeans, absolutely.
  2. Is it too big? With my small mitts, I need to use it two-handed most of the time, although this has not been an issue other than while trying to dial the phone while participating in another activity like carrying bags or driving. Now that I’ve said this, I love the larger screen.
  3. Has it replaced anything? The Short answer is Yes, it has replaced my 7” tablet + phone combination. For general use, I now only carry the Note II exclusively. If I’m going to read for an amount of time or am idle at home I’ll often pickup the Nexus 7 for a bigger screen. If you told me today I either had the choice to ditch the tablet or had to move back to a <5” phone to keep the tablet I would ditch the tablet and call it good. The screen is a perfectly usable size and I would have no fear reading entire books on it, which has never been something I would commit to with a phone in the past.
  4. Is Android ready for my parents? The Nexus 7 and Note II have proven to me that Android can be a reliable, daily-driver operating system. With these newest devices I would trust giving an Android phone to my (stereotypical, not real – the real one is more tech-savvy) mother, which is something I never would have endorsed in the past.
  5. Is the Stylus actually useful? Absolutely, especially when taking quick notes. For the first week it was a toy but I was still reaching for real paper when jotting down an address or other information. Not anymore, now I auto-pilot to my stylus and take the note, then go on my way. The only time this is a problem is if I’m creating a reminder, which you would typically stick in a place where it was apparent – it would be nice on the Note II to have small thumbnails of say, your last three notes so that you see that reminder each time you turn-on the phone.
  6. Is there a feature most people don’t know exist but is super cool? There are a TON of cool features hiding in the phone, shake the phone to do this, turn over to do that, eye detection (don’t turn off the screen if I’m looking at it) but the one feature I haven’t seen highlighted is the wireless charging capability, which I’ll talk about in the mods section below. The one other item that kicks ass is multi-window mode, which I’ll talk about in the mods section.

Apps built for phones running on the Note II:

I think it was on one of The Verge Podcasts where I heard them talk about the difference between Android Apps and Apple Apps. With Android apps, the apps are primarily built for phones and then scaled to tablets. With Apple, there is an entire ecosystem just for iPad apps.

Android needs this focus on two different types of apps and the Note II should have an option to use the tablet category (it might not fit all apps but will fit the majority.) Some of the fonts in apps are comically huge, which is great for people who have a hard time reading small fonts but it is pretty humorous. With this said, I’ll talk below about one of the mods I’ve performed to provide a little more screen real-estate. I should also note that Samsung has done a good job of adapting some apps, such as the phone dialer and default keyboard for single-hand use but those changes are largely a college try rather than a real solution in my book.

Now that I’ve thrown stones at Android Apps, I should mention that on my prior phones if I was going to read for any amount of time I moved to a tablet, whereas on the Note II I often forget that I have another tablet handy – it is that easy to read and view text.

Artificially Black Areas or Black Crush:

There is a forum post on XDA-Developers focused to issues with “black crush” or black issues on the Note II, which also haunted the original Note. I have one spot on my screen – a bit like a marker mark half-an-inch long, which is a little up from the middle of the screen. You can only see it when the screen is a dark grey; in those circumstances the spot is black when the rest of the screen is grey. I only see it once every few days, usually while in an app with a pretty dark, but not black background. It is a minor irritant, nothing to get worked-up about. It sounds like most of the owners have some sort of issue with their AMOLED screen whether or not they ever see it so I’m not worried about it. It is part of the risk associated with using a young technology in a production device.

Is the stock firmware good?

If you are new to the phone but do not want to dink with it, the stock firmware works great; no need to jump down the custom/modified firmware rabbit hole. There is a TON of useful functionality in the stock firmware. With this said, once you’ve decided to root, or do anything else, it is worth upgrading to the latest software before you start modding since many mods require newer firmware. When I acquired my phone it did not upgrade over the air but once I plugged it into the Kies software it had an update so for those who want to remain stock loading Kies is useful.

My Current Mod Status:

So far I’ve spent a significant amount of time dinking with the phone, although I’m still on Stock firmware to this day, which has proven solid and reliable. My phone originally shipped with an early version of the firmware, which I attempted to upgrade but Samsung detected that I had rooted the phone (primarily to get a solid backup using Titanium backup.) After reading about whether it was worth upgrading I decided to take the leap and rather than mess with going with the same country (Germany is where my phone was originally spec’ed for) I went straight to the newest Hong Kong firmware. I’ve noticed at least half a dozen refinements throughout the OS so it was worthwhile to make the leap before investing a ton of time into customizing the phone.

Below are the mods I have implemented and find useful:

  • Inductive/Wireless Charging – Taking off the back of the International version of the Note II you will notice two pin connections on the right side of the phone, which are unused. Those are the inductive charging pins. With a couple of ebay orders you can be wireless charging easily with no soldering or other hardware hacking. XDA has a few good posts discussing your options.
  • Root – At first I rooted to get Titanium Backup working, which is great if you upgrade/customize your phone. Now I’m using a few apps, which require root with the most important being the multi-window hacks and changing the LCD Density, which I’ll talk about below. It would be poor of me to not mention CWM Rom Manager/Recovery, which is important for any phone where you start hacking the firmware – sometimes when your phone isn’t booting, the easiest way to get it back is to restore your latest Nandroid backup.
  • Multiwindow Modification/Unlimited Apps – One of the coolest features of the Note II is multiwindow, it is also one of the most frustratingly limited since out of the box it is limited to <20 apps. With a fairly easy mod (assuming you are running the right firmware version and rooted) you can enable Multi-window for any app. I use this feature every day to bring up my password manager while browsing to websites or other applications.
  • DPI/LCD Density Change – By default the Note II doesn’t effectively use all of its resolution. If you prefer smaller fonts, notification bars and the like you can dink with the LCD Density setting, which will change how fonts and other graphics are handled on the screen for any DPI-aware apps, including the core OS. At this point it causes a bit of graphics oddness in apps such as the camera but that compromise has been completely worthwhile for me. At this moment I’m running a DPI/Density of 280 (about 13% more usable resolution), although I’ve been experimenting with 240 (25% more space) on and off also. Making the change is pretty simple, right now I’m using a tool called ROM Toolbox to make the change.
  • Launcher – Touchwiz, the default Samsung launcher, although lovely and tying beautifully to the stylus, is limited. Not being able to change the number of rows/columns on the screen means that there is an excessive amount of unused area on the screen. My go-to launcher for phones is ADW, which has been a good go-to for my device.

Overall, I would say the Note II is my favorite phone since the days when the iPhone 3Gs was cool. I’ve had three Android phones and three Android tablets so far and up until the Nexus 7 and Note II none of the devices felt put-together, there were always quirks, crashes, and other issues that caused what should be a reliable experience to occasionally become frustrating, even on stock devices.

The Note II and Nexus 7 have proven to me that Android software development is maturing and has the capability to do everything you need, every day. What is even better, is that Samsung’s add-on software to the Note II, although in a few places feels like bloat, is overall a huge value and completely worth the additional load. With this generation of Android devices I’m finally feeling good about trying to convince my wife that Android is her next-step (unlikely but I can try.)

The Lasik Experience – Four Years In

Posted by on August 1, 2012 No comments

It has been a little over four years since I had Lasik, which took my vision from “Only adequate at less than six inches” to “Reading street-signs at inhuman distances” in a matter of minutes.

The only long-term issue I had coming away from Lasik was dry eye. Four years later, I’m good to go. If my eyes are bugging me it is usually because I’m tired. This last winter I had to use eye drops only a handful of times, which is more than it was when I wore glasses but plenty acceptable.

Eyesight in one of my eyes is a little less sharp than it was. I suspect on a test I would still score a combined 20/20 but there is just a little less sharpness. It will be years before I need glasses or a touch-up but I can tell things have shifted a little.

As the doctor warned me, and I have witnessed in my family, I’m a little far-sighted at this point.  Reading at less than a foot or so becomes straining quickly, and small fonts on computer screens become an issue. On my notebooks I’ve found myself making the compromise between screen-space and font-size often. It isn’t too bad yet but in another ten years I’m sure I’ll need reading glasses, which is perfectly good with me.

It is worth noting if you have not read my prior blog posts on Lasik – my eyesight was very poor. In the shower the only way I knew where things were was by color blotches and in order to read my alarm clock I had to pull it within a few inches of my face. Due to this my risk vs. benefit perspective might be a bit different than many others so your mileage may vary.

Overall, other than getting married (obligatory plug so my wife doesn’t kill me :P ) and saving for retirement it is still one of the top investments of my adult life.

The Skype Podcast

Posted by on July 19, 2012 No comments

My first few experiences recording a Podcast via Skype sucked. I had all sorts of cables, hardware, and other complications that in the end were not required.

Below is my setup for recording sessions over Skype while on the road. It is simple but still keeps the risk for issues as low as can be without having several computers and a super-sexy Internet connection.

  1. Use your computer for Skype but nothing else. Shut-down all background applications. If you can arrange a hard-wired Internet connection, use it. Even if your Wifi shows 5 bars I’ve found wired connections to be more robust. If you still have issues, cut the video and perform an audio-only call.
  2. Use an external recorder. I use a Zoom H2n paired with either a pop filter or windscreen to cut the noise a bit. It does a great job of being able to record the podcast while also being able to handle the stereo output from a computer (an issue for many recorders, which were only built for line/mono-in).
  3. Don’t get overly concerned about how well the remote Skype participants hear you – Skype does a solid job of setting the gain on your signal to the appropriate level as long as you have a mic in the first place :^).
  4. Use a single cable between the recorder and the computer; I use the stereo-out audio jack on the computer connected to the line-in on the recorder.
  5. Don’t plug power into your recorder and computer at the same time. I know it is tempting; I think about it every time I connect my devices up. Due to potential noise issues, only connect one device to power if possible.
  6. Set your microphone (and beer/drink/bottle of wine) on a towel. This doesn’t sounds amazing in any special way but assists a great deal when the microphone stand shifts around, or you pickup your bottle of JD to take a swig. Yes, you can use a hotel towel, they won’t charge you.
  7. Plug your headphones into the recorder – this will assure that you hear the recorded signal rather than some artificial signal.

That is about it. If you check your microphone levels and assure that the room isn’t complete trash for recording it usually works out pretty well. The biggest tip with online audio recording is to remember that if the audio is not performing up to spec have the person repeat, and if necessary re-connect to the conference. If you can’t achieve reliable Internet access all-else becomes difficult.

Newbie Podcast Production according to a Podcasting Newbie

Posted by on July 6, 2012 1 comment

I’ll be the first to admit – I’m new at Podcast recording. We’ve only been doing it for about three months now. With this said, after the last three months I wanted to post a note regarding how we were doing production today. In later articles I’ll cover the details of how we manage the individual components, along with tweaks we make over time.

Today’s post will be high-level. In future articles we’ll dig into each aspect of recording and how to perform those specific tasks.

A High-Level Overview of how we Record/Produce:

  • Record your Podcast – On the road I use a Zoom H2n Recorder (line-in from my computer for the remote Skype participants – the H4n is also a popular model for Podcast recording) and at home I use a Korg D-888 mixer/recorder that I picked up from a pawn shop. You could use anything including your computer as long as it has good recording fidelity.  Anytime you google about music or podcast production you will find people stating that your microphone makes all the difference; I agree. Spend $40-$100 on a good microphone setup if you are going to keep it up. At the moment the two primary microphones we use in-house are an AKG Perception 120 and Audio-Technica AT2020, both <$100.
  • Import into Audio Editor/Digital Audio Workstation (Reaper in our case) – Import the WAV files into your audio editor on individual tracks. Setup reaper per the directions here for a podcast. The one other thing I do every time is turn off Grid Snapping in the Options menu.
    • Another thing I will note here is that whomever is editing should have a reasonable set of studio monitor headphones or speakers (I use headphones to keep it economical) for first-pass editing. Due to their frequency response you will hear issues on the track, which a normal set of speakers or headphones might not properly represent.
  • Normalize the Audio – Normalization modifies the volume of the track to a consistent level across the entire track. This will help you be able to hear things and keep the volume levels consistent. Reaper has a built-in Normalization function in the Item Properties dialog for each track.
  • Compress the audio – I use ReaComp, a supplied Reaper plug-in for this purpose. At the risk of an overly simplified description compression reduces the volume levels of audio after it reaches a certain point. It can do it slowly and smoothly or abruptly depending on how the compressor is configured. This helps to keep the audio pleasant to listen to, although it can also be used to add effects or specific distortion, which might be good in some circumstances.
  • Gate the Noise – For noise-removal I use the ReaGate Reaper Plug-in, although I’ve also been evaluating migrating to a gentler manner to remove noise from our tracks since some small level of noise is not a bad thing. In its most simple form with a gate you select a specific volume level and any audio that does not break that basic volume level is cut-out, removing the background noise. Today I tend to leave the quietest microphone un-gated so that there is some small amount of background noise.
    • Something to be aware of is that removal of all noise can be disconcerting to the listener, hence why on Voice over IP phone systems there is something called “Comfort Noise”, which provides a slight amount of background noise so that you know your phone handset is working. Use your personal judgment as to whether you leave any noise in your tracks.
  • Edit the Podcast– This is the longest portion of the entire process. You listen to the podcast and edit out long dead-air periods and depending on how refined you want it to be you remove excessive “ummms” and other over-used sounds/words. The Alt-P (Ripple Editing) hotkey and Command-Delete to remove highlighted sections (at least on Mac) are your friend. By editing multiple tracks at once and having Reaper automatically shift the sections where time was removed left you can save a lot of time.
    • If you are going to have a timeline/notes posted with your podcast this is also a great time to take those notes.
  • Export/Render to WAV – After editing in Reaper I export the podcast to a WAV file at full quality.
  • Pass through The Levelator - The WAV file is fed into The Levelator, which does a great job at making the audio levels consistent across the board, smoothing things out a bit more. The Levelator really is an amazing tool for getting quick results on a podcast, although if your audio levels are very different between people, you might find the really quiet ones disappear so you will want to check.
  • Convert to MP3 – Use whatever tool you would like to convert the file to MP3. I’m currently using Garageband (this is one area I should just spend an hour and setup another tool but I’m lazy and the to-do list is long :^) ) but you could keep it simple and use any random tool or throw the files back into Reaper and use LAME libraries to perform the export. The real tip here is to remember to balance audio quality and size. Currently I’m using 80kbps VBR (Variable Bit-Rate) Mono, which I find provides reasonable file sizes without inheriting the tinny sound that overly-compressed MP3s do.
  • Check – Check your podcast and make sure all people can be heard, and that the sound seems consistent from beginning to end. This is another point where listening with your studio monitors and one or two other sets of speakers/headphones is a great move. Not everyone will have studio monitors so you need to assure your podcast sounds good over other sets of speakers. I tend to listen to test-run samples via my notebook speakers, a good set of desktop speakers, and a set of $20 Sony headphones in addition to my studio monitors.
  • Upload – I’ll let you figure these bits out. Right now I’m using the blubrry.com statistics service and storing the files on my 1and1.com Internet account, although I’m always evaluating when it will be time to move to a service dedicated to fast downloads for podcasts. Most of the heavy lifting is done by plug-ins for wordpress.

I’ll leave it at that tonight. If you would like to know more or have advice/comments drop me at note at r.andom at this website.com or via a random social network.

Nest Thermostat Update 3

Posted by on July 5, 2012 No comments

After the last few updates I’m feeling much better about the Nest Thermostat. They have added statistics to the website and my Nest has not dropped off the network in months. If I were to do it again I would still evaluate the Ecobee as part of my options but at this time, for the price, I feel the Nest is a good value and I’m excited to see where they take it from here.

A couple of memorable podcast episodes…

Posted by on May 10, 2012 Comments Off

While driving from point A to point B somewhere in the south I heard two podcast episodes that stuck out in my mind as being more interesting, fascinating, strange, or otherwise engaging than others I’ve listened to recently.

Here they are: