Develop Bugs

DSP Manager: how to?

In several places in the forums I see DSP manager mentioned as a way to change the sound output from the phone.
It is possible to use the .apk file or flash the .zip file to a stock firmware that is rooted (no other changes), or does it have to be applied to a custom rom?
Ta.

Here you go...
http://www.multiupload.com/7VS5O9KKQ0
Flash as you would a ROM

Hmm, I flashed it and the settings appeared, but they seem to make no difference to the sound output!

Trying via headphones? As I doubt you'd notice from the internal speaker
Other than that I can't help, have no issues personally

Yep, trying via headphones. Seems to make no difference at all. I am running a stock rooted HTC Rom.

Hi, I flashed the DSP from recovery and rebooted. Installation was successful but I can't find the app anywhere in my phone? where do I see it?

SOLUTION
ilya.glants said:
Hi, I flashed the DSP from recovery and rebooted. Installation was successful but I can't find the app anywhere in my phone? where do I see it?
Click to expand...
Click to collapse
For anyone else having this problem:
I didn't find the app I installed so I searched the net for other installation files, and found this:
h ttp://androidforums.com/1446319-post107.html
after I flashed this and rebooted, I got a 'force close' notification for the app. Than I went to /system/app/DSPManager.apk and installed it.
DSP Manager now working great ^^

I did as u said but it gives me a force close and when i try to install it i cant cause its already installed, cant uninstall it either, what should i do ? BTW I'm using AuraxTSense v7.4

did you install the one in the second post as well?
I'm using AuraxTSense 7.0

Yes, first I installed that one, it didn't work, then I installed the other. Is that the problem ? I thought so... so how should I fix it ?

good question..I'm not sure.. try installing the first again

Ok I did it, it removed the app from the app list. What now ? If I try installing it from /system/app it gives an error.

I don't know.. i just rebooted my device and it gave me the force close again. so I did what I did the previous time and ran that app from the location I wrote.. worked like a charm.. again..

ilya.glants said:
I don't know.. i just rebooted my device and it gave me the force close again. so I did what I did the previous time and ran that app from the location I wrote.. worked like a charm.. again..
Click to expand...
Click to collapse
I installed the other zip again, gave me a force close so went to system/app and tried to install it but I can't, only have the options uninstall and launch... No idea why is it working for you and not for me...
EDIT: Ok it works now, had to remove first the odex file and install the other zip again

Update DSP Manager
You can remove the DSPManager.apk file using the terminal emulator.
NOTE: You need to have a rooted phone, Superuser & Terminal emulator.
STEPS
1. Change to root user it is granted super-user permissions.
su -​2. Then change to the system app directory.
cd /system/app​3. Then move the DSPManager.apk to the tmp directory.
mv DSPManager.apk /tmp​4. Move the new apk file to the system app directory.
NOTE: Change to the directory where the DSPManager_1.0.apk is.
cp DSPManager_1.0.apk /system/app​5. Reboot the phone.
6. Check in the apps list and the new DSP Manager should be in there.
NOTE: If it all worked you can remove the DSPManager.apk from /tmp
rm /tmp/DSPManager.apk​
Attached is the version I use on my rooted HTC Desire.

In order to work, DSP Manager also needs a file called libaudioflinger.so in the /system/lib directory in addition to the apk.
The easy way to get this done is to use an update zip for DSP Manager. Get it from one of these links (all links from this page):
FileServ
MultiUpload
My FTP

doesnt get android to work on my hd 2... i managed it once but since i updated my android build i dont get it anymore...
i think it because i dont have an root folder in the android folder where i can put the files in ????????
if i just install it from the zip via astro explorer it appears in the menue but there is no change in audio ?!?!?!
what can i do ???

B-Man2005 said:
doesnt get android to work on my hd 2... i managed it once but since i updated my android build i dont get it anymore...
i think it because i dont have an root folder in the android folder where i can put the files in ????????
if i just install it from the zip via astro explorer it appears in the menue but there is no change in audio ?!?!?!
what can i do ???
Click to expand...
Click to collapse
I don't think you can install the zip from Astro Explorer because it needs to copy files to the /system partition which is read-only when the phone is booted up. In other words, you must have a rooted phone to do this.
If you do have a rooted phone, then reboot into recovery mode and install the update.zip the usual way.
If you don't have a rooted phone, well that's a whole different story.

i , please help me.
I've installed it via recovery and I made backup with my original needly files: libaudioflinger and libaudio. Then i copied my files back (deleted new files and moved old files) . I restarted my phone and it didn't boot. Just show me the White window (T-mobile)... Can i repair my phone by myself? Please help me and sorry for my english.

maximus rus said:
i , please help me.
I've installed it via recovery and I made backup with my original needly files: libaudioflinger and libaudio. Then i copied my files back (deleted new files and moved old files) . I restarted my phone and it didn't boot. Just show me the White window (T-mobile)... Can i repair my phone by myself? Please help me and sorry for my english.
Click to expand...
Click to collapse
I'm sorry I don't really understand the problem. Normally, installing the update.zip should be all that you need to do. I don't understand why you copied the old files back and were those two files the only files that you backed up?

Downloading apps from fire stick

Can anyone tell me how to get the apk's from the Firetv stick?
I would like to get the Fire stick version of Directv now?

You got two very easy options...
Option 1 - ES File Explorer APK Extracting
1. Install ES File Explorer on your FTVS directly from Amazon or side-load it if you have a favorite version.
2. Open ES File Explorer & on the Homepage choose "APP". It should have a number under it showing you how many apps you have installed so far.
3. From your list of installed apps choose which ever APK you want to backup by clicking & holding the "OK/Enter" button until there is a check on that file. Add checks to any other APK's you want to backup up at the same time.
4. At the bottom of the options you should see the option "Backup". Click on it & you should see a message saying if the APK backup was successful.
5. This backups are stored @ "/sdcard/backups/apps".
6. The easiest way to get them to your PC or Mac is to go into ES File Explorer's "Network" on the left menu & "Turn On" "Remote Manager". This will give you a "ftp://" address you can visit from any browser that is on the same Wifi Network. You can even use your phones browser.
7. Navigate to the FTP's "/backups/apps/" folder & just choose which APK(s) you want to save to your device.
8. Don't forget to "Turn off" the Remote Manager on your FTV device. And you can use ES File Explorer to delete any APK you have already moved off your FTV device in "/backups/apps/" to reclaim that storage.​
Option 2 - ADB APK Extracting
1. Download & unzip the Amazon Fire TV Utility App v0.66 or newer on the C:\ of your PC. It should look like C:\FTV\ .
(Amazon Fire TV Utility App v0.66 or newer can be found here: https://sites.google.com/site/amazonfiretvutilityapp/ )
2. Add your FTV's device IP to the AFTV Utility under File/Settings & wait to see that it has connected to your FTV.
3. Once connected you can use the "APK Extractor" option to view a list of all installed APK's. Then just choose which one you want to download. Click on "Extract APK" & confirm is the one you want.
4. A window will pop-up. And if there are no errors extracting the APK it will just close once completed. You should find your extracted APK's under "C:\FTV\Extracted_APK" .​
Very easy to do...
Addendum: You can check/match the MD5 Hash values between the APK in your FTV(S) device with the backup file you create on your PC. Just use ES File Explorer properties to get the original files MD5 Hash values & compare them with the MD5 Hash Values you end up with the APK on your PC/Mac.

Thanks for the help. I was able to grab the app. I loaded it on my android tv. The app ran and I was able to log in, but video won't load. Live channels will not load, nor the guide guide. I can see options to play on demand stuff but none will play. I just get an error that video failed to load error 40 QP1404. I assume it is because there must be some kind of check that is failing. Does anyone know if this can be fixed?

If your trying to run it on a rooted device. Then just take a look at this:
http://www.aftvnews.com/how-to-use-directv-now-on-a-rooted-amazon-fire-tv-or-fire-tv-stick/
Should do the trick.
---------- Post added at 02:04 AM ---------- Previous post was at 02:01 AM ----------
btw, can you check on your AndroidTV if there is an app available called Opera TV Browser & what version is available. And see if our can make a backup of the latest APK. Thanks

How to Enable Viper with Stock Rooted Android 7

Various links in Google world. Some worked. Others had issues. To keep this simple I am going to attach two files to use. This is based on the use of Magisk for rooting your setup. It does NOT work if you are only using SuperUser. The mods that stated how to do this with SU did NOT work for me, so I will not include anything with regards to that. Again, this is working for me with latest just posted Android 7 firmware for my SM-G925T and rooted with Magisk and TWRP recovery installed. Please don't ask if you are not rooted or no TWRP or whatever. They ARE required and Magisk is required too. Plus go to Playstore and make sure BusyBox is installed. I would also uninstall any prior versions of Viper prior to doing this. Or use Titanium BU to delete so as NOT to have competing files. After the above, take the attached file audio_effects.conf and replace the one located in your system\etc folder. The file is zipped simply to allow uploading. This is NOT installable from recovery. Simply unzip to use the conf file. Disregard the backup file in this zipped upload. The .bak is not needed. You will need an app like root explorer to do this. Make sure you set the file permissions the same as the app you are replacing. This is important. Permissions must be the correct same as the original file. Finally...take the attached v4afx_v1.4 zip and install from TWRP recovery. Reboot and should be good to go. If done correctly the left menu in viper that shows driver status will show everything processing, enabled, and working when Viper is ON and music is playing

Added webcam shot showing driver status. A screen shot would remove that window showing driver status.

Do you randomly lose root after this install?

Rom Access or advice for TAB S4

My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin

This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.

cbb77 said:
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
Click to expand...
Click to collapse
thanks for the info, i saw a few threads a few days ago about secure storage and did it manually which didn't help with the issue. similarly neither does the module for Majisk . a case of keep looking i guess. any other suggestions will be very much appreciated

Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.

cbb77 said:
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
Click to expand...
Click to collapse
Cheers will give it a go - at this point i have nothing to lose, just taken a fresh backup so nothing ventured nothing gained

its stuck no boot while removing secure_storrage module from majisk
Oddly having tried the suggestion above of removing the majisk module the device no longer boots it gets stuck on the Samsung logo. For some reason the vendor partition is no longer able to mount.. Completed a restore eventually to get it to boot. Disabling the module yields the same result. no vendor partition and no boot. Going back to an earlier backup prior to the module being installed

The plot thickens
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts

c6pea said:
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
Click to expand...
Click to collapse
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false

Boot failure when LIbs replaced
ashyx said:
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Click to expand...
Click to collapse
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking

c6pea said:
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
Click to expand...
Click to collapse
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?

ashyx said:
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
Click to expand...
Click to collapse
Thanks for the assist
It occurs only when the Libs are changed.
Originally using the majsic module to install the libs it couldn't overwrite the files as they are in use. modifying the build.prop seemed to resolve that but as soon as those libs are change either manually through terminal or via the installer i end up with a soft brick LOL
its Bugging me!!!

Interestingly
Once the device hangs.
Simply restoring the vendor partition doesn't fix the boot issue.
In order to get the device to boot I have to restore /data (you don't need to restore /vendor just /data)
oddly restoring the /data partition restores the 2 library files in /vendor to their respective originals

Majisk zip extraction issue
so I have resolved the Bluetooth issue, Rather having majisk install the module i just downloaded it and extracted the contents and discovered that upon zip extraction the contents of each file were appended to themselves. see screenshot "confused.jpg" of the readme.md - so in relation to the library files, the files being installed were double in size hence corrupt.
ie /vendor/lib/secure_storage.so should =308kb the file being insatalled in my /vendor/lib partition was 616kb the 64 bit library was also double the size it should have been.
infarct all the files within the Zip had the same issue.
so i extracted the Zip contents on my pc and transferred the library files via usb. made the relevant changes to build.prop and stopped the secure_storage deamon. Machine now boots and Bluetooth pairings are retained across reboots.
Small Wins
Any one have a clue why the files would double up on content??????

built in zip extractor
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be

c6pea said:
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
Click to expand...
Click to collapse
7zip is the extraction utility you want. Winzip is pants.

ashyx said:
7zip is the extraction utility you want. Winzip is pants.
Click to expand...
Click to collapse
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility

c6pea said:
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
Click to expand...
Click to collapse
Same for winrar, closed source bloated rubbish.
7zip supports practically every format and totally ad free.

[GUIDE]Enable auto brightness in custom roms

Hello everyone, I want to share how to enable auto brightness also known as adaptive brightness to custom roms for redmi 7.
Steps to enable auto brightness:
1. Download the attached apk
2. Navigate to /system/vendor/overlay using any file explorer which supports root. I will recommend ES File Explorer
3. Now copy the apk file to the navigated path
4. Set the apk permissions to 0777. If you are using ES File Explorer, then skip this step.
5. Reboot your device
6. Go to Settings > Display > Adaptive Brightness and enable it.
Don't forget to hit the thanks button
Note: This solution was found by @BoomBoomsss and was posted on 4PDA. I am just sharing his solution.

I am sorry that I couldn't give you credit on my post. But I am pretty sure that you have misunderstood me.
First, I didn't know that you are on XDA or what's your XDA profile. That's why I can't give you credit. But now I know. I will give you the credit on this post.
Secondly, I didn't say it's my work I just wanted to everyone hit the thanks button. I was looking for auto brightness for so long. But couldn't find a solution. That's why I thought I should share the solution with everyone.
Last thing, Sorry once again.

Tried the step by step guide, but I can't copy or move the apk to the specified folder... Sometimes the app points an error, but sometimes it says it copied/moved successfuly, but when I reboot nothing happens. Tried with ES File Explorer, and other apps as well. Any ideas?

prezoto said:
Tried the step by step guide, but I can't copy or move the apk to the specified folder... Sometimes the app points an error, but sometimes it says it copied/moved successfuly, but when I reboot nothing happens. Tried with ES File Explorer, and other apps as well. Any ideas?
Click to expand...
Click to collapse
Yes. Follow these steps:
Open ES file explorer
Go to menu > Tools> Root Explorer
Select Mount R/W
Select '/' and 'vendor/' to RW
Click Ok button
Restart your phone. Now follow the main steps and reboot again.
Sorry for being late. ?

Not working
I've followed your procedure, everything worked fine except the autobrightness doesn't. Brightness slider doesn't work at all.
My setup:
- redmi note 7
- vendor stock
- rom: lineage os 17 gsi from andyyan
- microg working
- phh-magisk
My question is, should i delete the only other file in /system/vendor/overlay which has almost the same name? Or what else can i do?
Thanks in advance
Edit: found a fix: in this telegram group @Lavendergsi
Search for brightness fix lavender and rename the zip so doesnt have spaces anymore. Flash via orangefox