Alcatel's Cyanogen-running Hero 2+ phablet has officially been scrapped

Alcatel's Cyanogen-running Hero 2+ phablet has officially been scrapped
With no clear path to Android 5.1 Lollipop, Alcatel and Cyanogen have decided to shelve the promising Hero 2+ phablet. First unveiled back at Mobile World Congress, the Hero 2+ was touted as a branch of the OneTouch Hero 2, running the Cyanogen OS atop Android KitKat 4.4.4. But with the industry now moving in the direction of Android Lollipop and looking ahead to Android M, the delay of the Hero 2+ has reached the point where both Alcatel OneTouch and Cyanogen have decided to scrap it. 

A joint statement from Alcatel's Steve Cistulli and Cyanogen's Vikram Natarajan suggests that while the Hero 2+ is not going to reach fruiton, this isn't the end of the relationship between the two firms, and that we can expect more great hardware collaborations in the future: 

The fact that both companies remain focused on delivering new products down the line is definitely encouraging, despite the lack of a release that had bags of potential. At $299, it may have been a hit with fans of the popular Cyanogen OS, but after such a lengthy delay, it wasn't to be.

Still, if you're a fan of its design and features, the Alcatel OneTouch Hero 2 is still about, and as you'll see in our review, is bundled with plenty of goodies.



1. rd_nest

Posts: 1656; Member since: Jun 06, 2010

Hero 2+? When did Hero 1 or Hero 2 appear?

2. downphoenix

Posts: 3165; Member since: Jun 19, 2010

Maybe I don't understand how all this works, but why couldn't they just update it to Lollipop?

5. Doakie

Posts: 2478; Member since: May 06, 2009

It's not that simple. Cyanogen Inc sucks.

6. tokuzumi

Posts: 1957; Member since: Aug 27, 2009

While I'm not going to go as far as saying CM sucks, but they are now just like any other manufacturer skinned OS. They always waited for Android code to hit the AOSP, which we all accepted back in the pre-INC days. But now, they get the code, and have to put their changes into the code, test it, make changes, retest, etc. Before their decision to incorporate, if there were bugs, the dev community was stepping over themselves to offer logcat files, suggestions, etc. Now, most of this has been moved in house, which means it takes longer to post releases. I'm happy the CM team has found some decent success, but I don't see any real benefit for the consumer.

3. waddup121 unregistered

Hero 2+ by the power of infinity and BEYOND!

4. joey_sfb

Posts: 6794; Member since: Mar 29, 2012

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.