[Android Software Development] guitardedhero:
No, the Axon 7 system inside the zip is from the latest B32 firmware released two weeks ago.

I didn't mention this earlier, but there are a total of three Dolby Atmos systems with the ZTE™ Nubia Z17 Atmos system being the default installation if your firmware is deemed compatible, otherwise, the BQ M10 Atmos system (my favorite of what i now describe as the "non-Nougat audioserver Atmos" systems. I'll explain later lol...) is installed.

Until I prepare all selections in AROMA, I have provided a couple files to override the result of the installation script's Atmos Compatibility Determination function (A device compatible with what I now describe as the "Nougat audioserver Atmos" systems can install either the BQ M10 Atmos or the Axon 7 "Nougat audioserver Atmos" system instead of the default Nubia system).

Since there is only a single "non-Nougat audioserver Atmos" system currently in the zip, those with incompatible firmware will have no choice other than to receive the BQ M10 Atmos system when choosing to install Dolby Atmos.

If I'm talking to "you", do not feel discouraged. I ported and tested dozens of different Dolby systems, most of them Atmos, and BQ's M10 Atmos system is absolutely phenomenal and may very well sound the best of the available Atmos systems in the zip.

Regarding the files I mentioned earlier, I suggest the zip be extracted and examined, certainly the /info folder. The contents of this folder provide the information, sources, and the files to force an Axon 7 or BQ M10 Atmos installation:

bq_atmos

axon_atmos

These files satisfy the override function when found in /data/local/ on the device during installation.

The script will seek /data/local/bq_atmos before seeking /data/local/axon_atmos so having both files in /data/local/ will result with the BQ M10 Atmos installation since it has the first opportunity to satisfy the override function. /data/local/bq_atmos must be removed or renamed if Axon 7 is the desired Atmos installation.

Please know that I am not overjoyed with the necessary compatibility parameters put in place, these are the result from some comprehensive testing and a bootloop epidemic.

If you discover the BQ M10 Atmos installation is the compatible Atmos system from the displayed text during the installation of what was desired to be Axon 7 or Nubia, don't feel discouraged. You evaded a guaranteed bootloop by not receiving either "Nougat audioserver Atmos" system.

However, those not satisfied with anything other than "Axon 7 Atmos" have that option in ahrion's Collective Dolby Atmos® Port thread where he has just recently updated the available ports, including Axon 7. It's not the "Nougat audioserver Atmos" system, but I don't blame him either. The "Nougat audioserver Atmos" systems were a chore to successfully port and then were almost grueling to troubleshoot many problems to finally result with my Atmos Compatibility Determination function to prevent users from experiencing those issues by defaulting to the best "non-Nougat audioserver Atmos" system available. Still, there will be a persistent need to explain why this occurs as more and more users attempt an installation hoping for something not received.

However, I am stubborn like that and want to provide the absolute best of everything I come across when diving into firmware on a daily basis. Furthermore, this adds value to the Dolby category as I am providing different content and in a different package. By merging the pairs of apk's and including the necessary content and information to manually prepare a successful installation within each single apk, those users that poke around in apk's they downloaded online will be able to achieve a full installation if any of these are distributed without anything else found in the zip. :good:

---------- Post added at 04:01 AM ---------- Previous post was at 03:47 AM ----------

To answer your first question: Yes, that is correct.

To answer your second question: This conclusion can only be determined by you from comparing both setups.

However, the two zips are completely compatible with one another. To begin the troubleshooting procedure with you, I decided the best next course of action was to ensure no other Dolby content was present when observing what seemed to appear as events of a Dolby installation not belonging to the Atmos system in your log output. :good: