Related
or does anyone else feel like we dont have enough aosp love? I mean we have miui, cm7, had decks(went ghostbusters on us) and empiire(heard he got grounded for molesting his hard drive.) I understand theirs still kinks to be worked out but everything is Sense. Just wanted to see who else felt this way. PLEASE DONT COME IN AND START A PARAGRAPH WAR, I read enough in high school.
Temari x Shikamaru
Evervolv exists.
il Duce said:
Evervolv exists.
Click to expand...
Click to collapse
Link please. Ive been hunting it.
Temari x Shikamaru
Talked to shift on twitter yesterday, he said CM7 is being worked on. I honestly think what it is that people are happy with their phones just the way they are, so it brings less crowd. While it is smaller than the original Evo, there is still a pretty big following. Plus, this is just a US phone, so when comparing the Sensation with us is like apple and oranges. We just got mike and androidrevolution! Which is great.
Sent from my PG86100 using xda premium
PatrickHuey said:
Talked to shift on twitter yesterday, he said CM7 is being worked on. I honestly think what it is that people are happy with their phones just the way they are, so it brings less crowd. While it is smaller than the original Evo, there is still a pretty big following. Plus, this is just a US phone, so when comparing the Sensation with us is like apple and oranges. We just got mike and androidrevolution! Which is great.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Its not just US. Theres gsm models for overseas.
Temari x Shikamaru
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Can the gsm users get some aosp love? Any roms?
Sent from my Evo 3D GSM...bring on the AOSP!!!
housry23 said:
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Click to expand...
Click to collapse
This man is right. Most AOSP is done by Cyanogenmod devs and kanged from there. I can guarantee you when they come out with a CM7 RC, there will magically be other AOSP roms.
housry23 said:
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Click to expand...
Click to collapse
Your right. I forgot about that.
Temari x Shikamaru
housry23 said:
The problem is, most AOSP ROM's(99.99%) are based off CM kernel source, so with no update to CM, there's no update to other AOSP ROM's. Many devs might want to wait until a few more bugs are worked out of CM before they start kanging. Once we get an RC1 or a stable CM release, you may see more AOSP love.
Click to expand...
Click to collapse
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Sad Panda said:
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Click to expand...
Click to collapse
Damn. Such a long read. It was good though.
Temari x Shikamaru
knowledge561 said:
Damn. Such a long read. It was good though.
Temari x Shikamaru
Click to expand...
Click to collapse
I'm sorry, I originally had hoped for a much shorter post. I always try to get the thoughts in my head out "on paper" in the shortest, most efficient and least complex manner. This is my vision of a more free, "open source" world though. I think the freedom of information could be applied to many facets of society that would create a better future for all of us, and still preserve the competition that drives a more peaceful, better, cheaper, faster world. Sorry again!
Sad Panda said:
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Click to expand...
Click to collapse
The problem is that people don't always give credit where credit is due, which is one of the reasons some people don't like sharing stuff. I mean, let's say I made this awesome mod and let everybody use it. Then some kitchen dev comes along, kangs the **** out of it, doesn't mention me in his rom, and slaps a gigantic DONATE button at the bottom of his signature. It's frustrating.
Now I'm all about open source. I won't use a rom that doesn't post the source. That's the exact reason I won't use MIUI.
SolsticeZero said:
The problem is that people don't always give credit where credit is due, which is one of the reasons some people don't like sharing stuff. I mean, let's say I made this awesome mod and let everybody use it. Then some kitchen dev comes along, kangs the **** out of it, doesn't mention me in his rom, and slaps a gigantic DONATE button at the bottom of his signature. It's frustrating.
Now I'm all about open source. I won't use a rom that doesn't post the source. That's the exact reason I won't use MIUI.
Click to expand...
Click to collapse
I fully understand your frustration. I am a software engineer too so I know what you are going through. I have not yet begun developing for Android, but will. There is a little bit of a problem here that could easily be solved, and the community has a responsibility to protect the intellectual property rights that you and every other developer like you is entitled to. In fact it is a right that is protected by the integrity of the constitution of the united states, and many other countries and law enforcement around the world. This is a failure that not just developers, mods, and admins have, but a responsibility and failure that every user at xda shares no matter who they are.
First off; not to offend any MIUI developers that may be watching, but if you are developing for Android you need to be using a license that is open, and your source needs to be open too. This is especially true if you are using xda as a distribution medium, but sadly while xda has said they encourage, and want every development to be open source they are not forcing the matter. This is a failure I think. It also makes MIUI look suspicious too, as there isn't a way to verify if their source is uniquely theirs'. I personally believe xda should not allow software that is not open source to be distributed. If google didn't keep the open source principle when they acquired Android roms like MIUI would NOT exist! It is highly unethical to take the base ROM from google because it is open source, and then close the source. That is wrong wrong wrong! It is also illegal! You can not redistribute the Android OS even if you have made changes and then close the source and not maintain the software license google has on place.
Second; I believe as a user of xda it is your duty to maintain the integrity of the principles of xda, and Android. Don't support closed source works, voice your disgust so that xda sees the will of its users, that the over whelming majority wants things to remain open source. Tattle your ass off if someone has broke the copyright law and used someone's work without permission and credit.
It is important to keep both xda and Android running on the same principles it started with. Don't let this keep happening guys! This is very serious, a lot of developers are breaking the law doing what they are doing!
Sad Panda said:
I have complained about this over and over, and will continue to complain in multiple threads until more people see the point I make and support that. Using someone else's kernel and/or ROM as a base for their "new" ROM isn't all bad all the time. It is analogous to game development on a PC using another developer's graphics/game engine (only with permission and proper credit of course!!). It saves time, and in some cases help that particular engine to advance, but it slows down new technological advancement in the industry as a whole.
Developers need to start honing their skills, start attempting to bring a ROM to the public that they built from the ground up, that includes a kernel build from the ground up too. Doing this eliminates such a large collection of ROMs that are all essentially the same, and because of the open source nature of Android it brings new technological advances to the public faster. It also raises the bar, the standard. The public will begin to expect more out of Android, and this in turn creates more motivation for a newer, better Android.
I think some developers have lost sight of the purpose and nature of open source information and products. Instead of hijacking someone's source code, and using it as a base for a new ROM with a new name, and small amount of new features, development should be done that conforms to the original intent and purpose of open source. Work together with a developer that has created a ROM [from the ground up] that is most similar to the product you want to create. Improve the ROM as a team, make bug fixes and enhancement to the existing ROM. That is what open source was meant to do. This will prevent a forum list of 32 half assed roms, and replace it with 10 really good yet unique roms.
If you can't find an existing ROM, a Dev team that has different ideas of what make a ROM good, or there is no ROM that exists that is similar enough to your vision of the product then, and only then should you develop something new.
I realize my views aren't going to match up with everyone else, but I am sure a happy medium could be found that produces a situation better than what we have now. Thanks for letting me rant, and for reading my thoughts!
Click to expand...
Click to collapse
Or learn to code yourself and create roms from the ground up. Most devs do what they do for themselves first, and allow us to ride on their coattails. Not a bad ride if your like me and have no coding skills. Otherwise, I doubt your plea is going to convince a dev to do anything more or less then they do now, unless it interest them personally.
I do agree with you though. I'm coming from Android on the Touch Pro 2 where a small group of devs are building EVERYTHING from scratch. From the modems to the light sensor. It's a huge job done out of love for the hardware, for fun, and a passion for coding.
knowledge561 said:
Link please. Ive been hunting it.
Temari x Shikamaru
Click to expand...
Click to collapse
he links only via twitter posts and in his IRC, send him a tweet. iirc still in beta, but he does some nice ROMs
Serren said:
Or learn to code yourself and create roms from the ground up. Most devs do what they do for themselves first, and allow us to ride on their coattails. Not a bad ride if your like me and have no coding skills. Otherwise, I doubt your plea is going to convince a dev to do anything more or less then they do now, unless it interest them personally.
I do agree with you though. I'm coming from Android on the Touch Pro 2 where a small group of devs are building EVERYTHING from scratch. From the modems to the light sensor. It's a huge job done out of love for the hardware, for fun, and a passion for coding.
Click to expand...
Click to collapse
Thank you for your comment and support. I don't disagree with you. If you steal a loaf of bread to feed yourself, is it any less of a crime than to steal a loaf of bread to feed you and your family and friends? Or is it the same or worse?
I think either way it isn't ethical. People need to think less about themselves I think. I must reiterate and clarify so I am not misunderstood. I don't think it is inherently bad to be using a ROM as your base, but it is wrong to then close the source of a previously open piece of work and/or not maintain the original license, and give credit in every spot it should be given in. That would include its distribution, the license, the source code itself, and any where else that you put your own version, app info, and copyright notice. Am I wrong?
Sad Panda said:
I fully understand your frustration. I am a software engineer too so I know what you are going through. I have not yet begun developing for Android, but will. There is a little bit of a problem here that could easily be solved, and the community has a responsibility to protect the intellectual property rights that you and every other developer like you is entitled to. In fact it is a right that is protected by the integrity of the constitution of the united states, and many other countries and law enforcement around the world. This is a failure that not just developers, mods, and admins have, but a responsibility and failure that every user at xda shares no matter who they are.
First off; not to offend any MIUI developers that may be watching, but if you are developing for Android you need to be using a license that is open, and your source needs to be open too. This is especially true if you are using xda as a distribution medium, but sadly while xda has said they encourage, and want every development to be open source they are not forcing the matter. This is a failure I think. It also makes MIUI look suspicious too, as there isn't a way to verify if their source is uniquely theirs'. I personally believe xda should not allow software that is not open source to be distributed. If google didn't keep the open source principle when they acquired Android roms like MIUI would NOT exist! It is highly unethical to take the base ROM from google because it is open source, and then close the source. That is wrong wrong wrong! It is also illegal! You can not redistribute the Android OS even if you have made changes and then close the source and not maintain the software license google has on place.
Second; I believe as a user of xda it is your duty to maintain the integrity of the principles of xda, and Android. Don't support closed source works, voice your disgust so that xda sees the will of its users, that the over whelming majority wants things to remain open source. Tattle your ass off if someone has broke the copyright law and used someone's work without permission and credit.
It is important to keep both xda and Android running on the same principles it started with. Don't let this keep happening guys! This is very serious, a lot of developers are breaking the law doing what they are doing!
Click to expand...
Click to collapse
Let me preface this by saying that I agree with you..
However android is meant to be open source, the license that they use (Apache) does not require it.. The reason they chose the Apache license was to give people the freedom to choose (their words). So technically people like miui don't have to post source for anything other than kernel (which is GPL).
This link has some good info on it.
http://source.android.com/source/licenses.html
But even CM doesn't have to provide source, which in recent history they haven't while starting builds.. We can't demand source, when the licensing doesn't demand, but that doesn't mean we still can't prove direct kang. The reason I have android over anything else is the freedom it gives and the open nature of it.
Edit: and you should always credit someone if you are using their work, and also have their permission. I was referring to general source from android itself, not from each other.
_______________________
No d3rp left behind - ranger61878
The problem is, nobody wants to start a ROM from the ground up, and the people that do are already involved into team projects (CM/MIUI). It takes a long time to create a ROM from the ground up that utilizes all of a phone's hardware properly. Look how long it took CM to get 4G onto the EVO 4G, and that was a team of highly skilled individuals practically reverse engineering code to do it.
Now imagine all of the copy and paste kitchen users here trying to accomplish that. It just won't happen lol.
That's why we have pretty much the same thing in different colors. It kind of sucks, but hey, HTC did the majority of the work, and if something already works good enough, the average person will be fine with and use that.
Yeah, it does slow down the evolution and innovation of Android as a whole, but you have to put some of the blame on OEMs for pushing out 45 different phones a year. Nobody is going to be encouraged to create something from the ground up for a phone that will be replaced and obsolete by the time they're finished.
The G1 is the prime example of a great phone that got tons of developer support, tons of new things, and tons of unique ROMs. But that was the beginning, and I doubt that's ever going to happen again.
HTC all but pushed this EVO 3D out, and forgot about it. They've released a good 19 phones since then at the rate they're going, most of us will have moved on to the next one in a few months. Sad but true.
That is why I have stuck with and will probably continue to use a Stock ROM, modified to my liking and stripped. There isn't much else you can hope for. 3D has failed to really take off like HTC and the rest of us wanted. There is no motivation for any of the teams out there to focus on reverse engineering their ROMs to use 3D. MIUI to this day hasn't bothered with WiMAX and with good reason. Sprint all about blatantly announced its slow death in favor of LTE. It would have been a waste of time for the MIUI team to implement it. Kudos to Team Win and CM for gracing us with it on the EVO 4G. But, hindsight has probably made people mad that all of their time and energy went into something that's getting canned.
Alot of good points freeza. These are paragraphs I like to read.
Temari x Shikamaru
Why is there such alot more development and forum activity on for example the Xiaomi Redmi phones than on this one? The p9000 got excellent hardware for a great price but the community is really small somehow and the software is still buggy? How come? Do you think its still worth to wait for more activity and responses from developers for this phone or is it a "dead cow" already and better to swap to another brand to get support from developers on for example CM or RR?
furchtlos76 said:
Why is there such alot more development and forum activity on for example the Xiaomi Redmi phones than on this one? The p9000 got excellent hardware for a great price but the community is really small somehow and the software is still buggy? How come? Do you think its still worth to wait for more activity and responses from developers for this phone or is it a "dead cow" already and better to swap to another brand to get support from developers on for example CM or RR?
Click to expand...
Click to collapse
Development for this device is far from dead, we have a stable device tree for building custom ROM's, CM and RR ROM's already released, a fully source built TWRP and work on custom kernels is just beginning. That's a lot more development already than an awful lot of devices see in their entire lifetime.
I would rather say it has just begun. Development for this MTK chip is not a matter of course and the outcome so far is pretty exciting. This opens the way for other devs who work on other devices with the same chipset. It's just that many devs simply prefer Snapdragon which leads to higher dev count on those devices, faster bug fixing etc. I am pretty excited what the future brings not only for our P9000 but MTK devices in general as far as flashing and development goes.
Development is dead? What gave you that impression? For starter this phone already has a working twrp recovery. That is more then some Chinese phones get in their whole lifetime. Kernels is the area of development next and elephone has been kind to release the source code for the phone. Again more then most developers even bother with.
well, it got twrp,root and xposed working. More than some name brand phones that stop official updates after a year.
But i admit it is easier to update my old nexus 4 with cm downloader. Just click the update notification and latest cm gets installed.
It is also getting nougat in November hopefully
mangoman said:
well, it got twrp,root and xposed working. More than some name brand phones that stop official updates after a year.
But i admit it is easier to update my old nexus 4 with cm downloader. Just click the update notification and latest cm gets installed.
Click to expand...
Click to collapse
That's because Nexus 4 is an officially supported device by CM.
It's very difficult for MTK devices in general to get official CM support because we have to patch some things in the framework to make camera, RIL (mobile data) etc working.
The official stance is that these things should be done in device tree as no proprietary code is allowed in CM framework.
Initially when our patches were submitted to CM Gerrit they were rejected because of this, Leskal is working on minimising the patch work needed and getting more of the generic MTK code accepted on Gerrit.
Not helped by the fact that MTK themselves aren't helpful or willing to support developers as it doesn't suit their replace and force upgrade business model. Technically how they operate and their refusal to release official development tools or code is a violation of the open sources nature of Android. But google has yet to do anything serious about it. As far as I know, any code we have is from reverse engineering and leaks.
Android-UK said:
Not helped by the fact that MTK themselves aren't helpful or willing to support developers as it doesn't suit their replace and force upgrade business model. Technically how they operate and their refusal to release official development tools or code is a violation of the open sources nature of Android. But google has yet to do anything serious about it. As far as I know, any code we have is from reverse engineering and leaks.
Click to expand...
Click to collapse
Not true, I've met up with MTK engineers at DevCon and they do actually encourage development, they just seem to lately be wanting to protect their HAL's and drivers which as pointed out on the XDA portal article about this is sort of ridiculous. But then again it's proprietary code and not under the GPL so whilst we can say it's stupid we can't really contest it, it's their choice.
The code we have is completely official and not gotten from reverse engineering.
Jonny said:
Not true, I've met up with MTK engineers at DevCon and they do actually encourage development, they just seem to lately be wanting to protect their HAL's and drivers which as pointed out on the XDA portal article about this is sort of ridiculous. But then again it's proprietary code and not under the GPL so whilst we can say it's stupid we can't really contest ot, it's their choice.
The code we have is completely official and not gotten from reverse engineering.
Click to expand...
Click to collapse
I have seen many a leak before. But OK they support developing but at the same time they don't help provide any decent tools for troubleshooting or development.
Android-UK said:
I have seen many a leak before. But OK they support developing but at the same time they don't help provide any decent tools for troubleshooting or development.
Click to expand...
Click to collapse
Why do they need to? There's already great tools around for that, I know Qualcomm certainly used to provide a package for debugging the lower system levels but it wasn't widely available as the lower levels of the device booting process are not needed to be modified outside of OEM labs and manufacturing.
The lowest level we need is kernel debugging and the kernel already provides that via last_kmsg and desmsg etc, all other tools are already available as part of ADB, logcat etc. There are also a plethora of other tools readily available.
I would call it pretty dead now Well, if not dead then dying.
Let's hope for a Christmas special
Anyone else see this:
https://9to5google.com/2016/09/19/zte-is-working-to-bring-an-official-cyanogenmod-rom-to-the-axon-7/
Yes, it's been discussed in the CM dev topic.
xtermmin said:
Yes, it's been discussed in the CM dev topic.
Click to expand...
Click to collapse
What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
jim262 said:
What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/development/cyanogenmod-13-a2017u-t3457410/page10
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
jim262 said:
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
Click to expand...
Click to collapse
From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Only for USA.
rikin93 said:
Only for USA.
Click to expand...
Click to collapse
Correction: Only for unlocked bootloaders, as it will not be officially signed by ZTE.
xtermmin said:
From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Click to expand...
Click to collapse
Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
jim262 said:
Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
Click to expand...
Click to collapse
There's a huge difference between CyanogenOS and CyanogenMod behind the scenes though. Like you said, CyanogenOS is in-house, but most importantly it tends to include bloatware, especially now that Cyanogen the company is owned by Microsoft. And since it's closed source, people who want to develop custom ROMs will still have no access to the sources that would speed up development. Plus, if there are bugs or features that people want to implement, they can't, and have to wait for Cyanogen to release them. This also means that things such as security patches will have to wait for official rollout by Cyanogen.
Cyanogenmod, however, is open source, not controlled by Cyanogen the company at all, bug fixes / features can be added and addressed by the community, security patches can be applied to nightlies quickly, etc.
jim262 said:
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
Click to expand...
Click to collapse
It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
If they did offer open source at least it would alleviate concerns on the Chinese state-sponsored company reputation
Finally, the best hardware of 2016 and all it needs is aosp love... I hope this helps to spur more development or makes it easier for our fantastic developers at XDA.
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Do we have any ETA on this ?
I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
rczrider said:
It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
Click to expand...
Click to collapse
Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Araewuir said:
Do we have any ETA on this ?
I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
Click to expand...
Click to collapse
The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
jim262 said:
Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Click to expand...
Click to collapse
Okay.
xxBrun0xx said:
The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
Click to expand...
Click to collapse
I feel like the last phone I owned with that level of support was the Nexus 4.
rczrider said:
Okay.
I feel like the last phone I owned with that level of support was the Nexus 4.
Click to expand...
Click to collapse
One Plus released everything before the phone even hit the market, so there was development for the One Plus 3 from the beginning. The Axon, in my opinion, is a very good device, but ZTE has limited development of this product. It is almost as though they are perfectly happy being an iPhone/Apple wannabe.
japzone said:
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Click to expand...
Click to collapse
Which is never a good thing. Especially when they admit they don't care.
As a Sprint subscriber I'm locked out of the Axon7 until Sprint stop being dickbags about BYOD, which most likely will be never. If that changes, I'll probably buy an A7 if CM actually appears in a timely fashion since Shamu is being dropped by Google very shortly.
...but dumping code on the community and expecting them to make it right is massively annoying at best. It is exactly what Google does with AOSP....The Nougat AOSP is seriously broken and takes a ton of effort to fix enough just to get to compile. The stock AOSP GApps packages are all in varying stages of brokenness as of now. Sure they release the source, but what you get doesn't compile without a ton of forensic work.
Nougat has been on Nexus for over a month (minus Shamu)...and it is not going well.
I am surprised that you missed that or maybe I missed it here
I dirtyflashed it over a CM13 and it seems to work
testing now
here are the roms/links
on german x820 forum its clear #1
http://download.mokeedev.com/?device=le_x2
dont forget its without gapps so flash add them when you like google stuff
Se didnt miss it but thanks anyway. That ROM was deleted from xda due to the fact that some users that dont do anything else but complaining, and attacking the dev. The dev from mokee hás informed that hes not posting anymore ROMs in xda. Nougat included
What is the dif btw release n nightlies
nosidefcp said:
Se didnt miss it but thanks anyway. That ROM was deleted from xda due to the fact that some users that dont do anything else but complaining, and attacking the dev. The dev from mokee hás informed that hes not posting anymore ROMs in xda. Nougat included
Click to expand...
Click to collapse
Hello. You forgot to tell the full truth. The case is the dev was asked to release sources and he refused.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Filozof71 said:
Hello. You forgot to tell the full truth. The case is the dev was asked to release sourced and he denied.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
Thats not true. He said he wasnt releasing the source in that day. Three por four days later he released here the source code
nosidefcp said:
Thats not true. He said he wasnt releasing the source in that day. Three por four days later he released here the source code
Click to expand...
Click to collapse
Incorrect. People were asking for the Device Tree used to build Mokee, which wasn't and still hasn't been provided. XDA isn't a place for you to download roms, it's a developer community. Pretty sure the device tree would have been converted from one that was available (Probably OP3) and not sharing it is disrespectful to every developer who has worked on it previously.
https://github.com/MoKee/android_device_letv_le_x2 is empty.
mikeysteele said:
Incorrect. People were asking for the Device Tree used to build Mokee, which wasn't and still hasn't been provided. XDA isn't a place for you to download roms, it's a developer community. Pretty sure the device tree would have been converted from one that was available (Probably OP3) and not sharing it is disrespectful to every developer who has worked on it previously.
https://github.com/MoKee/android_device_letv_le_x2 is empty.
Click to expand...
Click to collapse
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
Who's talking about rules? This is a community and communities have standards. You're free to do whatever you like but expect people to be unhappy if you disrespect the community.
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
First of all: THANKS for your ROMs. Second: i would really consider publishing the device tree, because there might be a few others who would like to contribute.
Although the Max 2 is a rather "specific" smartphone, which - outside of India and China - nobody really considers buying.
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
The Open Source rule and spirit. We share our knowledge and we don't hide it.
https://github.com/deadman96385/android_device_leeco_x2
https://github.com/AndroPlus-org/android_device_leeco_x2?files=1
I know is difficult to you to understand this. There must be a reason why you don't want to provide your sources.
http://forum.xda-developers.com/showthread.php?t=3494247
ffboy doesn't own anybody anything. He releases his ROM's for free, he doesn't force you to use them. Many rom developers don't release their source code/device trees, one reason is that people could take there hard work getting everything to work and use to build their own ROM's and get donations from them without doing any hard work themselves. Even my grandma can build a ROM when eveyrthing is handed to her. One example is the very resepected developer arter97 who didn't release cyanogenmod device trees for s6 for a while when he was developing for s6. Get off ffboy's case, he is a developer and doesn't deserve this, if there was a downvote in xda I would downvote the haters. You've already been warned by the mods yet you still pour hate on to the dev.
Edit: I agree with ffboy we should continue petitioning LeEco for device trees.
@whymoo
I am not arter97, i don't care what he does and i don't accept donations.
ffboy released his rom under mokee s name who they aclame to be "open source". Also i except to see the whole source and not part of it.
If ffboy doesn't like this he could publice his rom to a hoster like "mega"
ffboy and not me already copied code and signed the same code as his own and don't gave proper credit.
We are a big community and we help each other. We share our knowledge and don't hide it. I and other people don't like to reinvend the wheel again. This is a waste of precius time who lot of us they don't have. Yes! we can contribute, merge bugs and maybe compile other roms and yes, ffboy must accept, that maybe me or others wanna use his device tree or some other code. BUT we don't forget to give credits.
Btw i don't be warned and i don't see a reason why should be.
It's CM or stock based?
ir work?
monleylord said:
@whymoo
I am not arter97, i don't care what he does and i don't accept donations.
ffboy released his rom under mokee s name who they aclame to be "open source". Also i except to see the whole source and not part of it.
If ffboy doesn't like this he could publice his rom to a hoster like "mega"
ffboy and not me already copied code and signed the same code as his own and don't gave proper credit.
We are a big community and we help each other. We share our knowledge and don't hide it. I and other people don't like to reinvend the wheel again. This is a waste of precius time who lot of us they don't have. Yes! we can contribute, merge bugs and maybe compile other roms and yes, ffboy must accept, that maybe me or others wanna use his device tree or some other code. BUT we don't forget to give credits.
Btw i don't be warned and i don't see a reason why should be.
Click to expand...
Click to collapse
first i opensourced kernel soucre as GPL requirement,but device tree was not GPL and you do not have the right to force me do things i dont like.
2nd i know i made mistakes on kernel source for commit authorship brcause i am not good at git tools but i have already corrected them.
i dont care you like me and my rom or not
i have released all source of mi max on my github
the only reason i dont release max2 device tree is,
Some people here is just do nothing but PUSHING AND ATTACKING me because they want my device tree to build there roms to gain Respect and donations i think.they are so rude and ridiculous
when i said "No plan to release kernel source RECENTLY" and released a few days later,they don't care and start attacking and pushing
i also dont warned by forum moderatoer by not released device tree
So ban me out of this forum if you can
ffboy2009 said:
first i opensourced kernel soucre as GPL requirement,but device tree was not GPL and you do not have the right to force me do things i dont like.
2nd i know i made mistakes on kernel source for commit authorship brcause i am not good at git tools but i have already corrected them.
i dont care you like me and my rom or not
i have released all source of mi max on my github
the only reason i dont release max2 device tree is,
Some people here is just do nothing but PUSHING AND ATTACKING me because they want my device tree to build there roms to gain Respect and donations i think.they are so rude and ridiculous
when i said "No plan to release kernel source RECENTLY" and released a few days later,they don't care and start attacking and pushing
i also dont warned by forum moderatoer by not released device tree
So ban me out of this forum if you can
Click to expand...
Click to collapse
I don't care if you like ne or not either. I gave you also a like. I don't care either to gain Respect or earn money through donations.
You are the only one here who try to gain respect or donations but your behavior shows me clearly that you are reacting like a little defiant child who felt driven into a corner.
I made a Pointment about you and you have to accept it.
monleylord said:
I don't care if you like ne or not either. I don't care either to gain Respect or earn money through donations. You are the only one here who try to gain respect or donations but your behavior shows me clearly that you are rect like a child. I made a Pointment about you and you have to accept it.
Click to expand...
Click to collapse
I'd be interested in the device tree so I could play around building with some custom toolchains. All my phones run ROM's I've compiled myself but I've never shared them with anybody here as they aren't my work.
mikeysteele said:
I'd be interested in the device tree so I could play around building with some custom toolchains. All my phones run ROM's I've compiled myself but I've never shared them with anybody here as they aren't my work.
Click to expand...
Click to collapse
This will become ridiculous be smart and open with everybody we talk about a phone don't forget this please
sdevaux said:
This will become ridiculous be smart and open with everybody we talk about a phone don't forget this please
Click to expand...
Click to collapse
I think you misunderstand. Building ROMs with custom toolchains and then posting them here would be passing off the work of others as my own, which is not on. I'm not making any source code changes.
mikeysteele said:
I think you misunderstand. Building ROMs with custom toolchains and then posting them here would be passing off the work of others as my own, which is not on. I'm not making any source code changes.
Click to expand...
Click to collapse
I understand it's just that everyone should be open with others it would allow us to move forward the rom development for this model that's just my opinion
I would really like to see the latest PA ported to the original MiPad. Is anybody up to take up the mantel!?
No go. Some of PA's stuff is closed source, so I'm afraid unless someone in the PA team gets a Mi Pad, we'll probably never see a build.
drakonizer said:
No go. Some of PA's stuff is closed source, so I'm afraid unless someone in the PA team gets a Mi Pad, we'll probably never see a build.
Click to expand...
Click to collapse
Thanks for shading light on the topic.
drakonizer said:
No go. Some of PA's stuff is closed source, so I'm afraid unless someone in the PA team gets a Mi Pad, we'll probably never see a build.
Click to expand...
Click to collapse
Did you read this https://plus.google.com/+ParanoidAndroidCorner/posts/dcrz5JP1HLg - seems there's hope after all
"Device Maintainers
We are currently looking to expand our roster of supported devices and to do this we would like to recruit some more developers to our team. If you think you have what it takes and have a device (or two) that you’d like to see supported by us we’d like you to get in touch. "
Palm Trees said:
Did you read this https://plus.google.com/+ParanoidAndroidCorner/posts/dcrz5JP1HLg - seems there's hope after all
"Device Maintainers
We are currently looking to expand our roster of supported devices and to do this we would like to recruit some more developers to our team. If you think you have what it takes and have a device (or two) that you’d like to see supported by us we’d like you to get in touch. "
Click to expand...
Click to collapse
Not yet unfortunately. They're looking for official maintainers. Our device can't go official for any ROM because in order to get a stable build, the developers patch the Android source itself, which is not possible in official builds built by a server. In addition, if we were to use the new blobs (that don't require said patches), we wouldn't have a working camera, which a custom ROM community like AOSPA would never agree to.
Once camera starts to work with new blobs, we can expect something.
drakonizer said:
Not yet unfortunately. They're looking for official maintainers. Our device can't go official for any ROM because in order to get a stable build, the developers patch the Android source itself, which is not possible in official builds built by a server. In addition, if we were to use the new blobs (that don't require said patches), we wouldn't have a working camera, which a custom ROM community like AOSPA would never agree to.
Once camera starts to work with new blobs, we can expect something.
Click to expand...
Click to collapse
Thanks for clarifying that Let's hope for the best.