• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] What is taking AOKP so long to get it's 4.2 Sagger on?

I am a pretty devoted AOKP user. Outside of a few weeks of Jelly Belly waiting for 4.1 to come out I've always been AOKP. Just wondering why it always take a little longer for the swag to come out compared to other ROMS.

Any thoughts?


Because the battery is draining faster than it can be coded. I kid, but seriously. I just dumped Milestone 1 for XenonHD's RC2 (4.2.1). I'm getting incredible a battery life now. No more phone idle eating 80% of the battery that AOKP had.


If I were you, I'd try Xenon. It has pretty much every feature AOKP has. And flash Lean Kernel 4.2 while you're at it.
 
  • Like
Reactions: jond0ugh
Upvote 0
The Top Three Points Of Rom Developer Etiquette:

1.) Don't ask for ETA's.
2.) Don't post how cool one Rom is in another ROM's thread.
3.) Don't ever trash talk on a ROM development team.

Now, I hope this post is not perceived as snarky as it was not at all my intent; and if anyone took it as such, I apologize.

Seriously, some dev's take longer to perfect their ROM than others. I agree, AOKP has been a good product. But life happens. And as such, it might have more happening for some dev's than others.
 
Upvote 0
live in a cave? aokp's been in the crapper for a while now. most of their developers stopped developing. notice their new releases have been coming out seriously slow for a while?

Actually, there is a dev on rootzwiki who's syncing with AOKP's github and compiling nightly "unofficial" builds. I haven't flashed one but it sounds they're fairly stable.
 
Upvote 0
The developers of ROM's do not develop ROM's for us as part of a full time job; heck not even a part time job. They only do it as a hobby and the satisfaction they might derive from others using and then liking their product. When we totally unlocked the RAZR (V3c/m dumb phone),and then helped others do the same, we did it for the same reasons. A hobby.

With this in hand, when people drop off and stop, we don't bang the floor and demand more, we accept it. It could be that at some point the developer stopped getting the personal satisfaction and/or other more important things got in the way.

Look at when Gingerbread hit AOSP. There were a boat load of folks on Cyanogenmod, but development by the CM team just dropped off for the OG Droid. Could it have been because all the demands for progress? I don't know, but it did. Months later after the furor died down suddenly stable releases came out.

I could say more and could point out so many examples, but I'm getting off the soap box, since I don't want anyone to think I meant any offence in this post; I didn't.
 
Upvote 0
As a huge fan of AOKP and open source, one thing I think is awesome is that anyone can build AOKP from AOKP source code. To that end, in the AOKP Thread in this very Forum, one can find a 4.2 build by a fan/user who built AOKP from source. It is an excellent build and speaks to the core of what Android means to me. Where there is a will, there is a way. Because Android is open, we can appreciate the work of Roman et al and further development if it suits us.

Thanks to AOKP and all the Devs who make time to provide anything to the community.

My 2
 
  • Like
Reactions: teddyearp
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones