Related
HELP!!
When i was running the RGUI ROM (JB) there was a fix zip to use in CWM to fix the 'Media' drain in the battery.
This worked wonders! So i just tried to flash it to my device again, except now i'm running the 'Anonorom' ROM.
It worked. Or flashed without error anyway.
The problem now is that since the reboot, the 'Fonts' have failed to be picked by my apps.
This is most noticibly with UCCW. The widget i created for the homescreen uses about 5 different fonts and its defaulted to 1 default font.
When i open the widget to change the fonts back, it tells me theres only 1 font available; "Default" and that if i want to add more then to put them in 'sd:\fonts'.
I've gone back to my file manager and checked this location and there are LOADS of fonts in there still, so its not as if they've been deleted.
Clearly this is the work of the fix_mediaDrain.zip, which i now obviously regret flashing. And WHO KNOWS what other errors i will now encounter!
So my question is, other than reflashing the ROM (which would be a pain because i've also flashed the JKay framework and other things like that, and amanaged to get the phone to my liking) does ANYONE know of a kind of UNDO fix for this fix_mediaDrain.zip that i can flash.
Obviously i dont even know if it exists,im just praying, but if anyone has any ideas i would greatly appriociate it.
I'm guessing the media scanner has been stopped, or a .nomedia file has been placed in the fonts folder.
So first check if there is a file called .nomedia in this folder and if so, delete it and reboot.
If not, then get rescan media root from play and try to enable media scanner and reboot.
Report back please
slaphead20 said:
first check if there is a file called .nomedia in this folder and if so, delete it and reboot.
If not, then get rescan media root from play and try to enable media scanner and reboot.
Report back please
Click to expand...
Click to collapse
Firstly, thanks for your reply..
I've checked the location for a '.nomedia' file and no it does not exist.
I even checked 'Root Explorer' incase the file was hiddenin my regular file manager. Still nothing.
I downloaded the 'Rescan Media Root' app, which looked successful, but didnt fix my issue.
I tried a different app called 'media Rescan Lite', but that too did not fix the issue.
It's not looking good for me is it?
well the obvious path note really is to post in the Rom thread/contact dev and find out what the file does and how it can be reverted, let me know if you don't have enough posts and I will post link to your dilemma for you
slaphead20 said:
well the obvious path note really is to post in the Rom thread/contact dev and find out what the file does and how it can be reverted
Click to expand...
Click to collapse
I have contacted the developer of this fix to ask what it does exactly and if theres any way to undo the fix.
I have also added a post to the thread where this fix was first suggested to me in the past, incase anyone there might be able to shed some light on it..
I will post my findings once i ear back from anyone incase anyone else ever has this problem...
Thanks again.
SOLVED!!
I have managed to fix this problem!
This is going to sound RIDICULOUS but.....
I renamed the 'Fonts' folder on my sdcard slightly.
I say 'renamed', but all i did was make the filename all lowercase, creating "fonts" instead of "Fonts".
Then, IMMEDIATLY, the fonts on my widget wer back to normal..!
How very odd that this was changed by the 'fix_mediaDrain.zip' throgh CWM + reboot.
AndyGalaxy said:
I have managed to fix this problem!
This is going to sound RIDICULOUS but.....
I renamed the 'Fonts' folder on my sdcard slightly.
I say 'renamed', but all i did was make the filename all lowercase, creating "fonts" instead of "Fonts".
Then, IMMEDIATLY, the fonts on my widget wer back to normal..!
How very odd that this was changed by the 'fix_mediaDrain.zip' throgh CWM + reboot.
Click to expand...
Click to collapse
well solved :thumbup:
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.
Hi guys,
Very people are having wifi problems in the mm based roms, i was having too until i tried this:
Copied the file: WCNSS_qcom_cfg.ini from the original oxygen or another oxygen based rom like skydragon or oxyslim, and then pasted it in the same directory in the mm based rom (in my case was exodus).
The file is in partition0/system/etc/wifi.
I hope that i can help some other of you that are having this problem.
If i helped then press thanks,
TS
Tierri said:
Hi guys,
Very people are having wifi problems in the mm based roms, i was having too until i tried this:
Copied the file: WCNSS_qcom_cfg.ini from the original oxygen or another oxygen based rom like skydragon or oxyslim, and then pasted it in the same directory in the mm based rom (in my case was exodus).
The file is in partition0/system/etc/wifi.
I hope that i can help some other of you that are having this problem.
If i helped then press thanks,
TS
Click to expand...
Click to collapse
what problems are you referring to?
Dinjesk said:
what problems are you referring to?
Click to expand...
Click to collapse
i think he's talking about Wi-Fi drops / disconnection. But seems to be a problem that touched some users and not others.
Could you maybe provide the file you're refering too - would be helpful I guess.
giving it a try.. when you copy it from oxygen os, paste it in downloads otherwise the system will wipe it out if its just under internal. I turned off wifi and deleted the old WCNSS_qcom_cfg.ini and then pasted in the copy from downolads and rebooted making sure the pasted one stuck and not rewritten. Using resurrection remix so I will update if it works
casual_kikoo said:
i think he's talking about Wi-Fi drops / disconnection. But seems to be a problem that touched some users and not others.
Click to expand...
Click to collapse
Yes i AM talking about WiFi drops and low speed downloads.
will this fix the bad mobile strength service or just wifi?
Equals_Android said:
will this fix the bad mobile strength service or just wifi?
Click to expand...
Click to collapse
just dropped wifi
Can someone please upload the specified file and attach it to OP...?
will help me from downloading the whole Oxygen OS
Thanks in advance!
okay.. this worked for me.. my wifi speed is back to normal.. no more sluggishness
daninantro said:
okay.. this worked for me.. my wifi speed is back to normal.. no more sluggishness
Click to expand...
Click to collapse
Can you please upload this file ?
srvoleti said:
Can you please upload this file ?
Click to expand...
Click to collapse
Prasad98 said:
Can someone please upload the specified file and attach it to OP...?
will help me from downloading the whole Oxygen OS
Thanks in advance!
Click to expand...
Click to collapse
Attached, unzip it and paste the file in the mentioned path as in OP.. make sure the permissions are rwx r-x r-x
also enable dhcp client from lollipop in developers settings.
Sorry guys i have deleted the file, it was a mistake. Now i AM on exodus and dont want to go back to oxygen just to pick the file.
Anyways @daninantro thanks for sharing the file with the guys.
My /system folder is empty.. :/
I am using ES file explorer
FAB1150 said:
My /system folder is empty.. :/
I am using ES file explorer
Click to expand...
Click to collapse
enable root explorer in es file explorer and give superuser permissions
daninantro said:
enable root explorer in es file explorer and give superuser permissions
Click to expand...
Click to collapse
I use root browser. And it only ask for permissions when i go delete the old file.
If any of you interested in the changes about this ini file over the time check this out:
https://github.com/CyanogenMod/andr...682640955ae42055dc701/wifi/WCNSS_qcom_cfg.ini
same here.it worked for me too. my wifi speed is pretty good now.
Trying this right now, let's see what it does to my ever dropping WiFi in CM based roms.
Made a flashable zip for this, credited Tierri in the script
https://www.androidfilehost.com/?fid=24459283995305319
EDIT:
Just noticed I didn't set permissions in the script, need someone to confirm the format in numbers for this, check this line?
set_perm(0777, 0644, 0644, "/system/etc/wifi/WCNSS_qcom_cfg");
Also noticed something else which makes me think this fix might not be what you think it is, this file already exists in the following folder:
/system/etc/firmware/wlan/qca_cld/WCNSS_qcom_cfg.ini
I think this is the method CM uses to add configs for individual devices, since they have to support multiple ones.
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?
Hi, I had written bad command in ADB and almost all in this folder (/odm/etc/camera/) is deleted.
Can somebody pls send me this folder as ZIP? I use OpenKirin's AOSP Treble Oreo but it's not importnant. I think that the folder is same for all version of EMUI/Android.
Please, please, please, without it I can't capture any photo.
Problem is solved
StromekCZ said:
Hi, I had written bad command in ADB and almost all in this folder (/odm/etc/camera/) is deleted.
Can somebody pls send me this folder as ZIP? I use OpenKirin's AOSP Treble Oreo but it's not importnant. I think that the folder is same for all version of EMUI/Android.
Please, please, please, without it I can't capture any photo.
Click to expand...
Click to collapse
Don't send me anything. I just change permission (using chmod) and everything is back. :laugh:
How did you that ? more in detail please, could be usefull. Root needed I think ?
sonneper said:
How did you that ? more in detail please, could be usefull. Root needed I think ?
Click to expand...
Click to collapse
OK I will try to explain this situation but my English is slightly bad. In a nutshell I had bought used Honor 9 with bad microphone (probably broken flex cable, idk) and I was wondering, how to fix it. I found on Google Play app 'Root Volume Mixer', but it's not working. After searching some information about it I found out, that in "/odm/etc/" folder are some configuration files (.xml, .conf). In this folder you can change a lot of things (e.g. boost up audio jack sound, turn off one of the microphones,...). I changed here microphone intensity and solved my problem.
This Thread is about that I had editted some camera '.xml' files and I had set bad permission (by mistake I had written bad command and had changed permission for whole folder), therefore I didn't see a lot of files in root browser. Today I found out, that all files&folders are still in folder "/odm/etc/camera/". I simply set same permission as before (using chmod calculator, ADB shell and SU) and problem is solved.
thanks !