Now that LG has corrected its source code, I’ve built my overclocked Android kernel for the Virgin Mobile Optimus V, a phone that’s nearly identical to my Sprint Optimus S and that also runs on Sprint’s 3G CDMA network. If your V needs a speed boost or extra driver support, keep reading! more …
Sweet victory! LG took quick action and wrote me yesterday to tell me they’d released an updated version of the source code for the Optimus V that fixes the bugs I identified over the weekend.
So, all is well in this small corner of the open-source world. I’ve downloaded the new source code (labeled “LGVM670(Thunder) Android Froyo/kernel bugs were fixed” on LG’s download site), and verified that the fixes were made and that the new code builds cleanly.
In case you’re interested in the differences between the Optimus S and Optimus V (LS670 and VM670, respectively), here’s a diff of the kernel sources that I’ve made.
I’ve discovered some bugs in the Linux kernel source code released by LG for the Virgin Mobile Optimus V, or VM670, a close CDMA twin to my Sprint Optimus S. It seems clear from the differences between the S and V source releases that LG has attempted to scrub code comments from the V source, but in the process they’ve created at least two syntax errors that break the code and cause it not to build.
They’ve also left out 15 files that are part of the Linux kernel’s netfilter and needed to build the kernel as configured by LG.
Update: LG has fixed the bugs, so keep reading only if you’re interested in the details.
I’ll detail the problems and explain how to (possibly) fix them below. However, the real issue is that the LG archive is broken as-is, so there’s no way it was used to build the actual Optimus V kernel. While I’m no GPL expert, it seems to me that LG is obligated to provide actual, working source code upon request, not an incomplete, broken fork. Let’s hope this was just an oversight, and one that LG will rectify. more …
Mozilla hit me with a double whammy of “your hardware sucks” last week, when they released major new versions of Firefox 4 and mobile Firefox 4 for Android (the first!) … but left me out of both parties.
My Android phone, the LG Optimus S, is only a few months old, but its ARMv6 processor isn’t supported. There’s a faint glimmer of hope there, but with the ARMv6 test builds already pulled, I’m not holding my breath. In the meantime, the stock Android browser and Opera Mobile are both great (Opera’s font rendering needs work in the hinting/character spacing department, but that’s it).
Meanwhile, my Powerbook G4 is still running happily along on OS X 10.4 Tiger, so I was happy to find the answer to my Firefox 4 woes in TenFourFox, a Firefox fork with builds optimized for various G5, G4 and G3 processors. Here’s a mini-review of my impressions after a week, and a look at what’s coming up in browser-land for those of us clinging proudly to the last generation of PowerPC Macintosh computers. more …