I have some experience flashing ROMS, rooting, and so forth. All the ROMS I have flashed thus far have all been condensed into one zip that I download and flash via safestrap. I am wanting to try out some different ROMS and was wondering if there is a general rule of thumb when the download link leads me to a page of nightlys? I have noticed that most ROMS are around 2 gigs and the file sizes for some of these files are very small. Should I download/flash all of the zips? The newest zip? etc... any help and advice would be greatly appreciated and thank you in advance.
liljoe727 said:
I have some experience flashing ROMS, rooting, and so forth. All the ROMS I have flashed thus far have all been condensed into one zip that I download and flash via safestrap. I am wanting to try out some different ROMS and was wondering if there is a general rule of thumb when the download link leads me to a page of nightlys? I have noticed that most ROMS are around 2 gigs and the file sizes for some of these files are very small. Should I download/flash all of the zips? The newest zip? etc... any help and advice would be greatly appreciated and thank you in advance.
Click to expand...
Click to collapse
Well first get a link to the download page you're looking at and I'll tell you what you're options are. Thing is, I've never seen a nightly built ROM that wasn't aosp, but if the builds you're looking at are really 2+ gbs then it definitely isn't aosp.
joshm.1219 said:
Well first get a link to the download page you're looking at and I'll tell you what you're options are. Thing is, I've never seen a nightly built ROM that wasn't aosp, but if the builds you're looking at are really 2+ gbs then it definitely isn't aosp.
Click to expand...
Click to collapse
This is the thread to the ROM http://forum.xda-developers.com/showthread.php?t=2630094
And the thread to the download link http://www.drdevs.com/devs/teamliquid/Nightly/S4_Unified/
It is an AOSP ROM and not compatible with my S4 and I am not wanting to flash on my phone, just looking to understand the AOSP flashing process a bit more as I am looking into other devices. i suppose I could have put all this in my original post and will try to suck less next time. lol.
liljoe727 said:
This is the thread to the ROM http://forum.xda-developers.com/showthread.php?t=2630094
And the thread to the download link http://www.drdevs.com/devs/teamliquid/Nightly/S4_Unified/
It is an AOSP ROM and not compatible with my S4 and I am not wanting to flash on my phone, just looking to understand the AOSP flashing process a bit more as I am looking into other devices. i suppose I could have put all this in my original post and will try to suck less next time. lol.
Click to expand...
Click to collapse
Okay yeah so those are all ~200mb, which is typical for aosp, a gb is a 1,000mb. The other files are just MD5 sums (used to check if your file downloaded correctly) and the text files are changelogs.
Generally when figuring out what to download, it depends on what you want and researching the associated thread. If you're looking to experiment or want to try a brand new feature, download the latest and see how it works. If you want something a little more stable, read the thread and see what nightly is working best for anybody. If you're looking for a daily driver, stick to a weekly or "milestone" build.
joshm.1219 said:
Okay yeah so those are all ~200mb, which is typical for aosp, a gb is a 1,000mb. The other files are just MD5 sums (used to check if your file downloaded correctly) and the text files are changelogs.
Generally when figuring out what to download, it depends on what you want and researching the associated thread. If you're looking to experiment or want to try a brand new feature, download the latest and see how it works. If you want something a little more stable, read the thread and see what nightly is working best for anybody. If you're looking for a daily driver, stick to a weekly or "milestone" build.
Click to expand...
Click to collapse
So, each of those zips that is around 200 megs is a "different version" of the same ROM, so to speak? And when something is changed, it becomes a new "nightly"? Generally speaking, there would only be small differences between the nightlys and that will be evidenced in the changelogs?
For example, Hyperdrive, when it gets released is a "milestone build", the proven AOSP ROMS such as an older version of CM, for example, would also be an example of a milestone build. The nightlys that are available under CM are little tweaks and changes that have been made to the newest version of CM? Is this about right?
liljoe727 said:
So, each of those zips that is around 200 megs is a "different version" of the same ROM, so to speak? And when something is changed, it becomes a new "nightly"? Generally speaking, there would only be small differences between the nightlys and that will be evidenced in the changelogs?
For example, Hyperdrive, when it gets released is a "milestone build", the proven AOSP ROMS such as an older version of CM, for example, would also be an example of a milestone build. The nightlys that are available under CM are little tweaks and changes that have been made to the newest version of CM? Is this about right?
Click to expand...
Click to collapse
Yes, each zip is an update from the last zip. The updates will be spelled out in the changelogs. And yes you're right, I'll just clarify a bit.
Hyperdrive, as well as every other ROM based on an OEM-skin (such as Touchwiz or HTC Sense), does not follow the release cycles of AOSP ROM's. AOSP ROM's are generally created by a big team of developers, then people called "maintainers" adapt the ROM to their specific device (EX: invisiblek is the official maintainer of CM for our phone). They release their ROM on a nightly basis because they have a lot of people working on it and a lot of issues to solve supporting so many devices. For example, when CM wants to add a new feature, they know that it needs to work on over a thousand different android phones, so they put it out in the nightlies to test it. Once it's truly stable on all devices, it's added to the milestone build.
Now these TW-based ROM's are different. It's typically one developer supporting one or a few devices. There's no typical release schedule, but most developers seem to update either monthly, based on firmware updates, or based on Android version updates. With only a few devices to support, these ROM's don't usually have too many issues that would need to be solved through a nightly nor do they usually have enough developers to support a nightly program.
Related
THREAD DEPRECATED! project moved here:
http://forum.xda-developers.com/goo...om-openpdroid-patched-cyanogenmod-11-t2817655
----------------------------
title is self explanatory. I'll share my builds in case others are interested.
please look for them here:
THREAD DEPRECATED!
EDIT:
information in the edit below is not longer current. please see:
http://forum.xda-developers.com/showpost.php?p=52664423&postcount=5
EDIT:
additional information as requested by moderator:
this is just a build of master branch cyanogenmod for hammerhead patched with the latest openpdroid patches as available on openpdroid's github (https://github.com/OpenPDroid/OpenPDroidPatches). not a single line of code was changed, as the source level patches still apply without errors.
it used to be the case that auto-patcher could smali-patch binary android builds. now auto-patcher has gone unmaintained and smali patches no longer apply on recent builds of cyanogenmod.
many people are not willing to build from source and are abandoning openpdroid. i will continue to use it on kit-kat at least. these are my builds and are shared here as a convenience for hammerhead users who do not want to build their own OS. no changes were introduced. source code is available on the respective project githubs.
NOTE: uploads are in progress, please check later.
new build (currently uploading to the dropbox link)
new build (currently uploading to the dropbox link)
this one cherry picks this:
http://review.cyanogenmod.org/#/c/62281/
to support 5x5 grid size in the home screen.
new build (currently uploading to the dropbox link)
CM11-M6 broke OpenPDroid patch compatibility. i forked OPD to restore compatibility, fix several bugs and clean up the code. sources here:
https://github.com/Lanchon/OpenPDroid-patches
cherry picks this (patchset 6) to support 5x5 grid size in the home screen:
http://review.cyanogenmod.org/#/c/62281/
Is it Art compatible ?
yuuzhantar said:
Is it Art compatible ?
Click to expand...
Click to collapse
Dude,
OP's built CM11 from source with the added OpenPDroid patches. The ROM that he's linked to us is just CM11 with OpenPDroid.
Your question should be: "Does CM11 allow you to select different runtimes?".
The answer to that question is: "Yes, this option is located under 'Developer Options'.".
If you next question is: "How do I access 'Developer Options'?", then look here: http://www.youtube.com/watch?v=XcFVRDZ5Z9Q.
LewisD94 said:
Dude,
OP's built CM11 from source with the added OpenPDroid patches. The ROM that he's linked to us is just CM11 with OpenPDroid.
Your question should be: "Does CM11 allow you to select different runtimes?".
The answer to that question is: "Yes, this option is located under 'Developer Options'.".
If you next question is: "How do I access 'Developer Options'?", then look here: http://www.youtube.com/watch?v=XcFVRDZ5Z9Q.
Click to expand...
Click to collapse
Dude,
last time we had informations about pdroid, it was "not compatible with art"
http://forum.xda-developers.com/showpost.php?p=47902311&postcount=3796
As we don't know if it's because of the smali patching process or anything else,
I asked to know if a rom build with openpdroid included in the source was Art compatible.
And if I ask about Art, likerly I know how to use it (it switched since 4.4 was released ... )
Anyway, I'm done with CM, I switched to Omni this week-end after my phone became unusable, corruption of system data
yuuzhantar said:
Dude,
last time we had informations about pdroid, it was "not compatible with art"
http://forum.xda-developers.com/showpost.php?p=47902311&postcount=3796
As we don't know if it's because of the smali patching process or anything else,
I asked to know if a rom build with openpdroid included in the source was Art compatible.
And if I ask about Art, likerly I know how to use it (it switched since 4.4 was released ... )
Anyway, I'm done with CM, I switched to Omni this week-end after my phone became unusable, corruption of system data
Click to expand...
Click to collapse
you should try making your own rom before you bad mouth another.
flex360 said:
you should try making your own rom before you bad mouth another.
Click to expand...
Click to collapse
What business is it of yours?
I just sayed that I stop using cm after it crashed
Great to have someone building CM11 with openpdroid! Can't thank you enough!!!
Just one question:
Which kernel works best with this CM11? Any bad experiences?
Gesendet von meinem Nexus 5 mit Tapatalk 2
new build!
EDIT: this build is now based on android 4.4.4. remember to UPDATE YOUR GAPPS, or else...
sorry for the delay. i took off to europe to try out something with someone i met last year... it was a good bet that didnt work
but im back!!!
this build includes the custom home screen grid size selection that was merged into master recently, and so the old cherry pick slash hack (http://review.cyanogenmod.org/#/c/62281/) is gone for good.
NOTE: the update WILL NOT import your home screens beyond the upper left 4x4 area. so if you were using the previous cherry pick to increase the grid size, make sure you reshuffle the icons and widgets to the upper left 4x4 subset of each screen. anything outside that area will be lost. after the update you can increase the grid again and reshuffle back to your liking.
yuuzhantar said:
Is it Art compatible ?
Click to expand...
Click to collapse
all OPD changes are at the java/dalvik level, which makes me suspect that this build is as ART compatible as standard CM. that said, i've never used ART.
schwarzlichtkind said:
Which kernel works best with this CM11? Any bad experiences?
Click to expand...
Click to collapse
any kernel that works well with CM standard should work as well with this build.
@Lanchon
Are you getting com.android.phone has stopped messages upon first boot? I have tried full wipe, flashing different kernels, different gapps packages, etc to no avail. I am installing as secondary ROM with MultiROM by the way. Your previous build (M6 I think) installs this way with no issues.
Thanks so much for keeping pdroid alive!
stone_ship said:
@Lanchon
Are you getting com.android.phone has stopped messages upon first boot? I have tried full wipe, flashing different kernels, different gapps packages, etc to no avail. I am installing as secondary ROM with MultiROM by the way. Your previous build (M6 I think) installs this way with no issues.
Thanks so much for keeping pdroid alive!
Click to expand...
Click to collapse
i havent done a clean install since i dont know when!! nor have i used multirom. im using BaNkS gapps minimal with some add-ons and i dont experience a hitch. note that you need 4.4.4 gapps for this rom. recommend you format the system partition (if it makes sense with multirom) before flashing rom and gapps. then wipe cache and dalvik.
new build uploaded!
i will also be building for the i9100; first build is uploading now...
THREAD DEPRECATED! project moved here:
http://forum.xda-developers.com/goo...om-openpdroid-patched-cyanogenmod-11-t2817655
So after years of flashing ROMs and kernels and owning so many android devices, some may call me crazy, I've finally decided to make a ROM for myself and share it with the public on XDA!
This ROM is all about simplicity, lightweight, being equipped with the right software, no crashes, speed, a nice minimal default theme, yadda yadda yadda.
I'll be posting nightly releases until I get everything just right, in the meantime hopefully by sharing these builds, I can get some feedback from you guys.
What works? Everything. What doesn't work? Nada.
Screenshots available in the screenshots section (link above post)
Latest Release: 1.0.2 - DOWNLOAD LINK
https://www.androidfilehost.com/?w=files&flid=30025
Make sure to flash SuperSU afterwards if you would like root.
Comes with ZenKernelv17 boot.img built-in, and I *highly", recommend you leave it at that.
Check the ZenKernel thread for updates:
http://forum.xda-developers.com/nexus-6/orig-development/3-10-zen1-dollar-drink-night-bfs-msm-t3062814
The default settings are all good. Double-tap to wake is enabled by default.
I promise, next release I'll also put up a thank-you list to a few developers out there! Enjoy
XDA:DevDB Information
l33t, ROM for the Nexus 6
Contributors
ozzyGEEK
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: Stock
Version Information
Status: Testing
Created 2015-04-23
Last Updated 2015-04-22
What stock build did you use?
Sent from my Moto Nexus 6
Nice, congrats on your first ROM.
LMY47I
Thank you and thanks for letting me use your kernel its the absolute best! I used to always go w/BFS kernels, I think it was on my Evo4G I believe
RSVP
Thanks for your energy and contribution to the N6 community.
Edit: I'm major Zen kernel user. Great inline choice.
Looks epic, but what is "zen kernel"?
Check out the thread in the OP I linked it. Its kinda like replacing a v6 mustang engine with a v8 that uses up half the gas for some odd reason o.0
nice build. very clean, snappy and stable. Look forward to future updates. Thanks for the ROM
ozzyGEEK said:
Check out the thread in the OP I linked it. Its kinda like replacing a v6 mustang engine with a v8 that uses up half the gas for some odd reason o.0
Click to expand...
Click to collapse
Oooh OK cool, but I'm a Camaro guy :/
Sent from my Nexus 6 using XDA Free mobile app
How did you get into making the ROM did you follow a guide or? How hard is it I'd like to have a go my self
Well it depends if you want to build an AOSP ROM from source or just base it off stock like I did. This project originally started with AOSP but then I converted most of my changes into stock.
i love double tap to wake. did you add anything for screen off. i am liking long-press back.:good:
ozzyGEEK said:
Well it depends if you want to build an AOSP ROM from source or just base it off stock like I did. This project originally started with AOSP but then I converted most of my changes into stock.
Click to expand...
Click to collapse
okay so, how would i go about just basing it off stock?
Well first thing you'll want to do is set up this tool called "apktool" I don't know if there are easier ways nowadays but that's what I use. Its a Java app so it'll work on any OS you're running.. What OS do you have running on your computer?
Actually long press back was supposed to be released on my next nightly.. Did I upload the wrong build? Lol I have builds scattered all around my desktop and documents folder, I usually look for the newest one by sorting by date modified lol really confusing.
Thing is, because this project started off AOSP, I used some files and apps from AOSP and mixed it in with stock ROM after stripping it down, that's how ingot the web browser and stuff, but other than that, its mostly using apktool to edit files ..
And knowing what files do in a ROM, knowing what they're used for, knowing what you can remove or add, I think building a ROM from source will teach you a lot, there's a good guide I used for that by Stephen, you can search for the thread
ozzyGEEK said:
Well first thing you'll want to do is set up this tool called "apktool" I don't know if there are easier ways nowadays but that's what I use. Its a Java app so it'll work on any OS you're running.. What OS do you have running on your computer?
Click to expand...
Click to collapse
Well I'm probably running the worst os for this sort of thing, I'm on mac
Anyone know how to disable double tap to wake as i have no need for it. Tried different kernel managers but settings don't stick. I looked in his kernel thread but didn't find anything. Any help in permanently turning this kernel feature off appreciated.
jackmacbunton said:
Well I'm probably running the worst os for this sort of thing, I'm on mac
Click to expand...
Click to collapse
That means nothing, I know plenty of developers that use mac
In the interest of keeping this topic easy to follow, lets keep the posts developer/development related. Off topic posts and questions will likely be reported. Warning From A Moderator: http://forum.xda-developers.com/showthread.php?p=64117749
Hello everyone,
This thread is for discussing, and furthering the development of aosp/cm for our devices. I and most others believe it is in the best interest of getting the port done if we all collaborate on it. I will try to update this op and post relevant information as it becomes available.
Cheers!
CM13 Working Repo
https://github.com/7420dev
Current Goals: Listed In Order Of Priority
1.) Fixing The Various Drivers(camera,etc.)
2.) Misc. Bug Fixing
Current Status:
Open Source Gralloc in testing. Appears to be working properly.(Screen Works)
List Of Working Drivers:
-WiFi
-GPS
-AP Hotspot
-Basic 2D Graphics
-GPS
-LED
-MTP
-Sound
-BT
-Texting(SMS/MMS)
-Mobile Data
-Telephony
Here's a video from @arter97 booting cm using @tdcfpp gralloc:
https://youtu.be/fv0I45HtgtQ
Donating:
If you wish to donate, please donate to the people putting the most effort into this project! To make it easier these are the top two currently.
@tdcfpp and @sktjdgns1189 and you can donate to him here: https://t.co/sf7R69JYqx tdcfpp is working extremely hard on porting gralloc, and making excellent progress. Sktjdgns1189 is working on hard on fixing various driver issues. So far he's fixed telephony, sound and WiFi to name a few. I will try to update this as more people contribute!
Do not ask for etas or test builds!
It will happen eventually, but it will be laggy, and buggy. There is no point, if people wanted AOSP or CM, they shouldn't get a Samsung/Exynos device.
Is posible to port meizu pro 5 rom wich have same soc aas galaxy s6.
Rekan_ said:
It will happen eventually, but it will be laggy, and buggy. There is no point, if people wanted AOSP or CM, they shouldn't get a Samsung/Exynos device.
Click to expand...
Click to collapse
I would be surprised if it was laggy. Buggy, most likely, but laggy I don't think so. I've used aosp on other Samsung devices and it was always faster than TW. I didn't buy my s6 with the expectation of aosp, but if it is possible, I would definitely like to try it. The exynos 7420 is an absolute beast, and if the 810 can run the nexus like butter, imagine what the 7420 could do.
kiko3 said:
Is posible to port meizu pro 5 rom wich have same soc aas galaxy s6.
Click to expand...
Click to collapse
It could be possible. It will be interesting to see when the source comes out.
Sent from my SM-G925K using XDA Free mobile app
Xileforce said:
I would be surprised if it was laggy. Buggy, most likely, but laggy I don't think so. I've used aosp on other Samsung devices and it was always faster than TW. I didn't buy my s6 with the expectation of aosp, but if it is possible, I would definitely like to try it. The exynos 7420 is an absolute beast, and if the 810 can run the nexus like butter, imagine what the 7420 could do.
Click to expand...
Click to collapse
Probably the older Samsung devices had their sources released and this phones sources haven't been.
And yeah, I had a smooth experience with my S4 and S3 with AOSP
Pure Android 6.0 on galaxy tab S is not laggy at all! it's so smooth compared to touchwizz. On S6 it will literally flying
I don't know anything about how to achieve this.
But I found the Meizu MX Pro 5 firmware (Which have the same chip as s6)
download.meizu.com/Firmware/Flyme/PRO_5/4.5.4.1/cn/20151022054017/9e3d5077/update.zip
Hope it helps
I know the end goal is to be able to compile Android for the Galaxy S6 from scratch, but I was wondering if it would be technically possible to create some sort of hybrid version. Although a complete AOSP version would be amazing, I believe a lot of users would be happy if someone could take the current kernel based on Samsung sources, so everything around boot and driver/hardware initialization should work, and put some version of the AOSP interface on top of that. Similar to how the Google Play Editions used to work. Is that in any way feasible?
woeds said:
I know the end goal is to be able to compile Android for the Galaxy S6 from scratch, but I was wondering if it would be technically possible to create some sort of hybrid version. Although a complete AOSP version would be amazing, I believe a lot of users would be happy if someone could take the current kernel based on Samsung sources, so everything around boot and driver/hardware initialization should work, and put some version of the AOSP interface on top of that. Similar to how the Google Play Editions used to work. Is that in any way feasible?
Click to expand...
Click to collapse
One of the things I have done is to take a hal library and substitute it on stock with an open source one. That have worked on the i9300 with gralloc.
---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------
One thing I would need from our kernel devs is a dual boot kernel. Would it be possible @arter97?
tdcfpp said:
One of the things I have done is to take a hal library and substitute it on stock with an open source one. That have worked on the i9300 with gralloc.
---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------
One thing I would need from our kernel devs is a dual boot kernel. Would it be possible @arter97?
Click to expand...
Click to collapse
Haha
I've been dualbooting my S6 since my kernel's debut.
This is a bit hacky, but it's working since S3 days.
This will give you a bit of an idea how it works :
https://bitbucket.org/arter97/andro...unt.sh?at=g920fi&fileviewer=file-view-default
First time I spun a CM build from bmc08gt sources, I dualbooted it with Touchwiz intact.
Obviously, ramdisk is not compatible. So to boot different ROMs, different boot.img would be needed but it's not a big deal (at least for me).
Even using the recovery as the handy multiboot solution is quite nice since I'd say the actual recovery won't be much needed during development.
BOOT = Touchwiz, RECOVERY = CM.
arter97 said:
Haha
I've been dualbooting my S6 since my kernel's debut.
This is a bit hacky, but it's working since S3 days.
This will give you a bit of an idea how it works :
https://bitbucket.org/arter97/andro...unt.sh?at=g920fi&fileviewer=file-view-default
First time I spun a CM build from bmc08gt sources, I dualbooted it with Touchwiz intact.
Obviously, ramdisk is not compatible. So to boot different ROMs, different boot.img would be needed but it's not a big deal (at least for me).
Even using the recovery as the handy multiboot solution is quite nice since I'd say the actual recovery won't be much needed during development.
BOOT = Touchwiz, RECOVERY = CM.
Click to expand...
Click to collapse
Well, I don't want to re-invent the wheel. Is it possible to dual boot with your s6 kernel?
tdcfpp said:
Well, I don't want to re-invent the wheel. Is it possible to dual boot with your s6 kernel?
Click to expand...
Click to collapse
By flashing the kernel each time, yes.
(Or using RECOVERY as a second kernel)
arter97 said:
Haha
I've been dualbooting my S6 since my kernel's debut.
This is a bit hacky, but it's working since S3 days.
This will give you a bit of an idea how it works :
https://bitbucket.org/arter97/andro...unt.sh?at=g920fi&fileviewer=file-view-default
First time I spun a CM build from bmc08gt sources, I dualbooted it with Touchwiz intact.
Obviously, ramdisk is not compatible. So to boot different ROMs, different boot.img would be needed but it's not a big deal (at least for me).
Even using the recovery as the handy multiboot solution is quite nice since I'd say the actual recovery won't be much needed during development.
BOOT = Touchwiz, RECOVERY = CM.
Click to expand...
Click to collapse
Couldn't we use an implementation of anykernel to allow ramdisk compatibility with cm and tw at the same time?
Xileforce said:
Couldn't we use an implementation of anykernel to allow ramdisk compatibility with cm and tw at the same time?
Click to expand...
Click to collapse
Multibooting with a single kernel requires multiple ramdisk to be in a single boot.img
Anykernel method is not suitable with this.
arter97 said:
Multibooting with a single kernel requires multiple ramdisk to be in a single boot.img
Anykernel method is not suitable with this.
Click to expand...
Click to collapse
Oh okay I see what you are referring to. I meant in terms of not multibooting. As in if we wanted to develop a kernel that would work on both tw and cm, probably the only way to do that would be anykernel correct?
Xileforce said:
Oh okay I see what you are referring to. I meant in terms of not multibooting. As in if we wanted to develop a kernel that would work on both tw and cm, probably the only way to do that would be anykernel correct?
Click to expand...
Click to collapse
Yes and it still requires some source changes to accommodate both CM and Touchwiz(MTP, etc) but still I don't like Anykernel method.
I will release 2 separate kernels if CM happens.
arter97 said:
Yes and it still requires some source changes to accommodate both CM and Touchwiz(MTP, etc) but still I don't like Anykernel method.
I will release 2 separate kernels if CM happens.
Click to expand...
Click to collapse
You got time ahead then.
arter97 said:
Yes and it still requires some source changes to accommodate both CM and Touchwiz(MTP, etc) but still I don't like Anykernel method.
I will release 2 separate kernels if CM happens.
Click to expand...
Click to collapse
Got it. I feared there may be some source changes. I've never been a fan of anykernel either.
Found out that this app is compatible with the s6. I'm wondering if the tool would be able to patch your kernel @arter97
http://forum.xda-developers.com/showthread.php?t=2447534
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
Hows the current development, been eager to try CM12.1 but waiting for a stable version
I'm not bashing the developers, just interested in hearing others views/update progress
Rossyyy said:
Hows the current development, been eager to try CM12.1 but waiting for a stable version
I'm not bashing the developers, just interested in hearing others views/update progress
Click to expand...
Click to collapse
Why no you join and make some kool stuff?
StraightEdgeKid said:
Why no you join and make some kool stuff?
Click to expand...
Click to collapse
I'd love to and i did a few years back but i dont have enough free time as it is
P.s do you know if there is a editable oxygen os rom file (i.e i can add stuff the to system folder)
Rossyyy said:
I'd love to and i did a few years back but i dont have enough free time as it is
P.s do you know if there is a editable oxygen os rom file (i.e i can add stuff the to system folder)
Click to expand...
Click to collapse
Ayy man, was just pulling your leg.
There is, in OPX General section, can't provide you link since replying from phone, but you'll find it easily.:good:
StraightEdgeKid said:
Ayy man, was just pulling your leg.
There is, in OPX General section, can't provide you link since replying from phone, but you'll find it easily.:good:
Click to expand...
Click to collapse
I looked at that but its all image files and different to when i used to mess with Huawei roms
Rossyyy said:
I looked at that but its all image files and different to when i used to mess with Huawei roms
Click to expand...
Click to collapse
Also coming from a Huawei?
Isn't there the full 003 ROM zip that you can even flash in TWRP shouldn't you could edit that zip? And if I'm correct there should be options to extract img files or you could make backups in TWRP and create flushable files out of them...
Regards
taaeem said:
Also coming from a Huawei?
Isn't there the full 003 ROM zip that you can even flash in TWRP shouldn't you could edit that zip? And if I'm correct there should be options to extract img files or you could make backups in TWRP and create flushable files out of them...
Regards
Click to expand...
Click to collapse
I think a stable base is lacking, from which developers can cook roms with. Thats why development is slow. I had opo from the first day, within a month we saw the creation of several custom roms. Opx is nearing the second month from release date.
Almost everyone can make a custom rom from a zipfile with a custom kernel added (blu kernel), build.prop tweaks, deodexed, optimal preinstalled settings and removal of unnecessary apps and files. But sd card and other stock problems will remain. So i think its holding people back to play with this rom.
Its a cyclical process, many people are waiting on developers because stock isnt stable. Developers are waiting for stock rom because custom wouldn't be stable (if there even are recognized developers who bought opx).
Rossyyy said:
Hows the current development, been eager to try CM12.1 but waiting for a stable version
I'm not bashing the developers, just interested in hearing others views/update progress
Click to expand...
Click to collapse
I'm coming from the Xperia L. It was released in spring 2013, and I got that device in August, but still had to wait till Dec till the dev scene took off. Still, once it took off the development was crazy. It was in fact one of the first phones to get CM12 (within a week, iirc) with very few bugs
Compared to that, development here feels amazingly fast. We already have an awesome custom kernel, and cm12.1 seems to be just about done. I'm sure things will get hectic soon around here too
It's nothing to do with a "stable base" or any other stuff like that. It's just a lack of time that the existing devs have. Had this device been out during the vacations or something, CM13 would've been daily driver stuff in less than a week.