|
||||
|
Re: Speaker volume (quiet then loud)
I just revisited this thread hoping a fix was found. Two months later and nothing. Wow.
Can anyone confirm Meatgel's Vibrate/Ring fix solved this problem as well? I NEVER hear my text messages. |
|
||||
|
Re: Speaker volume (quiet then loud)
I have no ring delay with my VZ TP2.
If I dial my phone from a landline, I hear the phony first ring you hear with any cell phone, then the TP2 starts ringing during the second ring (it rings faster than my Wife's flip-phone) ~John |
|
||||
|
Re: Speaker volume (quiet then loud)
Just wanted to check in and confirm I am experiencing the same hi/low volume on rings. It's weird and damn annoying.
__________________
If Guns cause crime, then Pencils cause misspelled words....
Nebraska Concealed Carry | WWW.NECCW.BLOGSPOT.COM | WWW.HANDGUNLAW.US | WWW.NEFIREARM.COM | WWW.NRA.COM | WWW.AMENDMENTARMS.COM |
|
||||
|
Re: Speaker volume (quiet then loud)
I have to report that since I ditched that crap a-$-$ stock rom and radio I having had this issue again. That is with Mighty, Juicy or NRG Roms... Might have just been a bug with the stock rom... much like that annoying behavior sometimes when you click start then settings and then it can't decide what settings main menu to put you into. *I can't beleive the quirks that were left in place on the factory rom. If we all weren't so stunned with the display and shear performance of our TP2's, we probably would have complained more about them.
|
|
||||
|
***FIXED FIXED FIXED*** Re: Speaker volume (quiet then loud)
After copious searching, I came across this thread over on XDA:
http://forum.xda-developers.com/show...15&postcount=1 This registry edit will fix the low ringer problem we have all been suffering with. I have tested multiple times and can attest to my TP2 finally being fixed. Your ringer should no longer ring low to high. This reghack will NOT fix the clicks and pops when you touch a button...only the low ringer problem. Seems like the problem is that within [HKEY_CURRENT_USER\ControlPanel\SoundCategories\Rin g] the value name "AttenuationCategory" is a String when it should be a DWORD. I have noticed within the keys InCall, InCall2 and InCall3 that this problem also exists. I have changed those strings to DWORD also, but don't know what they may have fixed. I personally only changed the following: [HKEY_CURRENT_USER\ControlPanel\SoundCategories\Att enuation] "5"=dword:00000001 -- Added "4"=dword:00000001 -- Added "3"=dword:00000001 -- Added "2"=dword:00000001 -- Added "1"=dword:00000001 "0"=dword:00000000 [HKEY_CURRENT_USER\ControlPanel\SoundCategories\Rin g] "InitVol"=dword:00000005 -- Increased value data "AttenuationCategory"=dword:00000004 -- Added "AttenuationCategory"=string:4 -- **DELETED** Don't for get to delete the String value name"AttenuationCategory" and create a new DWORD with the same value name. Please post back your results. |
| This post has been thanked 2 times. |
![]() |
|
|
|