How To: Fastboot or ADB on Ubuntu returning no devices or “Waiting for Device”? Here’s how to fix it.

I was having some issues getting my devices recognized in fastboot/adb on Ubuntu.

“fastboot devices” just returned back to the terminal prompt, without showing any connected devices, so I tried using the -i option to specify a usb vendor ID, like “fastboot-linux -i 0x413c reboot”. This just hung on “waiting for device”. I kinda ignored it, since I actually use my mac for most fastboot/adb, but tonight I was bored and fucking off on the CyanogenMod forums shoutbox, and someone was having the same problem. I did a bit of googling and found a solution that worked for me (and M.P.)

As usual, I’m not responsible for fucking your phone up or accidentally dividing by zero or going back to the future or hacking the gibson or anything else that happens. I’m not an expert. I wouldn’t listen to me, I’m kinda an asshole, I have no idea what I’m talking about, I’m usually just guessing. Proceed at your own peril, etc, etc, etc.

Here’s the step by step fix, assuming you’re running ubuntu 10.04:

1. Open a terminal window.

2. Log in as root.

sudo -i

3. Create a UDEV rule file.

cat > /etc/udev/rules.d/51-android.rules

This should give you a blinking cursor at the very beginning of a blank line, it’s waiting for you to tell it what the file needs to contain.

4. Enter this AFTER YOU REPLACE “XXXX” WITH YOUR VENDORID:

SUBSYSTEM=="usb", SYSFS{idVendor}=="XXXX", MODE="0666"

(You can find your vendor ID on this page.
For example, for my Dell Streak, I would use:

SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666")

5. Press CTRL + D to save, it should return you to the terminal prompt

6. chmod the new file

chmod a+r /etc/udev/rules.d/51-android.rules

7. Try fastboot. It should work now.

fastboot devices

Hopefully you get “Attached devices” with your devices serial number, if so, you’re good to go, fastboot should no longer hang at “waiting for device”. To be sure, try

fastboot reboot

If your device reboots, you win life.

Hey Dell, where the hell is the Streak Kernel source?

This isn’t a windows device, it’s open source, come off the Kernel Source, chickenfuckers!

Does your HTC Desire/Nexus One have an AMOLED screen or a Super LCD screen? Here’s how to tell the difference.

After a few hours of pulling my hair out digging around in the system files in an attempt to find a way to determine if someone’s HTC Desire has an AMOLED screen or a Super LCD screen, I realized there was a much easier way to tell the difference.

An AMOLED screen doesn’t actually display the color black at all, it simply turns off any pixel that is supposed to be pure black.

An LCD screen, on the other hand, does actively render the color black.

As such, an AMOLED screen displaying a black pixel looks exactly the same as an AMOLED screen that’s “turned off”, while an LCD screen looks decidedly different.

So, if you open photoshop/paint/whatever, and make an image that’s totally black, (hex code #000000), or just use this one I’ve so helpfully provided, it will look a lot different on an AMOLED screen than it does on an LCD.

This is black.

This is that very same image displayed on a Nexus One, with an AMOLED screen (left) and a Dell Streak, with an LCD screen (right), in the dark.

And both off, in darkness.

Note the AMOLED Nexus One looks the same, where it’s obvious when the Streak’s screen is on.

Now in normal light. Both powered on. Nexus One on the left, Streak on the right.

And again powered off.

Again, you can clearly tell when the Streak’s LCD screen is powered on, but the Nexus One’s AMOLED screen looks the same. This should be a pretty easy indicator as to which screen you have.

CyanogenMod 6 RC1 for Nexus One is out. Edit – Includes all red screen battery saver mode!

And the new Homescreen Tips are awesome :D

Find it HERE.

Edit – Just noticed this in CyanogenMod Settings, there’s a “Render Effect” setting that allows you to do this to greatly increase battery life:

As detailed on Engadget in THIS ARTICLE.

Obviously not something you would leave on all the time, but if you’re away from a charger (and won’t be near one for a few hours), and you’re down to 30%, it could be a real life saver. Great stuff from CyanogenMod as usual.

Edit 2 – Just tested the battery saver red screen mode. I just enabled screebl to keep the screen on, propped the phone up on my laptop, and swiped down, then up to unhide, then hide the notification bar every 5 minutes to keep screebl’s fail safe from turning the screen off.

I charged my phone fully, then started the test, and the stopwatch, and stopped when the battery level reached 90%.

In full color mode:

I then hooked my phone to the charger and fully charged again. I put it in red screen mode, unplugged it, and started the clock again, also hiding/unhiding the bar every 5 minutes.

I’m sold. I’ll keep it in mind when I need to stretch my battery life.

Flash 10.1 Beta for Android – Signup Open

Sign up HERE and you’ll get an email when you can download the beta release of flash 10.1 for Android.

Google Nexus One Documents Leaked, Pricing Revealed

First, here’s the Engadget Article.

From Engadget:

• Yeah, it’s $530 unsubsidized. Google’s not going to be selling the phone at cost, like so many people considered. They’re not going to save us from the “making money off of hardware” culture we’ve got right now, so this is basically just another Android handset, albeit a really good one
• If you want it subsidized, you’ll have to sign up for a 2 year mandatory contract and pay $180 for the phone
• There’s only one rate plan: $39.99 Even More + Text + Web for $79.99 total
• Existing customers cannot keep their plan if they want a subsidized phone; they have to change to the one plan, and this only applies to accounts with one single line
• If that doesn’t fly with you, you have to buy the $530 unlocked version—this actually might save you money over two years if you already have a cheap plan
• Family plans, Flexpay, SmartAccess and KidConnect subscribers must buy the phone unlocked and unsubsidized for $530
• You can only buy five Nexus One phones per Google account
• There is language in the agreement of shipping outside the US
• Google will sell it at google.com/phone, which explains what they were doing with that page a few weeks ago
• Google will still call it the Nexus One apparently, and not the Google Phone

And here is a big one:
• If you cancel your plan before 120 days, you have to pay the subsidy difference between what you paid and the unsubsidized price, so $350 in this case. Or you can return the phone to Google. You also authorize them to charge this directly to your credit card.

I gotta say, I’m disappointed. And I’ll admit off the top to that position being unfair. In all fairness, remove all the hype and hold this phone to the standard others are held to and it’s pretty good. If the current best guess at the specs are accurate, it’s a pretty impressive phone. The problem is, I expected more from Google.

Since the rumblings started about a google phone, people were speculating about it being sold direct through google at or below cost, especially with the activity at google.com/phone. Hopes were high that Google would make good on it’s overarching message of openness espoused since Android was in the early stages of development. Hopes were high that they would roll out a real iPhone competitor, devoid of the almost schizophrenic control Apple is known to hold over the iPhone. A phone that, at the very least, had full functionality on the two US GSM Carriers, T-Mobile and AT&T.

Turns out this isn’t the case. The Nexus One will technically work on both AT&T and T-Mobile, but due to a difference in the frequency used on their respective 3G Networks, it will only have 3G speed on T-Mobile. Meaning you’ll be limited to EDGE on ATT. For an entry level handset, this isn’t a big deal. For a full featured media phone like the Nexus One, iPhone, etc. It’s a deal breaker. Let’s do a test on my iPhone 3G.

First on 3G. 1.86Mbps down, 0.21Mbps up

Now on EDGE. 0.03Mbps down and 0.10 Mbps up.

Needless to say, the real world speed difference is astounding. On 3G, it basically loads pages as fast as the phone can render them, and file downloads are generally limited to the server’s speed. It’s comparable to your average DSL connection. On EDGE, you’re basically going back to 56k speeds, if that. This is pretty much a deal breaker for those of us not willing to break a contract and go with T-Mobile, assuming they even have 3G coverage in your area (And odds are they don’t).

From T-Mobile’s site:

As you can see, their 3G coverage leaves a lot to be desired. While AT&T has been chastised for lacking in 3G coverage, even they blow T-Mobile away.

That pretty much immediately removes it from the running for my sole mobile device, but had they done something like the speculation that they would sell it at or below cost directly, subsidizing the cost via advertising in the built in browser/email app, or some similarly innovative business model, I could have easily justified paying $200-300 for a device that works very well most of the time, and keeping my iPhone 3G in my bag for travel, tethering, etc. At $530, that’s not an option.

I’m guessing, and it’s just that, a guess, that the decision to use a radio compatible with T-Mobile’s 3G network was made to avoid a perceived snub, as they worked with T-Mobile for the original Android Device, the T-Mobile G1 , but I feel they’re limiting themselves in an attempt to maintain a good relationship with T-Mobile. The obvious aim of the device is to take some market share from the wildly successful iPhone line, but the problem is that the vast majority of iPhone users are on AT&T’s network and under contract. While AT&T’s network is far from perfect, it’s still better than T-Mobile’s, as evidenced above. Not many iPhone users are going to be willing to jump ship to another carrier, especially one with worse coverage, and especially given the cost of breaking a contract, around $200, last I checked.

Hopefully an AT&T 3G compatible iteration arises soon, and hopefully their press conference on the 5th still has surprises in store. Maybe they have something big up their sleeves, and I will be forced to eat my words, but as it stands, I feel they’ve failed to deliver on their promise to revolutionize wireless devices. The Nexus One and associated business model, at least based on the information available as I write this, is evolutionary at best.