Related
Hi all.
I have successfully flashed PsychoGame's CyanogenMod 7 ROM for GT-s5360 together with its kernel.
Now i would like to make some changes in the source code of CM7 and to build it from source. Unfortunately i have spent already 4 days without success.
Those are the steps that i did:
1. I have downloaded CM7 source code from git://github.com/CyanogenMod/android.git -b gingerbread
2. I have cloned PsychoGame's totoro device code into /devices/samsubg/totoro
3. i have connected my device via USB and run the script extract-files.sh which successfully extracted all files.
4. during the building i realized that the above script extract all essential files (like camera related), so i cloned PsychoGame's vendor directory from github.com/PsychoGame/android_vendor_samsung_totoro.git
5. now i realized that the file cyanogem_totoro.mk in the directory vendor/cyanogen/products is missing. where i can find a suitable file?
i have found somewhere such file and succeeded to build an ROM, unfortunately CWM does't let me to flash it because the assert command checks that the current device in "totoro" but it fails. i have tried to open the zip file of the ROM and to delete the assert command but CWM still can''t flash the new ROM.
can somebody please help me with some guild about how PsychoGame built his last vertion of CM - CyanogenMod 7 Alpha 5 Release
Thank you very much!
Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing
marcussmith2626 said:
Use percys source code - It has more fixes
Compare build.prop and update binary & scripts for cwm flashing
Click to expand...
Click to collapse
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!
yuripo said:
Hi, thank you for the information about gigngerDX. i found the github of the device but can you please tell me where to find all other files to build this rom? do i need to buld it without the kernel? how to do that?
thank you again!
Click to expand...
Click to collapse
Percys github is
https://github.com/percy-g2
I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy
I haven’t compiled a Cyanogen rom before
If you would like to contribute to the building of Cyanogen roms the best person to talk to is percy[/QUOTE]
can please somebody explain how to build only Percys ROM without the kernel?
thank you
Hi all.
Can somebody please give a small guide for how to build percy's CM7 ROM from source?
which directories in the CM7 i should replace? does the process of building is the same as with official ports?
Thank you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-N.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Feature List
Substratum rootless theme engine support (must install Substratum from play store)
Tentacles settings!
Pixel Launcher Included
OmniSwitch
Power menu options
Screenshot
Screen record
DPI settings
Status bar time and date options
Status bar network traffic indicator
Status bar notification settings
Quick tile settings
Volume button playback control
Volume button wake
DUI (fling, pulse, smartbar)
Screen record
And much more!!!!
Click to expand...
Click to collapse
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.2
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
Q: Why isn't there XYZ feature?
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-N.
Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
Flash ROM, GApps and any additional .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Donate to OctOS Development (PayPal)
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
AOSP
Open Gapps
LineageOS
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Team-OctOS!
XDA:DevDB Information
Oct OS, ROM for the Xiaomi Mi 3
Contributors
aniket.lamba, manfromgta
Source Code: https://github.com/Team-OctOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: A custom recovery (TWRP preferrable),ROM and Gapps zip file,knowledge on how to flash zip files.
Based On: Lineage
Version Information
Status: Stable
Created 2015-12-26
Last Updated 2017-04-29
OctOS 6.0.1
Team OctOs presents Oct-M.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes
Q: What code is Oct-M based on?
A: Starting with Oct-M, we've rebased OctOs on Aosp code.
Q: What happened to CM?
A: Octos was originally formed as an AOSP source rom. We have returned to those roots.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file, and grab your favourite gapps package
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
* Weekly Builds
* Release Builds
* Gapps 6.0 Mini
The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
A Special thanks to @audahadi for his device sources.
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Follow Us at the various websites below!
Kernel source - https://github.com/kernel-hut/android_kernel_xiaomi_cancro
Device - https://github.com/audahadi/android_device_xiaomi_cancro
Vendor - https://github.com/audahadi/proprietary_vendor_xiaomi
Bugs/Issues
[*]You tell me
Some ss
Rom is great for now.. all basic things works .. that is for now xD
Trying this rom for a few hours, I observed the followings:
The rom is smooth and rather fast.
Almost everything works properly.
Xposed works on this rom without any problem.
Battery life is reasonable.
Thank you so much, aniket.lamba.:good:
@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast
Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.
Cheers
rajib4 said:
@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast
Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.
Cheers
Click to expand...
Click to collapse
Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.
marko94 said:
Some ss
Rom is great for now.. all basic things works .. that is for now xD
Click to expand...
Click to collapse
Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?
---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------
aniket.lamba said:
Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.
Click to expand...
Click to collapse
"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.
Me_Ashish_ said:
Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?
---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------
"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.
Click to expand...
Click to collapse
For the initial stage it is CM based,this build which I've posted is an initial build (considering it still has issues) so we chose CM base as we draw more support of non-nexus devices,we'll shift the base to AOSP.I'll change the thread title so the users won't have a problem figuring out.
I have a doubt...does ambient display has a BUG or it's not working just for me.
nirjharmistry said:
I have a doubt...does ambient display has a BUG or it's not working just for me.
Click to expand...
Click to collapse
Never heard of someone who got Ambient Display working anytime. It just shows the, doesn't supports though.
Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all
Me_Ashish_ said:
Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all
Click to expand...
Click to collapse
Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.
Sent from my MI 4 using Tapatalk
diongdyh said:
Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.
Sent from my MI 4 using Tapatalk
Click to expand...
Click to collapse
That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.
Me_Ashish_ said:
That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.
Click to expand...
Click to collapse
If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.
Sent from my MI 4 using Tapatalk
diongdyh said:
If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.
Sent from my MI 4 using Tapatalk
Click to expand...
Click to collapse
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Me_Ashish_ said:
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Click to expand...
Click to collapse
Ooh did u mean that after flashing this ROM your system partition got reset to default (660mb)?
Cuz in the screenshot you attached it shows that you only have 660mb.
Sent from my MI 4 using Tapatalk
Me_Ashish_ said:
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Click to expand...
Click to collapse
yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD
marko94 said:
yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD
Click to expand...
Click to collapse
I too faced the same issue and with other ROMs too. There is an easy fix. If you are using twrp, go to Wipe->advanced Wipe Select "System" and click "repair or Change File system" below. Then Select "Resize". The issue will now be fixed.
If you are flashing ROM and Gapps, do the above step after flashing ROM before installing the Gapps.
Is this rom cm based or aosp based?
This ROM is based on Nightly version AICP but its Stable for daily use.
FEATURES:
All AICP features
Lollipop features (customized by AICP)
BUGS:
Unresized BootAnimation [on the center] (I did this on purpose, if you want you can change.)
Sees there is a sim card in tablet but there isn't. [Says "NO SERVICE"] (You can disable with " Permanent GSM solution down below)
Little bugs [does not affects daily use]
Can't install GAAPS because system partition is small (FIXED IN VERSION 2 ! - FIXED IN V2 !)
_-----------------------------------------------_
Permanent GSM solution:
1) not avaliable instructions
2) when way to disable cellular its entered ti here
INSTALLATION:
1. Install TWRP Recovery [if you haven't]
2. Boot into recovery mode
3. Wipe "System,Data,Cache,Dalvik Cache"
4. Flash ROM file from install zip section
Note: If you will flash GAAPS don't reboot after flashing system, flash GAAPS before rebooting.
Note2: Download v2 if you need flashing GAAPS.
XDA:DevDB Information
AICP SM-T800, ROM for the Samsung Galaxy Tab S
Contributors
romngenie
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: TWRP
Based On: AICP
Version Information
Status: Stable
Created 2016-06-25
Last Updated 2016-06-25
hello, after searching I've found out that AICP stand for Android Ice Cold Project. May I ask if it look like Cyanogenmod or the AOSP ? first time I hear about it...
and just to know, why isn't it on the list of : http://dwnld.aicp-rom.com/?device=all&type=all ? for the chagallwifi T-800 ?
zigonneux said:
hello, after searching I've found out that AICP stand for Android Ice Cold Project. May I ask if it look like Cyanogenmod or the AOSP ? first time I hear about it...
and just to know, why isn't it on the list of : http://dwnld.aicp-rom.com/?device=all&type=all ? for the chagallwifi T-800 ?
Click to expand...
Click to collapse
Because i just created a XDA project. I cant contacted to AICP
Sent from my Asus ZenFone 2 Laser (ZE550KL) using XDA Labs
nice rom but some errors: can't check for update. Can't install any gapps because lack of space in the system file. Very fast rom , but can't test anything else.
zigonneux said:
nice rom but some errors: can't check for update. Can't install any gapps because lack of space in the system file. Very fast rom , but can't test anything else.
Click to expand...
Click to collapse
System partition is 300-450 MB i dont know why you can't install GAAPS (Fixed in V2 of ROM)
Can't check for update because its unofficial and no more updated . (except bug fixes)
Thanks for installing.
zigonneux said:
nice rom but some errors: can't check for update. Can't install any gapps because lack of space in the system file. Very fast rom , but can't test anything else.
Click to expand...
Click to collapse
YOU CAN INSTALL GAAPS LIKE THIS: (GAAPS FIXED IN V2 - TRY V2 WITHOUT ANY "occupation")
1. Download and install V2 of the ROM.
2. Install Gaaps.zip (install pico)
download says: Uploaded: 2016-Jul-19 , so I guess that the Fixed file is not there yet. I'll wait for the Fix and test for the fun of it... post the link when the fixed file is ready. I'm too lazy to deal with the Solution : decompress and recompress etc.
zigonneux said:
download says: Uploaded: 2016-Jul-19 , so I guess that the Fixed file is not there yet. I'll wait for the Fix and test for the fun of it... post the link when the fixed file is ready. I'm too lazy to deal with the Solution : decompress and recompress etc.
Click to expand...
Click to collapse
GAAPS is fixed in V2 version.
http://forum.xda-developers.com/devdb/project/dl/?id=19411
there is V2 Link.
You dont need uncompress and other techniques for this. Just download V2 and your GAAPS will fixed.
And i know i dont update this ROM except bug fixes.
SM-T800 cihazımdan Tapatalk kullanılarak gönderildi
LineageOS for OnePlus3
Hi,
I'm offering unmodified LineageOS nightlies for our device. The builds should be online at around 4:00AM (UTC +1) everyday.
If you want a pure LineageOS experience you should probably give it a try. These builds dont have open beta blobs, oxygen firmwares or anything else included. You are free to flash firmware and modem though, I'm using Oxygen 4.0.1 firmware and modem and its working fine.
I'm not a developer and I won't fix any bugs. If there is a bug, wait for LineageOS team to fix it.
Changelog:
https://www.cmxlog.com/14.1/
Download:
http://webzukunft.de/lineageos/
Status:
OFFICIAL LINEAGEOS DOWNLOADS ARE ONLINE, I WONT POST ANY UPDATES HERE BUT YOU MAY FIND NIGHTLIES UNDER THE GIVEN LINK.
How to install?
1. Reboot to TWRP (I recommend using official twrp 3.0.3)
2. Wipe System, Cache and Dalvik
3. Flash ROM
4. Flash GAPPS (I recommend opengapps)
5. Reboot
Sources:
Kernel Tree
Device Tree
Code Review:
LineageOS Gerrit
Credits:
LineageOS Team
Contributors:
oelf
hutilicious
There is already a thread for lineageOS nightlys: https://forum.xda-developers.com/oneplus-3/development/rom-lineageos-oneplus3-t3528972
I think we don't need two of them
panther124 said:
There is already a thread for lineageOS nightlys: https://forum.xda-developers.com/oneplus-3/development/rom-lineageos-oneplus3-t3528972
I think we don't need two of them
Click to expand...
Click to collapse
This guy offers no up-to-date nightlies and MEGA is not everyone's choice to download from. Choose whats best for you.
Hi guys,
todays nightly is up and tested and running
Ive tweaked the build system so that nightlies are now available at 04:00AM (UTC +1)
have a good day
Dirty flashed without problems.
Only issue I have since weeks (with every rom) is that my camera is not working 100%. Either doesn't take pictures at all/ force closes or you have to trigger 3-5 times before a picture is taking
hoqpus said:
Dirty flashed without problems.
Only issue I have since weeks (with every rom) is that my camera is not working 100%. Either doesn't take pictures at all/ force closes or you have to trigger 3-5 times before a picture is taking
Click to expand...
Click to collapse
hi, Im facing the same issue. its not related to my build and seems to be a general custom rom 7.1.1 problem. thanks for your report.
Thanks for the build. Unfortunately with the latest 2 builds (16./17.1.) inbuild root is not working for me anymore.
Achi92131 said:
Thanks for the build. Unfortunately with the latest 2 builds (16./17.1.) inbuild root is not working for me anymore.
Click to expand...
Click to collapse
Hi, thanks for noticing. I didnt notice it but you are right.
Option is missing in developer settings, too.
You can try flashing SuperSU zip to retain root again! Make sure to check changelogs, so you know if this has been fixed.
Apart from that, 20170117 is up,tested and running.
EDIT:
Ive checked the changes and it seems that LineageOS disabled SU extension by default. Builds can still be made with SU but it has to be done by the device maintainer. They said they are working on an SU extension for Lineageos.
For the time being, you have to flash SuperSU.
Thx for your hard work ... No one is updating .. this ROM on daily basis ... Except you ...
Any differences between this builds and Dianlujitao builds?
Flamehell said:
Any differences between this builds and Dianlujitao builds?
Click to expand...
Click to collapse
I actually cant tell if there is any difference. This rom is build from LineageOS official github source only. I think dianlujitao uses unmerged commits in his builds sometimes. Choose whats working best for you.
SU is back
Hi guys,
As there wasnt anyone voting for no root, I decided to build this rom with SU now. So any builds starting from 2016-01-25 are with SU. Enjoy root everyone!
Update:
Due to unexpected syncing errors some latest commits are missing in todays 2016-01-25 nightly. Ive fixed the issues and running a build now. Please check for a new 2016-01-25.zip later that day. Sorry for any inconveniences.
According to ciwrl from the LineageOS Team, "Look for [official Lineage OS] builds to start rolling out this weekend" January 21st & 22nd, 2017
If you are not familiar with the builds download page, when an official LineageOS build is available it will be listed on that page. To find the build for your device, into the left side "Devices" column, click on the appropriate horizontal tab for your device brand name. Then click on the appropriate horizontal sub-tab model name. If your device is not yet listed it means that build is not yet released, please re-visit again later.
There are no estimated time of arrival (ETA) for all builds. If you want builds to be release faster you are welcome to love back your LineageOS community by contributing a code review. Either yourself as volunteer or by paying someone to contribute on your behalf.
Two types of builds:
1. Nightly: For clean fresh install. LineageOS Team recommends that users wipe when switching to LineageOS, and reinstall their gapps.
2. Experimental: For data migration/upgrade from CyanogenMod (CM) 13.0 or 14.1 to LineageOS 14.1. That data migration may or may not work. If it does not work you can always try the Nightly build. Experimental build may wipe permissions. In that case you will have to re-allow app permissions, but should retain all user data. Experimental build is watermarked with an ugly banner to ensure that you do not permanently run that Experimental build, and upgrade to a Nightly build after. Experimental build will be available for two months after January 20th, 2017. Read more.
Bugs and feature requests
Report bugs and make feature requests in that tracker. The LineageOS team are not accepting bug or regression reports until builds are available here. If you have any questions please check the instructions in that wiki or ask in #lineageOS on freenode.
Links
• Present Builds/Downloads available
• Verifying builds authenticity
• Update & build prep
• Bug and feature request tracker
• Wiki
• Status page
• Statistics
Enjoy
Why not a link to their official blog?
And when?
We all are waiting for official lineage-14.1 builds.
Good idea
RockyTV said:
Why not a link to their official blog?
Click to expand...
Click to collapse
RockyTV Good idea. Done I just added all the official links related to the coming soon official builds at https://forum.xda-developers.com/li...january-21-t3542405/post70658000#post70658000
waiting it like a child wait xmas
I think tomorrow will be available.
EvilHowl said:
I think tomorrow will be available.
Click to expand...
Click to collapse
I hope it does.. Well all the best!!
Seems like Lineage 14.1 builds have started.
https://review.lineageos.org/#/c/155809/
First build for Nexus 5x is up!
Enviado desde mi Nexus 6P mediante Tapatalk
Nexus nightly ready ... I wait for lg d802 ?
zifnab himself said it may take an hour for builds to be available in the download portal because of the hourly update interval on the mirrors; so it could take up to an hour for device builds to show up in the portal.
There's a ROM for Galaxy J2 (J200BT...)? If not, please do one, we're stuck on 5.1.1, and it's a horrible thing.
Do we know anything about lg g2 d802? I would like to know if it will get launched on los 13 or los 14.1 and when , thank you for your great work and for your time
pananoydakis said:
Do we know anything about lg g2 d802? I would like to know if it will get launched on los 13 or los 14.1 and when , thank you for your great work and for your time
Click to expand...
Click to collapse
pananoydakis The LineageOS Team said that the builds will be release periodically starting on January 21st & 22nd, 2017. When a build is available it will be listed on that page. Into the right side "Devices" column, click on the appropriate horizontal tab for your device brand and model. If your device is not yet listed, please re-visit again later.
There are no estimated time of arrival (ETA) for all builds. If you want builds to be release faster you are welcome to love back your LineageOS community by contributing a code review. Either yourself or by paying someone to contribute on your behalf.
For S5 klte pls
Enviado desde mi SM-G900F mediante Tapatalk
Why Cynogenmod and lineageOS does not make ROMs for meizu devices?
Why Cynogenmod and lineageOS does not make ROMs for meizu devices?
tank4k said:
will LOS get substratum compatibility?
Click to expand...
Click to collapse
I hope so... It sucks to have to reapply all of your themes whenever you update.
Ouch. I tried flashing the experimental OnePlus One (bacon) over CM14.1/LineageOS unofficial 20170117. The ZIP signature failed to verify. I (probably foolishly) tried it without ZIP signature verification, and it corrupted the partitions. Back to a few months ago CM14 TWRP backup...
So I highly DON'T recommend trying to flash the 20170123 bacon build if it fails ZIP signature verification.
(Going a touch deeper, there had been problems a couple of major generations of CM ago on the OnePlus One where the ZIPs were fine but the exact signing simply didn't work, and it was appropriate at that time to skip ZIP signature verification, but... oops).
libove said:
Ouch. I tried flashing the experimental OnePlus One (bacon) over CM14.1/LineageOS unofficial 20170117. The ZIP signature failed to verify. I (probably foolishly) tried it without ZIP signature verification, and it corrupted the partitions. Back to a few months ago CM14 TWRP backup...
So I highly DON'T recommend trying to flash the 20170123 bacon build if it fails ZIP signature verification.
(Going a touch deeper, there had been problems a couple of major generations of CM ago on the OnePlus One where the ZIPs were fine but the exact signing simply didn't work, and it was appropriate at that time to skip ZIP signature verification, but... oops).
Click to expand...
Click to collapse
If you flashed the actual nightly (and did a clean install), you shouldn't have this problem. I think.
RockyTV said:
If you flashed the actual nightly (and did a clean install), you shouldn't have this problem. I think.
Click to expand...
Click to collapse
It's possible that I caused the damage myself. The not-ZIP-signature-verified Experimental flash was taking far longer than usual; after about 30 minutes I cold re-started. After the restart, the /system file system was gone.
Two concerns remain:
1. That TWRP 3.0.2.0 fails the ZIP signature verification on BOTH the Experimental and the Nightly.
2. That the flash took 30+ minutes and hadn't completed, when a normal flash on the OnePlus One (including LineageOS unofficial just a few days earlier) takes perhaps 5 minutes, or less.