{
"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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei Mate 9.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei Mate 9
Contributors
OldDroid, XePeleato, rcstar6696, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27
Thanks for this! I am running the CarbonROM Beta 2 from the partner builds (released July 17). I notice that there is now an official version that is also labeled as Beta 2, but was released five days later (July 22). Can I flash the official build without going back to full stock first? Also, the newer build is significantly smaller: 599MB versus 1.6 GB. Is that because the newer build doesn't include GAPPS?
Thanks again and sorry if I missed the answers to these questions.
As an aside, I'm really liking CarbonROM. Great battery life and very smooth.
tim.malone said:
Thanks for this! I am running the CarbonROM Beta 2 from the partner builds (released July 17). I notice that there is now an official version that is also labeled as Beta 2, but was released five days later (July 22). Can I flash the official build without going back to full stock first? Also, the newer build is significantly smaller: 599MB versus 1.6 GB. Is that because the newer build doesn't include GAPPS?
Thanks again and sorry if I missed the answers to these questions.
As an aside, I'm really liking CarbonROM. Great battery life and very smooth.
Click to expand...
Click to collapse
the newer builds are xz compressed, you have to decompress them first.
If its the same rom (e.g. carbon -> carbon) you don't have to do a factory reset.
Regards
Thanks! And now I realize that I can't read and misread OmniROM for CarbonROM. Oops.
OldDroid said:
the newer builds are xz compressed, you have to decompress them first.
If its the same rom (e.g. carbon -> carbon) you don't have to do a factory reset.
Regards
Click to expand...
Click to collapse
What's the difference between OpenKirin LOS and Phusson's LOS?
kkslider1 said:
What's the difference between OpenKirin LOS and Phusson's LOS?
Click to expand...
Click to collapse
Phh LOS is a generic build meant for any device with treble support. The OpenKirin build is specifically targeted to Kirin devices.
Most of the changes are for dealing with the ways Huawei did things differently than everyone else. Also built in is the Huawei camera app, so (most of) the native camera functionality is available.
irony_delerium said:
Phh LOS is a generic build meant for any device with treble support. The OpenKirin build is specifically targeted to Kirin devices.
Most of the changes are for dealing with the ways Huawei did things differently than everyone else. Also built in is the Huawei camera app, so (most of) the native camera functionality is available.
Click to expand...
Click to collapse
Thanks! I want to try OpenKirin LOS (OKLOS), but how will I be able to flash Magisk without TWRP? OpenKirin LOS says that it requires the stock EMUI recovery, so how can I flash Magisk?
---------- Post added at 12:08 PM ---------- Previous post was at 11:38 AM ----------
Okay, so I clean flashed OpenKirin LOS Beta 5 on my MHA-L29. Fingerprint gestures are disabled/greyed-out despite the Mate 9 having a rear fingerprint sensor. Fingerprint gestures worked perfectly on Phh LOS, so I'm not sure why OKLOS isn't working on that end.
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Another issue I found: On OKLOS, the Mate 9's secondary top speaker isn't working when playing media. To be fair, it didn't work on Phh LOS either, so I'm not sure if that's an issue you guys can fix.
kkslider1 said:
Thanks! I want to try OpenKirin LOS, but how will I be able to flash Magisk without TWRP? OpenKirin LOS says that it requires the stock EMUI recovery, so how can I flash Magisk?
Click to expand...
Click to collapse
Use 'fastboot' command.
-> extract stock boot image, patch it by magisk manager, flash patched boot image by fastboot.
Or you can install (patch boot image and replace it ) in magisk manager directly.
michael_hamada said:
Use 'fastboot' command.
-> extract stock boot image, patch it by magisk manager, flash patched boot image by fastboot.
Or you can install (patch boot image and replace it ) in magisk manager directly.
Click to expand...
Click to collapse
Thanks! Much appreciated!
After a few days of running on my Mate 9, OKLOS is running super smooth! Much smoother than Phh LOS. Hoping @OldDroid and the team can address a few of the bugs listed in my earlier post. Keep it up!
kkslider1 said:
Thanks! I want to try OpenKirin LOS (OKLOS), but how will I be able to flash Magisk without TWRP? OpenKirin LOS says that it requires the stock EMUI recovery, so how can I flash Magisk?
---------- Post added at 12:08 PM ---------- Previous post was at 11:38 AM ----------
Okay, so I clean flashed OpenKirin LOS Beta 5 on my MHA-L29. Fingerprint gestures are disabled/greyed-out despite the Mate 9 having a rear fingerprint sensor. Fingerprint gestures worked perfectly on Phh LOS, so I'm not sure why OKLOS isn't working on that end.
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Another issue I found: On OKLOS, the Mate 9's secondary top speaker isn't working when playing media. To be fair, it didn't work on Phh LOS either, so I'm not sure if that's an issue you guys can fix.
Click to expand...
Click to collapse
disable the navbar to turn on navigation gestures.
This will be adressed in the next los beta so you can toggle the nav gestures with navbar enabled.
EDIT: please have a look at our telegram group if you need any guidance regarding the installation of magisk without a custom recovery (e.g. twrp).
Regards
i have a question , is it possible that ota to pie from lineageOS beat5 wihtout back to emui8
fate forget said:
i have a question , is it possible that ota to pie from lineageOS beat5 wihtout back to emui8
Click to expand...
Click to collapse
Flash new ROM & stock ramdisk (if you rooted with Magisk). Factory reset with stock recovery.
irony_delerium said:
Flash new ROM & stock ramdisk (if you rooted with Magisk). Factory reset with stock recovery.
Click to expand...
Click to collapse
thanks,I'm sorry for bothering you that,do you know how long will openkirin ROMs(for mate9) update everytime?
fate forget said:
thanks,I'm sorry for bothering you that,do you know how long will openkirin ROMs(for mate9) update everytime?
Click to expand...
Click to collapse
@OldDroid @irony_delerium This is something I'm also curious about. What is the average time between the 5 Betas for OKLOS? The changelog only shows the release date of the latest beta, not the previous versions.
kkslider1 said:
@[email protected]_delerium This is something I'm also curious about. What is the average time between the 5 Betas for OKLOS? The changelog only shows the release date of the latest beta, not the previous versions.
Click to expand...
Click to collapse
monthly security patches are guaranteed.
Regards
hello,
is there any way how the bugs should be reported?
In LOS Beta 5 I discovered that if trying to enable Bluetooth trigger in a Profile, the Settings crash. My phone is Mate 9.
PS Otherwise, the only thing I can say is Hats off to the developers! When I received the phone as a replacement (for a broken Nexus 6p) I thought "oh, crap: no Snapdragon, no LOS". This really made my day!
vedko said:
hello,
is there any way how the bugs should be reported?
In LOS Beta 5 I discovered that if trying to enable Bluetooth trigger in a Profile, the Settings crash. My phone is Mate 9.
PS Otherwise, the only thing I can say is Hats off to the developers! When I received the phone as a replacement (for a broken Nexus 6p) I thought "oh, crap: no Snapdragon, no LOS". This really made my day!
Click to expand...
Click to collapse
i'm aware of this issue. It will be adressed in the next update.
Regards
OldDroid said:
i'm aware of this issue. It will be adressed in the next update.
Regards
Click to expand...
Click to collapse
Thanks.
Although I meant it mainly as a general questions where the bugs should be brought up. In this thread? Or in the Telegram channel referenced in the 1st post? Or...?
PS I found out that NFC is not working, but that seems to be a known issue.
errors in logcat (omnirom)
Hello,
I am trying out OmniROM and I have been getting less than stellar battery life (though still acceptable). I took a look at the MatLog app and noticed a bunch of errors that keep coming up. One of them is from BatteryExternalStatsWorker: "no controller energy info supplied for wifi".
I googled around a bit and it appears this has popped up on other ROMs and it seems to be related to a missing API. There are other errors as well, many of them thrown by HWComposer: "invalid layer type change".
I have no idea if these are impacting battery life, but an error is an error.
I attached a zip with logs from MatLog.
Thanks.
Dear MR.OldDroid
Is it possible for you to add UMS (USB mass storage function, connect pc and turn Micro SD card in photo to be a removable flash disk on PC) into the Kernel? I like this function, it is much better than MTP function.
Thank you very much.
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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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. You can also view the Changelog for a full list of changes & features.
What's not working :
cool issues list
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=271106
https://sourceforge.net/projects/luk-lineageos/files/charlotte/lineage-15.1
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][charlotte][8.1] LineageOS 15.1, ROM for the Huawei P20 Pro
Contributors
LuK1337
Source Code: https://github.com/berkeley-dev
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-05-18
Last Updated 2018-08-30
Yes!!
Lineage!!
This is so exciting!!!
Thank you ?️
Sent from my CLT-L29 using XDA Labs
I didn't know it was possible to get Lineage up and running on the Kirin chips! This is great! Was it made easier because of Treble?
reeved said:
I didn't know it was possible to get Lineage up and running on the Kirin chips! This is great! Was it made easier because of Treble?
Click to expand...
Click to collapse
https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/
Warning: the LineageOS developers who created this ROM posted about this on the Honor View 10 forum, and state that it should work on any device with a HiSilicon Kirin 970
Click to expand...
Click to collapse
This makes me moist
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
Can we just flash magisk ontop in twrp?
I'll test soon enough
I'm hopeful that lineage will unleash this phones full potential without the bloat of emui
a question, what about the Huawei specific camera features like night mode etc? Thank you
faremoney said:
a question, what about the Huawei specific camera features like night mode etc? Thank you
Click to expand...
Click to collapse
Likely to be broken along with Desktop mode as well, which is a bit of a kicker really. Will see how this works and maybe if WiFi calling is functional I might stick with it.
DaveP2611 said:
Likely to be broken along with Desktop mode as well, which is a bit of a kicker really. Will see how this works and maybe if WiFi calling is functional I might stick with it.
Click to expand...
Click to collapse
Surely it would be possible to port over the P20 Pro camera app to Lineage? Phh ported over the Mate 10 camera for use with the Treble roms so I don't see why it shouldn't be possible.
i hope the devs manage to port the camera features then, because a stock experience on p20 pro would be dope but the camera is the killer feature for me on this phone
reeved said:
Surely it would be possible to port over the P20 Pro camera app to Lineage? Phh ported over the Mate 10 camera for use with the Treble roms so I don't see why it shouldn't be possible.
Click to expand...
Click to collapse
Oh I'm not saying it won't get ported, but I've always assumed that Lineage as it comes is stock, but there is nothing to stop ports happening, just wouldn't expect it to be included in the ROM
DaveP2611 said:
Oh I'm not saying it won't get ported, but I've always assumed that Lineage as it comes is stock, but there is nothing to stop ports happening, just wouldn't expect it to be included in the ROM
Click to expand...
Click to collapse
Oh yeah, for sure. It would be interesting to see however if this works on the Non Huawei ROMs.
https://forum.xda-developers.com/p10/themes/huawei-p20-pro-camera-apk-t3778392
reeved said:
Oh yeah, for sure. It would be interesting to see however if this works on the Non Huawei ROMs.
https://forum.xda-developers.com/p10/themes/huawei-p20-pro-camera-apk-t3778392
Click to expand...
Click to collapse
if someone can try...
(i'm still waiting for unlocking codes -_- )
faremoney said:
if someone can try...
(i'm still waiting for unlocking codes -_- )
Click to expand...
Click to collapse
I flashed Lineage for the honor view 10 a few days ago and moved camera libs and apk into priv-app. Night mode and AI definitely worked, but the UI scale for the app was totally wrong.
Edit: to clarify I have a P20 pro and flashed the honor view 10 Lineage onto it.
First of all @LuK1337 - big thank you!
If I might be so bold as to offer a suggestion, though:
@surdu_petru has successfully baked stock Huawei camera into AOSP based ROMs. If you're not already considering it or working on it, perhaps he could give you some tips on how to make it work.
There's also this thread, which you're probably aware of. https://forum.xda-developers.com/pr.../huawei-stock-camera-app-treble-roms-t3735169 Though obviously it'll need the latest version of stock camera - preferably from 120 firmware.
It would also probably be preferable to port the Huawei stock Gallery app, thereby eliminating the last issue with ported stock camera.
Again, thanks!
Edit: I see people are already talking about this.
Shaolin36 said:
I flashed Lineage for the honor view 10 a few days ago and moved camera libs and apk into priv-app. Night mode and AI definitely worked, but the UI scale for the app was totally wrong.
Edit: to clarify I have a P20 pro and flashed the honor view 10 Lineage onto it.
Click to expand...
Click to collapse
where are the camera libs?
mudnightoil said:
First of all @LuK1337 - big thank you!
If I might be so bold as to offer a suggestion, though:
@surdu_petru has successfully baked stock Huawei camera into AOSP based ROMs. If you're not already considering it or working on it, perhaps he could give you some tips on how to make it work.
There's also this thread, which you're probably aware of. https://forum.xda-developers.com/pr.../huawei-stock-camera-app-treble-roms-t3735169 Though obviously it'll need the latest version of stock camera - preferably from 120 firmware.
It would also probably be preferable to port the Huawei stock Gallery app, thereby eliminating the last issue with ported stock camera.
Again, thanks!
Edit: I see people are already talking about this.
Click to expand...
Click to collapse
I'm not going to work on EMUI Camera. Also Surdu wasn't really responsible for porting it, it was phh that did the actual work.
LuK1337 said:
I'm not going to work on EMUI Camera. Also Surdu wasn't really responsible for porting it, it was phh that did the actual work.
Click to expand...
Click to collapse
how is the camera on this lineage?
i flashed it but it required me to do a wipe on my /data so i had to skip it for the time being (cant setup my phone right now)
so i reverted back.
virtyx said:
how is the camera on this lineage?
i flashed it but it required me to do a wipe on my /data so i had to skip it for the time being (cant setup my phone right now)
so i reverted back.
Click to expand...
Click to collapse
No idea, even if I had this device I would pretty much never use the camera. I only have View 10 right now which is my main kirin970 dev phone (I may have Honor 10 too in the future, we'll see).
LuK1337 said:
I'm not going to work on EMUI Camera. Also Surdu wasn't really responsible for porting it, it was phh that did the actual work.
Click to expand...
Click to collapse
I know. My point was that he has now taken phh's work and baked it into custom ROMs successfully.
If you have no intention of doing so, hopefully others may pick up the baton now that you've released the first LOS / AOSP ROM for the P20 Pro.
mudnightoil said:
I know. My point was that he has now taken phh's work and baked it into custom ROMs successfully.
If you have no intention of doing so, hopefully others may pick up the baton now that you've released the first LOS / AOSP ROM for the P20 Pro.
Click to expand...
Click to collapse
There's no reason to do that. People that really want to use phh's camera app can just add it without my help.
{
"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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Honor 8 Pro/Honor V9.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Honor 8 Pro
Contributors
OldDroid, XePeleato, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS
Version Information
Status: Beta
Created 2018-07-14
Last Updated 2018-08-27
Glad to see this here. I thought custom ROM development for DUK-L09 is dead. I've been using RROS for the past month now. Everything necessary for a daily driver is working. Overall experience is very smooth. Minor bugs I encountered - NFC switch is not available, some features in the RROS configuration menu are not working.
I hesitate to flash LineageOS, is it stable enough and functional for a daily driver ? Are there any issues still present on the Honor 8 Pro?
Is the photo quality the same as on the stock ROM ? And does USB debugging work ?
In the meantime, thank you for your work
nK_BlaZy said:
I hesitate to flash LineageOS, is it stable enough and functional for a daily driver ? Are there any issues still present on the Honor 8 Pro?
Is the photo quality the same as on the stock ROM ? And does USB debugging work ?
In the meantime, thank you for your work
Click to expand...
Click to collapse
Yes as a daily driver, I've had it for a month. Camera quality stock quality for the basics however if you switch between camera and video it does stop and you have to restart. Other thing for me at least is that the Bluetooth audio works perfectly to my car BUT phone calls do not. But still much better than EMUI for me at least. Hope that helps you decode
Oh and yes USB debugging is how you flash it and works like a charm.
lunchplease said:
Other thing for me at least is that the Bluetooth audio works perfectly to my car BUT phone calls do not.
Click to expand...
Click to collapse
Do bluetooth phone calls work for you with other bluetooth devices (other than your car) ?
Because I call in bluetooth quite regularly...
nK_BlaZy said:
Do bluetooth phone calls work for you with other bluetooth devices (other than your car) ?
Because I call in bluetooth quite regularly...
Click to expand...
Click to collapse
You know....I haven't tried...but I will, and report back!
Will you ever add Kirin 650?
Can you only flash this via stock recovery and not twrp?
Vinzee said:
Can you only flash this via stock recovery and not twrp?
Click to expand...
Click to collapse
Please check out the website before posting any queries. Well it doesn't look like they will be answered anyway. It's as if the devs are under some obligation to make ROMs for kirin devices, since they almost never give updates to their ROMs.
OldDroid said:
We support 3 ROMs in total as of now - LineageOS (Unofficial), CarbonROM (Official), ResurrectionRemix OS (Official from Beta 2+)
Click to expand...
Click to collapse
Hello! Thank you for your hard work! You are doing great job.
Can I download RROS rom only from your site? I'm asking because I found this:
https://sourceforge.net/projects/resurrectionremix-oreo/files/kirin/
and I don't know if it's your release
procent said:
Hello! Thank you for your hard work! You are doing great job.
Can I download RROS rom only from your site? I'm asking because I found this:
https://sourceforge.net/projects/resurrectionremix-oreo/files/kirin/
and I don't know if it's your release
Click to expand...
Click to collapse
RR beta2 released today, now it's an official rom! You can download it from openkirin.net or sourceforge
cannot find the files on the sourceforge.
do you know the codename or the folder link?
i cannot find duk*
000001a said:
cannot find the files on the sourceforge.
do you know the codename or the folder link?
i cannot find duk*
Click to expand...
Click to collapse
Look for 'kirin', it's a generic build for 65x/95x/960/970 devices.
rongz said:
RR beta2 released today, now it's an official rom! You can download it from openkirin.net or sourceforge
Click to expand...
Click to collapse
RROS beta2 update is much smoother than the previous one. I feel there are battery improvements too. Fast charge is working properly, so that's great. Video camera seems to be working in order. Thanks RR team!
Few bugs I encountered -
-NFC seems to be missing.
-There is no option to select default keyboard. ( I had to disable other keyboard so I can use the one I want to use)
-It show SD card is corrupted and needs to format but is unable to mount it. It is automatically (temporary) fixed after a couple of reboot, no need to format. Issue returns after another reboot
irony_delerium said:
Look for 'kirin', it's a generic build for 65x/95x/960/970 devices.
Click to expand...
Click to collapse
in this folder is a *.img.xz
other folders have *.zip
is this OTA-able?
Using RROS Beta 2
- Heating issue while charging (Too Hot to handle), never happened on Stock ROM
- UI feels more of Tab like (Running it on 600 DPI settings)
- Disabled one SIM, but still shows both even I selected the option of Hiding it in the Settings
Apart from this, it is amazing!
dising007 said:
Using RROS Beta 2
- Heating issue while charging (Too Hot to handle), never happened on Stock ROM
- UI feels more of Tab like (Running it on 600 DPI settings)
- Disabled one SIM, but still shows both even I selected the option of Hiding it in the Settings
Apart from this, it is amazing!
Click to expand...
Click to collapse
No heating issues here. I suppose running on 600DPI will show a tab like UI, try default DPI.
Update available
RROS and Omni ROM beta 3 available now!
Help. I AM STUCK WITH FRP LOCK on my Honor 8 pro. I flashed the custom resurrection remix system image after resetting my device. So the Resurrection Remix boot up fine with my Google account but i cannot flash twrp recovery to get root.
@NIKHIL JOHN: wrong thread for your problem. also see: https://openkirin.net/support/ => no twrp support
please ask in the twrp thread: https://forum.xda-developers.com/honor-8-pro/development/wip-twrp-3-1-1-0-duk-t3625798
good luck for solving your issue
{
"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"
}
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Also does any build from now on require a vendor partition, by doing this you will lose the ability to flash official builds provided by ZTE. Any failure in this process of flashing or repartitioning could lead to an unrecoverable bricked device.
What's not working:
SELinux is permissive
Instructions:
Attention! The bootloader needs to be unlocked!
Attention! You'll need a vendor partition!
1. Install the Universal bootloader and your model specific modem. Download
2. Flash vendor creation tool. Download (unnecessary, if done already)
* On first flash the device will reboot, just reboot to recovery and reflash the zip.
3. Update your version of TWRP. Download
4. Perform a backup of your current ROM. (optional)
5. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
6. Install the ROM. Download
7. Install GApps. (optional) [Recommended -> Open GApps (arm64) (9.0)]
8. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev
Source Code: https://github.com/OrdenKrieger/android_kernel_zte_msm8996
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Testing
Created 2018-08-19
Last Updated 2019-07-28
Some features of LineageOS are missing, but they will be merged in future builds.
Some features may or may not work, sometimes also differently. Feel free to ask
any question.
UwU neat p finally
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Predatorhaze said:
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Click to expand...
Click to collapse
Read the instructions, they are there for a reason.
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
Los 15 is abandoned I assume?
And 16 besides nfc and volte is functional?
Thanks for contributing.
wow. It is all happening very fast.
Thanks
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important.You also say its optional to wipe system data cache if come from other rom,but in fact its REQUIRED to wipe system data if you come from other rom
Click to expand...
Click to collapse
GApps is always optional because some people want them and some don't. If you read carefully, on LOS 15.1 is the same.
I have heard Android Pie got GAPPS inbuild and i believe that because google dont want microg users.So its not true...
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Click to expand...
Click to collapse
Why should I mention other stuff if I already provide a working bootstack. Why would I give a download link for Gapps and add the the optionally tag, if they would be build in.
thnx @OrdenKrieger and all others involved :good:
Nice build - working smooth, no lag
DT2W ok
Used bitgapps as a starter
At last NO echo and incall volume adjustable
FP working
Hotspot OK
camera pics ok, recording crashes when saving - on both pics and video lag on movement
usb preferences work
afaik there is no way in settings to reverse softkeys so i used mine : https://androidfilehost.com/?fid=3700668719832237510 (be sure to be rooted and mount system/vendor)
Notifications work - on lockscreen and leds ok
EDIT : after testing a bit, definitely more heating and i mean a lot, more cpu load (f.e. as on the PPR1 img )..... could not stabilize temp on cpu 92C ! Only after applying powersave in EXKM...definitely something to look into (only Wifi on, no BT, no specific apps running....only the basic stuff to test your build )
EDIT2 : fast charging way more heat on battery - also battery drain too fast even with no cpu load
Will test further
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
2000impreza said:
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
Click to expand...
Click to collapse
yep, tried recording now and crashes when saving. Also lag on movement.
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Hellsbend said:
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Click to expand...
Click to collapse
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
ttkian said:
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
Click to expand...
Click to collapse
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Hellsbend said:
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Click to expand...
Click to collapse
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Edit
Of course, it's easier to flash because Post 1,2 and 3 are "included" now.
So it's quicker to flash.
Hellsbend said:
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Click to expand...
Click to collapse
Not quite. Mine was derived from Redmi Note 4. It looks the same for sure but devs have done some adjustments as to ECHO, dt2w working, notifications, ....
BUT my LOS16 build had no heating, nice CPU load and no battery drain and no heating when charging at all but had the annoying echo as we know it on other gsi builds and no dt2w, no notifications working on lockscreen, no led...
So there are definitely pros from this build and pros from mine.
Hope they can manage heating.
Also back on AEX as the heating (in my case) was too heavy. Dont want to ruin anything now
Android OS version: 9.0.0_r10
For devices: Oneplus 6
Authors build: sakindia123
Source code: https://github.com/nitrogen-project
Developers: sakindia123,xyyx, wight554
Thanks: darkobas,ezio84, beanstown106, maxwen, @SyCreed and etc.
Google Apps: Open GAPPS
Recovery: TWRP
{
"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"
}
Based on AOSP
xyyx (Max) - main developer
Make sure you have Hydrogen OS/OOS Stable/Beta installed on both A and B slots!Rom will not boot with Oreo firmware
Wipe Data(if coming from another rom)
Flash rom zip followed by Twrp installer zip
Reboot recovery
Flash gapps and Magisk 17+
Reboot - 1st boot takes around 5 minutes.
Enjoy
Download Link- HERE
Nitrogen Project
Device config
Known Bugs:
* ??
Telegram Discussion Group- https://t.me/joinchat/KCIhQw_ufo_vCBV93_tcoQ
XDA:DevDB Information
NitrogenOS, ROM for the OnePlus 6
Contributors
sakindia123, sakindia123, xyyx
ROM OS Version: 9.0.0 Pie
ROM Kernel: Linux 4.9.130
ROM Firmware Required: OOS Pie firmware
Version Information
Status: Beta
Created 2018-09-19
Last Updated 2018-09-19
NOS injected OP6! Fast and fuuurious! Great to see you guys here!
Are there screenshots, which additional features come with this rom?
Used to run this on my 6P time to relive the greatness
Need features n screenshots excited bout this rom...???
I am running OOS beta 3 and I am decrypted, will I be ok to flash? cheers
vtec303 said:
I am running OOS beta 3 and I am decrypted, will I be ok to flash? cheers
Click to expand...
Click to collapse
My guess is no, given the OP specifies OB1 and OB2.
One word of caution: I had quite the time going from OB3 back to a ROM requiring OB2 firmware. The first flash was fine, Havoc 2 set up great. But the second time I flashed, presumably the partition with OB3 on it, I softbricked the device. Could only get bootloader, and couldn't install twrp via fastboot. Had to revert to stock Oreo with the .bat procedure to get a working device.
Hopefully no else has that little adventure!
reaper000 said:
My guess is no, given the OP specifies OB1 and OB2.
One word of caution: I had quite the time going from OB3 back to a ROM requiring OB2 firmware. The first flash was fine, Havoc 2 set up great. But the second time I flashed, presumably the partition with OB3 on it, I softbricked the device. Could only get bootloader, and couldn't install twrp via fastboot. Had to revert to stock Oreo with the .bat procedure to get a working device.
Hopefully no else has that little adventure!
Click to expand...
Click to collapse
Yeah... I had to use Msmtools to fix my phone when I soft bricked. Couldn't get past Qualcomm crash dump mode. Took 3 hours to finally figure out how to use it.
rom running great... thanks! loved the oreo work as well.
vtec303 said:
I am running OOS beta 3 and I am decrypted, will I be ok to flash? cheers
Click to expand...
Click to collapse
how did you decrypt it?
didicola said:
how did you decrypt it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775
To OP: Rom is working flawlessly. One issue I faced is alert slider not working.
Edit:
After some time I found several minor issues
- Night light is not working
- Device theme is not working
- Colors shows nothing (just image, no list of selections)
- Also corners are without indent
Wow.. Atlast legendary rom came to op6 ?
Mr.RooT said:
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775
To OP: Rom is working flawlessly. One issue I faced is alert slider not working.
Edit:
After some time I found several minor issues
- Night light is not working
- Device theme is not working
- Colors shows nothing (just image, no list of selections)
- Also corners are without indent
Click to expand...
Click to collapse
So pretty much the same issues as other custom Roms?
mykenyc said:
So pretty much the same issues as other custom Roms?
Click to expand...
Click to collapse
Nah, alert slider works on most ROMs
Obamaloominaty said:
Nah, alert slider works on most ROMs
Click to expand...
Click to collapse
If I got it right it's just a matter of including it in the device tree. And as far as I've tested, the alert slider only works in LineageOS 16 since its tree is the only one to actually have the slider configs in it.
https://github.com/LineageOS/android_device_oneplus_sdm845-common/tree/lineage-16.0/KeyHandler
My guess is, also from my experience while trying to build AEX with that tree, that that folder has too many links to LineageOS and just flops when another rom is being built while that is in the device tree and calls for los stuff.
didicola said:
how did you decrypt it?
Click to expand...
Click to collapse
Read this thread...
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
didicola said:
how did you decrypt it?
Click to expand...
Click to collapse
followed the guide on the following thread but Keep in mind first time decrypting will wipe your internal drive, hope this helps.
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
---------- Post added at 06:48 PM ---------- Previous post was at 06:45 PM ----------
reaper000 said:
My guess is no, given the OP specifies OB1 and OB2.
One word of caution: I had quite the time going from OB3 back to a ROM requiring OB2 firmware. The first flash was fine, Havoc 2 set up great. But the second time I flashed, presumably the partition with OB3 on it, I softbricked the device. Could only get bootloader, and couldn't install twrp via fastboot. Had to revert to stock Oreo with the .bat procedure to get a working device.
Hopefully no else has that little adventure!
Click to expand...
Click to collapse
Had a few adventures like that myself..lol, but thanks for the advice I will keep that in mind, cheers.
i've two questions:
It's a mandatory decrypt storage for install this rom?
Works if i've oxygen beta 3 as base or i must have nitrogen?
Toni Moon said:
i've two questions:
It's a mandatory decrypt storage for install this rom?
Works if i've oxygen beta 3 as base or i must have nitrogen?
Click to expand...
Click to collapse
No mandatory decrypt.
Use OB1 or OB2 as base (not OB3).
So there are NO Fastboot OB1, OB2, or OB3 files that flash firmware to both slots. What is the correct process on flashing to BOTH slots?
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_polaris
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
NFC
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Mi MIX 2S variants.Builds are based off the Xiaomi's Android 9 firmware with proprietary blobs from MIUI 8.10.25 dev package.
Downloads:
Official download links
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Reboot to recovery (TWRP recovery for Mi MIX 2S)
Format /system, /data and /cache
Install LineageOS zip package
[*]Install [optional] the LineageOS su addon to get root (there are obviously other root methods, but this is the recommended one as it survives to OTA updates)
Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
Important notes:
* Required * firmware version must be based on MIUI P-based builds.
GApps can only be flashed on clean installs.
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
Credits & collaborations:
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Official wiki link
Wow, thanks. Yesterday i unlock my bootloader. Im now in AOSIP, but maybe later try this one.
I wonder what are the differences between yours and notsyncing's. Is this version more stable?
I tried aosip and lineageos 16, I prefer los 16, although both roms are equally fluid. note that aosip spends a little more battery, although I used it very little. no proximity sensor works, it can also be used daily. for the camera I use the last bgc, I miss the functions of the stock camera, it is the only thing that is made of less than miui.
I am on latest xioami.eu miui 10 beta ROM< and it has also problems with proximity sensor while using phone calls. So it means it is general problem on PIE android.
volte not workin?
Edlar said:
volte not workin?
Click to expand...
Click to collapse
Why?
Sent from my Mi MIX 2S using Tapatalk
slavke1976 said:
I am on latest xioami.eu miui 10 beta ROM< and it has also problems with proximity sensor while using phone calls. So it means it is general problem on PIE android.
Click to expand...
Click to collapse
No, in LOS it doesn't work at all as of now, in xiaomi.eu it may be unstable though on Pie Global miui it's getting better every release.
teddy74eva said:
No, in LOS it doesn't work at all as of now, in xiaomi.eu it may be unstable though on Pie Global miui it's getting better every release.
Click to expand...
Click to collapse
Thanks, and there is no possibility to instal MIUI kernel?
Thank you very much it works really fine, I have two questions
Is possible to install weather provider for clock?
Is possible to select different ringtone for each SIM?
Thanks
Sorry for my English...
is the second camera working?
Pixel Launcher doesn't work with this ROM, crashes at launch.
Magisk works but had to download and install manually Magisk Manager.
Boot is slower than Pixel Experience Pie but once it boots this ROM is faster overall.
This is great news. I was a long time Lineage user on my Mi5. Using Notsyncing build now on Mix2s because of working proximity sensor. Hope you get it working soon.
xarcoft said:
Pixel Launcher doesn't work with this ROM, crashes at launch.
Magisk works but had to download and install manually Magisk Manager.
Boot is slower than Pixel Experience Pie but once it boots this ROM is faster overall.
Click to expand...
Click to collapse
Confirms issue.
Also, Quick Charging seems broken... Getting only 500mA from stock wall charger and stock cable. Removed battery info from Recovery and got 1500mA, which is still far below normal; and it reverts to 500mA after reboot!
Also when I enter twrp the battery percentage shown there is usually 20% lower than in LOS. Bizzare.
Guess it could be issue with uncalibrated battery info. Will do a full cycle and see if things change.
For me Pixel Launcher from Playstore works just fine.And its normal that Magisk isnt pre installed
slavke1976 said:
Thanks, and there is no possibility to instal MIUI kernel?
Click to expand...
Click to collapse
The notes state no:
"No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case."
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Thanks Bruno for this! It's a rock solid ROM with excellent battery life and stability.
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
Fingdow said:
I wonder what are the differences between yours and notsyncing's. Is this version more stable?
Click to expand...
Click to collapse
notsyncing's version is a GSI/Treble build. This is a true polaris Lineage OS build made specifically for our device.
Can anyone compare this build and the one from notsyncing for me? Which one is better and why? ? Thanks in advance!
Great! Thanks! I'll move from GSI to this ASAP ? I just wish it's official so I can have OTA ?
eboye said:
Great! Thanks! I'll move from GSI to this ASAP I just wish it's official so I can have OTA
Click to expand...
Click to collapse
Will be official when time comes. But Xiaomi must release updated kernel source code so that we can have working proximity sensor.
bgcngm said:
Will be official when time comes. But Xiaomi must release updated kernel source code so that we can have working proximity sensor.
Click to expand...
Click to collapse
Any insight please on the charging issue?
Always falls back to slow charging after reboot.