Develop Bugs

[ROM][7.1.2_r27][STABLE] XOSP Project [Nicki][12/08/2017] - Sony Xperia M

{
"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"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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.
*
*/
What is XOSP?
XOSP is an after-market firmware based on CodeAuroraSources (CAF) destinated for a wide range of Android phones. The name stands for the Xperia Open Source Project and the project was initially created by @nilac for the Galaxy S+ (his old device) years ago when back then the ROM was called S+ Reborn. The vision was to create a minimal bloat free ROM which included Sony Xperia specific apps and various tweaks users would expect from a custom ROM.
S+ Reborn became a success and was eventually ported to different devices so from there it was rebranded to XOSP. Calin worked on the project for 2 years always trying to improve it. Eventually, Because of the fact Lollipop was buggy on his Galaxy S+, he decided to take a break from development until he got his hands on the Zenfone 2 in 2015 and from then he started again the development of XOSP and continued it ever since.
How do we release updates?
We release new updates for our Official devices each week by providing Delta updates to the users,so maintainers of the other devices can do the same as well if they want to keep up with the changes. We will make full zip releases only once a month except special cases like for example XOSPDelta is not working or something like it.
You can find all the included features right:
Here
You can find the list of current issues in the ROM right:
Here
First time installing XOSP on your Sony Xperia M, or coming from another ROM?
Make sure your Bootloader is unlocked and you're running the latest TWRP from Here
Download latest XOSP build, XOSPApps and GApps
Reboot to recovery
Full wipe
Flash latest XOSP build
Flash Dual SIM Patch (If required)
Flash GApps
Flash XOSPApps (Optional)
Flash Magisk (If you want root)
Reboot
Upgrading from earlier release or revision of XOSP:
Reboot to recovery
Flash latest XOSP build.
Flash Dual SIM Patch (If required)
Flash GApps if necessary
Flash XOSPApps (Optional)
Flash Magisk (If you want root)
Wipe cache and dalvik
Reboot
XOSPSite
XOSP Sources
Build XOSP for your device!
G+ Community
FB Page
XOSP Channel on Telegram
XOSP Community Group on Telegram
XOSP ROM
GApps
Dual SIM Patch
XOSPApps
Magisk
ROM sources
Device Tree
Kernel
Vendor
@PecanCM
@nilac and XOSP Team
CodeAuroraSources
Sony and the Xperia Community
@malybru for the XOSP banner
Mihir Mistry for the XOSP logo
XDA:DevDB Information
[XOSP] [Nougat] [Nicki], ROM for the Sony Xperia M
Contributors
Garv Maggu
Source Code: https://github.com/XOSP-Project
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Stable Release Date: 2017-07-02
Created 2017-07-02
Last Updated 2017-09-23

Reserved
SCREENSHOTS - HERE​

Reserved

ROM is very smooth. I am getting network only on 2nd sim and that also always 3G. Other than that no problem with anything. Thanks for this ROM

Please post screenshots, Make sure dual sim 2g and 3g working, Stable at all cases?
Please post screenshots, Make sure dual sim 2g and 3g working, Stable at all cases?

pa1 hack1 said:
Please post screenshots, Make sure dual sim 2g and 3g working, Stable at all cases?
Click to expand...
Click to collapse
for screenshots, maybe op will upload it later or you can try it by yourself. for Dual SIM it's depend only from dual sim user, are you know that OP is dual or single sim user? I mean if OP is single sim, then i think he can't predict this will work or not on dual sim. Since our device is already long leave from device maintainer, so you need to test it by yourself and following the procedure and i think this ROM is fully based on AOSP not lineage, so patch for dual sim will work if OP used blobs from our device maintainer. But i don't know from TheMuppets blobs.
So, please try it before you asked many question here. If you've problem, some member or OP itself will try to solve it. And for stability, you can see status of this ROM. Alpha,Beta or Stable, so please read whole thread and check main post before comment or post thread.

@pa1 hack1 I have provided screenshots. If anybody has any other questions please feel free. And @Nicklas Van Dam Regarding dual sim can we help op by providing some logs or anything?

Thank you developers, battery drain is very fast compared to original build, Microphone problem during call also persists

pa1 hack1 said:
Thank you developers, battery drain is very fast compared to original build, Microphone problem during call also persists
Click to expand...
Click to collapse
what you're mean by original build? stock rom by sony or custom lineage or aosp nougat? if you're compare it from stock ROM then you're not think about upgrading os without upgrading your current battery. And battery life itself can't survive or give same result in a times, because battery degradation . Microphone problem maybe from XOSP build, you can provide logcat when you receive a call and give that log to OP.
And please be polite on this forum, give a log or explain problem with clear explanation is needed here if you're new or not really understand about your current problem.
I don't know why, but some of new member on here not can't give clear detail about problem and said worse for some thread.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
hhjadeja007 said:
@pa1 hack1 I have provided screenshots. If anybody has any other questions please feel free. And @Nicklas Van Dam Regarding dual sim can we help op by providing some logs or anything?
Click to expand...
Click to collapse
you can help by provide logcat, i think KMSG or logcat. for kmsg or logcat, you can create easy from kernel adiutor app and go to settings or advance menu and choose create logcat,KSMG or DMESG if developers need it.
And maybe you can send PM to dev about your current problem if that problem is critical, i'm still search about this current problem too. But i'm not sure about it, since i don't have dual sim device.

---------- Post added at 02:43 AM ---------- Previous post was at 02:43 AM ----------
[/COLOR]Well I confirmed with other users and it seems like there is not a problem with dual sim patch. patch works fine but problem is maybe the procedure I follow or something else. Need to find out that.

hhjadeja007 said:
ROM is very smooth. I am getting network only on 2nd sim and that also always 3G. Other than that no problem with anything. Thanks for this ROM
Click to expand...
Click to collapse
pa1 hack1 said:
Please post screenshots, Make sure dual sim 2g and 3g working, Stable at all cases?
Click to expand...
Click to collapse
Yes, Dual SIM is working fine.
In SIM 1 - 2G is working fine.
In SIM 2 - Both 2G and 3G are working fine.
For proof, you can check the screenshots here.
Make sure to flash the patch here if you are a dual sim user.
pa1 hack1 said:
Thank you developers, battery drain is very fast compared to original build, Microphone problem during call also persists
Click to expand...
Click to collapse
Battery life is fine for me on this ROM. Check your battery stats and use the in-built Battery Adviser to check what's the issue. And there is no microphone problem during call, it is working fine, I tested it out myself.
Nicklas Van Dam said:
for screenshots, maybe op will upload it later or you can try it by yourself. for Dual SIM it's depend only from dual sim user, are you know that OP is dual or single sim user? I mean if OP is single sim, then i think he can't predict this will work or not on dual sim. Since our device is already long leave from device maintainer, so you need to test it by yourself and following the procedure and i think this ROM is fully based on AOSP not lineage, so patch for dual sim will work if OP used blobs from our device maintainer. But i don't know from TheMuppets blobs.
So, please try it before you asked many question here. If you've problem, some member or OP itself will try to solve it. And for stability, you can see status of this ROM. Alpha,Beta or Stable, so please read whole thread and check main post before comment or post thread.
Click to expand...
Click to collapse
Yeah, I have the Dual SIM variant C2004 and screenshots are added.
hhjadeja007 said:
---------- Post added at 02:43 AM ---------- Previous post was at 02:43 AM ----------
[/COLOR]Well I confirmed with other users and it seems like there is not a problem with dual sim patch. patch works fine but problem is maybe the procedure I follow or something else. Need to find out that.
Click to expand...
Click to collapse
Dual SIM is working fine, check the screenshots here.

hhjadeja007 said:
---------- Post added at 02:43 AM ---------- Previous post was at 02:43 AM ----------
[/COLOR]Well I confirmed with other users and it seems like there is not a problem with dual sim patch. patch works fine but problem is maybe the procedure I follow or something else. Need to find out that.
Click to expand...
Click to collapse
Oh okay, that's good. so patch for dual sim isn't have problem? with connectivity or internet data connectivity like 2G or 3G connection for both sim?

Can someone tell me what camera app it has? And does Radio FM works??

Dual sim working (Reinsert sim and try)
Usb data transfer not working
External storage selection not working in shareit app
Most stable ROM than any other
Battery drains faster
Very smooth and recommended to all xmd users.
Some features not included in this rom compared to lineage and cyanogenMod
Thank you very much developers

Does it uses xperia themes or hav to use substratum?

rez3vil said:
Can someone tell me what camera app it has? And does Radio FM works??
Click to expand...
Click to collapse
for camera, i think stock camera will work for both feature (camera and camcorder). But if camcorder (video recording) not work, then you can try another camera app from third party. Like google camera or other, but for google camera. Our device only can use old google camera, i think v2 for compatibility issue with new google camera.
and for radio itself, i don't know it work or not. i'm test it, but only can find a radio station but sound isn't out. I think that from my mod, and just ignore that. You need to test radio by yourself

@rez3vil FM is working fine. And dual sim is also working fine now. Actually I was using previous month's gapps. That's why dual sim was giving me problems.

After using this ROM for 3 days, mobile restarts 2 or 3 times a day, whenever i unlock screen, it strucks and automatically boots up. I am unable to take bug report, i think bug reporting itself a bug. Before testing the mobile in all aspects, dont show ROM as stable,
Battery remains at 57% for around 1 hr and suddenly switches off showing 0%.

pa1 hack1 said:
After using this ROM for 3 days, mobile restarts 2 or 3 times a day, whenever i unlock screen, it strucks and automatically boots up. I am unable to take bug report, i think bug reporting itself a bug. Before testing the mobile in all aspects, dont show ROM as stable,
Battery remains at 57% for around 1 hr and suddenly switches off showing 0%.
Click to expand...
Click to collapse
No user reported this bug so far. Make sure you have clean flashed the ROM.

pa1 hack1 said:
After using this ROM for 3 days, mobile restarts 2 or 3 times a day, whenever i unlock screen, it strucks and automatically boots up. I am unable to take bug report, i think bug reporting itself a bug. Before testing the mobile in all aspects, dont show ROM as stable,
Battery remains at 57% for around 1 hr and suddenly switches off showing 0%.
Click to expand...
Click to collapse
I m not experiencing any battery bug. Battery life is similar to stock. Yeah device do get hang sometimes and have to restart, but that only when I am using very high memory consumption apps like snapchat, which is normal I think.

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.

Code:
/*
*
* 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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.
What's working :
Boot
WiFi
Hotspot
Audio
RIL
Bluetooth
Sensors
FM
Camera
SDCard
GPS
Known issues:
VoLTE
Video recording
SELinux Enforcing
Instructions :
Download the build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Un-Official build: https://androidfilehost.com/?fid=673956719939815946
Google Apps: http://opengapps.org/
Credits : @ashwin007 (for his base trees)
LineageOS Team
XDA:DevDB Information
LineageOS 14.1 for taido, ROM for the Moto E3
Contributors
vinothvkr
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-01
Last Updated 2018-02-06

Reserved
Release - 28/01/2018
Synced with latest LineageOS source.

Reserved

Is this rom work on Moto E3 Power (XT1706)?

Darsh Monani said:
Is this rom work on Moto E3 Power (XT1706)?
Click to expand...
Click to collapse
This is a moto e3 thread and its posted in that thread so logic dictates it will work on either model of e3......
Its working on my e3 XT1700 (not power) but e3 power ROMs (XT1706) work on my e3.

Plz plz plz fix camera issues...
It's almost as if am begging for it

I wander and despair at some of these comments in ROM threads.
If its not volte, its the camera
Its not up to the ROM developments team to fix the camera.
Moto e3 never had an official 7.0 update so the camera is using a hack and that hack won't be fixed unless Motorola/lenovo release an updated source code, or mediatek release updated drivers for the processor..
Either way, posting here and begging won't get the camera or volte fixed, its going to take a long time to get the E3 camera up to AOSP standard, and to be fair, that's posted in most of the E3 rom threads, which people obviously don't read before coming here begging.....

bubba1601 said:
I wander and despair at some of these comments in ROM threads.
If its not volte, its the camera
Its not up to the ROM developments team to fix the camera.
Moto e3 never had an official 7.0 update so the camera is using a hack and that hack won't be fixed unless Motorola/lenovo release an updated source code, or mediatek release updated drivers for the processor..
Either way, posting here and begging won't get the camera or volte fixed, its going to take a long time to get the E3 camera up to AOSP standard, and to be fair, that's posted in most of the E3 rom threads, which people obviously don't read before coming here begging.....
Click to expand...
Click to collapse
A rom on YouTube claims to have the camera fixed but hotspot not working.
Channel name: Kartik Wadwa

manishah.1996 said:
A rom on YouTube claims to have the camera fixed but hotspot not working.
Channel name: Kartik Wadwa
Click to expand...
Click to collapse
It's the same Dev (samarV121) who's ROMs got removed from the E3 thread here on XDA if you didn't already know?
I've tried all of those 7.1.2 ROMs on my E3 (not power) and the camera isn't working on any of them, despite the claims otherwise.....
When you download one of those ROMs, the download link takes you to samarV121 android file host folder.
That's not a coincidence !
When I reported the fact the camera doesn't in fact work, I had a reply it was my fault for installing the ROM incorrectly on an "incompatible" device.
Strangely I never got a reply when I took the battery out of my E3 and sent a photo back of the label inside where it quite clearly states Motorola E3 XT1700......

bubba1601 said:
I wander and despair at some of these comments in ROM threads.
If its not volte, its the camera
Its not up to the ROM developments team to fix the camera.
Moto e3 never had an official 7.0 update so the camera is using a hack and that hack won't be fixed unless Motorola/lenovo release an updated source code, or mediatek release updated drivers for the processor..
Either way, posting here and begging won't get the camera or volte fixed, its going to take a long time to get the E3 camera up to AOSP standard, and to be fair, that's posted in most of the E3 rom threads, which people obviously don't read before coming here begging.....
Click to expand...
Click to collapse
All devices on LineageOS have their camera working on hacks - mostly by using BLOBs anyway. If the Camera is working, then the same part of the program which allows the device to access the Camera's BLOB should let the Camcorder of the device to communicate with it at that required DPI and resolution. From what I've figured out in some ROMs like those of SamarV which were blocked, his camcorder gets initialized, it's able to set the audio as well as the video source as it detects the camera when we switch to 'Video' mode and we are also able to select the format of the video that we are going to record, but is not able to prepare the camera for recording and crashes (falls on a error loop of some kind). While in ROMs like ashwinr's here, the application is not able to set the source of the video (detect device camera itself) and crashes. This is just a layman's view of the problem and it's probably already known by developers lol.
I'm not a coder, but it's just me trying to figure out the problem in my way and I do know for now the devs are literally working blind lol. *pun intended* So it's not entirely on the hands of the company of the device or the processor. But agreed, MediaTek is pretty useless when it comes to giving latest support to some recent past processors of theirs.

Does this ROM supports substratum?

Stuck on error 7

androidlover420 said:
Stuck on error 7
Click to expand...
Click to collapse
Try TWRP by ashwin
---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------
Camera isn't working

apurav.812 said:
Try TWRP by ashwin
---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------
Camera isn't working
Click to expand...
Click to collapse
Did you read the OP? (original post)
Its listed the camera doesn't work........
Just go back a page and read the comments..

bubba1601 said:
Did you read the OP? (original post)
Its listed the camera doesn't work........
Just go back a page and read the comments..
Click to expand...
Click to collapse
Yes I read the op

apurav.812 said:
Yes I read the op
Click to expand...
Click to collapse
Did you read the last page?
I'm not trying to be mean to you but on the last page there is a discussion about the camera, and its said its going to take a LONG time to fix.
Its better to read that sort of thing rather than keep posting about it, because I don't think this ROM is being developed anymore and the dev has moved to YOU TUBE......
I'm just trying to help you, the camera isn't going to be a quick fix.
Sorry.

Cannot connect to camera. where op says Camera working.
Please patch

Twrp error !
it is showing that "Updater Process Ended With Error 7" please help me:crying:
---------- Post added at 05:09 PM ---------- Previous post was at 05:00 PM ----------
twrp says that updater process ended with error 7. pls help me......:crying:

Narendranath said:
it is showing that "Updater Process Ended With Error 7" please help me:crying:
---------- Post added at 05:09 PM ---------- Previous post was at 05:00 PM ----------
twrp says that updater process ended with error 7. pls help me......:crying:
Click to expand...
Click to collapse
You have to flash the twrp given by him in this thread which is unique to this rom.
Each ROM build usually has their own unique recovery so unless he made the ROM build to work a generalised recovery, it will show the Error 7. Enjoy!

DystopianDJ said:
You have to flash the twrp given by him in this thread which is unique to this rom.
Each ROM build usually has their own unique recovery so unless he made the ROM build to work a generalised recovery, it will show the Error 7. Enjoy!
Click to expand...
Click to collapse
But there is no any specific recovery mentioned above

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! These builds are experimental and can contain Bugs (as listed above). Make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Special thanks to @derf elot and @modpunk for most of the work on the yoshino platform.
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia XZ Premium
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2019-08-24
Last Updated 2019-08-28

Downloading,I will feedback

Sorry for my bad english
But I found some problems:
1. NFC is not working, I cant open NFC
2.Fingerprint sensor is insensitive,
when I try to create my fingerprint,the system says "It has stains on sensor." but I have cleaned already
Sorry it seems that is my problem , please ignore it.
3.Style Cover Stand SCSG10 is working inappropriate (same problem on early oreo builds)
when i covered up, xzp couldn't sleep
4.Mobile data cant work
others seems work perfectly
My firmware is 47.2.A.10.107
---
Edit:
I changed firmware to 47.1.A.16.20, NFC can work now
SCSG10 still works inappropriately, and Mobile data doesn't work. (only calls / sms)
But now the system says "your vendor doesn't match to your system".

1,NFC is dead
2,G8142 card 2 can't be recognized
3,Network not available
（basic on .107）
other things working Great！！！
how about make Camera Switch available？

I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Edit: found the cause for the mobile data, must've removed that by accident during a cleanup. A working build will be released later today
EDIT2: Build is running right now and will appear on the download page once done.

Can anyone confirm camera2api and gcam hdr+ support?

Thanks for fixing Mobile data and now it works.
NFC is also working, but need reboot after gapps setup wizard or first boot, I dont know if this is a problem.
(Just clean flash 47.2.A.10.107, I dont know why i cant open nfc in my first try. I clean flashed before...)
Incrovantilist said:
Can anyone confirm camera2api and gcam hdr+ support?
Click to expand...
Click to collapse
No, this rom blobs are based stock, so no level3 support.

Just flashed the rom and its smooth and awesome. So far everything working except dt2w.
For some reason with Magisk 19.3, ctsProfile is returning false. It didnt fail in any of the other SODPs or the latest stock rom. Anyone facing same issue?

Myself5 said:
I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
Click to expand...
Click to collapse
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Myself5 said:
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Click to expand...
Click to collapse
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.

LSS4181 said:
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Click to expand...
Click to collapse
Given it works on both my phones that were on .107 before and that the blobs are from .107, this could be the cause. If you flash the latest stock ROM make sure to fully boot into it at least once because the stock ROM sometimes also upgrades the NFC Firmware on the chip itself.
P.S. The kernel is the same as cryptomilks.
LSS4181 said:
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.
Click to expand...
Click to collapse
Oh cmon man you literally quoted a message of me saying that I don't have the Dual SIM variant nor any testers for it (yet). I have quite a few ideas on how I could fix it, but without any testers I'm just not gonna touch it at all.

I have G8142 and I can say, "Yes, SD card still works on G8142."
But I dont have 2nd sim card so i cant test if dualsim works

.107 clean installation, there were also problems with NFC, after rebooting it was fixed.

The Smart Cover function does not work, the screen continues to light after closing the cover, or the action of the magnetic cover (by the Hall sensor), I do not know how it should, but it does not work ..

So far stable enough to be daily driver except issues with magisk. Magisk keeps getting uninstalled on its own and have to be reinstalled in twrp every now and then. And after it gets installed, the rom stutters and doesn't open any apps or the settings and have to be restarted a few times for it to go back to normal.
Also a feature to modify charging led settings would be awesome. (I tried to find and modify it in root but couldn't find the charging led settings in /sys/class/leds)
Camera is frickin awesome. It's sooo much better than stock even without lvl3 camera2api. For anyone trying to find a decent camera app, try using opencamera with camera2api enabled in settings. Except for hdr(doesn't work, will force close), it's able to take really good images. If only somehow able to shoot 960fps slomo .

Magisk 19.3 - there were no problems with self-removal, there is a delay when starting up applications with a white screen after a reboot, it holds the battery well 2% per night.

I spent some time working with @haiha2001 on the XZ1 Dual today. Along the road we came across a few things but it's not working yet. HOWEVER, the XZ1 seems to have a different/more advanced issue than the XZ Premium. Whereas the XZ Premium has SIM1 working, the XZ1 doesn't have any SIM working at all.
That brings me to the following:
There was a fairly obvious flaw (thank Sony for that for not having unity of system property locations across Single/Dual SIM) which could explain why only one SIM is working on the XZ Premium. I've fixed it in the linked boot.img. If someone with two SIM Cards and the Dual SIM variant could try and let me know how it's doing on maple_dsds I'd be very happy.
https://dl.myself5.de/maple/.fwafwafwafo/boot.img
flash it via fastboot with
Code:
fastboot flash boot boot.img
on top of the latest weekly.

Just flashed your boot.IMG
I'll put in the wife's sim and see

Myself5 said:
I spent some time working with @haiha2001 on the XZ1 Dual today.
Click to expand...
Click to collapse
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.

Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
Because I see the XZ1 seems to be less supported by programmers for this device while the XZ Premium has quite a lot, while I know that the XZ Premium is not too different from the off-screen XZ1, so I'm willing to support the programmers to check the rom or mod version for XZ1, if they have an idea I will help my best ?
Sent from my Sony G8342 using XDA Labs

beammer335d said:
Just flashed your boot.IMG
I'll put in the wife's sim and see
Click to expand...
Click to collapse
Did she voluntarily gave it to you yet or do we need to send armed troops to make her ? First screenshot looks promising already.
also, in case you're rooted, please get me the output of the following:
Code:
adb shell
then enter
Code:
su
(Accept Magisk request on the phone)
and then run
Code:
cat /cache/modem/modem_switcher_status
cat /cache/modem/modem_switcher_report
And send me the output.
Alternatively you can run it via terminal emulator starting at the "su" part.
Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
+1

Nothing would be possible without the work of @MrColdbird and the help of @Franssen​
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
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. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Firmware Version 9.9.3
Download link: https://drive.google.com/open?id=142PC3GNCnfrp4h5RGGSn-qV9aSZFE5M0
Latest Stable Release Version 14.0
Download link: https://mega.nz/#!C1tDyIBB!-2cpzfdKYDA05U6-SfQHqXpnzGgyHqqsbtopZjQntTY
Mirror: https://drive.google.com/open?id=1BJ1QtmPNF8Rqx80xsw_IUfKjHq0yOy0_
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet released for Pie, however you can try to use edxposed .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the FIRMWARE then ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work) and Magisk (root).
6. Reboot and set up your device,
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
Kernel source:
https://github.com/rr-mario/msm-4.4./stable
Device tree source:
https://github.com/Skyllery/device_xiaomi_nitrogen/tree/aicp-pie
Vendor source:
https://github.com/Black-Seraph/vendor_xiaomi_nitrogen/pie
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds[/B]
Contributors:
@MrColdbird @Franssen @Mario_R and my testers (Gryphon_D)
You want to see a "normal" night at the "DEV office", click here!!​
XDA:DevDB Information
AICP, ROM for the Xiaomi Mi Max 3
Contributors
Skyllery, MrColdbird, Franssen
Source Code: https://github.com/Skyllery/device_xiaomi_nitrogen/tree/aicp-pie
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.9.3
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.0
Stable Release Date: 2019-09-21
Created 2019-09-21
Last Updated 2019-10-17

Finally, AICP is out.

Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect

rudiratlos57 said:
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
Click to expand...
Click to collapse
Currently best ROM? Please explain why..

GEoMaNTiK said:
Currently best ROM? Please explain why..
Click to expand...
Click to collapse
The other roms Like Aoisp, havoc, Fest, lineage and the rest of it, always after a couple hours of usage, always start lagging to open apps and other. This one i have 24 Hrs, and still strong whit no problem. Don't ask me why but, for me right now, its perfect.

rudiratlos57 said:
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
Click to expand...
Click to collapse
Sorry but didn't understand what you mean. BTW i'm mostly a builder and modding AICP source code is far from my knowledge.
Regards

eloyho said:
The other roms Like Aoisp, havoc, Fest, lineage and the rest of it, always after a couple hours of usage, always start lagging to open apps and other. This one i have 24 Hrs, and still strong whit no problem. Don't ask me why but, for me right now, its perfect.
Click to expand...
Click to collapse
I'm using Revenge and it's as snappy as I've found... I've also underclocked my CPU and its quick!!!

GEoMaNTiK said:
I'm using Revenge and it's as snappy as I've found... I've also underclocked my CPU and its quick!!!
Click to expand...
Click to collapse
Remember we use the same device tree to build everything, GismoBe, Me, etc. It's mostly rom reputation and usage. There's no best or worst, we build as anyone can find what works for him.
Regards

@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:

shingers5 said:
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
Click to expand...
Click to collapse
It's because Revenge OS is not build by me ^^ It's Franssen (GismoBe on Telegram) but he's not much on XDA these days. I already tell him why there's not all their ROMS (AOSMP, Revange, etc) but he don't have much time.
Not tried it already .. open beta seems to be on 27th. I think i'll wait to xiaomi.eu or try to go on 10 gsi to see how it is. (Didn't look at this for the moment)
Regards

Skyllery said:
It's because Revenge OS is not build by me ^^ It's Franssen (GismoBe on Telegram) but he's not much on XDA these days. I already tell him why there's not all their ROMS (AOSMP, Revange, etc) but he don't have much time.
Not tried it already .. open beta seems to be on 27th. I think i'll wait to xiaomi.eu or try to go on 10 gsi to see how it is. (Didn't look at this for the moment)
Regards
Click to expand...
Click to collapse
i am trying it now guess xiaomi.eu will translate.and release soon. i like it and.the changes are nice. not bad for forst beta

shingers5 said:
i am trying it now guess xiaomi.eu will translate.and release soon. i like it and.the changes are nice. not bad for forst beta
Click to expand...
Click to collapse
On my side still on aex for the moment, in fact my preferred ROM builded by me. (Specially for battery backup)
Will try the beta tomorrow look promising .. but miui have some little things which kept me away to use it more than two days.
Sim activation by sending a sms to china (paid)
Region limitation for community access and theme options..
Poor theming compared to custom ROMs.
But it looks promising will give it a chance.
Regards
Sent from my MI MAX 3 using XDA Labs

shingers5 said:
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
Click to expand...
Click to collapse
Where to find the beta leak, what is the telegram page? Oh wow XDA posted them all as twrp recovery files.

Skyllery said:
On my side still on aex for the moment, in fact my preferred ROM builded by me. (Specially for battery backup)
Will try the beta tomorrow look promising .. but miui have some little things which kept me away to use it more than two days.
Click to expand...
Click to collapse
Tries AEX a few weeks back, it cannot run my banking apps, even with Magisk Hide. Malaysia Maybank and Singapore DBS, no choice but to give it up. Any changes since then? Any idea how to fix it? Thanks.

Awesome ROM.. have been using for a little under 24hrs.
I had a problem with Revenge, out of the blue my Mi Max 3 went into a bootloop.. did nothing different and no idea why...
One thing I've noticed since going to AICP,, my 5GHz wirelsss network keeps coming up as Disabled, after it briefly connects. The 2.4GHz network is working without problems and stays connected.
Anyone else having this problem or can help with what it might be?
All other custom ROMs haven't had an issue with 5GHz.

Wmateria said:
Where to find the beta leak, what is the telegram page? Oh wow XDA posted them all as twrp recovery files.
Click to expand...
Click to collapse
its a proper full flashable zip. its the Nitrogen Cloud telegrsm group. its Mi Max 3 specific.
https://t.me/NitrogenCloud/1879

GEoMaNTiK said:
Awesome ROM.. have been using for a little under 24hrs.
I had a problem with Revenge, out of the blue my Mi Max 3 went into a bootloop.. did nothing different and no idea why...
One thing I've noticed since going to AICP,, my 5GHz wirelsss network keeps coming up as Disabled, after it briefly connects. The 2.4GHz network is working without problems and stays connected.
Anyone else having this problem or can help with what it might be?
All other custom ROMs haven't had an issue with 5GHz.
Click to expand...
Click to collapse
Yes got the same here
Regards
Sent from my MI MAX 3 using XDA Labs

Skyllery said:
Yes got the same here
Regards
Sent from my MI MAX 3 using XDA Labs
Click to expand...
Click to collapse
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
---------- Post added at 08:00 AM ---------- Previous post was at 07:41 AM ----------
GEoMaNTiK said:
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
Click to expand...
Click to collapse
Ohh damn, typed too soon ... The 5GHz connection just dropped out again and can't get it back on.
2.4GHz working without issue still.

GEoMaNTiK said:
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
---------- Post added at 08:00 AM ---------- Previous post was at 07:41 AM ----------
Ohh damn, typed too soon ... The 5GHz connection just dropped out again and can't get it back on.
2.4GHz working without issue still.
Click to expand...
Click to collapse
You use correct firmware provided in op or some modded one ?
It didn't happen to me since a while. It's on every ROM but not so often. Or try to flash modem fix.ysl.zip on channel or group you'll find it. To restart modem.
Regards
Sent from my MI MAX 3 using XDA Labs

Skyllery said:
You use correct firmware provided in op or some modded one ?
It didn't happen to me since a while. It's on every ROM but not so often. Or try to flash modem fix.ysl.zip on channel or group you'll find it. To restart modem.
Regards
Click to expand...
Click to collapse
Have just moved to the latest Xtended ROM and have no issues with 5GHz wifi, same as the previous Revenge ROM with no issues.
Very strange.