Related
The solution: http://forum.xda-developers.com/showpost.php?p=13982398&postcount=14
I'm trying to fix the bug that when using normal stereo headphones (without mic) or a 3.5mm jack -> 2xrca cable is used, the internal mic is disabled.
I've gotten so far that I have modified rpc_server_handset.c to set value of /sys/class/switch/h2w/state to 2 when headphones are inserted.
Now logcat shows:
V/HeadsetObserver( 148): Intent.ACTION_HEADSET_PLUG: state: 1 name: ksatta headphones mic: 0
D/musicUtils( 829): wired_headset
E/AudioFlinger( 96): EQtype is 0, deviceType is 0
E/SRS_wowhd_binder( 96): startEqualizer EQtype is 0, deviceType is 0
E/SRS_wowhd_binder( 96): startEqualizer bSpeaker is 0
E/SRS_wowhd_binder( 96): equalizer1 EQtype = Default
Click to expand...
Click to collapse
Without the modifications logcat shows:
V/HeadsetObserver( 149): Intent.ACTION_HEADSET_PLUG: state: 1 name: Headset mic: 1
D/musicUtils( 788): speaker
E/AudioFlinger( 96): EQtype is 0, deviceType is 2
E/SRS_wowhd_binder( 96): startEqualizer EQtype is 0, deviceType is 2
E/SRS_wowhd_binder( 96): startEqualizer bSpeaker is 1
E/SRS_wowhd_binder( 96): equalizer1 EQtype = Default
Click to expand...
Click to collapse
So the logs look like my mod is working correctly, however now I can't hear anything from the phone or headphones and also the internal mic is disabled. I've been trying to debug this further, but I can't find where the SRS_wowhd_binder, musicUtils and AudioFlinger logs are generated. Looks like huawei modified some other files than the kernel files, but they haven't released sources for those?
I've tried tags android-2.2.1_r2 and android-2.2.1_r1 from android.git.kernel.org, I found the line where "Intent.ACTION_HEADSET_PLUG: state:..." is logged from HeadsetObserver.java, but I haven't found the others.
Looking further into this..
Anyone have any ideas/suggestions?
edit: looks like Huawei has modified AudioService.class from framework.jar. AudioService handles ACTION_HEADSET_PLUG and and determines if a headset or headphone is connected. Next I think I'll try to decompile the classes and see what's been changed. Or then I'll just try to stick the git version of AudioService on the phone (I wonder what other consequences this'll have, AudioServer handles a bunch of other stuff too).
edit2: I decompiled the phone's AudioService class, it totally ignores the microphone=0 variable Jeez, I wonder why Huawei is cheaper than some others.. Oh well, it's possible to fix. Next step is to edit the decompiled AudioService class and see if that works. Progress
edit3: Actually looks the mic = 0 isn't ignored, the decompiled class just looks really funky. For example "while (true) { return; ...". Might be effects of the decompilation process. Investigating further. The problem might also be in the native libmedia.so
edit4: I found this: http://code.google.com/p/toggleheadset2/ It is used to set output and input to headset.
Might be easiest to fix using a similar way to set output to headphones/line-out and leave the internal mic on.. Looking into that now, I'll post here if I get it to work.
Hey just a quick thing, I have absolutely no idea how easy or difficult it would be to do. But the phones seem to have a problem with headsets/headphones with the iPhone/Blackberry controls on them. It shorts and you can't hear much unless you're pressing the play/pause button.
AFAIK the ground/mic are switched round, but at least for the Samsung Galaxy S there is a kernal + rom out that fixes it so i'd imagine it was somewhat plausible with this phone too.
Don't necessarily need the buttons working (although they work with stock headphones, but meh) it'd just be nice to be able to using any type of headphones.
ryronz said:
Hey just a quick thing, I have absolutely no idea how easy or difficult it would be to do. But the phones seem to have a problem with headsets/headphones with the iPhone/Blackberry controls on them. It shorts and you can't hear much unless you're pressing the play/pause button.
AFAIK the ground/mic are switched round, but at least for the Samsung Galaxy S there is a kernal + rom out that fixes it so i'd imagine it was somewhat plausible with this phone too.
Don't necessarily need the buttons working (although they work with stock headphones, but meh) it'd just be nice to be able to using any type of headphones.
Click to expand...
Click to collapse
I think this would have to be fixed from some other place in the kernel. I'm now trying to mod toggleheadset2 so that it sets the audio output to headphones and leaves the internal mic on. I think your suggestion could be accomplished probably by checking out what they changed in the Samsung Galaxy kernel and doing the same changes.
in HTC devices do not have that problem. After connecting the headset microphone is working, one could see how it is set in the HTC. I have a headset phones that work with HTC and other companies. The X5 does not work and I get the impression that the reason is not software and the construction of the socket (While connecting).
Piron said:
in HTC devices do not have that problem. After connecting the headset microphone is working, one could see how it is set in the HTC. I have a headset phones that work with HTC and other companies. The X5 does not work and I get the impression that the reason is not software and the construction of the socket (While connecting).
Click to expand...
Click to collapse
Yes, the Ideos X5 seems to detect headset connected even if it's headphones or line-out cable. You might be right that it's a hardware issue.
If I get my fix to work it'll just force the internal mic to stay on if headphones/headset is used. It's a workaround
OK. Some "progress"..
When headphones without mic are plugged in the Huawei sets DEVICE_OUT_WIRED_HEADSET to 1 and DEVICE_IN_MIC_ARRAY to 1
When I manually set only DEVICE_OUT_WIRED_HEADSET (even if headphones are not connected), the internal mic is disabled.
If I set both DEVICE_OUT_WIRED_HEADSET and DEVICE_IN_MIC_ARRAY to 0 after plugging the headphones, then the internal mic works, but the output goes to the earpiece..
Then I tried to set:
DEVICE_OUT_WIRED_HEADSET 0
DEVICE_IN_MIC_ARRAY 0
DEVICE_OUT_WIRED_HEADPHONE 1
Then the internal mic worked, but the output was routed to the phone's speaker (speakerphone mode)
I think the problem is in AudioSystem.cpp (part of libmedia.so), of which Huawei hasn't released the source.. Since they haven't modified AudioSystem.java (diffed that..).
There is something really different in there, maybe they have changed it so that always when _output_ is set to headset, input is set to "mic_array" or something... and setting output to headphones sets output to speaker etc etc..
I think I'll still try setting output to speaker (if headphone and speaker ids are switched).. Or then create my own native program which sets output to headphones..
Looks like the main routing is done in frameworks/base/libs/audioflinger/AudioPolicyManagerBase.cpp..
Oh well, I'll continue tomorrow
Thanks for your efforts and for putting so much time into documenting the process.
I think if you can't find a simple solution the next step would be to try and get msm7k drivers with known source code working on our device, rather than spending time on guessing behaviours of a driver which we have no source for.
See the links below for the source for all of the msm7k drivers and a modified msm7x30 kernel from Kali. It might also be interesting to look at the Qualcomm sources to see how they have modified it (I think mostly it's just been changed to accommodate FM radio but there may be other changes).
https://github.com/Kali-/android_hardware_msm7k
https://github.com/Kali-/htc-kernel-msm7x30-exp
I will help with this when I can, but I am extremely busy at the moment with work and uni. Good luck!
stockwell said:
Thanks for your efforts and for putting so much time into documenting the process.
I think if you can't find a simple solution the next step would be to try and get msm7k drivers with known source code working on our device, rather than spending time on guessing behaviours of a driver which we have no source for.
See the links below for the source for all of the msm7k drivers and a modified msm7x30 kernel from Kali. It might also be interesting to look at the Qualcomm sources to see how they have modified it (I think mostly it's just been changed to accommodate FM radio but there may be other changes).
https://github.com/Kali-/android_hardware_msm7k
https://github.com/Kali-/htc-kernel-msm7x30-exp
I will help with this when I can, but I am extremely busy at the moment with work and uni. Good luck!
Click to expand...
Click to collapse
Actually I was thinking the same thing, move on to something of which I have the full source code.
Thanks for the info, I'll look into that. Fixing this "little bug" turned out to be quite a time-consuming process, but I'm getting good experience on modifying android. Also if I one day get this fixed, it'll be awesome
Actually the source for the msm7x30 is in the huawei's kernel source from huaweidevice.com.
I think there are also some problems with the libaudio etc for which Huawei haven't released the source.
Thanks for pointing me in the right direction, I'll see if can modify the msm7x30 from huawei source so that the int. mic isn't disabled.
edit: Yeah, this looks like the place where the actual routing is done. Of course, it's the kernel driver for the sound.. Learning something new all the time
I managed to get some logs from msm7x30.c:
device handset_dual_mic_broadside_tx set 1
device handset_dual_mic_broadside_tx set 0
when plugging headphones in and taking them out..
Now I think I'm getting close. A good point to continue from tomorrow
What I meant was that we don't have the libaudio source from Huawei, but we can use another source (Qualcomm/Kali/etc) for libaudio and then we need to change the kernel driver to suit it (which we can model from Kali's kernel drivers).
stockwell said:
What I meant was that we don't have the libaudio source from Huawei, but we can use another source (Qualcomm/Kali/etc) for libaudio and then we need to change the kernel driver to suit it (which we can model from Kali's kernel drivers).
Click to expand...
Click to collapse
Ahh, I see. Yeah now I understand.
I'll see if I can get the kernel driver modded so that it doesn't disable the internal mic. Ofcourse this would mean that the internal mic is never disabled (the kernel driver doesn't know why the int. mic is being disabled.) So it wouldn't be disabled even when using bt headset etc.. If I have understood correctly. A better way to fix it would be from the libX side. But let's see first how my kernel mod goes
I got it working so that when I plug in headphones during a phone call, internal mic works and the output goes to the headphones
But... the routing doesn't return back to normal without the headphones or if I plug in the headphones before the call etc etc... but this is looking good!
First of all thanks to:
wmi543 and stockwell for helping me get the stock kernel built.
stockwell also for helping me figure out where the problem could be fixed.
genokolar and stockwell for the working recovery.
And everyone else if I forgot to mention someone.
I modified the kernel sound driver (msm7x30.c) so that when the driver is requested to set the headset mic on/off or route to it, the speakerphone mic is used instead. I don't think there's a different mic for the speakerphone physically on the phone, but the device is called "speaker_mono_tx" and it probably uses different settings than when using the phone in non-speakerphone mode. So I figured it's best to use the speakerphone mic device instead of the normal mic settings (When headphones/line-out used).
Obviously DO THIS AT YOUR OWN RISK. It's always a good idea to take a complete backup with perfect recovery (http://forum.xda-developers.com/showthread.php?t=1067490) before changing anything.
Edit: This mod is now included in the franco.kernel (forum.xda-developers.com/showthread.php?t=1166560). You can just flash that kernel. Below are the old instructions.
Installation (in linux)
Note the attached boot.img contains the ramdisk of the Finnish operator Saunalahti. It seems to contain some wifi modules too, so it's better to create a new boot.img from your own boot.img (instructions below)
- Boot the phone in bootloader mode. (Hold down vol up and vol down and power on).
- In ubuntu the phone partitions are mounted automatically, you might have to mount them manually in some other distros.
- Find the phone's partition which contains the "image" directory. Go to the image directory.
- There should be a file called "boot.img". Take a backup of the original and replace it with the attached boot.img.
- Unmount all the phone's partitions
- Remove battery to exit bootloader mode.
- Put battery back and boot
- Now the internal mic should work with headphones without mic or for example when connected to a car stereo.
Updating your own boot.img
- Get abootimg source from http://gitorious.org/ac100/abootimg. (I couldn't find a compiled binary for ubuntu, except an old version 0.3).
- I had to install package libblkid-dev to build it. It probably also needs other packages too, but I had them already installed.
- Build it:
Code:
make
- After make finishes you should have the built binary "abootimg".
- Extract the attached kernel.zip (Contains zImage, the built kernel)
- The next command updates the boot.img, so copy your original to boot.img.orig for example.
- Update the boot.img file:
Code:
[path to the abootimg you built]abootimg -u [boot.img from your phone] -k [zImage from kernel.zip]
- Now you can use this updated boot.img on your phone following the instructions above.
Details
As Piron said I think the root of the problem is in the construction of 3.5mm socket so that it doesn't headphones correctly. However I tried to force the detection so that it always detects headphones instead of headset. But that didn't work. The libaudio etc probably have some bugs with the headphone mode (it's never been tested since the phone never detects headphones .
This mod forces the use of the int. mic instead of the headset mic. Obviously with this modified kernel you can't use a headset's mic if you want to.
The modified msm7x30.c is in the attached zip.
It's been quite an adventure but it's rewarding to finally get it to work
I already tested it in my car with background noise etc and it worked perfectly (I heard the other person via the car speakers and he heard me). Also there was no echo which is surprising. The phone's mic is probably directional or something. It's a good mic
Post here if it works for you or if you have problems with the mod.
stockwell said:
What I meant was that we don't have the libaudio source from Huawei, but we can use another source (Qualcomm/Kali/etc) for libaudio and then we need to change the kernel driver to suit it (which we can model from Kali's kernel drivers).
Click to expand...
Click to collapse
Ahh, I see. Yeah now I understand.
I'll see if I can get the kernel driver modded so that it doesn't disable the internal mic. Ofcourse this would mean that the internal mic is never disabled (the kernel driver doesn't know why the int. mic is being disabled.) So it wouldn't be disabled even when using bt headset etc.. If I have understood correctly. A better way to fix it would be from the libX side. But let's see first how my kernel mod goes
Click to expand...
Click to collapse
Now the headset mic is "replaced" with the phone's mic, so BT etc should work fine.
I tried to find the file from where the msm7x30.c functions are called from. I couldn't find anything from the kernel or from the android git source. Probably because I'm not really a C guru. If we could find the place from where the msm7x30 kernel driver is told to use headset mic etc, it could be also fixed from there. This would be better because then there could be a setting "force internal mic instead of headset mic" or something.
But the current kernel mod works for me. I might look more into this later.
If anyone figures out where the msm7x30.c functions are called from it should also be possible to fix the issue from that side. Or I mean have a setting for forcing the int. mic..
good job~~！
is there anyway to get this fix in an app version for those of us without a rooted phone? thanks.
m2hartman said:
is there anyway to get this fix in an app version for those of us without a rooted phone? thanks.
Click to expand...
Click to collapse
I haven't found a way (yet). It might be possible by calling some method from the internal android libs (something like I tried earlier in this thread) the set available method didn't seem to work correctly. For some reason setting headphones available routes output to speaker, and setting headset output available disabled the internal mic etc..
I might look more into this later, but I don't have time now. If anyone else wants to try I can give some pointers.
Sent from my u8800 using XDA App
Worked like a charm, great work
Edit: It seems that i have a huge battery drain and the wifi is not working after modding the file and the lower part of the device seems to be hotter than the rest. Had to go back to default boot.omg Any ideas?
If you could write a how to replace only the msm7x30.c file of the boot image, maybe could solve the problem?
Add1cteD said:
Worked like a charm, great work
Edit: It seems that i have a huge battery drain and the wifi is not working after modding the file and the lower part of the device seems to be hotter than the rest. Had to go back to default boot.omg Any ideas?
If you could write a how to replace only the msm7x30.c file of the boot image, maybe could solve the problem?
Click to expand...
Click to collapse
The msm7x30.c has to be replaced in the kernel source (http://www.huaweidevice.com/tcpsdow...achmentName=kernel-2.6.32-U8800-Froyo.tar.zip). The boot.img contains the built kernel with only the msm7x30.c changed. I changed some other files while looking for the problem, but I put back the original files before building the kernel I attached here. I can build it again tonight with only the msm7x30.c changed and see if that makes any difference, if I forgot to revert some files.
I've also had some problems with WiFi, but I also had some before my kernel mod. It's possible that the kernel source from huaweidevice.com is different than the one you had on your phone originally. I think Huawei hasn't released the sources for all the different kernel versions out there.
BTW. Are you using Go launcher EX? I just realized after the latest update that it kept hogging the CPU (would cause battery drainage, slow down the phone and heating). I had to kill it once, now it seems to work ok again.
I have just downloaded ASTRO file manager and started browsing through system files, then Ive found a file called calibration in /etc/wifi . In order to try to have a better wifi signal, i have opened that file with text editor and found a line where i can read pa0maxpwr=70 i guess it can be possibly by putting a higher level, make the wifi signal stronger, but I dont have enough time to try this, so please try to confirm this by yourself and write here obtained results....
This file has been found in firmware .042 in R800i device with stock kernel/rom
Ive found another line that says: pa0itssit=62 , but i dont know for what is used this value....
I don't think changing the number will make you have a stronger signal.
Maybe it's like if the power signal is 70 or more, show the wifi signal at max (the little dot and 3 waves on top of it).
bamsbamx said:
I have just downloaded ASTRO file manager and started browsing through system files, then Ive found a file called calibration in /etc/wifi . In order to try to have a better wifi signal, i have opened that file with text editor and found a line where i can read pa0maxpwr=70 i guess it can be possibly by putting a higher level, make the wifi signal stronger, but I dont have enough time to try this, so please try to confirm this by yourself and write here obtained results....
This file has been found in firmware .042 in R800i device with stock kernel/rom
Ive found another line that says: pa0itssit=62 , but i dont know for what is used this value....
Click to expand...
Click to collapse
In the cheapo Chinese tablets from 2010 there were similar mods to increase the Wifi signal though they made the device (and more specifically the wifi antenna) extremely hot. So I wouldn't fancy doing it on a proper device.
pa0maxpwr determines the max power that is given to the wifi antenna, increasing it will just give you a hot phone and short battery
i have tried it (increased to 90) , but the wifi antenna hasnt increase its temperature and the battery works as always....
And have you increased your Wifi strength?
Logseman said:
And have you increased your Wifi strength?
Click to expand...
Click to collapse
i dont fell any increase in the wifi signal.....
Txpower=100?
I tired changing the value, but it seems to revert back to its default (doesn't save). I'm rooted with the zergrush method.
If someone is playing with this, try 255 for a value and see if it makes a difference. 255 is max for an int (1byte)
Njord0 said:
I tired changing the value, but it seems to revert back to its default (doesn't save). I'm rooted with the zergrush method.
If someone is playing with this, try 255 for a value and see if it makes a difference. 255 is max for an int (1byte)
Click to expand...
Click to collapse
I think you have to mount the system as R/W. If it doesnt work try setting the correct properties/permissions of the file....
I found that file in other folders inside phone memory, maybe have to change all the same files....
AndroHero said:
pa0maxpwr determines the max power that is given to the wifi antenna, increasing it will just give you a hot phone and short battery
Click to expand...
Click to collapse
Isnt this phone hot already?
Pretty sure this is a dead end, even if pa0maxpwr is set to 0, wifi works the same as always
The A500 has keypress feedback sounds which I like, but I wish they were a little quieter. There is only an On/Off toggle in the settings, and the volume of the sounds is not affected by the 3 volume settings on the tablet.
Since my tablet ia rooted, I decided to experiment with trying to replace the sound files with copies modified to have a lower volume (using Nero Wave Editor on my PC).
I found the files are ogg-vorbis format, and stored in /system/media/ui. I backed them up to the SD card, then copied them off to my PC, did the volume voodoo, and copied them back to the above location.. The end result of my testing is that:
1 - a reboot is necessary to effect changes to those files
2 - the tablet doesn't like those files to be changed.
When things did not seem to be working out, I decided to restore the backups to the original file locations. But even after rebooting, and also trying toggling the keyboard sounds on and off, the tablet began malfunctioning in the attempt to play the sounds while typing. I had to restore a nandroid to get the original sounds working again.
I'd like to learn why this did not work. I suspect it has to do with file permissions, and/or formatting, because every time I copied the edited files back to the tablet by USB it warned that they might not be playable. That reminded me of how, when dealing in the past with some PDAs, files had to be ''converted'' for their use, even though they retained the same identical file name extensions. Might that be the case here?
To start, I'd like you all to know I've spent the better part of a day searching google and elsewhere for an answer to my quandary. If there is an answer to this somewhere that I've missed, I apologize. I am at my wit's end.
I'm running a rooted SM910P with MasterZen88's rom. I have hardly anything extra installed (just SuperSU, FX, TB). I cannot for the life of me get the system to use screen touch and screen lock sounds that I place in /system/media/audio/ui. I have adjusted the permissions for the new files as appropriate (rw-r-r), though they were properly set from the get-go anyway. I've tried restarting the phone and clearing the cache several times. No luck. Those sounds will not work - they are always the awful default sounds, even though I've explicitly overwrote those files.
It seems that the sounds in question are actually being read from somewhere else, but in my exploring I haven't been able to find them. Perhaps embedded in some of TW's apks? I don't know a whole lot about this. The most perplexing thing is that some of the sounds I replaced work perfectly fine - the pen detach/attach, the power on and power off, and even the charger connect sounds all work just fine. If anyone has any ideas or could point me in the right direction, it would be much appreciated.
As an update, I did find out that there are some raw resources in the default Keyguard.apk that I assume (I have not tested because I'm still learning how apks work) are being used in place of the /system/ui directory ones, but that's only really for the lock screen - it doesn't explain the screen touch sounds not working when replaced. Still at a loss there.
(FIXED)
Assalam o alaikum
Hi
I've an lg v20 Us996
Unlocked bootloader amd rooted
When i first bought this phone it was liquid and buttery but after few days device starts lagging and stucking,i farctory restored it but no fruit then plan to root it and j rooted it but still the device keep lagging.
I've strictly monitored the activities of my cpu and the thing which i captured is that My cpu min and max frequencies keep changjng by it self which makes it laggy.
Like the max frequency is 2.15, but i automatically scales down to 400mhz,900mhz,1036 and some others frequencies which slow down the device.
Even if i use kernal auditor and set the max frequency to sclae up still it automatically changes.
I've used 3different kernals and on stock based rom(weta rom)
Still the same issue.
Is it a hardware issue or software issue?
Thanks in advance
First off, this shouldn't be posted in the development section as it's unrelated to development.
Second, the CPU is supposed to scale, change frequencies depending what the phones doing, 307 MHz-2.15 GHz. If the CPU stayed at 2.15GHz, you would face dramatically shortened battery life and eventual overheating. Thermal throttling is a necessity. LG is a bit more conservative compared with some other vendors I have noticed but if the issue has just started I would look more towards a particular app running afoul.
+1 for app craziness... If you utilize any 3rd party stores, ie Aptoide,Blackmart,ect... Then I HIGHLY suggest getting some sort of active antivirus on your device at this point. Malware is getting good enough to bypass Google Play filters, what do you think is going on on the less-than-monitored stores? Mayhem... Silent, costly mayhem. Chances are, if your CPU is doing all of that randomly, and especially if it is getting warm for no reason/battery drain from sitting and doing nothing, chances are your device is part of an Ethereum/Bitcoin MineNet, making someone money... I suggest getting a Norton AntiMalware scanner.. I KNOW.. Norton blows on windows.. But it cleared my device of the exact same plagues... Just watch out for that FinSpy... That bites.... I just had a bit of that as part of an entire multi-zero-day attack on my networks I am in the process of writing up reports for CVE's.... It made a mesh network between anything with Wifi, Bluetooth, or IR... Kernel level on windows 10... and with the climate of today, and how you started the thread, if I were you, and if you connect your phone to your computer, and if you run Windows 10, then I would check your MBR, and your bootsec as well for possible buffer overflows that lead to code injection that might send your device booting elsewhere while images are being made of your system... This is a long shot... But these are the symptoms I experienced, which led me to literally watch my logcat with aLogCatView live for about 2 hours, watching my mic go on and off, and then once, in light blue letters, I caught FinSpy, with nothing after those letters... just a notation that scrolled on...
Now more than ever, exercize proper security. Especially on a device who's sec has been bypassed by the same exploits that the malware will use to gain access to do damage. We praise DirtyCow for giving us our phones, truly. But the nefarious praise it for giving THEM OUR devices... Just my .2
Ducter said:
First off, this shouldn't be posted in the development section as it's unrelated to development.
Second, the CPU is supposed to scale, change frequencies depending what the phones doing, 307 MHz-2.15 GHz. If the CPU stayed at 2.15GHz, you would face dramatically shortened battery life and eventual overheating. Thermal throttling is a necessity. LG is a bit more conservative compared with some other vendors I have noticed but if the issue has just started I would look more towards a particular app running afoul.
Click to expand...
Click to collapse
The problem was with thermal engine which I've fixed
maxi65 said:
The problem was with thermal engine which I've fixed
Click to expand...
Click to collapse
How did you fix it?
Sent from my LG-H918 using XDA-Developers Legacy app
Assalam o alaikum
You just simply have to replace thermal engine configuration file form your system/etc folder using root explorer and everything will be fine and smooth (in sha Allah)
Use root explorer
Go to system and find for 'etc' Folder
Then in etc folder find ' thermal engine 8996' and create a backup of that file by simply copy that file to your internal storage or wherever you want
Then replace this file with that file which I've provided you in attachment
Note: the attached file is in 'txt' format
Change the extension from 'txt' to 'conf' by simply renaming the file then replace it.
Thanks man You saved