Database Develop

!!Finally!! Fix for low Bluetooth Headset sound issue!!!

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?

[TUT] Build.prop Modifications how to !

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

[Tweak] Build.Prop

I want to first thank Hashcode, Jonpry, and everyone else that has worked to get Kexec working on our phone (props for Kholk too). I decided to add some tweaks to the build prop to enhance my experience with a rom. Please note that there are no magical tweaks that would make your phone perform even better but my tweaks seem to have a positive effect on a thing here and here. My build prop is attached to the forum below. I have also included in this post what additional tweaks I've added, and what they do. If you have any good tweaks, I will add them to the list! At this moment this is CDMA only, you will have to add GSM tweaks to this build prop for those using GSM.
Code:
ro.telephony.call_ring.delay=1500
My Tweak: Originally set to 3000ms I halved to 1500.
Reason: This reduces the lag while dialing out.
Code:
wifi.supplicant_scan_interval = 180
My Tweak: The scan interval was originally set to 90. I upped it to 180.
Reason: This determines when our phones will scan for remembered access points. The higher the number, the longer the interval of scans. This is important if you often forget to turn off your wifi, like me.
Code:
ro.max.fling_velocity=11750
ro.min.fling_velocity=7500
My Tweak: Faster scrolling
Reason: Faster and Furiouser.
Code:
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
My Tweak: Disables Error checking and sending of usage data.
Reason: In the basics of computers there are 1's and 0's. 1 means on or yes and 0 means no or off, an interesting fact is that most power button symbols show a 1 inside a 0. I disabled all error checking because it would likely use a little less resources and add some stability for some apps. Some people have been reporting issues with Angry Birds and other games kicking them back to the desktop. If an app that worked before this tweak constantly does not work (after a reboot), remove the first two lines. ro.config.nocheckin just sends usage data.
Code:
persist.adb.notify=0
My Tweak: Disables notification for debugging
Reason: My phones is always set to USB debugging, I don't need to be reminded. This just disables the notification in the notification bar.
Code:
dalvik.vm.dexopt-flags=m=v,o=y
persist.sys.purgeable_assets=1
My Tweak: More aggressive but reasonable RAM management
Reason: Your phone will be less likely to think that something is still in use when it is actually not being used. This will free up more ram but it will force the phone to use a little bit more of the processer from time to time. Our phones actually have a decent processer but they lack ram. I've noticed some RAM heavy apps perform a little better after this tweak. persist.sys.purgeable_assets=1 is an option I found in CM9 roms seems to be used quite often (will remove if problems occur).
Tweaks that either do not work in ICS or do nothing at all.
Code:
Stagefright
Myth: Better media management and perfomance
Reason: While it is possible that this is true, Stagefright has been known to cause audio issues on Motorola phones. This may not be true on our ICS build but it's not needed due to the way ICS works. If you have a good reason to add it, I am willing to change my mind.
Code:
Heap sizes greater than 64
Myth: The bigger the heapsize the better, allowing apps to process faster and to improve multitasking.
Reason: Google's ICS default is 64 for devices that have 1024 ram or lower, anything higher will not do anything. Developers will never need more than 64 for their apps, unless they need to improve their coding.
Code:
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Myth: A fair amount of people believe this will make our pictures, videos, and sounds load faster, stronger, and better.
Reason: It's already there! It would be redudant
Code:
dalvik.vm.execution-mode
Myth: Enables the execution of JIT, which makes the phone faster
Reason: JIT execution is enabled by default on ICS and some people say this is useless anyways.
Code:
windowsmgr.max_events_per_sec=##
Myth: Allows for inputs such as screen touches to be read faster
Reason: Google's default setting is 90. Android maxes out at 60fps, setting max_events too high could slow down the UI making it process way to many things that it shouldn't.
Code:
Magikarp uses Splash!
Myth: Splash is a water based attack so it should be super effective against the right opponent types
Reason: It does 0 damage, and just wastes time. Teach Magikarp a TM and use it until Magikarp evolves.
-------------------------------------------------------------------TESTING----------------------------------------------------------------------------------​
The following code has not fully been tested, or I know little of it's effectiveness. I am in the process of testing.​
Code:
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
Supposedly this will force the system to use the GPU for 2D frames in applications and make things smoother. I'm almost positive that this is built into the rom.
-----------------------------------------------------------------Install--------------------------------------------------------------------------------​
***There are three build.props. builds.prop is Stable. BuildT.prop is my test build. Try it out at your own risk! Be sure to back up your original build prop. I have added it to the post as BuildO.prop just in case you need it. XDA will not allow extension .prop so I changed it to .txt****
To install it:
I am not responsible for anything that happens to your phone, you do this at your own risk.
1. Open your root explorer
2. Navigate to the very root of your phone
3. Go to System, and copy your original build.prop somewhere else or change the extension to .bak
4. Naviate to the build.prop you downloaded and copy it
5. Navigate back to root -> system and paste
6. Rename it to build.prop
7. Reboot.
* If problems occur, you can delete it and rename or replace it with the original but a build.prop has to be in there for it to reboot!

waiting for the gsm BUILD.prop

I will be looking into a downloadable GSM build.prop. In the mean time whatever method used to get GSM working on the stock Kexec build can be used on this build prop.
Sent from my XT862 using xda premium

I made an 883 prop thread in the General section if you want.
Sent from my XT883 using xda app-developers app

GPS.Conf file

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.

get UL and DL and frequency band in LTE Android

0
down vote
favorite
I am doing an APP for get many values of LTE so I want to get UL and DL speed I have a code that get RSSI CQI and many other but not DL and UL and frequency
String ssignal = signalStrength.toString(); String[] parts = ssignal.split(" ");
With that code I select the values that I dont have values that I want