Stock ROM has problem with bluetooth aptx codec. If bluetooth device supports both, aptx and aac, than aac preffered.
Solvetion is to disable aac codec for bluetooth connections in build.prop
If you have root, just add string to build.prop:
persist.bt.a2dp.aac_disable=true
Don't forget to set permissions to 755.
Than reboot.
Another not tested variant:
change persist.vendor.btstack.a2dp_offload_cap=sbc-aptx-aptxhd-aac
to persist.vendor.btstack.a2dp_offload_cap=sbc-aac-aptx-aptxhd
In this variant aac stay enabled
Hey! Could you explain it very simply? I have root and BuildProp Editor, but I have never used it, I do not have the lines you typed and I do not understand what is this 755?
figer said:
Hey! Could you explain it very simply? I have root and BuildProp Editor, but I have never used it, I do not have the lines you typed and I do not understand what is this 755?
Click to expand...
Click to collapse
Use buildprop editor, you should add if it is not there already and set permissio to rw- r-- r-- . Es file explorer has built in buildprop editor and ability to set required system files permission, or you can use any other app with similar function. Please find attachment to get better idea.
changed it and saved, but after restart buildprop file is as before edition.
Any idea?
I did this , it is not working unfortunately
figer said:
changed it and saved, but after restart buildprop file is as before edition.
Any idea?
Click to expand...
Click to collapse
Bronnel said:
I did this , it is not working unfortunately
Click to expand...
Click to collapse
You need to check that changes are saved in build.prop
And check the permissions of file, they should be 755
figer said:
Hey! Could you explain it very simply? I have root and BuildProp Editor, but I have never used it, I do not have the lines you typed and I do not understand what is this 755?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
No need to use permissions. Just add the line, save and reboot.
Sent from my LG-H932 using XDA Labs
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
Aptahar said:
Stock ROM has problem with bluetooth aptx codec. If bluetooth device supports both, aptx and aac, than aac preffered.
Solvetion is to disable aac codec for bluetooth connections in build.prop
If you have root, just add string to build.prop:
persist.bt.a2dp.aac_disable=true
Don't forget to set permissions to 755.
Than reboot.
Click to expand...
Click to collapse
Might just be better to post this link,
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
tell people to copy
persist.bt.a2dp.aac_disable=true
And add it in the app. Save and reboot.
Sent from my LG-H932 using XDA Labs
Aptahar said:
You need to check that changes are saved in build.prop
And check the permissions of file, they should be 755
Click to expand...
Click to collapse
I change the 755, adds a row. I save everything.
Validating - for sure by opening the file again. A new row is added. The file has permission for execute - it is 755.
I restart the phone.
After reboot, the BuildProp file is 644 again, and the added row in it is not there !!!
As if the system was restoring the file before the changes during the system reboot.
I have root and changes I made in BuildProp Editor and a normal text editor, changing permissions to the file using Root Browser.
Each time after reboot the changes are reversed.
figer said:
I change to 755, adds a line "persist.bt.a2dp.aac_disable" with value=true . I save everything.
I check for certainty by opening the file. A new row is added. The file has permission for execute - it is 755.
I restart the phone.
After reboot, the BuildProp file is 644 again, and the added row in it is not there !!!
As if the system was restoring the file before the changes during the system reboot.
I have root and changes I made in BuildProp Editor and a normal text editor, changing permissions to the file using Root Browser.
Each time after reboot the changes are reversed.
Click to expand...
Click to collapse
Try to use Root Explorer, and when he asks to mount system as R/W, bump Yes.)
Root Explorer has built in text editor and permission changer.
Aptahar said:
You need to check that changes are saved in build.prop
And check the permissions of file, they should be 755
Click to expand...
Click to collapse
I already did this, still not working.
BROKEN1981 said:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
No need to use permissions. Just add the line, save and reboot.
Sent from my LG-H932 using XDA Labs
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
Might just be better to post this link,
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
tell people to copy
persist.bt.a2dp.aac_disable=true
And add it in the app. Save and reboot.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I tried this, it is not working, I even tried "persist.vendor.bt.a2dp.aac_disable=true" the same
Bronnel said:
I already did this, still not working.
I tried this, it is not working, I even tried "persist.vendor.bt.a2dp.aac_disable=true" the same
Click to expand...
Click to collapse
give me your build.prop
Aptahar said:
Try to use Root Explorer, and when he asks to mount system as R/W, bump Yes.)
Root Explorer has built in text editor and permission changer.
Click to expand...
Click to collapse
I made changes of permissions by Root Explorer - and then add the line by text editor build there - its wont save changes.
I copied buildprop file to sd card, edited, copied to system directory, changed permissions to 755, restarted and... file after restart is 644, and added line is gone. Recovered by something to default state
figer said:
I made changes of permissions by Root Explorer - and then add the line by text editor build there - its wont save changes.
I copied buildprop file to sd card, edited, copied to system directory, changed permissions to 755, restarted and... file after restart is 644, and added line is gone. Recovered by something to default state
Click to expand...
Click to collapse
That strange. What does Google says on it?
Aptahar said:
Try to use Root Explorer, and when he asks to mount system as R/W, bump Yes.)
Root Explorer has built in text editor and permission changer.
Click to expand...
Click to collapse
Yes, Root Explorer is the best.
I've used it for years.
Aptahar said:
give me your build.prop
Click to expand...
Click to collapse
sorry for my late reply , here is my unmodified build.prop
Bronnel said:
sorry for my late reply , here is my unmodified build.prop
Click to expand...
Click to collapse
Can you give cust.prop file from OP directory
Aptahar said:
Can you give cust.prop file from OP directory
Click to expand...
Click to collapse
here it is
Bronnel said:
here it is
Click to expand...
Click to collapse
Your files build.prop ans cust.prop doesn't contain any lines about aptx.
This codec supports on your device?
This trick with disabling AAC codec checked only on ROM for European devices
Aptahar said:
Your files build.prop ans cust.prop doesn't contain any lines about aptx.
This codec supports on your device?
This trick with disabling AAC codec checked only on ROM for European devices
Click to expand...
Click to collapse
Yes I definitely have aptx , I can select it in developer options
Related
I tried replace the Poweron.wav in sys/etc
but it said copy failed.
I'm on the latest siyah kernel
wanewon said:
I tried replace the Poweron.wav in sys/etc
but it said copy failed.
I'm on the latest siyah kernel
Click to expand...
Click to collapse
take it you have set correct permissions and changed ownership of file ??
and the file is poweron.ogg not wav
DJBoxer said:
take it you have set correct permissions and changed ownership of file ??
and the file is poweron.ogg not wav
Click to expand...
Click to collapse
how do I do that? I just watched a youtube video on how to change the boot sound. and I failed..: (
and I downloaded the original S2 boot animation and sound from this thread:
http://forum.xda-developers.com/showpost.php?p=24910851&postcount=22359
and it's in wave format..
wanewon said:
how do I do that? I just watched a youtube video on how to change the boot sound. and I failed..: (
and I downloaded the original S2 boot animation and sound from this thread:
http://forum.xda-developers.com/showpost.php?p=24910851&postcount=22359
and it's in wave format..
Click to expand...
Click to collapse
yes most prob wav not used cm9 myself but on most sammy ones it ogg but anyways try this navigate to system/etc using root explorer make sure its set to RW then copy/move/paste file into location then change owner to root/root and set permissions to RW-R-R .
hopefully this will work for you if not trying renaming file to ogg
DJBoxer said:
yes most prob wav not used cm9 myself but on most sammy ones it ogg but anyways try this navigate to system/etc using root explorer make sure its set to RW then copy/move/paste file into location then change owner to root/root and set permissions to RW-R-R .
hopefully this will work for you if not trying renaming file to ogg
Click to expand...
Click to collapse
ahh. I got the problem fixed. I didn't enable root access and system files as writable. now it worked.
I replaced the poweron.wav successfully.
but,
the sound doesnt play during the boot animation...-__-
wanewon said:
I replaced the poweron.wav successfully.
but,
the sound doesnt play during the boot animation...-__-
Click to expand...
Click to collapse
yes but do all the steps i stated even tho you added the file dosent mean its gonna work set the permissions correctly etc and also i mentioned to change file from wav to ogg as a last resort but hmmm i swear that it is ogg for power on but not sure as i find it annoying upon boot lol
DJBoxer said:
yes but do all the steps i stated even tho you added the file dosent mean its gonna work set the permissions correctly etc and also i mentioned to change file from wav to ogg as a last resort but hmmm i swear that it is ogg for power on but not sure as i find it annoying upon boot lol
Click to expand...
Click to collapse
Root explorer as in the one thats $3.99 at the playstore??
You can't just rename the file from wav to ogg. They are different file formats. You need to convert it.
ctomgee said:
You can't just rename the file from wav to ogg. They are different file formats. You need to convert it.
Click to expand...
Click to collapse
so it is really ogg?
the default one that was already in the folder is in wav
wanewon said:
so it is really ogg?
the default one that was already in the folder is in wav
Click to expand...
Click to collapse
Depends. Apparently it should be wav for GB, ogg for ICS.
well I'm using resurrection ICS remix 2.0 if that helps.
and waiting for the root explorer reply.
wanewon said:
well I'm using resurrection ICS remix 2.0 if that helps.
and waiting for the root explorer reply.
Click to expand...
Click to collapse
So... Given the name of the ROM, surely you can determine if it's GB or ICS... Yes?
You can use any file explorer that gives root access. Root Explorer is just one of them. ES File Explorer is another.
However, I don't think Resurrection Remix supports boot sounds at all, but I'm not positive about that. Someone who uses that ROM will have to answer that.
ctomgee said:
So... Given the name of the ROM, surely you can determine if it's GB or ICS... Yes?
You can use any file explorer that gives root access. Root Explorer is just one of them. ES File Explorer is another.
However, I don't think Resurrection Remix supports boot sounds at all, but I'm not positive about that. Someone who uses that ROM will have to answer that.
Click to expand...
Click to collapse
downloaded a Poweron.ogg as well. and I just figured out the permission management thing and I turned on all the permissions. still no luck. As for the ownership thing that the other poster was talking about. I dont know how to do in es explorer.
anyway, I tried both ogg and wav. maybe you could be right that ICS remix doesnt support boot sounds
Code:
First of all, you like it or dont like it, feel free to ask for changes , but not for ETA.
Don´t post it elsewhere, without permission!
Code:
Your bootanimation is might be in /system/customize/resource
Download the bootanimation
Push it with ADB to /system/customize/resource or use file manager app to copy
# use filemanager for paste©
# set the right permissions (644 rw r r )
I am not responsible for anything, except my own phone
It is an edit of the stock animation, same framerate and resolution
Thanks for your effort!
Did anyone test it?
Did anyone test it?
Click to expand...
Click to collapse
Yes, I run it on my own device, if it doesnt work ... there will be set wrong permissions :angel:
Notechis said:
Yes, I run it on my own device, if it doesnt work ... there will be set wrong permissions :angel:
Click to expand...
Click to collapse
sorry if noob question but how to set permission? I really want to try this bootanimation.
Thank before
You can set the permissions using a file manager, I´ve tested venom explorer a few seconds ago, but I cannot find the option .
You can try solid explorer ...
Notechis said:
You can set the permissions using a file manager, I´ve tested venom explorer a few seconds ago, but I cannot find the option .
You can try solid explorer ...
Click to expand...
Click to collapse
Where do I paste the files?
Sent from my HTC One X+ using xda premium
Post 1 is updated with path
Notechis said:
Post 1 is updated with path
Click to expand...
Click to collapse
I paste it in the correct path and set permissions to 644 rw-r-r and its not working for me
Sent from my HTC One X+ using xda premium
On some ROMs (e.g. InsertCoin) you have to rename the two files to 'hTC_bootup_one.zip' and 'hTC_downanimation.zip'. These are the names of the animations in the stock ROM.
Correct
THX for the addition
Just for infos sake,,,,,,,,,
I had to rename mine to "ATT_bootanimation.zip" and "ATT_dow,,,,,,,,
That's what the originals were named.
Thanks for the hard work.
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
Hello all,
since we now have root and access to root files.. is there any way to remove the provisioning on the 'hot spot' app so we can use native tethering? I know this was done on the G2. and was hoping we could make something like that work on the V10.
Thanks!
Have you tried backing up the files and using the G2 files? It is possible they will work.
Just use FoxFi
Use file explorer or something and just delete it and reboot.
Hey i have the modded v10 native hotspot provisioning
superdallas said:
Hey i have the modded v10 native hotspot provisioning
Click to expand...
Click to collapse
Already using FoxFi (because I have to)... don't like the VPN stuff. rather go native.
Will you provide a link and some directions? or PM me?
Thanks!
Pm'ed
here is the one from the G4 which seems to work
I used Root Explorer
Navigate to /System/App/HotspotProvision
Rename HotspotProvision.apk to HotspotProvision.bak
Paste/move the downloaded modified HotspotProvisionVZWV10.apk file to /system/app/HotspotProvision
Long-press on the file > properties to change the permissions
Change the permissions to 644 (rw-, r--, r--)
Reboot
There is already a thread for this.
http://forum.xda-developers.com/verizon-g4/general/how-to-enable-native-hotspot-unlimited-t3166435
carycooke said:
here is the one from the G4 which seems to work
I used Root Explorer
Navigate to /System/App/HotspotProvision
Rename HotspotProvision.apk to HotspotProvision.bak
Paste/move the downloaded modified HotspotProvisionVZWV10.apk file to /system/app/HotspotProvision
Long-press on the file > properties to change the permissions
Change the permissions to 644 (rw-, r--, r--)
Reboot
Click to expand...
Click to collapse
Thanks man. Got my tethering back!
Sent from my VS990 using Tapatalk
zatanas33 said:
There is already a thread for this.
http://forum.xda-developers.com/verizon-g4/general/how-to-enable-native-hotspot-unlimited-t3166435
Click to expand...
Click to collapse
I believe I stated this in my original post
Sent from my VS990 using Tapatalk
is it possible to change dpi in miui without having weird icons .
Camlin3 said:
is it possible to change dpi in miui without having weird icons .
Click to expand...
Click to collapse
Use any file explorer like Es explorer etc.
Go to /system/build.prop
Add this line in the build.prop
ro.sf.lcd_density=the value you want.
Save the file and reboot
gulshanstrider said:
Use any file explorer like Es explorer etc.
Go to /system/build.prop
Add this line in the build.prop
ro.sf.lcd_density=the value you want.
Save the file and reboot
Click to expand...
Click to collapse
Done already cause icon got distorted like a small square protude seperate from whole icon.
Use easy dpi changer from playstore. Then add/modify ro.sf.lcd_density=x in build.prop in case the dpi change messes up icons and images in apps.
adizz4 said:
Use easy dpi changer from playstore. Then add/modify ro.sf.lcd_density=x in build.prop in case the dpi change messes up icons and images in apps.
Click to expand...
Click to collapse
Ok i will try again,but i ran into other problem in nougat roms ,i cant edit any txt file via es file explorer integrated text editor,pls have a look ,is it app bug ? Sorry screenshot not uploading .it says error occured while saving file and create a tmp file with same name in directory.
Camlin3 said:
Ok i will try again,but i ran into other problem in nougat roms ,i cant edit any txt file via es file explorer integrated text editor,pls have a look ,is it app bug ? Sorry screenshot not uploading .it says error occured while saving file and create a tmp file with same name in directory.
Click to expand...
Click to collapse
Flash latest supersu and try, someone else had the same problem.
I use root explorer and sr1 2.79 ssu and everything works fine.
(assuming you're trying to edit build.prop)
Use imgur or some other image host to share images, xda upload seems to be broken rn.
adizz4 said:
Flash latest supersu and try, someone else had the same problem.
I use root explorer and sr1 2.79 ssu and everything works fine.
(assuming you're trying to edit build.prop)
Use imgur or some other image host to share images, xda upload seems to be broken rn.
Click to expand...
Click to collapse
No ,its in nougat ,even a txt file in sdcard cant be edited with es file explorer.in mm ,it works fine.
Camlin3 said:
No ,its in nougat ,even a txt file in sdcard cant be edited with es file explorer.in mm ,it works fine.
Click to expand...
Click to collapse
That's really weird.
You could try a different app I guess.
adizz4 said:
That's really weird.
You could try a different app I guess.
Click to expand...
Click to collapse
Ya i know ,it seems like app bug,i used fx file explorer.
Camlin3 said:
No ,its in nougat ,even a txt file in sdcard cant be edited with es file explorer.in mm ,it works fine.
Click to expand...
Click to collapse
Use Kernel Auditor or Build prop editor app
gulshanstrider said:
Use Kernel Auditor or Build prop editor app
Click to expand...
Click to collapse
I am only enquiring abt es file explorer ,other goes well
Thanks for reply
here's a full youtube tutorial that doesn't affect icons
https://www.youtube.com/watch?v=btabIccFrHY