(Make sure to turn on Captions, the GoPro microphone is not the best)

Quick video demoing the details that make a difference of driving an electric car.

This post is the product of about 48 hours of not being able to work on what I was supposed to be working because I had to deal with build issues in Eclipse.

Hopefully If you follow these steps you will be able to solve some of the issues you may be facing right now with your build.

Some of these issues are:
- Class not found errors, even though your app was built and uploaded to your device.
- R.java not being compiled.
- *.aidl interfaces not generating .java files.

1. Make sure your project’s compiler is set (as of the current android release) to be Java 1.6 compliant.

If you work on several java projects outside of Android, you may probably need to work with Java 1.7 compiler specs and by mistake you may have set it as the default for all projects.

This may cause a lot of stuff to break on your Android projects, including the generation of .java files out of .aidl files.

Make sure your Android project is using Java 1.6 (which is sadly all of what Android supports as of this writing)

2. Make sure the .jars you want to export are CHECKED in your Java Build Path > Order and Export settings

After updating my Android SDK tools last friday, I wasted a whole day trying to figure out why on earth my application was giving me runtime Class Not Found errors on classes that exist inside android-support-v4.jar, even though I had all my jars placed on the proper standard “libs/” directory in my project.

The culprit was that the checkboxes along the .jars in my Order and Export tab were not checked.

3. Make sure your source folders are placed in the right order in your Java Build Path > Order and Export settings

That right order for me has been:
1. My source folders at the top.
2. The “gen” folder right after the source folders.
3. My jars and Android dependencies at the the bottom.
4. Make sure “Android Dependencies” and “Android Private Libraries” are all the way at the bottom. I found out having them before the .jars causes issues when you want to attach source code to your .jars, eclipse will try to browse the .class inside the “Android Private Libraries” which does not allow for source code attachments, therefore not letting you see the source code you’ve attached on the build settings.

3. Make sure the .jar dependencies you need are saved inside the libs/ folder in your project.

That’s all I have for you.
Clean and Rebuild.

Tesla designed a really cool fob “key” to control the car’s locks, trunk and “frunk”, it looks like a little toy car, but there’s a fundamental problem, it wasn’t designed to be part of a regular keychain, and if you’re not careful you might lose the key fob easily.

I hope you came across this post and you didn’t scratch your fob already, I suggest you get something like this and then attach that to your key chain, it only costs $6 and it’s quite convenient.

via evstories.com

I’m a software developer and this is everything I was carrying in my backpack today April 26th 2013 (from the top, left to right)

1. A case for SD cards.
2. Raspbery PI I’m toying with at the moment.
3. A roll of #punsr stickers
4. US Passport, you never know when you get a crazy invitation (or emergency) to fly out.
5. Emergency Icebreaker underwear, you never know if your luggage might get lost, you can at least take a shower and have a fresh pair.
6. Checkbooks, electronic bank keys.
7. Snes-like USB gamepad (for the Raspberry PI video game console project)
8. pens
9. Microsoft USB wired optic mouse, still my favorite, never worry about not having batteries for it.
10. Punsr business cards, Tech Consulting business cards.
11. Amazon Kindle Fire HD
12. iPad
13. Beats Pro headphones
14. toothpicks, so you never have to suffer with food between your teeth for hours.
15. coins (I try to not have coins, I keep them in the car for parking meters)
16. Nexus 4
17. Galaxy SII
18. USB power adapters
19. WD My Passport 2TB backup drive (I keep another at home attached to my monitor for automatic backups)
20. Macbook PRO Power adapter
21. European power converters
22. Ethernet cable for the raspberry pi and because you never know when you might need it.
23. prescription sunglasses, needed in sunny florida.
24. MacBook PRO 2.3 GHz Intel Core i7, 8 GB ram, 500GB SSD

I’ve just gotten started into BitCoin a little late in the game (April 2013) and if you’re reading this you’re probably on the same boat.

This post details the steps I took to start mining BitCoins with GPU on a MacBook Pro.

1. Get DiabloMiner. You will need to have installed git and a jdk (Java Development Kit) to build it.
Clone the source code from the github repository into your computer. From the command line

git clone https://github.com/Diablo-D3/DiabloMiner

after it downloads you will have to build it, invoke

cd DiabloMiner

mvn package

it will download all its dependencies and build itself.

2. Register into a Bitcoin Mining Pool

Now you will see a “DiabloMiner-OSX.sh” script. if you try to use it to mine in solo mode (connecting agaisnt localhost:8332), you will get errors, it seems nowadays there’s only pooled mining (i may be wrong), so you will have to register into a Bitcoin mining pool to make this happen.

I registered my account at deepbit.net, in there you get to enter your BitCoin address to receive your mining rewards.

3. Launch DiabloMiner (in as many machines as you can using your pool mining account)

./DiabloMiner-OSX.sh -u youremail@somedomain.com -p yourpasswordhere -o pit.deepbit.net -r 8332 -g 5 -w 64

and you should see…

[4/26/13 11:02:23 PM] Started
[4/26/13 11:02:23 PM] Connecting to: http://pit.deepbit.net:8332/
[4/26/13 11:02:24 PM] Using Apple OpenCL 1.2 (Dec 4 2012 18:26:30)
[4/26/13 11:02:24 PM] Added ATI Radeon HD 6750M (#1) (6 CU, local work size of 64)
mhash: 46.0/44.4 | accept: 0 | reject: 0 | hw error: 0

Hope this helped you.

(My previous post)

So now that we have a Raspberry PI we need an ARM based Operating system to go on it.

My original idea is to run Jelly Bean on it, but I couldn’t quickly find an image for the Raspberry PI (which means I’ll either have to find harder or I’m gonna have to bust my ass and build one myself and add all the drivers necessary so that it runs like charm)

At this point I just need to know that my hardware is good to go, so the quickest, easiest way to put an OS on the Raspberri PI that I found was to get a Debian based Linux on it called Raspbian “wheezy”.

You can download the .zip file that contains the image file via http or you can help seed a torrent of it after you get it.

Once you download that you will end up with a 493.6MB .zip file, unzip it, and you will see the 1.96GB 2013-02-09-wheezy-raspbian.img file.

Now you have to put that .img file inside the SD card that will go into the Raspberry PI.

I’ll teach you how to do that on a Mac (on a linux box is quite the same, the file and mount locations are probably the only thing that’ll change)

1. Stick the SD card on the SD slot of your macbook.
2. On the Finder, Eject the SD card as soon as it comes up.
3. Open a Terminal
4. Execute sudo diskutils list, you should see something *like* this (this is actually how it’ll look when you’re done)

$ sudo diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            499.4 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *2.0 TB     disk1
   1:                  Apple_HFS Time Machine            2.0 TB     disk1s1
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:                  Apple_HFS PICS_AND_MOVIES         999.9 GB   disk2s2
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *15.9 GB    disk4
   1:             Windows_FAT_32                         58.7 MB    disk4s1
   2:                      Linux                         1.9 GB     disk4s2

I want you to notice the “/dev/disk4“, judging by the size, that’s our 16 GB SD card right?

5. Now that we know where it is, let’s copy the image file into it. First make sure to unmount the partitions that are on the SD Card so you can write on it, for example, I have there a Windows_FAT_32 partition I don’t want to loose (disk4s1), you unmount it like this:

sudo diskutil unmount /dev/disk3s1

Then copy the image using the awesome dd utility, if the .img file was in your “Downloads” folder the command would look like this. (“if” stands for “input file”, make sure you put the full path to the file, or go to that folder and execute the command below)

sudo dd bs=1m if=~/Downloads/2013-02-09-wheezy-raspbian.img of=/dev/disk4

This will take a few minutes, be patient.

Once done, take the SD card, put it in the Raspberry PI SD Slot, hook it up to a monitor and power, snap a mouse and keyboard, and boot. It should work.

Download the APK or get it at Google Play

A new FrostWire for Android is here, this is a major update that you should not skip, specially if you’ve had issues in the past.

The biggest changes are:

Integration with Archive.org

Archive.org indexes free files from all over the internet, there’s a huge amount of Public Domain files and Creative Commons files, so keep an eye for those archive.org results if you’re looking to remix legally free available content, FrostWire will be a great tool to find it.

Archive.org also indexes torrents of these files, if you download and seed you will help make its contents more decentralized and durable, not to mention you will save archive.org some bandwidth.

The Archive holds over 7.3 million files, it’s a powerful content library that now is easily accesible from anywhere using FrostWire, we hope you find it very useful, for example, law students and attorneys can now use FrostWire to search for public transcript of court cases, among other documents. Almost every known public domain film, book, and audio recording is available and best of all we’ve integrated it with FrostWire after revamping our search architecture which now delivers results as soon as possible to your android device.

Search results coming from archive.org include basic information about the file’s license if available, make sure to check the licenses and to respect your local copyright laws, FrostWire condemns copyright infringement.

Faster Search, Reduction of CPU/Battery consumption

We’ve made search considerably faster, now results are shown as soon as they come in, in the past our algorithm would wait for a certain amount of results to come in and show them to you, the search experience should feel snappier now. Also we optimized and fixed our code and some third party libraries that weren’t meant to be used on Android so now the app consumes up to 84% less CPU which will result in your battery lasting a lot longer if you’re running FrostWire.

We’ve made a few improvements in the bittorrent core, namely the hashing algorithms are about 15% faster than before which also reduces battery consumption while downloading and checking torrent chunks.

More stable and compatible

Since our last release in november we received thousands of crash logs from users worldwide and we went through all of them fixing bug by bug, in the process we did a few updates on the user interface you will notice a nicer looking navigation menu, and more intuitive icons to share/unshare files on the Wi-Fi network.

Many fixes related to the audio player, specially an annoying double-playback bug lots of you reported, thank you.

Full Changelog

For those of you following the codebase and who know geek-speak

FrostWire 1.0.6 - APR/08/2013
 - Faster search results. Search architecture revised and improved.
 - Includes search results from archive.org, which indexes millions
   of public domain and creative commons works from all over the
   internet.
 - Reduces CPU and battery consumption up to 84%.
 - FrostWire won't disable screen locking during audio playback.
   It's now up to the user to set longer auto-locking timeouts if
   they want to use FrostWire as an audio player in their vehicles.
 - UI fix, media player screen is correctly updated if a song starts
   while the screen was locked.
 - Updated icons and graphics.
 - Improved mime type detection.
 - Supports WebM video search results.
 - Updated UPnP cling libraries for better Wi-Fi sharing discovery.
 - Multiple crashes and freezes fixed.
 - Opens .torrent files from urls and from any file browser.
 - Faster hashing and checking of ongoing and finished torrent downloads.
 - Fixes a crash when sharing files from third party apps like FileKicker
   which pass filepath uris instead of android provider uris.
 - Fixes double audio playback issue with third party media playing apps.
 - Fixes bug where the app would force close and restart on phones without SD cards.
 - Fixes bug on Android 4.x where finished document downloads wouldn't appear under
   documents.
 - Avoids crash caused by AdMobSDK and WebView's cache being null.
 - Fixes bug where sharing files from a third party app would open FrostWire
   in a way that hitting the back button would take the user to the desktop and
   not back into the third party app.
 - Replaced navigation menu for a better one that presents itself with a smooth
   brief zoom-in animation.
 - Navigation menu and transfer screen looks properly on Motorola Razor
 - More efficient use of Bitmaps should cut down on the number of Out of Memory errors on most devices.

On May 21st this year, 12 years after their incredibly successful “Discovery” release (and after doing Tron Legacy’s Soundtrack and the not so successful “Human After All” album), french Duo Daft Punk will release Random Access Memories in the US (comes out on the 17th in other countries) with some great collaborators that tell a little bit about the production process of this album.

Judging by this, there’s been a tremendous amount of work behind every track and they’ve gone for nothing but perfection, I’ll have my fingers crossed for a masterpiece classic release.

First Impressions
Feels good in my ears (I’m already used to in-ear buds, this ones have a nice vacuum when you slide them in)

Unlike my old sport Sennheiser headphones (which I love for running) the speakers are joined by a thick cable, not a thin cable enclosed by a plastic frame.

It took a couple of minutes but the drive “WALKMAN” was mounted automatically! Maybe it was the first time the device was started it may have needed to boot or it just didn’t have enough charge to mount itself, who knows. it’s mounted now, I’ll be uploading music to it with drag and drop next.

Controls

The controls are placed on the underside, buttons are nicely separated. You will have volume controls on your left ear, the same goes for one button to turn shuffle on or off. Controls are responsive, skipping is instant just like you’d expect.

On the right ear you will have skip and play/pause buttons. Some buttons trigger a female voice that tell you what you just did, that’s a nice touch.

I’d give the controls and overall design a 4/5.

Sound
If you’re used to Dre. Beats you will be disappointed, If however you use regular headsets sound quality is comparable to the sport Sennheisers, it seems like they will do the job well when you’re running.

You won’t be able to blast super hard with these headsets, and a downside is the sound bleed. People around you will hear your music, something that surprises me because they are in-ear, but now I’m starting to think that the in-ear part is only to avoid sweat from going into your ear canals when you’re running, it’s not related to sound quality.

I’d give them a 3.8/5 in sound, I guess if you’re not too demanding they’re fine.

I’ll be updating this post after I take them on a 3 mile run.

Specs
2GB storage.

1.5 hours to charge, up to 8 hour playback.

water resistant, perfect for sweaty runners like myself.

Verdict

They are well worth the $55, Get them on Amazon if you like them.

Disclosure: I didn’t buy the Sony Walkman, they’ve been given to me by Klout perks, probably with the intention of me reviewing these and generating buzz around the product. Still the targeting by Klout Perks was great, I’m a geek and a runner and I do need a product like this. I would’ve probably not bought it in the first place since I tend to do all my running work outs using my Android phone and several apps (FrostWire for the media player, Cardio Trainer for mile tracking)

I got everything on amazon, didn’t pay for shipping (Prime member):

So far I bought:
- Raspberry PI ($48)

- Raspberry PI case ($14)

- Power adapter ($2.25)

- SNES-like Controller with USB jack ($10.75)

- SanDisk SDHC 16GB class 6 (30mb/s) ($15)

I first intend to install Ubuntu ARM along with several video game console emulators for NES, SNES, SEGA, N64.

People at the Raspberry PI G+ Community have suggested instead to install arch linux and keep it light, I’ll go first for ubuntu since I know it well.

However I’m thinking that a more interesting option, given that it has an ARM processor is to install Android Jelly Bean on it and see if not only I can run game emulators on it, I’ll be running and testing FrostWire for Android on it.

Ever since I started developing FrostWire for Android I’ve thought that Android has everything in it to be a desktop operating system, maybe Raspberry PI’s will be the hardware I’ll use to prove my vision.

The idea is to end up with a nice tutorial on how to do this after I’m done so you can all do it. In the meantime I’ll keep posting updates.