I spidered my D2 a handful of weeks ago. The replacement phone I received shipped with Gingerbread…which with my previous version of CyanogenMod was built on top of. I rooted the new device immediately, and dumped all of the garbage apps. My thought was to keep the stock ROM on the device, in order to have a stock testing device once I moved on to a new device.
Well, even stock Gingerbread is borderline useless by comparison. The most annoying tic that developed was with the camera…the flash stopped syncing with the camera shutter, rendering the flash useless.
Change of plans…dev device will run CyanogenMod 7.1.
landscaping?
I falsely assumed that flashing a ROM would work the same on Gingerbread as it did on Froyo for the Droid 2. Way wrong…I honestly thought I had bricked the phone. I ended up having to get creative with ADB and flashing an older firmware version, and standing Froyo back up on my device. From that point, it was the same old song and dance…testing ROMs, pulling batteries, hanging out on the recovery screen.
I wound up settling on an old nightly build of CG7.1. I am due for a phone upgrade right now…my wait for ICS is way more tolerable with a usable phone.
The project is wrapped. I have fully shown servo control via bluetooth, via Android, via IOIO. +3 via
no hands
The easiest way to test this, by far, is to snag the app on the Android Market. Here:
market-y
This does require a newer version of the IOIO bootloader than is currently shipping from units at Sparkfun, but details can be tracked down at this Google Groups area on how to update. It will work standardly, with a USB cable.
I haven’t included the IOIO libraries, but that will be part of the Eclipse setup if you decide to start hammering out some code. I can provide some guidance if anyone is in need of any.
Take a look. I bumped the SDK minimum again, in order to ensure that this function is intact. If this causes any hardship, I can relax the requirement.
Anyhow, take a look at the app in action in the previous post. Cheers.
My relationship with Motorola’s firmware has ended. It was a good run…well, no. That is a lie. It was certainly better after rooting my Droid 2 and wiping out Verizon’s boatware, but the Moto* junk had to go too. I finally decided to gut everything and install Cyanogenmod yesterday.
It is plus one awesome.
Although the process of flashing Cyanogenmod’s firmare involves a little work, it is no more difficult than rooting the phone in the first place. Since I did that a while ago, I really wasn’t concerned with blowing up my warranty…I figured bricking the thing would either result in some sweet haxxing or a new phone. Win / win.
I would suggest an upgrade to anyone. My phone finally screams, as it should have from day one. My battery life is better | everything imaginable is configurable | my apps and Google accounts all work | and, wait for it, I don’t have to kill processes all day. In fact, I don’t have a stand-alone task killer going…that is pretty surreal still.
Well, as with any exercise of this nature, backing up is imperative. Astro File Manager is great…Titanium Backup is great. The other players are the same too…ClockworkMod Recovery makes snagging the MODs easy. I am actually running a daily build, since there is not an official stable build for the Droid 2 yet. No memory leaks though, and everything so far has been functional.
Anyhow, on to the actual firmware stuff. I downloaded the zip file, and booted into recovery mode…
lousy picture is lousy
…during game one of the World Series. Not sure if that is Pujols or Furcal in the reflection. Either way.
Great picture, huh? This is the first time I have used my webcam since upgrading to Ubuntu 9.11. Whoops…screwed up the camera, fellas.
On the screen is a ClockworkMod selection for Google’s bits. I imagine that this was done for legal reasons. Anyhow, I had to go back and install this from recovery, as I missed it at first.
Katie's guest cameo
Hi Katie. ^
I also managed to get stuck in a boot loop of sorts during my first attempt. It turns out that I cleared the data but not the cache from the recovery menu. No good. A pulled battery and some troubleshooting and we were good to go.
post boot loop
I spun up the Android market, and did fresh installs of my apps. For the important stuff (the Angry Birds Trilogy, 9 Innings Pro Baseball, et. al.) I pulled the backup data back over top of things. No issues.
I had been wanting a landscaped workspace since I got my phone. .. now I know why… at long last
It just makes sense. CM7 allows this to be configured. Like basically everything else. Want your menu on the bottom? Put it there. There are options all over the map…like the camera exposure, for instance.
choice laden
Sweet. It is tough to beat the performance gains in general, but it is wholly possible. Check this out:
here be dragons
One stop overclocking. Disregard that popup and go nuts.
One part of me wishes that mobile carriers would take note of Cyanogenmod’s presence and push Android updates to customers. The other part of me likes to void warranties and do things that the clowns from Verizon frown upon. Either way, my phone is now awesome…that is all that matters.