Related
As I making a beats mod for sense 3.5, found interesting file TPA2051_CFG.csv and TPA2051_CFG_XC.csv, the first one should be the template and the second one is the working i2c command file for various system volume, search google for TPA2051, is the amplifier which uses i2c interface, I don't know what exactly i2c is, maybe electronic engineers can explain. Comparing XE and normal sensation's, giving only one difference value, see below in blue, that is the playback_headset max amplified value, XE is 55, sensation is 50, that's why the later you hear a lower volume, tweak it to 56 or maybe higher to here boom-boom-boom, pong-pong-pong, ping-ping-ping effect!
For ICS, get the files from my beats mod.
Do not tweak other values except you know exactly what you are doing, there are many of them are gain control, just one bit of them could doubled the gain and may damage your speaker. The datasheet has all the descriptions of these registers of I2C interface.
0x55 seems to be the largest value that the stock htc headset and beats headset can tolerate, 0x59 seems to be the largest value that the speaker can tolerate. For both, the largest volume value is 0x5F.
This should also applies to any other htc devices as long as there is a file similar to this, this is sensation's TPA2051_CFG_XC.csvf ile, if you are using other device, just use that file of your device.
================================================
SoundBoostForGB&ICS.zip
This work for both GB & ICS, without enable the AGC, enabling AGC making music sounds not so good, values for headset is default of XE ROM (0x55), and speaker is (0x59)
#TPA2051 PYDLE_20111027_1Voutput_ON_55_OFF_4F,,,,,,,,,
#mode/kind/i2c_cmds[7],,,,,,,,,
#kind = 0:spk, kind = 1:HEADSET, kind = 2:ring ,kind = 3:rev,kin=4 : 0ff,,,,,
0,4,0x00,0x90,0x00,0x00,0x00,0x00,0x00,#TPA2051_MODE_OFF
1,0,0x00,0x82,0x00,0x07,0xCD,0x59,0x0D,#TPA2051_MODE_PLAYBACK_SPKR
2,1,0x00,0x8C,0x20,0x57,0xCD,0x55,0x0D,#TPA2051_MODE_PLAYBACK_HEADSET
3,2,0x00,0x8E,0x20,0x57,0xCD,0x16,0xCD,#TPA2051_MODE_RING
4,0,0x00,0x82,0x00,0x07,0xCD,0x59,0x0D,#TPA2051_MODE_VOICECALL_SPKR
5,1,0x00,0x8C,0x20,0x57,0xCD,0x55,0x0D,#TPA2051_MODE_VOICECALL_HEADSET
6,0,0x00,0x82,0x00,0x07,0xCD,0x59,0x0D,#TPA2051_MODE_FM_SPKR
7,1,0x00,0x8C,0x20,0x57,0xCD,0x0B,0x8D,#TPA2051_MODE_FM_HEADSET
8,3,0x00,0x8C,0x20,0x57,0xCD,0x55,0x0D,#TPA2051_MODE_PLAYBACK_rev
9,3,0x00,0x8C,0x20,0x57,0xCD,0x55,0x0D,#TPA2051_MODE_VOICECALL_rev
10,4,0x00,0x8C,0x20,0x57,0xCD,0x55,0x0D,#TPA2051_MODE_PLAYBACK_HEADSET_BEATS_ON
11,5,0x00,0x8C,0x20,0x57,0xCD,0x4F,0x0D,#TPA2051_MODE_PLAYBACK_HEADSET_BEATS_OFF
i2c is a in-circuit protocol for comunicating. Thats the protocol the chips and memory banks use to transfer and address data. It is based on a serial connection. I dont know if any of that helps but just wanted to share that info. Now for a question, how to apply and what are the compatable ROMs?
celelivada said:
i2c is a in-circuit protocol for comunicating. Thats the protocol the chips and memory banks use to transfer and address data. It is based on a serial connection. I dont know if any of that helps but just wanted to share that info. Now for a question, how to apply and what are the compatable ROMs?
Click to expand...
Click to collapse
A big thank for your information, and that proves that value is the radio button of amplifier, and since it is a protocol, it will alike for all devices that uses the same chip, how to apply I'll post it on first post. Thanks.
Hi,
I just tested for the value in PLAYBACK_SPKR,set as you recommended and...Yes it works!There is an improvement
Thank you very much for this tip,very good
No one else has tested
WELL DONE. It works !!!! I will look into the other files and see how to tweak them if and when I get time because I'm at college for my masters all day. If there's anything I can help you, feel free to PM.
senastoin xe sense 3
would this work on my sesation xe runing sense 3 stock rom and were do i fiid the files new to this first andriod phone was using wm6.5
it should work, didnt check it but it has ti have this cofig file. It says in the first post, I used ES file manager, and enabled the root access feature and browsed to the file specified and chenged the 2 values.
---------- Post added 15th December 2011 at 12:25 AM ---------- Previous post was 14th December 2011 at 11:48 PM ----------
I found the AIC3254_reg_dualmiccx file and after a loooong review of the datasheet from texas instruments, it seems that the video recording clipping can also be fixed this way. I found that in the:
A17,VideoRecord_IMIC,SET,w,w,w,w,w,w,w,w,w,w,w,w,w,w,w,w,w,w
,,REGISTER,0x00,0x34,0x36,0x37,0x39,0x3B,0x3C,0x00,0x51,0x52,0x53,0x54,0x00,0x0E,0x0F,0x09,0x12,0x13
,,VALUE,0x01,0x20,0x02,0x20,0x02,0x58,0x58,0x00,0x00,0x88,0x00,0x00,0x01,0x02,0x02,0x3F,0x03,0x03
you can change 83 and 84 memory bank (0x53 and 0x54) to control the volume. 0000 0000 is default in the datasheet, which is 0dB.To lower the gain you have to write a negative digital number in those registers eg. 1111 1111 is a gain of -0dB.
Thank you celelivada, I'll try at weekend. One more question, I,m tweaking some soundimage file for sound effects, the srs processor, there is input & output gain, default is 1.0 in and 1.0 out, the question is if input tweak to 0.5, will I get a a louder out?
Works great, thanks for the tip ...
Sent from my HTC Sensation Z710e using XDA App
nice. cant believe a volume fix was that easy and i know its been an issue for a long time.
mudhi said:
Thank you celelivada, I'll try at weekend. One more question, I,m tweaking some soundimage file for sound effects, the srs processor, there is input & output gain, default is 1.0 in and 1.0 out, the question is if input tweak to 0.5, will I get a a louder out?
Click to expand...
Click to collapse
I cant really tell, I really dont know if the input and output of that chip are connected, it has 2 miniDSPs, one is for input and one for output. But I think (because it sounds like it) that the number here represents a normal linear scale, not a dB one. So if you enter "2", the output would be doubled, although not twice as loud because of the whole logarithmic scale of the human ear. Be carefull with that number anyway, do small increments when testing.
edit___ I made a zip for flashing, so try it out, its based on the script for BEATS. I havent tested it but theres no reason for it not to work.
http://dl.dropbox.com/u/29005924/SoundBoost.zip
The Illest 619 said:
nice. cant believe a volume fix was that easy and i know its been an issue for a long time.
Click to expand...
Click to collapse
It is that really easy, but the process of finding that easy is really soooooooo hard. found it until I replace files of /etc from other device.
The zip file is not working. It says: installation aborted, error 6.
Sent from my HTC Sensation Z710e using Tapatalk
I'd be curious to see what RING does. Never hear it in my pocket...
Congrats on the work, though i have read this before and believe the Beats i flashed to my IC rom follows the same princepal. However what i am looking for is an improvement in Notification/Ringtones.
Is there anything in the file to indicate these can be adjusted?
vis-tec said:
Congrats on the work, though i have read this before and believe the Beats i flashed to my IC rom follows the same princepal. However what i am looking for is an improvement in Notification/Ringtones.
Is there anything in the file to indicate these can be adjusted?
Click to expand...
Click to collapse
Ringtones and notification uses the that micro mono speaker, there is no other way to improve it except change it to larger one
There is another way, I saw a post to edit the audio file raising the volume, but same principle, the speaker is not big enough to deliver higher volume.
Although I don't really understand what is the exact meaning, but those 0x values are commands to be send to the chip, and those meanings are ins/outs, directions and level of amplifying, the rings I already tried but have to read the datasheet to understand the meaning, perhaps celelivada wants to read it.
I will read it when I get the time. Now i worked on the soundimage files, and edited the SRS for music headset, and made a much punchier bass. For the .zip , I was in a hurry to make it, but it is really simple to make it yourself or just opet up the beats mod, because it already has the file but it is on stock values. You can open the zip end edit the file there than flash it.
are there other csv files where you can change a value to increase the in-call volume? on my Nexus One, Desire and INC S kernel devs were able to boost in-call volume for the HANDSET (not HEADSET). i'm assuming that the values in the OP do not affect the in-call volume/speaker versus the speaker on the rear of the phone. sadly for me, i haven't read/seen in-call volume tweaks for Sensation kernels. thanks for taking time to read/reply to my questions. (i wish i were savvy enough to do this on my own, lol).
cortez.i said:
are there other csv files where you can change a value to increase the in-call volume? on my Nexus One, Desire and INC S kernel devs were able to boost in-call volume for the HANDSET (not HEADSET). i'm assuming that the values in the OP do not affect the in-call volume/speaker versus the speaker on the rear of the phone. sadly for me, i haven't read/seen in-call volume tweaks for Sensation kernels. thanks for taking time to read/reply to my questions. (i wish i were savvy enough to do this on my own, lol).
Click to expand...
Click to collapse
This reminds me my first impression on sensation is the front speaker volume is too low, and I never seen any post on how to improves it, but it should be possible, and I believe it is the same csv file. Need some readings on datasheet and trying.
celelivada said:
I will read it when I get the time. Now i worked on the soundimage files, and edited the SRS for music headset, and made a much punchier bass. For the .zip , I was in a hurry to make it, but it is really simple to make it yourself or just opet up the beats mod, because it already has the file but it is on stock values. You can open the zip end edit the file there than flash it.
Click to expand...
Click to collapse
so the beats mod have not enough punch. Some informations I know had posted over beats mod. The best source I can find on wow settings is here
Maybe increase trubass speaker size and level, decrease focus and definition, and increase ogain... Just a reminder that you don't have to wipe cache and dalvik everytime, to save time on reboot.
Sound effect tuning should be as easy as using Windows Media Player or any other player, just can't imagine why htc doesn't give this out but instead giving a fixed value, they are supposed to be have sliding bars for emphasize effects. May be they just focus on beats (which is only a bass enhancement and nothing else, and can only be tweaked by hacking the libbeatsbass.so library).
I share how I edit and push it to phone, if you are using Windows.
Using Android SDK, and set environment variable so that everywhere you can adb push and pull, if you install htc sync, adb are also installed, they may not the same version as the Android SDK and will giving that adb is outdate and restarted everytime, so delete those files adb.exe, adbwinapi.dll adbwinusbapi.dll. For win 7 just hold shift and right click to a folder to open cmd prompt.
To compare agains files or folders, first install notepad2 and replace the default notepad, download and use windiff.exe, it can compare difference on word by word, right click can open notepad to edit, and you can easily distinguish between them.
You can leaving notepad2 open just save values you changed and push to the phone and adb reboot. And can go back or go forward for the changes.
celelivada said:
I will read it when I get the time. Now i worked on the soundimage files, and edited the SRS for music headset, and made a much punchier bass. For the .zip , I was in a hurry to make it, but it is really simple to make it yourself or just opet up the beats mod, because it already has the file but it is on stock values. You can open the zip end edit the file there than flash it.
Click to expand...
Click to collapse
If you get the time, please read the datasheet and find the tweak for handset voicecall volume. I found something interesting on sensation XL, but it's not easy to figure out. There is a new kind rev (reverse?) reverse for front and back speaker? front speaker is verrrrrrrrrrrrrry important.
#TPA2051 Runnymede_20111005,,,,,,,,,
#mode/kind/i2c_cmds[7],,,,,,,,,
#kind = 0:spk, kind = 1:HEADSET, kind = 2:ring ,kind = 3:rev,kin=4 : 0ff,,,,,
0,4,0x00,0x90,0x00,0x00,0x00,0x00,0x00,#TPA2051_MODE_OFF
1,0,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_MODE_PLAYBACK_SPKR
2,1,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_MODE_PLAYBACK_HEADSET
3,2,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_MODE_RING
4,0,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_MODE_VOICECALL_SPKR
5,1,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_MODE_VOICECALL_HEADSET
6,0,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_reserve
7,1,0x00,0x8C,0x25,0x57,0xD3,0x0D,0xAD,#TPA2051_MODE_FM_HEADSET
8,3,0x00,0x82,0x25,0x57,0x13,0x4D,0x0D,#TPA2051_MODE_PLAYBACK_rev
9,3,0x00,0x82,0x25,0x57,0x13,0x4D,0x0D,#TPA2051_MODE_VOICECALL_rev
10,4,0x00,0x8C,0x25,0x57,0xD3,0x4D,0x0D,#TPA2051_MODE_PLAYBACK_HEADSET_BEATS_ON
11,5,0x00,0x8C,0x25,0x57,0xD3,0x0D,0x8D,#TPA2051_MODE_PLAYBACK_HEADSET_BEATS_OFF
I use my phone almost daily to listen to music when biking to work, and i really hated the low volume, even with In-Ear headphones!! i could still hear cars and things....
So... i did some searching, and this first solution was posted on the german forum for P6
if this bricks your phone, i'm not responsible
Method One:
using a ROOT BROWSER delete the following folder and all its contents
/system/etc/audio/codec
Click to expand...
Click to collapse
BEFORE doing this please backup the folder first.
IMPORTANT
after doing this, i noticed that sound coming out of headphones is really good "louder" but i also noticed that sound coming out of the speaker is not so crisp, to be honest i never listen to music through the back speaker, it's up to you guys to test it and give some feedback.
Method Two: not tested by me
Using a ROOT BROWSER open this file in your phone with a text editor
cust/channel/weurope/prop/local.prop
Click to expand...
Click to collapse
Look for line
ro.config.hw.security_volume=11
Click to expand...
Click to collapse
and change it to
ro.config.hw.security_volume=#
Click to expand...
Click to collapse
hamdimo said:
I use my phone almost daily to listen to music when biking to work, and i really hated the low volume, even with In-Ear headphones!! i could still hear cars and things....
So... i did some searching, and this first solution was posted on the german forum for P6
if this bricks your phone, i'm not responsible
Method One:
using a ROOT BROWSER delete the following folder and all its contents
BEFORE doing this please backup the folder first.
IMPORTANT
after doing this, i noticed that sound coming out of headphones is really good "louder" but i also noticed that sound coming out of the speaker is not so crisp, to be honest i never listen to music through the back speaker, it's up to you guys to test it and give some feedback.
Method Two: not tested by me
Using a ROOT BROWSER open this file in your phone with a text editor
Look for line and change it to
Click to expand...
Click to collapse
The first method worked for me, many thanks
Both methods working!
head phone volume
Hi!
I want to know if there is a way we can check balance setting for head phone volume.
My right channel volume is low and base is also low.
I have tried different head phones to rule out headphone issue.
thanks
titus
Method Two is 100% working, with some changes: in /cust/channel, you have to find the local.prop which contains your CustCVersion. If you don't know it, yuo can easily find it in Settings -> About phone -> Custom Version. For example my CustC is 185, which means I had to edit /cust/channel/neeurope/prop/local.prop. In local.prop, don't change ro.config.hw.security_volume from 11 to #, you have to write a "#" before two lines: ro.config.ce_authenticate=1, and ro.config.hw.security_volume=11, so the file should look like:
# DTS2012112701533 shifengbing 20121219 delete
ro.config.hw.BH_defaultlanguage=true
# DTS2012112610240 mashangrong 20121203 begin
ro.product.Certification=true
# DTS2012112610240 mashangrong 20121203 end
persist.telephony.mpdn=false
# /*<DTS2012112007884 chenzhong KF65276 20121120 begin */
ro.config.hw_ReplaceSr=true
# /*DTS2012112007884 chenzhong KF65276 20121120 end> */
#ro.config.ce_authenticate=1
ro.config.hw.security_enabled=true
#ro.config.hw.security_volume=11
ro.config.hw_opta=185
ro.config.hw_optb=999
ro.product.CustCVersion=C185
ro.product.CustDVersion=D221
Hello,
Thanks for the tips with the # on the two rows. It increase the volume but it is still too too low. And unless i m alone in my room in the middle of the night music is still unlistenable.
Why it ils ok for other people but not for me?? Ils there something that I didnt do?
Thank you for tour help
Shadowprince94 said:
Method Two is 100% working, with some changes: in /cust/channel, you have to find the local.prop which contains your CustCVersion. If you don't know it, yuo can easily find it in Settings -> About phone -> Custom Version. For example my CustC is 185, which means I had to edit /cust/channel/neeurope/prop/local.prop. In local.prop, don't change ro.config.hw.security_volume from 11 to #, you have to write a "#" before two lines: ro.config.ce_authenticate=1, and ro.config.hw.security_volume=11, so the file should look like:
# DTS2012112701533 shifengbing 20121219 delete
ro.config.hw.BH_defaultlanguage=true
# DTS2012112610240 mashangrong 20121203 begin
ro.product.Certification=true
# DTS2012112610240 mashangrong 20121203 end
persist.telephony.mpdn=false
# /*<DTS2012112007884 chenzhong KF65276 20121120 begin */
ro.config.hw_ReplaceSr=true
# /*DTS2012112007884 chenzhong KF65276 20121120 end> */
#ro.config.ce_authenticate=1
ro.config.hw.security_enabled=true
#ro.config.hw.security_volume=11
ro.config.hw_opta=185
ro.config.hw_optb=999
ro.product.CustCVersion=C185
ro.product.CustDVersion=D221
Click to expand...
Click to collapse
Does anyone know what /cust/channel/ I should edit if my CustC is C113 ?
Thanks much
In channel folder ther eis several other folders.
you have to check each build.prop. at the end of each build.prop, you could see the custC number.
You just have to found wich one it is. for sure it is not weurope
any issues with method 1?? ive read before that modifications can affect call volume,etc
omg omg omg omg omg *drops dead*
First method Works Great. I thought i was stuck and would have to hung myself. Got a portable amp but this phone is already so big. Thanks allot bud.
Dunno which method worked on me, did both, then restarted my phone, and hell yeah...so loud...even must put lower volume not to harm my ears Thanx!
method 1, adapted
What worked for me was to cut the codec folder as described with a root browser, paste it to SD as a backup, reboot, reinstate codec folder, reboot, loud as hell!
I have no idea how this works, but happy!
Mate7 supported ?
The fix also applies to Mate7 ?
Worked!
I tried first method on my Honor 6 (H60-L04), and it's work Now I can REALLY enjoy my music.
Thanks mate!
I don't have permission to delete, change or modify the folder, any ideas? I am using Root Browser
It works! Thank you very much
Does my p6 have to be rooted in order to save the settings?
ANy solution without Rooting?
Hi,
I'm looking for solution without rooting, any idea?
Thanks
Thanks
Thank you guys, you made my day! I was complaining about the volume in the headphones at a Honor 6, H60-L04, I did both of these modifications and it rocks! The volume is to the sky, i have to keep it even at 75 % so i don't fry my ears ).
Shadowprince94 said:
Method Two is 100% working, with some changes: in /cust/channel, you have to find the local.prop which contains your CustCVersion. If you don't know it, yuo can easily find it in Settings -> About phone -> Custom Version. For example my CustC is 185, which means I had to edit /cust/channel/neeurope/prop/local.prop. In local.prop, don't change ro.config.hw.security_volume from 11 to #, you have to write a "#" before two lines: ro.config.ce_authenticate=1, and ro.config.hw.security_volume=11, so the file should look like:
# DTS2012112701533 shifengbing 20121219 delete
ro.config.hw.BH_defaultlanguage=true
# DTS2012112610240 mashangrong 20121203 begin
ro.product.Certification=true
# DTS2012112610240 mashangrong 20121203 end
persist.telephony.mpdn=false
# /*<DTS2012112007884 chenzhong KF65276 20121120 begin */
ro.config.hw_ReplaceSr=true
# /*DTS2012112007884 chenzhong KF65276 20121120 end> */
#ro.config.ce_authenticate=1
ro.config.hw.security_enabled=true
#ro.config.hw.security_volume=11
ro.config.hw_opta=185
ro.config.hw_optb=999
ro.product.CustCVersion=C185
ro.product.CustDVersion=D221
Click to expand...
Click to collapse
In my Mate 7 local.prop is in /cust/hw/eu/prop
Mediatek and GPS, ah, how we love trying to get it to work. People have been making foil antennas, tweaking GPS.conf, meddling with NTP and all manner of other things to get it working only to find that the very next day it is back to sullenly sitting there with ne'er a satellite in view. Duff hardware? It seems likely - only it's not. There is nothing at all wrong with the Mediatek GPS hardware. When it is allowed to work, it works as well as anything I've come across, SiRF included.
The problem is assumption on the part of manufacturers and our insatiable lust for a bargain. Assume makes an ass of u and me.
Prerequisites:
Root and the ability to mount /system RW. Sorry if you're one of these people who flatly refuses to root their devices, this is not the solution you're looking for <fx:waves hands/>
Some method of getting into MTK Engineering Mode, whether that's MobileUncle, the "secret" dialler code, GravityBox etc.
A text editor that doesn't follow the MS rule that their line breaks are correct and everyone else+dog is wrong. Notepad++ will do for those of you who cannot break the Redmond shackles. MS Notepad is just going to corrupt the files.
ADB set up and working.
No allergy to XML. If you start sneezing, your eyes start streaming or anything happens to your vision after looking at a few <>'s, please discontinue use.
Step 1: Disable EPO. It's worse than useless for any other starting location but Shenzhen. If you don't believe me, try enabling it again after you complete the rest of the steps. Go into engineering mode and, under Location/Location based service/EPO deselect the obvious checkboxes. This on its own improves matters enormously. With some ROMs you can also do this through Settings by tapping the "GPS satellites" item in Location access and deselect the "Enable EPO assistance" checkbox.
Step 2: Mount /system read/write with whatever method you normally use, whether that's adb remount, adb shell mount -o rw,remount /system or whatever.
Step 3: cd to a clean directory, say MTKGPS.
Step 4: adb pull the following files:
Code:
/system/etc/gps.conf
/system/etc/agps_profiles_conf.xml
/data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
Careful with that last one, it appears in more than one place but it is the com.mediatek.lbs.em version we want
Note the file permissions for these files as they stand on your particular ROM.
Code:
-rw-r--r-- root root 164 2014-06-19 18:29 gps.conf
-rw-r--r-- root root 9502 2014-06-20 15:29 agps_profiles_conf.xml
-rw-rw---- u0_a39 u0_a39 2659 2014-06-20 20:21 agps_profile.xml or
-rw-rw---- 10039 10039 2659 2014-06-20 20:21 agps_profile.xml
The owner of the agps_profile.xml file should be the user's UID. It may be different on your handset. Check it first, please. If any of these differ on your ROM, use the permissions on yours as canonical. This is just a guide.
Step 5: Now we're going to do what FasterGPS does, only a bit more. Edit the gps.conf to look something like this:
Code:
NTP_SERVER=<your country>.pool.ntp.org
SUPL_HOST=supl.nokia.com
SUPL_PORT=7275
INTERMEDIATE_POS=1
ACCURACY_THRES=5000
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_USER_PLANE=TRUE
Purists will note I'm using Nokia's SUPL server here. A little research tells me that Google's SUPL is, well, it's a bit pants - and not just because it's one more way they get PII from you. YMMV, beware of the leopard, and so forth. If you want to use the chocolate factory's SUPL, just swap the SUPL_HOST line to supl.google.com.
Save the file.
Step 6: Now let's undo the mistakes of the manufacturer. Unfortunately we have to delve into some unholy XML for this but don't worry, it's not that difficult despite how daunting the file looks in a text editor. Open agps_profile.xml in your editor.
Make sure the following lines (amongst loads of others that should be left alone) appear as shown:
Code:
<int name="slp_port" value="7275" />
<string name="slp_code">NOKIA</string>
<boolean name="agps_enable" value="true" />
<string name="slp_addr">supl.nokia.com</string>
That's the barebones. Don't exit the file yet. Locate the following lines:
Code:
<float name="nTargetAreaGeolat" value="nn.nnnnn" />
<float name="nTargetAreaGeolng" value="nn.nnnnn" />
See the problem? Try sticking the co-ords from your file into an online mapper. These are passed to the SUPL server no matter what CellID your phone reports. Worse, if you have no cellular radio, it's taken as gospel so you get ephemeris for the middle of China. Useful. This is why cold start takes even longer than it would on a standalone GPS from cold.
Now, what we need to do is set those up for your general location. It doesn't need to be point precise, just a general 0.1 degree lat and long.
IMPORTANT: If you are West of the Meridian, you need to do some jiggery-pokery with your longitude. This file treats the world as a 360 degree ball, so you need to subtract your longitude from 360. For example, if you're 4 deg W of Greenwich, your longitude would be 356.0. 110.3W equates to 249.7. Yes, this number drops as your longitude goes up if you're West.
Save this file.
Step 7: Now let's edit the agps_profiles_conf.xml. This one's fairly easy, just change the end to look like this, with the usual GOOGLE in default_profile if that's your bag:
Code:
<agps_conf_para
agps_enable="yes"
ca_enable="no"
cdma_agps_preferred="0"
cp_auto_reset="no"
cp_gemini_pref_sim="1"
cp_up_selection="up"
default_cdma_profile="CDMA1"
default_profile="NOKIA"
disable_after_reboot="no"
ecid_enable="yes"
gpevt="no"
log_file_max_num="10"
ni_request="yes"
notify_timeout="8"
roaming="yes"
si_mode="mb"
supl_version="1"
verify_timeout="8"
/>
</agps_profiles>
Note cp_gemini_pref_sim can be set to 2 if that's your main SIM that usually has a signal. It is used as the CellID source for aGPS, not the data connection the aGPS data is fetched on.
Save the file.
Step 8: Push the files back with adb and set up their ownership and permissions:
Code:
adb remount
adb push gps.conf /system/etc/gps.conf
adb push agps_profiles_conf.xml /system/etc/agps_profiles_conf.xml
adb push agps_profile.xml /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
adb shell chown 10039:10039 /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
adb shell chmod 660 /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
adb shell chmod 644 /system/etc/agps_profiles_conf.xml
adb shell chmod 644 /system/etc/gps.conf
Step 9: Reboot and retry your GPS. Once you have checked everything is working, you can re-enable EPO, clear the aGPS data in Engineering Mode and try again just to verify I'm not talking out of my backside. EPO really doesn't help in this guise, at least not in the UK.
In conclusion, these can be made to work. With these changes in place I can get an indoor lock in airplane mode in just under ten seconds a day and a reboot after last using the GPS. You need a rooted device and some bright spark will no doubt automate all of this - I'm no Android hacker so don't look at me. GravityBox would be my guess as it's developed at a remarkable pace - thanks for the app, BTW
I do hope this works for everyone. It would be nice to put this one to bed once and for all. A final note: There may be errors in this. I'm only human. Check, double check, triple check, take backups, all the usual stuff. Flames to /dev/null, please.
Question: When I enter the coords of my general location, does that mean I will have trouble if I travel to another country or just very far from the mentioned coords?
Thanks for the guide BTW. This deserves more views.
DiGtal said:
Question: When I enter the coords of my general location, does that mean I will have trouble if I travel to another country or just very far from the mentioned coords?
Thanks for the guide BTW. This deserves more views.
Click to expand...
Click to collapse
It certainly won't be any slower than stock, that is for sure. Eventually it'll override the aGPS if you're away from your normal starting location. For occasional use abroad, it won't make it any worse and you should have a cell tower's details to pass to the SUPL server anyway.
Sounds a lot of work for such little thing.
I just use 3 apps and about 2 minutes of my time. And GPS works like a charm.
I'm not trying to dis you work friend. But there are simpler ways to do the same thing.
So, here it is:
Get "FasterGPS" app from Google Play Store. \
Get " MT GPS" app from Google Play Store } All free.
Get "MobileUncle" app from Google Play Store /
Go to Your GPS and mark everything ON.
Use FasterGPS and change your GPS Zone. i.e. Europe/Portugal
Use MT GPS to download the EPO Files.
Use MobileUncle, click on engineer mode, again on engineer mode (mtk),
sweep to the left until you find YGPS, click on it, then on information,
down you'll see hot, full and AGPS restart, follow this order and click on them.
Go back and click on satellites, and that's it...
Personally i use Sygic v14.02, it's the best to find satellites and a very quick fix.
But you use whatever you wish.
bravesoul said:
Sounds a lot of work for such little thing.
I just use 3 apps and about 2 minutes of my time. And GPS works like a charm.
I'm not trying to dis you work friend. But there are simpler ways to do the same thing.
So, here it is:
Get "FasterGPS" app from Google Play Store. \
Get " MT GPS" app from Google Play Store } All free.
Get "MobileUncle" app from Google Play Store /
Go to Your GPS and mark everything ON.
Use FasterGPS and change your GPS Zone. i.e. Europe/Portugal
Use MT GPS to download the EPO Files.
Use MobileUncle, click on engineer mode, again on engineer mode (mtk),
sweep to the left until you find YGPS, click on it, then on information,
down you'll see hot, full and AGPS restart, follow this order and click on them.
Go back and click on satellites, and that's it...
Personally i use Sygic v14.02, it's the best to find satellites and a very quick fix.
But you use whatever you wish.
Click to expand...
Click to collapse
Olá amigo, i´ve tryed everithing for my thl w8s and with no results, i will try the aluminium strip and post results.
I followed through your tutorial except this part:
HTML:
<float name="nTargetAreaGeolat" value="nn.nnnnn" />
<float name="nTargetAreaGeolng" value="nn.nnnnn" />
It is not present on my file, so I thought it would be best not to add some hardcoded GeoRef, is it needed for something special?
Disabling EPO gave me an accuracy close to 3.0, with EPO enabled accuracy remained on 4.5.
Great work!
NunoFilipeSantos said:
I followed through your tutorial except this part:
HTML:
<float name="nTargetAreaGeolat" value="nn.nnnnn" />
<float name="nTargetAreaGeolng" value="nn.nnnnn" />
It is not present on my file, so I thought it would be best not to add some hardcoded GeoRef, is it needed for something special?
Disabling EPO gave me an accuracy close to 3.0, with EPO enabled accuracy remained on 4.5.
Great work!
Click to expand...
Click to collapse
I did the above combination on a FAEA F2 (MT6589)
Tried the same on a Jiayu G4 (MT6589) and worked again beautifully, 3.4 Accuracy without EPO enabled.
In my ROM (MT6589T soc), 2 of the files are missing:
Code:
/system/etc/gps.conf
/data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
I know i can create gps.conf (seen it in some custom roms) but don't know about the other file?
Also, there is /system/etc/epo_conf.xml which seems to enable epo.
Should that be changed also?
Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<epo_profiles version="1">
<!-- The following parameters are provided for customer to
configure EPO default value.
-->
<!--
epo_enable:
Wether to enable EPO when device first boot up.
auto_enable:
Wether to enable EPO auto download feature when device first boot up.
update_period:
Update period, the unit is minute. if the value is set to "4320",
then it will update EPO file per 3 days (3 days = 4320 minutes).
The minimal value of update_period should not be less than 1440 (1 day).
-->
<epo_conf_para
epo_enable="yes"
auto_enable="yes"
update_period="21600"
/>
</epo_profiles>
major issue
I have a Jiayu G3C a Chinese phone it's running on android 4.2.2 and I believe it's the latest version fir this phone..the processor is MediaTek 6582
problem is EVEN IF SWITCH OFF the GPS so long as DATA is turned on it will keep on searching for gps. if I'm on Wi-Fi this problem doesn't happen...now I bought the phone due to its low cost, DUAL SIM + massive 3000mAh battery..but this battery is drained massively because of this bug. I can't enjoy the very first reason why I bought the phone. I went to engineering mode tried to disable AGPS and save the settings but the settings don't actually get saved n the bug continues to exist
The /system/gps.conf file didn't exist, till i got FasterGPS. I actually set the all the values recommended on FasterGPS as it has all the options recommended here. Why didn't it exist before? Any problem to set it this way?
The file /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml doesn't exist as well. What should i do?
Oh, i got a THL 5000 and Bshuy's ROM.
Has anyone tried this and can confirm it works?
Got my mum a Jiayu G4S and whilst it locks on pretty quickly just driving a couple of miles up the road leads it to go haywire. Showing us as being in different roads 100's feet away
Thank you so much!
Thank for your amazing post you was light of dark night I test it on my phone (huawi holy hol-u19) and it works perfectly now it can find and fix more than 4 satlite indoors.
I really wonder why a good hardware pulled down by **** software.
anyway thank so much keep on share your exprieces whit us.
can`t get gps on english us
M8 ..thanx for that tutorial !!
I use ZTE Blade Q (mtk6572) and i just set UID for agps_profile.xml and edited this strings
<agps_conf_para
agps_enable="yes"
ca_enable="no"
cdma_agps_preferred="0"
cp_auto_reset="no"
cp_gemini_pref_sim="1"
cp_up_selection="up"
default_cdma_profile="CDMA1"
default_profile="NOKIA"
disable_after_reboot="no"
ecid_enable="yes"
gpevt="no"
log_file_max_num="10"
ni_request="yes"
notify_timeout="8"
roaming="yes"
si_mode="mb"
supl_version="1"
verify_timeout="8"
/>
</agps_profiles>
Click to expand...
Click to collapse
After that i get fix in 2 sec indoor by the window :good:
Mr
Good day,
My apologies if I am out off line! The explanation for a problem with the Mediatek GPS is way over my head.
The problem is that the system lost its boot sequence and stop on a update window. It used to run Windows CE5 but that seems to be gone. The product is a Chinese 4" screen and that is all I've got.
Looking at the thread it seems to me that I must become a rocket scientist to get it to work again and at my age that is not possible. Friends of mine recommend: buy a new one!
Any suggestion?
Tom
PS. Enjoy the new year!
brangryavesoul said:
Sounds a lot of work for such little thing.
I just use 3 apps and about 2 minutes of my time. And GPS works like a charm.
I'm not trying to dis you work friend. But there are simpler ways to do the same thing.
So, here it is:
Get "FasterGPS" app from Google Play Store. \
Get " MT GPS" app from Google Play Store } All free.
Get "MobileUncle" app from Google Play Store /
Go to Your GPS and mark everything ON.
Use FasterGPS and change your GPS Zone. i.e. Europe/Portugal
Use MT GPS to download the EPO Files.
Use MobileUncle, click on engineer mode, again on engineer mode (mtk),
sweep to the left until you find YGPS, click on it, then on information,
down you'll see hot, full and AGPS restart, follow this order and click on them.
Go back and click on satellites, and that's it...
Personally i use Sygic v14.02, it's the best to find satellites and a very quick fix.
But you use whatever you wish.
Click to expand...
Click to collapse
I was so angry with the crapy performance of my MTK 6582 GPS.
This is the only thing that worked for me after so many days. After every reboot I have to manually turn off EPO downloading again, and to update EPO manually butI can live with that.
Thank you so much
Chron0s said:
Mediatek and GPS, ah, how we love trying to get it to work. People have been making foil antennas, tweaking GPS.conf, meddling with NTP and all manner of other things to get it working only to find that the very next day it is back to sullenly sitting there with ne'er a satellite in view. Duff hardware? It seems likely - only it's not. There is nothing at all wrong with the Mediatek GPS hardware. When it is allowed to work, it works as well as anything I've come across, SiRF included.
The problem is assumption on the part of manufacturers and our insatiable lust for a bargain. Assume makes an ass of u and me.
Prerequisites:
Root and the ability to mount /system RW. Sorry if you're one of these people who flatly refuses to root their devices, this is not the solution you're looking for <fx:waves hands/>
Some method of getting into MTK Engineering Mode, whether that's MobileUncle, the "secret" dialler code, GravityBox etc.
A text editor that doesn't follow the MS rule that their line breaks are correct and everyone else+dog is wrong. Notepad++ will do for those of you who cannot break the Redmond shackles. MS Notepad is just going to corrupt the files.
ADB set up and working.
No allergy to XML. If you start sneezing, your eyes start streaming or anything happens to your vision after looking at a few <>'s, please discontinue use.
Step 1: Disable EPO. It's worse than useless for any other starting location but Shenzhen. If you don't believe me, try enabling it again after you complete the rest of the steps. Go into engineering mode and, under Location/Location based service/EPO deselect the obvious checkboxes. This on its own improves matters enormously. With some ROMs you can also do this through Settings by tapping the "GPS satellites" item in Location access and deselect the "Enable EPO assistance" checkbox.
Step 2: Mount /system read/write with whatever method you normally use, whether that's adb remount, adb shell mount -o rw,remount /system or whatever.
Step 3: cd to a clean directory, say MTKGPS.
Step 4: adb pull the following files:
Code:
/system/etc/gps.conf
/system/etc/agps_profiles_conf.xml
/data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
Careful with that last one, it appears in more than one place but it is the com.mediatek.lbs.em version we want
Note the file permissions for these files as they stand on your particular ROM.
Code:
-rw-r--r-- root root 164 2014-06-19 18:29 gps.conf
-rw-r--r-- root root 9502 2014-06-20 15:29 agps_profiles_conf.xml
-rw-rw---- u0_a39 u0_a39 2659 2014-06-20 20:21 agps_profile.xml or
-rw-rw---- 10039 10039 2659 2014-06-20 20:21 agps_profile.xml
The owner of the agps_profile.xml file should be the user's UID. It may be different on your handset. Check it first, please. If any of these differ on your ROM, use the permissions on yours as canonical. This is just a guide.
Step 5: Now we're going to do what FasterGPS does, only a bit more. Edit the gps.conf to look something like this:
Code:
NTP_SERVER=<your country>.pool.ntp.org
SUPL_HOST=supl.nokia.com
SUPL_PORT=7275
INTERMEDIATE_POS=1
ACCURACY_THRES=5000
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_USER_PLANE=TRUE
Purists will note I'm using Nokia's SUPL server here. A little research tells me that Google's SUPL is, well, it's a bit pants - and not just because it's one more way they get PII from you. YMMV, beware of the leopard, and so forth. If you want to use the chocolate factory's SUPL, just swap the SUPL_HOST line to supl.google.com.
Save the file.
Step 6: Now let's undo the mistakes of the manufacturer. Unfortunately we have to delve into some unholy XML for this but don't worry, it's not that difficult despite how daunting the file looks in a text editor. Open agps_profile.xml in your editor.
Make sure the following lines (amongst loads of others that should be left alone) appear as shown:
Code:
<int name="slp_port" value="7275" />
<string name="slp_code">NOKIA</string>
<boolean name="agps_enable" value="true" />
<string name="slp_addr">supl.nokia.com</string>
That's the barebones. Don't exit the file yet. Locate the following lines:
Code:
<float name="nTargetAreaGeolat" value="nn.nnnnn" />
<float name="nTargetAreaGeolng" value="nn.nnnnn" />
See the problem? Try sticking the co-ords from your file into an online mapper. These are passed to the SUPL server no matter what CellID your phone reports. Worse, if you have no cellular radio, it's taken as gospel so you get ephemeris for the middle of China. Useful. This is why cold start takes even longer than it would on a standalone GPS from cold.
Now, what we need to do is set those up for your general location. It doesn't need to be point precise, just a general 0.1 degree lat and long.
IMPORTANT: If you are West of the Meridian, you need to do some jiggery-pokery with your longitude. This file treats the world as a 360 degree ball, so you need to subtract your longitude from 360. For example, if you're 4 deg W of Greenwich, your longitude would be 356.0. 110.3W equates to 249.7. Yes, this number drops as your longitude goes up if you're West.
Save this file.
Step 7: Now let's edit the agps_profiles_conf.xml. This one's fairly easy, just change the end to look like this, with the usual GOOGLE in default_profile if that's your bag:
Code:
<agps_conf_para
agps_enable="yes"
ca_enable="no"
cdma_agps_preferred="0"
cp_auto_reset="no"
cp_gemini_pref_sim="1"
cp_up_selection="up"
default_cdma_profile="CDMA1"
default_profile="NOKIA"
disable_after_reboot="no"
ecid_enable="yes"
gpevt="no"
log_file_max_num="10"
ni_request="yes"
notify_timeout="8"
roaming="yes"
si_mode="mb"
supl_version="1"
verify_timeout="8"
/>
</agps_profiles>
Note cp_gemini_pref_sim can be set to 2 if that's your main SIM that usually has a signal. It is used as the CellID source for aGPS, not the data connection the aGPS data is fetched on.
Save the file.
Step 8: Push the files back with adb and set up their ownership and permissions:
Code:
adb remount
adb push gps.conf /system/etc/gps.conf
adb push agps_profiles_conf.xml /system/etc/agps_profiles_conf.xml
adb push agps_profile.xml /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
adb shell chown 10039:10039 /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
adb shell chmod 660 /data/data/com.mediatek.lbs.em/shared_prefs/agps_profile.xml
adb shell chmod 644 /system/etc/agps_profiles_conf.xml
adb shell chmod 644 /system/etc/gps.conf
Step 9: Reboot and retry your GPS. Once you have checked everything is working, you can re-enable EPO, clear the aGPS data in Engineering Mode and try again just to verify I'm not talking out of my backside. EPO really doesn't help in this guise, at least not in the UK.
In conclusion, these can be made to work. With these changes in place I can get an indoor lock in airplane mode in just under ten seconds a day and a reboot after last using the GPS. You need a rooted device and some bright spark will no doubt automate all of this - I'm no Android hacker so don't look at me. GravityBox would be my guess as it's developed at a remarkable pace - thanks for the app, BTW
I do hope this works for everyone. It would be nice to put this one to bed once and for all. A final note: There may be errors in this. I'm only human. Check, double check, triple check, take backups, all the usual stuff. Flames to /dev/null, please.
Click to expand...
Click to collapse
GPS works ok for me without any change, but will be very slow to start without AGPS which requires a SIM card, or wifi connection. Of course you generally don't have access to AGPS inside an airplane in an underground place or anywhere radio waves can't enter, etc.
Hello xda community
Today I am sharing my knowledge related to the sound modding in android as a way of saying thank you for all the support I received from the xda members in the forums
About myself: I have been working as professional DJ and sound engineer for serious gigs since 15 years.
Goals: This is a general guide to help you understand the fundamentals of sound output in android and how to edit it, then you have to do some research specific to your phone/tablet or experiment on your sound file to have the desired levels. Theorically, this applies to any android phone or tablet, although the values to input will differ from one device to another and from one manufacturer to another. Here I am describing how I boosted the sound in my Xperia Z1, so be aware that applying the same values on a different phone might get different results.
Why I wrote this: Most of the sound mods will not work if you have a different android version than the one of the modder because the architecture of the sound paths might differ from one android version to another, even if it's exactly the same device, so it's vital to be able to boost your sound on your own if all the mods didn't work for you or no mod exists for your device. Sometimes also, a modder wishes to create a sound boost mod but doesn't know how to get the maximum loudness without losing quality. This will no more happen if you read and understand this guide
Note: I am not responsible if you cause any damage to your device or your sound stops working, you are the only one responsible for what you do with what is described in this guide.
Requirements: rooted phone, file explorer and note editor (I use Es File Explorer as it has both)
I wrote this guide to clarify what needs to be edited to get a louder sound without losing quality, so here are the facts:
To get started, use a file explorer and navigate to /system/etc and locate a file named mixer_paths.XML
I recommend that you make a copy of this file in case you need to restore it later if you get undesirable results with your experiements.
Open it using a note editor and locate the sections of your interest, usually there is a title for each section with the values coming right under it, e.g "Headset volume" or "microphone volume"
Starting from here you will have to find out the values specific to your device either by finding them in the forums (if you are lucky) or experimenting by editing the values I am about to explain.
HPH (amplifier/electric output) vs RX (digital/signal):
HPH: Basically, the best way to get a volume boost without decreasing the sound quality is to increase the amount of electric power that your device outputs, this will have the effect of feeding your headphones with more power which will generate more acoustic pressure (DeciBels/db) without degrading the quality (provided you didn't reach the limits of your headset). To do this, just set your HPHR and HPHL to as high as your device allows.
Rx: This is somehow the input signal of your sound, increasing this value will boost the source signal which will create distortion and saturation, this will result in a sound that will feel louder because of the generated compression, but the cost is a loss in dynamics and quality, the loss is proportional to the increase in the signal. In other words, increasing the RX value will distort and saturate the sound, you will have a louder but poor sound quality with a huge loss of bass and a flat sound, with the possibility that this will fry/damage your phone sound card and/or headphones at high volumes because of the saturation generating constant electric current which could overheat the wires/transistors beyond what they were designed to take. Add to this a higher risk to internal ear damages.
My advice is to start increasing the HPH value to the highest possible value first, save the file, reboot and see if the sound boost is high enough for you. If that was not loud enough, then try increasing the RX value by +3, save, restart and try again.
Facts: The loudness doubles at every +3 db, which means RX 85 should be 2 times louder than RX 82
Conclusion: The first step to boosting your sound is to increase the HPHR and HPHL. If more loudness is needed, increase the RX value gradually by +2 or +3 until you reach the desired loudness (try to find a good balance, I wouldn't recommend going more than +3 beyond your current RX value). Keep in mind that too much increase in RX will make you lose bass and sound quality, at that point don't expect the equalizer (EQ) of your music player to give you more bass or improve your sound quality because you have saturated/damaged the sound at its origins.
I hope this will help you set your sound at the desired levels without damaging your sound quality or devices or headphones or ears.
Note: I am using these settings on my Xperia Z1 with my Sony MH1C headset, these values should work for the Xperia Z1 Compact because it has a similar hardware. Theorically, this guide is universal and can be adapted to work with any android device, the values in mixer_paths.xml might be different on other devices but the boosting principle is the same.
More infos:
HPHR = Right output
HPHL = Left output
People with impaired hearing can set up these 2 values differently. E.g: HPH? 20 should be for the weak ear, set the value for the strong ear at anything below 20 until you reach the balance between the 2 ears.
Edit for some CyanogenMod Based ROMs: On my S4 mini running a Resurrection Remix Marshmallow ROM, which is based on CM, I didn't find the mixer_paths.xml file, instead I found a file which contained similar settings for the sound.
The file is named snd_soc_msm_2x and is situated in : system/etc/snd_soc_msm
If you found this useful, please click on the "thanks" button below to thank me That will make my day
Additional Information
Here is an additional post worth reading:
Quote:
Originally Posted by barkohba
Ok so here's the deal with (truly) increasing the ANALOG (which is what you want) volume of your xperia.
For starters, I want to specify that what I am about to present is valid, to my knowledge, to Xperia Z1, STOCK (I don't know how it behaves for other firmwares like CM11) and only rooted.
Also, I am using an MDR-1R (Sony) headset. These are high end over the ear headsets, and what's important to note is that they're made to handle, among a bunch of other sound details, high volumes without distortion,
HPH vs RX (digital):
If you increase the RX volumes, you will get a digital boost. What that means is basically you WILL get a volume boost, but that boost comes with the cost of quality, and will clearly deteriorate the sound, making the sound feel very uncontrolled and distorted. That is not normal at these volume levels with the headsets that I use, due to the fact that when I connect them to an iMac (which has a much more powerful and higher volume than what can be achieved on a smartphone/mp3 player due to its high quality sound card) the sound keeps all of its details intact, with NO distortion.
The HPH (L/R) is what you're after. This increases the analog volume (aka true volume), which raises all of the frequencies equally, giving you a real volume boost, without distorting the sound (if you have a low end headset, at high volumes the sound could sound distorted not due to the phone, but because of the headset drivers/quality). For reasons I can not explain, raising the value above 20 (I actually tried it with 23 and 25, but I have the feeling even at 21 the same thing happens, though you are free to try and report on your findings) makes the volume drop way below standard. So what you want to do is increase both HPH levels to 20!
Now in my case, and this is valid for high end headphones (at least to my knowledge), setting the HPH to 20 and slightly increasing the RX to 85 helps a bit, as the lows and especially the mids get a small boost without distorting the sound, making my MDR-1Rs sound as good as possible on a mobile device without a portable amplifier.
Basically, for me, with the aforementioned headset, the best settings is HPH-20 (both), RX-85 (both) .
You can fell free to play around with these settings, but the bottom line is, for most headsets, especially the in ear ones that come bundled and other low or mid range headsets, the best settings is increasing the HPH volumes up to 20 (or less if at max volume the headsets give out uncontrolled and distorted sound), and completely leaving the RX alone, as increasing it to levels above 85 basically destroys the sound quality, and we don't want that.
Of course, if you have high quality over the ear headsets, which tend to have pretty low volume on mobile devices due to their large drivers which need a lot of power, the absolute best option to get the most out of them is buying a mobile amplifier. Of course such amplifier cost around 600 dollars, and are specifically targeted for rich audiophiles or musicians. Sony makes on of the best portable amplifiers out there, but it's an expensive proposition since it costs as much as a flagship xperia, and is even a bit larger than one (though it does come with a special straps to hang on to your device)
Hope that helped!
Source: http://forum.xda-developers.com/showthread.php?p=62188768#post62188768
If a moderator could edit the title and correct the last word to "quality", that would be appreciated Thank you in advance
This has been tested by me and I confirm that it's working on:
Samsung Galaxy S3 i9300 (Jellybeans 4.3 stock rom, Kitkat 4.4.x and lollipop 5.x.x various custom roms)
Sony Xperia Z1 (stock lollipop 5.x.x)
I never tested this on ICS or previous android versions, but it should work if there is an mixer_paths.XML file
Happy modding and feel free to post if you have further questions, I will be more than happy to help.
Please no questions related to what values you should set to your device, this is impossible to answer if you have a different device than mine, obviously I don't own every device out there to experiment with
Very clear and well explained......One thing to mention......
I had a look in the system directory for the file (and found it)......it's in a directory that my file explorer classes as 'read only'.......
Not sure if it's necessary to change it to 'read/write' before you start?.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
Very clear and well explained......One thing to mention......
I had a look in the system directory for the file (and found it)......it's in a directory that my file explorer classes as 'read only'.......
Not sure if it's necessary to change it to 'read/write' before you start?.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Welcome Keithross39 Glad you joined my thread
I don't know what file manager you're using, but I have never had issues or warning messages (about read/write requirements) using Es File Explorer. I don't think it would harm anything if you turned the file from "Read-Only" to "Read and Write". Alternatively, you could just copy the file to another directory, then edit the parameters you wish to adjust (boost) using a note editor and save, then you can paste the edited file on the same folder and you will be asked by your file manager whether you wish to replace the file or add a copy, just select to replace and it should be it, then you can just restart the phone and see if there is an improvement on the things you modified (headset, speaker, microphone, bluetooth headset, alarms, or anything else you edited).
If you encounter a problem, just place the original (untouched) file back to that folder and overwrite, restart and you're back to stock values.
PS: For a louder sound, I don't recommend using apps from the play store because they give false claims, they just compress your sound to make it sound louder but you lose the quality, on the top of that you may get bugs or shorter battery life if the app is running in the background. My trick doesn't require any app (other than your usual file manager and note editor) and the results are cleaner louder sound with a stable system, and these modifications will not use any additional resources (cpu or ram) since this is part of the native boot process.
On what device are you planning to boost your sound? If you wish, try posting your mixer_paths.xml file here and I will see if I can edit it to suite your needs (specify what you wish to boost in your reply)
I currently use Viper4Android with a 6 db gain boost (the maximum boost the app allows) across both speaker and headphones for alarm volume, and music/videos (headphone and speaker)
Never used sound mods from playstore. I have purchased Poweramp but I don't even use the equaliser functions built into that.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Here's my xml file (Galaxy s5, f variant running stock 4.4.2)
The +6 db is fine for speaker, but I'd be looking for more out of the headphones....View attachment mixer_paths.xml.zip
keithross39 said:
Here's my xml file (Galaxy s5)
The +6 db is fine for speaker, but I'd be looking for more out of the headphones....View attachment 3475791
Click to expand...
Click to collapse
I have some good news for you
I took a look at your xml file and I wanted to know what would be the maximum value I could set to certain various, so I googled and I found a thread which already implemented these changes in a mod with various boost levels. The files in the thread are flashable zips (twrp or cwm or any other will do). Alternatively, you can unzip the zip of your choice and go inside the system folder then etc and copy the xml file from there and replace manually the one in your device's system/etc folder by overwriting it.
Here is the link to the mods: http://forum.xda-developers.com/showthread.php?t=2729652
As I already mentioned before, sometimes mods will not work if you happen to have a different android version or a different device, so what I did is to open the xml you provided and open the xml from this mod side by side, I compared them line by line to make sure that all the lines from the mod are the same as the ones from your file (a missing or different line would lead to a possible crash or missing feature or error messages due to a bad linking), I was pleased to see that everything from this mod is 100% the same as in your file, it's just the values that are increased comparing to your file (since this is a sound boost mod). So I can assure you that this mod will work on your phone, just make sure to temporarily disable viper4android to avoid any possible conflict, try the different boost levels until you find the one that suits you most, then you can try to enable viper4android again in order to equalize your sound, it shouldn't cause any conflict in my opinion.
As to what I think you should choose, from what you mentioned in your last post I would say the V1 lite or the V4 Lite would be perfect for your needs.
Don't hesitate to ask me if there is anything else I can help you with And please tell me if it worked for you
PS: make sure you grab the KitKat version of the mod, not the lollipop, as I think you're still running KitKat and that's the version of the XML I checked
Note: It looks like Samsung engineers are very smart in the way they set their default sound values, I say this because it looks like the HPHR and HPHR levels are already set to their maximum (Most other manufacturers have these lowered, such as what I found out in my Sony Z1). So what they did is setting the amplifier to the maximum value and reduce the gain value well below the norms (this is the RX value) in order to avoid distortion and/or possibly to be in conformity to the international laws that forces manufacturers to set a volume limit to avoid hear damage. So basically, all that needs to be done is to increase the gain through the RX values knowing that there is a point where going beyond will affect the sound quality. I think V1 lite and V4 lite will be under or equal to the right balance between loudness without losing quality. V2 medium may be equal or over the balance level, the increase in loudness will be big but the decrease in sound quality might not be noticeable to the average user, so that's possibly still a good value to consider if V1 lite was not loud enough for you, although I don't recommend it. V3 is a big NO for me, I guess you already know why, lol
Thanks for the heads up on that thread.......read the first 25 or so pages and found a headphone only zip.....
Extracted it and pushed the new xml file to the correct location (deleted the original), kept viper enabled (mentioned in the thread that viper and the boost mod can be used together) and now I have the volume combo that best suits my needs.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
Thanks for the heads up on that thread.......read the first 25 or so pages and found a headphone only zip.....
Extracted it and pushed the new xml file to the correct location (deleted the original), kept viper enabled (mentioned in the thread that viper and the boost mod can be used together) and now I have the volume combo that best suits my needs.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I am really happy that your sound is better, I wasn't sure how viper4android works and I wasn't sure combining it with the mod will be giving any improvement over the already boosted sound from the mod alone, but I am glad it worked fine
The crazy wife stole all my time this weekend, I lost hope on rooting my S5, now I'm jealous that you have the mod and I don't hahaha, just kidding. I am truly glad that you have it boosted, I will let you know when I get my S5 rooted, perhaps I will enquire some tips from you regarding what ported apps I shouldn't miss
Till then, have fun in Oxford
Ps: I did a private party once in Oxford, it was great I believe it was in 2007 when I was still living and DJing in London. Germany is kind of boring in comparison and I am planning to return to London in February 2017, I have some kind of contract blocking me here for another 15 months
volume boost speaker and headphone z3c
thanks for the tecnical explication
i want volume boost speaker and headphone in my z3 compact whit 4.4 but have mooore value in the xml file help me please
brattak said:
thanks for the tecnical explication
i want volume boost speaker and headphone in my z3 compact whit 4.4 but have mooore value in the xml file help me please
Click to expand...
Click to collapse
Hello and thank you for reading my article
I will try to help you as much as I can but you will possibly have to edit the values on your own to set how loud you like your sound to be. Also, I don't have the same phone, so I can't do more than assist you.
So here is a mod for the z3c on lollipop which I advise you to download in order to have an idea of the values you can change and up to what limit. I can not say whether or not this mod keeps a good sound quality when getting a boost simply because I don't own an Xperia Z3c device to try it, sorry about that, but people reported that it was loud and clear.
https://mega.nz/#!b8M1xQ4I!Twhozp_4XZhMgFlgSPkkc9QZCpIony0K0fjtKzdlyfQ
If it was up to me, I would NOT use the lollipop file from the Z3c directly on a kitkat rom because there might be a very slight difference which would make something not work at some point. What I mean is that the mod might work to bring your volume louder when listening to music, but then in a month you decide to skype with someone and you will not get any sound, you will be wondering why and you will possibly not think that it's due to the mod.
This mod has parameters written in a case-sensitive text, each line is linking an instruction to something specific either in the software or the hardware level. If a line is missing or has values unsupported by your device, you will have a particular parameter which may not work at all, or worse case senario is that you get no sound at all. This can be reverted if you just backed up your original sound mixer file.
What I would do:
I would download the lollipop boosted sound mixer file for the Z3c from the link I provided above, open it in a text editor. Extract the same file from the folder system/etc of your phone and open it in a text editor.
Now you have the two files side by side, you can compare the lines and the values, you can then copy the values from the lollipop file and paste them on the file you extracted from your phone. Make sure you only copy/paste the numbers, as they represent the values, don't modify the text.
Once you finish this, you can save your edited file (don't change the name of it), and paste it to system/etc on your phone. Reboot and voila, you have the mod on your phone, 100% guaranteed to be compatible and will not cause you any bugs in the future, unlike if you used any Mod.
Could you please report if it worked for you?
Also, if it works for you, you will be the creator of a z3c kitkat sound boost mod, feel free to post it here so that people with your device and rom can benefit from it
If my post was helpful to you, just press the "Thank you" button
I also found this thread which seems to have the boosted file for the z3 (not compact) on kitkat. You can unzip the archive and find the mixer_paths.xml file, open it side by side with the file you extracted from your phone and copy paste the corresponding numbers (values) without altering the text.
http://forum.xda-developers.com/z3/development/z3-speakers-incoming-call-headphones-t2889964
Let us know the results
thanks for help i use this for compare ( http://www.corefiling.com/opensource/xmldiff.html) and have many difference but i only mod in my file the value 84\95 other i dont know......its correct ?
brattak said:
thanks for help i use this for compare ( http://www.corefiling.com/opensource/xmldiff.html) and have many difference but i only mod in my file the value 84\95 other i dont know......its correct ?
Click to expand...
Click to collapse
I had a look at your original file and the one which I shared with you earlier and it seems the main differences are the 84 which was increased to 95. In my opinion, this is too much and will result in a loss of quality. As I explained in my first post, changing the value with +3 will double the volume, therefore I would advise you to try changing your values from 84 to 87 in the first place, save and put the file on the right directory, reboot and listen to something other than hard rock and see if the volume is loud enough. If you are almost happy, try changing the values to 88 or 89. If you feel you are still not satisfied, continue increasing the values but keep in mind that every increase you do will generate further distortion which degrades the quality, at some point you will hear it even if you are not a sound engineer.
Also, you may not want to boost everything and rather just boost the headphone volume for music, then try to leave the default parameters for everything except the headphones that you can set to your preference.
Thank you for providing the link to the tool to compare 2 files, it looks useful and I will possibly use it in the future.
Let me know what is the best value in your opinion, and try to share the file so that others benefit from it
Don't forget to hit the thank you button if my answer was helpful
Ok
Inviato dal mio D5803 utilizzando Tapatalk
brattak said:
Ok
Inviato dal mio D5803 utilizzando Tapatalk
Click to expand...
Click to collapse
Hello Brattak
Did you manage to get the boost working on your Z3c with Kitkat?
I would like to help you, so feel free to ask all your questions or let me know if you need help
Forza Star Gate SG1
Thanks i set first 84 before 95 but the sound not have difference
I download another sound mod for z3c for lollipop extract and compare in this mod the value is 125.......now i try increase over 100 but 125 is very high.....
Sorry for my english im italian ?
Inviato dal mio D5803 utilizzando Tapatalk
brattak said:
Thanks i set first 84 before 95 but the sound not have difference
I download another sound mod for z3c for lollipop extract and compare in this mod the value is 125.......now i try increase over 100 but 125 is very high.....
Sorry for my english im italian
Inviato dal mio D5803 utilizzando Tapatalk
Click to expand...
Click to collapse
He he he, don't worry about your English, I think most people managed to understand
I am sorry if the boost was not loud enough for you, but it's not really a problem since you can change the values to higher numbers and get the loudness you want
It looks like the values in the Z3c are different from the Z1 and that's why I can not give you exact numbers, but you can try a setting of 100 and see if it suits your needs. You can then try 110 and decide if you want louder with 115 or want to go lower with 105
I hope it works out well for you and that everyone can learn from your experiment
Don't forget to hit the thank you button if you want to thank me
quick intro..
I bought the Lenovo m8 FHD. Great tablet, Im using mine as a car head unit to replace a buggy old Nexus 7 with Timur's kernel. I was gonna get a Galaxy Tab A or any Galaxy but none of the sizes woud fit (too wide). When I discovered the Lenovo was the same width with more height, much better spec it was a no brainer. Its perfect for a car head unit! Rooted with magisk, I bought a LavaSync OTG hub which doesn't require root but bought it anyway (American company, google it). This provides USB audio out to my miniDSP. Use tasker to set up any automated options, ie when powered [do this] else [sleep...]. Simples
I just need to increase volume steps then I can install the thing -
Iv tried to increase the volume steps using apparently the most popular solution - ro.config.media_vol_steps=30 (30 is required) in build.prop and deafualt.prop as running Android 10. After a reboot I now have 30 steps but from 1 to 15 is mute to full volume and 16 to 30 is also mute to full volume! Im still learning here but where should I be looking to find these settings?
I see, using ADB, the 'ETC' folder (file) has alot of audio related files but just not sure where this device keeps the config settings for something like this?
Thanks in advance for any help
Moving on then. My next step to solve this is to change permissions and copy mmcblk0 to my windows machine and use an app to explore it at leisure. I will update anything I find..
mamba76 said:
quick intro..
I bought the Lenovo m8 FHD. Great tablet, Im using mine as a car head unit to replace a buggy old Nexus 7 with Timur's kernel. I was gonna get a Galaxy Tab A or any Galaxy but none of the sizes woud fit (too wide). When I discovered the Lenovo was the same width with more height, much better spec it was a no brainer. Its perfect for a car head unit! Rooted with magisk, I bought a LavaSync OTG hub which doesn't require root but bought it anyway (American company, google it). This provides USB audio out to my miniDSP. Use tasker to set up any automated options, ie when powered [do this] else [sleep...]. Simples
I just need to increase volume steps then I can install the thing -
Iv tried to increase the volume steps using apparently the most popular solution - ro.config.media_vol_steps=30 (30 is required) in build.prop and deafualt.prop as running Android 10. After a reboot I now have 30 steps but from 1 to 15 is mute to full volume and 16 to 30 is also mute to full volume! Im still learning here but where should I be looking to find these settings?
I see, using ADB, the 'ETC' folder (file) has alot of audio related files but just not sure where this device keeps the config settings for something like this?
Thanks in advance for any help
Moving on then. My next step to solve this is to change permissions and copy mmcblk0 to my windows machine and use an app to explore it at leisure. I will update anything I find..
Click to expand...
Click to collapse
******* *** * *if anyones interested amongst the flood of responses from this thread you need default.prop from Vendor folder not root folder ******** ** ****
mamba76 said:
******* *** * *if anyones interested amongst the flood of responses from this thread you need default.prop from Vendor folder not root folder ******** ** ****
Click to expand...
Click to collapse
** actually no it does the same thing- 2 lots of volume bars stacked on top of each other, 0-15+0-15 = 30 steps, fail!, it should be 0-30=30 steps,