Related
Friends,
The work on Cyanogen OS/MOD 12.1 seems to be stopped.
Developers are working hard on Cyanogen OS/MOD 13.
So lets discuss about Cyanogen OS/MOD 13.
Add your suggestions, which we want in Cyanogen OS/MOD 13.
www .cmxlog. com/12.1/ham
www .cmxlog. com/13/ham
Why there are no changelogs ? last 2 Nigthlys came without any information.
Because developers are moved towards canogenmod 13
Hope next week we get CM13 Nightly`s on our devices
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Klanac89 said:
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Click to expand...
Click to collapse
The s3 has long been in the market, others (s6, etc) cost more than double
Enviado desde mi Z1 mediante Tapatalk
Don't worry. As long as I and JoaoPaulo are around you guys will have the latest Android versions.
Just get our unofficial CM13 build.
It has everything but the fingerprint reader working and even that one is only a matter of time until we get it working.
Klanac89 said:
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Click to expand...
Click to collapse
LOL! Typical for people like you. Go ahead, don't buy. Would you rather like to get constant updates with tons of bugs, or just stable and working OS.
And watch your language here.
Also Huawei is one of the greatest players on the market... You obiviously do not know a thing and all you do is rage on xda.
(Huawei made some ofNEXUS devices also. Would Google let Nexus line to someone stupid?)
Maybe it's your first Cyanogen OS phone but I use CM already for 5 years (CyanogenMod). Huawei got 200 devices, Cyanogen 4-5 and no-cyanogen-phones get CM13 Cyanogen is just clean Android, nothing special like MIUI with ton of tools.
If you can't wait for updates just start building for yourself? So do I. That's one of the opportunities you have with our Zuk Z1. At least everything is working as it should with Cyanogen Mod on it. I had a lot of phones in the past which had Cyanogen Mod but a lot of features wasn't working anymore.
Klanac89 said:
Maybe it's your first Cyanogen OS phone but I use CM already for 5 years (CyanogenMod). Huawei got 200 devices, Cyanogen 4-5 and no-cyanogen-phones get CM13 Cyanogen is just clean Android, nothing special like MIUI with ton of tools.
Click to expand...
Click to collapse
CyanogenMod and CyanogenOS aren't same.
Also, they have scheduled it way before. There was already information when Cyanogen OS 13.1 is coming to this phone before you could buy it. So please just be careful and don't whine about update. Everyone would rather like good and stable update over some quick and buggy update. And only most of premium devices are getting update now , not this price range.
YoolaCro said:
CyanogenMod and CyanogenOS aren't same.
Also, they have scheduled it way before. There was already information when Cyanogen OS 13.1 is coming to this phone before you could buy it. So please just be careful and don't whine about update. Everyone would rather like good and stable update over some quick and buggy update. And only most of premium devices are getting update now , not this price range.
Click to expand...
Click to collapse
100% True.
To that guy that was talking without knowing anything:
CM13 was scheduled for ZUK Z1 way before i get it, and i get this device like one month ago, but they are working on it offline for sure. They prefer to get a fully working ROM to a device than give it a full buggy one. Me and @MrColdbird just could not wait more until they release their source, and i came from a nexus device (pretty sure you know that i downgraded from android 6.0 to 5.1.1 when swap devices), and we decided to work on 6.0 to give users an early experience of CM13, because we can't handle 5.1.1 anymore.
We made a almost full bringup of 6.0 devtree and kernel, and we made a port from a completely different CAF branch, in about 15 days, imagine in what time can CM do it, as they are maintaining this device. Even CM for Nexus Line and OPO (their big son), have bugs on SystemUI and other things, do you think they will even consider about making builds to another phones?
I think almost android users prefer a 100% working device with less features, than a device with newest Software and filled you bugs.
So are u still arguing?
If you don't like CM devices, just don't SPAM our threads like you have reasons to do so.
Go SPAM your device thread, and leave us alone.
Best Regards,
João Paulo
JoaoPaulo said:
100% True.
To that guy that was talking without knowing anything:
CM13 was scheduled for ZUK Z1 way before i get it, and i get this device like one month ago, but they are working on it offline for sure. They prefer to get a fully working ROM to a device than give it a full buggy one. Me and @MrColdbird just could not wait more until they release their source, and i came from a nexus device (pretty sure you know that i downgraded from android 6.0 to 5.1.1 when swap devices), and we decided to work on 6.0 to give users an early experience of CM13, because we can't handle 5.1.1 anymore.
We made a almost full bringup of 6.0 devtree and kernel, and we made a port from a completely different CAF branch, in about 15 days, imagine in what time can CM do it, as they are maintaining this device. Even CM for Nexus Line and OPO (their big son), have bugs on SystemUI and other things, do you think they will even consider about making builds to another phones?
I think almost android users prefer a 100% working device with less features, than a device with newest Software and filled you bugs.
So are u still arguing?
If you don't like CM devices, just don't SPAM our threads like you have reasons to do so.
Go SPAM your device thread, and leave us alone.
Best Regards,
João Paulo
Click to expand...
Click to collapse
Well said bro...we are waiting for your updates for the fingerprint, please never mind what others are saying we know you guys are doing a very good job for our ZUK Z1.
Ramshu97 said:
Well said bro...we are waiting for your updates for the fingerprint, please never mind what others are saying we know you guys are doing a very good job for our ZUK Z1.
Click to expand...
Click to collapse
Yes you have mentioned in detailed, hope he understood, while you preparing, pls consider the following things as my request,
1. Full screen caller dial, existing like in Cos 11
2.Camera like ZUI or Color OS camera which can use only in OPO & OPPO
---------- Post added at 01:17 PM ---------- Previous post was at 01:17 PM ----------
JoaoPaulo said:
100% True.
To that guy that was talking without knowing anything:
CM13 was scheduled for ZUK Z1 way before i get it, and i get this device like one month ago, but they are working on it offline for sure. They prefer to get a fully working ROM to a device than give it a full buggy one. Me and @MrColdbird just could not wait more until they release their source, and i came from a nexus device (pretty sure you know that i downgraded from android 6.0 to 5.1.1 when swap devices), and we decided to work on 6.0 to give users an early experience of CM13, because we can't handle 5.1.1 anymore.
We made a almost full bringup of 6.0 devtree and kernel, and we made a port from a completely different CAF branch, in about 15 days, imagine in what time can CM do it, as they are maintaining this device. Even CM for Nexus Line and OPO (their big son), have bugs on SystemUI and other things, do you think they will even consider about making builds to another phones?
I think almost android users prefer a 100% working device with less features, than a device with newest Software and filled you bugs.
So are u still arguing?
If you don't like CM devices, just don't SPAM our threads like you have reasons to do so.
Go SPAM your device thread, and leave us alone.
Best Regards,
João Paulo
Click to expand...
Click to collapse
Yes you have mentioned in detailed, hope he understood, while you preparing, pls consider the following things as my request,
1. Full screen caller dial, existing like in Cos 11
2.Camera like ZUI or Color OS camera which can use only in OPO & OPPO
Some news ?
Klanac89 said:
I think I will never buy again a Cyanogen OS phone. Cyanogen OS with MS crap and lame updates. Old S3 get CM13, ZUK Z1 still not get CyanogenMod 13 :/
Note 5 get Android 6, S6 get it and even Huawei roll Android 6 out... Huawei xD
Click to expand...
Click to collapse
I'm new to this Cyanogen/CM and don't know how Cyanogen updates their phones, but from their page at /support it doesn't look like any of their phones got version marshmallow. Are they reliable with updates? I'm wondering how long will Z1 be supported.
we will wait
i see right now all waiting 6.0 and cm 13
me too and im one from those dont know any thing about flashing but i thank u guys for ur work
and i wait the 6.0 for my zuk
and i want to be helpful
if u want any thing to do with my phone to test or somthing i will do
iam Arabian user for the cm 12.1 now
its very good
waiting ur updates soon as possible
If you are fine without a fingerprint reader for now then you can just run the unofficial CM13. JoaoPaulo will implement the fingerprint reader later in January.
Hey, I really would like to test your CM13 build. You wrote, that it is important to backup the persist-partition, if we want to change back to CM12.1. Can I do this with the 'partition backup & restore' app? And just restore the perisist partition after reflashing CM12.1? Or is it included, when I make nandroid-backup via TWRP? Thank you very much!
Gesendet von meinem Z1 mit Tapatalk
bjoerniko said:
Hey, I really would like to test your CM13 build. You wrote, that it is important to backup the persist-partition, if we want to change back to CM12.1. Can I do this with the 'partition backup & restore' app? And just restore the perisist partition after reflashing CM12.1? Or is it included, when I make nandroid-backup via TWRP? Thank you very much!
Gesendet von meinem Z1 mit Tapatalk
Click to expand...
Click to collapse
You can back it up in a root terminal via the following command.
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img
And no, it's not part of a nandroid backup. But yes, any mean of backing up and restoring partitions should (theoretically) work.
Although I'm not entirely sure that restoring the partition in a running Android OS is possible as the partition might be mounted at the time. Restoring it via fastboot or TWRP will work though.
After I've reat a lot of threads about the OnePlus 3T, it seems that CM13 for the OnePlus 3 isn't compatible to the OnePlus 3T. Unfortunately there don't even exists a correponding thread in the CM forum for the OnePlus 3T. Even more unfortunately - I've also reat, that the developers won't support the OnePlus 3T.
Is that true... ore just a bad joke?
rUmtifUsel said:
After I've reat a lot of threads about the OnePlus 3T, it seems that CM13 for the OnePlus 3 isn't compatible to the OnePlus 3T. Unfortunately there don't even exists a correponding thread in the CM forum for the OnePlus 3T. Even more unfortunately - I've also reat, that the developers won't support the OnePlus 3T.
Is that true... ore just a bad joke?
Click to expand...
Click to collapse
that was the only reason I bought 3T Maybe I should return this before my return period is over
Oh, come on...
Things take time.
Verstuurd vanaf mijn SM-T813 met Tapatalk
So, CM isn't compatible with a Snapdragon 821? Because that's the only real difference. I don't think so somehow.....it's more likely that some developers are resentful that OP discontinued the OP3 and started the OP3T and most developers bought a OP3, thus aren't buying a OP3T and make the small changes necessary to make ROMS work on OP3T?
So what about trying to do it yourself =)
Envoyé de mon Redmi Note 3 en utilisant Tapatalk
kamnikaz said:
So what about trying to do it yourself =)
Click to expand...
Click to collapse
I´m interested to learn but if cm needs to be built from scratch, that will be far away from my knowledge
http://forum.xda-developers.com/oneplus-3t/help/help-development-t3508892
I'm almost certain someone will build it at least since the Oneplus 3 is supported. Worst case I will build it myself. Got it to boot on the Huawei P8 so it shouldn't be too difficult for the 3T. I'm more interested in an AOSP build.
fisher6 said:
I'm almost certain someone will build it at least since the Oneplus 3 is supported. Worst case I will build it myself. Got it to boot on the Huawei P8 so it shouldn't be too difficult for the 3T. I'm more interested in an AOSP build.
Click to expand...
Click to collapse
I prefer Resurrection remix but cm is a very good start. Do you need to create all the drivers self or how does it work when the first build should be created?
Anyone already working on this? I thought about it, but it would be my first build... could be fun.
I think there are few things like sd 821 which make op3 cm doesn't work on op3t, it should be compatible mostly.
This should help: hxxps://wiki.cyanogenmod.org/w/Build_for_oneplus3 hxxps://wiki.cyanogenmod.org/w/Doc:_porting_intro
lindahl85 said:
I prefer Resurrection remix but cm is a very good start. Do you need to create all the drivers self or how does it work when the first build should be created?
Click to expand...
Click to collapse
As soon as the device and kernel trees are up RR will be officially supported
And personally. I don't think Source will release until nougat. Why would they release them with nougat less then a month away. Why would Devs spend the time making a rom when nougat is almost here.
If Oneplus 3T and 3 are mostly identical, then could all you really need for CM14.1 would be to edit the script in meta>google>android>script? or is CM not that simple?
c_86 said:
And personally. I don't think Source will release until nougat. Why would they release them with nougat less then a month away. Why would Devs spend the time making a rom when nougat is almost here.
Click to expand...
Click to collapse
That is an incredibly sage observation. If there are developers ready plug the CyanogenMod hole for the 3T (and I'm confident there's at least one or two), it'd be silly for them to plug it with CM13.1. The first CM build the 3T will see is likely 14.1.
If and when it does drop a month or two from now, I'll be abandoning OxygenOS immediately and permanently..
apascual89 said:
As soon as the device and kernel trees are up RR will be officially supported
Click to expand...
Click to collapse
They were already available ahead of launch ?
https://forums.oneplus.net/threads/...and-kernel-sources-for-the-oneplus-3t.473810/
apascual89 said:
As soon as the device and kernel trees are up RR will be officially supported
Click to expand...
Click to collapse
https://github.com/OnePlusOSS
Ivalicenyan said:
If Oneplus 3T and 3 are mostly identical, then could all you really need for CM14.1 would be to edit the script in meta>google>android>script? or is CM not that simple?
Click to expand...
Click to collapse
People, DON'T do this
Sent from my GT-S7580 using Tapatalk
I may have this wrong, but I was looking at CM ROMs over at the oneplus 3 forum (dev), and it appears that the first version of CM wasn't release for a little over 2 months from the release date of the oneplus 3. I wouldn't expect anything quicker over here (if anyone is trying). (well, someone is always trying).
I've built CM12 and 13 on various devices. There are guides all over the place that make it a matter of "process of elimination of errors" just to build, which can take from an hour to forever. (or a week) ; -- Getting it to boot is another thing entirely. You can get all of the useful blobs for the 3t even now from system.img (3.5.3) and build 3.5.3 based ROMs.
People are making the difference between 3t and 3 sound like a gaping chasm, when it's not very clear that there's a significant difference in instruction sets. Maybe the case is more than some developers don't want to support the 3t and all it's associated "problems". (some of those problems are just perceived problems). IF they just do the bare minimum and release 3t ROMs and Kernels then there'll be near chaos with a ton more people whining about something that doesn't work. Since the processor (and GPU) are different, then of course, that'll be a target for whiners that can't handle getting something for free and the few bugs that go with that. The thing that keeps me off of public development (these days) is how much crap I had to listen to while doing it ~3-10 years back.
I'm guessing a "fresh" set of people will do these next iterations of CM-NN.X coming along. Also, it would be somewhat "inspiring" if OnePlus would release those damn Camera sources (or even blobs).
white43 said:
So, CM isn't compatible with a Snapdragon 821? Because that's the only real difference. I don't think so somehow.....it's more likely that some developers are resentful that OP discontinued the OP3 and started the OP3T and most developers bought a OP3, thus aren't buying a OP3T and make the small changes necessary to make ROMS work on OP3T?
Click to expand...
Click to collapse
i'm a developer lel...i bought a oneplus3t and i think that port of a oneplus3 rom isn't too difficult, the snapdragon820 and the snapdragon821 are basically the same processor, the only difference is the clock.so..for the building the device tree is identic, what changes is the kernel and the vendor..for the kernel i can use the same patch that cm have used for the oneplus3 so probably i'll support the oneplus3t. My rom isn't a cm based but when we talk about kernels and vendors the rom don't make any difference.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
Ivalicenyan said:
If Oneplus 3T and 3 are mostly identical, then could all you really need for CM14.1 would be to edit the script in meta>google>android>script? or is CM not that simple?
Click to expand...
Click to collapse
ABSOLOUTLY NOT, DON'T DO THAT.
they are similar but not identic. there is motivation if the name is Oneplus3t and not oneplus3
---------- Post added at 09:00 PM ---------- Previous post was at 08:53 PM ----------
fisher6 said:
I'm almost certain someone will build it at least since the Oneplus 3 is supported. Worst case I will build it myself. Got it to boot on the Huawei P8 so it shouldn't be too difficult for the 3T. I'm more interested in an AOSP build.
Click to expand...
Click to collapse
trust me, if you want to port a nougat rom or any versione of android on a non-nexus or on a non-pixel device don't build aosp...build AOKP, DirtyUnicorns (they are aosp based but they have a lot of modifications for non-nexus devices) or at last cm, cm is caf and with a caf base you can try to port the rom but don't belive to make a completly functional rom, for now doesen't exist a nougat kernel for oneplus3t so..if you succesfully build the cm probably will not boot or you could have many other problems.
MasterJack1697 said:
i'm a developer lel...i bought a oneplus3t and i think that port of a oneplus3 rom isn't too difficult, the snapdragon820 and the snapdragon821 are basically the same processor, the only difference is the clock.so..for the building the device tree is identic, what changes is the kernel and the vendor..for the kernel i can use the same patch that cm have used for the oneplus3 so probably i'll support the oneplus3t. My rom isn't a cm based but when we talk about kernels and vendors the rom don't make any difference.
Click to expand...
Click to collapse
Can you build cm for OP3T? That would be great! OP btw released the kernel and device tree for OP3T:
https://forums.oneplus.net/threads/...and-kernel-sources-for-the-oneplus-3t.473810/
Hi
I was just wondering after release of AOSP Sources , how long it wipp take for stable build of android o for oneplus 3T
after the release of android z
It may be a few months, may be next year. Nobody knows at this point. Official OOS 8.0 Release will be in a few months so a custom rom release could also be around that time
Mizart said:
It may be a few months, may be next year. Nobody knows at this point. Official OOS 8.0 Release will be in a few months so a custom rom release could also be around that time
Click to expand...
Click to collapse
Why do we need oos to push out 8.0 for us to get it with custom ROMs? Thought custom ROMs can be somewhat 'ported' over from some devices or built from the open sources? I was also wondering the same as op, but didn't expect it to take that long. Hopefully it will be sooner than later
SourPower said:
Why do we need oos to push out 8.0 for us to get it with custom ROMs? Thought custom ROMs can be somewhat 'ported' over from some devices or built from the open sources? I was also wondering the same as op, but didn't expect it to take that long. Hopefully it will be sooner than later
Click to expand...
Click to collapse
I wasn't implying we need to wait for OOS. I was merely stating if OOS is gonna take a few months, Custom Devs might as well. But i do hope I'm wrong. I think either RR or PA would be the first to take it up.
When Android M and N were was released, we started getting custom roms within 1~2 months on OP2. Should be fast than this on OP3T.
Mizart said:
I wasn't implying we need to wait for OOS. I was merely stating if OOS is gonna take a few months, Custom Devs might as well. But i do hope I'm wrong. I think either RR or PA would be the first to take it up.
Click to expand...
Click to collapse
RR is based on LineageOS, so that's not gonna happen unless the source updates first.
PA has limited resources meaning it could take a while for them too.
I'm guessing it's gonna be a random dude with an AOSP port with the first alpha in about 3 weeks. Just a guess, so don't count on it.
https://www.xda-developers.com/android-oreo-xiaomi-mi-3-mi-4/
ast00 said:
RR is based on LineageOS, so that's not gonna happen unless the source updates first.
PA has limited resources meaning it could take a while for them too.
I'm guessing it's gonna be a random dude with an AOSP port with the first alpha in about 3 weeks. Just a guess, so don't count on it.
Click to expand...
Click to collapse
+1
Just a question for the future. Are there custom roms like Lineage OS coming for Mi 11 Ultra?
Probably just a matter of time....
It's available for most of the earlier devices already: https://www.cyanogenmods.org/lineageos-18-mi-10-pro/
I don't think it will show up anytime soon...
When I got MiNote10, it was one of few phones with new 108MP camera sensor, developers had bad time trying to find drivers, or do anything to be able to use camera, as Xiaomi release only part of source code for this phone. As for now, there is no official LOS for MiNote10, just UNOFFICIAL, and the phone was released around November 2019 ?
MI11 Ultra also have new camera sensor GN2, display on the back, new chipset, I wish to see LOS or other custom ROM, but I know how hard is to build custom ROM for new hardware if you don't have drivers/source code.. Only hope in Xiaomi if they release complete source code needed to build ROM.
We'll have to wait for the popularity of this phone to go up first. Might take a while. But with miui12.5 being the crap fest that it is right now... I hope we don't have to wait too long for an aosp based ROM to come out
I would voluteer for testing... anything is better than this miui crap. So, anyone, please DM me, if you need a tester.
And put TWRP on the list. I might suffer from a good old fashioned paranoia, but kind if don't trust the current distributions of TWRP for the MI11U.
Hi.
LineageOS 20 is now officially released, but I can't find it for Sony Xperia XZ1c.
Does anyone know where it can be downloaded?
Thanks
There isn't official Los 20 for the XZ1c, but you have the unofficial version by derfelot. It works the same as the official versions for other devices, the only differences being the lack of OTA updates and the time between updates varies. I think we're getting an update to the Los20 rom soon, since I see commits submitted in github.
Hi,
I've installed the previous unofficial version on my XZ1c, and am looking forward to the mentionned unofficial LOS20 update before I install it (I didn't see it was already available at the time I installed 19 in december). I have a question, not too silly I hope :
I've read on LineageOS website that if some developers have a running and reliable LOS version developed for a device that is not yet officially supported, they can submit their version so that then the version becomes "official" and one can get it from LOS website. Is it planned with this unofficial LOS version ? why / why not ?
Thanks
I think It's not official because the devs don't want to involve/don't have the time to become official maintainers, instead releasing updates less frequently. Basically It's a responsibility. That's what I think and personally I'm fine with the unofficial builds, these devs do a lot already.
So in theory, If someone has the skills/time to maintain this device officially, It could become one without an issue.
Let me ask another question (since this is new post):
Which of available ROMs suits You all best and why?
I Was on Havoc 4, then 5, Lineage 17, now I'm back to Havoc 3.11 but this one gets random freezes and battery heats up. Only issue I have with new releases is lack of Android Auto support.
maarek7 said:
Let me ask another question (since this is new post):
Which of available ROMs suits You all best and why?
I Was on Havoc 4, then 5, Lineage 17, now I'm back to Havoc 3.11 but this one gets random freezes and battery heats up. Only issue I have with new releases is lack of Android Auto support.
Click to expand...
Click to collapse
Hi, I don't have an answer to your question since so far I've tested only lineage 19. But I'd like to ask you why you chose to go back to Havoc 3.11 even though it heats and freezes ? (Why not a more recent ?)
And what are the differences between Havoc and LOS in everyday use, what did you personnally notice / prefer ?
Arcline said:
I think It's not official because the devs don't want to involve/don't have the time to become official maintainers, instead releasing updates less frequently. Basically It's a responsibility. That's what I think and personally I'm fine with the unofficial builds, these devs do a lot already.
So in theory, If someone has the skills/time to maintain this device officially, It could become one without an issue.
Click to expand...
Click to collapse
Ok, indeed it would add more work/responsibility to the developpers.
eve1374 said:
Hi, I don't have an answer to your question since so far I've tested only lineage 19. But I'd like to ask you why you chose to go back to Havoc 3.11 even though it heats and freezes ? (Why not a more recent ?)
And what are the differences between Havoc and LOS in everyday use, what did you personnally notice / prefer ?
Click to expand...
Click to collapse
Hi,
I wanted to try and test Android Auto mostly to be honest.
As per differences - Havoc gives You way more options to customize whole phone (appearance), have more features (gestures, status bar, dock etc., you might even forget half of the settings after finishing configuring it), Lineage on the other hand I believe consumes less battery, appears to be quicker, is neat.
But I've tried either Havoc and Lineage on Android 12 and both works smooth. Testing Lineage 20 currently and can't say any bad word. But I'm kind of lucky with custom ROMs, never had any major issues, all worked fine always