Jump to content

[IMPORTANT UPDATE] SRS WOW HD 1.5.1 crash fix please try


Recommended Posts

Guest cyberarmy
Posted

Don't know what happened but now I think I need to hard reset my phone. My Omnia has got problem waking up now after a couple of these trails, it probably messed up the suspend registry. Power off/reset does not restore some of my control function like touch screen (partial), optical mouse. I had already uninstalled all the fixes I installed and SRS/RSV already after I discovered this fix is not working for me.

Guest maf107ezk0
Posted

lastnikita, can you make some registry edit so that the TrueBass settings can be set and not be reverted after every soft-reset? Thanks in advance :D

Guest Clos
Posted

Well the hanging is back. I don't know why sometimes it works fine for a while then at other times it frequently hangs after suspend ?

My current approach is to use R2VS most of the time and install SRS WOW if I'm going to listen to music for a while and uninstall it when I've finished.

A crazy way to do things but it seems to be the best for me. I only notice battery drain when SRS WOW hangs. I guess rebooting uses a lot of power?

I still don't understand why samsung don't seem to be bothered about the audio quality of the Omnia as it has such potential?

I would love a proper fix....

Guest FerdiBorbon
Posted

Try this after reboot, goto WoW HD settings disable hit ok...then hit your power button to sleep for a sec, hit power again then enable Wow HD...seem to work ok with me with the second cab posted on the 1st page.

Guest Clos
Posted

Thanks. I'll try that.

I also have another idea for a get round solution. I have realised that the phone doesn't hang if I hit suspend whist using pocket player (I do this a lot to continue to listen to music while saving battery) I'm wondering if having pocket player running but paused in the background will prevent the phone from hanging in suspend mode. I've been trying it for an hour and so far so good.

I hope this makes sense

Guest mykls
Posted

Hi all,

There seems to be a pattern where this fix might work for WM6.5 ROMS but not 6.1 ROMS. Could people please state whether they are WM6.5 or 6.1 when saying if this fix is working? Thanks.

Mike

Guest FerdiBorbon
Posted

Above: i dont think it will hang coz the audio is playing using WOW, coz i do the same with pocket player <_<

Guest dwallersv
Posted

I'm sad to say that none of this is working for me anymore either. Disappointing.

I decided to wipe the phone and start over, rebuilding my configuration from scratch. I had so much junk installed, reg tweaks and experiments, etc. -- even doing a "ROM upgrade mode" restore of my M2D config over the leaked rom upgrade, then manually ripping M2D out to install MS3.

Starting from scratch, I have a much, much cleaner installation now. I get crashes with the latest cab from lastnikita, and was having crashes with my previous setup with these changes that we thought might fix the problem.

What consistently works, every time, is achen-su's solution of suspending the phone while in the SRS WOW cpl. I have never had the phone lock up by using this method. Made it all day yesterday, over night, to today without a single freezeup. That's with using the phone a lot, suspend/wakeup probably 20 or more times, suspended as long as 10 hours, and with the phone taking tiny sips of the battery so that it still read 100% this morning after a full charge about 13 hours prior.

Best of all, with the clean rebuild of my configuration, it now stays asleep! I knock it out, and it stays that way until I either get a phone call, some notification (like an alarm or appt reminder), or wake it up myself. Previously, it would usually wake up immediately after suspending it, suspend again, wake up again, sometimes 4 or 5 times before I could get it to stay asleep, and then it would often wake up at some random time in the future, S2U2 would put it out again, and it would be frozen.

So, here's another thing to try if anyone's game: A mortscript that can trap the suspend event and open up the SRS cpl before going asleep. Automate the achen_su solution. With MS3 the current situation is nearly effortless because you can put a shortcut on the home screen for the WOW settings panel, so suspend is a two-press operation rather than just one for me most of the time, which is hardly burdensome. More than worth it enough to have this great enhancement.

Any mortscript gurus out there that want to give this a try?

Also, I'm not convinced that the driver power state configs in the registry are not still a possible solution. I will be experimenting with this more to see if some configuration of wav1 and wav8 in the various states solves the problem.

Guest paxt0r
Posted (edited)

A mortscript like this?

BattTimeout = RegRead("HKLM", "System\CurrentControlSet\Control\Power\Timeouts","BattSuspendTimeout")

If (BattTimeout = 0)

 RegWriteDWord( "HKLM", "Software\SRS\WOWHD\BtA2dpSnd", \ "WOWHDEnable",0 )

 RegWriteDWord( "HKLM", "Software\SRS\WOWHD\WaveDev", \ "WOWHDEnable",0 )

Endif

If (BattTimeout() > 1)

 RegWriteDWord( "HKLM", "Software\SRS\WOWHD\BtA2dpSnd", \ "WOWHDEnable",1 )

 RegWriteDWord( "HKLM", "Software\SRS\WOWHD\WaveDev", \ "WOWHDEnable",1 )

Endif

I dont know how it work, because i'm at work and can not test it. It's my first script and maybe i'm wrong, maybe some guys can use this part.

I'm from german(y) ^^. My English is terrible, sorry.

Edited by paxt0r
Guest dwallersv
Posted

I'll give it a try.

I don't know Mortscript, so I can't really interpret what you've written. However, it looks like all you're doing is sampling a registry entry to determine system state, and then changing a registry value as a result.

Does mortscript "poll" (i.e. run this script periodically, like every half second of so)? In that case, I can see how this would meet half the requirement -- "trap" the suspend event/transition.

I'm completely at a loss, though, to understand how simply setting a WOW-related registry setting will actually invoke the control panel applet and display it.

I suppose I should do a little mortscript self-education <_<

Guest NeMisiz210
Posted

So how does this fix the problem for days on end for most of the people at the start of this post and all of the sudden just stop working for them?....does it at least make the freezes less frequent?

Guest NeMisiz210
Posted (edited)

I saw this post in xda developers and no one had replied to it not even once...it was posted back in march and claims to fix the problem. I havent installed these and tried them yet but maybe someone knows some info on these?

Link -- http://forum.xda-developers.com/showthread.php?t=494552

*Edit: Nvm this is for the i900 and I found a similar post in these forums for it....but i still didnt gather anywhere if this worked for the i910 or not

Edited by NeMisiz210
Guest dwallersv
Posted (edited)
I saw this post in xda developers and no one had replied to it not even once...it was posted back in march and claims to fix the problem. I havent installed these and tried them yet but maybe someone knows some info on these?

Link -- http://forum.xda-developers.com/showthread.php?t=494552

*Edit: Nvm this is for the i900 and I found a similar post in these forums for it....but i still didnt gather anywhere if this worked for the i910 or not

Picked the cab apart, and there's nothing there we haven't already tried from a registry perspective. It looks almost lie the vbox cab with a few reg settings missing (notably the HARDWARE key creating a "HeadSet" value to 1). Here are the registry settings that cab in the thread above set on install:

<characteristic type="Registry">

<characteristic type="HKLM\SOFTWARE\SRS\WOWXT\WaveDev">

<parm name="SRSCenter" value="49" datatype="integer" />

<parm name="DefinitionLevel" value="59" datatype="integer" />

<parm name="FocusLevel" value="39" datatype="integer" />

<parm name="TruBassLevel" value="49" datatype="integer" />

<parm name="InitialSRSMode" value="0" datatype="integer" />

<parm name="SRSLevel" value="100" datatype="integer" />

<parm name="TBExternalSize" value="100" datatype="integer" />

<parm name="DisableInternal" value="0" datatype="integer" />

<parm name="TBInternalSize" value="40" datatype="integer" />

<parm name="WOWHDEnable" value="1" datatype="integer" />

</characteristic>

<characteristic type="HKLM\Drivers\BuiltIn\WaveDev">

<parm name="DACVol_0Ch" value="7" datatype="integer" />

<parm name="SPKVol_NotPhoneCall_02h_06h" value="0" datatype="integer" />

<parm name="SPKVol_PhoneCall_02h_06h" value="3" datatype="integer" />

<parm name="HPVol_PhoneCall_04h" value="4" datatype="integer" />

<parm name="GainADC_BluetoothMIC_12h" value="33" datatype="integer" />

<parm name="GainADC_LoudSpkMIC_12h" value="55" datatype="integer" />

<parm name="GainADC_HeadsetMIC_12h" value="42" datatype="integer" />

<parm name="GainADC_ReceiverMIC_12h" value="55" datatype="integer" />

<parm name="3DEff" value="0" datatype="integer" />

<parm name="MicGain" value="39" datatype="integer" />

<parm name="AGC" value="0" datatype="integer" />

<parm name="Treble" value="0" datatype="integer" />

<parm name="Bass" value="0" datatype="integer" />

<parm name="IClass" value="{A32942B7-920C-486b-B0E6-92A702A99B35}" datatype="string" />

<parm name="OldDriver" value="zylonite_wavedev2.dll" datatype="string" />

<parm name="Dll" value="WOWHD_ARM_WCE_PPC2005_Driver.dll" datatype="string" />

<parm name="Flags" value="2" datatype="integer" />

</characteristic>

Nothing to see... move along. <_<

One thing that I haven't tried that is implied in that post is to set things up so the only way to sleep the phone is from the power button. I'm going to give that a try. It's still quite sub-optimal, but if my phone will stay asleep (which it does now that I wiped it and reinstalled everything cleanly), and that method is reliable in preventing crashes, it's a usable workaround for me.

Edited by dwallersv
Guest achen_su
Posted

I find solution about InputGain and OutputGain Back to Default after soft reset

in 

HKLM\SOFTWARE\SRS\WOWHD\WaveDev

"InputGain" = 2

"OutputGain" = 0

after add this value you input gain = -2 and output gain = 0.

dwallersv, about "wav8:" = 4 and "wav1:" = 4

i try phone freezer every day.

can you give some solution.

do you use "acs1:" = 4?

"headset" = 1 (make my phone dry battery very fast) but help me setting headset

i give u solution make shoutcut in starup wow arm panel.

every time soft reset, phone automatic show srs wow hd setting.

if u forget press wow hd. this phone sleep but not freezer.

i try every day.

my phone crash in 2 situation.

1. receive sms and read sms, show in thread. then press power button my phone freezer. 

2. open opera close opera press power button phone freezer.

but after 2 situation before press power button, i press wow hd. then press power button. my phone no freezes.

can  u give me solution

  • 2 weeks later...
Guest NeMisiz210
Posted

So did everyone give up on this? The previous cab from xda-deveolopers actually seems to help a lot for me, but I usually turn srs wow off when I'm not using it for music(and I turn my phone screen off myself). I still get a crash like once every few days but not nearly as much as before....maybe theres something there that can still help us? I know you picked it apart but something in there definately slowed the frequency of freezes. I have faith that someone can find a fix for this. Dont give up

Guest NeMisiz210
Posted

By the way the xda-developers cab works perfect for me until i send a text message (maybe receive also)....no power problems whatsoever for days until i text someone, then instantly after i exit the text message window and put my phone to sleep it wont wake back up. Maybe this could help with a direction towards what drivers are being used?

Guest maf107ezk0
Posted

Can you please give a link or upload it here? <_<

Guest NeMisiz210
Posted
Can you please give a link or upload it here? :D

The link is on another post in here on the second page also....theres a similar post by the same person on these forums but i dont have the link on me right now...u can find it by searching for his name "cryingman" or w/e....either way it seems to work somewhat until i send text messages

http://forum.xda-developers.com/showthread.php?t=494552

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.