LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for LG G4 . The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
Video Recording
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
h815: https://download.lineageos.org/h815
h811: https://download.lineageos.org/h811
personnal nightlies http://host.erwanleboucher.fr/
XDA:DevDB Information
CM 14 on LG G4, ROM for the LG G4
Contributors
genesixxbf3, codeworkx
Source Code: http://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: V20A Bootloader and modem
Version Information
Status: Beta
Created 2016-10-10
Last Updated 2018-01-28
Reserved
What's working.
everything except what's not working.
What's not working ?
encryption (who use that )
f2fs (who use that too )
QHD video recording
official = signed
unofficial = no signed
to go to unofficial to official flash experimental first (and boot it)
Reserved
If you don't have a sim card detected try that
Code:
adb root
adb shell rm /data/user_de/0/com.android.providers.telephony/databases/telephony.db
adb shell rm /data/user_de/0/com.android.providers.telephony/databases/mmssms.db
adb reboot
Nice job mate! Thank you!
Everythink work ??? no bug ? no issues ? theme engine work ?
yes i know Nougat is too Young for Stable custom Rom at this moment but hope
What doesn't work? if you dont mind me asking?
Awesome work, thanks Genesixx
If there are known issues I am sure the OP will update the first post. You can also flash it and post if you find anything, just don't forget to make a full backup first ????
How is the camera on this build?
Op says you should flash gapps 6.0, is this right?
ashensii said:
Op says you should flash gapps 6.0, is this right?
Click to expand...
Click to collapse
7.0 gapps
to see what's not workin check second post
wow excellent work!
Is this stable enough to use as a daily driver?
ceanth said:
wow excellent work!
Is this stable enough to use as a daily driver?
Click to expand...
Click to collapse
It is
Was running the 10-05 build for several days. I find it works just as good as CM13, possibly better (smoother/faster). Bugs are very minimal, features are too but overall this is a very stable and solid build so far!
THANK YOU @genesixxbf3 for bringing this to us! I don't really like CM13, but 14, something about it is very nice (coming from someone that prefers stock over aosp).
EDIT: It should be posted that H811 users need to be on 20o FW before flashing this, to make sure they get best experience (if you want sound/camera working).
EDIT2: Oh and now there is a thread for me to report: Zooming with standard gallery hot-reboots the phone.
theslam08 said:
It is
Was running the 10-05 build for several days. I find it works just as good as CM13, possibly better (smoother/faster). Bugs are very minimal, features are too but overall this is a very stable and solid build so far!
THANK YOU @genesixxbf3 for bringing this to us! I don't really like CM13, but 14, something about it is very nice (coming from someone that prefers stock over aosp).
EDIT: It should be posted that H811 users need to be on 20o FW before flashing this, to make sure they get best experience (if you want sound/camera working).
Click to expand...
Click to collapse
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
ceanth said:
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
Click to expand...
Click to collapse
Unfortunately I am not sure about the h815. With the h811 we had a recent issue where we had to be on the latest FW for it to fully work.
I would 'assume' it would be the same for you. May wish to wait for 815 users to report back which FW they're on and how it all works for them.
(and you don't have to actually be running the stock ROM before flashing this, the firmware is a once-flash-always-flashed type situation; firmware is not ROM based it stays between ROMs)
ceanth said:
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
Click to expand...
Click to collapse
v20A or newer. So you are fine. Before flashing you don't care what rom you are on. You just need to wipe system , data , cache and dalvik cache and flash whatever you like.
kessaras said:
v20A or newer. So you are fine. Before flashing you don't care what rom you are on. You just need to wipe system , data , cache and dalvik cache and flash whatever you like.
Click to expand...
Click to collapse
ok great.
I'll give it a go and report back with feedback to the group
ceanth said:
ok great.
I'll give it a go and report back with feedback to the group
Click to expand...
Click to collapse
(out of subject)
I wonder how do you live with the stock rom on G4
You charge the phone 2 times per day ? haha
The stock rom has issues and it doesn't let the phone get into doze.
Have fun flashing you will never wanna go back to stock again
kessaras said:
(out of subject)
I wonder how do you live with the stock rom on G4
You charge the phone 2 times per day ? haha
The stock rom has issues and it doesn't let the phone get into doze.
Have fun flashing you will never wanna go back to stock again
Click to expand...
Click to collapse
Haha. I flashed stock rom because I wanted to use Android Pay. There is a deal on in the UK where by you get free London Underground travel on Mondays throughout October.
I was planning on flashing something else after the offer is done but Android Pay failed to work this morning causing a massive queue behind me I have had enough of it!
ceanth said:
Haha. I flashed stock rom because I wanted to use Android Pay. There is a deal on in the UK where by you get free London Underground travel on Mondays throughout October.
I was planning on flashing something else after the offer is done but Android Pay failed to work this morning causing a massive queue behind me I have had enough of it!
Click to expand...
Click to collapse
Hmmm. I don't use android pay but I read somewhere that you can use it with cm 14 or 13 if you use an official and stable build , not nightly or unofficial , and disable superuser in developer settings.
Of course I don't know if that's true
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
audio lag in some games
dialer shows an ugly screen on incoming calls
drm support is broken (e.g. play movies)
package manager sometimes installs x86 libs when it needs arm libs (causes some apps to not work at all)
selinux enforcing mode
sim 2 cannot be disabled
sim 2 audio quality issues when also on a call on sim 1 (unconfirmed)
USB UMS (Mass Storage) - Killed off for now, MTP works just fine
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM @ download.crpalmer.org
CyanogenMod for Z008/ ze550ml: ROM @ download.crpalmer.org
Recovery Links
Z00A
CM Recovery CM Recovery @ download.codefi.re/jrior001
theSSJ's TWRP: XDA thread
Official TWRP: TWRP.ME
Unofficial F2FS TWRP: jrior001's unofficial twrp
Z008
CM Recovery CM Recovery @ download.codefi.re/jrior001
Unofficial F2FS TWRP: jrior001's unofficial twrp
theSSJ's TWRP: XDA thread
Official TWRP: TWRP.ME - PENDING ACCEPTANCE
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
Currently only supported in jrior001's unofficial TWRP
May or may not work in others
** see this post for more info **
Intel stores some modem firmware in the OTA's in a file labeled "ifwi.zip"
These are flashable zips to receive the updated firmware while staying on custom ROMS
**THIS IS A ONE WAY PROCEDURE, JUST LIKE THE OTA's THERE IS NO KNOWN WAY
TO FLASH BACK TO EARLIER MODEM FIRMWARE, PROCEED WITH CAUTION**
IF you still wish to proceed, current flashable ifwi zips are available HERE for Z00A AND Z008
XDA:DevDB Information
Unofficial CyanogenMod 12.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
crpalmer, jrior001, hharte
Source Code: https://github.com/CM-zenfone2
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 2.19.40.22 stock base
Version Information
Status: Beta
Created 2015-07-24
Last Updated 2015-10-02
Reserved
Known issues are know in the first post so that all the maintainers can updated it and keep it current.
FAQ
Does Official TWRP work?
* Only if they have the device called Z00A. As of the initial release the official TWRP did not but will likely soon be named properly.
* If it doesn't work,arecovery from the OP.
Can I use a custom kernel with these builds?
* No, there are no custom kernels build based off of our source tree, using our defconfig and which contain the proper ramdisk.
*Also, doing so makes any feedback useless to us because the kernel and the ROM are a complete package and changing part of that means you may have broken something beyond our control.
Will this be an Official ROM?
* When all the show stopping bugs are fixed and all the upstream commits are merged, yes.
* Until then, no because CyanogenMod has very high standards for accepting new devices.
What about the Z008 aka ze550ml?
* Right now none of the developers who are working on the development own one and therefore we can't support it.
* One of the developers working on this said he was purchasing one (even though he already owns the ze551ml). When he gets it and has time to work on it we may see it. Without us owning the device though, there will never be support for it.
Do I need to unlock the bootloader?
* Yes.
thanx Chris, a zillion people have been waiting for your hard work and quality as always , thankyou chris,,steve
Finally !!!!!!! Damm Finally !!! Thanks a lot man !! been waiting for this so long !! Finally some development !! Thank You
Finally.....cm 12.1 has landed on zenfone 2
knitesh813 said:
Finally.....cm 12.1 has landed on zenfone 2
Click to expand...
Click to collapse
This TWRP recovery work??
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
Thank You for your work!
john_petrucci said:
This TWRP recovery work??
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
Click to expand...
Click to collapse
Cannot confirm but there should be an official twrp update later today that will for sure.
Sent from my ASUS_Z00A using XDA Free mobile app
Just as info and to avoid questions: My TWRP should be working here as ro.product.device is set to Z00A
OMG....OMG......can't wait to flast it....!
Please someone give me a review.
How about memory leak?
How about battery?
Thankyou very much
Ready to Flash... Thxxx Guyss. was waiting for soo long
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
allasca said:
Please someone give me a review.
How about memory leak?
How about battery?
Thankyou very much
Click to expand...
Click to collapse
Give it a try...
Cheers for the hardwork.
Accept donations?
allasca said:
Please someone give me a review.
How about memory leak?
How about battery?
Thankyou very much
Click to expand...
Click to collapse
I am using the 2gb/16gb ZE551ML and I have around 600-1gbmb free at any given time (OS is only doing around 800mb-1gb so I'd imagine the 4gb should have 3gb+ free). Now battery life, loving it, around 1% every 5-7 minutes with the screen on
crpalmer said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Click to expand...
Click to collapse
Whoop, there it is! :thumbup:
jrior001 said:
Cannot confirm but there should be an official twrp update later today that will for sure.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
Whoop, there it is!
FINALLY, thank you both so much for all your hard work, including @TheSSJ!
Sent from the Ace's MB865 using Tapatalk
Please provide a google drive link please...
Download is becoming unsuccessful
Does the second sim card work? From what I understand this is not supported by Cyanogen.
All set up using twrp on z00a..had to factory reset and then a reboot to get sim recognised..46,000 in antutu on this build...
Yahoooooo!!!!
Thank you very much devs...bloody amazing
working
ok i can confirm that @TheSSJ twrp flashed CM successfully[made a clean wipe other than microsd]
mtp is buggy for me sadly,cant transfer more than 1 file
camera totally black..maybe i doing something wrong.. my bad,have to wait for few seconds,,camera working
as said by op,first boot not showing sims,,have to restart
wifi,bluetooth,network,message,settings are working....others didnt check
and thanks for everyone who made the hardwork for this CM12.1
using ZE551ML 2gb version
maback said:
Does the second sim card work? From what I understand this is not supported by Cyanogen.
Click to expand...
Click to collapse
I have two sim cards and both work for telephony. You can even call yourself to and from your phone!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Ingress, Polaris Office, Chase Mobile, Showbox...
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM @ http://get.cm/?device=Z00A
CyanogenMod for Z008/ ze550ml: ROM @ http://get.cm/?device=Z008
Recovery Links
Z00A
Official TWRP: TWRP.ME
Z008
Official TWRP: TWRP.ME
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps. Our resident x86 GAPPS guru @deadman96385 has been working with the opengapps crew to keep these current for us.
Flashable Modem updates:
Currently only supported in jrior001's unofficial TWRP
May or may not work in others
** see this post for more info **
Intel stores some modem firmware in the OTA's in a file labeled "ifwi.zip"
These are flashable zips to receive the updated firmware while staying on custom ROMS
**THIS IS A ONE WAY PROCEDURE, JUST LIKE THE OTA's THERE IS NO KNOWN WAY
TO FLASH BACK TO EARLIER MODEM FIRMWARE, PROCEED WITH CAUTION**
IF you still wish to proceed, current flashable ifwi zips are available HERE for Z00A AND Z008
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 13.0 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 2.20.40.16x stock base
Version Information
Status: Nightly
Created 2015-12-05
Last Updated 2016-09-07
Reserved
FAQ
Does Official TWRP work?
* Yep
* Unified recovery builds as of TWRP 3.0.0-0, same build for both Z00A/Z008
Can I use a custom kernel with these builds?
* At your own risk, don't complain here if something gets broken in the process
*Also, doing so makes any feedback useless to us because the kernel and the ROM are a complete package and changing part of that means you may have broken something beyond our control.
Will this be an Official ROM?
* When all the show stopping bugs are fixed and all the upstream commits are merged, yes.
* Until then, no because CyanogenMod has very high standards for accepting new devices.
* As of 3/17/16 we now have official builds
Do I need to unlock the bootloader?
* Yes.
Upgrade from CM-12.1 ?
* Tools have been put in place to make upgrading from 12.1 nightlies smooth however backups are always recommended. Make a backup and attempt upgrade from 12.1 -> 13.0. Make sure to Flash 6.0 gapps at the same time. 6.0 only applies the proper permissions for system apps on first boot.
* If the above fails to load smoothly, restore your backup, take the necessary backups of apps and such and make a clean flash upgrade instead.
EXTERNAL SDCARD in M
* There were major changes in AOSP in the handling of storage.
* Two options :
(1) used as external storage. Removable, plug and play storage like we all know and love.
(2) used as Adoptable storage. non removable, Sdcard becomes an extenstion of your /data partition. Removing Sdcard will cause signifigant data loss.
* On first boot you are presented with the option to choose how to handle your sdcard. CHOOSE WISELY
* read more about this feature in this article from android central
Green lines on Pixelmaster camera/Snapchat
* In the Asus camera app disable "Optimizations", this should clear green lines/distorted pictures here.
* In Snapchat, issue is far less intrusive and there is no workaround.
FM Radio
* Currently this is unsuported. As of yet we have not managed to figure out how Asus made this feature work. Should we figure that out We'd love to support it but until then it is not a high priority issue to resolve. ** UPDATED** I found some source code for the FM radio implementation but it's clearly marked as proprietary and unuseble by us at this time.
Call Recording
Native Call Recording is a feature that while only legal in some countries, has become very popular on CM.
Currently we do not have full audio HAL source for Intel devices and have no way to implement this in CM for this device.
C-APPS
They're are currently no C-APPS packages for CM-13. Due to the way M handles system app permissions this is not likely to be available at any time in CM13.
I'd like to make a donation
Support of this project is a joint effort between @crpalmer and @jrior001. Many users like to show support via Donations. If you feel so inclined to support us in this manner you can do so HERE(jrior001) and HERE(crpalmer). Donations are by no means expected, but always appreciated.
Reserved
Wow.. AWESOMEE.. Thanks Guyzz
Full wipe required when coming from 12.1?
Awesome!!! But... Must.. Resist... The urge.... Aauuggggh.
Updates issues and notes on upgrading from cm-12.1 .
RIL connectivity is not very good right now, requires manual setup on most sims. Clean install w/gapps is preferred, but CM team goes to great lengths to make sure upgrade path is smooth so a flash-able update from 12.1 nightly "should " work fine. Just make sure to flash your gapps w/ROM prior to rebooting. Flashing gapps later is not something that is going to work well for you.
jrior001 said:
Updates issues and notes on upgrading from cm-12.1 .
RIL connectivity is not very good right now, requires manual setup on most sims. Clean install w/gapps is preferred, but CM team goes to great lengths to make sure upgrade path is smooth so a flash-able update from 12.1 nightly "should " work fine. Just make sure to flash your gapps w/ROM prior to rebooting. Flashing gapps later is not something that is going to work well for you.
Click to expand...
Click to collapse
We have resolved the DRM video issue and the audio lag in games has yet to be an issue in cm-13 thus far.
I should be studying for a test, but........CM13 is coming first now
Sent from my ASUS_Z008 using XDA Free mobile app
Fantastic! Just Z00A for now?
Just finished the SAT. Came home to a welcome surprise!
troy5890 said:
I should be studying for a test, but........CM13 is coming first now
Sent from my ASUS_Z008 using XDA Free mobile app
Click to expand...
Click to collapse
550 version doesn't seem to be up yet, unfortunately.
kanagawaben said:
Fantastic! Just Z00A for now?
Click to expand...
Click to collapse
I manually ran a z00a build to test the setup. Assuming all goes well, there will be a z008 build tomorrow.
kanagawaben said:
550 version doesn't seem to be up yet, unfortunately.
Click to expand...
Click to collapse
We weren't going to do the thread till tom but somebody found the test build.... It will come, but probably not till next nightly cycle
Sent from my N5206 using Tapatalk
crpalmer said:
I manually ran a z00a build to test the setup. Assuming all goes well, there will be a z008 build tomorrow.
Click to expand...
Click to collapse
Thank you! No rush at all, of course.
---------- Post added at 11:44 PM ---------- Previous post was at 11:42 PM ----------
jrior001 said:
We weren't going to do the thread till tom but somebody found the test build.... It will come, but probably not till next nightly cycle
Sent from my N5206 using Tapatalk
Click to expand...
Click to collapse
Ditto, my comment above. Absolutely delighted it is coming, and happy to wait a bit longer. Thanks for your sterling work guys!
jrior001 said:
Updates issues and notes on upgrading from cm-12.1 .
RIL connectivity is not very good right now, requires manual setup on most sims. Clean install w/gapps is preferred, but CM team goes to great lengths to make sure upgrade path is smooth so a flash-able update from 12.1 nightly "should " work fine. Just make sure to flash your gapps w/ROM prior to rebooting. Flashing gapps later is not something that is going to work well for you.
Click to expand...
Click to collapse
yeah, i got that sim problem, but choosing manually worked, flashing this rom with open gapps worked fine
Seutp wizard has closed. Keep getting g that message. Back to 12.1.
How install super SU?
Awesome
I formatted my sdcard1 over and over... but my zen can't access it.
Any reason why?
Introduction
Sailfish OS is a mobile operating system combining the Linux kernel for a particular hardware platform use, the open-source Mer core middleware, a proprietary UI contributed by Jolla, and other third-party components.
Click to expand...
Click to collapse
This is a port of Sailfish OS to cancro (Xiaomi Mi3/Mi4), based on CyanogenMod 12.1.
What Works: https://wiki.merproject.org/wiki/Adaptations/libhybris#Smartphones (Check Xiaomi Mi3)
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 new:
Updated to Sailfish 2.1.3.7
Click to expand...
Click to collapse
Known issues:
1) Wifi mac address not detected properly
Click to expand...
Click to collapse
Current TODOs: Sailfish OS on cancro's Trello Board
Download links:
Cyanogenmod 12.1 base: https://www.androidfilehost.com/?fid=529152257862691291 (Mirroring this, as CM servers are shutting down)
Sailfish OS rootfs: https://www.androidfilehost.com/?fid=817906626617953262
Click to expand...
Click to collapse
Installation Instructions:
NOTE: This release is also available as an OTA to existing users.
1) Make sure your device has the new partition layout needed for Android M and a custom recovery. Boot to Recovery, wipe cache, dalvik-cache, system and data. ( https://jrizzoli.github.io/dotfiles/ )
2) First install cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-cancro.zip As your base ROM, and make sure it works well.
3) Then Install sailfishos-cancro-release-2.1.3.7-beta.zip on top of it. This will replace your boot image with sailfish boot image, and installs sailfish os to /data/.stowaways/sailfishos . The installation can take a little while, so be patient.
If you are already running, CM12.1 YOG7D/already have SailfishOS installed, you can simply flash the Sailfish OS without wiping flash/partition.
Click to expand...
Click to collapse
Big kudos to @mixmoto and Nokius, for patiently testing this release over and over.
P.S Thank you all for your support. I really really appreciate it - and it's what motivated me to make some time in my busy days to create this release. Wish you all Happy Holidays!
XDA:DevDB Information
Sailfish OS for cancro, ROM for the Xiaomi Mi 3
Contributors
saidinesh5, Ar4er, Folks at #sailfishos-porters, especially @mal-
Source Code: https://github.com/CancroSailors
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Must have CM12.1-YOG7D
Based On: CyanogenMod 12.1-YOG7D
Version Information
Status: Alpha
Created 2016-09-15
Last Updated 2018-01-07
Hey Dinesh,
Thanks for your work,
does this have sfdroid support?
Ekril said:
Hey Dinesh,
Thanks for your work,
does this have sfdroid support?
Click to expand...
Click to collapse
Hey, Nope. SFDroid support is on my TODO list for now.
It may take a while though. I need a Multirom working with CM13.0(which is my primary ROM), so I can safely port all the needed changes for SFDroid to my CM12.1 base without losing all my data. Any help welcome here!
Cheers
saidinesh5 said:
Hey, Nope. SFDroid support is on my TODO list for now.
It may take a while though. I need a Multirom working with CM13.0(which is my primary ROM), so I can safely port all the needed changes for SFDroid to my CM12.1 base without losing all my data. Any help welcome here!
Cheers
Click to expand...
Click to collapse
Thank you!!! this is awesome!!
Almost everything it seems to be working :good:
Is it stable for daily use?
Rocketval said:
Thank you!!! this is awesome!!
Almost everything it seems to be working :good:
Is it stable for daily use?
Click to expand...
Click to collapse
Great!
Right now i don't think it's ready for daily use yet, as sometimes my device's sensors and audio stop working randomly. Not sure if it is just my device though (because of some weird hacks I've been using).
I suspect this maybe because the CM 12.1 zip i was using to boot differs from the sources I've used to compile this rom. Once that issue is fixed, i think this will be usable for daily use. Camera works, Browser works, basic apps work.. And compiling that cm 12.1 means even sfdroid will work ...
saidinesh5 said:
Great!
Right now i don't think it's ready for daily use yet, as sometimes my device's sensors and audio stop working randomly. Not sure if it is just my device though (because of some weird hacks I've been using).
I suspect this maybe because the CM 12.1 zip i was using to boot differs from the sources I've used to compile this rom. Once that issue is fixed, i think this will be usable for daily use. Camera works, Browser works, basic apps work.. And compiling that cm 12.1 means even sfdroid will work ...
Click to expand...
Click to collapse
For what I know only few cm12 builds worked fine when flashed before sfos..
Maybe you need another build.. I don't know..
Rocketval said:
For what I know only few cm12 builds worked fine when flashed before sfos..
Maybe you need another build.. I don't know..
Click to expand...
Click to collapse
Could be. Most bugs i had to fix last week were because of differing versions too. That's why I'm trying to compile a cm12.1 right now.
Also right now as I'm on CM13.0, i was just using a system.img from the CM12.1.zip.. And making sailfish loop Mount that as the actual /system/ . not sure if that's causing any issues.
Right now my options are port multirom to CM13.0 (having some weird errors there) or wipe my device clean and downgrade to CM12.1 (have been trying to avoid this for months now!).
saidinesh5 said:
Could be. Most bugs i had to fix last week were because of differing versions too. That's why I'm trying to compile a cm12.1 right now.
Also right now as I'm on CM13.0, i was just using a system.img from the CM12.1.zip.. And making sailfish loop Mount that as the actual /system/ . not sure if that's causing any issues.
Right now my options are port multirom to CM13.0 (having some weird errors there) or wipe my device clean and downgrade to CM12.1 (have been trying to avoid this for months now!).
Click to expand...
Click to collapse
Yeah, we definetely need multirom, with 64gb mi4w I have more than 32+ free and a lot of will to try
Thank bro
Thank you!!!
As a temporary fix for radio, pulseaudio could be restarted, NOT as root.
Code:
systemctl restart pulseaudio --user
adeen-s said:
As a temporary fix for radio, pulseaudio could be restarted, NOT as root.
Code:
systemctl restart pulseaudio --user
Click to expand...
Click to collapse
I currently use this command everytime i wanted the FM radio to work. I will have to look into why this is failing by default though
Code:
$pactl set-source-port source.primary input-fm_rx
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Dr. Ramm said:
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Click to expand...
Click to collapse
this isn't android, you cannt flash gapp
Dr. Ramm said:
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Click to expand...
Click to collapse
Due to legal reasons, Sailfish OS doesn't bundle the proprietary blobs(device drivers, system libraries etc..) provided by the phone vendors in it's zip.
As I have compiled Sailfish OS using sources from CM-12.1, it tries to access these proprietary files on your device via. CM-12.1 libraries. That's why you have to flash a CM-12.1 zip first, before flashing Sailfish OS. (i.e just clean flashing sailfish.zip won't work)
As of now, you don't have to flash gapps, as there is no way to use them from Sailfish OS. Once we get sfdroid running, we can run Android apps from within Sailfish OS, then you can flash gapps if you want.
Sailfish OS already comes with an su binary (accessed via. devel-su command) and full root access. So, you won't need Super SU.
saidinesh5 said:
As I have compiled Sailfish OS using sources from CM-12.1, it tries to access these proprietary files on your device via. CM-12.1 libraries. That's why you have to flash a CM-12.1 zip first, before flashing Sailfish OS. (i.e just clean flashing sailfish.zip won't work)
Click to expand...
Click to collapse
got it
saidinesh5 said:
As of now, you don't have to flash gapps, as there is no way to use them from Sailfish OS. Once we get sfdroid running, we can run Android apps from within Sailfish OS, then you can flash gapps if you want.
Click to expand...
Click to collapse
Stock market not working (as u say in 1st post) but how i can install some apps?
saidinesh5 said:
Sailfish OS already comes with an su binary (accessed via. devel-su command) and full root access. So, you won't need Super SU.
Click to expand...
Click to collapse
nice
run very smooth on my mi3
Dr. Ramm said:
got it
Stock market not working (as u say in 1st post) but how i can install some apps?
nice
Click to expand...
Click to collapse
You can use https://openrepos.net/content/basil/warehouse-sailfishos app to install apps.. I will include this in the zip for the next build (Which will soon be available).
First enable installation of untrusted software in Settings, then download the latest rpm of that from your browser and install it.
saidinesh5 said:
You can use https://openrepos.net/content/basil/warehouse-sailfishos app to install apps.. I will include this in the zip for the next build (Which will soon be available).
First enable installation of untrusted software in Settings, then download the latest rpm of that from your browser and install it.
Click to expand...
Click to collapse
can u tll me where located screenshots and how i can upload it on pc
some screens is here
after turn off mi3 10s, i dont turn on device
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Live Display (color calibration) not working yet
Screen recording not working
Chromecast screen mirroring not working, native casting works though.
factory reset from setting menu has been reported to cause recovery boot loops.
Battery life is horrible, numerous display wakelock issues
CM14 (not device specific issues)
No CMTE yet
Status bar icon changing broken
CM file manager has trouble accessing external sdcard
Battery profile is non functional/string errors
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM
CyanogenMod for Z008/ ze550ml: ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code: https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-22
Reserved
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
CM 14.1 from Stock MM
1) Unlock Bootloader
2) Flash compatible TWRP
3) Perform desired backups
4) From recovery, factory reset & install ROM & 7.1 GAPPS
5) Enjoy!
CM 14.1 from CM13 Mm based beta builds
1) Reboot to TWRP( should already have good version)
2) Flash CM14.1 and 7.1 GAPPS
3) Reboot and enjoy!!
Yes!!!
yes u made it sir.. most awaited build of the year.. we really appreciate your time and efforts given to the project.. May God bless you.. behalf of all the zf2 a big thanks to @jrior001 and @say99
Sent from my ASUS_Z008 using XDA-Developers mobile app
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
leoarten said:
just a question. Do i need to be on MM Bloobs or can I upgrade straight from LP bloobs? Also has the Brazilian sensors bug been fixed on CM14.1?
Click to expand...
Click to collapse
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Awesome!
Downloading...
Downloading now.
Is the camera bug still present on N? Shouldn't the MM BLOBS fix that?
Thanks for your effort, @jrior001 !!!!
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
leoarten said:
Thanks.. but just to clarify.. I need to update bootloader to MM Blobbs before I install CM14 right? or just flash new TWRP and flash rom as per usual (from LP Bloobs)? Im a bit confused.. Yes I saw theres a MM Bloobs session.. but couldnt find the answer to this.
Awesome work btw
Click to expand...
Click to collapse
Direct from post #2:
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
Sent from my ASUS_Z00A using Tapatalk
Thank you very much..
jrior001 said:
Direct from post #2:
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks for your job, but no sensors found in brazilians devices...
ysllan said:
Thanks for your job, but no sensors found in brazilians devices...
Click to expand...
Click to collapse
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Is there Xposed for CM 14?
yumms said:
Is there Xposed for CM 14?
Click to expand...
Click to collapse
Nope right now. Just stay tuned for updates from rovo's thread.
Sent from my ASUS_Z00A using XDA Labs
jrior001 said:
Not that I can do anything about Asus's fail here but I'd like to see a logcat & dmesg captured from boot on this issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Did you use the 144 blobs? Asus solved problems with this version.
Enviado de meu ASUS_Z00A usando Tapatalk
I'm sorry to be a pain in the ars*. But you've mentioned you're basing on .144 stock update right? Having said that the link you posted with the zip to update bootloader Ive found files mentioning 4_21_40_134.bin (.134) wouldnt this be the reason sensors arent still working for brazilians devices? I had a look at Asus website and this is fix has been implemented on .144 update. So is this update on script and files updating bootloader or are they on the ROM itself..
Now I know the rules on XDA and I wouldnt dare to ask for ETA, however if this is the case, I would ask very politely if you could update the scripts files to .144 whenever's convenient for you and whenever you have time. That would be much appreciate. I will be coming back to this post and will be waiting anxiously for this.. Take you time and Thank you again.
jrior001 said:
Has this been resolved in stock? I've heard mixed reports. I've included the updated sensor firmware from the .144 stock update so if it's in there we got it.
See post 2 as I update it, gonna try trying o cover all possible situations in guide there.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
jrior001, crpalmer, say99 are best!)) Makes backup and installed
see, told you guys that it will be soon please take use of logcat whenever you guys are reporting some issue, we won't be able to do anything without logcat if we can't produce it on our device. Enjoy people
jrior001 said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Ingress, Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml:ROM
CyanogenMod for Z008/ ze550ml:ROM
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code:https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Beta
Beta Release Date: 2016-11-09
Created 2016-11-09
Last Updated 2016-11-09
Click to expand...
Click to collapse
haha thx so much bt wechat isnt working too haha
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* 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.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on find7
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want. Recommended nano package)
Official root addon
LineageOS Extras
Changelog:
Changes for find7
Bug reports:
How to submit a bug report
LineageOS JIRA
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 15.1 for Find7a/s, ROM for the Oppo Find 7
Contributors
mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any version of ColorOS. Unified storage not supported.
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-07-09
Last Updated 2018-11-15
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Am having problem of cold start gps. Takes about 8-10 mins before locking in. However, once lock in,everything work perfectly.
Updated on 18july.now everything is perfect. Even the battery life got better.
thank you???
luckywang95 said:
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Click to expand...
Click to collapse
You can delete the storage check in the installer script. Did it before and worked fine. I'm gonna try it tonight with this build.
Update: Stucked in bootloop. Gonna try tommorow again.
Update#2: Here is my working solution:
1. Flashing rom
2. Flashing addonsu
3. Flashing openGapps micro
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Zoltan-X said:
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Click to expand...
Click to collapse
Are you serious? These are just simple apks for the styles you can change from display settings.
If you are so curious about "being hacked" look at the source: https://github.com/LineageOS/android_packages_overlays_Lineage
Curios i've had in those app a data collecting folder structure,
like db, files, and more, maybe a rootkit on my device???
I don't know, since i removed those my find7 works again really well,
what it didn't do since a long time in this year....
With best regards
Code looks fine and i'll recheck if the image was compromised or not or how, but later these days.
thank you for the quick hint to those files!
P.S.: I've dirty reflashed the image i used to install lineageOS, after the expected remove, and no these nightly seems not been compromised,
Sorry for the alert,
but in the last days many hacks occured in my private relationships with my dearest, so I was a little curios, but seems now clean on my device!
Thank You verry much,
and Kudos Kudos Kudos to your quick hint reply.
I just installed lineage-15.1-20180806-nightly-find7-signed.zip to replace my stock Oppo Find7 firmware on the weekend and after a few days with it, so far so good! I had to lose the LVM unfortunately, but I'd rather have an up to date OS.
The battery life seems shorter than the stock firmware. I can still get through the day, but down to 40 or 50% or less by 6PM instead of much more with the stock Oppo FW. I haven't tried tweaking any battery life settings yet though.
Two minor things with the install compared to the LineageOS howto - the SD card path was different to what was documented ( /internal_sd not /sdcard) , and I had to install open_gapps-arm-8.1-pico-20180812.zip (pico instead of the documented nano version)... but this was minor stuff and I got where I wanted to go.
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
knusto said:
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
Click to expand...
Click to collapse
Wooot ! They have nougat builds for find 7
hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
It will be fixed in next build.
mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Thank you so much. Can't wait
hexplor said:
Wooot ! They have nougat builds for find 7
Click to expand...
Click to collapse
AOKP is now on Oreo for Find 7
mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Got the latest build. All fine Thanks
Allthough its not supported i've got unified working. not reliable tho. the only way i got it working when flashing los and direct rebooting into recovery again and then flashing the cm-13.0-find7-unified-storage-patch.zip from the according thread. cuz the original link is dead incl mirror i got my copy uploaded to gdrive here. https://drive.google.com/file/d/1sZ72qUD5P7qL4tsIF3MB-cQk9x9pamRR/view?usp=sharing
only drawback being you cant reboot anymore cuz that will somehow give you the your-sdcard-is-****ed message. havent found a reasonable routine so i guess you'll have to try your luck yourself and maybe give feedback?
Hi, could you disable CABC(Content Adaptive Brightness Control) or provide a way to disable it? The hardware of Find 7 use it and it really makes some troubles, brightness, color. Really thanks if you have that time
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Manas1796 said:
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Click to expand...
Click to collapse
That commit has already been applied for Find7 - https://github.com/LineageOS/androi...mmit/80e1e7e5ffca2c69730eecc8c498423c2ea48463