Hi there,
since i got my Kaiser i always had a problem with the low BT Volume. I tried many fixes from here but noone works for 100%.
The only lud roms were the PDA Corner ones.
So i made my own
Install the attached cab and restart your device. Then sound will be fine and loud.
If you use SRS Wow it won't work after installation, cause i had to change the drivers in registry.
@MODS: CAN WE MOVE THIS TO DEV/HACKING SECTION? CAUSE I THINK THIS COULD WORK FOR ALL DEVICES!!!
what exactly does this do (on your phone, what does it change, or is it a program always running?) and if it makes things worse is it uninstallable ? (since I see it's a cab).
Mr. Kayne said:
what exactly does this do (on your phone, what does it change, or is it a program always running?) and if it makes things worse is it uninstallable ? (since I see it's a cab).
Click to expand...
Click to collapse
The .cab file just contains registry settings and the file 'AudioPara3.csv'. As far as I can tell the 'AudioPara3.csv' is identical to the one already in my ROM (stock-ish 5.2.19212), however there are quite a few new registry entries that I can't see in my ROM
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\A2DP\Settings]
"SampleRate" = 48000
"BitPool" = 0
"UseJointStereo" = 0
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"PowerSave" = 1
"ConnectHFOnCall" = 1
"Capability" = 101
"BTAGExtModule" = OEMAGW.dll
"SupportCLI" = 0
"BTAGPBModule" = \Windows\BthAGPhonebook.dll
"NoRoleSwitch" = 1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd]
"GainADC_LoudSpkMIC_12h" = 60
"OldDriver" =
"Dll" = bta2dp.dll
"SPKVol_NotPhoneCall_02h_06h" = 0
"SPKVol_PhoneCall_02h_06h" = 3
"HPVol_PhoneCall_04h" = 4
"GainADC_BluetoothMIC_12h" = 33
"GainADC_HeadsetMIC_12h" = 42
"GainADC_ReceiverMIC_12h" = 55
"3DEff" = 0
"MicGain" = 39
"AGC" = 0
"Treble" = 0
"Bass" = 0
"IClass" = {A32942B7-920C-486b-B0E6-92A702A99B35}
"Sysintr" = 25
"Flags" = 65538
"Index" = 8
"Order" = 8
"Prefix" = WAV
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
"OldDriver" =
"Dll" = Wavedev.dll
"Flags" = 0
"IClass" = {A32942B7-920C-486b-B0E6-92A702A99B35}
"DACVol_0Ch" = 7
"SPKVol_NotPhoneCall_02h_06h" = 0
"SPKVol_PhoneCall_02h_06h" = 3
"HPVol_PhoneCall_04h" = 4
"GainADC_BluetoothMIC_12h" = 33
"GainADC_HeadsetMIC_12h" = 42
"GainADC_ReceiverMIC_12h" = 55
"3DEff" = 0
"MicGain" = 39
"AGC" = 0
"Treble" = 0
"Bass" = 0
"Sysintr" = 25
"Priority256" = 149
"Order" = 11
"Index" = 1
"Prefix" = WAV
Andy
The .cab file just contains registry settings and the file 'AudioPara3.csv'. As far as I can tell the 'AudioPara3.csv' is identical to the one already in my ROM (stock-ish 5.2.19212), however there are quite a few new registry entries that I can't see in my ROM
Code:
Click to expand...
Click to collapse
Yes thats right, the most of the cab are just reg keys, there is no app or similar that runs in background. The audiopara.csv is from an oldr att rom.
First i trie every fix around here on xda-developers, but no one of them worked properly. Then i mixed some of the together, and i noticed an improvement. Some days ago i got the csv file and replace it with the one in my actually rom and volume was very high. I checked this on several roms and for me it seems to work. Some of the reg keys don't do anything with the volume but they improve the sound quality over bluetooth.
Would be great if some of you could post their results.
Don't matter, i don't know if you can completly uninstall this, but there is no key or so that will make bt or so not work anymore.
Also it would be great if you could send my you audiopara.csv files and the reg keys of the rom you are usin (if it's loud), so i try to improve it more and more, or am i the only one with bad volume?
If anyone is using a pda corner rom at the moment, please send me the reg keys and the audiopara3.csv cause theese roms had the best sound quality and volume with bt.
well I tried it out and I guess my bluetooth is slightly louder. ( I checked it before and after)
No adverse effects.
Solace v1 (ROM version 3.29.707.0 WWE)
Radio 1.70.19.09
Windows Mobile 6.1 of course. Hope that helps in some way.
Thanks my brother,i'll test your cab.
Hi Jecky
Thanks for this !!!!!!
To be honest, can't differentiate a "absolutely louder" feeling.
Can you tell us how to modify / what / which part to modify by ourselves to alter the volume up or down? Thanks.
My BTHS is Omiz2099, when matched to ELF is loud as hell. But when match to Asus P552w GalaxyMini2 is soft as hell.
Hence this is much appreciated. eventhough not feeling significantly, but Thanks still.
Did u changed the parameters of the sound variables to their maximum values in that registry tweak ????
BT headset micro_speaker volume change
BT headset's micro_speaker volume hasn't increased, but MIC pickup has, after I changed everything to "100".
I notice there isn't any BT heatset micro_speaker's volume control.
i.e. I suspect need "BTVol_PhoneCall_??h_??h" = ??
but I don't know how many h or whatever to use behind.
Anyone can shead of light?
This project started becaues at night the Atrix display is far too bright. I've successfully compiled the kernel (faux's) and made some changes to the display driver, and from there I found a world of useful info and hacks which enhance our display.
Kernel Update
I have compiled faux's kernel and attached it to this thread. please note, this is NOT the cyanogen version of the kernel, only standard ROM's that use faux123's kernel. i can compile the cyan kernel next. this kernel change is simple, it defaults both the display and buttons to the lowest 5mA display mode. this way a reboot puts you right into the lowest mode, and you can manually set reg 17 to higher as-needed. reg 17 will stay set until the next next reboot.
NOTE: THIS RAMDISK WAS MINE PULLED FROM THE STOCK ROM "WITH EXTRAS", SO PLEASE IF YOU TRY A DIFFERENT ROM HAVE A NAND BACKUP READY TO RESTORE JUST IN CASE!!! I HAVENT TRIED THE OTHER ROMS.
it is the zImage and Ramdisk, so it is flashed like:
boot into fastboot (volume down and power on, then vol down till fastboot shows, then vol up to select).
Code:
moto-fastboot flash:raw boot zImage ramdisk.gz
sorry it's not a flashable zip. i purposely uses RAR so nobody tries to flash it with CWM.
Update - The brightness limit of 30 has now been removed:
The autobrightness can now go all the way down to 00 even with your stock kernel and ROM. The limit was coming from the frameworks. I've re-compiled the frameworks for the stock ROM and also for Cyan pre-beta 3. There are 2 frameworks attached to this post, stock and cyanogen. download from this post and unzip your correct file for your ROM, and ADB push the files to your phone:
Code:
- boot to recovery
- mount system
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
Update - Cyanogen Pre Beta 4 frameworks added
unzup and flash with adb shown above.
Here is what is found in the frameworks, under res/values/arrays.xml:
Code:
10
50
100
150
200
700
1300
2000
3000
4000
5000
6000
7000
8000
9000
20
20
34
46
62
81
100
119
137
138
153
170
187
206
221
255
255
255
255
192
128
0
0
0
0
0
0
0
0
0
0
0
I changed the first value in config_autoBrightnessLcdBacklightValues from a 20 to a 2, and now in auto brightness mode the screen goes all the way down to 2.
Update:
We now have the proper official data sheet (link below) thanks to Saltinbas.
Documentation - Data Sheet
Our backlight chip is the lm3532, which is basically same as lm3530 which is used in the moto droid. i've read the entire data sheet twice and still trying to grasp everything. the data sheet can be found here:
http://www.national.com/ds/LM/LM3532.pdf
Not all registers are exactly the same, so some reverse engineering is needed.
Source Code (Kernel)
The relevant kernel source code:
leds-lm3532.c - Driver
leds-lm3532.h - Headers
board-mot-lights.c - Initialization
What I've Tried So Far
The first change I made was in board-mot-lights.c.
Code:
struct lm3532_platform_data lm3532_pdata = {
.flags = LM3532_CONFIG_BUTTON_BL | LM3532_HAS_WEBTOP,
.init = disp_backlight_init,
.power_on = disp_backlight_power_on,
.power_off = disp_backlight_power_off,
.ramp_time = 0, /* Ramp time in milliseconds */
.ctrl_a_fs_current = LM3532_26p6mA_FS_CURRENT,
.ctrl_b_fs_current = LM3532_8p2mA_FS_CURRENT,
.ctrl_a_mapping_mode = LM3532_LINEAR_MAPPING,
.ctrl_b_mapping_mode = LM3532_LINEAR_MAPPING,
.ctrl_a_pwm = 0x82,
};
I changed lines 99 and 100 to this:
Code:
.ctrl_a_fs_current = LM3532_5mA_FS_CURRENT,
.ctrl_b_fs_current = LM3532_5mA_FS_CURRENT,
Success
And bingo, display brightness reduced significantly lower than stock. the display has many different "modes" and I went right to the lowest on the list. Here are the brightness modes which can be found in the header file leds-lm3532.h:
Brightness Config Values (Header File)
Code:
#define LM3532_5mA_FS_CURRENT 0x00
#define LM3532_5p8mA_FS_CURRENT 0x01
#define LM3532_6p6mA_FS_CURRENT 0x02
#define LM3532_7p4mA_FS_CURRENT 0x03
#define LM3532_8p2mA_FS_CURRENT 0x04
#define LM3532_9mA_FS_CURRENT 0x05
#define LM3532_9p8mA_FS_CURRENT 0x06
#define LM3532_10p6mA_FS_CURRENT 0x07
#define LM3532_11p4mA_FS_CURRENT 0x08
#define LM3532_12p2mA_FS_CURRENT 0x09
#define LM3532_13mA_FS_CURRENT 0x0A
#define LM3532_13p8mA_FS_CURRENT 0x0B
#define LM3532_14p6mA_FS_CURRENT 0x0C
#define LM3532_15p4mA_FS_CURRENT 0x0D
#define LM3532_16p2mA_FS_CURRENT 0x0E
#define LM3532_17mA_FS_CURRENT 0x0F
#define LM3532_17p8mA_FS_CURRENT 0x10
#define LM3532_18p6mA_FS_CURRENT 0x11
#define LM3532_19p4mA_FS_CURRENT 0x12
#define LM3532_20p2mA_FS_CURRENT 0x13
#define LM3532_21mA_FS_CURRENT 0x14
#define LM3532_21p8mA_FS_CURRENT 0x15
#define LM3532_22p6mA_FS_CURRENT 0x16
#define LM3532_23p4mA_FS_CURRENT 0x17
#define LM3532_24p2mA_FS_CURRENT 0x18
#define LM3532_25mA_FS_CURRENT 0x19
#define LM3532_25p8mA_FS_CURRENT 0x1A
#define LM3532_26p6mA_FS_CURRENT 0x1B
#define LM3532_27p4mA_FS_CURRENT 0x1C
#define LM3532_28p2mA_FS_CURRENT 0x1D
#define LM3532_29mA_FS_CURRENT 0x1E
#define LM3532_29p8mA_FS_CURRENT 0x1F
Then i discovered that we don't even need to compile a new kernel to access this chip. We have the proper sysfs files already given to us by motorola engineers. here are some useful commands:
Terminal Commands
Use terminal app and navigate to:
Code:
su
cd sys/bus/i2c/drivers/lm3532/0-0038/leds/lcd-backlight
you can set any of the above modes you want. as an example let's say I want to set to maximum brightness mode, use the corresponding hex value in the header file from earlier, and type:
Code:
echo 17 1F > registers
that sets register 0x17 (the brightness register) with value 0x1F (the maximum brightness value from the list).
To set the minimum brightness:
Code:
echo 17 00 > registers
now for those of you who would like to help out with this and test other registers, you can see all register values by typing:
Code:
cat registers
that brings up this:
Code:
OUTPUT_CFG_REG (0x10) = 0xD4
START_UP_RAMP_REG (0x11) = 0xC0
RUN_TIME_RAMP_REG (0x12) = 0xC0
CTRL_A_PWM_REG (0x13) = 0x86
CTRL_B_PWM_REG (0x14) = 0x82
CTRL_C_PWM_REG (0x15) = 0x82
CTRL_A_BR_CFG_REG (0x16) = 0xE3
CTRL_A_FS_CURR_REG (0x17) = 0xFF
CTRL_B_BR_CFG_REG (0x18) = 0xE3
CTRL_B_FS_CURR_REG (0x19) = 0xE4
CTRL_C_BR_CFG_REG (0x1a) = 0xF1
CTRL_C_FS_CURR_REG (0x1b) = 0xF3
ENABLE_REG (0x1d) = 0xFF
FEEDBACK_ENABLE_REG (0x1c) = 0xF9
ALS1_RES_SEL_REG (0x20) = 0xE0
ALS2_RES_SEL_REG (0x21) = 0xE0
ALS_CFG_REG (0x23) = 0x44
ALS_ZONE_REG (0x24) = 0xF0
ALS_BR_ZONE_REG (0x25) = 0xF8
ALS_UP_ZONE_REG (0x26) = 0xF8
ZB1_REG (0x60) = 0x35
ZB2_REG (0x61) = 0x33
ZB3_REG (0x62) = 0x6A
ZB4_REG (0x63) = 0x66
CTRL_A_ZT1_REG (0x70) = 0x51
CTRL_A_ZT2_REG (0x71) = 0x66
CTRL_A_ZT3_REG (0x72) = 0x99
CTRL_A_ZT4_REG (0x73) = 0xCC
CTRL_A_ZT5_REG (0x74) = 0xFF
CTRL_B_ZT1_REG (0x75) = 0x00
CTRL_B_ZT2_REG (0x76) = 0x66
CTRL_B_ZT3_REG (0x77) = 0x99
CTRL_B_ZT4_REG (0x78) = 0xCC
CTRL_B_ZT5_REG (0x79) = 0xFF
CTRL_C_ZT1_REG (0x7a) = 0x33
CTRL_C_ZT2_REG (0x7b) = 0x66
CTRL_C_ZT3_REG (0x7c) = 0x99
CTRL_C_ZT4_REG (0x7d) = 0xCC
CTRL_C_ZT5_REG (0x7e) = 0xFF
VERSION_REG (0xcc) = 0xE4
You can set any register XX with any value YY as follows:
Code:
echo XX YY > registers
additional knowledge i've learned so far. Ctrl A is the main display. Ctrl B is the bottom buttons. Ctrl C is webtop. So all we really care about are Ctrl A registers for now.
Additional Info
The display is set to linear mapping mode by default. but changing to exponential mapping mode gives a huge range from minimum to maximum brightness. but it's still not ready for primetime. to try out exponential, type:
Code:
echo 16 01 > registers
now go to your main phone settings, display, brightness, and drag the slider from min to max and see the enormous full range now available. dont worry, to reset exponential mode just lock the screen with power button then unlock, exponential mode gets cleared. that can be fixed later in the kernel when we get it working better.
just setting to minimum brightness alone gives a huge increase in battery life for display-on time, specifically at night. there's more potential to get out of this chip so hopefully you guys can dig up more stuff that i'm missing.
at some point I can compile the kernel with any changes discovered from this thread, and perhaps we can merge the code changes back into the kernel repo if faux doesn't mind.
Problem 1
I don't fully understand the meaning of the header file brightness values. The names list current mA values, that is clear. but there are also other info in the name which I don't understand yet.
similarly, in the data sheet, they give detailed examples of how to calculate the current draw of each brightness mode, and walk thru setting up the general configuration register. i've been reverse engineering the registers by looking at the data sheet, seeing each 8 bits and what they are assigned, then using appropriate hex value to turn off and on each of those bits in the output config reg. i echo a value, and see the result. most of the time it matches the data sheet, but not always.
Problem 2
There are also 4 boundary zones which trigger the backlight to adjust it's brightness. i've attempted to set these boundaries to different values, but so far i've not had any success with this.
Problem 3
Before this all started, no matter what the display brightness only goes down to 30 from a range of 0-255. even changing all the modes i've listed above, in every one it stops at 30. you can check brightness level by:
Code:
cat brightness
I'm stumped on where the 30 limit is coming from.
Ultimately, we can permanently change the following code in board-mot-lights.c to whatever desired values we want to be in the kernel permanently:
Code:
struct lm3532_platform_data lm3532_pdata = {
.flags = LM3532_CONFIG_BUTTON_BL | LM3532_HAS_WEBTOP,
.init = disp_backlight_init,
.power_on = disp_backlight_power_on,
.power_off = disp_backlight_power_off,
.ramp_time = 0, /* Ramp time in milliseconds */
.ctrl_a_fs_current = LM3532_26p6mA_FS_CURRENT,
.ctrl_b_fs_current = LM3532_8p2mA_FS_CURRENT,
.ctrl_a_mapping_mode = LM3532_LINEAR_MAPPING,
.ctrl_b_mapping_mode = LM3532_LINEAR_MAPPING,
.ctrl_a_pwm = 0x82,
};
And a companion app could also be made to automate the setting of these registers and such.
last thing, above notice the PWM value being set to 0x82. this is pulse width modulation mode, and is a significant power saving method in electronics. fortunately this is turned on by default, which is what the value 0x82 is doing. i've experimented turning it off and on for the hell of it.
hope some experts can join in this thread and see how far it goes. any questions feel free to ask.
Curious about the difference between software modification (screen brightness apps) and kernel modification (for brightness)
Excellent I like tinkerers and thanks for info so far
Magnetox said:
Curious about the difference between software modification (screen brightness apps) and kernel modification (for brightness)
Click to expand...
Click to collapse
Well this project is both kernel and could use an app to control the registers. But primarily this is to make kernel changes for now.
is this able to lower the brightness to BELOW the '2' setting? that's as low as AdjBrightness app lets me go, and also doesn't allow me to dim the home buttons. it would be nice to be able to dim the buttons at least, especially if watching a movie or something in the dark.
dLo GSR said:
is this able to lower the brightness to BELOW the '2' setting? that's as low as AdjBrightness app lets me go, and also doesn't allow me to dim the home buttons. it would be nice to be able to dim the buttons at least, especially if watching a movie or something in the dark.
Click to expand...
Click to collapse
Yes this can absolutely dim the buttons, anywhere from off to full brightness. Just echo to ctrl B register.
I'm not aware of the display app you mentioned. Does it do all the things I already listed in this thread? If so I feel dumb, I've not heard of the app you said.
Edit: I see that app in the market. This thread is specific to the atrix kernel, so it offers much more control. Activate exponential mapping mode and the display brightness goes down so low you wont even believe it. We'd then maybe make an app to automate it.
Forgive my ignorance, but the app SuperDim changes the brightness on my Atrix. Perhaps you guys are talking about something else though?
The lowest brightness setting is still much too bright to enjoy my Atrix in the dark (lol). The wife gets pissed... but this app definitely works.
Very cool!
'cat registers' only works when display is on. I'll have to see if an app can be done that doesn't have to fight the system.
Cheers!
or you could get an app called screen filter which does all this o.o
xepter said:
or you could get an app called screen filter which does all this o.o
Click to expand...
Click to collapse
Well, no, actually.
Hopefully something similiar to this, kernel maybe, all contains settings for the touch screen(digitizer)and we can alleviate the pesky rain drop detection issue.
A little late for me to start playing with this, maybe tomorrow!
Thanks
Sent from my MB860 using xda premium
what this is doing is reducing the current sent to the backlight to dim it.
Screen filter doesnt reduce current to the backlight past the stock minimum limit. It just puts a transparent "mask" over the display with the opacity depending on your setting, done entirely in software.
m0biusace said:
what this is doing is reducing the current sent to the backlight to dim it.
Screen filter doesnt reduce current to the backlight past the stock minimum limit. It just puts a transparent "mask" over the display with the opacity depending on your setting, done entirely in software.
Click to expand...
Click to collapse
Yes you bring up my next point, this isn't just brightness. This let's us reduce the current draw pulled by the display, and a good amount at that if you read the data sheet and look at the registers.
Additionally this let's us set and change the zone boundaries of the light sensor. It let's us change mapping mode between linear and exponential.
It also let's us control PWM, though that should just stay on all the time. Also there is ramp time register, which is set to zero by Motorola, so that might be useful.
Also there is the brightness config reg, full scale current reg, and general output config reg. All these look to have purpose needed to be tested.
There are many registers to tweak which gives us control, and that's the goal of this thread I think. Once we crack it all open then we can make permanent kernel changes if we want. Or an app would work. I think we could do something crazy like double screen time by finding optimal combo of reg settings, e.g. set min brightness mode with exponential mapping mode, then adjust the zone boundaries slightly,and it literally could give huge display savings for power. At least worth testing to see.
faux123 said:
Excellent I like tinkerers and thanks for info so far
Click to expand...
Click to collapse
Dude thank you for letting me compile your kernel. Much appreciated! And tinkering is what's fun about android!
some interesting behavior here:
lowest brightness in Stock 2.3.4 is "20", you can adjust to "2" by using app "adjbrightness", while you can set brightness lower to "1" in "moboplayer".
Even though, the "1" brightness is not good enough.
I'm wondering if this MOD can make brightness lower than "1"?
NFHimself said:
Very cool!
'cat registers' only works when display is on. I'll have to see if an app can be done that doesn't have to fight the system.
Cheers!
Click to expand...
Click to collapse
Yeah the driver is overriding some things, we could easily fix the code though. For example if you change the gen config reg to activate a different mode, soon as screen goes off locked the register is set back to previous value cause its hard coded. We just change that. So during testing I just keep the screen on.
I do have a battery app which does the echo and cat commands already written. Could just change the path and use it for this project...
kenyloveg said:
some interesting behavior here:
lowest brightness in Stock 2.3.4 is "20", you can adjust to "2" by using app "adjbrightness", while you can set brightness lower to "1" in "moboplayer".
Even though, the "1" brightness is not good enough.
I'm wondering if this MOD can make brightness lower than "1"?
Click to expand...
Click to collapse
Yes. Just enable exponential mapping mode, then use the slider in main display setting to see the full range.
echo 16 01 > registers
Be ready, super dim with that setting. Note still even with that being much lower brightness, the actual brightness value still wont go lower than 30. I can't figure out why.
SuperDim
As member bongd mentions already, SuperDim does the thing, free on the Market. I've pressed thanks button to show appreciation to the OP's efforts.
maajstor said:
As member bongd mentions already, SuperDim does the thing, free on the Market. I've pressed thanks button to show appreciation to the OP's efforts.
Click to expand...
Click to collapse
Superdim does not allow the brightness to even get close to the minimum level that the screen does by setting the registers. Testing is needed and that's kinda the point here.
So the lm3532 chip has brightness capabilities from 5mA up to 29the mA. Stock value in the kernel is set to very high at 26 mA. So just setting the lowest brings the current draw to 5 mA. The data sheet then shows the equation gives final result of close to 0.78 mA with all set properly. So there's savings to be had which is what needs to be tested here.
As an example, last night I changed to the lowest register setting, and after an hour of web screen-on time I was still at 86%the battery still.
maajstor said:
As member bongd mentions already, SuperDim does the thing, free on the Market. I've pressed thanks button to show appreciation to the OP's efforts.
Click to expand...
Click to collapse
Wow! You guys just aren't getting it. The apps you find in the market do not do the same thing. "Yes in the aspect they dim the screen" but they do it in to completely different ways. The way the op is talking about could add hours of battery life to are phones if done right. Because it changes how much power the display uses. There is not an app in the market or out that does that.
Hello all from research and test o my rom dev discovered this and want share it with all can help ^^
The following lines in the build.prop file can be added and edited to change several properties in your device:
debug.sf.hw = 1
Render UI with GPU (relieves pressure on CPU)
dalvik.vm.heapsize = 32m
Set size of Dalvik VM heap (how much RAM each instance of the VM is allowed); depending on how much RAM that is available to a device, this can be increased.
persist.adb.notify = 0
Stop debugging icon from appearing in status bar
windowsmgr.max_events_per_sec = 120
Increase to improve scrolling response
persist.sys.use_dithering = 0
Do not use surface dithering (surface dithering improves image quality)
debug.sf.nobootanimation = 1
Disable boot animation
ro.HOME_APP_ADJ = 1
force home launcher into memory
ro.sf.lcd_density = 240
Set screen density; change according to your device or what suits you, a lower value will display more but may be too small to use on a device with a smaller screen. Also note that changing the pixel density will make some applications in the new market ‘incompatible with your device’.
mot.proximity.delay = 150
Lower to fix black screen after calls issue
ro.telephony.call_ring.delay = 0
Decrease dialling out delay
ro.gsm.2nd_data_retry_config = max/_retries=3, 2000, 2000, 2000
Change MMS APN retry timer from 5s to 2s
wifi.supplicant_scan_interval = 120
ro.ril.disable.power.collapse = 0
pm.sleep_mode = 1
Increase battery saving potential
ro.com.android.dataroaming=true
Enables data-roaming by default in the build
ro.com.android.dateformat=dd-MM-yyyy
Changes default date format to day-month-year
ro.config.alarm_alert=*.ogg
ro.config.ringtone=*.ogg
ro.config.notification_sound=*.ogg
Changes the default sounds for each item. Must correlate to ogg files available in /system/media/audio/
ro.build.display.id=NAMEOFROM
In Settings>About Phone, it lists the name of the build number. This is where you set it.
ro.product.locale.language=en
ro.product.locale.region=GB
Sets the default region and language. You must have the correct letter combo, and the language must be available for this to work.
video.accelerate.hw=1 or 0
Whether to use hardware acceleration to render videos, doesn’t work on all devices
Some of those lines are missing from my build.prop. Can I place them anywhere in my build.prop or not?
jayrome876 said:
Some of those lines are missing from my build.prop. Can I place them anywhere in my build.prop or not?
Click to expand...
Click to collapse
yes after all line add thos you want
I've been having constant problems with the gps on my phone. If I TOT back to 11a, gps is ok. Nothing stellar but seems to get a fix after a spell.
If I take the OTA 12b my GPS goes to hell. Fix takes 1 min + sometimes. Looking through the threads I've tried and attacked the gps issue with everything everyone had to offer.... In one fix found from the Samsung Galaxy SIII forum, by editing the gps.conf file to focus the search to only US and North America servers you can speed up the fix. Makes sense to me.
In reading the code for my stock GPS.conf I see ntp_servers for Korea, Europe, asia, Japan, and North america.
For each server there is a description enclosed in hashtags: #Asia# #Korea# #Europe#
For my limited coding experience I'd assume the hashtags prevent that content from being read, allowing the coder to leave a comment or descriptor within the hashtags.
That being said, why doesn't the north america title have a second hashtag?
Mine reads like this from OTA 12b:
#Test
# NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
#Korea
# NTP_SERVER=0.kr.pool.ntp.org
What language is being used here? Does the hashtag matter or is it unneeded? Because if it does matter, then the correct north america server isn't being read. It's being obscured by the hashtags and being read wrong.
I went into the file using file explorer, "open in text editor", and added just a hashtag after the north america. I went from sitting and watching the gps status and toolbox endlessly look for a fix to grabbing satellites after a few seconds.
Am I crazy?
Here is my VZN g2 GPS.conf. Much better lock time.
#Uncommenting these urls would only enable
#the power up auto injection and force injection(test case).
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0
#NTP Server- This server chooses the closet geographical server in your region.
NTP_SERVER=time.nist.gov
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
#DEBUG_LEVEL = 3
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1
# supl version 1.0
#SUPL_VER=0x10000
# supl version 2.0
SUPL_VER=0x20000
# GPS Capabilities bit mask
# SCHEDULING = 0x01
# MSB = 0x02
# MSA = 0x04
# ON_DEMAND_TIME = 0x10
# GEOFENCE = 0x20
# default = ON_DEMAND_TIME | MSA | MSB | SCHEDULING | GEOFENCE
CAPABILITIES=0x31
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7278
SUPL_NO_SECURE_PORT=3425
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
####################################
# LTE Positioning Profile Settings
####################################
# 0: Enable RRLP on LTE(Default)
# 1: Enable LPP_User_Plane on LTE
# 2: Enable LPP_Control_Plane
# 3: Enable both LPP_User_Plane and LPP_Control_Plane
#LPP_PROFILE = 0
LPP_PROFILE = 3
################################
# EXTRA SETTINGS
################################
# NMEA provider (1=Modem Processor, 0=Application Processor)
#NMEA_PROVIDER=0
NMEA_PROVIDER=1
##################################################
# Select Positioning Protocol on A-GLONASS system
##################################################
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
A_GLONASS_POS_PROTOCOL_SELECT = 0x1
################################
# LGE EXTRA SETTINGS
################################
VENDOR=VZW
LGE_TLS_MODE=1
LGE_GPS_POSITION_MODE=0
Sent from my VS980 4G using XDA Premium 4 mobile app
The # is used to cmment out the line which means it's not considered in the conf file.
Sent from my VS980 4G using XDA Premium 4 mobile app
jrgilbert79 said:
The # is used to cmment out the line which means it's not considered in the conf file.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So as long as the beginning of the line has the #, whatever follows is ignored? No closing # is needed?
Not like C+ where a line would begin ( and then at the end have the closing )?
What language is this written in? Do you need a special app to modify?
It seems when I open the file in either the text editor of root explorer or notepad there are no returns at the end of the line. Just spaces.
cdangerb said:
So as long as the beginning of the line has the #, whatever follows is ignored? No closing # is needed?
Not like C+ where a line would begin ( and then at the end have the closing )?
What language is this written in? Do you need a special app to modify?
It seems when I open the file in either the text editor of root explorer or notepad there are no returns at the end of the line. Just spaces.
Click to expand...
Click to collapse
no idea what language it is, but it's standard in config files throughout android and a lot of windows even. closing hashes aren't needed, however returns are. idk if its your editor not reading the returns but they're necessary. i wouldn't worry too much, its known that jellybean causes painfully slow gps locks on some g2s regardless of the gps config... hashes are usually used like this:
#title of the program
#explanation of the file
#explanation of the line bellow
actual code to be read
#explanation of the line bellow
#optional code that can be enabled by taking out the hash
so your gps conf is set up for north america which makes sense for a verizon phone, with the servers for all other continents commented out which arent necessary. there are apps out there though that can add better servers onto the file if you're rooted.
Sent from my LG-VS980 using xda app-developers app
Is there any way to make the gps config flashable/easy to install because I don't see some of the data in the config file.