I'm curious to see what percentage of our readers who run custom ROMs are using AOSP (Android Open Source Project - something pretty close to vanilla Android, such as CyanogenMod), and what percentage are using something based on stock device ROMs. More specifically, I want to find out if people on certain manufacturers are more likely to go AOSP than others - in other words, is Blur/NinjaBlur pushing more people to AOSP than TouchWiz, or is there no difference?
Hot on the heels of the report from the analytics firm Canalys, market research firm IDC has reaffirmed Apple as the largest smartphone manufacturer in the world. Unlike the findings from Canalys, which grouped smartphone OS platforms together irrespective of manufacturer, IDC's study has broken down shipment numbers in Q2 2011 according to device vendors. The findings (courtesy of Engadget) are as follows:
Smartphone shipments in Q2 2011 totalled 106.6 million, an increase of 42.2 million from last year.
Android updates are a bit of a tricky subject for all involved parties. Obviously consumers and Google are on the same page in that they want Android updates to roll out to individual devices as soon as possible. But for manufacturers and carriers, updates are costly to customize, quality test, and roll-out.
Manufacturer user interfaces (UIs) can be a bit of a hot-button topic in the Android world. Some prefer vanilla Android, à la CyanogenMod. Others have no issue with them whatsoever, and even actively seek to restore some of the functionality. (Others still prefer to roll their own, or like the ability to switch at will...
In light of this week's bootloader lockdown bonanza, it makes sense to ask something related. We know that as an Android-centric blog, our readers are likely to be a bit more hack-'n-mod oriented, so we're interested to see: who will manufacture your next device?
The "why" isn't crucial, though you're certainly encouraged to share your reasoning via the comments.
It appears Verizon has altered the terms of its "Certified Like New Program" ("CLNP") (pray they don't alter them further) to be a lot more demanding regarding the condition of exchanged devices.
Namely, if you send in your destroyed DROID, don't expect to get a shiny new replacement without a serious penalty - all phones sent in on warranty exchange must now meet the following requirements:
CLNR Cosmetics Standards
CLNR Cosmetic Standard Summary:
- No blemishes are permitted on front surfaces such as the touch screen, keyboard
- No more than two flaws, which must be less than 5mm in length, are permitted on other surfaces
- No flaws or defects on lens
- No dust, dirt, or fibers under lens
- Ports must be free of foreign material and corrosion, be in operating condition, and have the plugs in place if applicable
This means even if your Android device suffers from a warrantied defect and fails, you may be out of luck trying to get it exchanged if you haven't kept it in tip-top condition.
If you’ve cruised the blogosphere today, you’ve probably noticed a number of articles talking about the Digital Millennium Copyright Act (DMCA), and the Library of Congress having decided to add a few exemptions to the sweeping piece of legislation’s authority. Why is this a big deal? And is it a big deal at all?
On the latter, in some ways yes, and I’ll explain why only some later. For the former, it signifies a change in attitude over what constitutes infringement of digital copyright for two major pieces of technology, one of which we’re interested in here at Android Police (take a guess at what sort of technology that is).