Develop Bugs

[ROM][CAF][D802/D805][6.0] CyanogenMod 13.0 [UNOFFICIAL]

Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
Changelog:
Code:
2015-11-17
- New sepolicy.
- Boringssl wrapper removed.
- Otg storage fixed.
2015-11-18
- Bring back boringssl wrapper to fix camera.
2015-11-21
- Device tree synced with cm repo.
- Sony thermanager removed.
2015-11-24
- Device tree synced with cm repo.
2015-11-25
- Device tree synced with cm repo.
- Facebook crash is gone.
- Kernel: Use interruptible waits to fix high load average
2015-11-26
- Sync with cm source
2015-11-28
- Camera fix
- r/w mount fix
Known Issues:
Bugs from CM12.1 (Random vibration, low speaker volume, etc...).
These are very-pre-experimental builds, issues may happen.
How to install:
Download ROM
Download GApps
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Select "Install zip from SDCard"
Choose the bootstack zip file
Choose CM13.0 zip file
Choose GApps zip file
Reboot system
DOWNLOAD ROM
DOWNLOAD GAPPS​
Facebook fix: delete or rename the libsslx.so from /data/app/com.facebook.katana-1/lib/arm and from /data/app/com.facebook.orca-1/lib/arm
Click to expand...
Click to collapse
Sources:
Device: https://github.com/victormlourenco/android_device_lge_g2-common/tree/cm-13.0
Kernel: https://github.com/victormlourenco/android_kernel_lge_msm8974/tree/cm-13.0-stock
XDA:DevDB Information
[ROM][CAF][D802/D805][6.0] CyanogenMod 13.0 [UNOFFICIAL], ROM for the LG G2
Contributors
Rick Roll
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-11-16
Last Updated 2015-11-25

Thanks.
Waiting for reviews. Can anyone tell if this ROM has the same sound skipping issues which happen on Lollipop?

Downloading

Does this rom support latest version of xposed?

sheikhramnuj said:
Does this rom support latest version of xposed?
Click to expand...
Click to collapse
yes

Thanks for these builds - please add the random vibration vibration bug to the known bugs list.

@Rick Roll, thanks for sharing such an early version of CM13 Tried it for less than hour, it looked quite solid and quick. Any bugs will be ironed out later, probably.
I only found out that changing dpi is quite hard, because we can't mount system as rw. However, it's possible in recovery. Layers won't work because of the same reason.

Hbohd said:
I only found out that changing dpi is quite hard, because we can't mount system as rw. However, it's possible in recovery...
Click to expand...
Click to collapse
sorry to bore you... but can you explain a bit more... I use to change system fonts plus other small things such as dpi, modded hosts file, etc... but as you know /system partition isn't re-mountable as RW
You suggest to do it from recovery, I tried but adb shell won't start from recovery... can you give me some hints? thank you :good:
driver issue perhaps? even if adb shell works regular (booted phone)
EDIT: never mind found solution... I had to install adb universal drivers (downloaded from here: http://adbdriver.com/downloads/)
thank you anyway

Many days ago i was on stock lolipop 5.0.2, rooting in that time and used Autorec v2 to flash TWRP recovery.
Question is - this ROM will boot on my autorec TWRP recovery 2.8.6.1?
I'm now on CM 12.1 Official

Radac Stunghthumz said:
Many days ago i was on stock lolipop 5.0.2, rooting in that time and used Autorec v2 to flash TWRP recovery.
Question is - this ROM will boot on my autorec TWRP recovery 2.8.6.1?
I'm now on CM 12.1 Official
Click to expand...
Click to collapse
I've your same recovery, no problem here
just be sure to remove after flash and before reboot (within the recovery I mean) the apk under /system/app/qualcomm folder (use file manager included in recovery under "advanced")
for gapps you should use opengapps (opengapps.org), choose 6.0 and I suggest to start with a smaller package (I tried micro & nano and both worked)
good luck!

Any chance for d800?
Sent from my LG-D800 using Tapatalk

suiller said:
I've your same recovery, no problem here
just be sure to remove after flash and before reboot (within the recovery I mean) the apk under /system/app/qualcomm folder (use file manager included in recovery under "advanced")
for gapps you should use opengapps (opengapps.org), choose 6.0 and I suggest to start with a smaller package (I tried micro & nano and both worked)
good luck!
Click to expand...
Click to collapse
I haven't removed this apk and it still booted fine bro!

Good rom
But not very stable

For now it all seems to be ok, the ROM is stable, no random reboots, no lags, everything works (Facebook from Play Store works), the only two bugs I found are the editing of the navigation ring targets, and the low quality of microphone recordings in WhatsApp (I don't know if it's only in WhatsApp or in calls too).
I'm using the build of 16/11.
EDIT: Camera is not working, neither AOSP Camera nor Google Camera, I'll try Lenovo Camera or the new build of 17/11.

I try to flash cm13 zip files for 4 times with old twrp, 1 times with latest twrp. But there is no changes. Everytime I have try to flash cm13, It giving error "Failed" with "Invalid checksum for partition /dev/block/platform/msm_sdcc.1/by-name/aboot" "E: error executing updater binary in zip '/sdcard/cm-13.*-20151117-UNOFFICIAL-d802.zip'" "Error flashing zip 'sdcard/cm-13.0-20151117-UNOFFICIAL-d802.zip" "Updating partition details..." "...done" And failed.
How can I fix it?

Markster93 said:
EDIT: Camera is not working, neither AOSP Camera nor Google Camera, I'll try Lenovo Camera or the new build of 17/11.
Click to expand...
Click to collapse
apart some FC on close... snap camera (on playstore) works very well
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Heroata said:
I try to flash cm13 zip files for 4 times with old twrp, 1 times with latest twrp. But there is no changes. Everytime I have try to flash cm13, It giving error "Failed" with "Invalid checksum for partition /dev/block/platform/msm_sdcc.1/by-name/aboot" "E: error executing updater binary in zip '/sdcard/cm-13.*-20151117-UNOFFICIAL-d802.zip'" "Error flashing zip 'sdcard/cm-13.0-20151117-UNOFFICIAL-d802.zip" "Updating partition details..." "...done" And failed.
How can I fix it?
Click to expand...
Click to collapse
if you have 802 model you should 1st flash this:
https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802

suiller said:
apart some FC on close... snap camera (on playstore) works very well
https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802
Click to expand...
Click to collapse
Are you using the 16/11 build or the 17/11 build?
EDIT: Anzi, visto che sei italiano, stai usando la build del 16 novembre o quella di oggi?

Markster93 said:
Are you using the 16/11 build or the 17/11 build?
Click to expand...
Click to collapse
I live in italy but I'm not italian
anyway 16th nov
you have to flash an hybrid-caf bootloader, I had a similar issue... didn't remember exactly the error but I think was that
If you have a D802 model the one I posted is the correct one

suiller said:
apart some FC on close... snap camera (on playstore) works very well
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
if you have 802 model you should 1st flash this:
https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802
Click to expand...
Click to collapse
I did already.

suiller said:
I live in italy but I'm not italian
anyway 16th nov
you have to flash an hybrid-caf bootloader, I had a similar issue... didn't remember exactly the error but I think was that
If you have a D802 model the one I posted is the correct one
Click to expand...
Click to collapse
It still doesn't work

[ROM][MASTER][6.0.1] AOSP Master Branch Built by Khaon

AOSP MASTER BRANCH FOR MANTA DEVICE
Hello everyone, you can download on XDA many good ROMS but each of them are based on "stable" android releases. That's why I chose to share something else.
I am offering a master branch build
Why use master branch ?
clang 3.8 | daily updates | java 1.8
instructions :
reboot to twrp recovery ( you can use mine if you want to use f2fs or having issues flashing my packages)
flasy my package
reset factory and IF YOU COME FROM ANOTHER DISTRIBUTION delete /sdcard/Android/data folder
flash gapps package ( I recommend opengapps)
reboot
I recommend people to factory reset time o time because of the master branch, it can be required to remove some bugs
What is not working/bugging for now
ROOT: latest supersu are patching the boot image and this doesn't work currently with my master branch releases. You need to use SuperSU v2.56
MXPlayer: for some reasons mxplayer doesn't find libcutils.so while it does exists. So for now, you gotta to use some alternatives: vlc, or what ever
Download link​
Sources
How to use AdwAway
In oder to get AdAway working you need to do the following:
1/ Set a file at
Code:
su/su.d
with the following content
Code:
mount -o bind /su/etc/hosts /system/etc/hosts;
2/ Make an empty host file at
Code:
/su/etc/hosts
I think you can find a working flashable package doing this on the unoffical adaway thred
XDA:DevDB Information
AOSP Master Branch for Manta, ROM for the Google Nexus 10
Contributors
Khaon
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2016-04-22
Created 2016-01-27
Last Updated 2016-04-21

Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!

PainToad said:
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
Click to expand...
Click to collapse
This is not 100% PURE aosp.
The base is aosp master branch. I have included some several extra such :
bootanimation
long press recent switches to latest app
led
...
Well nothing much.
The only critical thing I have touched is android permission : I override user's permission for google play service for the location permission access: otherwise it crashes.

I have uploaded a new build.
Too much changes to display here the changelog.
If you want extra tracking you should head here
To me, the main change, is clang prebult updated!

OP updated, root is now working.

I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?

ace9988 said:
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
Click to expand...
Click to collapse
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?

Khaon said:
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Click to expand...
Click to collapse
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.

ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
HmHm it is kinda late for me ( european timezone) but I have no issues using app requesting SU rights. I will take a look however at it tmr.

Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says

Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
what opengapps version did you isntall ?
I am using pico, and I have no issue flashing it.

ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
How is your supersu status ?
I have no issue with su.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
I was reported an issue when formating to f2fs rebooting to the rom would format the userdata partition.
I investigated the AOSP code source and some commit format the partition if it fails mounting. Ofc trying to mount a f2fs partition with ext4 is considered as a fail...
Flashing my standalone kernel permit to pass that issue : my stand alone kernel will transform ext4 entries to f2fs(and vice versa) depending on the actual underlying fs.
The current release I am using features fixes for this, however, something broke the libsensors, so I need to find out what.

Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
Ewww, it should work ! Any other informations ? such logs ?
-----------------------------------------------------------------------------------------------------------------------------------------------------------
I am uploading a new build, I had issues for days with the builds.
Please tell me if you got bootloop on reboot. From what I saw bootloops do not longer exist.

I uploaded a new build.
It features master branch 02/21 with my latest kernel.
You just need latest opengapps for marshamallow and supersu 2.56.
Have fun.

All I see is one dated 2/5?
Sent from my Nexus 10 using XDA Free mobile app

"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.

Der_Graf said:
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Click to expand...
Click to collapse
Grant play service the location permission and it will be fixed.

Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
I had this issue sometimes when installing the Rom and gapps in the same queue.. Installing the gapps seperatly afterwards worked then.. Try this out

Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.

Der_Graf said:
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Click to expand...
Click to collapse
@Der_Graf
Hehe sorry for you this issue happens, the real culprit is Google. Since MM, the dev got to ask permission if not given. Google Play Frameworks/Service doesn't ask for this. So that's why you got FC. You should try after a Factory Rest- you need to that anyway when coming from another ROM- not installing Gapps in order to not have the first setup screen where you will get stuck because of the fc's spam.
Then Install gapps, and, since you will boot on the Home Screen, you should be able, with some pain, to get access to the app menu to get Location permission for Google Play Services.
Then, for any upgrade install, you won't have issues as the permission is already granted.
I know this sucks, but I tried to force give the permisison and it doesnt work :angry:
Ewwwww.
I wanted to share my latest build, as of the 25th feb, but NFC is broken and makes continuous FC'S, this appears also on my friend nexus 6's device, which is still supported by Google. So this is the bad news I've got to understand why this happens, well until Google fixes it or I find the culprit.
However, the good news is, that this friend, maintains more extra features then I do, so the next releases will feature more extra features

[ROM] [6.0.x] [BETA] Unofficial CyanogenMod 13.0 Nightly Builds (KIW-L24 / L22 / L21)

CyanogenMod 13.0 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.
Note: This thread is not about:
- Other devices!
- General Honor 5X stuff (Unlocking, Emui, going back to Stock, Updating Stock...)
- Aliens, UFOs, ...
-> Generally: ANYTHING not specifically about CyanogenMod 13.0 for Honor 5X
Important Notice:
Code:
As of July 19, an upgrade of the firmware to MM-Firmware is required ([URL="http://forum.xda-developers.com/showpost.php?p=67840582&postcount=1813"]Link to instructions[/URL],
possibly find your firmware update here: [URL="http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288"]LINK[/URL] - note: not related to us, thanks @clsA).
If you run a device below the required firmware,
flashing will fail due to checks in the upgrade package! (No, you shouldn't remove the checks!)
In that case please use a build of July 18 or below. (Link: [URL="https://www.androidfilehost.com/?w=files&flid=72880"]clsA's repo[/URL])
Please DO NOT complain about this, we are not responsible for non-released firmwares
and other things not directly under our control. Please also DO NOT ask for any support
of firmware update in this thread! Go to Q&A section and create or use an existing thread there!
Preparation
To make sure you can run the builds from July 20 and up, please do the following
(For all commands please copy everything between the quotes not including them! All commands require to press [ENTER] to execute)
1) Open the terminal app or connect via computer and type "adb shell"
2) Type "su"
3) Type (or copy)
strings /dev/block/platform/soc.0/7824900.sdhci/by-name/tz | sed 's/QC_IMAGE_VERSION_STRING=//p;d'
4) Compare the output to:
TZ.BF.3.0.C3-00025
5) Are they equal? Go on with the instructions and use a newer build
They are different? -> Go with build of July 18
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
1) Read this post completely! Make sure you are aware of the issues!
2) Download the zip(s).
3) Install a compatible Recovery (e.g. TWRP (Link))
4) Perform a NANDroid backup of your current ROM (Optional)
5) Wipe data & cache partitions of your device (required when coming from stock!).
6) Flash CyanogenMod.
7) Optional: Install the Google Apps addon package. (Pay attention to the note in "Download links"!)
Changelog
Device tree
Kernel tree
Generic CM tree
Broken Features / Known Issues
camera does not support HDR photos - no need to try other camera apps, it's disabled completely!
dt2wake doesn't use the proximity sensor to filter bogus d2twake triggers and therefore can turn on too easily in your pocket,
but it DOES work without proximity sensor
Builds older than July 20: fingerprint sensor not implemented! (Do not even ask for it, search the thread!)
smart view case support
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.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), use adb or any other file explorer tool to pull a copy of
/sys/fs/postore/console-ramoops
after the reboot and provide that.
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)
Download Links
CyanogenMod: ROM @ http://download.crpalmer.org/nightlies/kiwi-cm-13.0
Google apps addon:
(Note: Not required to run the ROM)
We are using Open GApps (Link) Arm64 version. (make sure to use 64bit when using other packages), others might also be working
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
Note: If you install a package which replaces the default dialer (mostly "Stock Gapps") you have to go to Settings->Apps->Gear-Icon and set the new dialer as a default telephony app to prevent force closing of apps
XDA:DevDB Information
CyanogenMod 13.0 Builds, ROM for the Honor 5X
Contributors
crpalmer, BadDaemon
Source Code: https://github.com/CyanogenMod/android_kernel_huawei_kiwi
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Created 2016-03-25
Last Updated 2016-07-27

Reserved
Known Issues:
Moved to first post (above).
Other Issues:
If I don't list it as a known issue, it means I do not think it's a problem because I have never encountered whatever you think is broken.
If you post "_____ is broken", I will ignore it unless you:
* Provide appropriate logs
* Provide clear instructions to reproduce the problem or a statement that it just randomly happens
* Have the problem on a "clean" install (see below).
Getting Logs:
You can use SysLog by Tortel from the play store to get logcats (Main Log), dmesg (Kernel log) and Radio Logs. These will capture the log after the fact. You can also get the logs via adb:
PHP:
adb logcat -v time -d > logcat.txt
adb logcat -v time -b radio -d > radio.txt
adb shell dmesg > dmesg.txt
You can use either a file explorer app that allows root access or adb to get the last kernel log. Via adb you would plug your phone into a computer that has adb access to it and run
PHP:
adb root
adb pull /sys/fs/postore/console-ramoops
Appropriate Logs:
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), the only log that will contain useful information if the last kernel log. All other logs are cleared on a reboot and will be useless.
If you have any issue with telephony, wifi, bluetooth or anything related to externally communicating via your phone, please provide all 3 logs (logcat, radio log and kernel log).
If you submit radio logs, please do so via a PM as the logs may contain phone numbers and other information such as your IMEI.
Clean Install:
If you have a reproducible problem:
* Backup your current install in twrp (so you can go back to it, if you want, when you're done)
* Factory reset
* Wipe system
* Install CM, install GApps (and not one that replaces system apps like the camera, especially if you think the camera is broken!)
* Do not install anything else, do not restore anything else via Google, Titanium Backup, etc.
* DO NOT INSTALL Xposed
* Install the apps that you need to reproduce the problem
* Collect logs
* Restore your backup
If the problem is not reproducible, you still need to run on a clean install and wait for it to happen. In this case do:
* Backup your current install in twrp (so you can go back to it, if you want, when you're done)
* Factory reset
* Wipe system
* Install CM, install GApps (and not one that replaces system apps like the camera, especially if you think the camera is broken!)
* Do not install anything else, do not restore anything else via Google, Titanium Backup, etc.
* Install the apps that you need on your phone via Play Store and do not restore data from anywhere or install any other tweaks, scripts.
* DO NOT INSTALL Xposed
* Wait for it to happen
* Collect logs
* Restore your backup
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)

Reserved

So happy to see marshmallow come to this amazing device. Many thanks to all contributing

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
Thanks @crpalmer. You might want to change above to 6.0.x
Sent from my A0001 using Tapatalk

Keep getting "App not responding" every few minutes. Not sure if I'm the only one.

Going to flash it right now; fingers crossed.
Thanks for your work @crpalmer

InfamousGam3r said:
Keep getting "App not responding" every few minutes. Not sure if I'm the only one.
Click to expand...
Click to collapse
Same Issue, Facebook and Messenger.

Damn bro... You're amazing.... I would love to taste marshmallow on this device but i think I'll refrain until some important bugs are fixed.... Thnx a lot for your hard work
Sent from my KIW-L21 using Tapatalk

Elmerdus said:
Same Issue, Facebook and Messenger.
Click to expand...
Click to collapse
Yep, exact same problem[emoji14]Facebook and Messenger seem to be giving that error on cm13 3/24/16
Sent from my KIW-L24 using Tapatalk

Amazing work this is the first time I'm actually using marshmallow . The rom feels a bit slower than the lolipop version, but hey having shower in the acid feels better than using the stock rom.
right now the battery indication seem to be stuck at 100%, need to reboot to check if it is actually valid.
Battery works now I have to allow all this user permissions
---------- Post added at 09:31 AM ---------- Previous post was at 09:23 AM ----------
InfamousGam3r said:
Yep, exact same problem[emoji14]Facebook and Messenger seem to be giving that error on cm13 3/24/16
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
mine works pretty well for messenger and.... restoring facebook..... yup works perfectly; I'm using custom booster so maybe?

nemexs said:
Amazing work this is the first time I'm actually using marshmallow . The rom feels a bit slower than the lolipop version, but hey having shower in the acid feels better than using the stock rom.
right now the battery indication seem to be stuck at 100%, need to reboot to check if it is actually valid.
Battery works now I have to allow all this user permissions
---------- Post added at 09:31 AM ---------- Previous post was at 09:23 AM ----------
mine works pretty well for messenger and.... restoring facebook..... yup works perfectly; I'm using custom booster so maybe?
Click to expand...
Click to collapse
What do you mean "custom booster"? I was coming from CM12.1 with GApps Arm64 5.1 Minimal, updated to CM13 (3/24/16) and GApps Arm64 6.0 Micro

InfamousGam3r said:
What do you mean "custom booster"? I was coming from CM12.1 with GApps Arm64 5.1 Minimal, updated to CM13 (3/24/16) and GApps Arm64 6.0 Micro
Click to expand...
Click to collapse
skynet project
http://forum.xda-developers.com/android/software-hacking/android-l-booster-1-soon-t3030796
The apps that didn't run properly from the titanium I reinstalled them.
For developer: Battery indicator is bugging out again, rebooting........ same problem, removed the gravity box [MM]; busybox has a problem too. Ok Google seems to crash every time I reboot.
Workaround the batter indicator bug: if you are plugged to a power charger the indicator works perfectly.
Update: busybox works with graphics just crashing, but app working well.

nemexs said:
skynet project
http://forum.xda-developers.com/android/software-hacking/android-l-booster-1-soon-t3030796
The apps that didn't run properly from the titanium I reinstalled them.
For developer: Battery indicator is bugging out again, rebooting........ same problem, removed the gravity box [MM]; busybox has a problem too. Ok Google seems to crash every time I reboot.
Workaround the batter indicator bug: if you are plugged to a power charger the indicator works perfectly.
Click to expand...
Click to collapse
Going to try and use that custom booster you linked me to, reinstalling CM13 again (reverted back to CM12 earlier because of a few issues). Doing it all fresh this time, just hate having to re-arrange my stuff haha.
Thanks,

@crpalmer , call recording works on cm13 .
Doze is working fine .
Major bugs are battery status and all CPUs online .
If you could fix this , cm13 comes to use as a daily drive .

Still getting "Unfortunately, *APP* has stopped." on CM13 3/24/16. Clean install. CM13 > GApps Arm64 6.0 nano

InfamousGam3r said:
Still getting "Unfortunately, *APP* has stopped." on CM13 3/24/16. Clean install. CM13 > GApps Arm64 6.0 nano
Click to expand...
Click to collapse
Are you l24 or l21? :/
http://opengapps.org/ This one? arm64 6.0 nano works fine for me

nemexs said:
Are you l24 or l21? :/
http://opengapps.org/ This one? arm64 6.0 nano works fine for me
Click to expand...
Click to collapse
KIW-L24
and... OpenGapps ARM64 6.0 nano.

InfamousGam3r said:
KIW-L24
and... OpenGapps ARM64 6.0 nano.
Click to expand...
Click to collapse
Maybe l24 problem? I'm using it on l21 and the only thing that's bugging is "OK Google." Have you tried redownloading it?

[DISCONTINED] [ROM] [7.1.x] Official LineageOS 14.1 Weekly Builds (Z00A/Z008)

SUPPORT FOR THIS HAS BEEN DISCONTINUED
LineageOS 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.
*
*/
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.
Instructions
First time flashing LineageOS 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 LineageOS.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Optional: Install the addon SU zip (x86 version)
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.
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...
[*] Screen recording not working Works now.
Chromecast screen mirroring not working, native casting works though.
[*] factory reset from setting menu has been reported to cause recovery boot loops. Works now.
CM14 (not device specific issues)
No CMTE yet
CM file manager has trouble accessing external sdcard
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
DOWNLOADS.LINEAGEOS.ORG
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.
SU addon:
Flashable SU addon/removal
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
LineageOS 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code: https://github.com/LineageOS/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: Nightly
Beta Release Date: 2016-11-09
Created 2017-01-27
Last Updated 2018-01-28

Reserved
DATA MIGRATION BUILDS
"THESE BUILDS WILL TAKE A LONG TIME (~30 mins) TO BOOT"
LineageOS has moved to private key signed builds. This is something that typically requires a full data wipe to transition too. To ease this burden for users who are not accustomed to that , the initial release builds are designed "MIGRATION" to help users who do not want to clean flash from an existing CM/Lineage build. Use the data migration builds as a one time "Flash this first, and then the officials" to migrate to private key signed builds. Follow the below instructions using the admiration builds to preserve app data if so desired, Otherwise feel free to clean flash directly to the weekly release builds
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!!

Reserve !
---------- Post added at 09:28 AM ---------- Previous post was at 09:14 AM ----------
I've just want to verify
to flash lineageOs
Its required Mm bootloader.
Is it required to flash also the firmware of Mm or just the bootloader and twrp !

Flashed migration build just fine. Didn't take too long. Flashing nightly now!

Thanks for big work. We love this rom, LinOS ???

Finally here!!!! Great job guys I'm glad you didn't give up through everything <3

jrior001 said:
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
Click to expand...
Click to collapse
Damn that's a lot of issues! Is this from the Lineage OS official build or from the unofficial ? Some of them issues must have had been fixed, right ?

beibyboy06 said:
Reserve !
---------- Post added at 09:28 AM ---------- Previous post was at 09:14 AM ----------
I've just want to verify
to flash lineageOs
Its required Mm bootloader.
Is it required to flash also the firmware of Mm or just the bootloader and twrp !
Click to expand...
Click to collapse
no... just upgrade your bootloader to MM, download and flash
---------- Post added at 03:15 AM ---------- Previous post was at 03:12 AM ----------
PedroCaseiro said:
Damn that's a lot of issues! Is this from the Lineage OS official build or from the unofficial ? Some of them issues must have had been fixed, right ?
Click to expand...
Click to collapse
give them time bro.... First nightly is up just now... chill

Why the zip on the lineageOS download page are not signed ? I need to disable the verification to install it in TWRP...

PedroCaseiro said:
Damn that's a lot of issues! Is this from the Lineage OS official build or from the unofficial ? Some of them issues must have had been fixed, right ?
Click to expand...
Click to collapse
Provably a few of those I can clean up, was just quick copy/pasta from the other thread
Sent from my ASUS_Z008 using Tapatalk

persieghini said:
no... just upgrade your bootloader to MM, download and flash
---------- Post added at 03:15 AM ---------- Previous post was at 03:12 AM ----------
give them time bro.... First nightly is up just now... chill
Click to expand...
Click to collapse
Ok btw can I upgrade my lollipop bootloader to MM via twrp
And also should I unroot and uninstall xposed?

cedric1997 said:
Why the zip on the lineageOS download page are not signed ? I need to disable the verification to install it in TWRP...
Click to expand...
Click to collapse
The builds are signed, its your twrp that's not signed with the same private key(and never will be) that keeps you from using that sig verification.
Sent from my ASUS_Z008 using Tapatalk

jrior001 said:
Provably a few of those I can clean up, was just quick copy/pasta from the other thread
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Is the battery life really horrible? Is it worse than the MM blobs CM 13? Anyways, thanks for continuing to develop this great ROM.

How can I enable also G-Assistant and G-Now on LinOS

crisvincent said:
Is the battery life really horrible? Is it worse than the MM blobs CM 13? Anyways, thanks for continuing to develop this great ROM.
Click to expand...
Click to collapse
No, it's actually been much better recently. I cleaned up a couple of the issues that were causing inconsistent wakelock issues a week or so ago.
Sent from my ASUS_Z008 using Tapatalk

jrior001 said:
No, it's actually been much better recently. I cleaned up a couple of the issues that were causing inconsistent wakelock issues a week or so ago.
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Can confirm, I noticed my battery get much better recently before realizing you had updated that. I still have an issue with losing fast/quick charge, but I haven't seen others mention this so it's likely an issue on my end.

New nightly rom is amazing.... Thanks a lot guys @jrior001
---------- Post added at 04:11 AM ---------- Previous post was at 04:07 AM ----------
beibyboy06 said:
Ok btw can I upgrade my lollipop bootloader to MM via twrp
And also should I unroot and uninstall xposed?
Click to expand...
Click to collapse
No you can't do it with twrp... You need adb(comp) and unrooting is not necessary... Uninstalling xposed is also not necessary... It won't work in nougat.. It'll just be there

Can i use SuperSU instead of the official root?

Wow , I know I've just done a clean install of the nightly ....but , is it just me or is this a lot faster , more fluent browsing the web pages than anything built in the past ? Or am I slightly delirious thru watching all that blue building up coff ?
Hats off to the new age lineage and the master dev

Just moved to the official branch. Migration tool worked perfectly, and SU optional package did its job as well.
The whole process was absolutely painless, so let's enjoy OTA updates from now on!

[ROM] [Stock] [H930] Debloated Stock ROM Open EU 11m

After some hard work i like to share you the first working optimized stock rom from version 11M with stock kernel (for now).
This rom is a minimal rom, as i like it. No Google services or Framework inside.
I will provide extra packs for google stuff.
Main features:
- full deodexed
- De-bloated (Removed Google & some LG Apps)
- Kernel is free from dm-verity and root check
Tweaks:
- Jpeg and Video optimization
- remove some debug
- high Impedance Mode All The time (big thanks @Whiskeyomega)
- build.prop optimization
Installation:
You need an open Bootloader!
This rom is ONLY FOR H930!
You can flash the rom inside twrp.
After flashing the rom please install the neweset magisk root.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Then wipe Dalvik/ART and Cache.
Feedback:
If you find some bugs or something is not working correct, please contact me.
Future Release:
- include magisk installer
- include new modem
- you tell me
Download:
Version without Google:
https://drive.google.com/open?id=11Zy0Sac9LXZDqHODosPDBmsGtdedI8ob
Version with all Apps:
https://drive.google.com/open?id=18xDw6X5SYF9FBwZTyGWmEKthICWf5h08
XDAevDB Information
Debloated Stock ROM Open EU 11m
Contributors
djsven
Source Code: http://opensource.lge.com
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-01-25
Created 2018-01-25
Last Updated 2018-01-25

Downloading and testing right now! MANY MANY THANKS!!

You are the first one..
Thanks me after you test it

Dumb question now that i read it ... Google service and Framework free ... can i flash Gapps?

Not realy i guess..the gapps are for aosp roms ?
If, you do not flash this..
I will provide tomorrow an update packet for it.
Have you flashed the rom?

Dirty flashed from 10f for now. Google FC's as thought. Tried flash gapps but the same. Ok then i will restore twrp backup. Cannot test more after i am in montenegro the whole weekend where i have no time to test/flash more. Need a working system for the weeken. ....
Sent from my LG-H930 using XDA-Developers Legacy app

Oh wow....Yea i havent the time to fix my rom really. had problem after problem IRL so im glad someone else got there.

@ Whiskeyomega
Thanks
@ Mr. Schnabel
I will upload a new ZIP with Google Inside.

Flashing right now...
Edit1: No way... It tells me The encription did not succeed ! And i have to reboot the phone...

Thanks for your anwer.
So you did encrypt your phones data partition?
Realy strange.
Is this the only message?
My phone is not enctypted.
I will have a look on it.

djsven said:
Thanks for your anwer.
So you did encrypt your phones data partition?
Realy strange.
Is this the only message?
My phone is not enctypted.
I will have a look on it.
Click to expand...
Click to collapse
I followed the step from another user. I paste all steps.
"The order i flashed everything and how i set up everything was:
1) flash twrp and make sure it sticks
2) boot twrp
3) completly wipe /data, so twrp is able to mount it (you have to format the data partition.)
3.5) DONT reboot
4) flash no-verity-opt-encrypt-6.0.zip, root disabler and magisk
5) boot stock rom and setup everything (initial setup and so on)"
I wiped all data, system, internal, etc... also I formatted /data ....
I'll do some checks and I'll post the results.
Thx in advance
---------- Post added at 09:14 AM ---------- Previous post was at 08:58 AM ----------
It seems I partially solved. It boots but it stuck at "Checking for updates... This may take a minute or two"
Of course, as i saw, this rom does not include gapps so i'm unable to setup the google account, and that's why I select "set up as new".
Edit: I think i'm going to wait for the google framework included version How is it going?

Stock ROM with google is uploading now..

New Version with all google inside is up...

Would it be possible to flash micro gapps from opengapps onto the ROM with gapps removed?
Might try it out in a couple of hours and I'll report back.

djsven said:
New Version with all google inside is up...
Click to expand...
Click to collapse
It would be perfect if the gapps package incuded in the full version comes with some bloat
I mean movies, music, powerpoints, documents from google... For me this is bloat too
5 hours with the full version flashed and at the moment zero problems.

This is an idea..
Iam going to create a tool for deleting the bloatware which you want.
But my focus i on the kernel now.
Thanks for positiv feedback .-)

I need the phone working for the weekend but gonna definitely try this on Monday. Good work!

djsven said:
This is an idea..
Iam going to create a tool for deleting the bloatware which you want.
But my focus i on the kernel now.
Thanks for positiv feedback .-)
Click to expand...
Click to collapse
I'm trying again with the version without google and there is no way to enter the wifi key to continue. and it stops searching for updates. But it promises
Good job

fliky said:
Would it be possible to flash micro gapps from opengapps onto the ROM with gapps removed?
Might try it out in a couple of hours and I'll report back.
Click to expand...
Click to collapse
Just finished installing it with the no Google ROM and pico gapps it works great, just one hitch when installing I couldn't get the keyboard to come up on the screen.
Solved the keyboard issue by connecting an external keyboard and installing gboard from the play store.

Realy interesting.
@ fliky
Which keyboard you like to use?? Stock one or from google?
@all
This rom is the beginning!! The first one.
Now we have the base to do more.