[OFFICIAL] LineageOS 15.1 for ZTE Axon 7

[Predatorhaze]

los15 with hellsgate x13 works good

 

[Stagnation2]

Last few updates have left me with a phone that's getting really hot while doing just about anything (CPU temp is getting over 70C just browsing Reddit, Youtube gets to over 88C before I shut it off). Phone also can't outcharge the battery drain. Anyone else experiencing this?

 

[jelly28]

Thanks for the reply. I ran into a glitch where I can access adb but not fastboot. While I expect this is an issue for another forum if any readers are familiar with fastboot hassles using Ubuntu 18.04 I'd appreciate the advice.

Once I figure this out I shall return.

Dave

I can't find the solution. My dilemma, again, is with bootloader. Adb works in that adb devices generates a reply although I get no reply from fastboot devices.

My OS is Ubuntu and I don't have a windows machine.

Thanks in advance,

Dave

 

[koftheworld]

I'm confident it has something to do with the updated gps blobs lineage switched to a few weeks ago. Everyone was working fine till about the last release or so when they merged that change. I just wish I could help trouble shoot.

I know going back to stock would work, but love lineage.

I love lineage as well, but I've been having volte issues for awhile and most recently these GPS problems have directly affected me. I was in the middle of nowhere the other day with no access to maps. It was perfect. Entirely my fault for not fixing gps before then but it wasn't a good feeling returning to a pre gps reality.

Anyway I'm on b20 and not hating it.

 

[Axon7User]

I just installed the Build from 29.11 on my axon 7. It runs just fine but I can not download any apps from the appstore. It says something like download pending...
What can I do, to resolve that?

 

[williamthardy]

I just installed the Build from 29.11 on my axon 7. It runs just fine but I can not download any apps from the appstore. It says something like download pending...
What can I do, to resolve that?

Which Open-GApps version?

 

[fuzzmania]

I have a stupid question, this, and any custom ROM will always fail safetynet since bootloader must remain unlocked to boot yes?

 

[_phk_]

I have a stupid question, this, and any custom ROM will always fail safetynet since bootloader must remain unlocked to boot yes?

You have to install module safety patch via magisk manager.

 

[fuzzmania]

You have to install module safety patch via magisk manager.

Thanks, that helps except my work profile got removed because now I'm rooted, wooo
even hid root from Hub and Workprofilesetup, however when it adds the other applications they detect root before I can block them and remove the whole profile. LOL

 

[haerwu]

@fuzzmania search thread - instructions were provided in past.

 

[seliqui]

outgoing phone call issue

Anyone else experience the Outgoing phone call issue?

If someone calls me, everything works fine.
But if I want to call someone, neither me or the other side can hear anything when the connection is established.
Also I can't hear the sound you hear that indicates that the other phone is ringing.

- It's NOT the issue where switching to Speaker and back solves the problem (had that too on a early LOS15 Version some time ago, and there the other side could always hear me).
- Installed LOS Version is the currently latest nightly (lineage-15.1-20181208-nightly-axon7-signed.zip) for the A2017G
- Also tried re-flashing the Modem via TWRP. No difference.
- Tried both the LOS Dialer and the Google Dialer App

Can anyone suggest something I could try?
(Quick search via google and on XDA didn't returned a solution that worked - although it could be that I missed something.)

Update #1:
Could be a issue with "Voice over Wifi / Voice over LTE". If I disable WIFI and Mobile Data, outgoing phonecalls work.
But if either Wifi or Mobile Data / LTE is enabled, the Problem persists.

Update #2:
Found a solution!
Settings > Network & Internet > Mobile network > Expand "Advanced" > DISABLE "Enhanced 4G LTE Mode"
(or in German: Einstellungen > Netzwerk & Internet > Mobilfunknetz > Erweitert > "Erweiterter 4G LTE-Modus" ausschalten)

 

[abel408]

I figured out what I did wrong. I need to keep holding the volup button until I enter twrp again.

Anyway, at step 11, I tap on Expand OS and nothing happens. Then I tried to boot to system. At the very first google set up screen I got the google.media has stop and then google services framework keep stopping keep persisting and I cant proceed with the set up.
Then boot into twrp I installed 8.1 gapps micro and tried to boot to system but same thing happen with google services framework keeps stopping.
Please advise.

Edit: keeping everything else from Oki, I tried installing just the latest Los 15.1 rom and gapps and same errors
edit2: I follow all installation steps from OP and still got the google.process.media and google services framework errors at initial set up. can't proceed.
I also tried installing just the rom without gapps but same error
Also tried ext4 and no luck

I'm also having this issue. Keep getting random apps that say "keeps stopping". If I ignore them, the phone doesn't get past the looking for updates screen. Perhaps a modem issue? I did flash the correct modem though so I have no idea what's causing this. I'm coming from stock everything. Just unlocked the bootloader using miflash and used party to create vendor partition.

 

[Mart Son]

I'm also having this issue. Keep getting random apps that say "keeps stopping". If I ignore them, the phone doesn't get past the looking for updates screen. Perhaps a modem issue? I did flash the correct modem though so I have no idea what's causing this. I'm coming from stock everything. Just unlocked the bootloader using miflash and used party to create vendor partition.

Did you wipe the data partition when coming from another rom?

 

[fanta110]

Anybody have problems to mount /data in twrp? As I can't mount /data partition after first booting. Formatted /data again and again after booting can't mount /data in twrp. Came yesterday from stock 8.0 A2017G

 

[okmikel]

Anybody have problems to mount /data in twrp? As I can't mount /data partition after first booting. Formatted /data again and again after booting can't mount /data in twrp. Came yesterday from stock 8.0 A2017G

You have to remove encryption if you want to be able to mount data in TWRP. Or use nfounds TWRP with vendor support.

 

[_phk_]

this will fix low persistence mode on oreo

diff --git a/drivers/video/msm/mdss/mdss_fb.c b/drivers/video/msm/mdss/mdss_fb.c
index e4dee9359a2c..30cc6fe3e64d 100644
--- a/drivers/video/msm/mdss/mdss_fb.c
+++ b/drivers/video/msm/mdss/mdss_fb.c
@@ -835,7 +835,7 @@ static ssize_t mdss_fb_change_persist_mode(struct device *dev,
        struct mdss_panel_info *pinfo = NULL;
        struct mdss_panel_data *pdata;
        int ret = 0;
-       u32 persist_mode;
+       unsigned int persist_mode;
 
        if (!mfd || !mfd->panel_info) {
                pr_err("%s: Panel info is NULL!\n", __func__);
@@ -858,8 +858,10 @@ static ssize_t mdss_fb_change_persist_mode(struct device *dev,
        mutex_lock(&mfd->bl_lock);
 
        pdata = dev_get_platdata(&mfd->pdev->dev);
-       if ((pdata) && (pdata->apply_display_setting))
+       /*if ((pdata) && (pdata->apply_display_setting))
                ret = pdata->apply_display_setting(pdata, persist_mode);
+       else pr_err("could not apply");*/
+       pdata->vr_mode_enable(pdata, persist_mode);
 
        mutex_unlock(&mfd->bl_lock);

Thx @Unjustified Dev for backporting the function from nougat. It will now be automatically triggered (at least in the LOS unoffical builds).
The vr_mode_enable function will be called by /sys/class/graphics/fb0/msm_fb_persist_mode file handle.

 

[abel408]

Did you wipe the data partition when coming from another rom?

Yes, I formatted data. Came from an encrypted device though. Does that matter? I believe the format wiped the encryption.

 

[lichtblitz]

Take oki's twrp. The one w/o b12 encryption support. Then format again.

 

[[armitage]]

@Unjustified Dev
I know that you are probably busy with life and I get that your private life is much more important than android and roms and of course that's the way it should be.
I'm not trying to annoy you and I hope I don't and I do get that this is a hobby done in your freetime and if you don't have any time for it then of course I completely understand. I do get all that and I really hope that I don't and didn't sound demanding in any way.
Nevertheless I just have to ask if there is any chance that you could take a look at the gps problem that some of us have...
If you can't or simply won't, which of course is fine as well, then so be it and of course I'm still grateful for all that you've done so far.
In any case, all the best man and thanks anyway.

 

[Unjustified Dev]

this will fix low persistence mode on oreo

diff --git a/drivers/video/msm/mdss/mdss_fb.c b/drivers/video/msm/mdss/mdss_fb.c
index e4dee9359a2c..30cc6fe3e64d 100644
--- a/drivers/video/msm/mdss/mdss_fb.c
+++ b/drivers/video/msm/mdss/mdss_fb.c
@@ -835,7 +835,7 @@ static ssize_t mdss_fb_change_persist_mode(struct device *dev,
        struct mdss_panel_info *pinfo = NULL;
        struct mdss_panel_data *pdata;
        int ret = 0;
-       u32 persist_mode;
+       unsigned int persist_mode;
 
        if (!mfd || !mfd->panel_info) {
                pr_err("%s: Panel info is NULL!\n", __func__);
@@ -858,8 +858,10 @@ static ssize_t mdss_fb_change_persist_mode(struct device *dev,
        mutex_lock(&mfd->bl_lock);
 
        pdata = dev_get_platdata(&mfd->pdev->dev);
-       if ((pdata) && (pdata->apply_display_setting))
+       /*if ((pdata) && (pdata->apply_display_setting))
                ret = pdata->apply_display_setting(pdata, persist_mode);
+       else pr_err("could not apply");*/
+       pdata->vr_mode_enable(pdata, persist_mode);
 
        mutex_unlock(&mfd->bl_lock);

Thx @Unjustified Dev for backporting the function from nougat. It will now be automatically triggered (at least in the LOS unoffical builds).
The vr_mode_enable function will be called by /sys/class/graphics/fb0/msm_fb_persist_mode file handle.

Thanks I'm backporting the updated version from A2017G Oreo and I will apply the persist_mode dependency to enable it each time the light HAL writes to msm_fb_persist_mode

edit: This appears to already be done in A2017G Kernel

bool vr_mode_judge = 0;
static ssize_t mdss_fb_change_persist_mode(struct device *dev,
		struct device_attribute *attr, const char *buf, size_t len)
{
	struct fb_info *fbi = dev_get_drvdata(dev);
	struct msm_fb_data_type *mfd = (struct msm_fb_data_type *)fbi->par;
	struct mdss_panel_info *pinfo = NULL;
	struct mdss_panel_data *pdata;
	int ret = 0;
	u32 persist_mode;

	if (!mfd || !mfd->panel_info) {
		pr_err("%s: Panel info is NULL!\n", __func__);
	return len;
	}

	pinfo = mfd->panel_info;

	if (kstrtouint(buf, 0, &persist_mode)) {
		pr_err("kstrtouint buf error!\n");
		return len;
	}

	mutex_lock(&mfd->mdss_sysfs_lock);
	if (mdss_panel_is_power_off(mfd->panel_power_state)) {
		pinfo->persist_mode = persist_mode;
		goto end;
	}

	mutex_lock(&mfd->bl_lock);

	pdata = dev_get_platdata(&mfd->pdev->dev);
	if ((pdata) && (pdata->vr_mode_enable))
		pdata->vr_mode_enable(pdata, persist_mode);

	mutex_unlock(&mfd->bl_lock);

	if (!ret) {
		pr_debug("%s: Persist mode %d\n", __func__, persist_mode);
		pinfo->persist_mode = persist_mode;
	}
	vr_mode_judge = pinfo->persist_mode ;
end:
	mutex_unlock(&mfd->mdss_sysfs_lock);
	return len;
}