Disclaimer
Code:
/**
* You flash this ROM at your own risk and responsibility.
* This ROM is provided without ANY WARRANTY WHATSOEVER, not even the warranty that it works.
* None of the developers of this ROM will be held accountable for any damages, complaints or thermonuclear war.
**/
Introduction
This is LineageOS 14.1 for our ZUK Z2 (z2_plus, z2131, z2132).
This ROM is mainly an adaptation of fedor917 and davidevinavil's superb work on this device. My sources are continuously being updated to their changes and improved to better work for LineageOS.
Features
LineageOS 14.1 with Android 7.1.1, including all features from LineageOS.
Always updated to the latest upstream sources and security patches
Clean builds without any additional bloatware
Updated every 1/2 weeks
Requirements
Unlocked bootloader
Latest TWRP (Link)
Reading this whole post. If you don't read the post, it's important that you read at least the FAQ. If you don't read it and then ask stupid questions, I reserve my right to make fun of you.
Your Z2 and your brains
Installation instructions
Wipe system, cache and dalvik
If not flashing over a LineageOS 14.1 build, wipe data
Flash the ROM
Flash root if you want (Link)
Flash GAPPS if wanted (Link, select arm64, android 7.1)
Reboot
Changelog
You can always find the changelog at the device wiki.
Downloads
Link
Credits
Thanks to Fedor, Davide and all other contributors!
Donations
I'm doing this in my free time and to use myself. Furthermore, both davidenavil and fedor917 have done much, much more work than I to make this ROM possible. If you're feeling like donating you should donate to them first.
If after reading this you still want to donate to me, here's a link:
Insert Coin (Paypal)
Note that by donating you are confirming that you're not paying for any service whatsoever, but freely giving away your money without any warranty or right to refund. I take donations as a form of saying thanks, not as payment for my work or the works of others.
XDA:DevDB Information
LineageOS 14.1 for ZUK Z2, ROM for the Lenovo Zuk Z2 Pro
Contributors
varotone, davidevinavil, fedor917, many others
Source Code: [url]https://github.com/ontherunvaro/android_device_zuk_z2_plus[/URL]
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2017-02-11
Last Updated 2017-10-15
Reserved
FAQ
Does this ROM have OTA updates?
Yep, since release 20170420.
LTE/Calls not working?
Please make sure you're on the latest baseband before reporting these bugs. Also remember that flashing a new baseband will re-lock your bootloader and you'll have to unlock it again. Search the forum for more info.
The U-Touch settings are not in my language?
Some of the U-Touch strings were added by Fedor and others by me. I don't know any languages other than Spanish and English, and there's some Russian strings too.
If you want to translate the settings, send me a DM with this file translated to your language, plus which language it is and from which country. You can also send pull requests - do NOT open issues for this.
What's with the root in this ROM?
LineageOS have dropped prerooted roms in favor of a separate root addon. It is the one linked in the first post. This is managed in "Developer options" after you've flashed it.
You can also flash other root options (SuperSU, Magisk, etc.) if you prefer.
How can I contribute to this ROM?
You can contribute to my sources on GitHub by doing pull requests or issues. If you're serious about it, contact me and we can setup an organization.
You can also contributing by reporting bugs and errors, always accompanied by a logcat and a sufficient description of the bug. Please check it's not a known bug first.
Can you add PIE controls / Omniswitch / this app...?
No. I only build clean, bloatware-free LineageOS ROMs, without any extras.
You're running late on your updates!
This is not my job, and I actually have one. I will try to update frequently but I cannot promise anything.
How can I talk to you?
You can find me sometimes on ##z2_plus-dev at irc.freenode.net. You can also post your doubts or suggestions in this thread or the dedicated DevDB pages.
I will not answer any DMs or emails for bugs, feature requests or technical assistance. That's what the forum is for.
Reporting bugs
Should I report this bug?
If you find a bug you want to report, please check these things first:
It's actually a bug:
Missing functionalities generally are not bugs. Bugs are things that are there, are supposed to work, but don't work. For example: camera crashes are bugs, but "there isn't a navbar option" isn't.
As stated in the FAQ, I only build clean LineageOS, so only things in base LineageOS will make it to the rom.
If some functionality is missing, wait until LineageOS includes it, do not ask me. This includes: navbar options, more quicksettings tiles, theme engine, etc.
It's not already been reported:
Check the "Known Issues" list in the first post, and see if your bug is there before reporting it.
It's related to the ROM itself:
I will only accept bug reports related to the ROM. That means I won't accept bugs related to DivineBeats, Xposed, Atmos or any other addons. Those addons have their own support threads in xda or similar forums.
How do I report this bug?
Once you confirm you've got a bug and it's not been reported yet, you shall do the following:
Capture a log.
There are plenty of tutorials on using logcat on the internet. You should reboot the phone, reproduce the bug and capture the logcat then. Do not send me logcats when the phone it's been on for hours.
Send the bug report.
Either make a post here, or open an issue in the github page. Make sure to write a sufficient description of the bug and instructions to reproduce it, and attach (attach, NOT paste) the relevant logs.
Bonus - dmesg: There's another type of log apart from logcat which is also useful called the dmesg. Again, there are tutorials on the internet on how to capture one. If you can also provide a dmesg, besides the logcat, that would be great! But remember, logcat is essential, I can't do anything without a logcat.
Bonus 2 - ramoops: If the phone hangs (black screen with led) you can get the logs by rebooting and getting the console ramoops:
Code:
adb shell cat /sys/fs/pstore/console-ramoops > ramoops.txt
Run this code on your computer after a reboot to get your ramoops log.
My bug is already reported, how can I help?
You can read the relevant GitHub issue and provide any missing relevant information via comments. If you see a bug with the needs-logs tag, that means no logs are available, so you can contribute by providing them.
NOTE: "I also have this bug" is NOT relevant information if the bug is already verified. Such comments will be deleted, and their author shamed. You've been warned.
its for the zuk z2 pro or plus?
XDAevDB Information
LineageOS 14.1 for ZUK Z2, ROM for the Lenovo Zuk Z2 Pro
iliakele said:
its for the zuk z2 pro or plus?
XDAevDB Information
LineageOS 14.1 for ZUK Z2, ROM for the Lenovo Zuk Z2 Pro
Click to expand...
Click to collapse
Edited the FAQ to clarify this.
Hi, will be released official rom?
Link posted
Please start a thread in Zukfans.eu , there is a much better response and discussion there . Thank you for this ROM and your hardwork.
Sent from my Redmi 4 using Tapatalk
Karthik9425 said:
Please start a thread in Zukfans.eu , there is a much better response and discussion there . Thank you for this ROM and your hardwork.
Sent from my Redmi 4 using Tapatalk
Click to expand...
Click to collapse
http://zukfans.eu/community/index.php?threads/4852/
Guys please confirm me that can all the roms for this device be installed on the Indian variant lenovo z2 plus?
Dashing_97 said:
Guys please confirm me that can all the roms for this device be installed on the Indian variant lenovo z2 plus?
Click to expand...
Click to collapse
Yes, its for 2131/2132
@varotone check this thread for enabling VoLTE maybe it can help https://forum.xda-developers.com/re...t/volte-patches-nougat-based-cm-roms-t3509257
i want to disable the vibrate when unlock phone with touch finger print
how to do this
Thanks for the hard work, I would like to report some issues that I have encountered are :
1. There's no way to enable on screen nav bar.
2. Root doesn't work, I have tried flashing LineageOS addonsu and SuperSU but no luck
20170217 released. Links and changelog in the first post.
Ritik17 said:
Thanks for the hard work, I would like to report some issues that I have encountered are :
1. There's no way to enable on screen nav bar.
2. Root doesn't work, I have tried flashing LineageOS addonsu and SuperSU but no luck
Click to expand...
Click to collapse
Woops, I forgot to edit this thread. LineageOS addonsu is broken for now (working on it). SuperSU should work though (working on my device). Try it on a clean flash, or use the LOS addonsu remover before flashing SuperSU.
As for the nav bar, it's a missing feature in LineageOS for now iirc.
varotone said:
Woops, I forgot to edit this thread. LineageOS addonsu is broken for now (working on it). SuperSU should work though (working on my device). Try it on a clean flash, or use the LOS addonsu remover before flashing SuperSU.
As for the nav bar, it's a missing feature in LineageOS for now iirc.
Click to expand...
Click to collapse
Yeah I tried a clean flash and it works. The build is working good so far, those were the only problems I have seen yet. I will update and let you know how it goes.
Configuring notification light doesn't work properly and shows this notification until the charger is plugged. Both USB and this are system notifications, it should be hidden.
Edit: The led notification pops up every time configured, but still it should be hidden.
This ROM looks great but it crashes during setup after the wifi connection screen, weather i connect or not.
SachK2 said:
This ROM looks great but it crashes during setup after the wifi connection screen, weather i connect or not.
Click to expand...
Click to collapse
Try this link and after completing the setup update to the latest build. Download here
I have an "x" in the signal bar. What can it be?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click here to get to the new post where we'll keep updating this rom
What it is
It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)
Disclaimer
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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
What gapps to flash?
Use f-droid
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!
NEW RELEASE
2017-06-13:
Xperia Z3
Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09
Xperia Z3 Dual
See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.
Temporal Z3 Dual rom (fixes SIM problems)
nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody
Click to expand...
Click to collapse
What's new:
Code:
- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness (again)
Release notes:
2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual
Older Releases
Based on Kernel 3.4
Some of these can be found here
Release History
Code:
2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17)
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU
2017-05-17:
- Tweaked general audio output processing
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates
2017-04-16
- Audio changes,
- NFC fixes,
- Brightness changes,
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more
2017-04-05:
- Enforcing selinux
2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now
2017-03-22:
- Full rework based on stock 3.4 kernel
Based on Kernel 3.10 by @nailyk
2017-01-23:
Download
md5: 04a3a614d820df78e7a70538df61203d
sha1: 10a3ea95d823a6b87b5f5a8f79896e3dabf7a8b5
Status
Workaround for in-call reboot
Include PR1130 PR1128
2017-01-15:
Download / 2
md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
Use of the reworked device trees
Include some experimental kernel pull requests
2017-01-01:
Download
md5: 6c5abcbeda01c75344cd4296bb2358d1
sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
Switch to LineageOS
Bluetooth deepsleep fixed
2016-12-02:
Download
md5: 496de65608fd4236f5d451a4179e1ce8
sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
Bluetooth improvements
P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.
Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.
XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3
Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-09
Created 2016-11-27
Last Updated 2017-07-01
Thank you!
Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5
All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.
TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me
FAQ
How to post
I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.
This is not against you but try to keep thread clean as a dev reference. Thanks in advance.
What is not working
BT headset calls --> pending. Detailed post.
OTG --> 2017-04-16
Wifi auto connect (boot/deepsleep),
HW Encryption, --> 2017-04-16
Vibrator level
4k (unfixable without Sony camera app)
120 fps (pending)
Some volume loudness problem --> not reported
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
Slow charging,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
NFC, --> topic
Wifi access point,
Adaptive brightness not good. --> Fixed by @xkeita
How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward
Some examples:
I cannot record videos with open camera.
Click to expand...
Click to collapse
Is useless on a dev thread and you probably won't get an answer.
Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Click to expand...
Click to collapse
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.
This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)
@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
steadfasterX said:
You talked about using IRC to get support. What is this and how can I use that?
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
Click to expand...
Click to collapse
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.
How to contribute
I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.
What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.
Thanks for posting this rom. Thank you for your awesome developing.
Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks
great work and z3 compact?
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
Click to expand...
Click to collapse
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?
Click to expand...
Click to collapse
Can you report me as I can answer please?
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
Click to expand...
Click to collapse
Well, thanks then.
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.
drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Click to expand...
Click to collapse
IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.
If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
Click to expand...
Click to collapse
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
Click to expand...
Click to collapse
Hey no problems, I'm actually battling just to get my latest CM build to install properly
mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly
Click to expand...
Click to collapse
Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.
2016-11-28 release
Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.
Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.
This rom is not intended to be used as a daily driver and is unstable!
cm14.1 wowww :good:
After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?
Unofficial LineageOS 14.1 for Sony Z1 Compact
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.
*/
General
This is an unofficial LineageOS 14.1 as is build for the Sony Z1 Compact, (Amami/D5503).
The builds will be builds when i want it, as long as LineageOS updates and support LineageOS 14.1 or when it goes official.
I won't include features that I dislike. If u want something else, build it.
Install
How to install:
New Install (coming from another ROM)
Do a full backup with your favorite latest Nougat compatible recovery (3.1.0.0 ATM)!
Download the Rom zip and an OpenGapps file for 7.1.2, 32 bit, Arm
Do a full wipe in recovery (data/factory reset, system)
Install the Rom zip and Gapps zip through recovery compatible with Nougat!
Enjoy!
Coming from previous version of LOS14.1
Do a full backup with your favorite latest Nougat compatible recovery!(optional, for if things go wrong)
Download the Rom zip
Install the Rom zip (and Gapps if getting erros with Google services) through recovery compatible with Nougat!
Enjoy!
Downloads
Latest-Rom: lineage-11-20170810-UNOFFICIAL-smi.zip
XDA Download Section
Github Version number is different
Project manifest
Manifest/Roomservice
Bugs/Issues
HW overlay needs to be disabled for some full screen video applications and front camera
Bluetooth may not work as expected
Reboot to recovery doesn't always work
Needs a compatible recovery to install
Camera may not work 100%
Will never pass full CTS test?
Wifi starts without data connection after reboot
NFC HCE will maybe never be supported, used for android pay
Thanks and credits
SpiritCroc
SuperLamic
All MSM8974 Maintainers
Sony (OSS)
LineageOS
All the rest that have helped to construct these builds and develop software for Z1 Compact directly or indirectly in the past.
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the Sony Xperia Z1 Compact
Contributors
Hazou
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Current Beta Version: lineage-14.1-2017080
Beta Release Date: 2017-08-10
Created 2017-07-14
Last Updated 2017-08-10
Hazou said:
Unofficial LineageOS 14.1 for Sony Z1 Compact
I won't include features that I dislike. If u want something else, build it.
2017-07-14
Click to expand...
Click to collapse
Nice, thanks. Could you summarize which features you did implement? I'm currently using LOS by Micha-Btz, and it's working great,but I might try this out if it's any different...
levone1 said:
Nice, thanks. Could you summarize which features you did implement? I'm currently using LOS by Micha-Btz, and it's working great,but I might try this out if it's any different...
Click to expand...
Click to collapse
Can't say for sure what he changes. Not all his repos are open to public.
This version is the latest updated version of lineage, at the time of build. With all the newest changes from the msm8974 maintainers to get a working Android 7.1.2 on this device. The only extra difference is that I included the smartcard API, so u could use NFC pay with a compatibele sim card.
Hazou said:
Unofficial LineageOS 14.1 for Sony Z1 Compact
Click to expand...
Click to collapse
Which kernel does this ROM use? I can't find a repository at your GitHub
Might be a good idea to link to these sources from OP as public sources are required by GPL.
Btw, this information seems to be wrong
Hazou said:
Downloads
Latest-Rom: lineage-11-20170227-UNOFFICIAL-smi.zip
Click to expand...
Click to collapse
hahnjo said:
Which kernel does this ROM use? I can't find a repository at your GitHub
Might be a good idea to link to these sources from OP as public sources are required by GPL.
Btw, this information seems to be wrong
Click to expand...
Click to collapse
Thx for sharing. Will add them right away. They are indeed not on mine or lineage GitHub. The kernel source is on another GitHub. Will add a local_manifests to the message.
Thx. Works great so far.
My findings:
- original Sony camera app has that hw overlay issue.
- automatic brightness seems to be calibrated to bright
- wlan works smoothly (current aicp has has issues with that)
Not tested Bluetooth yet
Regards
Update:
[2] lineage-14.1-20170721-UNOFFICIAL-amami.zip
Fixes:
Audio_effect fix
A tiny bit better battery life
Fix nightly reboot when charging
Thermal improvements in config
LineageOS changes
Known bugs:
HW overlay needs to be disabled for some full screen video applications
Bluetooth may not work as expected
Reboot to recovery doesn't always work
Needs a compatible recovery to install
Camera may not work 100%
Will never pass full CTS test?
Wifi starts without data connection after reboot
NFC HCE will maybe never be supported, used for android pay
Great firmware!
Problems with lineage-14.1-20170721-UNOFFICIAL-amami.zip
- I still get nightly (while recharging) and some times random reboots
- HW Overlay with Camera
I didnt have any other issues yet
@Hazou thanks for your work! This device still can work well and thanks for support LOS!
Pardon, is it possible to have this feature enabled to receive mms when data is disabled? It can be much of annoyance and inconvenience to have data always be turned on for those with limited data or having to turn data on and of manually just to receive mms
https://review.lineageos.org/#/c/172853/ I can beta test a patch if need, very useful feature. This device deserves a good maintainer like you!
Thanks again sir for attention!
echo124 said:
@Hazou thanks for your work! This device still can work well and thanks for support LOS!
Pardon, is it possible to have this feature enabled to receive mms when data is disabled? It can be much of annoyance and inconvenience to have data always be turned on for those with limited data or having to turn data on and of manually just to receive mms
https://review.lineageos.org/#/c/172853/ I can beta test a patch if need, very useful feature. This device deserves a good maintainer like you!
Thanks again sir for attention!
Click to expand...
Click to collapse
Thank you, But I am not alone Doing this stuff with many others
And yes, we could implement this, than u need to test it, will have a look at it for next update
Hazou said:
Thank you, But I am not alone Doing this stuff with many others
And yes, we could implement this, than u need to test it, will have a look at it for next update
Click to expand...
Click to collapse
Great, will test and thans much to all developers for their time and awesome work! Thanks for this very much!
is the gps working?
- GPS works
- HWOverlay needs to be disabled for Cam or Youtube
- Nightly reboots if the phone is charging over night - even with 21.07.2017 version
Hopefully the team could fix it. Great work so far
Frash said:
- GPS works
- HWOverlay needs to be disabled for Cam or Youtube
- Nightly reboots if the phone is charging over night - even with 21.07.2017 version
Hopefully the team could fix it. Great work so far
Click to expand...
Click to collapse
Yup, we are working on them. Just takes a lot off time to debug and find the issue. Also it's holiday season; sun, beach, party
New version 8-10
Changelog:
3AM bug solved
Touch firmware update (changed to stock amami)
Time correctly set at boot
Update in media codecs/profiles
BLE peripheral mode enabled
Network type change and search should be fixed
Thanks for the update!
Thanks for the update, Hazou!
Unfortunately, changing of network operator does not work with my 2 SIM cards.
I can change the network type and search for network operators, but changing the network operator is not possible.
I have tested various ROMs (AICP, Lineage - yours and Micha-Btz - and Paranoidandroid, v6.03).
Only with the stock Rom and with Paranoidandroid I can change the network operator.
The problem seems related to accessing the SIM card (at least my SIM cards). When the Z1C can read the contacts stored on a SIM card, I can also change the network operator.
Can you change the network operator without problem?
Hi Hazou,
there also seems to be a problem with the telephone function if you toggle the loudspeaker or the mute button during a call.
Once you click mute and enable the mic again, it will stay muted... Same problem seems with the loudspeaker button from time to time.
Would be great if this could be fixed.
Good work! It is really appreciated!
Hi Hazou,
I have also a problem with telephone calls. The microphone seems always to be muted.
When I use Google Duo or WhatsApp Calls if works flawlessly.
The reboot bug while charging is also still existant.
Bisides that: Nice work, thanks for that.
LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5
Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.
Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'
Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.
Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...
I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.
I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices
What DPI is this device? 320dpi right?
nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution
MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.
my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.
This thread was formerly "[ROM][9] LineageOS 16.0 + AOSPExtended + PixelExperience // personal builds" - yes, once again, the title can't fit the full names of all these ROMs :/
This thread hosts personal builds of LOS 16.0 and other Android 9 (Pie) ROMs for Mix 2, currently built from @wight554 's trees. Similar to Oreo, full credits to Wight and others behind the scene for the bringup, allowing us to build upon the awesome work.
Currently I build the following ROMs, usually monthly (in sync with security patch):
LineageOS 16.0
ResurrectionRemix 7
AOSPExtended 6
PixelExperience 9
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
...
What's working:
Everything?
Instructions:
Coming from official MIUI? Since the new encryption has been implemented, you only need to wipe (not format) /data.
Flash any Pie firmware (firmware Stable V10.4.1.0 recommended) for builds starting from May, or firmware Stable V10.0.2.0 otherwise.
Use official TWRP or OrangeFox.
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies to Pie
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "9" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
https://github.com/wight554/
About "official" status:
Currently I don't plan to apply for "official" for any of these ROMs, because 1) Wight is the actual maintainer who did the bringup and maintenance work, and 2) I like to be able to apply changes at will to the OS itself without restrictions from the official team.
Donation:
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 16.0, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, wight554, Cozzmy13
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V10.4.1.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2018-09-25
Last Updated 2019-09-27
Reserved
Just an additional note: I'm not as enthusiastic about building ROMs as I was early this year, so expect less regular updates and/or unanswered fix/feature requests. I'm just a builder, not nearly as capable of Demon or Wight doing all the heavy lifting, so I'll only do what my ability/time permits.
Thanks for all your work, Andy
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Fairtex said:
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Click to expand...
Click to collapse
Statusbar customizations like network traffic aren't merged yet, just wait.
Can we have that slide down gesture to bring the notification bar down like we had in PE Oreo? Thanks
Hey,i have a question. Is it possible to port full screen gestures from miui 10 to los 16?
Are the quick settings on the status bar still a bit off on PE edition?
Folks who have tried, please do let me know about the battery consumption. This build added some CPU governors to the kernel and defaulted little cluster to one of them, and I'm not sure of its actual impact. It's my first time fiddling with kernels and I can't guarantee the change will be satisfactory.
Fairtex said:
Are the quick settings on the status bar still a bit off on PE edition?
Click to expand...
Click to collapse
I acknowledge the lack of padding there, but I don't quite want to look into it now. It's supposed be a problem for PE upstream anyway.
Greetings!
I've downloaded the rom last night. And until now, I have no problem: the camera works perfectly, the sound sound good and gaming performance are good.
The thing which attracted me was the mention of "Lineage OS" and I'm not disappointing to see that it's so close of the official and stable version . I'm blind in context of "find the bugs", so maybe we could find some but this is not my domain.
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Install custom navigation bar .Its work fine
Wysłane z mojego MI MIX 2 przy użyciu Tapatalka
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Expanded Desktop is a feature that will surely be merged in the future. As the other user said, there are 3rd-party apps that can achieve the same goal. I myself am using Tiles since it places a shortcut in Quick Settings.
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
MrSammyMcG said:
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
Click to expand...
Click to collapse
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
AndyYan said:
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
Click to expand...
Click to collapse
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
MrSammyMcG said:
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
Click to expand...
Click to collapse
This is Treble-enabled but this is NOT a GSI (Generic System Image). You still flash as you would do a regular ROM, just with a Treble-enabled recovery.
Quick update to sync with Wight's updated battery data - from this build on you're supposed to use newer firmwares. OP has been updated with the mandatory new firmware requirement and TWRP build from Wight.
Thanks for your work,I have used aex for two days.It is very nice.But I notice a small problem that sometimes the fingerprint unlock is very slow and I have to touch several times to unlock it.Is it a bug of this rom?
Duble tap on screen for wake up dosent works too
Who are we?YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Downloads
Downloads
cheeseburger (OP5) : https://drive.google.com/file/d/11S4K-_SGOJLyHFd9hX_P_Uj_2Ai4wzQL/view?usp=sharing | https://yaap.angerycat.tk/YAAP-11-Alpha-yaap_cheeseburger-20201025.zip
dumpling (OP5t) : https://drive.google.com/file/d/1B4JIzRcl3iLmq7imzYvhrNQ3ESjfRe8U/view?usp=sharing| https://yaap.angerycat.tk/YAAP-11-Alpha-yaap_dumpling-20201025.zip
Flashing ProcedureInstall TWRP (Latest codeworkx is recommended)
Coming from a different rom / OS you'll need to clean flash:
1. Wipe data (Factory reset)
(1.1.) If coming from stock OS you may need to format internal storage
2. Flash rom
(2.1.) Flash mods (magisk, no veirty if on ext4 decrypted.)
3. Rejoice
For dirty flash just skip step 1, 1.1
and possibly 2.1 if your mods support addon.d (ex: Magisk)
It does not matter when you flash the firmware zip, and you only need to flash it once per firmware version
XDA:DevDB Information
Yet another AOSP project, ROM for the OnePlus 5
Contributors
poad42
Source Code: https://github.com/yaap
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS stable 10.0
Based On: AOSP
Version Information
Status: Alpha
Created 2020-09-15
Last Updated 2020-09-15
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Alert slider, Panel modes, HBM stuff
Permissive kernel
SafetyNet
Broken:
Encryption
Note: The ROM includes gapps with some pixel additions .
Feel like buying me some coffee for my efforts?
Donation link: https://paypal.me/generichandle
Join our chat : https://t.me/yaapop5 or https://t.me/yaapcommon
Screenshots
Congrats and Thanks for the Wonderful Support. Downloading the same...
woah! thank you so much for you work. I'm excited!
Great job Devs thank you
awesome, this is not a alpha, this is a beta :good: (my first post)
>barebones AOSP
>includes Gapps
Ok
d1n0x said:
>barebones AOSP
>includes Gapps
Ok
Click to expand...
Click to collapse
Barebones AOSP in regards to the UI because the dev's previous NitrogenOS had a bunch of customisations. I don't think that's very hard to understand. The objective is to be as barebones as possible, Gapps have nothing to do with being barebones or not.
Hello! Thank you in advance for doing this great project. It is possible to make a ROM Similar to Oxygen OS 11? I really liked this new Oxygen aesthetic. Thank you again for doing this for us.
Spider-Vice said:
Barebones AOSP in regards to the UI because the dev's previous NitrogenOS had a bunch of customisations. I don't think that's very hard to understand. The objective is to be as barebones as possible, Gapps have nothing to do with being barebones or not.
Click to expand...
Click to collapse
Yes it does. It isn't as barebones as possible in its current state because GApps is unnecessary for Android to run. It also increases the file size of the rom. False advertisation.
Besides, I've never, ever seen an initial AOSP rom for a new Android version that includes GApps on XDA. Heck, I've never seen a "barebones" AOSP rom that includes GApps. I think that's quite telling.
poad42 said:
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Broken:
Alert slider, Panel modes, HBM stuff (all need source side changes)
Permissive kernel
SafetyNet
Note: The ROM includes gapps with some pixel additions .
Click to expand...
Click to collapse
So what can be done for broken (how can we do side changes .. Permissive kernel any link for that
Tq exited for ur reply
SirSoviet said:
Yes it does. It isn't as barebones as possible in its current state because GApps is unnecessary for Android to run. It also increases the file size of the rom. False advertisation.
Besides, I've never, ever seen an initial AOSP rom for a new Android version that includes GApps on XDA. Heck, I've never seen a "barebones" AOSP rom that includes GApps. I think that's quite telling.
Click to expand...
Click to collapse
Well, actually a lot of 'AOSP' roms are just 'LineageOS based but with the AOSP interface'. Even in this case some repos are based on the LineageOS repos:
https://github.com/yaap/device_oneplus_cheeseburger/commit/62baf1aa2596ecc100b36890f2245ba832ff3cfc
robertogl said:
Well, actually a lot of 'AOSP' roms are just 'LineageOS based but with the AOSP interface'. Even in this case some repos are based on the LineageOS repos:
https://github.com/yaap/device_oneplus_cheeseburger/commit/62baf1aa2596ecc100b36890f2245ba832ff3cfc
Click to expand...
Click to collapse
The device tree was created by los yes, but has been extensively reworked both in Q and R, the cheeseburger tree is just a bunch of makefiles. The common tree is the one that has most of the stuff. So its not los based with an aosp interface or anything like that lol. Its just its own thing.
Thank you for freely sharing your great work. It is much appreciated! :highfive:
poad42 said:
Working:
Camera/Video/Mic
Fingerprint
Dash Charging/USB stuff
DRM(Netflix,prime video playback)
IMS (VoWIFI/VoLTE)
RIL
Video playback
Wi-Fi
Broken:
Alert slider, Panel modes, HBM stuff (all need source side changes)
Permissive kernel
SafetyNet
Note: The ROM includes gapps with some pixel additions .
Click to expand...
Click to collapse
It's purely already amazing bro, thx
Will redo a donation soon, keep my NOS Nand Backup for trying this A11
poad42 said:
The device tree was created by los yes, but has been extensively reworked both in Q and R, the cheeseburger tree is just a bunch of makefiles. The common tree is the one that has most of the stuff. So its not los based with an aosp interface or anything like that lol. Its just its own thing.
Click to expand...
Click to collapse
1st thing first: Congrats for working so frequently to bring up Android 11 for oneplus 5 & 5t. Brother I've suggestion not to react for users who don't understand the efforts of dev's hard work, I know how much time it takes and from where that time we manage? We cut down that time from our family, our rest and by changing our sleeping pattern. It's not our business, We're doing this just for hobby not for money. But instead of appreciation getting questions. I haven't seen if anyone has asked politely that " Sir please correct barebones word because you've included GApps". Brother again I'll say don't answer to users who always seeking your writing mistakes but not measuring your efforts and hard work.
[Thread Cleaned]
As outlined in our Forum Rules:
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
Click to expand...
Click to collapse
Please respect the wishes and decisions of the developer. You may provide constructive criticism but spewing disbelief for a feature or module that is or isn't present does not comply with the above rule.
Keep in mind there are plenty of alternatives to choose from and realize how lucky you are with a device that gets so much development love.
If you are wondering why your post was removed or edited, please feel free to drop me a PM.
Have a great day and keep it safe!
Thanks for your work mate! Great to have R for OP5. I planned to change my phone, but if I can have R as daily driver, I may wait a bit more
Do you plan to stay "barbone" or will you gradually port nitrogen's features to R?