To those curious about why Cyanogenmod 12.1 builds for Samsung Galaxy Tab S 8.4 (SM-T700) are stuck at cm-12.1-20150714-NIGHTLY, the Cyanogenmod build bot has been failing builds for klimtwifi. A log of a recent build failure can be seen here (Build cm-12.1_klimtwifi-userdebug-nightly-- Jul 19, 2015 6:11:09 AM).
I'm not a developer, but I believe I've found the cause in a recent commit forcing the removal of a "deprecated" (obsolete) config file from the official Cyanogenmod source tree. The commit is described here.
This post is a call for help for developers who may have a better idea of what is going on, and who can push the needed changes for review and, hopefully, approval by the Cyanogenmod team.
Related
Hello I have a s4 mini with cm 12.1 snapshot of 17th november 2015.
I want to know if cyanogenmod will release cyanogenmod 13 s Nightly. They will release??
Our big master arco68 is currently working on. As usual, no ETA are due... he said that there were some problems about RIL. I don't know the actual situation, but I can see that he is committing on cmxlog.
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
flamingspartan3 said:
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
Click to expand...
Click to collapse
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
flex1911 said:
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
Click to expand...
Click to collapse
Thanks for the help! I was able to get it to work by running 'lunch cm_flo-userdebug' and then mka.
Are you sure the Krack fix isn't already in 14.1:
https://www.lineageos.org/Changelog-15/
KRACK Wi-Fi vulnerability has been fixed in both LineageOS 14.1 and 13.0
Click to expand...
Click to collapse
Any chance we'll see LOS 16 or other ASOP Pie 9 ports to Galaxy Tab S? I have unofficial LOS 16 on my 2013 Nexus 7 tablet and it works quite well.
To get Pie, someone (read - me) should invest 2-3 months of spare time to make it production. The team is basically silent, and I am more concerned about my paid job and keeping N security up-to-date. I am also building 16.0 internally but it is not even alpha for me (like, not completing boot on chagalllte)
gellmar said:
To get Pie, someone (read - me) should invest 2-3 months of spare time to make it production. The team is basically silent, and I am more concerned about my paid job and keeping N security up-to-date. I am also building 16.0 internally but it is not even alpha for me (like, not completing boot on chagalllte)
Click to expand...
Click to collapse
Anyway to help out ?
I've just put Exynos5420 LineageOS 14.1 vanilla onto a tablet.
Also just setup a build environment, grabbed the Exynos5420 git repo's source code and built successfully the cm-14.1 branch.
bluess57 said:
Anyway to help out ?
I've just put Exynos5420 LineageOS 14.1 vanilla onto a tablet.
Also just setup a build environment, grabbed the Exynos5420 git repo's source code and built successfully the cm-14.1 branch.
Click to expand...
Click to collapse
@thompatry is working on resurrection of 15.1 - check if you can help him with camera & gps stuff.
Edit: nvm. Haggartk posted an update for 4/8/19 thanks haggartk!
I see that haggartk has an unofficial build but the last update was 2/27/2019. Has he dropped maintenance for 14.1?
If so, then is there someone else on this forum perhaps who is maintaining the 14.1 build, who is trustworthy/well known here in the forum?
Unofficial Builds Honor 5x 15.1 by @wileyc
Click to expand...
Click to collapse
A note by @wileyc
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
with android 16.0 a device as with 2gb ram started hanging. Even with the These Zram Compression Tweaks , this device still wasn't performing optimally. Wiley already creating ROMs for many other lineageOs devices for prior generations. So I, had asked him for same if that can be done with HONOR 5x also. And he did that. And as from community i am very thankful to him.
Notes: This flashing procedure is same. If you are coming from any other ROM clean flash is needed. And obvisouly latest gapps.
Please do not ask anything in official to official lineageOs thread. And neither do I or Wiley will be looking at any error. These are builds are coming directly from lineageOs sources.
Kernel Sources : Github LInk
Credits : @BadDaemon @crpalmer @dobrosław Kijowski
@wileyc
Download Links
Honor 5x Download Link
All this is happening because of @wileyc. Please consider donating him. He is paying from his own money. We as community should be thankful to him for what he is doing all of us.
Click to expand...
Click to collapse
OTA update
Does ota update work?
50UND2 3NG1N33R said:
Does ota update work?
Click to expand...
Click to collapse
Afaik yes.