[ROM][9.0.0_r46][A2017X][OFFICIAL] crDROID v5.12 [FINAL]

[Whoooo?]

Working fine on latest 06.17 build - checked on clean flash.


Checked myself on a clean 6.17 build and MAC stays fixed after reboot or by enable/disabling it.

Hi there and thanks a lot for the quick reply!


That's weird, I checked and I'm definitely on the latest 6.17 build as well (installed as per posts above, however formatting data didn't format data/media).


A simple Wifi on/off changes the MAC.
It looks like the SELinux bug they reported in the lineage thread
https://forum.xda-developers.com/ax...zte-axon-7-t3800214/post77915524#post77915524

But that should be fixed - unless there was some leftover from my previous Nougat install?

Does anyone know if adding a mac in /persist/wifimac2.dat really fixes the issue?
EDIT:
Doesn't seem to read either wifimac.dat or wifimac2.dat - I changed both to the original (device) Mac and it is still gnerating random Macs...
(should I use one of the random ones instead of the original?)
Interestingly wifimac.dat and wifimac2.dat used a slightly different format:
wifimac.dat was 'wifiaddr:0xAA 0x...'
wifimac2.dat was 'wifiaddr: 0xaa 0x...'

Thanks again!

 

[raystef66]

NEW CRDROID BUILD 2020.07.22

Download on SourceForge crDroidAndroid-9.0-20200722-axon7-v5.12

Since my work on MI9 and Axon7 Q, except possible releases on sec. updates, no more request-builds will be made for axon7 crDroid

changelog :

====================
22-07-2020
====================

- Updated Sec.Patches July 2020

NOTE : still for some reason on a clean flash homescreen apps can being modified. Though Dirty flash will leave your homescreen apps untouched

 

[waltibaba]

Black screen systemUI crash loop

Same thing happens when you set the device to dark mode in either the crdroid settings or by searching for theme from the settings menu. Only solution is a factory reset. Seems like systemUI is crash looping.

I finally managed to test every one of my new rom changes, and found the cause.
If you enable Battery Bar, SystemUI goes into a crash loop, on any version of this and RR that I have tried!
@raystef66 is there anything I can do for you to solve this issue? Is it even within your scope or is this a crDroid issue?

 

[raystef66]

I finally managed to test every one of my new rom changes, and found the cause.
If you enable Battery Bar, SystemUI goes into a crash loop, on any version of this and RR that I have tried!
@raystef66 is there anything I can do for you to solve this issue? Is it even within your scope or is this a crDroid issue?

I've tested and no issues on my device. Even tested now on MI9 10.0 crDroid and working flawless.

 

[Archebalt]

Good day, have problem with gpay. In security - trust it says that "platform - actual; Manufactor (sorry, translating from rus ver.) - old"
There was comments, that gpay works fine on this one, so i'm thinking that I've done something wrong.

 

[sashamsuper]

Sound and DAC. 48Khz.

When using Poweramp, listening on hires output is impossible, because dvc have to be turned off due to low Volume when dvc is on. In other cases, the frequency is set at 48 kHz. Accordingly, in terms of using Dac for the firmware, there are big questions. Maybe someone has a different experience?

 

[apoha]

When using Poweramp, listening on hires output is impossible, because dvc have to be turned off due to low Volume when dvc is on. In other cases, the frequency is set at 48 kHz. Accordingly, in terms of using Dac for the firmware, there are big questions. Maybe someone has a different experience?

You cannot get Hi-Res output from any onf Android 9.0 &10.0 Roms. Even poweramp is reporting Hi-Res when DVC is ON, it is not real. The audio output is capped to 48Khz by audiopath in the ROM. I retested this rom 3 days ago but got same result.

This is the reason I cannot upgrade from moded Stock Oreo.

 

[sashamsuper]

answer

You cannot get Hi-Res output from any onf Android 9.0 &10.0 Roms. Even poweramp is reporting Hi-Res when DVC is ON, it is not real. The audio output is capped to 48Khz by audiopath in the ROM. I retested this rom 3 days ago but got same result.

This is the reason I cannot upgrade from moded Stock Oreo.

I have big doubts about the destriction in the latest versions of Android(Google High-Resolution Audio, no link for junior) . I rather think about the lack of support from ZTE and the unwillingness to present this information in the firmware description.

 

[apoha]

I have big doubts about the destriction in the latest versions of Android(Google High-Resolution Audio, no link for junior) . I rather think about the lack of support from ZTE and the unwillingness to present this information in the firmware description.

The problem is for "Axon 7" custom roms; other official or custom Android 9+ roms for other phones have proper Hi-res output, such as my OnePlus 5 has Android 10 and Hi-Res working as intended.
I think the problem is caused by audio drivers/paths on vendor partition.

 

[sashamsuper]

The problem is for "Axon 7" custom roms; other official or custom Android 9+ roms for other phones have proper Hi-res output, such as my OnePlus 5 has Android 10 and Hi-Res working as intended.
I think the problem is caused by audio drivers/paths on vendor partition.

As a result, we can only assume. I think the current problem is raising the audio volume when the DVC is on. I doubt Poweramp is reporting the wrong 192 kHz frequency. There are audio tag errors in CatLog but it is not clear how to interpret them.

 

[apoha]

As a result, we can only assume. I think the current problem is raising the audio volume when the DVC is on. I doubt Poweramp is reporting the wrong 192 kHz frequency. There are audio tag errors in CatLog but it is not clear how to interpret them.

this is what you get on Android 9+ on Axon 7 :

This is what you get after removing Dolby on Oreo:

 

[sashamsuper]

this is what you get on Android 9+ on Axon 7 :

This is what you get after removing Dolby on Oreo:

This is significant and sad. Interesting graphics using mods, such as AINUR NARSIL, for its part, is not yet available to make them.

 

[SkaboXD]

I just want to thank you for providing 1 year support of crDroid ROM for this device, it really means a lot, thank you!

 

[mohitomish]

Issue resolved

 

[blackpac]

I don't know if it's a Rom specific or not but found 2 bugs

* SIM 2 data activated but not working
* SMS can't be sent from SIM 2 while SIM 1 is engaged in a call

 

[raystef66]

NEW CRDROID BUILD 2020.08.14

Download on SourceForge crDroidAndroid-9.0-20200814-axon7-v5.12

Since my work on MI9 and Axon7 Q, except possible releases on sec. updates, no more request-builds will be made for axon7 crDroid

changelog :

====================
14-08-2020
====================

- Updated Sec.Patches August 2020
- Added Signature Spoofing Patch

NOTE : still for some reason on a clean flash homescreen apps can being modified. Though Dirty flash will leave your homescreen apps untouched

 

[samwichse]

Dirty flashed the update from the previous build and everything is working just as well as before. Love me some sweet, sweet security patches

It's also amazing how much less buggy this rom is than the releases ZTE put out themselves ??? I was about ready to get rid of this thing before loading this ROM... secretly wishing the hardware would die so I could just but a new phone. Now it's pretty much perfect!

 

[rn777]

It's realy perfect. Thank's a lot.

 

[randomUsername1]

CRDROID BUILD 2020.08.14 - Changing volume does not work.

NEW CRDROID BUILD 2020.08.14 - This is really great, THANK YOU, this is the best ROM no doubt.

But I cannot change the volume with the latest update...

- Cannot change it using the hardware buttons (nothing happens). Volume panel on the slide does not show up either. Literally nothing happens.

- Cannot change it via the settings (you can slide the slider, but nothing happens; the sound stays the same).

- Would love to provide a logcat, but don't know how...

Dirty flashed.

 

[SkaboXD]

NEW CRDROID BUILD 2020.08.14 - This is really great, THANK YOU, this is the best ROM no doubt.

But I cannot change the volume with the latest update...

- Cannot change it using the hardware buttons (nothing happens). Volume panel on the slide does not show up either. Literally nothing happens.

- Cannot change it via the settings (you can slide the slider, but nothing happens; the sound stays the same).

- Would love to provide a logcat, but don't know how...

Dirty flashed.

Try clean flash. I always do clean flash to avoid additional bugs as much as possible.