OK everyone, there seems to be mass confusion on what to do to get Viper4Android running, this guide should help clear that confusion.
DO NOT USE THESE FILES UNLESS YOU HAVE A NEXUS 6P. SO MANY PEOPLE HAVE ISSUES BECAUSE THEY USE FILES DESIGNED FOR OTHER PHONES.
Firstly: Are you running normal root or systemless root?
If you are running systemless root I suggest you switch over to normal root to get things working. So far, systemless root has been a roadblock for some people and Viper4Android starts acting up with systemless root installed.
Secondly: Have you flashed any of the billion V4A recovery flashable zips?
If yes, restore your system partition as those have a billion and one differently modified files that will probably screw over how your phone functions.
Thirdly: Do you have enough room in the /system and /vendor partitions?
Install the Busybox binaries (linked below) and open a terminal (using your favorite terminal app, or Terminal Emulator) and run
Code:
df
and make sure that you have enough room for the files.
If your /system partition is full, try deleting common apps like Chrome or Drive and install them from the Play Store as user apps instead.
If your /vendor partition is full, there isn't much to fix other than if you installed overlays for Layers, try uninstalling one (some overlays can go up to 400KB, like ones for Chrome). However, it may seem that you don't need to worry about the /vendor partition, more on that below.
OK, now it is time to continue.
If you don't want to follow this guide, then you can use Lollviper's recovery flashable zip, as it works just fine. Use the standard zip, and not the surround zip: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Choose your favorite v2.3.4.0 version of V4A and install it to /system/priv-app/. Just create a folder with the same name as the APK, give it the same permissions as the other folders, and drop the APK in it making sure to also give it the permissions that the other APKs get. If you encounter issues with a customized version of V4A, I suggest you use the standard version. So far, Lolliviper seems to work.
Make sure to install BusyBox, I recommend this one: https://play.google.com/store/apps/details?id=stericson.busybox
If the files linked below can't be downloaded, use the zip file at the bottom of this post and continue following the guide.
Now, download this file (49_viper4android.sh) : https://www.dropbox.com/s/rcp77ul41m...ndroid.sh?dl=0
And create a folder called su.d in /system/. The path should be /system/su.d/, and then give it permissions 0700 with root:root, and drop the script into the folder with permission 0755 with root:root. This script will allow V4A access to mediaserver, so it can see audio to do it's magic. You can make sure that the script worked on boot by checking /data/v4a_script.txt for if it exists, or, was modified recently to correlate with you booting your phone.
Now do the same for this file (audio_effects.conf) : https://www.dropbox.com/s/57y44o74dk...ects.conf?dl=0
And drop the file in /system/etc/ AND in /system/vendor/etc/ (alternatively you can go to /vendor/etc/ as it's actually the same folder). Both of the files should have permissions 0644 with root being the owner and group. This modified file will allow V4A to be used as an equalizer and allow it to do magic in your audio. Quick note, if V4A keeps asking to install the driver, then delete the audio_effects.conf in /system/vendor/etc/ and don't worry about it.
Now the file which will allow V4A to work system-wide, like in YouTube (audio_policy.conf) : https://www.dropbox.com/s/yi8u3j91z3...licy.conf?dl=0
And drop it in /system/etc/ and give it permissions 0644 with root being owner and group, and you are good to go. This modified file removes the "deep_buffer" module that made it so apps that don't hook into Viper4Android (apps that aren't music players) wouldn't have their audio processed. Some of the flashable zips included modified files, but usually only for the Nexus 5.
Now disable or delete the app MusicFX:
This is necessary as Google Play Music will use MusicFX over Viper4Android if the app isn't disabled.
That should be it, you can now continue with your installation of Viper4Android and it should work.
Issues:
Viper4Android still doesn't work!
Click to expand...
Click to collapse
Are you sure you followed the guide correctly? Wipe everything and start fresh because if you used recovery flashables they do stuff they really shouldn't.
My headphones don't work.
Click to expand...
Click to collapse
Another potential issue with random recovery flashables, suggest you wipe and start again.
Viper4Android's driver doesn't stick.
Click to expand...
Click to collapse
Install Viper4Android to /system/priv-app/ and that should fix your issue.
OR
Delete the audio_effects.conf file from /system/vendor/etc/.
Viper4Android doesn't work in Google Play Music.
Click to expand...
Click to collapse
Remove the MusicFX app.
Viper4Android doesn't work in YouTube.
Click to expand...
Click to collapse
Make sure you did the proper steps for the audio_policy.conf file.
worked like a charm. Thanks mate!!!
Why do you guys need this? Audio reproduction is excellent and this will only make it sound worse. The only way to improve the sound would be better headphones and/or amp.
Thanks @Namelesswonder for the help .. I have not used your steps might use them based on other users findings and plus these steps will have to redone upon every ROM flash..
I believe all this could be done with a flashable zip , I know we had flashable zips for Nexus5.
@AndrasLOHF I see you have Nexus6P now , will you be able to help us out
Thanks
likonvampire said:
Thanks @Namelesswonder for the help .. I have not used your steps might use them based on other users findings and plus these steps will have to redone upon every ROM flash..
I believe all this could be done with a flashable zip , I know we had flashable zips for Nexus5.
@AndrasLOHF I see you have Nexus6P now , will you be able to help us out
Thanks
Click to expand...
Click to collapse
I haven't rooted or anything yet. From my experience on all the dev previews I would think the Lolliviper zips would still install fine just as they used to. Just don't use the Surround Sound zip.
Thank you! Works great on Nexus 6p. Can't live without the Viper.
designgears said:
Why do you guys need this? Audio reproduction is excellent and this will only make it sound worse. The only way to improve the sound would be better headphones and/or amp.
Click to expand...
Click to collapse
You must be unaware the audio sound is completely subjective.
AndrasLOHF said:
I haven't rooted or anything yet. From my experience on all the dev previews I would think the Lolliviper zips would still install fine just as they used to. Just don't use the Surround Sound zip.
Click to expand...
Click to collapse
Yeah, I just checked it and Lolliviper flashable does work just fine, I'll put it up in the post. My intent for this post was to just outline how to install it without using flashable zips as people were using the wrong ones and having troubles.
Shockz said:
You must be unaware the audio sound is completely subjective.
Click to expand...
Click to collapse
You misread what I said. If you like crappy sound, you like crappy sound, nothing can be done about that. Running audio thru any software filter will degrade the quality, period.
I flashed the lolliviper zip, but viper4android keeps asking me to install drivers (even after install and reboot).
Edit: I'll re-flash and wipe dalvik/cache and try again.
Edit 2: Yup, still having the same issue. It also takes awhile for the driver install to happen too (even though it doesn't actually work).
mugenga said:
I flashed the lolliviper zip, but viper4android keeps asking me to install drivers (even after install and reboot).
Edit: I'll re-flash and wipe dalvik/cache and try again.
Edit 2: Yup, still having the same issue. It also takes awhile for the driver install to happen too (even though it doesn't actually work).
Click to expand...
Click to collapse
OK then, try using my way instead. Weird, because flashing the zip worked for me. Do you have systemless root? Try renaming the audio_effects.conf in /vendor/etc/, checking the permissions on audio_effects.conf and audio_policy.conf in /system/etc/, and checking that the 50viper.sh file in /system/su.d/ at least has permissions 0755.
Namelesswonder said:
OK then, try using my way instead. Weird, because flashing the zip worked for me. Do you have systemless root? Try renaming the audio_effects.conf in /vendor/etc/, checking the permissions on audio_effects.conf and audio_policy.conf in /system/etc/, and checking that the 50viper.sh file in /system/su.d/ at least has permissions 0755.
Click to expand...
Click to collapse
I don't have systemless root, but I'll look into the permissions.
Edit: All my permissions look fine. I'll try and tinker around some more. Still not sure why the driver isn't installing.
You probably need more space in the system partition. Delete an app and reinstall from there play store.
---------- Post added at 19:46 ---------- Previous post was at 19:46 ----------
You probably need more space in the system partition. Delete an app and reinstall from the play store.
AndrasLOHF said:
You probably need more space in the system partition. Delete an app and reinstall from there play store.
---------- Post added at 19:46 ---------- Previous post was at 19:46 ----------
You probably need more space in the system partition. Delete an app and reinstall from the play store.
Click to expand...
Click to collapse
I have 1.8GB free in my system/root partition.
Edit: I solved my issue. I had to delete audio effects conf from system/vender/etc
mugenga said:
I have 1.8GB free in my system/root partition.
Edit: I solved my issue. I had to delete audio effects conf from system/vender/etc
Click to expand...
Click to collapse
Thanks a lot for this. I was having same issue and this worked for me.
I did flash the lolliviper zip , the processing worked with pocketcast app but no go with SoundCloud...
Sent from my Nexus 6P using Tapatalk
mugenga said:
I have 1.8GB free in my system/root partition.
Edit: I solved my issue. I had to delete audio effects conf from system/vender/etc
Click to expand...
Click to collapse
Yes worked like a charm!
Hi guys,
How does this improve audio quality from the speakers? Coming from Boomsound the speakers on the 6P seem to lack any kind of bass. Could viper help in that department?
Sent from my HTC One using XDA Free mobile app
tgeza said:
Hi guys,
How does this improve audio quality from the speakers? Coming from Boomsound the speakers on the 6P seem to lack any kind of bass. Could viper help in that department?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Anyone?
Sent from my HTC One using XDA Free mobile app
tgeza said:
Anyone?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Because you can tune the way the speakers sound to your liking. It makes the phones speaker and any headphones sound much better than they normally do.
Related
So after using the Samsung Galaxy S II for over a month now I've had one complaint. In-Call Volume using the handset ear piece. It was "OK" in quiet places but anywhere else...way below par.
So, after looking around for several weeks trying to find a fix I finally got help from a well know dev (Entropy512) as well as using system/lib audio files from Designgears ROM 'Perception'.
So...how do you finally get your in-call volume increased?
First and foremost...Always backup whatever you're changing. Better safe than sorry. Just make a copy of your current system/lib folder, rename it something like 'backup_lib' and place on your sd card somewhere.
Option 1
Download this flashable zip, flash it in CWM, Reboot, Enjoy. (This zip includes some audio files from the Perception ROM, if for any reason DesignGears has an issue with this PM me and I will remove the zip. I'm only using the files to help others solve their in-call volume issue)
MAKE A BACKUP BEFORE FLASHING
Download the Flashable Update Here
I have tested this on three different SGSII's and all seems well! This is a NO WIPE flash, I do reccomend clearing your Dalvik Cache and Cache Partition though.
-Reboot into Recovery
-Scroll down to 'Advanced' and select
-Select "clear Dalvik Cache"
-Flash this update
-Reboot your phone and enjoy!
Option 2 (Incase the flash doesn't work or I am asked to remove the the zip file)
1) Download Designgears ROM 'Perception' Found Here
2) Open the zip file of your current ROM (doesn't matter what ROM)
3) Open the system folder and then open the system/lib folder (of your current ROM)
4) Next, Open the same folder in the Perception ROM
5) Copy the files listed below from the Perception ROM and paste them over the files in your ROM:
- lib_Samsung_Acoustic_Module_Llite.so
- lib_Samsung_Resampler.so
- lib_Samsung_Sound_Booster.so
- libaudio.so
- libaudioeffect_jni.so
- libaudioflinger.so
- libaudiohw_op.so
- libaudiohw_sf.so
- libaudiopolicy.so
- liblvvefs.so
- libmediayamaha.so
- libmediayamaha_jni.so
- libmediayamaha_tuning_jni.so
- libmediayamahaservice.so
- libsamsungAcousticeq.so
- libsamsungSoundbooster.so
- libsoundalive.so
- libsoundpool.so
- libSR_AudioIn.so
- libyamahasrc.so
*Only copy/replace the files listed above as they are only audio files. DO NOT COPY/REPLACE all system/lib files... You'll have unwanted consequences and you'll probably kill a puppy.
6) Now go to the Perception ROM and open system\app and find phone.apk. (Save a copy of your current phone.apk...Just in case)
-Copy (Perception's) phone.apk and replace the phone.apk on your current ROM.
7) After you replace the files listed above on your ROM, reflash your ROM and enjoy your increased call volume.
Note: If you don't want to reflash your ROM and risk losing any settings, you should be able to copy the files and replace them with Root Access and a file explorer, then Reboot your device immediately after. I haven't tried this yet so if someone wants to try and leave feedback, please feel free.
EDIT: Copying the files using a root explorer does work but may cause your phone to crash/reboot afterwards. I'd still recommend just re-flashing the ROM to avoid potential issues. Once again, make sure and make a back up so you can revert any changes if something doen't work properly.
I will try uploading a zip file with appropriate files so you can download but currently I do not have Designgears permission. This is their code and I don't want to step on any toes.
EDIT: I have tried reaching out to DG for permission but had no luck, if he asks that I remove the zip file, I will do so.
Known Potential Issues:
- When flashing over a stock/rooted ROM this update may cause the phone application to crash/force close. I have tried this update personally on every ROM I could flash and haven't had any issues. However, I have not tried it on the stock ROM. If you're on stock/rooted, please make a backup so if it does cause issues you can simply revert the changes.
Much thanks goes to Entropy512 for the help with solving this issue and Designgears ROM 'Perception'. Using Perception showed me that increasing the in-call volume was possible! (it's a very stable and awesome ROM as well )
***UPDATE***
Due to some people being a worried about flashing the update I have taken the liberty of making the backup files for you and making them flashable!
- I have made revert files for all of the major ROM's we currently have for our device. I did not include Perception because that ROM is where the audio files originated from. Below is the download links for the backups.
IF my volume fix does NOT work, simply download the backup for your ROM and flash it. It will revert all the changes my fix made.
- Revert_CM7.1_Stable
- Revert_H8s2_1.2.2
- Revert_Serendipity_8.2
- Revert_Stock_UCKH7
- Revert_UnNamed_1.2
- Revert_MIUI 1.11.4 v1
- If you are using Perception ROM you do NOT need the volume fix as this ROM has the files built in
As a side note, I have tried this on several I9100 ROM's as well and had luck with them all.
If this thread helps, please click the thanks button for me, I'm new to the XDA community.
Any I9100 ROM should work here for the libs - however:
Your mic will be screwed up for outgoing audio unless you change the Samsung Noise Reduction settings. (DG forced this in Perception, I believe he did it in an APK somewhere and not in the libs.)
Entropy512 said:
Any I9100 ROM should work here for the libs - however:
Your mic will be screwed up for outgoing audio unless you change the Samsung Noise Reduction settings. (DG forced this in Perception, I believe he did it in an APK somewhere and not in the libs.)
Click to expand...
Click to collapse
I just tried a call and you're correct, the mic isn't working properly. Do I need to find the APK or do you know what changes I need to make? This is a popular issue and I'm hoping this thread can help.
Edit: I found some APK's....any idea which one would deal with the mic?
-CallSetting.apk
-Phone_Util.apk
-Phone.apk
-Settings.apk
Ahahaha, good thing I made a backup before pasting, but pasting the files in root explorer does work, however your phone will crash and reboot, but it is louder.
Doesn't work on the apk :v
penguinlogik said:
Ahahaha, good thing I made a backup before pasting, but pasting the files in root explorer does work, however your phone will crash and reboot, but it is louder.
Click to expand...
Click to collapse
I'm testing different apk's right now. As soon as I figure out which apk the fix is located in I'll edit the post.
Maybe DG can drop a hint to me
Hmm does this enable the AUDIO part of the Samsung Service mode?
penguinlogik said:
Hmm does this enable the AUDIO part of the Samsung Service mode?
Click to expand...
Click to collapse
I haven't tried the audio menu yet, feel free to try if you'd like and let me know. 2 birds 1 stone.
Nope... ATT WHY YOU DISABLE THE MOST IMPORTANT MENU.
penguinlogik said:
Nope... ATT WHY YOU DISABLE THE MOST IMPORTANT MENU.
Click to expand...
Click to collapse
I figured out which apk fixes the mic issue it's the phone.apk. I updated the original post. Sorry for the set back. Let me know if you experience any issues
Just posting another screenshot to show the phone.apk.
penguinlogik said:
Ahahaha, good thing I made a backup before pasting, but pasting the files in root explorer does work, however your phone will crash and reboot, but it is louder.
Doesn't work on the apk :v
Click to expand...
Click to collapse
Try copying the CallSetting.apk as well (use both). If you still don't have any luck with fixing the mic issue and you're using a file manager to make the switch, try re-flashing your ROM with the apk changes instead.
Make a backup before doing it so you can restore all your settings if it doesn't work for some reason.
It works after I replaced it in my ROM zip
Sent from my SAMSUNG-SGH-I777 using xda premium
penguinlogik said:
It works after I replaced it in my ROM zip
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Did you have to re-flash? Just trying to make sure my instructions are correct.
Did you need to add both apk's as well?
No, I just added replaced the files in the Unnamed 1.1.0 full update zip, ran an update via CWM, with only the phone.apk and microphone works.
penguinlogik said:
No, I just added replaced the files in the Unnamed 1.1.0 full update zip, ran an update via CWM, with only the phone.apk and microphone works.
Click to expand...
Click to collapse
Ok, glad it works and the kinks are worked out thanks for you patience and tests.
Thats awesome news. Low mic has always been an issue for me. Just wondering if someone can create a flash able zip that automates everything, if possible.
Great work guys.
daraj said:
Thats awesome news. Low mic has always been an issue for me. Just wondering if someone can create a flash able zip that automates everything, if possible.
Great work guys.
Click to expand...
Click to collapse
IF I can get approval from Designgears to use some sources from his ROM I shouldn't have any issues putting this into a zip file for everyone. I've reached out to DG, just awaiting a response
Great keep us posted please. It will make a big difference to many people
Sent from my SAMSUNG-SGH-I777 using XDA App
crazyagg said:
IF I can get approval from Designgears to use some sources from his ROM I shouldn't have any issues putting this into a zip file for everyone. I've reached out to DG, just awaiting a response
Click to expand...
Click to collapse
Excellent! Been looking for something like this, because I also noticed that the volume was really horrible... Keep us posted on a zip file. Rather be "SAFER" than sorry with doing something that does it automagically for me
Knowing my patience, I'll probably manually do it once I get home from school... lol
SpectraDawn said:
Knowing my patience, I'll probably manually do it once I get home from school... lol
Click to expand...
Click to collapse
LOL! Me too! I all over this!
YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. WE ARE NOT RESPONSIBLE FOR YOUR DEVICE. FLASH AT YOUR OWN RISK.
This will enable Native Tether for Build 21.11.21. Shout out goes to @iKrYpToNiTe for his work with this.
Prerequisites:
Droid Maxx/Ultra Rooted w/WP off
METHOD 1: TWRP INSTALL
1) Download the package below labeled "21.11.21tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
METHOD 2: MANUAL INSTALL
1) Download the package below labeled "21.11.21tether".
2) Download root browser by Jrummy from the play store
3) Navigate to System/Priv-App and rename VZWEntitlementservice.apk to VzwEntitlementservice.apk.bak.
4) Navigate to System and rename the build.prop to build.prop.bak
5) Place the package on the root of your sd card and extract the build.prop file within the folder.
6) Navigate to system and Copy and paste the new file.
7) Set permissions for the file to
Owner: Read/Write
Group: Read
Others: Read
This should show (rw-r--r--)
8) Reboot. Verify tether works
9) Profit.
REVERTING
METHOD 1:
If installed in twrp, download the package below labeled 21.11.21tether_revert. Flash in Twrp, reboot, verify subscription check re-enabled.
METHOD 2:
If manually installed, simply delete the build.prop you installed, remove the .bak extension from the original build.prop, verify permissions, reboot.
there is nothing in the .zip folder?
Kickbut101 said:
there is nothing in the .zip folder?
Click to expand...
Click to collapse
Are you asking or stating? If you are stating, then you may have gotten a bad download. I just re-verified the download and all is well. The file is very small.
Works perfectly. Thanks!
After reboot, original build.prop is back and the vzw files dropped the .bak. I am rooted, but not unlocked so wp is on, and I guess native tether is not gonna work. Didn't try it before reboot though.
Sent from my XT1080 using XDA Free mobile app
socobandit said:
After reboot, original build.prop is back and the vzw files dropped the .bak. I am rooted, but not unlocked so wp is on, and I guess native tether is not gonna work. Didn't try it before reboot though.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Product of wp being on. You can try to open my build.prop and copy and paste the entire prop into your file effectively replacing the contents. See if that takes.
What is a native tether exploit used for?
Sent from my XT1080 using XDA Free mobile app
johnny567 said:
What is a native tether exploit used for?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
To enable native tether, obviously. Search is your friend.
---------- Post added at 06:04 PM ---------- Previous post was at 05:56 PM ----------
@Topsnake, is it possible to rig your previous MOD ([MOD][ROOT]Native Wireless Tether for build 19.6.3) for 4.4.4?
It appears that having a modded VZWEntitlementServices.apk which takes care of the native tether and only that is a cleaner solution than modifying the build.prop as the latter is referenced a lot by many processes which, consequently, could lead to far reaching side effects.
BTW, do you know if anyone tried your VZWEntitlementServices.apk on 4.4.4?
CrazyRussianXDA said:
To enable native tether, obviously. Search is your friend.
---------- Post added at 06:04 PM ---------- Previous post was at 05:56 PM ----------
@Topsnake, is it possible to rig your previous MOD ([MOD][ROOT]Native Wireless Tether for build 19.6.3) for 4.4.4?
It appears that having a modded VZWEntitlementServices.apk which takes care of the native tether and only that is a cleaner solution than modifying the build.prop as the latter is referenced a lot by many processes which, consequently, could lead to far reaching side effects.
BTW, do you know if anyone tried your VZWEntitlementServices.apk on 4.4.4?
Click to expand...
Click to collapse
Thought I replied to this.
The 19.5.3 would probably work for 4.4.4 but I haven't tried it.
The build.prop is a much cleaner install when done correctly.
Topsnake said:
Thought I replied to this.
The 19.5.3 would probably work for 4.4.4 but I haven't tried it.
The build.prop is a much cleaner install when done correctly.
Click to expand...
Click to collapse
@Topsnake can you please elaborate on the changes you made to the stock buiuld.prop file?
I know you've mentioned in another thread that your method and the one using EntitlementBypass-v1.2.apk (from Moto X forum) are using the same commends. Would I be correct assuming that you've:
1. Added net.tethering.noprovisioning=true
and
2. Changed ro.mot.tether_dun_required to 0
Are those are the only difference between your build.prop and the stock one?
The reason I ask, is that, as I said earlier in this thread, build.prop is pretty significant file (from what I understand) and sets a lot of variables and settings. I'm hesitant to modify it in fears that by enabling native tether other unwanted side effects would arise.
Thanks
CrazyRussianXDA said:
@Topsnake can you please elaborate on the changes you made to the stock buiuld.prop file?
I know you've mentioned in another thread that your method and the one using EntitlementBypass-v1.2.apk (from Moto X forum) are using the same commends. Would I be correct assuming that you've:
1. Added net.tethering.noprovisioning=true
and
2. Changed ro.mot.tether_dun_required to 0
Are those are the only difference between your build.prop and the stock one?
The reason I ask, is that, as I said earlier in this thread, build.prop is pretty significant file (from what I understand) and sets a lot of variables and settings. I'm hesitant to modify it in fears that by enabling native tether other unwanted side effects would arise.
Thanks
Click to expand...
Click to collapse
I can guarantee you that this mod will not give any effects other than enabling tether. 110% positive
Topsnake said:
I can guarantee you that this mod will not give any effects other than enabling tether. 110% positive
Click to expand...
Click to collapse
line 259 net.tethering.noprovisioning=true appears to be the only addition to the original build.prop
Should the result should be the same if we just edit the prop.buld right on the device and add that line?
Are you unlocked bl?
Topsnake said:
Are you unlocked bl?
Click to expand...
Click to collapse
yes
CrazyRussianXDA said:
yes
Click to expand...
Click to collapse
So then copy the contents of the build prop into yours or replace it all together. It takes of all about 3 seconds.
It will be the same.
Whelp that's it's for me @NWKENT @Jaocagomez @Caseyk621 @bigv5150 @rmjones2006 i'm done helping this community and dealing with all these people who feel like something is owed to them. It's been fun.
Topsnake, thank you! For all you have done in the past and now.
Sent from my XT1080 using XDA Premium 4 mobile app
rekids said:
Topsnake, thank you! For all you have done in the past and now.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I appreciate that buddy. Thanks.
CrazyRussianXDA said:
"I'm not required to disclose the details of any mod to you" - this might or might not be true as I'm not familiar with Open Source Licensing and you might be required to disclose. Regardless, you did not, that's part why you came across as not completely honest.
The fact that most developers (Jcase, Faux123, beaups, iKrYpToNiTe, just to name a few) DO disclose everything makes me thank that you might be required to do full disclosure.
"Either apply it, or don't." - I did not. I applied command provided by iKrYpToNiTe
Click to expand...
Click to collapse
If you are really that concerned about the build.prop being altered in a way that you feel the need to be worried, then simply compare your current build.prop to the modified one that topsnake has provided. It's that simple. No need to start arguments about what one person feels is better or safer or whatever else you think; I personally research anything that I do to my phone by tearing down apk's or batch files or whatever it might be that I'm applying to my phone to see what is being done. By doing this it also helps you learn how these exploits work and helps you learn more about your phone in general.
If you're not comfortable with changing files then don't do it. It's that simple.
Not calling any one particular person out in general, but there is so much of the same information continually being repeated that it is extremely frustrating. I'm to the point where I don't even try and help because I'm just repeating what I said a page or two back, or the post directly below.
Topsnake said:
Whelp that's it's for me @NWKENT @Jaocagomez @Caseyk621 @bigv5150 @rmjones2006 i'm done helping this community and dealing with all these people who feel like something is owed to them. It's been fun.
Click to expand...
Click to collapse
Please don't leave us! We appreciate everything you do!
Hello everyone.
The main thread for CM12 was closed and so I will be posting the modded mixer_paths.xml here. It will boost headphone volume and speaker volume. Be careful.
UNZIP, the xml is inside. XDA won't let me upload straight xml files. Dum.
Just drop it in /system/etc and fix permissions. Done!
Remember to make a backup of your original.
Thank you so much for this. Works great
Sent from my LG-ls990 using XDA Free mobile app
Thanks for this. I tried it out and had distortion on music and video. Seems to be just a tad bit to loud. I ended up reverting back to stock.
I was just getting on here to ask for this. And here it is. Good work my friend.
Great Develoment
Not a total newb, but where do I need to go to fix permissions after pasting the file in system/etc?
It depends on your file browser. I use root explorer, just long press the file and it will be an option.
Sent from my LGLS990 using XDA Free mobile app
I'm using root browser, and I see options for permissions, but it's to change them for owner, guest, and others. Not sure what they are supposed to be set at, and whether the setting should be for the file I'm moving, the etc folder, or the system folder. Messed around with them but the volume isn't changing.
clark44 said:
Hello everyone.
The main thread for CM12 was closed and so I will be posting the modded mixer_paths.xml here. It will boost headphone volume and speaker volume. Be careful.
UNZIP, the xml is inside. XDA won't let me upload straight xml files. Dum.
Just drop it in /system/etc and fix permissions. Done!
Remember to make a backup of your original.
Click to expand...
Click to collapse
awesome , thanks
Please forgive my noob/ingorance here...but I need some help.
I use ES Explorer (with root enabled) and I have no problem unzipping, grabbing the xml file & pasting it in /system/etc file.
My question is, how exactly do I then 'fix permissions' ?
Thanks in advance.
Please disregard previous post, got it & it's working great! Thank You
clark44 said:
Hello everyone.
The main thread for CM12 was closed and so I will be posting the modded mixer_paths.xml here. It will boost headphone volume and speaker volume. Be careful.
UNZIP, the xml is inside. XDA won't let me upload straight xml files. Dum.
Just drop it in /system/etc and fix permissions. Done!
Remember to make a backup of your original.
Click to expand...
Click to collapse
I have been looking for this! Thank you. And now for the very "noob" question . . . what should the permissions be set to? I am using ES File Explorer. TIA
Will this work with any cm12 variant? Like candy 5...
I did this exactly and changed the permissions and I have no sound whatsoever. I am on a sprint lg g3. Please help.
wojo797 said:
Will this work with any cm12 variant? Like candy 5...
Click to expand...
Click to collapse
Should.
jreink01 said:
I did this exactly and changed the permissions and I have no sound whatsoever. I am on a sprint lg g3. Please help.
Click to expand...
Click to collapse
Did you reboot?
jreink01 said:
I did this exactly and changed the permissions and I have no sound whatsoever. I am on a sprint lg g3. Please help.
Click to expand...
Click to collapse
What file explorer are you using? I asked a question here days ago and - while trying to figure this out for myself - ended up in one of my "efforts" with your same situation. I finally got this to work and may be able to help you.
I redownloaded the file and installed and now works great, must have been a bad download.
question
whoppe862005 said:
Thanks for this. I tried it out and had distortion on music and video. Seems to be just a tad bit to loud. I ended up reverting back to stock.
Click to expand...
Click to collapse
after I extract it on my computer how and where do I put it in system /etc I don't understand I looked in my file ex and cannot find file "system" at all where is it at? please gimmie a hand if you know please... thank you .Jake
jfive83 said:
after I extract it on my computer how and where do I put it in system /etc I don't understand I looked in my file ex and cannot find file "system" at all where is it at? please gimmie a hand if you know please... thank you .Jake
Click to expand...
Click to collapse
Download a root browser. I use fx file Explorer. Click on the system partition and grant it root permissions open up the etc folder and overwrite the mixer_path.xml in there. After that long click on the mixer_path.xml and click details, then click where the permissions are and set them to 0644 then Reboot. Make sure to set the permissions correctly otherwise you won't have sound or end up in a bootloop. Make a nandroid before you do this so incase something happens you can revert back to that.
Edit: download it on your phone and extract it and follow the steps above. No need to do it through a computer. It can all be done from your phone.
Sounds twice as loud, thank you!
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Masterjuggler said:
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Click to expand...
Click to collapse
Did the logcat give any pointers as to why it might have crashed?
It's a camera app, for MiFavor, and only for MiFavor. It's probably depending on something else from the stock ROM, and that's why it's crashing in CM.
I like this idea. I might even look into modifying the app itself, to see if we can get it working outside of MiFavor.
I don't think I worded it clearly enough, the first time I converted it to a user app and back to system, it was still in the stock ROM. Something about the conversion screwed things up. I'll have to flash stock again at some point and grab logcats while it's working and after I screw it up.
In the meantime, I attached a logcat for everything containing "camera" after it was converted to a system app in cm13. It's kind of harsh to look at it in pure text format, but I used the matlog app with its color coding to record it.
To be honest, I'm not quite sure what I'm looking at with this, or if I went about this in the right way.
EDIT: I have no idea why the logcat is not attaching correctly. I'll need to find some other way of doing it.
It works fine under CM according to a friend. You just need the libs to go along with the app.
Here is the WHOLE folder of ZTE camera, he just put this inside the /system/priv-app/ folder and apparently it's working just fine after a reboot.
https://my.mixtape.moe/znyabg.7z
Remember to press thanks and buy me a beer.
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Was it a deodexed ROM? Might need to try it with the odex files? When I check /system/priv-app/ZTE_Camera, there's also an "oat" folder with odex files since this hasn't been deodexed...
Or maybe SuperR's kitchen was trying to automatically deodex while you were extracting.
To be honest, I never understood odex, just throwing ideas out at this point.
Masterjuggler said:
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Click to expand...
Click to collapse
I'm sure it works, friend confirmed it works on CM13 and I'm using it on BrokenOS. To clear it up.
It should be /system/priv_app/ZTE_Camera. And inside that folder should be the apk along with the lib. If you just extract the zip I gave you into priv_app it should just work. I have no idea why it doesn't work for you. Everything about the camera works. Slomo, video h265, the works.
You can try making a backup of the stock camera app using titanium backup then install it on your phone after flashing CyanogenMod. What I would do is flash zad miix then back up the stock camera app with titanium backup. Then transfer the back up to your PC. Then flash CyanogenMod and reinstall the camera app with titanium backup.
as already I will have this phone I start doing this mods
if anyone can search the file this and tell me if an entry is interesting?
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
NadavCE said:
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
Click to expand...
Click to collapse
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
lian00 said:
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
Click to expand...
Click to collapse
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
Used SuperSU 2.79SR3.
I can confirm using the files provided works. I have the stock MM camera working with all of it's shooting modes !
Any body have the files in a .zip they can upload? I have no computer access and the few apps I tried on my phone seem to corrupt the files.
First app I tried extracted the 7zip file just fine.
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Erahgon said:
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Click to expand...
Click to collapse
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
NadavCE said:
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
Click to expand...
Click to collapse
Maybe the app permissions are wrong?
Erahgon said:
Maybe the app permissions are wrong?
Click to expand...
Click to collapse
Should I give it full permissions then?
---------------------------------------------------------------------------------------------------------------------------
Update: After giving everything (ZTE_Camera folder, the APK, the lib folder, the arm folder, and all the libs) full permissions, the app works. However resolution is limited to 8Mp 4:3 (3200 x 2400). Can anyone else confirm this?
Hey everyone, so i never really post mods or anything, and I'm not sure if this truly constitutes a mod, because it's just a simple copy paste job, but here are all of the files to copy to your V20 in order to have a silent camera and video camera.
**MUST BE ROOTED**
Every noise that's associated with the camera apk will be gone with no flashing of any kind! All you're doing is simply replacing all of the files on your device with the ones in the attached zip file! Your camera will now be completely silent without having to use a modded camera apk or flashing any sort of files in twrp.
(New Method provided by stangdriver. can flash his file Silent_Camera.zip in twrp if you'd rather flash than manually copy/paste!)
Instructions:
1.) Download the attached zip file
2.) Extract and copy all 15 files to system/media/audio/ui. Make sure permissions are set to rw-r-r correctly
3.) Reboot
Alternate Instructions (thanks to stangdriver!)
1.) download Silent_Camera.zip
2.) Flash in TWRP
3.) Reboot to system
done!
Now you've got a completely silent V20 camera! Instructions 1:http://cloud.tapatalk.com/s/593c8892b4fad/V20SilentCameraFiles.zip
Instructions 2:
http://cloud.tapatalk.com/s/593e74f74646c/Silent_Camera.zip
Sent from my LG-US996 using Tapatalk
Not sure if you or maybe users viewing this thread are interested, but I made a zip installer that replaces the files and sets permissions by just flashing in recovery.
These are not my files, just used the donwload from the OP and made a flashable zip.
So users can either use the instructions from above or flash the attachment from below.
If you do the manual way as posted above, make sure and set permissions for the new files to 644 (rw-r--r--)
Good luck and enjoy the silent camera!
good tip, stang! I'll post your file in the op as well!
Sent from my LG-US996 using Tapatalk
so.... anyone try it out? lol
Sent from my LG-US996 using Tapatalk
jayochs said:
so.... anyone try it out? lol
Sent from my LG-US996 using Tapatalk
Click to expand...
Click to collapse
That's right. I am waitng for someone to be first and test it out. Im not good with that and would be not possible to fix it.
netgar said:
That's right. I am waitng for someone to be first and test it out. Im not good with that and would be not possible to fix it.
Click to expand...
Click to collapse
jayochs said:
so.... anyone try it out? lol
Sent from my LG-US996 using Tapatalk
Click to expand...
Click to collapse
Silent zip flashed fine for me, works great. VS995 running latest build of WETA.
Sent from my VS995 using XDA-Developers Legacy app
great to hear!
Sent from my LG-US996 using Tapatalk
It works too in a H990ds. Used the instructions #1
Used Stang's zip file.
Working flawlessly in H990ds.
Thank you.
Zip works great on my h910. Thanks for this.
Mod works great!
Do you know if there is a way to keep music playing while using camera app? (Like Google Camera)
Thank you very much
This also, works for the LG V30. Thanks.
Delete
Works well. Instead of flashing zip, I extact into the ui folder and overwrite all the files. Make copies of original if you want to backup.
Hello what root browser do you use ? i have solid explorer and i have issues
Hello what root browser do you use ? i have solid explorer and i have issues settings the permits i want change the power on, shut down sounds but the solid explorer is not working even with root allowed, so maybe is just my explorer ? or how i set the chmod permission?
stangdriver44 said:
Not sure if you or maybe users viewing this thread are interested, but I made a zip installer that replaces the files and sets permissions by just flashing in recovery.
These are not my files, just used the donwload from the OP and made a flashable zip.
So users can either use the instructions from above or flash the attachment from below.
If you do the manual way as posted above, make sure and set permissions for the new files to 644 (rw-r--r--)
Good luck and enjoy the silent camera!
Click to expand...
Click to collapse