NXP Smart AMP, a smart amplifier manufactured by NXP Semiconductors, a globally-leading electronics brand. A smart amplifier, as the name suggests, boosts the audio output of the smartphone. The NXP Smart AMP is the latest and best solution, with the best efficiency and best power-saving performance.” In fact, the ASUS R&D team collaborated with the NXP Semiconductors team to calibrate the smart amplifier, to maximize its performance while minimizing wear and tear to the device.
But what, exactly, does the NXP Smart AMP do? Firstly, it senses the speaker unit in real-time in order to dynamically increase efficiency while also protecting the speaker. “Speakers can overheat if they’re broadcasting at high volumes for long periods, but a smart amplifier can precisely detect the speaker’s position, resonance, and temperature, and keep tabs on its status. This allows it to avoid frequency ranges that could easily burn out the speaker. It can even adjust the volume dynamically to protect the hardware.”
Secondly, the NXP Smart AMP converts digital signals into analog sound waves more efficiently.
So, with this file will enable NXP "again" on custom roms that lacks NXP support. This file will fix volume step bugs on custom roms, fix distortion at max volume, fix in-call low volume and make speaker as loud as stock.
Flash the NXP.zip with twrp or other recovery, mount vendor partition first and don't forget to wipe dalvik cache.
Note: certain cusrom audio feature might be disabled after flashing this file (depend on cusrom itself).
Do with your own risk.
https://drive.google.com/file/d/1VGQ8Bk_Mix2XR7nMDcPRGjnHYIZQaU9R/view?usp=drivesdk
Great!
Can i use it in stock rom?
Is it possible for you to make a magisk module for the same?
iamfarhanansari said:
Can i use it in stock rom?
Click to expand...
Click to collapse
Stock rom already comes with NXP
Prashant324 said:
Stock rom already comes with NXP
Click to expand...
Click to collapse
But sound quality is not that great
NXP is not working in pixel experience latest caf based
mayank.. said:
NXP is not working in pixel experience latest caf based
Click to expand...
Click to collapse
Worked for me
amitahirwar24 said:
Worked for me
Click to expand...
Click to collapse
What are the steps to successfully install and enjoy it. Thanks!
Deleted.
chayansraj said:
What are the steps to successfully install and enjoy it. Thanks!
Click to expand...
Click to collapse
Mount cust/vendor partition first before flashing, then wipe cache + dalvik after finish, reboot, done.
vewa52 said:
Is it possible for you to make a magisk module for the same?
Click to expand...
Click to collapse
Nxp driver is "basic" / core level speaker driver that exist on vendor partition, different from other secondary level audio mod / filter like dolby, viper, etc.
chayansraj said:
What are the steps to successfully install and enjoy it. Thanks!
Click to expand...
Click to collapse
Download NXP zip
Reboot to recovery
Mount vendor system
Flash NXP.zip
Wipe dalvik/cache
Reboot to system
Done.
amitahirwar24 said:
Worked for me
Click to expand...
Click to collapse
How?
mayank.. said:
How?
Click to expand...
Click to collapse
I just flashed NXP zip via twrp
amitahirwar24 said:
I just flashed NXP zip via twrp
Click to expand...
Click to collapse
Didn't you mouth vendor?
mayank.. said:
Didn't you mouth vendor?
Click to expand...
Click to collapse
Yes I Mount vendor before flashing
How to check if I have NXP
After flashing this in havoc os left and right ear piece not function properly, and in pubg u can't hear properly from where enemy coming
Kang bang
Related
As most of you know, alankila published a modified AudioFlinger library that gives rooted Android installations much-needed DSP capabilities. (See here.) This has been upstreamed to Cyanogen-6 development branch and has been released in CM6 stable and a few other cooked ROMs. However, there wasn't much information on installing it on stock ROMs with locked bootloaders/recovery images (i.e. will only accept Google-signed update ZIPs), so here's a tutorial on how to do that. This has been tested working on my Nexus One running FRF91 and the stock HTC Passion bootloader and recovery image.
NOTE. You must be root!
1) Download the attached dsp-signed update ZIP. I'm not sure which version this is, but it lets you control both the speaker and headset curves independently.
2) Extract its contents to a local folder or to the SD card on the phone.
3) Using ADB, drop to a root shell (adb shell, then su.) and remount the system partition as read-write.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Afterwards, make a backup of libaudioflinger so that you can restore it in case your phone blows up.
Code:
mv /system/lib/libaudioflinger.so /system/lib/libaudioflinger_bak.so
. Finally, copy DSPManager.apk to /system/app and the modified libaudioflinger on your SD card to /system/lib.
Code:
mv [path-to-files]/DSPManager.apk /system/app/
Code:
mv [path-to-files]/libaudioflinger.so /system/lib/
4) Reboot.
If your phone fails to boot, just delete the libaudioflinger library you copied over and restore the original from the backup you made.
Enjoy! It's fantastic!
This works great on my Incredible with stock 2.2!
Thanks!
Of course, you could also just install ROM Manager, then flash a custom recovery image and install the update ZIP that way if it's easier.
Does this app control ear piece, speaker and headphones? also does it apply the settings to calls as well as music? thanks. I have it on my phone for evils sense rom but not really noticing much of a difference. thanks.
This works great, I just wish the sliders were a bit more responsive.
installed through clockwork recovery on LeoFroyo rom 2.0.1Beta3, and it works like a charm. the sliders could use + and - icons on side to help change the numbers.
All the dsp settings do is make my speakers clip...
Sent from my Nexus One using XDA App
I would be careful with equalizing the speaker; if it's like most phone speakers, it's pretty fragile...
@jdub: It works for speakers, headphones and bluetooth devices. It affects all sound on the phone.
dgart08 said:
All the dsp settings do is make my speakers clip...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Same here, no matter how slightly (0.3dB or so) I change the level of any band, it clips when connected to my car stereo, with headphones the issue is also present but less annoying.
will this work for bluetooth streaming
danimar1 said:
Same here, no matter how slightly (0.3dB or so) I change the level of any band, it clips when connected to my car stereo, with headphones the issue is also present but less annoying.
Click to expand...
Click to collapse
I found if you have your Nexus connected to your car stereo, the speakers will not clip if you turn the headset volume down one or two notches below 100%.
GchildT said:
I found if you have your Nexus connected to your car stereo, the speakers will not clip if you turn the headset volume down one or two notches below 100%.
Click to expand...
Click to collapse
I think I already tried that, but I'm not totally sure though ... I will flash it again and give it a try. Thanks for the tip!
can this be installed on miui as per the OP?
mtw4991 said:
can this be installed on miui as per the OP?
Click to expand...
Click to collapse
The framework etc. in MIUI is not compatible with this mod. will cause bootloops... But if you find a solution please share, I'm really missing the DSP Manager and Trackball Alerts in succession on the MIUI Rom!!
cyberspaced said:
The framework etc. in MIUI is not compatible with this mod. will cause bootloops... But if you find a solution please share, I'm really missing the DSP Manager and Trackball Alerts in succession on the MIUI Rom!!
Click to expand...
Click to collapse
I am running DSPManager v1.0 on my N1 using Rodriquez v1.1 ROM. I actually used Titanium Backup to install from a backup. The apk is in my /data/app folder. APK is listed as com.bel.android.dspmanager-1.apk
Docmjldds said:
I am running DSPManager v1.0 on my N1 using Rodriquez v1.1 ROM. I actually used Titanium Backup to install from a backup. The apk is in my /data/app folder. APK is listed as com.bel.android.dspmanager-1.apk
Click to expand...
Click to collapse
Yes, you can install and run the app, but i doubt it will actually do anything, might also be the reason Rodriguez removed the app from his ROM....
cyberspaced said:
Yes, you can install and run the app, but i doubt it will actually do anything, might also be the reason Rodriguez removed the app from his ROM....
Click to expand...
Click to collapse
I could have sworn on his first version I did hear a difference. Just checked with v1.1 and you're right. Nada. My bad....but appreciate the reply.
droid x 2.2 fails to boot, stuck on motorola logo.
someone *please* make this work!
To preven cliping enable audicompression to lowest level. Works for me
I badly want to try the DSP manager. Can I use this with my rooted vibrant running stock android 2.1?
This Guide helps on configuring the A.R.I.S.E. (Auditory Research in Sound Enhancement) Sound System, including Viper4ARISE, in your Axon 7. This fixes the low volume problem for the EU version of AXON 7 2017G and increases the quality in all the models. Among other features it reconstruct the signal for streaming audio, increasing the spectrum and bringing more detail to the sound. It is also compatible with Dolby ATMOS. The official thread is complicated since it offers a lot of different options. Here I try to provide an easy and straightforward guide for beginners. After a while you will be able to get into the universe of profiles, settings and extras explained in the official thread.
REQUIREMENTS:
- Since this package modifies your system partition, it requires unlocked bootloader and root.
- Another requirement is to have the Busybox patch. If your root method is not including it, just grab one of the many free Busybox Apps from Play Store.
WARNINGS:
- Since this module is not systemless, in case of an OTA upgrade you will need to reflash the stock system before performing an OTA upgrade, apply the upgrade and then reinstall the Sound System.
- Unfortunately there is no uninstaller so keep a backup of your system partition before proceeding with the installation.
DOWNLOADS:
For a safe installation begin using ARISE Deuteronomy 2.2.3 Patched. Some people likes better the sound athmosphere provide by this version. The latest stable release ARISE Deuteronomy 2.3.3 and other versions can be found in the official thread. However 2.2.3 patched has proven to be very stable and fully compatible with our device. Later on you can test upgrading to the current or another release.
Since ARISE Sound Systems rewrites the audio configuration depending on your settings, you may need the Dolby ATMOS add-on too to recover this feature.
You'll have to flash it using TWRP recovery 3.0.3 or Flashfire app.
INSTALLATION:
STEP 0: Ensure you have a backup of your system partition and you have downloaded the ARISE Sound System to the internal or external storage of your phone.
STEP 1: Disable Dolby ATMOS.
STEP 2: Flash ARISE Sound System version 2.2.3 patched either using TWRP or Flashfire.
STEP 3: Reboot, play some music, open Viper4ARISE, activate the master switch for your headset and enjoy. Save your current configuration in the hamburger menu before testing new settings. You can also tune the phone speakers, bluetooth and external USB DAC settings.
STEP 4 (Optional): If Dolby ATMOS is not working after applying the patch, Flash the Dolby ATMOS add-on.
TROUBLESHOOTING:
- If ask for driver installation then Open your favorite file explorer and go to: /vendor/etc and rename audio_effects.conf to audio_effects.conf.bak, reboot and follow step 3 again.
- Ensure you have unlocked the system partition by typing reboot disemmcwp in the system or TWRP terminal or ADB shell. and repeat from step 1.
MY SETTINGS:
My recommendation is to leave Dolby ATMOS disabled unless you are watching a movie or concert. You do not have to disable Viper4ARISE when using Dolby ATMOS, however do never mix surround or spatial processing in both, it will be a mess. I share my general settings as an starting point, however you can experiment with all the parameters to find the sweet spot for your gear. Do not forget to save your current configuration in the hamburger menu before testing new settings, it is hard to remember the detailed configuration afterwards:
Check that the Headset HiFi setting in your Phone settings is set to Super. and for Viper4Arise set:
Master Power ON
Spectrum Extension ON (only for low quality streaming)
- Strength: 0.2
Dynamic System ON (Headset Only)
- Listening Device: Common Earphone v2
- Dynamic Bass: 18% for acoustic music and high dynamic range sources, up to 29% when listening dance/electronic
ViPER Bass OFF (only activate it if your headphones require extra Bass. In my case I have it disabled).
- Bass Mode: Natural
- Bass Frequency: 40hz
- Bass Boost: 13dB
VIPER Clarity ON (It can bring up pretty good detail to the sound).
- Clarity Mode: Natural
- Clarity: 6dB
Master Gate (Limiter)
- Channel Pan:0%
- Output Gain: 2.3dB (set more if you want more output volume without making quantization noise audible)
- Limit Threshold: 0dB
After setting it, just toggle the master switch several times to hear the difference. You will realize how much quality can be extracted from this excellent Axon 7 hardware.
How was your experience?
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
vyurdin said:
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
Click to expand...
Click to collapse
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Loader009 said:
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Click to expand...
Click to collapse
It works now, thanks! luckily I didn't have to edit that file.
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
nupi said:
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
Click to expand...
Click to collapse
Change the Selinux to Permissive on boot.
reV17 said:
Change the Selinux to Permissive on boot.
Click to expand...
Click to collapse
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
Unfortunately I don't believe it'll work if you put it back to enforcing.
tele_jas said:
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Click to expand...
Click to collapse
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have: the bootloader unlocked, F2FS filesystem, root, Xposed (all 9 modules working) and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
You can try setting up V4A in enforcing mode using this guide.
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Killerdog said:
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Did you try xposed 87? November security patches broke the earlier versions
nupi said:
Did you try xposed 87? November security patches broke the earlier versions
Click to expand...
Click to collapse
i try updating xposed inside the app. update is ok, but if i activate any module it bootloop at next reboot.
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Killerdog said:
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Try rooting your device using this method. The root includes Xposed (I have 8 modules up and running) and everything should be working. Probably using HelsAx7 as the base ROM could solve your problem.
tele_jas said:
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Click to expand...
Click to collapse
PowerAmp and Player PRO are the best in sound quality, the second is even better. And both seem to be working fine with Viper4ARISE. What kind of source are you playing (bandwidth and bitdepth)?
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Teet1 said:
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Click to expand...
Click to collapse
You can use wake lock detector to check what's wrong. The package is pretty stable. Could you please provide some more info (device, ROM, root method, media player, ARISE version, Viper4A configuration...)?
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
I'm wondering if you can help me with another issue I'm experiencing since I last posted here. My battery started draining really fast since I flashed the audio patch, I'm aware that's normal for viper but this is abnormal since the battery drains when the phone is not in use and it tends to stay warm. I have never had this issue when I had viper on my note 4.
The steps I have done for my phone:
Root method by jcadduono’s official thread in your safety net guide with success.
Done all steps with safetynet steps from above with success.
And I did the audio upgrade from this thread with success by using your preferred one.
And that's when my phone started draining more than it usually does for viper and being slight warm when not in use. I have already done a wipe before I did all these methods.
EDIT: Someone already mentioned the issue I'm having and I did not see that on mobile. I'm running all of those on A2017U stock rom running on b29 for additional info. I used stock music player, usb audio player pro (eXtream Software Development) for external dac and Equalizer + (DJiT) which i rarely use. I'll install wakelock detecter and ill report back what I find.
Hey, anybody knows how can I increase the volume on Android One? I know for a fact that it could be easier in a custom rom but for now I think that stock it's the best option at the moment.
So, I tried editing different mixer paths files (changing rz0 and rx1 values) because that usually worked on my old XZ Premium and a Redmi Note 5 running PE, but the values keeps resetting to default after reboot, any ideas?
Build a Magisk module for system files modification. Direct editing is "fixed" by DM verity and it's error correction mechanism.
Also you can use equalizer app which has pre-amp/gain function (REEQ, EQFY, Viper4android, probably James DSP, ..).
_mysiak_ said:
Build a Magisk module for system files modification. Direct editing is "fixed" by DM verity and it's error correction mechanism.
Also you can use equalizer app which has pre-amp/gain function (REEQ, EQFY, Viper4android, probably James DSP, ..).
Click to expand...
Click to collapse
Forgive my noobery but how do I do magisk module for that?
Yup, I'm using V4A but preamp gain usually may result in distortion whereas using sound control via custom kernel or editing audio files result in a boost on the volume evenly
abrahamrhs said:
Forgive my noobery but how do I do magisk module for that?
Yup, I'm using V4A but preamp gain usually may result in distortion whereas using sound control via custom kernel or editing audio files result in a boost on the volume evenly
Click to expand...
Click to collapse
Download the template https://github.com/gedoor/magisk-module-template
And follow the tutorial https://topjohnwu.github.io/Magisk/guides.html
Or..download one of the existing modules from Magisk repo and try to modify it to your purpose https://github.com/Magisk-Modules-Repo
Though I'm not sure if there is really some difference between using EQ pre-amp gain and modifying XML paths, both work with digital gain and too much gain will result in distortion. But I might be wrong, I didn't test it.
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. I am not responsible for any hearing loss, please listen at a safe volume level. Use this mod at your own risk there is no warranty or guarantee.
This mod will enable your Quad DAC & enable LGMusic player.
If not rooted with Oreo on H910 link
build.prop mod + Force true 24 bit 44.1 kHz link
Version 1.1
Updated twrp install script
Just flash on top of older versions
Version 1.2
Updated group file permissions, this should not cause an issue with v1.1 but I wanted to correct it. Just flash on top of older versions
Version 1.3
Fixed a permission error. Just flash on top of older version to update.
Should work on other lgv20 phones that never had LG Music Player installed from the factory.
Note: This mod will only work on Stock Oreo 8.0 rooted, wont work on LineageOS
.
Requirements:
Root /w twrp
Stock Oreo 8.0
Never had with LGMusic player installed from the factory.
No LGMusic player apk installed on your phone.
You can Flash the mod in twrp or follow the guide.
Guide Enable DAC & LGMusic player.
First download the H918 rom H91820f.zip You can download it from mega, should download fast.
[Rom][Oreo][Rooted] T-Mobile H918 [20f] [20g] [20h] Oreo flashable
Then extract the zip file.
mount system.img on your computer.
Then copy the five folders and one file from the mounted image, to your phone in the same directory structure listed below. Overwrite.
/system/priv-app/LGMusic
/system/priv-app/LGMusicWidget
/system/priv-app/LGMusicController
/system/etc/com.lge.music.xml
/system/vendor/overlay/com.lge.music
/system/vendor/overlay/com.lge.sizechangable.musicwidget.widget
You should not have to change the file permissions if using a root file manager. in Android. But if you using adb or twrp file manager you may have to.
File permissions to 0644
/system/etc/com.lge.music.xml
/system/priv-app/LGMusic/LGMusic.apk
/system/priv-app/LGMusicWidget/LGMusicController.apk
/system/priv-app/LGMusicController/LGMusicWidget.apk
/system/vendor/overlay/com.lge.music/com.lge.music.apk
/system/vendor/overlay/com.lge.sizechangable.musicwidget.widget/com.lge.sizechangable.musicwidget.widget.apk
Restart phone.
Credits, A Special Thank You
@dudeawsome for providing the H918 rom XDA
I'm guessing this has no effect on Bluetooth audio quality? Only when using a wire?
thejjmax said:
I'm guessing this has no effect on Bluetooth audio quality? Only when using a wire?
Click to expand...
Click to collapse
That's a good question and I am glad you asked it. Because I forgot include that answer in my guide. So to answer you question, there is a noticeable difference in sound quality with using Bluetooth. I am using aptx hd, as for sbc Bluetooth I am not sure. But you are correct a wired headset should get up-scaling to 32 bit sound with LGMusic player.
thejjmax said:
I'm guessing this has no effect on Bluetooth audio quality? Only when using a wire?
Click to expand...
Click to collapse
Oh I forgot to mention that the sound on the internal speaker has improved also. I am using the build prop tweaks that enables system wide Quad DAC support in any app.
Unlock the FULL Potential of the Lgv20's Quad DAC. (root only)
There is a twrp file you can flash now to enable the dac support.
Many thanks for this. Flashed the TWRP zip and it worked flawlessly. Now have working LG Music on my H910 for the 1st time ever. Yes, it's still my daily driver...
q1nt said:
Many thanks for this. Flashed the TWRP zip and it worked flawlessly. Now have working LG Music on my H910 for the 1st time ever. Yes, it's still my daily driver...
Click to expand...
Click to collapse
Your welcome, glad you enjoy it.
This TWRP zip doesn't do the build.prop mod to Force true 24 bit 44.1 kHz does it?
The build.prop mod + Force true 24 bit 44.1 kHz .zip linked in the first post enables it. Haven't tested 24/44, but ADB test with the mod installed showed 16/44 does not get interpolated to 16/48 and 24/192 plays natively. So I doubt there would be any problem with 24/44
Thanks edwin_ecoral for the original mod
Adapted from that for Galaxy A50
Features-
Enabled Dual Speaker
Some more audio Effects in Dolby Atmos Config.
Note-
1. I am not responsible for any damage, proceed on your own.
2. Since the second speaker is not a dedicated audio speaker, was only meant for calls, don't complain about low volume. It is what it is. Try building your own if you want.
Not tested for M31. Only tested for M31s.
If working on M31, please write in the comments.
Edit 1-
Tested on One UI 4.1
Working on m31 but yeah volume is quiet low from other speaker
Anishx said:
Working on m31 but yeah volume is quiet low from other speaker
Click to expand...
Click to collapse
That's just the hardware
works great on m31 superior os a13
This works on M21 one ui 4.1, thanks for making this
how to install for m31 stereo speaker
bgr.kya1 said:
how to install for m31 stereo speaker
Click to expand...
Click to collapse
Install zip file in TWRP
Tried through termux
Then found out that you need to install it through TWRP
I entered TWRP, spend 15 minutes trying to access internal user storage ("/storage/emulated/0/"by default), no luck
Then booted into Android, copied to SD card, which I could access, and tried to reboot fo TWRP again
Tried with Volume Up + Power like 7 times then + USB connect, nah, everytime I wait to boot into Android, then power off, now hate TWRP
I was really angry, so f TWRP
I also reminded that in Magisk, you can reboot to recovery, but opened the wrong app, and my phone freezed for another 2minutes
Last try really
Nah, I getting (permission denied) errors to every data folder when installing zip