Related
This guide tries to explain very briefly the different types of CyanogenMod builds, particularly for the Sony Xperia devices, and what usage each type may be suitable for. The guide is oriented towards newcomers, who often find themselves wondering what are the differences between these various builds (don't worry, I used to be perplexed myself) and which one would serve them better. Anyone seeking further information is well advised to check the CyanogenMod wiki or search around the forums here.
The nightlies are regular automatic builds* of the CM source. Because changes get constantly pushed to the CM source from various developers, these builds reflect a more or less random state of the code, and because there's no human intervention in deciding whether to build or not, the nightlies can contain random bugs. Actually, the larger and most severe bugs are typically filtered out by the preliminary testing and review process before they even get committed, but it's impossible to catch everything that way. Indeed, the nightlies' primary purpose is just to make sure that the code still builds correctly. Nevertheless, they are also a rather useful tool for large-scale testing -- and that's how these not-so-huge bugs get caught as well.
The more substantial changes or the ones that could possibly break a lot of things (or few things really bad) get tested separately, with the experimental builds, before they are committed to the CM source.
The stable builds are based on a snapshot of the source code that is deemed suitable enough for everyday use. They are expected to be free of any serious bugs. By the way, a "snapshot" is just what it sounds like: a momentary picture of the code at some specific point of time, as decided by of the developer(s) who oversee the project development. In technical terms, the snapshot is a Git tag.
When a stable release is planned, the commits are gradually restricted to only the ones that fix things; the ones that "merely" introduce new functionality (which potentially means new bugs) are postponed until after the release (in developer terms, the code is "frozen"). In this process, the code gets several preliminary snapshots, namely, the release candidates (or RC), which reflect the advancements in the code stabilization and bug fixing. In other words, each new RC should have more and more of the identified issues ironed out, until all of them eventually get fixed, at which point the stable version is finally released (hence why an RC is just a "candidate").
The FXP builds are manual builds of the CM code with patches by the FreeXperia project. FreeXperia is the core group of developers who, with the help from other skilled developers from XDA and CM, maintain the Sony Xperia line of devices for CyanogenMod. This means that (an often asked question) most of these patches get promptly committed to the general CM source. The only exception might be changes that turned out to behave badly. In other words, any fixes or new features in the FXP builds very soon get included in the CM nightlies as well. Unlike the CM nightlies, however, the FXP builds are manual, so they are expected to be more stable: whether because the current code has been confirmed as stable enough, or because particularly problematic one has been patched. Thus, they might be considered the equivalent of the CM milestone (or M) releases.
IMPORTANT: Whichever type of build you choose, always keep current enough backups, preferably of different types (e.g. a nandroid/CWM/TWRP and a Titanium/etc. one) and in different physical locations (in particular, keeping your backups only on your SD card is asking for trouble). Keeping several chronological versions is a wise practice as well (you might, for instance, find your last and only backup to be corrupt). Remember that you can never have too many backups!
Which version should I use if I...
TBA
This guide started as a post in another thread, and I'd like to thank @tilal6991 for confirming what had been only assumptions then. All your recommendations, whether to fix mistakes or to enhance the guide, or even just comments, will of course be very welcome.
----
*) The current list of the automatically built targets, together with the frequency of the builds, is here.
Changelog
----------------
12 Sep 2013 - Initial version.
Note to the mods: I'm afraid I couldn't think of better forum for this short guide. It is relevant to more than just the Xperia T, yet perhaps not that helpful beyond the Sony devices, as the major source of confusion seems to be the FXP builds (and these, of course, are Sony specific). If you do have a better idea, please don't hesitate to move the thread -- and thanks a lot in advance.
Note about "Which version should I use if I...": I'll try to fill that one in as soon as possible, but I got some serious problems at home, so it may actually take a while. Sorry about that.
Guide moved to general...
Nice guide Btw
Sent from mALL GLORY TO THE HYPNOTOAD!!
Lollipop
No doubt the big news at the beginning of November was the release of the Android 5.0 Lollipop source code. AOSP began seeing the code on the 3rd, and completed the majority of the push on the 4th, with some remaining stragglers seeing code uploaded midday on the 12th. Work on CM12 began in earnest at the end of last week, and you can now successfully sync and build the work in progress against a handful of devices.
We are unlikely to enable nightlies against CM12 until towards the end of this month, or early next month, as we work to incorporate the CM features you’ve all come to appreciate into the new code base, and reimagine those that no longer translate to the Material look of L. It is also currently too soon to tell how many devices will transition from 11 to 12, though early traction has this number higher than we had initially hypothesized.
Home builders and community members are welcome to take a peek at the builds at their leisure, just repo init the new branch using the following command:
repo init -u https://github.com/CyanogenMod/android -b cm-12.0
Again, please be aware that not every device is in a ‘daily driver’ state under CM12, and the codebase is nowhere near feature complete. Our contributors are working hard, and our gerrit is aflutter with activity. If all goes well, we’ll have something special to welcome the upcoming holidays and New Year.
Happy Flashing
-The CyanogenMod Team
ps: can someone finaly tell me why the hack are there s3 QandA threads in here???? s3 has their own section for A and Q -.-, why do the spam here in i9305 forum???
klemen241 said:
Lollipop
No doubt the big news at the beginning of November was the release of the Android 5.0 Lollipop source code. AOSP began seeing the code on the 3rd, and completed the majority of the push on the 4th, with some remaining stragglers seeing code uploaded midday on the 12th. Work on CM12 began in earnest at the end of last week, and you can now successfully sync and build the work in progress against a handful of devices.
We are unlikely to enable nightlies against CM12 until towards the end of this month, or early next month, as we work to incorporate the CM features you’ve all come to appreciate into the new code base, and reimagine those that no longer translate to the Material look of L. It is also currently too soon to tell how many devices will transition from 11 to 12, though early traction has this number higher than we had initially hypothesized.
Home builders and community members are welcome to take a peek at the builds at their leisure, just repo init the new branch using the following command:
repo init -u https://github.com/CyanogenMod/android -b cm-12.0
Again, please be aware that not every device is in a ‘daily driver’ state under CM12, and the codebase is nowhere near feature complete. Our contributors are working hard, and our gerrit is aflutter with activity. If all goes well, we’ll have something special to welcome the upcoming holidays and New Year.
Happy Flashing
-The CyanogenMod Team
ps: can someone finaly tell me why the hack are there s3 QandA threads in here???? s3 has their own section for A and Q -.-, why do the spam here in i9305 forum???
Click to expand...
Click to collapse
I tried to build Lollipop myself but i get some annoying error. BTW s3 threads in the s3 lte Q/A are heck of a spammers.
limnaln said:
I tried to build Lollipop myself but i get some annoying error. BTW s3 threads in the s3 lte Q/A are heck of a spammers.
Click to expand...
Click to collapse
my friend ported aosp to lg l9, the phone i used to own. But i guess its easy from nexus 4 to lg l9, i kinda hate samsung for the complexity of porting
klemen241 said:
my friend ported aosp to lg l9, the phone i used to own. But i guess its easy from nexus 4 to lg l9, i kinda hate samsung for the complexity of porting
Click to expand...
Click to collapse
I didn't tried with AOSP, I tried with CM12.
Hi guys, it's true that s3 will not receive official cyanogen mod cm12 ? It's not even showed on github branchs about this device. https://github.com/CyanogenMod/android_device_samsung_i9300/tree/cm-11.0
I'm on a group about cyanogen mod on facebook, an italian group, and there a guy from this group that said me that s3 will not be supported from cm12, no lollipop officially speaking from cyanogen mod, only unofficial. So it's really true ? Someone here know something about this story ?
... Is the question we get asked ALL the time on this forum. This is currently being written on my phone so there might be some typos. I'm going to try and explain why we as a community find it so hard to develop for this phone and maybe how we can solve it.
1. AOSP
Maybe one of the biggest issues with this phone - AOSP, and the device tree.
When Sony made this phone in 2014, Jellybean was originally made with this phone and it was very stable - whereas Sony rushed the Kitkat update, meaning that many, many bugs were left unfixed making the phone unstable. Sony couldn't be bothered to then support this phone any further and left us with this heap of a mess. They also rushed the kernel too - and this is where AOSP comes into play.
I recently posted in the AOSP support fourms about our phone and Sony said to boot into AOSP the phone would need to have extensive changes to the kernel to boot into AOSP. The reason they would have to make these changes (and by that they mean rework the entire ROM and firmware) is because Sony rushed the Kitkat update making everything unstable. This means that we have no full device tree meaning that building from source is very difficult. This is why Caio's CM11 is very buggy atm. Hopefully Caio and Kizoky will make a breakthrough soon. Good luck!
2. Why do we have so many Stock UI modified ROMs? (Yes, there is more to it than that)
It literally links in with the top post.
Because we have no full sources, we can't build free, custom ROMs that have nothing to do with Sony. If Sony gave us this (which right now Sony are not playing ball) we could, of course, build custom ROMs.
3. No support/repoduction? (I dont know if this phone is still being made)
Sony made a bad job of this phone; god, I would not buy this phone if it wasnt given to me. Support has ended for this phone because of its unpopularity; high cost, low-end specs, rushed updates. When Kitkat came out for us the update (as we know) was very rushed and a lot of users just... left this phone to mirgrate to different phones - my dad left this for a Galaxy A3 - and my god, what a phone that is for the price. Of course, a LOT of devs then left this phone, and so Sony left this phone as well.
This thread is in no way finished yet - there are many more things to add. I'm gonna get my hands dirty with this phone soon when summer break comes around for me, but ill start small until then. My plans are kernel first then maybe PA4 or CM developing, not sure yet.
Caio's and Kizoky's posts - thanks to them, @Caio99BR and @Kizoky
@Caio99BR
4. Why do the devs not like to develop for this device?
First because that reason #1 in first post, second because this is a low-end device, many of then not have a full developer (eg L1II, Xperia E) and when have most of then try to do something but is stopped by low knowledge or some impossible fix problem, third in my opinion is because confusion made in building a ROM to a new device.
5. Why are you building KitKat(CM11) and not JellyBean4.3(CM10.2)?
First problem: DualSim
Only CM11 support it, and we not have only the Single Variants, I have choiced this too for L3II, and this have been released with JB4.1.
After it this not have problems, the CM10.2 is more stable and with less ram consumption (like CM10.1 is more more stable and etc), but is more time lose if we back to it now, if someone want to make it, go and Good Luck
6. Why the greatest devs not make something to this device?
First thing is time, or if not time, just forgived this, 2 Recognized Developers (Yes, its a ****ing awesome flag) said "I have got this phone and I will do something for him", one posted at here on XDA, and other said it to me (member of FXP Team - greatest Team behind some Sony devices), today no one of two have made nothing, this last said "I will help you" but no, @Kizoky helped more than him, but I'm of subject.
By final its more a revolt than a answer, good devs after get flags, reputation, forgive simple things and not help others or not make that things he did to gain prestige.
Sorry if it not answer the ask, but it's the true, also sorry my english, its damaged.
@Kizoky
7. Low end phone
8. High price when phone released (Xperia E1 2014: 512mb 3MP Sony you are drunk vs. Xperia M 2013: 1024mb 5MP lower price)
9. Not available in the U.S
Good luck all with developing!
3. Why the devs not like to develop to this device?
First because that reason #1 in first post, second because this is a low-end devices, many of then not have a full developer (eg L1II, Xperia E) and when have most of then try to do something but is stopped by low knowledge or some impossible fix problem, third in my opinion is because confusion made in building a ROM to a new device.
4. Why are you building KitKat(CM11) and not JellyBean4.3(CM10.2)?
First problem: DualSim
Only CM11 support it, and we not have only the Single Variants, I have choiced this too for L3II, and this have been released with JB4.1.
After it this not have problems, the CM10.2 is more stable and with less ram consumption (like CM10.1 is more more stable and etc), but is more time lose if we back to it now, if someone want to make it, go and Good Lucky
---
Sorry if I'm using your space, but I like write some stupid/real things before sleep
1. Low end phone
2. High price when phone released (Xperia E1 2014: 512mb 3MP Sony you are drunk vs. Xperia M 2013: 1024mb 5MP lower price)
3. Not available in the U.S
Haha thanks you two for those additions! About to go through OP and add some stuff; but ill leave your posts up and I wont add that stuff you guys said
xeonyt12 said:
Haha thanks you two for those additions! About to go through OP and add some stuff; but ill leave your posts up and I wont add that stuff you guys said
Click to expand...
Click to collapse
OK XD, other thing to add:
- Why the greatest devs not make something to this device?
First thing is time, or if not time, just forgived this, 2 Recognized Developers (Yes, its a ****ing awesome flag) said "I have got this phone and I will do something for him", one posted at here on XDA, and other said it to me (member of FXP Team - greatest Team behind some Sony devices), today no one of two have made nothing, this last said "I will help you" but no, @Kizoky helped more than him, but I'm of subject.
By final its more a revolt than a answer, good devs after get flags, reputation, forgive simple things and not help others or not make that things he did to gain prestige.
Sorry if it not answer the ask, but it's the true, also sorry my english, its damaged.
Some fun facts:
* The touchscreen used in Xperia E1 is more old than JB, made for MTK devices
* The bar led is the same used Xperia E
* Maybe because the Camera sensor Sony not builded the Lollipop for this device, since it's too old too, and need some hacks in kernel to make it work (by now camera sensor is broken on my LP and after in MM ROM :/)
I think that's all, just for annotation.
Caio99BR said:
Some fun facts:
* The touchscreen used in Xperia E1 is more old than JB, made for MTK devices
* The bar led is the same used Xperia E
* Maybe because the Camera sensor Sony not builded the Lollipop for this device, since it's too old too, and need some hacks in kernel to make it work (by now camera sensor is broken on my LP and after in MM ROM :/)
I think that's all, just for annotation.
Click to expand...
Click to collapse
And sources for E1 is garbage
JB was rushed, and left buggy
KK was rushed, and left more buggy than JB
Sony didn't even bother to make this phone stable (and even refused to help E1 users)
Your CM11 is still has bugs, but it is more stable than Stock ROM, I wonder why..
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Hello jcole20
That would be awesome if some devs started doing something with the RP2! If I had the knowledge, I would!! I've had the RP2 since June of this year. I had some issues with it at first but they have been worked out. I really like the phone and it would be cool to see some devs show the RP2 some love lol. Hopefully you can get something started! Take care!
Dennis
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
I am sure people would love to see some device specific development. I have read that since the release of project treble most people just flash the system image from other roms. I specifically would love to see a stockish rom so I don't loose chroma but still get updated security patches.
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Krazy_Calvin said:
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Click to expand...
Click to collapse
Most functionalities work on Pie GSIs out-of-box (you need to manually install ims.apk in order to receive SMS while on LTE, see relevant threads here, or look for it on some GSI threads such as Havoc 2.9). exFAT also works on supported GSI (with arter97's kernel), while it's not supported on stock. The only problems I have so far are bluetooth-related, and also the inability to set SELinux to permissive (not sure which might be the real cause as arter97 stated the SELinux could be permissive).
Bluetooth media audio doesn't work at all on GSI, partly due to the crippling overlays (which prevents aptX from working, and probably some other limitations). Phone calls work with a bluetooth headset, but for some reasons I couldn't properly route phone calls to my Huawei Watch 2 (which means I always have to take the call from my phone directly).
Given the mostly positive result with numerous GSIs (and that some users are happy with stock ROM, or stock-based ROM modifications), active ROM developments for the device itself doesn't seem to be at a high priority (as some might be able to contribute patches for this device to their favorite GSI instead)...
I'm currently working on my own build of LOS. I haven't seen to much active development either I'm new to rom building but looks like we could use all the help we can get!
I think the only active dev we have for this phone is Arter97's kernel and people tinkering with GSIs to get them working as they should. I wish there was more being done with the stock ROM because I like a lot of it's features, but am having a hard time dealing with it's overall instability. I'd be happy to help develop or test in whatever way I can, though.
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
Yeah, it’s definitely just total lack of interest from other devs. We even have a guy with a prototype Razer Phone 2 with an intact DRM partition and unlocked bootloader (Allowing Netflix HD and Vudu HDX) but we couldn’t even pay anyone to try to port it.
I think if we had a fully working AOSP tree that it would possibly bring other devs into the scene. Who knows though, it has never been a popular device despite how great it is.
LSS4181 said:
Most functionalities work on Pie GSIs out-of-box.
Click to expand...
Click to collapse
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
EMJI79 said:
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
Click to expand...
Click to collapse
A stock Android 10 (which means a stock vendor image for Android 10) is not necessarily required to have a usable Android 10 ROM (though it may speed up the development to some extent, if it does have one), but for GSI, having a stock Android 10 vendor image can be better (currently it's a hit-or-miss on existing Android 10 GSIs).
Another device that I have, Google Pixel C, never had stock Android 9 (so never had stock vendor images for Android 9, only for up to Android 8.1), but custom Android 9 ROMs are already available (thanks to followmsi's efforts) and are working well. For Android 9 ROMs, the build system builds new vendor images along with system image.
It's just whether we're going to see our device's trees being made possible, so we can start from there to develop our own custom ROMs. The existing materials might be a good starting point in making trees.
- Working with proprietary blobs (from Lineage)
- arter97's kernel (can be useful for making a kernel tree, though one can also consider using stock kernel source as a base)
- Razer factory images and kernel sources (for studying stock ROM/kernel details, and extracting necessary system and vendor blobs)
If you can port LineageOS to this device, great!
I don't understand why people aren't flocking to this device. I came from the LG G6 that probably will be stuck on Oreo forever that is way more popular. The RP2 is cheap, has killer specs + a micro SD card slot + a newer version of Android. Should be a developers dream, you would think. *shrug*
Not sure if anyone's active on this device at present. With RP2's 9.0 MR2 available on the official factory images page the latest proprietary blobs (as well as stock kernel source) are now publicly accessible.
Actually arter97 once mentioned that his RP2 kernel is almost inline with his OP6 kernel (which is also sdm845 and shares some similarities), so it's possible that OP6 (enchilada) trees may be a good starting point, but I'm not sure if any configurations are needed to keep 120Hz working as high refresh rate is relatively uncommon.
My time is very limited so I won't be able to dedicate too much time to experiment on this. At present most functionalities work fine with GSI (including Bluetooth, although tricky and aptX still not working).
IDK how relevant this is anymore but as a new razor phone 2 user to be soon I have been keeping up and it seems that @f(x)THaxxorX could be a possible candidate of what you're looking for I've been keeping up with development on the phone seems like he is doing pretty well even if we get patched gsi which properly work is better than nothing.
Hi,
so do you actually recommend the Asus Zenfone with LineageOS? Like if you compare it to other phones with LineageOS, is Zenfone 8 a good choice if you aim to use the Phone solely with LineageOS? Are there any major bugs, drawbacks? Is there like a list of known issues and broken functionalities?
Do you know anything about the plans for the future? I have seen that only Lineage OS 18.1 is available, is it planned to support LineageOS 19 and future versions?
When I bought my Sony Z1C a long time ago, development was very active before I got my phone, but literally just as I bought it, development stopped and I was stuck with CyanogenMod 11 (KitKat) and bugs. Huge disappointment. I want to avoid that.
Lineage 18 is almost flawless on ZF8, add gcam only