In AnTuTu, I've gotten over 19000 a few times, but averaging between 17500 and 18500. Talk about miles above from stock. XD
wonder how does bionic patch and kitkat is going to raise the score ^-^, or even that extra 50MHz on that gpu
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.
In AnTuTu, I've gotten over 19000 a few times, but averaging between 17500 and 18500. Talk about miles above from stock. XD
DEFCONFIG MODEL DEVICE
msm8960-apollo N9101 ZTE Imperial
msm8960-becky Z995 ZTE Overture
msm8960-coeus Z930L
msm8960-demeter T83 ZTE Dave
msm8960-gaea ???? Unknown
msm8960-hera N9511 ZTE Source
msm8960-iris ZTE Grand S Flex
msm8960-metis Z740
msm8960-nestor ???? Unknown
msm8960-nex N800 Virgin Mobile Awe
msm8960-oceanus ZTE Blade Apex
msm8960-stormer N9520 ZTE Stormer
msm8960-warplte N9510 Boost Warp 4G
Released devices that have the MSM8930/MSM8630 chipset:
ZTE Imperial apollo (U.S. Cellular)
ZTE Overture becky (AIO Wireless)
ZTE Source hera (Cricket Mobile)
Virgin Mobile Awe nex (Virgin Mobile)
Boost Warp 4G warplte (Boost Mobile)
AT&T Z998 ???? (AT&T Go Phone)
Would you be able to get me the recovery image of both devices?actually as it turns out the upload wasnt working. so here i uploaded it to my dropbox
https://www.dropbox.com/s/xxy6gzkxngc6czg/warp_lte_and_source.zip
I say go for it. I know I'd much rather follow a video of somebody else doing it rather than have to follow a guide and hope I'm doing it right.
Oh yeah, did the CWM zip work for you?
Here is something to keep in mind as the kernel device tree is worked on. I was perusing the defconfigs, and all of the msm8960-codename_defconfig's stuck out (since the awe/nex falls into that group). I just spent some time figuring out what devices most of the other msm8960 codenames are attached to. Most of them are not released yet, some don't have names yet - only model numbers.
Here ya go:
Code:DEFCONFIG MODEL DEVICE msm8960-apollo N9101 ZTE Imperial msm8960-becky Z995 ZTE Overture msm8960-coeus Z930L msm8960-demeter T83 ZTE Dave msm8960-gaea ???? Unknown msm8960-hera N9511 ZTE Source msm8960-iris ZTE Grand S Flex msm8960-metis Z740 msm8960-nestor ???? Unknown msm8960-nex N800 Virgin Mobile Awe msm8960-oceanus ZTE Blade Apex msm8960-stormer N9520 ZTE Stormer msm8960-warplte N9510 Boost Warp 4G Released devices that have the MSM8930/MSM8630 chipset: ZTE Imperial apollo (U.S. Cellular) ZTE Overture becky (AIO Wireless) ZTE Source hera (Cricket Mobile) Virgin Mobile Awe nex (Virgin Mobile) Boost Warp 4G warplte (Boost Mobile) AT&T Z998 ???? (AT&T Go Phone)
I'm compiling 4..4.2 right now, it should boot after a few ramdisk mods. will post build for testing when completed.
no clue on msl codes, i dont use stuff like that but i think you can dump it from QPST
rom is STILL compiling...ugh
!! kitkattttHere is a working cyanogenmod build for the ZTE Warp of the same Android version.
CyanogenMod10 - 4.1.2
http://androidforums.com/boost-mobi...-cyanogenmod-10-jellybean-4-1-2-zte-warp.html
Here is a working cyanogenmod build for the ZTE Warp of the same Android version.
CyanogenMod10 - 4.1.2
http://androidforums.com/boost-mobi...-cyanogenmod-10-jellybean-4-1-2-zte-warp.html
that's no kitkat or art :'(
So this is for the warp? Or is it flashable to the awe? Im assuming not
Yeah its for the warp, wouldn't flash if you tried i'm sure.
If the right person played with that rom, they could bring it over.

do not flash that rom... its not for the warp 4g its for the original warp. if it did flash it would brick your phone permanently
oh and none of it is transferrable
I guess i'll be the first to tell you that kitkat would be the last rom to be brought to this phone.
kitkat was a world of work for the galaxy s4, took me forever to get a working build out and it had a lot of developers. the first logical step would be to port a Cyanogenmod with the same base android version as the rom we have. which is 4.1.2
Our matching version of cyanogenmod is the standard CM10.0
It would be the most painless, compatible way we could go.
It's either KitKat, or my phones going on a date with a baseball bat