curbthepain
Well-Known Member
Does anyone want me to dedicate the next year of my development to a Rom made purely for performance?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
sure why not
Which is?I just want someone to solve the storage issue on 4.4.4.
I just want someone to solve the storage issue on 4.4.4.
any 4.2.2/4.3 port would make me a happy camper
and the graphics driver
Which is?
any 4.2.2/4.3 port would make me a happy camper
As close as we are to getting 4.4 stable wouldn't 4.3 or lower be stepping backwards? Chances are there'd be the same bugs (camera specifically) wouldn't it be more effective if everyone who has the coding and trouble shooting skills to aid in bug squashing on the 4.4.X source? Just a thought.
The key words are "getting close" for 4.4. Since AOKP 4.2.2 has been out for quite a while, it has (hopefully) matured and has most of the major issues already worked out. If we define performance as speed, stability and battery life, then AOKP meets all of those criteria. While KK is awesome, it still requires quite a few resources (battery, processor, etc) while the bugs are being hammered out. Also, the specs on this phone are good (not great) and one can reasonably assume that it should run 4.2.2 much better than 4.4.
Just thinking out loud - hope no one is offended. Everyone's hard work is truly appreciated in the community. At the end of the day, it's up to each of the devs (curbthepain in this case) to decide what itch they want to scratch
Not offended at all...however you have to understand that camera(for example) drivers and libs and hals and so forth are device specific... Keep in mind just because the issues were addressed in the AOKP source for "supported" devices doesn't hold true for unofficial builds. So again the developers would be faced with bug squashing on an android version that is obsolete and also keep in mind that 3rd party app developers will be moving forward using newer APIs and that backwards compatibility is becoming a thing of the past. Especially with L on the horizon...
However KitKat actually was designed by Google to run on 512mb ram phones and up and was/is meant to reduce android version fragmentation across the spectrum of devices. It actually uses less resources than JB and is compatible with more devices than any other previous android version.