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/
This a a port of an amazing Rom by Parth111999, Radioactive V1. Please go to his post here [url]https://forum.xda-developers.com/galaxy-j7/development/rom-t3713641[/URL] and give him a thanks. I will post some screenshots when I have a chance, but if you go to the link above, you can see the screenshots there as this is a full port of his rom. Mr.Duck254 has compiled one of the best kernels I have ever seen, this battery with said kernel is by far the best this device has ever seen. Also, BOLO. He has some monsters of Roms on the horizon, he is the man when it comes to this device as personally development on the US J7 had grown stale. Now, we are invigorated with new gusto and development has and will continue to grow in strides equal to that of the international J7 community. So thanks to those devs over there as well. This rom has it all, and no blue light filter will never work cuz of the hardware of the device.
Install instructions
Put all required files on external SD card
it should be the rom, oreo beta edge zip, systemless root of your choice, then the encryption breaker.
Next you should boot to recovery, wipe everything but internal and external storage.
Then flash the rom, edge, root, and encryption breaker.
the awesome boot logo will start and then turn off its normal with root, then the second time around the watchdogs animation will start and boot takes about ten mins. Setup your phone and enjoy.
Radioactive V1 Rom
[url]https://drive.google.com/open?id=1y54U-yEE60hBO9v3yLNe2VJu44jL8JN-[/URL]
Oreo Beta Edge Zip
[url]https://drive.google.com/open?id=1JApkXxLU1OgdwusM1HuA2zqbG5sgMvBL[/URL]
Bugs-
Only two, at boot it will say edge screen stops, click close and carry on.
app linking on app edge causes a force close, its a oreo feature so just not compatible with Nougat
Anything else? Please let me know.
XDA:DevDB Information
[ROM][N]Radioactive V1 Port By FullOfHell & Mr.Duck254, ROM for the Samsung Galaxy J7
Contributors
fullofhell, fullofhell, mr.duck254, parth111999
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Nougat Update
Based On: Touchwiz
Version Information
Status: Stable
Current Stable Version: 2017-12-08
Stable Release Date: 2017-12-08
Created 2017-12-08
Last Updated 2017-12-08
Thank you brother! We're not worthy
The best work you've done really congratulates the three good ROM
carlosbalbuena_ said:
The best work you've done really congratulates the three good ROM
Click to expand...
Click to collapse
Thank you Carlos! I tried thanking u but all out of thx!
I am taking a poll what roms would u guys like to have ported and built?
Hello bro, I do not know if you have noticed but when placing one of the blocking methods when trying to unlock it has a delay of 10 seconds you think it can be fixed
carlosbalbuena_ said:
Hello bro, I do not know if you have noticed but when placing one of the blocking methods when trying to unlock it has a delay of 10 seconds you think it can be fixed
Click to expand...
Click to collapse
No, it cannot it is like that with nougat. Im not sure if you noticed but its with every nougat build. Android fixed that problem with 8.0 best advice is after you type pin hit recents then recents again it should make it quicker. I noticed it first when we got the 7.1.1 update.
fullofhell said:
No, it cannot it is like that with nougat. Im not sure if you noticed but its with every nougat build. Android fixed that problem with 8.0 best advice is after you type pin hit recents then recents again it should make it quicker. I noticed it first when we got the 7.1.1 update.
Click to expand...
Click to collapse
then you tell me that is a failure next in all ROMs nougat.
I said that cuz it is a major glitch and if u don't believe me don't ask me. I have no reason to make it up. Go flash stock and try it . It does the same thing. I'm running revolution right now and it does it on this.i finally ported fast rom it does it on that. I ported on8v2 and it does it there. It does it on nova. It's a nougat bug. Hitting recent kills the delay.
So in other news I did find a way for blue light. With our next rom it's working
fullofhell said:
I said that cuz it is a major glitch and if u don't believe me don't ask me. I have no reason to make it up. Go flash stock and try it . It does the same thing. I'm running revolution right now and it does it on this.i finally ported fast rom it does it on that. I ported on8v2 and it does it there. It does it on nova. It's a nougat bug. Hitting recent kills the delay.
Click to expand...
Click to collapse
I think you did not realize my question or the translator did not work well, but in this error in stock, it never occurred to me only now that I tried this ROM, I just ask if the error is found in all ROM nougat these models that was my question
carlosbalbuena_ said:
I think you did not realize my question or the translator did not work well, but in this error in stock, it never occurred to me only now that I tried this ROM, I just ask if the error is found in all ROM nougat these models that was my question
Click to expand...
Click to collapse
Sorry man I didn't realize you used a translator. Yes it is in stock and I have not found a nougat rom that doesn't have this bug. My apologies. Wait till you see what is to come.
fullofhell said:
Sorry man I didn't realize you used a translator. Yes it is in stock and I have not found a nougat rom that doesn't have this bug. My apologies. Wait till you see what is to come.
Click to expand...
Click to collapse
ok bro luck with the other rom
fullofhell said:
I am taking a poll what roms would u guys like to have ported and built?
Click to expand...
Click to collapse
Hello friend. Since you are asking, is there any way you could port either
[ROM][7.0][J7 2015 Exynos] Revolution OS v5.0.1
-- OR --
[ROM][7.0][J7 2015] Xperience OS v2.5
Thanks for all your hard work here, and for pointing me over here to the correct sub forum
Thibor69 said:
Hello friend. Since you are asking, is there any way you could port either
[ROM][7.0][J7 2015 Exynos] Revolution OS v5.0.1
-- OR --
[ROM][7.0][J7 2015] Xperience OS v2.5
Thanks for all your hard work here, and for pointing me over here to the correct sub forum
Click to expand...
Click to collapse
Yes we are working on them
I really like Dr Ketan's rom for the note 4 and note edge, he was up to nougat when I lost my note edge. Idk if he's still building these ROMs or if he would let you port. He seemed a little protective of his work... Just an idea though
Though I doubt you can do anything with Dr Ketan's rom. Is really like to see an AOSP based ROM...maybe resurrection remix, oxygen os, nitrogen os, dirty unicorn, etc....something pure Android or very close
fullofhell said:
Yes we are working on them
Click to expand...
Click to collapse
AWESOME !!! Let me know if you need any testers....
Peace
fullofhell said:
I am taking a poll what roms would u guys like to have ported and built?
Click to expand...
Click to collapse
Would it be possible to have a AOSP build ? I understand we do not have a AOSP base, so technically wouldn't be a " port " .
[ROM][7.0][NOTE 8 Ux][STABLE][BUILD 2.0][GENISYS XPERIENCE ROM]
Click to expand...
Click to collapse
[ROM][BUILD 5.0][NN][FAST_ROM_NOUGAT][Galaxy J7 15][STABLE][LATEST**]
Click to expand...
Click to collapse
Thanks for the release
hightech316 said:
Would it be possible to have a AOSP build ? I understand we do not have a AOSP base, so technically wouldn't be a " port " .
Thanks for the release
Click to expand...
Click to collapse
We will try soon as we have a device tree
Guys does anyone know when we will get the official pie ? For g6
spreet said:
Guys does anyone know when we will get the official pie ? For g6
Click to expand...
Click to collapse
whenever they start doing soak test and they haven't started it yet but that should start soon. More than likely early 2019
ninjakira said:
whenever they start doing soak test and they haven't started it yet. More than likely early 2019.
Click to expand...
Click to collapse
Do we have a stable gsi rom ??
spreet said:
Do we have a stable gsi rom ??
Click to expand...
Click to collapse
I mean there's really no such thing as stable when it comes to gsi roms unless there specifically built for the device like the stock roms and official builds of custom roms like lineage and RR. You can technically flash any gsi rom but there is a strong chance of device related issues. some gsi images work better than others. There's fixes for some issues but I myself don't know em because Im not on a gsi image
ninjakira said:
I mean there's really no such thing as stable when it comes to gsi roms unless there specifically built for the device like the stock roms and official builds of custom roms like lineage and RR. You can technically flash any gsi rom but there is a strong chance of device related issues. some gsi images work better than others. There's fixes for some issues but I myself don't know em because Im not on a gsi image
Click to expand...
Click to collapse
Are you on stock ??
I'd assume it would be soon because the Moto x4 just got the Pie beta. That phone came out not long before this one.
spreet said:
Do we have a stable gsi rom ??
Click to expand...
Click to collapse
Not really, most of them won't even boot. I'm hoping 9.0 drops by the new year for our G6.
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
Bluemgt06 said:
I'd assume it would be soon because the Moto x4 just got the Pie beta. That phone came out not long before this one.
Click to expand...
Click to collapse
The x4 has been out for well over a year now. There's quite a gap between it and the g6 series.
Wait around one year or so for the update to 9.0... Motorola/Lenovo has ruined the updates so I have lost the hope in this company ...
fix-this! said:
Not really, most of them won't even boot. I'm hoping 9.0 drops by the new year for our G6.
Click to expand...
Click to collapse
All of the arm/A roms including unofficial pixel experience and aosp by phh boot fine. Only problems I've found are no hotspot and Bluetooth and notification ringtones sounding garbled. There is a fix that requires deleting a folder from your vendor for the last two problems
Rapid OS 8.0 for Redmi Note 3 Pro [kenzo/kate]
What is AOSP ROM?
An AOSP ROM is a ROM based on the Android Open Source Project. In the purest sense, AOSP refers to unmodified ROMs or code from Google
About Rapid OS:
Rapid OS is a pure stock android experience, much like the pixel devices, with a lot of under the hood tweaks, which optimize the specific device to unleash it's fullest capability, be it in terms of performance, battery, or stability.
It does not come with any bloatware at all, and comes only with the apps you'd find on a pixel.
Code:
#include
/*
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth (buggy sometimes)
FMRadio (buggy sometimes)
FPC Fingerprint
Lights
Sound / vibration
IR
Known issues
Goodix fingerprint
Extras
Pixel colors
Pixel Launcher
INBUILT GAPPS
GCAM
Backlight on hardware keys
Credits
Thanks to all who have helped me (directly or indirectly), especially to these guys: @xyyx, @billchen1977,@akhilnarang, @GreekDragon, @abhishek987, @ jhenrique09 (Based on his aosp rom only).
@ jhenrique09 AOSP 8.0 for kenzo: https://forum.xda-developers.com/redmi-note-3/development/rom-aosp-oreo-t3664605
Disable HWKeys and enable navbar (don't install in another ROM, because it will not work):
https://www.androidfilehost.com/?fid=889764386195926971
SOURCE: (Built upon @jhenrique09 AOSP 8.0 for kenzo/kate: https://forum.xda-developers.com/redmi-note-3/development/rom-aosp-oreo-t3664605).
Pls post logs of any bugs that you may have!
NOTE: I'm Currently working on android pie based Rapid OS. Pls support the development guys!!
XDA:DevDB Information
Rapid OS, ROM for the Xiaomi Redmi Note 3
Contributors
shivaay1234
Source Code: https://forum.xda-developers.com/redmi-note-3/development/rom-aosp-oreo-t3664605
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest TWRP and firmware, Unlocked bootloader
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-11-07
Created 2019-11-07
Last Updated 2019-11-07
Links
Sorry for the delay in uploading the links. They'll be up right here, in about an hour.
EDIT: Links updated!
https://drive.google.com/drive/folders/1-0FycnVRg68vtjcXQC1U_xOvUuHFIoMk?usp=sharing
Download the rom and the bootfix from the above link.
FLASH INSTRUCTIONS:
1) Wipe system, data, cache, dalvik cache.
2) Flash the ROM zip only (Don't add anything to the queue).
3) Flash the BOOTFIX.
4) Don't flash GAPPS (it's already there).
5) Reboot and enjoy!!!
NOTE: The rom takes quite a while to install, so please be patient.
Wow, tried this rom. It's really epic. Just the best balance between performance, battery and stability. I want you to make the pie rom. Please continue the hard work. Your rom makes my device feel new. The scrolling in this rom is just insane! Feels like a oc'd display! Thanks for the great work mate.
---------- Post added at 12:05 PM ---------- Previous post was at 11:59 AM ----------
This is what "stock" means. Many guys give their roms saying it's "stock", but have all sorts of customisations and ****. But this one has none of those, and i love it. Pure stock android makes my device feel like a pure pixel. Thanks again dev
EDIT: This rom comes with gcam as the stock camera app, and it is just lit??
Will wait for pie version. Can someone please provide screen shots? Thanks again for keeping this device alive. XD
Soojikahalwa said:
Will wait for pie version. Can someone please provide screen shots? Thanks again for keeping this device alive. XD
Click to expand...
Click to collapse
The model number says SM-G955F, Cuz i installed the vulkan activator on my device too. The rom is epic man. I think you should give it a try even though it's Oreo.
will wait on pie
---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------
Will wait on pie
Divyeshj66 said:
The model number says SM-G955F, Cuz i installed the vulkan activator on my device too. The rom is epic man. I think you should give it a try even though it's Oreo.
Click to expand...
Click to collapse
Why's the security patch so old?
Soojikahalwa said:
Why's the security patch so old?
Click to expand...
Click to collapse
It's the initial build of not only oreo, but rapid OS, so didn't think about that. Sorry. Anyway, the future builds, and the pie build will come with the latest security patch. Did you like the ROM though?
shivaay1234 said:
It's the initial build of not only oreo, but rapid OS, so didn't think about that. Sorry. Anyway, the future builds, and the pie build will come with the latest security patch. Did you like the ROM though?
Click to expand...
Click to collapse
This is the best. Loved it. Gonna keep using it until the pie version releases. Please make it happen.
anyone using this for 2gb / 16gb kenzo? review please
Divyeshj66 said:
The model number says SM-G955F, Cuz i installed the vulkan activator on my device too. The rom is epic man. I think you should give it a try even though it's Oreo.
Click to expand...
Click to collapse
2017 Security Patch? Whoat
Ya_SG said:
2017 Security Patch? Whoat
Click to expand...
Click to collapse
Dude, if you want to use it use it, else leave. I already said why this happened
Android 10
Are you guys fine, if I stop work on the pie based ROM, in order to get the 10 based ROM faster? I can only work on one of them...
shivaay1234 said:
Are you guys fine, if I stop work on the pie based ROM, in order to get the 10 based ROM faster? I can only work on one of them...
Click to expand...
Click to collapse
I would rather like to get Android 10 as there are several Pie ROMs already.
shivaay1234 said:
Are you guys fine, if I stop work on the pie based ROM, in order to get the 10 based ROM faster? I can only work on one of them...
Click to expand...
Click to collapse
Go toward 10
shivaay1234 said:
It's the initial build of not only oreo, but rapid OS, so didn't think about that. Sorry. Anyway, the future builds, and the pie build will come with the latest security patch. Did you like the ROM though?
Click to expand...
Click to collapse
Please don't be sorry buddy, thanks for keeping the device alive. I was just wondering why the patch is old as seen from the screenshot. I don't have a clue about developing. I was just curious. I appreciate you doing this for our redmi note 3. I have just shifted to Aex pie by Amol Amrit. Will try this out after a while, I'll let you know what I think about the ROM when I do. Thanks again.
Android 10 development
Hi guys. As requested by many people, I have started working on the 10 build. It might take a while to fix all the bugs. If you guys just want to test out the builds and are fine with the bugs, you can PM me. The test builds will be available from next-week hopefully. Thanks for the support guys:good::good:
codergenius said:
anyone using this for 2gb / 16gb kenzo? review please
Click to expand...
Click to collapse
Yes buddy, I'm using it on my 2gb ram variant of kenzo. Runs really well ram management is much better than the pie ROMs. And since it is absolutely pure android, with pixel goodies, I love it...
---------- Post added at 12:31 PM ---------- Previous post was at 12:31 PM ----------
shivaay1234 said:
Hi guys. As requested by many people, I have started working on the 10 build. It might take a while to fix all the bugs. If you guys just want to test out the builds and are fine with the bugs, you can PM me. The test builds will be available from next-week hopefully. Thanks for the support guys:good::good:
Click to expand...
Click to collapse
Thanks bro. We'll keep supporting you??
shivaay1234 said:
Hi guys. As requested by many people, I have started working on the 10 build. It might take a while to fix all the bugs. If you guys just want to test out the builds and are fine with the bugs, you can PM me. The test builds will be available from next-week hopefully. Thanks for the support guys:good::good:
Click to expand...
Click to collapse
But you can make a telegram group instead and post the beta builds there, so that people can test the builds and help you isolate the bugs.
Ya_SG said:
But you can make a telegram group instead and post the beta builds there, so that people can test the builds and help you isolate the bugs.
Click to expand...
Click to collapse
K. will do that.