It’s been two weeks since I first wrote about BlissPop, the first Lollipop-based custom Android ROM good enough for my OnePlus One. Now that I know my way around a bit better, I can tell you at length about why you might want to consider it for your device.
In case you were wondering, the clock and weather widget that you’re looking at is a Lollipop beta of DashClock, and the circular app icons are from the Flux CM12 Theme—I kept the icons and ditched everything else.
Let’s take a closer look!
For me BlissPop’s biggest and most unexpected perk is the built-in ad-blocker; just like AdAway, you can download a custom hosts file and never again see ads on your phone or tablet. It works so well, in fact, that I’m not currently running AdAway at all.
Fans of Greenify will be similarly served by a built-in wakelock detector and blocker, making installation of that app redundant as well.
Thanks to Cyanogen’s theme engine you can customize the look of your device however you see fit. Or you could just change your wallpaper to one of the options available in BlissPop’s online directory. The screen above is only an example; there are lots of really good wallpapers to choose from.
OnePlus One users are particularly well-served by BlissPop’s gesture support, pretty much identical to what you’d get with Cyanogen OS.
The ROM isn’t perfect, though. I’d be remiss if I didn’t let you know about two shortcomings that I’ve found so far…
BlissPop is what the XDA crowd would refer to as a “kang”—that is, a bunch of features from other ROMs “kanged” together. As a result, I found myself confused by the screen above. BlissPop is pre-rooted by default, so this root option in the developer settings is entirely unnecessary.
The only actual bug I’ve found with BlissPop is with the in-call proximity sensor, which doesn’t seem to work. When I made my first call the screen immediately went blank and then never woke up. I addressed the issue by turning off the sensor altogether—problem solved. I hate making voice calls anyway, so this wasn’t at all a deal-breaker for me.
Hopefully the flaw is only present in this particular build, and hopefully it will be fixed in a future update.