OK, my first "production" use of the phone and it worked outstanding! I watched the last couple of Futuramas (from HD, HB'ed to 800x480), looked and sounded great! I also had Up! and Ninja Assassin from HD sources ready too I relaxed to some Radiohead (also from the phone) for the last 30 minutes [of the flight] or so. It was a perfect entertainment device for the place I used Flight View and built a trip with my flight up and back. VERY cool app, with flight times, mapping, all sorts of super helpful flying tools. I had also installed DC Metro which is a schedule checker, train/line planner for getting around on the Metro. While I already know the trip in from Reagan pretty well, it was slick seeing the real time train arrival time. I handled a couple of emails on the train to clients too, made a few calls, etc., a couple of emails had attachments which the phone handled perfectly. I also used maps/nav to find the hotel and the new Google Places to locate a place to grab something to eat. I planned on using it as a WiFi tether via the Google app, but it wouldn't fire up, so I'm going to re-investigate that issue (it wound up not being needed this trip). The phone did doing a great job of end-to-end "business trip support", from mapping, scheduling, flight monitoring, email, phone, etc. So after I got back from DC (and I purposely held off doing anything radical before the trip) I decided to try the ext4 fix. Before I did it, I used ROM Manager to create a backup, though the current update.zip was actually the ext4 fix (I used the ext4-root version). I ran the ext4-update.zip via ROM manager (using the original filename), it ran, I rebooted, and it seemed to run just fine, but I didn't have the SL4A app. So I re-ran it via the regular recovery mode (Vol up+down+power) by renaming the file to update. This time the SL4A app showed up, and I selecting the ext4 script, it seemed to run, but apps starting crashing. I let it complete, and when I rebooted, EVERYTHING was FC'ing all over the place (some of the core apps did fire up, because I was getting email notifications). So... I downloaded the Odin 3 bundled with the stock firmware (original non-leaked, JF6), got the phone into download mode (not sure why this is so tough for some folks?), flashed a fresh, OEM ROM. The phone fired up, everything looked fine (though crap-tacularly stock ). So I connected the phone, accessed the SDCARD, and moved the backup-update.zip to the SDCard root, renamed it, went back to recovery, loaded the update, got the ROM Rec menu, selected Nandroid [restore], and 10 minutes later, I'm back to almost exactly where I was before the ext4 attempt. Odin, ROM Man, etc., all worked AMAZING. Nice job to the various developers. The weirdness? The phone is SMOKING fast. No lag. Opening app grid? Super fast. Smart Shortcut? It used to have a big lag when opening it from the home screen. Now it's instant. Locked? No problem, instant unlock. It's almost like the ext4 fix took and the restore applied the backup to the faster filesystem[?] I haven't really sat down and thought about the logistics of everything that happened, but _something_ has greatly affected (for the better) the speed (and the lagginess). Could it be the cache was flushed by flashing a new stock ROM and restoring? The only thing that's a touch funky is via AppBrain a couple of apps are showing update available but result in a 'file not found', though that may be totally independent of my gyrations. I also can't push down app directly from AppBrain, it's just indicating the app on my phone expired, so I'm assuming some value stored in the system wasn't restored, so I'll just re-install it and see if that fixes it up. Whew! tl;dr version: Went to DC, phone worked great. Lag fixed, it "blowed up real good". Reflash stock ROM, restored backup. Phone is now super fast.