Related
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?
DISCLAIMER
Code:
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.
Steps to install:
(0. Install any 6.0 rom)
1. Factory reset
2. Make sure you format /system and /data to ext4 for the install
2. Install ROM zip, you will get a warning about partition size change of system if its the first time you flash, just flash it a second time to confirm the change, this will erase your data partition!
3. Please do NOT install Gapps (you can still do it, but at your risks)
4. Reboot
5. Wait for a long time
Known Bugs:
- First boot is slow
- RIL sudden crash (?)
- Webkit render issues with the latest cm14.1. It will be fixed in the next build.
- CM's FileManager is bugged
Features:
- Stock Cyanogenmod 14.0
- Dirty CoW patched kernel (anyone cares ?)
- kernel built with GCC 6.2.1 with -03
- F2fs support on /data but not on /system
- Bigmem enabled (no cma for now)
- sdcardfs support to come someday
- Zram enabled
Please note that this rom is not ready for daily usage yet, it's an alpha.
Downloads:
Android 7.0:
http://www.mediafire.com/file/5d1fdr0f75rywml/cm-14.0-20161120-UNOFFICIAL-galaxysmtd.zip
Android 7.1.1:
http://www.mediafire.com/file/xfcjvn1y1vjwwpu/cm-14.1-20161223-UNOFFICIAL-galaxysmtd.zip
I will provide mirrors later if needed.
Please check the MD5 !
094fa2133073f22cea28e80d18a628e5
HUGE thanks to @xc-racer99 for his AMAZING work on his variant, without him, this woudn't have been possible at all.
XDA:DevDB Information
CyanogenMod 14.0, ROM for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99, sooti
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2016-10-28
Last Updated 2016-12-23
Reserved
Changelog:
23/12/2016
Android 7.1.1 r6
No more crashes due to the graphic driver
Working ril (except data on the first boot apparently ?)
Fixed internal storage issues
Updated kernel
Latest TWRP (without their new app, tell me if you want me to add it back)
20/11/2016
Latest CM 14.0
As people wanted, cmc is back
Tweaked art settings (lag should be gone)
Fixed video recording
Fixed MTP crash
Fixed adb authkey issue
Disabled SDcardFS
More stable RIL (but there are still issues with 3g)
28/10/2016
Initial release
Reserved
FAQ & tips :
Where is SuperSU ?
You don't need to flash SuperSU, just enable it under the Developer options.
How to change Bigmem modes ?
You can change it in advanced parameters>Bigmem
What are the best schedulers/governors/...
That's up to you, personaly, I like the combinaison of smartassV2 and bfq.
But ... how to change them ???
You can use Kernel Adiutor or any other app like that.
When will you release the next build ?
Don't ask for ETA ..... and wait.
Something isn't working, please fix it, please PLEASE
Logcat. No logcat == no fix.
If you don't know how to logcat properly, read this.
My phone is bootlooping ,what can I do ?
Pull battery and restart. Also don't forget to do a factory reset before flashing this rom.
Can you add X feature on your rom ?
No. I wont add additional features, this is stock cm. The only thing I might add is signature spoofing support.
Here are a few additional tips to get the most of this rom :
Format /data in f2fs in TWRP
OC your cpu if it can handle it
Use Bigmem
Don't install unnecessary apps
Remove apps from startup
(Wait for the next build)
Wow!!! It is impossibly! Big thanks!!!
+1
:good:
Link is up, make sure to check the md5sum and tell me if you experience issues.
Logcats appreciated !
Ok, just tested it. Was compared with AOSP 7 from x-racer99.
Seems CM14 more laggy in games. Not so smooth like an AOSP. But problem probably is not in the kernel. Cause i was also use x-racer99 kernel on your CM14 rom. Look at this videos with Mega Jump game:
https://youtu.be/ueyjuPu3BgA AOSP rom by x-racer99
https://youtu.be/FWbCNKZdAdE Cyanogenmod 14 rom with x-racer99 kernel.
Second video is not so smooth with a lot of jerks. May be problem in low memory killer settings, or GFX drivers, or V-Sync, or build.prop tweaks, i do not know.
Also i prefer CMC instead Voodoo Color. Because VoodooColor have two bugs since android 2.x.x. It is yellowish tint of all screen (CMC have more right white balance) and green bug on low backlight with high gamma settings, look at this video:
https://youtu.be/gkP7VgWbTlY
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
About CMC, you can tweak voodoo by yourself, but yeah if many people want me to switch to CMC, I will do it.
Coldwindofnowhere said:
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
Click to expand...
Click to collapse
You can just download Subway Surfer from market or another place and try to make run this game more smoother. Some times Subway Surfer have bad responce on touch and can hung up after long play. Also can try this on Mega Jump or other dynamic game.
Thank you!
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
P.S. Issue with MXplayer was resolved by itself after reboot phone.
M1n3cr4f7.G4m35.2015 said:
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
Click to expand...
Click to collapse
Um pull off the battery, start the phone again. Got this issue once but no idea why.
jupiter5700 said:
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
Click to expand...
Click to collapse
Bigmem patched, I haven't tested 720p videos tbh.
This rom can run on samsung wave?
thinhx2 said:
This rom can run on samsung wave?
Click to expand...
Click to collapse
I haven't tried but as it's really similar to the i9000, you should give it a try.
Coldwindofnowhere said:
I haven't tried but as it's really similar to the i9000, you should give it a try.
Click to expand...
Click to collapse
Screen is different. You think driver display of i9000 can work on wave?
thinhx2 said:
Screen is different. You think driver display of i9000 can work on wave?
Click to expand...
Click to collapse
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Coldwindofnowhere said:
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Click to expand...
Click to collapse
You can public your kernel for aosp 7 of ss s1?
thinhx2 said:
You can public your kernel for aosp 7 of ss s1?
Click to expand...
Click to collapse
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/commits/staging
No way man, nice work
Android 7 N for s1
Ejgjskfkcisvjj hahah
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!
What is the difference?
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
THIS IS A UNOFFICIAL VERSION BECAUSE IT CAN'T BE BUILT AT OFFICIAL SERVER! I just want you know Mokee and other AOSP ROM can't be official unless alberto96's lineage os be official.
I won't have time to update it anymore,you can use my source to continue it.See you next summer,everyone.(if nobody want to continue it,I will update it mouthly.(Sometimes weekly)
About
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Credits:
Google, Qualcomm, Linux Kernel Organization, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser, lineageOS, TeamWin,
Smartisan Digital Co, Substratum Development Team, The Open GApps Team.
ContributorErag0n(Migrate source from Lineage OS and build a zip) @sunilpaulmathew(Thanks for his suggestions and reply, most importantly, his awesome Kernel source.) @Alberto96(all hard work)
Features
1.Fully OMS Supported
2.Xposed Framework Supported
3.Can make a dirty flash which Lineage OS can't.
4.Phone & Messaging:Quick contacts look up, speed dialing, caller location and other useful features
5.Colorful Themes:Unleash the creative side of you, customize how your phone looks; make it cool, make it colorful!
6.Smart Controls:Increase your productivity with Active Display, Lockscreen Notifications and other shortcuts
7.Power Saver:With our unique battery saving strategies, get the most out of your phone's battery
8.Latest source merge from google android source.
9.Minimal but not simplify.
10.Delta update:8~15Mb, more than 300mb download space saved.
11.OTA Update
12.Odexed
Supproted Devices
ja3gxx(GT-I9500),ja3gchnduos(GT-I9502),jaltelgt(SHV-E300L),jalteskt(SHV-E300S/K),ja3gduosctc(SCH-I959).
After Odexed,ROM may have a large size(600~700MB),but it can get a better improvement.
Enjoy it!
Change logs:
MK60.1-8.13
Alpha build,this build is a stable RELEASE version,what is RELEASE?Please see the first line of post.
MK71.2-7.23
First build,sync to latest Mokee Source.
MK71.2-7.24
Second build, sync to lastest Mokee Source, Delta update available, Automatical translation, charger:fix small capture font.
MK71.2-7.25
Sync to lastest Mokee Source, change pixel launcher to default launcher, new kernel merged, now you can use Kernel Adiutor to custom kernel governor.
MK71.2-7.25-17.06
Fixed all bug, include high sensitive screen, display mode, novbar.Alberto not fixed bug I unable to fix.
MK71.2-7.26
Sync to latest source.
MK71.2-7.27
Sync to lastest Mokee Source, Kernel updated to 3.4.113, thanks to sunil.
MK71.2-7.28
Sync to latest source, stability is improved.
MK71.2-7.28-19.31
Sync to latest source.
MK71.2-7.29~8.05
Sync to latest source,new LawnChair launcher is added.
MK71.2-8.12
Xposed app added,automatical translation.Update to android-7.1.2_r29-tag
MK71.2-8.13
Only update for ja3gchnduos,jaltelgt,jalteskt.
MK71.2-8.20
Update source,probably fixed jalteskt incoming problem.OTA update supported,Gapps added.
MK71.2-8.26
Device Source updated,PowerHAL added,odexded,improve boot speed,Blur effect added and etc.
MK71.2-8.30
Source Update,bug fix.
MK71.2-9.02
Hardware source update,in next build,Gapps will be removed.
MK71.2-9.09
Source Update and Gapps removed, device ja3gduosctc added.
MK71.2-9.15
Source Update.
MK71.2-9.23
Source Update,kernel change to origin.
Delta update and full download：
Everyone can use delta update now, even installed stock gapps.
Delta Update can save your download time but get full function which contains in full update.
Full update is made for who use Mokee just once or need system files repaired.
Delta(OTA) update will keep 1 generation system up to date, in order to save space.
Version MK 71.2-7.23~7.26
https://drive.google.com/folderview?id=0B5BV4JClBJELa19mNjU4b2ZubUk
You must choose a version which is correct for you.
Version MK 60.1-8.13&MK 71.2-7.27 and above.(You can find all ROM contains MK 60.1 in it)
https://www.androidfilehost.com/?w=files&flid=202052
Recommend Kernel: (Now is build-in in Mokee.)
SmartPack is a good kernel that can give you better battery drain and system fluency.Thanks to sunilpaulmathew for making a awesome kernel.
If you want to see more about kernel,here is the link:https://forum.xda-developers.com/ga...nel-smartpack-project-lineage-os-14-t3590858/
How to build:https://github.com/exynos5410/manifest There are some unique changes for mokee open source,if you want to build one,ask me for help without hesitation,I will try my best to help you.
Issues (copy from Alberto's post)
MK 71.2 issues:
Filesystem Socket Whitelist (https://goo.gl/1N6n7G) - The only issue that requires to be fixed in order to get official.
SELinux (Permissive)
BASED ON USERS FEEDBACK: Mobile Signal Reception isn't 100% stable.
Shared Storage (doesn't encrypt the storage)
ja3gxx: In-Call Echo Effect (random and rare)
ja3gxx: In-Call Volume can't be increased/decreased
ja3gxx: OK Google (Automatic Voice Recognition)
ja3gchnduos: Missing Dual SIM support.
jalteskt: Mobile Data and Incoming Calls don't work.
jalteskt: USSD Codes can't be sent.
jaltelgt: RIL crashes on boot, meaning that Calls/Data won't work.
MK 60.1 issues:
1.Audio HAL isn't working correctly, causing VOIP issues, HDMI audio instabilities and mixer paths conflicts
2.STK Toolkit isn't working yet, SMSs aren't properly sent (RIL issue)
3.SELinux policies are almost complete, with just some minor missing rules
4.Wireless Display (or Miracast if you like) stream is corrupted, buffer issues
5.Adoptable Storage isn't stable, crashes while encrypting the external storage (Kernel Panic). Read Here: http://goo.gl/0w6DPt
6.Device Encryption isn't stable for the same issue that affects Adoptable Storage
Problems report
You need report problems with your
ROM Version
Step to get bugs
If possible,with a logcat is better.
Source Code
https://github.com/Dracanrage
Sorry for my bad English
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.113
ROM Firmware Required: Lollipop Bootloader and Modem, TWRP 3.1.1 as Recovery
Based On: AOSP
Version Information
Status: UNOFFICIAL
Created 2017-07-23
Last Updated 2017-09-23
Screenshots
Is there any differences between Los and it?
Super Sha said:
Is there any differences between Los and it?
Click to expand...
Click to collapse
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Erag0n said:
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Click to expand...
Click to collapse
Nice work!I will try it soon. Will it be official?
Super Sha said:
Nice work!I will try it soon. Will it be official?
Click to expand...
Click to collapse
Sorry, it can't be.
As Alberto says, unless Samsung update the Kernel source to fix the Zygote problem, it can't be official.
i will try, thanks.
Is there any problem with mobile data and call echo?
tosunkaya said:
i will try, thanks.
Is there any problem with mobile data and call echo?
Click to expand...
Click to collapse
As Lineage OS, there should not have any problem with mobile data, but call echo will appear randomly (according to different hardware which Samsung use).
app to sd
how to move app to sd card ?
RahmahTunisa said:
how to move app to sd card ?
Click to expand...
Click to collapse
There is a error in make SD card as internal storage, so it can't move app to SD card in Nougat.
This error is mentioned in Alberto's post, I use his device, vendor, hardware source to make this ROM, so this ROM have the same problem.
What about battery draining?
It's like lineage ?
Mohamed rajab said:
What about battery draining?
It's like lineage ?
Click to expand...
Click to collapse
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Hey, guys.
Delta update is come back now, you will see it in today's update.
Edited
Delta update is available.
Camera2.zip for installed stock gapps guys.
About how to use, please read the main post.
Edited
This file is useless, you need get Camera2.app from 7.23 ROM zip.
Edited 7.25
Mokee updated the check script, it is no need to keep Camera2 installed.
Nice work
Thank you so much
Erag0n said:
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Click to expand...
Click to collapse
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
nebrassfarfoor said:
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
Click to expand...
Click to collapse
Yes, you can use aroma, but had better not install Google camera in order to use delta update.
It support remapping the hardware but not support long press custom.
About bugs, please read the main post
About battery drain, Mokee Open Source make some optimizations, and kernel is not been limited.
About using smartpack Kernel, you can use twrp to flash it, and I am working for merge smartpack kernel to Mokee.
About telegram group, I am so sorry that I can't make one because Chinese telephone number is limited in sent message to strangers.
Hey, guys.
I fixed my S4 today.
Now I can test a amazing Kernel.
Thanks to @sunilpaulmathew for his help and smartpack source.
Hi
Bug = not notification miscall and sms
deletanha said:
Hi
Bug = not notification miscall and sms
Click to expand...
Click to collapse
Oh, it was terrible.
Let me check.
Waiting for a minutes please.
Edited
In my S5 official Mokee, missing was common if I use Aegis.
Did you use it?
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021
Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5
Has anyone tried it yet?
DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.
Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.
How does Resurrection Remix compare to CrDroid?
asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.
hockeymikey said:
Resurrection Remix Oreo
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.
jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.
Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere