As there is no official support, just ports and remakes I would like to see if I can contribute to get official Defy+ support for CyanogenMod.
I know where to find the Defy+ source code, I have said device at hand and I can find out how to get the general CM source.
That said, some helpful advice on where to start and what to do would be welcome. I tried posting the questions in the CM forums but was advised to XDA.
Sent from my MB526 using XDA
Related
Please someone give me the url if cm7.
I am sixk n tired of searching and searching and searching.....but couldn't find it!!
From X10i+TEAM v3.1 using XDA premium
Keep searching.....
Seriously? It's in the X10 Android development section. It's the one made by FXP. J/FXP's rom will be the one that will be released in the CyanogenMod website. Apparently there are still bugs to iron out. You can help the cause by testing it out and reporting to J/FXP.
http://forum.xda-developers.com/showthread.php?t=911364
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
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
EDIT FROM Moscow Desire,
Pax is now retired from FSM Duties. :crying:
MD
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
Welcome great job thanks for being a mod;-)
Welcome~!
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Timelord83 said:
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Click to expand...
Click to collapse
Why not just go get it from rootzwiki if you want it so bad?
bfranklin1986 said:
Why not just go get it from rootzwiki if you want it so bad?
Click to expand...
Click to collapse
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Timelord83 said:
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Click to expand...
Click to collapse
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Just to clear this up, roms are under Apache v2 license (which doesn't require source release) kernels are under GPL which does require source release.
Sent from my R800x using Tapatalk 2
ezterry said:
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Click to expand...
Click to collapse
sadly i do but the thread i linked is albeit messy with side stuff i made the assumption it was mod locked. after talking with the other people i have foudn out that the OP requested it be locked. i went and got the rom from AOKP website and as far as i can tell is Thor free and i run clockwork recovery and V8 ICS bootloader.
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Uhm... Hi paxChristos! Welcome to our slightly disfunctional family! I hope that you have a great time.:silly:
Timelord83 said:
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Click to expand...
Click to collapse
As do we all (want larger choices in roms).
But there-in lies the issue. We have an AOKP rom that has been through many hands, and at times, had some suspicious coding involved. Including getting closed on more than 1 occassion due to shady practices and non-GPL kernels. Might have been 3 seperate roms for all we know.
To post the rom now, would probably piss off quite a few people if enough credits were not given, even if the kernel proved to be legit. And even then, you would have several people claiming the rom was theirs and they were the original authors. That's the nature of these "KANG" roms and "MIUI" roms.
Well, we have polluted PaxChristo's welcome thread enough for now. I suggest we give it a rest, and probably open a new thread in the General Forum. I'll DL and install it, and see what's up with it. Post some results later.
MD
good job
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
t my a500wondering where to post question about how to root my tab. Sadly it is running 3.2 honey and I am very confused as what to do to get it rooted. I am in southern Louisiana, maybe there are folks close to me that could help.
Thanks everyone don
Hey thanks for being a mod' it is a lot of work I know. Listen I am knew as I just go
hi
will wi-fi direct work on defy/defy+ ??
new defy xt are supporting it with stock GB itself..
Thanks for all the replies.
Please ask all questions in the Q&A section. Thread moved there.
Not implemented yet
Sent from my MB526 using xda premium
I know th thread is over two years old, but my question is the same. Is WiFi Direct already implemented in any of the available roms? I looked for it but the only one I found was CM10 by Quarx and after install I still cannot find any info about WiFi Direct on my phone.
Hey folks!
The guys over at CM have officially released CM10 for our device iyokan/MK16i.
I thought it would be good if we could keep all the discussion related to that in a single thread to keep it organized and available for readers.
Get it here:
CM 10 OFFICIAL NIGHTLY
pteek said:
Hey folks!
The guys over at CM have officially released CM10 for our device iyokan/MK16i.
I thought it would be good if we could keep all the discussion related to that in a single thread to keep it organized and available for readers.
Get it here:
CM 10 OFFICIAL NIGHTLY
Click to expand...
Click to collapse
I have been using cm-10-20121218-NIGHTLY-iyokan.zip and all the upper versions except the latest 20121221 and 20121222... They were stable and great for daily use but it had a lot of bugs... and they have been releasing a new rom everyday since then so i thought I might for a while until we actually get a stable one...
There were no major bugs... just small ones... like low in-call volume and stuff which is probably fixed in the latest version...
Do we have a list of what's not working and other known issues?
I might give it a try over the weekend.
Sent from my MK16i using xda app-developers app
Read the first reply above your post. I might make a list after few people report what is working and what is not.
pteek said:
The guys over at CM have officially released CM10 for our device iyokan/MK16i.
Click to expand...
Click to collapse
How is this work related to the work done by team FXP (discussed at this thread)? Is this the same build?
Or is it different?
I thought FXP was the official maintainer of CM for these devices; why is there on official, non-FXP build @ CM,
and a different, FXP build elsewhere?
Could someone please explain?
Thank you:
I guess M66B answered it in the PRO CM10 thread. It is work of the FXP team.