Looks like most of it was shot in and around Portland, which is also fun. http://peopleforbikes.org/
About a week ago I got the Nexus One from Google. Today I decided to delve into the SDK and see if I could get a “Hello, World!” script running on the phone. Following the Android Developers website, I downloaded the SDK and installed the Eclipse plugin for Android. I was able to get the Hello, World! script running fine in the virtual Android machine, but when I started trying to connect my phone for debugging I started running into issues. I’m using the Nexus One which is currently on Android 2.1 and I’m on OS X 10.6 (Snow Leopard). It seemed that whenever I ran the command adb devicesin the terminal, I got an empty list of devices. Frustrating.
Well after scouring the internets with no results, I remembered that when I installed the SDKs with Eclipse, there seemed to be a lack of overlap between the two. When installing the Eclipse Plugin, it creates a folder in the workspace called com.google.android.sdk, except this SDK doesn’t line up with the SDK from the Android Developers site. When I had initially put things together I simply copied over some of the files created by Eclipse to avoid breaking the plugin. But when running adb devices, it was running from the Eclipse provided SDK. Upon trying again with the adb command from the Android Developer’s SDK, the phone shows up on the list of devices. So now I’m copying arranging files to use the good SDK.
Not sure if this will have an effect on the Eclipse plugin. I’m assuming not. My guess is that the Eclipse plugin was simply packaged with an older version of the SDK. We’ll see though. So happy to see the Android SDK is in Java though. Way better than the iPhone SDK.
UPDATE:
Looks like you don’t want to overwrite any files. Simply leave the com.google.android.sdk directory as is and point to the downloaded SDK in the Android preferences pane in Eclipse (SDK Location). I had to delete and recreate my helloworld project in Eclipse to repair the errors due to the missing core library (android.jar).
via eBay
After 2 long loyal years I’ve decided to sell my iPhone. Why? Damn the Man. Save the Empire. That’s why.
For quite some time the idea of building my own wheels has intrigued me. There just seems to be this mystical perception of wheel building. That you’d have to be a skilled and train professional to become a wheel builder and that somehow anyone who knows how to build a wheel was born with the gift and knowhow. Simply put, it’s seems to be an unobtainable goal for most bike enthusiasts. Naturally, I felt determined to overcome this perception and delve into wheel building myself. I also love bikes partly due to how sustainable they are. Not in the eco-friendly, save the planet sort of sustainability — although they’ve definitely got that going for them as well — but I’m talking about sustainability in the sense of basic independence. I love that I can get on a bike and ride free of charge and when something goes wrong I’m able to fix it myself. Aside from running into a local bike shop for a new intertube or the like, I don’t need to depend on anyone but myself. And as I’ve mentioned in earlier posts, I’m building up my Long Haul Trucker with the goal of doing everything myself; and of course, this includes wheels.
I’m using these wheels for loaded Touring and so I wanted something pretty tough. I may have got a little overboard, but from all the research I’ve done, it seems that when it comes to touring, going overboard is rarely a bad thing. And since the most common issues people run into is with their rear wheel, I wanted to have something pretty tough. After researching, I decided to go with Mavic A719 rims and Shimano’s Deore XT hubs. The decision for the hubs was largely based on availability. Generally speaking, a rear hub with 135mm spacing (a standard for mountain bikes) that isn’t fitted for disc brakes can be hard to find. Disc brakes have become a norm for mountain bikes and so there are limited options when it comes to non-disc 135mm rear hubs, or so I found. It would have been great to fit the bike with disc brakes, but since the LHT frame isn’t built for disc-brakes I didn’t want to risk the added stress to the frame. The XTs seemed to be a solid hub for a reasonable price that fit my needs. As for spokes I when with some pretty gnarly DT Swiss Alpine III spokes, which are triple butted at 2.3/1.8/2.0. Word on the street is that they’re pretty f***ing tough. As for nipples, I just went with some DT Swiss brass nipples. Nothing fancy there.
So here are some shots of the wheels…
my first wheelset
Mavic A719
Shimano Deore XT
fancy shot
current build
Seems that since 1980 Republicans have found a new meaning to the phrase “fiscally responsible” which ironically has nothing to do with being fiscally responsible. I also find it interesting that (according to this graph) is appears that George W Bush’s contribution to the national debt seems to have doubled in the final year of his presidency. Burn and run Bush. Burn and run. Turns out he wasn’t as immature and irresponsible as we’d thought. I really don’t know who he could have learned it from either? Hmm…
For those who don’t like to read: the fix.
I upgraded to Snow Leopard (OS X 10.6) from Leopard (OS X 10.5) last week and everything seemed to go off without a hitch, until…
I have a bluetooth, wireless, keyboard that I use for work. At some point in the past week, not initially, my keyboard started acting up. At first I didn’t think anything of it because the lady’s computer is also paired with the same keyboard and when the problem first occurred it was because the keyboard was connected to her computer, also on Snow Leopard, rather than mine. I ended up removing the keyboard from her bluetooth setup and re-pairing (no pun intended) the keyboard to my computer. Everything worked fine and I went through my day.
The next day, I found that my keyboard would not pair up again. WTF!? So I go through the process again, thinking maybe Laura and I did a keyboard swap or something and that was the problem. Re-paired, everything’s cool. Whatever. If it happens again, I’ll deal with it.
Finally, today, day 3, I start up my computer and the keyboard won’t connect. Immediately I try to re-pair the keyboard and suddenly the computer tells me there must be some compatibility issue. Thanks Apple. I have an Apple keyboard I’m using with an Apple Macbook Pro and I have a f***ing compatibility issue. You’d think they would make sure that bluetooth continued to work between upgrading from Leopard to Snow Leopard. Oh well.
So I resort to Google. And basically what I find is that I have to reset my System Management Controller (SMC). Do I know what an SMC is? No. Do I care? Not really… okay, so I do a little. Apparently the SMC handles a lot of the lower level operations performed by the computer like “the power button”. Sweet Apple. Okay, so what to do. You have to reset the SMC. To do this follow the steps specified here. Be sure to read through the process and select the procedure that matches your computer. Different laptops, desktops, etc. will have a different method for resetting the SMC.
All in all, it’s disappointing that Apple overlooked this issue. Seems too often that companies can be aware of an issue be keep it quiet for the majority of users that don’t use (in this case) bluetooth, while those that due have to spend have their day in frustration.
Dear Apple,
Don’t pull Quit pulling a Microsoft.
Your Friend,
Mr. Customer
I just bought my first vinyl produced by Rhymesayers Entertainment of Minneapolis: US by Brother Ali.
Brother Ali, US
Upon opening the album I found a business card with a code to download the MP3 version of the album off of the Rhymesayers website. Awesome. I’m not sure if this if a regular practice of newer albums or not, but this is the way it should be. Pay for a hard copy and still get a digital version. The best of both worlds. Again, simply awesome. Thank you Rhymesayers and Brother Ali. Y’all Rock.