Hello,
I got my evo 4g broken, then buy a ZTE Warp.
I am missing my Cyanogen rom.
Any chance Cyanogen include ZTE Warp ?
I had my ZTE Warp rooted by
http://androidforums.com/zte-warp/
then I installed Titanium Backup and restored all apps I had on my evo 4g.
So, ZTE Warp users have root and apps but no custom roms and recoveries yet.
Some devs are working in a recovery and is almost done:
http://androidforums.com/warp-all-things-root/455592-testers-wanted.html
Thanks
That's not quite how it usually works. You see the CyanogenMod developers probably don't own a ZTE Warp & they are all busy with their own devices.
If you have any decent developers with one of these devices then it shouldn't be a hard job for them to make an unofficial CyanogenMod port. Most ZTE phones share similarities, so the ZTE Blade port might be a good starting point. If they get that port working well, up to a standard that is acceptable to Cyanogen, then it may get accepted as an official CyanogenMod device & they could maintain CyanogenMod for that device.
Just rooted and CWM with one click on warp after update with Ultimate Warp Drive. Saw some custom roms on same page... ics, cm9 in android forums...
bpwent said:
Just rooted and CWM with one click on warp after update with Ultimate Warp Drive. Saw some custom roms on same page... ics, cm9 in android forums...
Click to expand...
Click to collapse
search for different forums there might be any unofficial port for ZTE warp.
BEST OF LUCK!!!!
The devs are doing their best to port cm9 but are having ril issues... there are alot roms out now.... I myself have made one and there are many others
Sent from my N860 using XDA
Related
I'm just curious what's usually involved. I know cyanogen mod does some custom things but ignoring those customizations, what is involved exactly in porting it to a device?
I would assume the major hurdle is driver support. As in the linux kernel compiled/used has hardware support for device x. But other than that, what else?
For ex, with the nook color, what is needed to port it? We can't expect a recent kernel for the nook color from barnes and nobles, but what about the existing kernel used in cm7?
Or if it's not just a kernel issue what are the issues/hurdles. I'm not a developer but just curious from a layman's point of view.
I would think if a working kernel is ready, wouldn't it be just a matter of compiling? I guess I'm curious as to why some say it takes a month or so.
First we need an upgraded kernel to even think about ICS. Then there will also need to be drivers written/rewritten for hardware acceleration and such. Also many other things that will need to be put together to compile even a semi-working rom.
---------------------------------
Sent from my LG Optimus V using Tapatalk
I hope by Xmas, CM team will prevail new ROM running ICS.
I don't care it called CM8 or CM9, as long as it's ICS supporting NC, I'm happy
Slight thread-jacking here, but somewhat related:
Kernel wise, what's the difference between an SDK port vs an AOSP port?
dormido said:
Slight thread-jacking here, but somewhat related:
Kernel wise, what's the difference between an SDK port vs an AOSP port?
Click to expand...
Click to collapse
The SDK is used by devs to create apps so only code relevant to having a semi- working simulator is present. AOSP is the full source code, witch includes everything but it is only built for one device, the galaxy nexus, so there is still much work involved in porting.
---------------------------------
Sent from my LG Optimus V using Tapatalk
There is samsung's ics for galaxy s 2, so is it possible to port it to sgs?
http://www.sammobile.com/2011/12/14/exclsuive-android-4-0-1-by-samsung-for-sgs2-custom/
There are only few features what can be ported to i9000 cause of reallly diffrent pcb used in sgsII.. more realiable is using sources from nexus S when they will be avaible... also if samsung is working on ics for sgsII they can use their resources to made rom for i9000 preaty fast.. and here is one more thing samsung not forgot about us cause of relasing few new roms in past month even yesterday xD
Ok, thanks for your answer. Let's hope that nexus s ics sources comes out soon.
We have ufficial ics from samsung
Sent from my GT-I9000 using XDA App
there are already very good ports by team hack sung, why bother with those other ones?
Nexus S also as not received the official ICS yet, their ICS ports are weaker than the i9000 ICS ports
quite offtopic answer but team hack sung could make their build more modern.. that means go step further and dont using old kernel resources 2.6.35/7 and go direct to kernels 3.0.8... (they need to port drivers to new api anyway) only nikademus pawtip onecosmic AFAIK(I'm new here in i9000) trying to do sth with it... but i know that kerels 3.0.x works with less laginnes after some time,, its may be cause of many junks and workarounds in obsolete 2.x.x kernels.... thats my point
Yeah as said the ICS builds posted in the Android Development forum would be much better than bloated touchwiz ICS. If you have problems with bugs it's best to be patient until they are fixed.
Being a total Android n00b, I just finished converting my SE X10 mini pro from stock to MiniCM-2.1.9+ nAa-11 kernel, and now I want to go on taking care of my ZTE Blade, but as far as I have seen by now, development for the ZTE Blade is quite different.
The official stable CM7 seems to be stuck at 7.1.0 since autumn, somewhere it was mentioned that nightlies have been discontinued, I could not find any info on kernel development, and progress only goes on with builds called KANGs?
Has official CM7 development shifted to CM9 only?
Can someone explain please, what KANG means?
Which CM 7.2 KANG is the current recommendation (I read about targetBSP, BurgerZ, burstlam and sej7278) and what are the differences?
You can say these as unofficial nightlies built by other people with their own small modifications but with all the official CM updates.
The names you mentioned are the one who built them
The one that i found fastest was the burstlam build but they're all pretty similar....except..targetbsp's version is more like a vanilla version meaning using all official cm updates only no extra mods etc. s
CM7 is still being developed, the only thing that stopped were the nightly builds, think it was hd failure on the server or something. CyanogenMod recently took donations for new servers, so they should be back up & running soon.
KANGs are just versions built from CM7 source, but not by CyanogenMod. There isn't much real development going on with them. They're just more recent because the CM7 nightly builds stopped months ago.
wbaw said:
CM7 is still being developed, the only thing that stopped were the nightly builds, think it was hd failure on the server or something. CyanogenMod recently took donations for new servers, so they should be back up & running soon.
KANGs are just versions built from CM7 source, but not by CyanogenMod. There isn't much real development going on with them. They're just more recent because the CM7 nightly builds stopped months ago.
Click to expand...
Click to collapse
great information included in this post had no idea that the cyanogen servers had some problems thanks for the information mate
Master One said:
Being a total Android n00b, I just finished converting my SE X10 mini pro from stock to MiniCM-2.1.9+ nAa-11 kernel, and now I want to go on taking care of my ZTE Blade, but as far as I have seen by now, development for the ZTE Blade is quite different.
The official stable CM7 seems to be stuck at 7.1.0 since autumn, somewhere it was mentioned that nightlies have been discontinued, I could not find any info on kernel development, and progress only goes on with builds called KANGs?
Has official CM7 development shifted to CM9 only?
Can someone explain please, what KANG means?
Which CM 7.2 KANG is the current recommendation (I read about targetBSP, BurgerZ, burstlam and sej7278) and what are the differences?
Click to expand...
Click to collapse
Go for Burstlam's build. Has good options for UI customisation and also has lesser battery consumption.
Sent from my Blade using XDA app
Hello Guys,
Just wondering if CM9 for ZTE Blade released? or under development?
As Qualcomm has made a driver for Adreno 2xx
Numerous Zte blade and Dell XCD users still waiting for the official CM9.
Any update regarding this will be really appreciated.
jishneo said:
Hello Guys,
Just wondering if CM9 for ZTE Blade released? or under development?
As Qualcomm has made a driver for Adreno 2xx
Numerous Zte blade and Dell XCD users still waiting for the official CM9.
Any update regarding this will be really appreciated.
Click to expand...
Click to collapse
I think u must go through the development forum carefully
im not sure about an official cm9 release directly from cyanogen since problems may still occur in development but i am sure that one of our developers will make this happen for our blades mate.
saaransh9 has a great thread open about android 4.0.0+ going on i would advise you to read the thread since a lot of information can be found there
As suggested by Kannibalism, have a look at the thread by saraansh9 regarding CM9...
Some features like Camera, video recording and some other stuff are still under development...
The basic version is out...Still won't recommend for daily use...
But, its smother than CM7....
stev007 said:
As suggested by Kannibalism, have a look at the thread by saraansh9 regarding CM9...
Some features like Camera, video recording and some other stuff are still under development...
The basic version is out...Still won't recommend for daily use...
But, its smother than CM7....
Click to expand...
Click to collapse
camera is working
saaransh9 said:
camera is working
Click to expand...
Click to collapse
Mahn...!! Thats good news...
But still waiting for fully functional CM9...
since the drivers for armv6 have been released i am sure we will be seeing better builds in the near future mate
Do you guys think cyanogen will eventually add this phone to its official supported devices?
Coming from a Nexus 5 with endless rom development It'd be a shame if this phone didn't see as much. Especially since it has such potential
No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!
kishan12345 said:
No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!
Click to expand...
Click to collapse
yes cm13 will be officially available soon!And you are wrong ! one plus had a bad breakup with cyanogen but theirs a diiference between how people work on cynogenos and cyanogenmod !It depends on the devolepers of each community on how they work on devolepment on a particular device but one plus two devolepment is insane so cm13 is on the way and if u are still concerned look at the devs of HTC 826 they made thier device get official support and dont worry as far as i know the devolpement for this device will be booming shortly !And theirs already a thread on CM 13 !
Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk
kishan12345 said:
Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
lol bro if they get unofficial builds perhaps in a week ..then tell ME why wont they make it official after a month !what one plus one had is the cyanogen os and not cyanogenmod !To make a device official in cyanogenmod u have to have good devolpment for a particular device and the works for cm13 is already started for op2 !Check out cm12.1 thread garak is working on cm13 and threres another thread called cm13
As i understand, in order to get an official support from cyanogen to our device there must be unofficial CM build, witch can be sent to CM team for a review. If it passes, has most things working, then they add it to their device tree and officially supports it. In other words, anyone there can take CM vendor and framework codebase and then go and start adding the code necessary to make CM work properly on OPT device. When developer gets far enough along, he can then submit that code back to CM for inclusion into CM's github. If that code passes the checks that the CM team has, then the CM team will merge that code into its own device tree and add official support for that device.
Also there are chance of CM team taking this step by their selves .. but there is probably no hope for that. So the only hope is Grarak
This information is found in the official CM forum so i doubt it is false.