Hi all,
My apologies if this is in the wrong thread but I'd just like to clarify a few things about the types of roms out there and I'm sure you all understand the whole process better than me.
So my understanding is that aosp is the Google "original" android source so to speak, upon which other distributions are based such as cyanogenmod, miui and aokp??
Now taking cyanogenmod for our Xperia Sp for example, we have the "official" nightlies and snapshots of cm11 created by who?
And then do these form the base of say baguyz and mr steves lbl cm11 distributions? Or do they build them themselves from somewhere?
The reason I ask is because we have a cm12 lbl rom from baguyz but there are no "official" nightlies and snapshots for cm12 for huashan yet so where did this come from?
Lastly, now cm12 is released, does whoever works on the nightlies and snapshots for cm11 for huashan start doing the same for cm12 or does cm11 remain in development? If so, doors that mean we will see more cm11 m builds in the future, or just nightlies? And will there ever be an "official" cm12 for huashan?
I know this question isn't specific to xperia sp but i think it would be easier to understand in the context of a device, or more specifically, my device.
Thanks
panda_watch said:
Hi all,
My apologies if this is in the wrong thread but I'd just like to clarify a few things about the types of roms out there and I'm sure you all understand the whole process better than me.
So my understanding is that aosp is the Google "original" android source so to speak, upon which other distributions are based such as cyanogenmod, miui and aokp??
Now taking cyanogenmod for our Xperia Sp for example, we have the "official" nightlies and snapshots of cm11 created by who?
And then do these form the base of say baguyz and mr steves lbl cm11 distributions? Or do they build them themselves from somewhere?
The reason I ask is because we have a cm12 lbl rom from baguyz but there are no "official" nightlies and snapshots for cm12 for huashan yet so where did this come from?
Lastly, now cm12 is released, does whoever works on the nightlies and snapshots for cm11 for huashan start doing the same for cm12 or does cm11 remain in development? If so, doors that mean we will see more cm11 m builds in the future, or just nightlies? And will there ever be an "official" cm12 for huashan?
I know this question isn't specific to xperia sp but i think it would be easier to understand in the context of a device, or more specifically, my device.
Thanks
Click to expand...
Click to collapse
Hello there,
You already have quite a good understanding of the matter although you are a bit rough around the edges so to speak.
Let's get right on it!
1) AOSP is the "Android Open Source Project" and it is a pile of codes, different softwares from C++ to Java and more to derive the source you are able to obtain through their repositories. This in turn, gets modified by both carriers and software development teams to create third party products you see today such as Touchwiz and the SenseUi. Most of the Android Systems and modifications are tied to this source code.
2)The Official CyanogenMod Nightlies are being built by what we call as, Build Bots. This BuildBots create Cyanogenmod from source as instructed by the Device Maintainers, who's job is to modify and improve the CyanogenMod source for the device.
3)CM12 builds you see currently are being built upon multiple sources from AOSP to CyanogenMod and maybe even OmniRom. They compile and improve the code to build this ROMs that you utilize.
4) Look to "3" for the answer
5) The device maintainers are still developing cm11 and will only start on cm12 if they're directed to do so. For why this is happening, I recommend reading the CyanogenMod blog article entitled, "L is for Later". It gives you a good explanation of why they are not creating cm12 as of now.
Regards,
Furrydaus
Thanks so much for getting back to me @Furrydaus.
Sometimes no matter how much you read there's just a few things that are difficult to understand.
Thanks for taking the time to reply as i know you are quite a busy dev!
panda_watch said:
Thanks so much for getting back to me @Furrydaus.
Sometimes no matter how much you read there's just a few things that are difficult to understand.
Thanks for taking the time to reply as i know you are quite a busy dev!
Click to expand...
Click to collapse
Not a problem Panda_Watch! I'm happy to help out with the community
Regards,
Furrydaus
Related
Hey so I love that we have AOSP for my Sony = Sony Nexus!!
But who should I be following as the cutting edge of AOSP. I know Sony releases some sources but not the proprietary ones so I know most of it comes from there. I myself have just installed the latest RC3 of CM 10.1. And the bugs I used to have like Lockscreen delay and No audio on Hangouts seem to have gone. But why should I install FreeXperia over CM?
Is CM the base that everyone bases their AOSP on? Is Free Xperia more focused on the Sony Specific Issues?
And what about Linaro? Carbon? AOKP? Are they all based off the same source (they all seem to have the same bugs)
Thoughts? Direction?
Thanks in advance!
First of all, CM roms are made by the FXP team as they are official CM maintainers for Sony devices.
Secondly, Sony's AOSP sources are different from that of CM sources. AOSP implies pure android with stock customizations. CM sources is heavily customizable (think of all the settings you can do in CM10.1) they are based on Google's open source as well as the device specific source code released by Sony.
Sent from my C6602 using xda app-developers app
CM10.1 vs. Free Xperia
What is the difference between the regular CM and the one you can download from FreeXperia project?
E.g. for Xperia Z (the latest releases at the moment):
FXP222a-cm-10.1-20130604-UNOFFICIAL-yuga.zip
Click to expand...
Click to collapse
vs.
cm-10.1-20130608-NIGHTLY-yuga.zip
Click to expand...
Click to collapse
80mercury said:
What is the difference between the regular CM and the one you can download from FreeXperia project? ...
Click to expand...
Click to collapse
I too would like to know this - obviously, they're very close, but there must be something different there.
I spent an hour trying to find this out the other night - got slightly excited when I saw a message from some poor sucker who explained he was a noob, etc, blah, blah, and would someone please explain the difference. The only reply he got was a terse demand that he go read the FreeXperia dev thread and work it out for himself ...
If someone can write an explanatory sentence or two about the difference between the builds on the official Cyanogen Mod site and the FXP* builds from freexperiaproject.com, I would appreciate it.
ratworks said:
I too would like to know this - obviously, they're very close, but there must be something different there.
I spent an hour trying to find this out the other night - got slightly excited when I saw a message from some poor sucker who explained he was a noob, etc, blah, blah, and would someone please explain the difference. The only reply he got was a terse demand that he go read the FreeXperia dev thread and work it out for himself ...
If someone can write an explanatory sentence or two about the difference between the builds on the official Cyanogen Mod site and the FXP* builds from freexperiaproject.com, I would appreciate it.
Click to expand...
Click to collapse
hey man, I had forgotten that I had made this thread but long story short FXP and CM are the same. CM has their own schedule, standards and code they develop and CM work towards AOSP for all their devices. FXP are SONY only, They use the code by CM and are responsible for both the Sony releases via CM and FXP. How FXP differs is that they can go ahead and release a lot of versions without any established "stable" or milestones they just release updates as they go. CM take those Sony specific changes that are made and combine them standard CM code are release Milestones, RC's and Nightlies with varying results
TLDR: They are the same, All the Sony specific code in CM is FROM FXP, FXP has no interest in making a stable version they just release new code in an almost "nightly" fashion. Their is no guarantee that the newest FXP will be more stable then the previous, its the same risk you take when you go with CM nightlies.
Personally I prefer CM Nightlies. If you want stable (with established bugs) go with CM, if you want to be running the latest CM code go with CM but if you want the latest sony fixes (unstable at times) go FXP, who updates about 1 every 1-2 weeks
Great explanation mate, thanks for that.
Hi All,
I remember that we will not be receiving next major version of Android by CM becoz of lack of NEON instructions. I only wonder, if we will still get CM 10.2 or our last version will be CM 10.1.
Can anybody with CM insider knowledge answer?
I can only see that there was not created CM10.2 branches in our P990 github related repositories, which is bad sign to me.
Edit: Answer is Yes, CM10.1 is last version.
CM 10.1 seems to be the latest official version of cyanogenmod. But just look at all the gifted developers in the development thread. I guess someone will get it working on our device .
I think even some time ago pengus or tonyp mentioned that they like the challenge ....:thumbup:
Sent from my LG-P990 using xda app-developers app
Yes, I have read tonyp's thread and there was mentioned that CM team officially won't support 10.2 for our phone. But I hope Pengus and Tonyp will make something But it's quite possible that it will be a little bit unstable and glitchy...
p.valenta said:
Hi All,
I remember that we will not be receiving next major version of Android by CM becoz of lack of NEON instructions. I only wonder, if we will still get CM 10.2 or our last version will be CM 10.1.
Can anybody with CM insider knowledge answer?
I can only see that there was not created CM10.2 branches in our P990 github related repositories, which is bad sign to me.
Edit: Answer is Yes, CM10.1 is last version.
Click to expand...
Click to collapse
nope it isn't if you watch the developer thread you see cm10.2 only camera doesn't work yet but further it is smooth and stable i am posting this cause you may didn't see it
winstonxl2 said:
nope it isn't if you watch the developer thread you see cm10.2 only camera doesn't work yet but further it is smooth and stable i am posting this cause you may didn't see it
Click to expand...
Click to collapse
Thanks, I know about it. But unfortunately it will not be official CM, only experimental.
It's great that there are still developers who want to keep our device up to date :fingers-crossed: , but looks like it's time to look around for next future device.
p.valenta said:
Thanks, I know about it. But unfortunately it will not be official CM, only experimental.
It's great that there are still developers who want to keep our device up to date :fingers-crossed: , but looks like it's time to look around for next future device.
Click to expand...
Click to collapse
it isn't really experimental only the camera doesn't work and all cm10.1 bugs are included but cm10.2 is smoother and hdmi is partly fixed
I've been wondering for awhile now, which is better? The official CM11 builds, or the unofficial FXP builds for Xperia T? If anyone's tried both recently, please give your thoughts on performance, battery life, stability, etc. comparisons between the two. Thanks!
Personally I think both are not great. Non of the custom roms are
r-l said:
Personally I think both are not great. Non of the custom roms are
Click to expand...
Click to collapse
That's not helpful, dude...if you're not going to contribute to the discussion then don't post. Thanks anyways though.
You're asking people for there opinion and i gave mine. I tried every rom so yes it does contribute to the discussion
r-l said:
You're asking people for there opinion and i gave mine. I tried every rom so yes it does contribute to the discussion
Click to expand...
Click to collapse
When you simply say that you dislike both ROMs and all custom ROMs on the T in general, that's not contributing. It doesn't help anyone decide between CM11 and FXP. The discussion is about how you think these ROMs compare to each other. If you're just gonna say that you think they both suck, then there's no point in posting.
I suggest you know the "difference", if you could call it like this, of these two ROMs?
If not, I'll quote myself from another thread (http://forum.xda-developers.com/showpost.php?p=54754522&postcount=1049)
They've [FPX] got their own FXP releases (unofficial CM releases) which do not come that frequent (with their own boot animation e.g.); in the meantime they work on official CM - so they make the nightlies and your [CM] M9, too.
Click to expand...
Click to collapse
Meaning: FXP releases necessarily/of course contain CM code, because they maintain/supply CM for our Xperias. For FXP unofficials don't come as frequently as CM nightlies, the chance of getting a stable build is bigger than with CM nightlies. Because the FXP releases always contain FXP boot animations, these will never be official CM builds - what, in the end, implicates that neither FXP nor CM is better per se.
I'd prefer FXP over CM nightlies, but a CM snapshot over FXP relases. Just a feeling - there's no absoulte answer.
zandm7 said:
I've been wondering for awhile now, which is better? The official CM11 builds, or the unofficial FXP builds for Xperia T? If anyone's tried both recently, please give your thoughts on performance, battery life, stability, etc. comparisons between the two. Thanks!
Click to expand...
Click to collapse
TX here, but if I had to recommend one, I'd go with FXP, since I know that they at least do own a T, and can develop properly; at least it would seem so. Obviously FXP uses CM code.
On the other hand, if I had to choose, I'd choose neither and go with one of the Omni builds made by @tilal6991, since he's actually implemented fixes that, as far as I know, the "real" developers haven't done yet.
Most of the problems I see T users reporting (such as the blue screen flickers) are because they are using FXP/CM builds, and, as far as I know, Tilal fixed that, as an example.
We do not allow comparison threads on XDA, comparing or asking which is best can be seen as disrespectful towards the developers who's work is being compared. Besides the question is subjective.
Thread closed
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
There is no Cyanogen for our tablet for the moment
You can check here : http://download.cyanogenmod.org/
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Dekan54 said:
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Click to expand...
Click to collapse
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Okay - That makes sense.... I will help test if you get to that point.
Would be nice with cm12 but probably with lots of drawbacks. Samsung won't release source code of drivers and could be problematic with exynos nor will fingerprintscanner work.
BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
You may want to ask @eousphoros for help. He got it rolling on the the tab s I bet he could help you big time!
BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
Good to hear someone is working on it. ?
Sent from my not-so-stock SM-T810
CM is always buggy and lots of features wont work or plain buggy. Bloat is very minimal and works quite smoothly stock. Dont blame you if you like the "fun" of constantly flashing roms and waitkng for bug fixes.
Dekan54 said:
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
Click to expand...
Click to collapse
Hey there. As a dev myself I will explain you the difference between official CM builds (build = the ROM) and unofficial builds. Official builds are made by the pros. The guys that are in the CyanogenMod group. They know how things work and patch them due their high knowledge. They will try to update the ROM regularly and fix it as well as they can. Then there are the unofficial builds from people like me. It depends what your skills are and with what board you are working (Exynos is a pain in the ass). Not to forget what version of android your device is currently running. Unofficial builds can be buggy and could take some time to get fixed. However devs will listen to the feedback of the community too.
Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.
https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230
Which modem and boot loader can you recommend?
audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0
I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.
What device tree and kernel did you use?
DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.
If that's still Solk2's stuff it might be very old indeed.
DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.
zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.
PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.
JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards
Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.