[OFFICIAL] [NIGHTLIES] LineageOS 17.1 - Moto Z2 Force ROMs, Kernels, Recoveries, & Other

{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK29, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Newest firmware available for your variant
Based On: LineageOS
Version Information
Status: Stable
Created 2020-04-01
Last Updated 2020-04-15

Removed

Hey, I cant find the link of lineaeg 17.1? (Build 0401, yesterday i found!) Just a joke?

How can I unlock bootloader, install TWRP and LineageOS on my XT1789-04 (AT&T)?

It is a beautiful day!
Although there's no download links.

A Sad Story said:
Hey, I cant find the link of lineaeg 17.1? (Build 0401, yesterday i found!) Just a joke?
Click to expand...
Click to collapse
I downloaded and installed and everything is ok xD

bogante said:
I downloaded and installed and everything is ok xD
Click to expand...
Click to collapse
I cant find link. In download.lineageos no build of 17. Can u share it?

A Sad Story said:
I cant find link. In download.lineageos no build of 17. Can u share it?
Click to expand...
Click to collapse
Oh man, my upload speed is 50kb/s it will take forever

Hi devs!
Trying it out, seems pretty great! Very few bugs (not related to device probably, just LOS17).
Only device bug I've found is the camera focus: it doesn't seem to be focusing properly (or at all).
If you need any logs let me know - eager to help out.
EDIT: That's weird. Somehow after using the camera app and moving the thing around I got it to work again. Although it's sporadic at best - focusing isn't working reliably.
EDIT 2: Found what allows it to work sometimes: open and close the camera app briefly time and time again and it starts working.

Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
I jumped to 17.1 straight from stock, so not sure if it used to work in 16.0. I manually tried adding the ims apn for Jio, but no go...

Jelixis said:
Hi devs!
Trying it out, seems pretty great! Very few bugs (not related to device probably, just LOS17).
Only device bug I've found is the camera focus: it doesn't seem to be focusing properly (or at all).
If you need any logs let me know - eager to help out.
EDIT: That's weird. Somehow after using the camera app and moving the thing around I got it to work again. Although it's sporadic at best - focusing isn't working reliably.
EDIT 2: Found what allows it to work sometimes: open and close the camera app briefly time and time again and it starts working.
Click to expand...
Click to collapse
I'm facing same issue
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
ph03n!x said:
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
I jumped to 17.1 straight from stock, so not sure if it used to work in 16.0. I manually tried adding the ims apn for Jio, but no go...
Click to expand...
Click to collapse
Again facing the same issue here
Calls don't work with jio and I'm also facing camera focus issues

ph03n!x said:
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
Click to expand...
Click to collapse
Adding to my quote here, I got incoming calls coming in! Only outgoing is not, the rest of the stuff I've reported remains the same. Also, the phone is able to query the status of Call Waiting and Call Forwarding, so IMS is partially working. This is a pure LTE provider, does not have a fallback.
Shreeram02 said:
Again facing the same issue here
Calls don't work with jio and I'm also facing camera focus issues
Click to expand...
Click to collapse
I haven't tried the camera. But did you upgrade from LOS16, and did Jio work fine there?

ph03n!x said:
Adding to my quote here, I got incoming calls coming in! Only outgoing is not, the rest of the stuff I've reported remains the same. Also, the phone is able to query the status of Call Waiting and Call Forwarding, so IMS is partially working. This is a pure LTE provider, does not have a fallback.
I haven't tried the camera. But did you upgrade from LOS16, and did Jio work fine there?
Click to expand...
Click to collapse
Yea incoming calls are fine btw normal messages don't work either
Yes in los 16 everything is fine
in los 17(not 17.1)(the September 21 unofficial build) calling is working fine camera has same bugs there too tho
But if u want everything working los16 is the option

@erfanoabdi @ThE_MarD @npjohnson not sure if you had a chance to review this - while this installs in LOS17.1, does not really control efficiency mode.
However we can still see the battery % of the Incipio Mod:
https://forum.xda-developers.com/z2-play/themes/motomodbattery-service-lineageos-15-1-t3895041/
https://github.com/devilsclaw/MotoModBattery
I was looking for a way to find the mod's battery % and stumbled on this...

no signal
i dunno what im doing wrong but when i flash LoS 17.1 and reboot the rom start but i have no signal

bogante said:
i dunno what im doing wrong but when i flash LoS 17.1 and reboot the rom start but i have no signal
Click to expand...
Click to collapse
Do you see your phone's IMEI in settings > about phone? Baseband version when you tap the Android version (10) in the same screen?

Magisk manager
I update LOS 16 to this 17.1 and everything seems to work fine, no real bugs. I've installed latest 7.2 google camera port from Arnova and picture/video/selfies are great. Phone calls no problems and it's a my impression but finally loudspeaker volume is higher than previous lineage versions. Only a question, maybe someone can help me, I've lost magisk root access, is it possible to install it with a temporaney twrp as in LOS 16 or is there any other method please?
[SOLVED] Maybe could be useful for someone. I tried the pie method: I've installed Magisk zip booting (not flashing) TWRP 3.3.1-0 (the 3.3.1-1 doen't boot on my device). Everything is working fine, I don't have any glitch and now my devices is rooted too

Getting Glitches when Playing Games Like Asphalt 9 also Same Camera Focusing Problem here too.

I'm seeing glitches in the home screen/ launcher too. Happens at random, gets psychedelic when unlocking - there are wavy lines (stock LOS17.1 wallpaper) on the image that move. Screenshot does not capture this, but I can take a photo if it helps figure the problem.
Messing with Developer Options (disabling overlay, etc) has not effect. Let me know if I can help troubleshoot...

Heyyo @ph03n!x, my nash is broken btw so I can't help too much.
Anywho, for the graphical glitches? Please try to go into your LiveDisplay settings and disable any special profile you have selected. I think those profiles are actually broken on nash hence the graphical issues when waking up the device after it sleeps.
Can you do me a favor please? Test my latest build of TWRP for nash. version 3.3.1-1 that contains a bunch of fixes and so far no feedback...
https://forum.xda-developers.com/showpost.php?p=82170641&postcount=590

Related

[ROM][OFFICIAL][7.1.1][hydrogen] CyanogenMod 14.1

{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.0 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint (FPC1020 only)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
What's not working :
SELinux permissive
Camcorder can be a bit buggy at times.
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads:
Official nightly builds: https://download.cyanogenmod.org/?device=hydrogen
Google Apps: http://opengapps.org/
Device wiki:
Official wiki link
Device wiki:
CyanogenMod 14.1 nightlies changelog link
Credits:
@luca020400: "Me: HAALP!" He answered me
CyanogenMod Team
Xiaomi: For providing the Kernel Source Code
Donations:
You don't have to but if you want;
Donate via PayPal: http://paypal.me/ParthBhatia/
Donate via PayTM: http://i.imgur.com/54cQl9N.jpg (QR code)
XDA:DevDB Information
CyanogenMod 14 for hydrogen, ROM for the Xiaomi Mi Max
Contributors
TheStrix
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2016-11-20
Last Updated 2017-04-07
Source Code:
Device Tree(s):
android_device_xiaomi_msm8956-common: https://github.com/CyanogenMod/android_device_xiaomi_msm8956-common/tree/cm-14.1 (Gerrit)
android_device_xiaomi_hydrogen: https://github.com/CyanogenMod/android_device_xiaomi_hydrogen/tree/cm-14.1 (Gerrit)
Kernel Tree:
android_kernel_xiaomi_msm8956: https://github.com/CyanogenMod/android_kernel_xiaomi_msm8956/tree/cm-14.1
Note: It is a unified kernel for both Mi Max and Redmi Note 3.
Vendor:
proprietary_vendor_xiaomi: https://github.com/TheMuppets/proprietary_vendor_xiaomi/tree/cm-14.1 (For WIP: this)
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. (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.
Frequently Asked Questions:
Q)What phone variants are supported?
A)Mi Max with SD650 (hydrogen) is supported by me and NOT Mi Max SD652 (helium).
So helium users are not suggested to flash this.
Q)OH MY,.. CRASHES!?
A)This is a very early build of CyanogenMod running nougat and things are still WIP.
You may experience number of crashers here and there. These will be get fixed with time.
Q)Why did TheStrix made this UNOFFICIAL?
A)Because, we need our device to be bug free before enabling official CyanogenMod nightlies.
Q) Is VoLTE supported?
A) No. IMS seems to crash on N
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Yes, that would not show superuser icon in statusbar. This seems to break sensors on N, wait for update on this.
Q) How do I update GApps? (Also useful if you have GApps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + GApps. (Yes, without rebooting). Reboot.
Gr8 work Another 14.1 rom !!
Is this one compatible with Helium devices?
Heh, FAQ posted after my post answered my question, thank you
Oh nice!
I see you have a successful Redmi Note 3 ROM - im excited to see your skills on the Mi Max
Good Work
@TheStrix Great work sir.
Waiting for fully working, bug free CM13 from your side.
Will report back on this build.
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
mat9v said:
Gr8 work Another 14.1 rom !!
Is this one compatible with Helium devices?
Click to expand...
Click to collapse
Sir please read FAQ.
Sir please read FAQ.
Click to expand...
Click to collapse
Well, FAQ was posted 15 minutes after my post, so there
This I gotta try
TheStrix did incredible work on CM14 and a few related ROMs for the Redmi Note 3, I was using TheStrix's CM14 as a daily driver for a long time. Here's to a great CM14 for Hydrogen and Helium too.
Does this ROM work on CDMA carriers like China Telecom? I'm using the latest Hydrogen RR and it works fine on China Telecom using a UIM card and a few other overseas LTE/WCDMA/GSM carriers.
Thank you so much.
Welcome!
Great to see you starting development for Mi Max @TheStrix:good: One step closer to get CM official...
Now we will progress fast I am sure of it...
Don't know how aware are you of the custom roms development so far but allow me to point you to the most annoying and hard to fix bug we've had so far... the famous 3G data bug that some users in some countries with some service providers on some band frequencies suffer from. We fought this bug for a couple of months before I was able to find a workaround as I call it now. Then just recently with the great help of @The_Serial switching roms and providing radio logs(I don't have the bug) I managed to get to the root of the problem... See here for details...
I am eager to hear your respective opinion about this issue.
BTW I already have a test patch prepared for fix in Android telephony framework but can't build right now to test it... Let me know if you are interested...
Thank you for your work!
nijel8 said:
Great to see you starting development for Mi Max @TheStrix:good: One step closer to get CM official...
Now we will progress fast I am sure of it...
Don't know how aware are you of the custom roms development so far but allow me to point you to the most annoying and hard to fix bug we've had so far... the famous 3G data bug that some users in some countries with some service providers on some band frequencies suffer from. We fought this bug for a couple of months before I was able to find a workaround as I call it now. Then just recently with the great help of @The_Serial switching roms and providing radio logs(I don't have the bug) I managed to get to the root of the problem... See here for details...
I am eager to hear your respective opinion about this issue.
BTW I already have a test patch prepared for fix in Android telephony framework but can't build right now to test it... Let me know if you are interested...
Thank you for your work!
Click to expand...
Click to collapse
It's funny, but i don't have this problem on Nougat (this and karthik's). To be precise, the icon H dont showing, but 3G is works. On Marshmallow 3G still don't turns on.
Hunter Mossberg said:
It's funny, but i don't have this problem on Nougat (this and karthik's). To be precise, the icon H dont showing, but 3G is works. On Marshmallow 3G still don't turns on.
Click to expand...
Click to collapse
Now I am a little confused
I am pretty sure @karthick mostwanted already implemented the working radio blobs in his vendor tree but then you should get H icon. Nougat acts differently!?
Don't know about what @TheStrix is using...
If that issue is not present in Nougat at all that's great... Just needs some small changes to recognize DC-HSPA+ networks as HSPA+ and we'll get icon back...
Can you post radio log from this release clean installed? See my signature for how to take it.
Ow! Great news!
I am ready to test and promise to be a good tester
Few minutes later I will answer about 3G
nijel8 said:
Now I am a little confused
I am pretty sure @karthick mostwanted already implemented the working radio blobs in his vendor tree but then you should get H icon. Nougat acts differently!?
Don't know about what @TheStrix is using...
If that issue is not present in Nougat at all that's great... Just needs some small changes to recognize DC-HSPA+ networks as HSPA+ and we'll get icon back...
Can you post radio log from this release clean installed? See my signature for how to take it.
Click to expand...
Click to collapse
Of course.
Very good! Amazing! Best beta with a few problems like not working rotation and closing my poweramp...
Ho! 3G works. Without data have "H" letter and HSDPA, with data no letters and UMTS.
In information.
About bugs:
1 - even I use only one simcard in the second slot in notificatinon line and in settings them show me two simcards and number one I can not turn off. Reboots resolve it.
2 - in status bar I choose "circle" battery status style, but it shows standard icon.
3 - status bar menu in settings is not translated and many other settings are not translated, T9 is not translated
4 - flashlight does not work
5 - Settings -> System Profiles -> Settings ->Preferred network type = FC (logcat attached - settings.zip).
going on...
addon:
radio log on 3G is attached
Awesome first build apart from some bugs that will be fixed in time.
Fantastic work!
Will stay tuned!
Alex Tian8800 said:
Very good! Amazing! Best beta with a few problems like not working rotation and closing my poweramp...
Click to expand...
Click to collapse
Do not flash SuperSU or sensors will crash. (mentioned on faq as well)
The_Serial said:
Ho! 3G works. Without data have "H" letter and HSDPA, with data no letters and UMTS.
In information.
About bugs:
1 - even I use only one simcard in the second slot in notificatinon line and in settings them show me two simcards and number one I can not turn off. Reboots resolve it.
2 - in status bar I choose "circle" battery status style, but it shows standard icon.
3 - status bar menu in settings is not translated and many other settings are not translated, T9 is not translated
4 - flashlight does not work
5 - Settings -> System Profiles -> Settings ->Preferred network type = FC (logcat attached - settings.zip).
going on...
addon:
radio log on 3G is attached
Click to expand...
Click to collapse
OK, tbh, I still didn't get what 3G problem you guys are talking about. You are able to use 3G but don't see the icon in status bar? Something like that?
2,3 and 5: CyanogenMod bugs.
4: Camera is buggy on all devices with M blobs/libraries due to changes in camera driver in nougat.. Either we get N blobs or wait for some miracle guy to solve camera with M blobs fully. (scenario as of today)
TheStrix said:
You are able to use 3G but don't see the icon in status bar? Something like that?
Click to expand...
Click to collapse
yes, when have any data sending / receiving - no icon, when not have any data sending / receiving - icon "H".
But! Is it miracle? All other cm-based roms did not have an ability to work with "hspap" (for details contact nijel8, in post number 11 He started to explain and invite You to give full explanation of the 3G issue.

[OFFICIAL] [WEEKLIES] Lineage OS 15.1

{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18
first (always wanted to do that)
thanks for this, nice work everyone!!!
Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.
??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
fixed, can remove this.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
fixed, can remove post now.
Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?
npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?

[ROM][AOSP][UNOFFICIAL][9.0] Pixel Experience [TREBLE]

{
"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"
}
PixelExperience for Mi Max 2[OXYGEN]
What is this?
Pixel Experience is an AOSP/CAF based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Code:
[LIST]
[*]Wifi
[*]RIL
[*]Mobile data
[*]GPS
[*]Camera
[*]Flashlight
[*]Camcorder
[*]Bluetooth
[*]FMRadio
[*]Fingerprint Sensor
[*]Lights
[*]Sound / vibration
[*]Face unlock
[*]OTG
[/LIST]
Known issues
Code:
[LIST]
[*]Users facing in-call echo even now can follow [url=https://forum.xda-developers.com/showpost.php?p=79080851&postcount=67]this[/url]. And don't forget to thank for the post!
[*]In-call volume not adjustable
[*]Vendor Image mismatch can come up with some Magisk Module
[*]Screen Mirroring doesn't work
[/LIST]
-
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Google Drive
Donate to PEX Developer - jhenrique09
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
Flashing Instructions
Code:
[LIST=1]
[*]Download PixelExperience_oxygen-V.v-YYYYMMDD-HHMM-UNOFFICIAL.zip
[*]Formatting instructions:
-> [B]Existing Users:[/B] Wipe /system and /vendor partitions only
-> [B]Existing Users facing issues after installation:[/B] Wipe /system, /vendor, /cache and /dalvik or art partitions
-> [B]New User/Clean Installations:[/B] Wipe /data, /system, /vendor, /cache and /dalvik or art partitions
[*]Be sure to flash the latest Dev Firmware files (Please google them)
[*]Now flash the ROM.zip
[*]Optional Steps:
-> Flash Magisk 19.3 for root access
-> Flash the audio mods if needed (Link is provided below) - [B][COLOR="Red"]Instructions[/COLOR][/B]:
=> First flash the TWRP_Arise_Sound_System_Dolby_Atmos.zip package
=> Then flash Clear Soundmod (sangga).zip package, and you're good to go!
[*]Reboot
[/LIST]
Extras Download link:
Arise Mod(Note that the mod takes a few minutes to install): https://drive.google.com/open?id=1qV2b6PPKMgyil1OtGJ_JnM8us-p3cpVL
Magisk module to resolve "Magisk not installed" issue: Magiskd-Helper
Sources :
PixelExperience source code : https://github.com/PixelExperience/
Translation : https://translate.pixelexperience.org/
Telegram channel : https://t.me/PixelExperience​
Contributors :
@Hard_Rock83
Source Code: https://github.com/rakeshraimca/Kernel_xiaomi_oxygen
XDA:DevDB Information
[9.0] Pixel Experience - Mi Max 2 (Oxygen) - 12-Jan-2019, ROM for the Xiaomi Mi Max 2
Contributors
V_v3k, Hard_Rock83
Source Code: https://github.com/PixelExperience/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 3
Stable Release Date: 2019-03-10
Created 2019-01-12
Last Updated 2019-03-10
Release Changelogs:
Jan-2019
Initial release
Everything works
Magisk Mods may cause vendor image issues.
Feb-2019
Buggy release
Mar-2019
Apr-2019
Jun-2019 - Current Release
Res2
Nice to see this ROM getting support as its quite good
Do you have any plans on making it official?
Based on hardrock latest sources or older sources?
What is the latest firmware dev, where do i get it from? What do you mean when you say ,,flash latest firmware dev first"?
SMS
I love this rom !!!
But I really need some help ... Please...
SMS - not working. for me (orenge - romania).
To test the above problem and to clarify if there is a problem from my network operator or PixelExperience, I flashed the ugly ROM MIUI Dev (12/27/2018) and updated last night to last dev build (09-01-2019).
Unfortunately, SMSs work with MIUI ...
On MIUI: * # * # 4636 # * # * - works correctly, and displays my SMSC number at refresh. (I also managed to see the number from SMSC in Havoc build 4, after I moved the SIM into Slot 1 but the SMSs were still not going to the destination. In Slot 1 I usually have SDCARD...)
I just flashed the latest version of Pixel and I have the same problem: SMS does not leave. I can receive, but I can not send.
I've already tried other apps: Textra and SMS Messeging(AOSP)
I have attached a logcat of sms sending time.
Can someone help me ...
thank you
PS.
Before installing MIUI, I tested with Arrow build 13 (10-01-2019) and Havoc OS build 4, clean flash (format: vendor, date, system, cash, dalvik, all...) and the problem persisted ...
mfd10000 said:
I love this rom !!!
But I really need some help ... Please...
SMS - not working. for me (orenge - romania).
Click to expand...
Click to collapse
I don't know what the issue is but it sounds similar to what I experienced on one of the other pie ROMs.
MMS working fine prior to upgrade but couldn't get it work on Pie.
It's almost like the phone isnt reading the APN type correctly.
Google Messages app was reporting the service as not available on the network, which is obviously incorrect, as it works perfectly again after rolling back to the previous ROM.
mfd10000 said:
I love this rom !!!
But I really need some help ... Please...
SMS - not working. for me (orange - romania).
..
Click to expand...
Click to collapse
Ok..
Strange...
I've managed to solve SMS sending by changing to "Settings-> Network & Internet-> Mobile network-> Preffered network type" in anything that does not contain LTE ...
As soon as the network type contains LTE, SMS does not work ... Unfortunately, I think changing the setting means I can not use VoLTE anymore ...
cool subbed and adding to the index!
is it TREBLE enabled?
Facing mic problem on discord and pubg. Mic work for a MI and then off
Okay so have been using this rom for a lot of time.
Here are few bugs I am facing.
1. Kernel auditor, gain sets back to 12 even after enabling the script, after every reboot.
2. I used H/W mido module from magisk to disable HW keys, so after that I am receiving -"there is an internal problem with your device. contact your manufacturer for details" after every reboot.
3. There is safety net failing in magisk, so for making ctsprofile true I used, patcher and after that, safety net is passed but root is removed automatically and even after flasking magisk zip so manytimes root is not getting enabled.
(*In havoc it was working properly)
These are few issues which is not getting resolved, even after many attempts.
Overall best stable rom, first preference after HAVOC OS.
sinhapratik.11136 said:
Okay so have been using this rom for a lot of time.
Here are few bugs I am facing.
1. Kernel auditor, gain sets back to 12 even after enabling the script, after every reboot.
2. I used H/W mido module from magisk to disable HW keys, so after that I am receiving -"there is an internal problem with your device. contact your manufacturer for details" after every reboot.
3. There is safety net failing in magisk, so for making ctsprofile true I used, patcher and after that, safety net is passed but root is removed automatically and even after flasking magisk zip so manytimes root is not getting enabled.
(*In havoc it was working properly)
These are few issues which is not getting resolved, even after many attempts.
Overall best stable rom, first preference after HAVOC OS.
Click to expand...
Click to collapse
I think op is not interested or active for some time.
[email protected] said:
I think op is not interested or active for some time.
Click to expand...
Click to collapse
Maybe, not active. But who knows might be updating or working on making it official.
mfd10000 said:
Ok..
Strange...
I've managed to solve SMS sending by changing to "Settings-> Network & Internet-> Mobile network-> Preffered network type" in anything that does not contain LTE ...
As soon as the network type contains LTE, SMS does not work ... Unfortunately, I think changing the setting means I can not use VoLTE anymore ...
Click to expand...
Click to collapse
I had that problem too with Pixel Experience on Oreo as well as Pie. I'm in Canada with Virgin Mobile. You can still use LTE for data, try unchecking "use enhanced LTE for voice calls". You won't be able to use volte but at least you can still use LTE data.
daubh said:
I had that problem too with Pixel Experience on Oreo as well as Pie. I'm in Canada with Virgin Mobile. You can still use LTE for data, try unchecking "use enhanced LTE for voice calls". You won't be able to use volte but at least you can still use LTE data.
Click to expand...
Click to collapse
Hello!
Yes I know...
But I really want to use VoLTE.
Anyway, meanwhile, I falshed Havoc OS.
The problem, unfortunately, is the same.
Probably the Orange Romania network operator uses network switching to sending SMS and not sending them all over LTE ...
I can send SMS messages if VoLTE is active to another phone number that uses VoLTE.
Is this probably possible due to RCS ...?
Hey guys! I was busy with my end semester exams till yesterday so couldn't do much(probably none). So I've gone through most of your issues.
For people facing network issues with SMS/MMS, you didn't have this issue with MIUI right?
And it has Treble enabled(thanks to Hard_Rock83 bro)!
Just to be on a safer side, be on the latest dev firmware. You can get it from the update file manually for the time being.
As for the internal error issue, I'll need some time identifying it, for now to pass CTS profile, please use the "MagiskHide Props Config" module. And avoid using any module that affects the system.
Also please be aware that, I'm currently not planning to make it official.
Next update will be available soon (Using latest codes from Hard_Rock83)
V_v3k said:
For people facing network issues with SMS/MMS, you didn't have this issue with MIUI right?
Click to expand...
Click to collapse
I forgot to post an update on my MMS issue.
Don't waste any time looking into it as it turned out to be a service provider issue. I just hadn't noticed it until Pie.
Well done on completing your exams and looking forward to trying out the next build.
V_v3k said:
Hey guys! I was busy with my end semester exams till yesterday so couldn't do much(probably none). So I've gone through most of your issues.
For people facing network issues with SMS/MMS, you didn't have this issue with MIUI right?
And it has Treble enabled(thanks to Hard_Rock83 bro)!
Just to be on a safer side, be on the latest dev firmware. You can get it from the update file manually for the time being.
As for the internal error issue, I'll need some time identifying it, for now to pass CTS profile, please use the "MagiskHide Props Config" module. And avoid using any module that affects the system.
Also please be aware that, I'm currently not planning to make it official.
Next update will be available soon (Using latest codes from Hard_Rock83)
Click to expand...
Click to collapse
Good to know that you are back

[ROM][9.0.0_r52][A2017X][UNOFFICIAL] ArrowOS 9.x

YAPR [YET ANOTHER PIE ROM]​
{
"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
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Click here (read more on our website)
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM:
ArrowOS 9.x
Arrow-v9.0-axon7-UNOFFICIAL-20191117
LATEST Arrow-v9.0-axon7-UNOFFICIAL-20200126
Gapps: Click Here for GApps
Note : Pico, Nano or Micro Gapps are recommended.
ROM Source: https://github.com/ArrowOS
--------------------------------------------------------------------------------------------------------------------------------------
Installation :
1. wipe system, vendor, data, cache
2. install ROM
3. GApps, Magisk
4. reboot
Contributors
@raystef66
Credits to
ArrowOS Team
LOS Team
KERNEL SOURCE: https://github.com/OrdenKrieger/andr...el_zte_msm8996 thnx @OrdenKrieger
ROM OS Version: 9.x PIE
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Unlocked Bootloader, Latest TWRP Recovery
Based On: LineageOS device, vendor, kernel
Version Information : 9.x
Status: Pure & Stable...afaik
Sec. Patches : 2020.01.05
Created : 2019.10.12
Last Updated : 2020.01.26
Thanks Raystef66, I'm using this ROM as of tonight. I have successfully upgraded from AOSP 6.5 (May) on my A2017 (chinese).
Much smoother and quicker, although that is expected with a new ROM install after so long! I hope to give you more feedback.
Dungeon Maker had issues installing, which i think may be due to CTSmismatch in magisk (v20). I still have not been successful in passing it.
Do you have a kernel recommended? Or which kernel do you have with this ROM?
Thank you for all of your hard work in keeping the Axon7 ROMs active.
darth_antz said:
Thanks Raystef66, I'm using this ROM as of tonight. I have successfully upgraded from AOSP 6.5 (May) on my A2017 (chinese).
Much smoother and quicker, although that is expected with a new ROM install after so long! I hope to give you more feedback.
Dungeon Maker had issues installing, which i think may be due to CTSmismatch in magisk (v20). I still have not been successful in passing it.
Do you have a kernel recommended? Or which kernel do you have with this ROM?
Thank you for all of your hard work in keeping the Axon7 ROMs active.
Click to expand...
Click to collapse
Install MagiskHidePropsConfig and Busybox and run "props" via terminal and choose f.e. the axon7 oreo FP. You'll pass cts. I run magisk 20.0 and all ok.
I suggest installing the RC1.2 kernel which you can find HERE.
In my next build I was planning to take that one within the ROM. But you can install it without probs tho
Btw, picture below is on new crDroid but MHPC should give u the same results on ArrowOS
Thanks Ray, I appreciate your reply and knowledge of this.
The app updated and worked without needing the ctsmismatch pass, so i'll just wait for your update.
In the 3 days since I've been using this ROM, I can appreciate the following coming from AEX 6.5. A freshly installed ROM does have some of these benefits so I'm probably biased.
1. Arrow has a faster boot into the rom. the loading screen is awesome and the loading effect is great.
2. Arrow uses half as much ram, 1.7gig compared to 3.2gig. This is probably a fresh install thing though, as i have a lot less apps now.
3. quicker and cleaner.
Thanks, the only thing i hope you have in future builds is the cts, and the option for when you reset the phone, there are the extra options to boot into recovery.
*found this option under 'buttons' in the android menu, apologies.
Ive been using this for a month now and its been awesome.
The only bug or issue I've had is the dictionary and auto-correct. Auto-correct does not work at all, and it doesnt recognise mis-spelt words. Android keyboard seems to have limited option.
Thank you for developing this ROM.
NEW ARROW BUILD 2019.11.17
Arrow-v9.0-axon7-UNOFFICIAL-20191117
changelog :
* november sec. patches
* added RC1.2 baddar kernel
* added proper thermal fix
Hi raystef66,
Thank you so much for your great efforts and sharing with this amazing ROM.
The only issue for me is so far - Gesture Typing of AOSP Keyboard is not working.
I have checked its setting to make sure the gesture typing function turned on, but still not working.
Is it experiencing only me? how about other people?
I'm sure that this is an ignorable minor bug for me, otherwise this ROM is finely matured exquisite PIE ROM.
In the next update, however, would you mind adding the advanced settings option?
Thanks again.
BUILD 2019.11.17 First Impressions
Pretty happy with this ROM coming from the most recent (now deprecated) Lineage 15.1 Official Nightly and really loving Arrow.
The only thing I'm missing is the ability to slide finger on status bar to adjust brightness.
I noticed the battery life seems noticeably better. I was hours away from replacing my Axon due to the battery just being horrible, even after being recently replaced. Everything seems buttery smooth besides the Gcam app I'm using. It works, but very sluggish.
Please do recommend your favorite camera app for this ROM.
I'm passing SafetyNet after installing Pixel Android 9 Props.
GPS took over a minute to get a lock the first time around, but now works within 15 seconds as expected.
USB tethering has been temperamental. I disabled hardware acceleration via Developer Settings and it seems to be working better.
I can confirm that swipe texting on AOSP keyboard does not work, however works fine with Gboard.
Hardware keys work as expected however even with the home button Long Press Action set to activate Google Assistant it does nothing. It seems that the Google Assistant action does not work with any of the button settings including the on screen navbar.
I haven't been able to get USB-OTG to work on any ROMs since ditching stock. Maybe someone knows a fix. It doesn't work in TWRP either, so maybe it's my hardware.
Besides a few minor quirks, I am hugely grateful for this ROM providing Pie and rekindling my love for this aging Axon. Thank you!
Swipe typing on the aosp keyboard just means it's missing the libs. Seen it before. Last I checked open gapps aroma let you restore the libs.. But using a different keyboard is a better idea.
Thank you for the update and fixes! Still using this since September.
As above, the keyboard (and in my case, autocorrect doesnt work as well as other roms) is the only thing thats not going so great.
Apart from that, its flawless. Thank you again!
Hi,
Thank you for this very good ROM!
Tested several days, I only noticed a bug in the Google camera with the GAPPS stock. When the application is updated, it stops working.
I also wonder if wifi calls work. Maybe I didn't find the right option to activate them.
(and the GPS sometimes remains blocked at a location and does not update itself).
Everything else is perfect!
Wi-Fi access point and usb modem do not work ....
Wi-Fi access point and usb modem do not work .... sometimes attempts to turn on those options cause a system lock and forced hard reset
PS I turned off hardware acceleration as someone wrote here - USB tethering works ... the problem with the wireless hot spot remains ...
PS2 I don’t know why, but during a 10-kilometer trip, GPS is lost several times, and somewhere near the final destination of the trip, the phone suddenly starts to show the right way this is already becoming a tradition.....
I my location on this ROM i have a problem with conersation. Before i used AOSP 5.7 based on Oreo and in my room i could talk by phone. Acctually i must go to kitchen because only there i can normally talk.
It's look like worse signal or not all bands compatible. My Axon have B20 (it isn't china version). Sometimes i have problem with internet - connecting by LTE isn't possible. When i was in London i couldn't use internet. Phone found transmitter, about 3/5 signal strange but any page or facebook lite no load.
NEW ARROW BUILD 2020.01.26
Arrow-v9.0-axon7-UNOFFICIAL-2020.01.26
changelog :
* Merge branch 'android-9.0.0_r52'
* jan 2020 sec. patches
Thank you for not abandoning our dear Axon 7. Please continue to develop ROMs for him!
Thank you very much for the rom, my Axon 7 is now back to life.
Dark mode isn't forced in other apps, like google photos.
larsky said:
BUILD 2019.11.17 First Impressions
Pretty happy with this ROM coming from the most recent (now deprecated) Lineage 15.1 Official Nightly and really loving Arrow.
The only thing I'm missing is the ability to slide finger on status bar to adjust brightness.
I noticed the battery life seems noticeably better. I was hours away from replacing my Axon due to the battery just being horrible, even after being recently replaced. Everything seems buttery smooth besides the Gcam app I'm using. It works, but very sluggish.
Please do recommend your favorite camera app for this ROM.
I'm passing SafetyNet after installing Pixel Android 9 Props.
GPS took over a minute to get a lock the first time around, but now works within 15 seconds as expected.
USB tethering has been temperamental. I disabled hardware acceleration via Developer Settings and it seems to be working better.
I can confirm that swipe texting on AOSP keyboard does not work, however works fine with Gboard.
Hardware keys work as expected however even with the home button Long Press Action set to activate Google Assistant it does nothing. It seems that the Google Assistant action does not work with any of the button settings including the on screen navbar.
I haven't been able to get USB-OTG to work on any ROMs since ditching stock. Maybe someone knows a fix. It doesn't work in TWRP either, so maybe it's my hardware.
Besides a few minor quirks, I am hugely grateful for this ROM providing Pie and rekindling my love for this aging Axon. Thank you!
Click to expand...
Click to collapse
##############################
1- To enable assistant you have to choose the google app for the default assistant in the default apps settings.
2- I have trsted nearly 80% of all gcam apks, and the best one so far and the newest is Urnyx05 latets version, you can find it here
https://1-dontsharethislink.celsoazevedo.com/file/filesc/GCam_7.3.018_Urnyx05-v2.2-fix.apk
3- Aosp keyboard is a just terrible, just get Gboard.
4- Clean flashing the rom will solve GPS and USB problems, always clean flash.

[OFFICIAL] LineageOS 19.1 for the Razer Phone 2

{
"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"
}
Razer Phone 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Razer Phone 2.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
aura - Official builds​
aura - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Known bugs (won't fix):
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_razer_sdm845
Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?
runuts said:
Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?
Click to expand...
Click to collapse
it works on PE?
npjohnson said:
it works on PE?
Click to expand...
Click to collapse
No. This is why I switched from PE to Lineage 19.1 where it also didn't work. Flashed back to 18.1 and it is working.
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
Hint: I am working on m8 right now
npjohnson said:
Hint: I am working on m8 right now
Click to expand...
Click to collapse
That is good to know. I installed an unofficial LineageOS 18 ROM recently, but haven't played with it since then.
Just updated to LineagOS for MicroG 19.1 so far so good.
unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
If you read the install instructions this is normal behavior
npjohnson said:
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Click to expand...
Click to collapse
Not really a bug as its an app in the stock ROM. The current solution is to root and install Logo+ and it works.
Should also list Dolby Atmos missing too
omega552003 said:
If you read the install instructions this is normal behavior
Click to expand...
Click to collapse
I did. It was not unexpected.
I followed the instructions to the letter upgrading from 18.1 and mine is stuck in boot. It's been showing the little logo animation for almost 10 minutes now. Mild panic has set in.
edit: Fixed it!
Had the wrong gapps package. Downloaded the correct one, (MindTheGapps12.1 arm64 for those lost souls still out there).
Fixing procedure if stuck on LOS logo loop:
1. Make sure your devices is still plugged into your computer and hold down power button until you see the fastboot landing page where it gives you the option to pause boot. PAUSE BOOT.
2. hold down power button again to turn phone off. You'll know it's off when you get the white and black charge animation
3. hold power and volume down until you get to the recovery page.
4. Choose recovery mode, recovery from adb, and then run adb sideload /path/to/zip to install the correct gapps package.
Hope no one else does the same dummy move I did but if they do I hope this helps.
P.S. I have no idea yet what my screw up did long term btw. Device is still finishing the update. I did have to reinstall messages and gmail but for all I know that would have needed to happen anyway.
Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?
edison said:
Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?
Click to expand...
Click to collapse
Yes, it should. I remember seeing some folks have similar issues with 18.1 but I don't recall what the issue was. Maybe check out the 18.1 forums and see if there's any applicable advice there
Coming from Pixel Experience and I am getting audio crackling/stuttering only when using game streaming apps such as Moonlight and PSPlay and the volume is less than 50%. I had the same issue on Pixel Experience but the dev had fixed it using this commit. Any chance the fix can apply here too?
With the most recent build I am seeing Location pings even though Location is off and no apps are granted Location permissions. It was difficult, but I did get a screen capture of the event. You can see the location pip in the status bar. What is going on?
How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager
Cylow333 said:
How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager
Click to expand...
Click to collapse
I was looking for the same information
This is working very well for me keep up the good work. One thing I have found however is that while on a call rtt or tty as it is known seems to be on. I have made sure it is off in accessibility settings so I am sure it's just a bug but wanted to make aware of it. Does anyone else have this issue? I am on verizon. Not sure if that matters.
marcxpr said:
I was looking for the same information
Click to expand...
Click to collapse
I was able to root by adb sideload and running adb sideload followed by the magisk.zip file

Categories

Resources