vbox, брат ще го пробвам и ако работи имаш 1 бира от мене 
R2VS for Omnia i900 (Updated 19-Jun-2009)
Started by
rith
, Mar 13 2009 08:54 AM
#181
Posted 11 May 2009 - 06:16 PM
#182
Posted 11 May 2009 - 07:04 PM
Never mind, vbox, I extracted the _setup.xml from the cabfile and accessed the registry settings you provided there.
***** A VERY PROMISING POSSIBLE FINAL, TRUE, REAL FIX FOR THIS WOW/SUSPEND HANG PROBLEM!!! *****
Very interesting clues from your registry settings, vbox! This reg setting in particular caught my eye, and looks to me to be the magic bullet that solves this WOW/suspend issue:
[HKLM\System\CurrentControlSet\Control\Power\State\Suspend]
"acs1:"="4"
"acs1:" looked driver-like to me, so I fired up FDC Task Manager on my Omnia and went looking in the Devices section for that name -- and found it. However, that is the driver for the accelometer, not SRS WOW. Hmmm.... so, not knowing anything about the above reg key, went searching around the net. And found this very useful page: Power Management under Windows CE
Started reading through this and got very excited about the prospect of finally solving this thing! This information is right there, for what we need to know to fix this if its a power management problem as we've suspected in this thread. Readers, the upshot of that document is that there is a place in the registry where WM can be told not to shut down a driver while in suspend mode, because it doesn't support that low power mode.
What doesn't add up, though, is the reg key that vbox provided. That driver name, as I pointed out above, is the accelerometer driver. Further, judging by the article linked above, state 4 would be full power off suspend support, so what this entry tells the OS is that, when entering the suspend state, turn off the accelerometer driver (i.e., put it into the power off state, requiring power-on initialization when it wakes up).
So, it seems to me that what we need to solve this is instead an entry like this in the above reg key, which tells the OS to leave the SRS/WOW driver in the fully powered on state when going into suspend:
"wav8:"=0
As per edits below, this didn't work. Trying 4 instead (see below).
On my device, "WAV8" is the driver name associated with the SRS/WOW driver dll, as determined by looking at the active device listing in FDC Task Manager.
So, I'm going to add this value to my existing installation (I haven't installed vbox's version yet), reset, and see what happens.
Anyone else that wants to give this a try too, first check your installed device drivers and find out what name WOW has on your device (I suspect it's also WAV8, but I don't know whether or not this is dynamic during install, so check to make sure), go to the reg key above, and add a DWORD value under it named "WAV8:" (or whatever yours is called) and set it tozerofour.
I'll report back later. Shouldn't take long... WOW crashes my Omnia almost immediately unless I use the achen method for suspend.
EDIT: First test is encouraging... Can suspend the device via the power button or a soft-suspend (via application), and a few minutes later wake it up with no freezes. Prior to this reg change moer times than not the Omnia would be dead under exactly these circumstances. Next test: Reconfigure automatic suspend in the Power cpl, set up S2U2 to turn off the device when it times out. Then, wait a longer stretch (half hour to an hour) and see if it's still alive.
EDIT: It crashed. However, don't give up yet... I decided to try setting 4 (Power Off state) and see if that would work, on the theory that the problem is the driver not getting properly initialized on wakeup. Rebooted, and it's been going strong for over an hour now, going to sleep manually with the power button, and automatically via the Power cpl timeout, as well as S2U2 timeout. So, looking encouraging...
***** A VERY PROMISING POSSIBLE FINAL, TRUE, REAL FIX FOR THIS WOW/SUSPEND HANG PROBLEM!!! *****
Very interesting clues from your registry settings, vbox! This reg setting in particular caught my eye, and looks to me to be the magic bullet that solves this WOW/suspend issue:
[HKLM\System\CurrentControlSet\Control\Power\State\Suspend]
"acs1:"="4"
"acs1:" looked driver-like to me, so I fired up FDC Task Manager on my Omnia and went looking in the Devices section for that name -- and found it. However, that is the driver for the accelometer, not SRS WOW. Hmmm.... so, not knowing anything about the above reg key, went searching around the net. And found this very useful page: Power Management under Windows CE
Started reading through this and got very excited about the prospect of finally solving this thing! This information is right there, for what we need to know to fix this if its a power management problem as we've suspected in this thread. Readers, the upshot of that document is that there is a place in the registry where WM can be told not to shut down a driver while in suspend mode, because it doesn't support that low power mode.
What doesn't add up, though, is the reg key that vbox provided. That driver name, as I pointed out above, is the accelerometer driver. Further, judging by the article linked above, state 4 would be full power off suspend support, so what this entry tells the OS is that, when entering the suspend state, turn off the accelerometer driver (i.e., put it into the power off state, requiring power-on initialization when it wakes up).
"wav8:"=0
As per edits below, this didn't work. Trying 4 instead (see below).
On my device, "WAV8" is the driver name associated with the SRS/WOW driver dll, as determined by looking at the active device listing in FDC Task Manager.
So, I'm going to add this value to my existing installation (I haven't installed vbox's version yet), reset, and see what happens.
Anyone else that wants to give this a try too, first check your installed device drivers and find out what name WOW has on your device (I suspect it's also WAV8, but I don't know whether or not this is dynamic during install, so check to make sure), go to the reg key above, and add a DWORD value under it named "WAV8:" (or whatever yours is called) and set it to
I'll report back later. Shouldn't take long... WOW crashes my Omnia almost immediately unless I use the achen method for suspend.
EDIT: First test is encouraging... Can suspend the device via the power button or a soft-suspend (via application), and a few minutes later wake it up with no freezes. Prior to this reg change moer times than not the Omnia would be dead under exactly these circumstances. Next test: Reconfigure automatic suspend in the Power cpl, set up S2U2 to turn off the device when it times out. Then, wait a longer stretch (half hour to an hour) and see if it's still alive.
EDIT: It crashed. However, don't give up yet... I decided to try setting 4 (Power Off state) and see if that would work, on the theory that the problem is the driver not getting properly initialized on wakeup. Rebooted, and it's been going strong for over an hour now, going to sleep manually with the power button, and automatically via the Power cpl timeout, as well as S2U2 timeout. So, looking encouraging...
Edited by dwallersv, 11 May 2009 - 09:49 PM.
#183
Posted 11 May 2009 - 09:25 PM
Ok, now I thought something which`ll be better becase not suspending SRS will dramaticly decrease battery life and the phone may get warm... BUT if we (someone who knows how
) can make a script that simply turns SRS ON or OFF (enable/disable) - there has to be a .reg key for that... Then when I want to use SRS I`ll just start the icon and then open the player - it`s one tap more but also more battery life 
Edited by maf107ezk0, 11 May 2009 - 09:27 PM.
#184
Posted 11 May 2009 - 09:47 PM
The difference this program makes is AMAZING!!!! its jsut to bad it caused my phone to crash atleast 3-4 times a day.
Alot of the time when i was recieveing a call the ringtone would skip like a scratched cd and sometimes it would just straight freeze. Tried making the power setting changes with no success, then i even tried uninstalling the WOW HD app and still got the problem. Removed SRS and problems stoped. Any one have any other fixes that might make this work better on the i910 because i was very impressed with the changes and would love to get this to work properly
Alot of the time when i was recieveing a call the ringtone would skip like a scratched cd and sometimes it would just straight freeze. Tried making the power setting changes with no success, then i even tried uninstalling the WOW HD app and still got the problem. Removed SRS and problems stoped. Any one have any other fixes that might make this work better on the i910 because i was very impressed with the changes and would love to get this to work properly
#185
Posted 12 May 2009 - 01:42 AM
dwallersv, appreciate your work and help and sorry for the late post.
As most of the people on the planet, i have to work too...
maf107ezk0, пробвай драйвера, но както си прочел, не е много сигурно дали ще работи, поне май не е довършено, нищо че работи на моята Омния. И мерси за бирата предварително!
И си направи бекъп преди това.
dwallersv, you dont need to install my driver. I will upload all my registry, taken from cab, but you gave me an idea. I have to think about to search for registry in Resuming, not in Suspend keys, but it is very late now 2.50am, and tomorow i am on work again.
Maybe you have miss that registry:
[HKEY_LOCAL_MACHINE\System\State\Hardware]
"Headset"=dword:00000001
It will enable WOW HD to run in initial state as Headphones profile selected.
Because i see that you may have more experience with WinMo registry than me, i will suggest to see all reg, that is related to WOW HD: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev] and [BtA2dpSnd] - the driver for BT is bta2dp.dll, [HKEY_LOCAL_MACHINE\SOFTWARE\SRS... if there is WOWXT key, i think it is not used, only WOWHD is used for Omnia. I suggest to see too that i have no OutputDevice in my cab, WOW HD will care all sound traffic.
Now i have entered your idea (for my device is wav1) in Suspend key, but as dword "wav1":0. I was tring that before, without understanding meaning of number and maybe was miss that 0 possibility. I have thinking to enter in Suspend key Iclass key for the driver, but what numbers in other keys mean? edit: alredy readit from your usefull link.
And i have to say, that my device work fine and alredy worked fine for a days. So i realy dont know if the "wav1:"-0 think work. I have entered and for now it work as before, i softresetted device after key change. I know from my experience that with other number - i have tried 4 and 3, it will freeze again.
Aachen_su i have not experienced that problem before, because i mostly use Skyfire as a brouser and yes - i have do the steps with the Opera and the device was freezed with WiFi on, i resetted it and try it with no internet connection, no 3G or WiFi and it freeze again. But aachen_su, can you please explain me what is the connection between Opera and sound driver, when even there was not sound comming from device at the moment? I have tried and something different - i have wait the device to go suspend itself after exiting Opera. And it not freezed! But maybe you are correct if they both (Wifi and Sound) use the same flag register.
Tulius, at the moment it looks the driver not work for many people. If you want to try it, have full backup of device, but it is not finished yet, maybe it will not be, who knows.
So, the post has become long... dwallersv, i realy appreciate if you continue to work on this. I think we need some registry to be entered in [HKEY_LOCAL_MACHINE\System\State\Hardware] and that will overcome the driver то try to search key to switch over internal profiles - they are many, but only 2: Headphones and Internal (stereo) are available for our devices. But i have tried so many, have hex researched the driver and did not find anything usefull, except Headset key. Maybe with your help that driver will become acceptable for more Omnias.
As most of the people on the planet, i have to work too...
maf107ezk0, пробвай драйвера, но както си прочел, не е много сигурно дали ще работи, поне май не е довършено, нищо че работи на моята Омния. И мерси за бирата предварително!
dwallersv, you dont need to install my driver. I will upload all my registry, taken from cab, but you gave me an idea. I have to think about to search for registry in Resuming, not in Suspend keys, but it is very late now 2.50am, and tomorow i am on work again.
Maybe you have miss that registry:
[HKEY_LOCAL_MACHINE\System\State\Hardware]
"Headset"=dword:00000001
It will enable WOW HD to run in initial state as Headphones profile selected.
Because i see that you may have more experience with WinMo registry than me, i will suggest to see all reg, that is related to WOW HD: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev] and [BtA2dpSnd] - the driver for BT is bta2dp.dll, [HKEY_LOCAL_MACHINE\SOFTWARE\SRS... if there is WOWXT key, i think it is not used, only WOWHD is used for Omnia. I suggest to see too that i have no OutputDevice in my cab, WOW HD will care all sound traffic.
Now i have entered your idea (for my device is wav1) in Suspend key, but as dword "wav1":0. I was tring that before, without understanding meaning of number and maybe was miss that 0 possibility. I have thinking to enter in Suspend key Iclass key for the driver, but what numbers in other keys mean? edit: alredy readit from your usefull link.
And i have to say, that my device work fine and alredy worked fine for a days. So i realy dont know if the "wav1:"-0 think work. I have entered and for now it work as before, i softresetted device after key change. I know from my experience that with other number - i have tried 4 and 3, it will freeze again.
Aachen_su i have not experienced that problem before, because i mostly use Skyfire as a brouser and yes - i have do the steps with the Opera and the device was freezed with WiFi on, i resetted it and try it with no internet connection, no 3G or WiFi and it freeze again. But aachen_su, can you please explain me what is the connection between Opera and sound driver, when even there was not sound comming from device at the moment? I have tried and something different - i have wait the device to go suspend itself after exiting Opera. And it not freezed! But maybe you are correct if they both (Wifi and Sound) use the same flag register.
Tulius, at the moment it looks the driver not work for many people. If you want to try it, have full backup of device, but it is not finished yet, maybe it will not be, who knows.
So, the post has become long... dwallersv, i realy appreciate if you continue to work on this. I think we need some registry to be entered in [HKEY_LOCAL_MACHINE\System\State\Hardware] and that will overcome the driver то try to search key to switch over internal profiles - they are many, but only 2: Headphones and Internal (stereo) are available for our devices. But i have tried so many, have hex researched the driver and did not find anything usefull, except Headset key. Maybe with your help that driver will become acceptable for more Omnias.
Attached Files
#186
Posted 12 May 2009 - 08:52 AM
**Vbox** again thank you for your hard efforts on providing this file...finally i have it working perfectly, all that i need to do as per your instructions above is.
** after soft reset, disable SRS WOW hit ok...wait 30 secs...re enable hit ok**
Thats it guys...no power issues what so ever, power management is still default settings, ive hit power on off many times...and left phone by itself overnight, which before would wake up and noticed my phone will not power on...this time definate fix!!!
Really happy now thanks vbox!!
** after soft reset, disable SRS WOW hit ok...wait 30 secs...re enable hit ok**
Thats it guys...no power issues what so ever, power management is still default settings, ive hit power on off many times...and left phone by itself overnight, which before would wake up and noticed my phone will not power on...this time definate fix!!!
Really happy now thanks vbox!!
#187
Posted 12 May 2009 - 02:51 PM
vbox: Good find on the "Headset" value... That does the trick on the bootup initialization! I've tested reboots twice with just those two registry hacks (the one I posted above, and the Headset change), and it now boots, times out on its own and goes to sleep, then wakes right up without any problems.
BTW, with the change I posted above, made it 18 hours now, with an overnight, without a crash/freeze. I'm thinking maybe we've got it.
Disappointing that the driver name, "WAVx", is not consistent w.r.t. the number value for "x". That will make it MUCH harder to put together an installer that will automatically set all this up for people.
It may have been missed in all the editing I did to that original post... I found that the WOW driver suspend state needs to be set to 4 (power off), not 0 (power on) for this to work. New theory is that this forces WM to completely reinitialize the driver upon coming out of suspend; old theory that setting the suspend state to power on would just keep the driver going was wrong, and after reading up more on WM power management it makes sense that that was a bogus idea.
The rest of those sets of reg values specific to the WOW driver I've messed around with before, and got nowhere. However, that may be where the default settings can be set up now to persist across boots, with the Headset hack apparently initializing the driver properly.
I'll keep experimenting, and among all of us we'll get this thing solved!
BTW, with the change I posted above, made it 18 hours now, with an overnight, without a crash/freeze. I'm thinking maybe we've got it.
Disappointing that the driver name, "WAVx", is not consistent w.r.t. the number value for "x". That will make it MUCH harder to put together an installer that will automatically set all this up for people.
It may have been missed in all the editing I did to that original post... I found that the WOW driver suspend state needs to be set to 4 (power off), not 0 (power on) for this to work. New theory is that this forces WM to completely reinitialize the driver upon coming out of suspend; old theory that setting the suspend state to power on would just keep the driver going was wrong, and after reading up more on WM power management it makes sense that that was a bogus idea.
The rest of those sets of reg values specific to the WOW driver I've messed around with before, and got nowhere. However, that may be where the default settings can be set up now to persist across boots, with the Headset hack apparently initializing the driver properly.
I'll keep experimenting, and among all of us we'll get this thing solved!
#188
Posted 13 May 2009 - 12:26 AM
vbox, on May 11 2009, 13:40, said:
Hi all
WOW HD is great sound enhancement, but R2VS is low dynamics, noisy and useless, by my opinion. Because they are not work together in any way, I think there no need of R2VS.
I have played with registry for weeks and found a way to avoid freezing the device, when it comes to suspend with WOW HD working. I have created cab with WOW HD instalation with more specific registry for Omnia, but it must be installed on a clear device.
So if you want to try it, remove R2VS, remove WOW HD, softreset and make sure the sound is working and device is not freeze anymore when it's going to suspend. Then install my cab and try if it will work.
My advice is if the device freezes and cannot wakeup, after reset or switch on, first go to WOW HD settings and turn it off for a moment, press OK, then turn it on again, and it will work until next reset.
In my Omnia WOW HD works without any sound/power issues, suspending and waking up with any button, playng music, TV online, radio on a handsfree or bluetooth stereo headset (Jabra BT8010) and the sound is exelent.
I have notice that it may freeze when it suspend after turning off bluetooth, but there is so many issues with bluetooth and power management, so it is acceptable for me.
My device is: Omnia/8G, PDA: I900DXIA2/DZIA1 lite ROM, Phone: I900DXID1
P.S.: It will install registry for WOW HD with bluetooth too. It will uninstall proper all, if not work in your device, i have test that.
And please excuse me - my English is very bad.
WOW HD is great sound enhancement, but R2VS is low dynamics, noisy and useless, by my opinion. Because they are not work together in any way, I think there no need of R2VS.
I have played with registry for weeks and found a way to avoid freezing the device, when it comes to suspend with WOW HD working. I have created cab with WOW HD instalation with more specific registry for Omnia, but it must be installed on a clear device.
So if you want to try it, remove R2VS, remove WOW HD, softreset and make sure the sound is working and device is not freeze anymore when it's going to suspend. Then install my cab and try if it will work.
My advice is if the device freezes and cannot wakeup, after reset or switch on, first go to WOW HD settings and turn it off for a moment, press OK, then turn it on again, and it will work until next reset.
In my Omnia WOW HD works without any sound/power issues, suspending and waking up with any button, playng music, TV online, radio on a handsfree or bluetooth stereo headset (Jabra BT8010) and the sound is exelent.
I have notice that it may freeze when it suspend after turning off bluetooth, but there is so many issues with bluetooth and power management, so it is acceptable for me.
My device is: Omnia/8G, PDA: I900DXIA2/DZIA1 lite ROM, Phone: I900DXID1
P.S.: It will install registry for WOW HD with bluetooth too. It will uninstall proper all, if not work in your device, i have test that.
And please excuse me - my English is very bad.
Hi vbox, where can I get the SRS WOW Cab file u mentioned?
#189
Posted 13 May 2009 - 01:58 AM
after install this reg cannot solve my problem.
after open opera then exit opera press power button to suspend phone cannot wake up again
after open opera then exit opera press power button to suspend phone cannot wake up again
#190
Posted 13 May 2009 - 06:00 PM
vbox, on May 11 2009, 05:40, said:
Hi all
WOW HD is great sound enhancement, but R2VS is low dynamics, noisy and useless, by my opinion. Because they are not work together in any way, I think there no need of R2VS.
I have played with registry for weeks and found a way to avoid freezing the device, when it comes to suspend with WOW HD working. I have created cab with WOW HD instalation with more specific registry for Omnia, but it must be installed on a clear device.
So if you want to try it, remove R2VS, remove WOW HD, softreset and make sure the sound is working and device is not freeze anymore when it's going to suspend. Then install my cab and try if it will work.
My advice is if the device freezes and cannot wakeup, after reset or switch on, first go to WOW HD settings and turn it off for a moment, press OK, then turn it on again, and it will work until next reset.
In my Omnia WOW HD works without any sound/power issues, suspending and waking up with any button, playng music, TV online, radio on a handsfree or bluetooth stereo headset (Jabra BT8010) and the sound is exelent.
I have notice that it may freeze when it suspend after turning off bluetooth, but there is so many issues with bluetooth and power management, so it is acceptable for me.
My device is: Omnia/8G, PDA: I900DXIA2/DZIA1 lite ROM, Phone: I900DXID1
P.S.: It will install registry for WOW HD with bluetooth too. It will uninstall proper all, if not work in your device, i have test that.
And please excuse me - my English is very bad.
WOW HD is great sound enhancement, but R2VS is low dynamics, noisy and useless, by my opinion. Because they are not work together in any way, I think there no need of R2VS.
I have played with registry for weeks and found a way to avoid freezing the device, when it comes to suspend with WOW HD working. I have created cab with WOW HD instalation with more specific registry for Omnia, but it must be installed on a clear device.
So if you want to try it, remove R2VS, remove WOW HD, softreset and make sure the sound is working and device is not freeze anymore when it's going to suspend. Then install my cab and try if it will work.
My advice is if the device freezes and cannot wakeup, after reset or switch on, first go to WOW HD settings and turn it off for a moment, press OK, then turn it on again, and it will work until next reset.
In my Omnia WOW HD works without any sound/power issues, suspending and waking up with any button, playng music, TV online, radio on a handsfree or bluetooth stereo headset (Jabra BT8010) and the sound is exelent.
I have notice that it may freeze when it suspend after turning off bluetooth, but there is so many issues with bluetooth and power management, so it is acceptable for me.
My device is: Omnia/8G, PDA: I900DXIA2/DZIA1 lite ROM, Phone: I900DXID1
P.S.: It will install registry for WOW HD with bluetooth too. It will uninstall proper all, if not work in your device, i have test that.
And please excuse me - my English is very bad.
Hi vbox,
Where can I find ur WOW cab?
Samsung Omnia 7 ( 8GB)
Samsung Omnia i900 (16GB) + 8GB MicroSD Card
PDA: i900DXIF1/OMNIA
PHONE: i900DXIA5
Samsung Omnia i900 (16GB) + 8GB MicroSD Card
PDA: i900DXIF1/OMNIA
PHONE: i900DXIA5
#191
Posted 14 May 2009 - 06:12 AM
#192
Posted 14 May 2009 - 12:00 PM
my phone just hang up and shut down repeatedly after i uninstalled it! ( actually it worked great... but so damm power hungry.... so i decided to remove it ) soft reset? nope.... its a hard reset bro...
#193
Posted 14 May 2009 - 01:46 PM
So...still is not recommended isn't it?
I want to increase audio quality, but don't want to have that sort of problems related to battery, BT Handsfree or low volume on calls using the headset.
I want to increase audio quality, but don't want to have that sort of problems related to battery, BT Handsfree or low volume on calls using the headset.
#194
Posted 14 May 2009 - 09:37 PM
Yeah im a little confused...so can we just download the original SRS WOW HD cab and then just copy/paste your settings and then add dwallersv settings as well?
Or did you pull your cab from the website vbox? Because i'm looking for your version VBox and i can't seem to find it..
Or did you pull your cab from the website vbox? Because i'm looking for your version VBox and i can't seem to find it..
#195
Posted 14 May 2009 - 11:51 PM
guys, go over to this thread on the SRS WOW fix... lastnikita cabbed up the whole thing, including the registry changes I made.
Good reports over there of Omnias running days without any crash.
Good reports over there of Omnias running days without any crash.
Edited by dwallersv, 14 May 2009 - 11:55 PM.
#196
Posted 15 May 2009 - 02:25 AM
dwallersv, on May 15 2009, 07:51, said:
guys, go over to this thread on the SRS WOW fix... lastnikita cabbed up the whole thing, including the registry changes I made.
Good reports over there of Omnias running days without any crash.
Good reports over there of Omnias running days without any crash.
So, Izit still heavy drain for the Omnia battery power?
#197
Posted 15 May 2009 - 11:29 AM
DEAR SIR/ALL FORUM MEMBER
AFTER INSTALLING BELOW MENTION BOTH APPLICATION MY TOUCH SCREEN FINTIONALITY AND SOUND OF PHONE IS COMPLETELY GONE I TRIED RESET, REBOOT, REMOVE BATTERY , UNINSTALL BOTH APPLICATION BUT MY CAN PHONES SOUND IS COMPLETELY GONE - NO SOUND AT ALL ? PLEASE PROVIDE SOLUTION HOW CAN I GET MY SOUND BACK WIHOUT HARD RESET? PLEASE REPLY URGENT AS THERE IS EVEN NO SOUND ON INCOMMING OR OUTGOING CALL AS WEL PLEASE REPLY ON [email protected] AS WELL
THANKS
[size=5]Thank to all the contribtors to this thread you are all unbelievable to make R2VS working on Omnia i900.
R2VS is 3D Sound, Equalizer, 5.1Ch Effect sound enhancement for Omnia (just like SRS WOW HD)
I made a new working cab out of the box so no need to manually edit the registry at all.
Fix registry to work with Bluetooth Stereo Headset was added.
[/size]
----------------------------------------------------------------------------------------------------------------------------------------------
[size=4]For those who try to make a sucessful SRS WOW HD installation please try this trick:
- Remove previous not working SRS WOW HD and soft reset
- Install R2VS cab below, soft reset and enable it
- Install SRS WOW HD cab below, soft reset and check it
- In order to fix SRS WOW HD device not wake up problem you must set Power setting for both [On Batterry Power] & [On External Power] to None
[/size]
----------------------------------------------------------------------------------------------------------------------------------------------
[size=5]
I think i770 has newer version of R2VS coz I saw it has different short cut icon but I don't have i770 so I can't tell if it true or not
If it uses R2VS_ARM_WM6_PRO_Driver.dll or newer exe I will try port it Omnia i900.
Anyone here who has Samsung Saga i770 can you check what does is the dll in registry or Windows folder ? Is it R2VS_ARM_WM5_PPC_Driver.dll or R2VS_ARM_WM6_PRO_Driver.dll or something else? can you post the dll or registry related to R2VS or its dumped rom ?[/size]
RV2S
SRS WOW HD
Power Setting for SRS
[/quote]
AFTER INSTALLING BELOW MENTION BOTH APPLICATION MY TOUCH SCREEN FINTIONALITY AND SOUND OF PHONE IS COMPLETELY GONE I TRIED RESET, REBOOT, REMOVE BATTERY , UNINSTALL BOTH APPLICATION BUT MY CAN PHONES SOUND IS COMPLETELY GONE - NO SOUND AT ALL ? PLEASE PROVIDE SOLUTION HOW CAN I GET MY SOUND BACK WIHOUT HARD RESET? PLEASE REPLY URGENT AS THERE IS EVEN NO SOUND ON INCOMMING OR OUTGOING CALL AS WEL PLEASE REPLY ON [email protected] AS WELL
THANKS
[size=5]Thank to all the contribtors to this thread you are all unbelievable to make R2VS working on Omnia i900.
R2VS is 3D Sound, Equalizer, 5.1Ch Effect sound enhancement for Omnia (just like SRS WOW HD)
I made a new working cab out of the box so no need to manually edit the registry at all.
Fix registry to work with Bluetooth Stereo Headset was added.
[/size]
----------------------------------------------------------------------------------------------------------------------------------------------
[size=4]For those who try to make a sucessful SRS WOW HD installation please try this trick:
- Remove previous not working SRS WOW HD and soft reset
- Install R2VS cab below, soft reset and enable it
- Install SRS WOW HD cab below, soft reset and check it
- In order to fix SRS WOW HD device not wake up problem you must set Power setting for both [On Batterry Power] & [On External Power] to None
----------------------------------------------------------------------------------------------------------------------------------------------
[size=5]
If it uses R2VS_ARM_WM6_PRO_Driver.dll or newer exe I will try port it Omnia i900.
Anyone here who has Samsung Saga i770 can you check what does is the dll in registry or Windows folder ? Is it R2VS_ARM_WM5_PPC_Driver.dll or R2VS_ARM_WM6_PRO_Driver.dll or something else? can you post the dll or registry related to R2VS or its dumped rom ?[/size]
RV2S
SRS WOW HD
Power Setting for SRS
[/quote]
#198
Posted 15 May 2009 - 07:28 PM
Good, but your attachments don`t show 
#199
Posted 24 May 2009 - 03:14 PM
My phone freezes if i press the power button although i changed the power settings. Too bad. The sound is nice.
#200
Posted 17 June 2009 - 02:33 AM
Thanks for this COOL "SRS" feature!!! Really make the sound much much better.
I notice something... I do not change my power saving settings and I have no problem of going suspend/sleep mode by pressing the "Power Button" and coming back from sleep mode by pressing the Power Button.
I also tried leave it alone so it goes to sleep mode by itself and then wake it up again.
BUT when I switch my USB connectivity from Storage to ActiveSync, when it goes to sleep (either by itself or pressing Power Button), it cannot wake up anymore. To solve it, I need to take out the battery and plug it back.
When I switch the USB connectivity back to storage, Sleep/Wake up is working again.
SH
I notice something... I do not change my power saving settings and I have no problem of going suspend/sleep mode by pressing the "Power Button" and coming back from sleep mode by pressing the Power Button.
I also tried leave it alone so it goes to sleep mode by itself and then wake it up again.
BUT when I switch my USB connectivity from Storage to ActiveSync, when it goes to sleep (either by itself or pressing Power Button), it cannot wake up anymore. To solve it, I need to take out the battery and plug it back.
When I switch the USB connectivity back to storage, Sleep/Wake up is working again.
SH
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users






Sign In
Create Account


Back to top









