If you watch ppc forum you will see there is a driver and program improving sound quality of devices that is SRS WOW HD. We can use this driver for our smartphones with 240*320 resolution now. Install and reboot your smartphone then you can hear high definiton sounds. Enjoy...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
where did you get it? and why in SRS Mode it's not recognizing my headset even when I connected it? It always says Mode: Speakers
Is there any system requirements to work this SRS soft?
Will it works on my Samsng i600 @ 220Mhz?
srs wow xt should fail to work with some devices because of registry settings could be different. if you load this software then software made your device silent you must change some registry settings.
before loading the srs wow xt you must take note some registry settings of your device. run registry editor and go to those two keys:
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev and
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd keys.
Dll: ........... note this value
IClass: ...... note this value
Order: ....... note this value
you will take 6 different registry values from 2 different keys. then install the apllication. Reboot your device and run registry editor again.
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev and
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd keys.
OldDriver: change this value with noted DLL value.
IClass: change this value with noted IClass value.
Order: change this value with noted Order value.
kasovnik said:
Is there any system requirements to work this SRS soft?
Will it works on my Samsng i600 @ 220Mhz?
Click to expand...
Click to collapse
system requriments are wm5 and wm6. try to install dont wory you could unistall when you want. it could work with your device.
Using the bundled handsfree from samsung (an ordinary pair of headphones), would be there any noticable difference in the sound quality?
Thanks
kasovnik said:
Using the bundled handsfree from samsung (an ordinary pair of headphones), would be there any noticable difference in the sound quality?
Thanks
Click to expand...
Click to collapse
sure you will hear difference of sound quality. but if you install this program and reboot your device and your device go silent then you must follow instructions of #4 post.
revanmj said:
where did you get it? and why in SRS Mode it's not recognizing my headset even when I connected it? It always says Mode: Speakers
Click to expand...
Click to collapse
i found from airfagev forum and i added some registry entries that allows listen music with srs wow xt over stereo bluetooth (a2dp). i dont know why this program does not recognize your headset. may be you must change settings from speakers to headset manually.
there is a newer version :http://amnezja.info/sp/SRS_WOW_HD_v1_28_5_0_ENG_RUS_WM5_WM6.zip
Works On My Dash
Works on my Dash like a charm, awesome find dude, no registry edits required. The stereo sound has greatly improve to the utmost like night and day,yeah.......!
hello
Must say i am not that impressed with my qtek 8500... It has very high treble... however i use the headset that came with the phone witch is not the best out there...
Too bad that it eats some more CPU.. while i'm listening to music, CPU load is above 40-45%
I'm using a HTC Tornado (SPV C600) @ 180Mhz.
The highs are too sharp when the volume is above 80%.. can this be adjusted? via registry ? or anything?
Can you change the SRS Mode? I cannot change it. It remains always on 'Speakers' Mode.
Headsets in.
Also, the PPC version has more options.. can we get more for smartphone too?
a2dp support
can i know where and how do i change registry settings so that i can experience the srs wow 1.28.1 effect on by bluetooth stereo headset.
mobile HTC mda
wm 5.
Great!
Loaded the old version and I have noticed a real improvement in clarity of sound. It's also possible to tune the sound 'on the fly' which makes it easy to customize the sound to suit.
Well worth a try
prasanna_tr said:
can i know where and how do i change registry settings so that i can experience the srs wow 1.28.1 effect on by bluetooth stereo headset.
mobile HTC mda
wm 5.
Click to expand...
Click to collapse
Go here and grab the BT version:
http://amnezja.info/sp/
Some Answers!
If your Phone doesnt work with SRS WOW via Blue Tooth Headset, you need to edit some Regkeys!
Here is a Copy about a Thread with the right issue:
That worked through BT headset it is necessary to copy all parameters from [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Wave Dev] in HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd
Except for value of parameter "OldDriver", he should be such, as was "DLL"
For example:
Before
"DLL" = "bta2dp.dll"
After
"DLL" = "WOWHD_ARM_WCE_PPC2005_Driver.dll"
"OldDriver" = "bta2dp.dll"
http://forum.xda-developers.com/showthread.php?t=355913&page=3
http://forum.xda-developers.com/showthread.php?t=357071
To have real stereo with your bluetooth stereo headphone you have to change the following registry key:
HKLM\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings
Change the UseJointStereo value 1 to 0.
The value 1 means dual mono, value 0 means stereo
Next point are the Blue Tooth Settings for Blue Tooth Audio Compressions, but i doesnt know in the moment all settings :->
With it you can change the Frequency from 44,1khz to 48khz, the compression rate and the stereo Mode. Joint Stereo is only a Mono Channel with additional Stereo Infos. This save bandwith!!! The most ppls think, the quality is higher ... but it isnt!! Dual Mono are better, if you make the bandwith for blue tooth higher.
if you need more infos about joint stereo, search via google for "wiki joint stereo"
Infos about Joint Stereo
Broken Link
revanmj said:
there is a newer version :http://amnezja.info/sp/SRS_WOW_HD_v1_28_5_0_ENG_RUS_WM5_WM6.zip
Click to expand...
Click to collapse
Sorry, link is broken... can anyone put it online again?
Thanxs!!!!
LightofMagic said:
Sorry, link is broken... can anyone put it online again?
Thanxs!!!!
Click to expand...
Click to collapse
i have added link to first post.
ragor_ali said:
srs wow xt should fail to work with some devices because of registry settings could be different. if you load this software then software made your device silent you must change some registry settings.
before loading the srs wow xt you must take note some registry settings of your device. run registry editor and go to those two keys:
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev and
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd keys.
Dll: ........... note this value
IClass: ...... note this value
Order: ....... note this value
you will take 6 different registry values from 2 different keys. then install the apllication. Reboot your device and run registry editor again.
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev and
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd keys.
OldDriver: change this value with noted DLL value.
IClass: change this value with noted IClass value.
Order: change this value with noted Order value.
Click to expand...
Click to collapse
I have this problem, that i don't hear anything after installing the driver.
But if I follow your tutorial, I don''t have a value called IClass, in both keys.. I have Order and DLL, and Index and Prefix. But not iClass...
What to do? I have a HTC vox
Related
Hi
Any ideas on how to adjust the a2dp bitpool settings. I am coming from windows mobile where this was easy to do in the registry. The stock bitpool seems to be 32 as per the logcat readout below. This is coming from an Evo 4G:
W/BTLD ( 1677): ### :: codec open ::
W/BTLD ( 1677): ### mtu 512, 660 bytes/frame, bitrate 229, nbr ch 0, freq 240
W/BTLD ( 1677): ### alloc : 3, blk len 240, chmode:15, bitpool 32:2, subbands 12
the sound is ok but could be better.
Another interesting part of the logcat is:
V/A2dpAudioInterface( 136): setParameters() bt_headset_name=DRC-BT15;bt_headset_nrec=on
E/AudioHardwareQSD( 136): setParameters() bt_headset_name=DRC-BT15;bt_headset_nrec=on
I/AudioHardwareQSD( 136): Using default acoustic parameters (DRC-BT15 not in acoustic database)
(I wonder what the acoustic database is.)
Any suggestions would be welcome. I did search around and found nothing easily implemented. Also nothing on the market.
Thanks
I want to know the exact same thing and not ready to accept that WinMo is superior to Android in any way...
I just found this page here which discuss some terminal and backend files in OSX for modifying these settings. Is there any similar file or terminal command we can do on our own unix based systems?
I have spent the last couple of weeks working on this and have come up with nothing. But I am not a programmer. Hope someone knows where to make the changes.
any update on this?
I am no programmer in any way, but I would realy like to know the outcome of this thread because it's been bugging me since I bought my Desire. I realy can't stand the loss of sound quality when listening to music on a bluetooth headset with my sennheiser headphones(HD215) connected.
I was wondering about the same thing. I used to tweak my WinMo Bitpool and samplerate. Any way to do this on Android?
I have been following this too. There must be a way to edit this somehow!! The a2dp quality of the evo/desire is awful! Must find a way!!!
I'm also disappointed in the audio quality on my Desire. I use my phone to listen to music in my car or mobile speaker via bt. But there are many tracks with high frequencies (or frequencies in some range), that causes some really disturbing clicking noise! Which I don't had on my Nokia N82 and SE K800i.
This really annoys me, and I consider to change to a different phone if there will not be a solution I'm currently using the original HTC firmware/radio, because I haven't rooted my phone yet. Is it possible that flashing a different radio will help?
I'm not sure if this is caused by the bitpool setting.
I will try to capture/upload some fragment with this clicking...
Edit: The microphone isn't good enough to record the clicking, but this fragment illustrates it very well (the clicking was actually in the track itself, but it sounds almost the same):
fragment (mp3)
Has there been any kind of an update on this one? A fix or a setting that could be changed?
I'm thinking of buying a Desire Z, but I will certainly stick to my ancient Touch Pro if the A2DP quality on Android is as bad as you all say. Bitpool of 32 is unlistenable, and I can't believe that neither Google nor HTC care about it.
Now that Cyanogen has fixed this in their ROM, I don't understand why no one has released a method for people not running Cyanogen.
So it has been fixed? What bitpool does that ROM run? I can't seem to find any info :S
And will they make a ROM for Vision with that fix?
I know I've got stupid noobish questions, but I'm completely new to the whole Android story and I haven't used these forums for ages so I'm quite lost atm...
CM6 is running 53
Thanks for the info
I'm having issues with an epic I just got (luckily in the 30 day return period). The a2dp audio sounds like garbage. The a2dp audio on my touch pro stock (before tweaked) was much better.
This could be a dealbreaker for me.
naorion said:
Now that Cyanogen has fixed this in their ROM, I don't understand why no one has released a method for people not running Cyanogen.
Click to expand...
Click to collapse
This is good news, but surely Mr.Cyanogen can pass on his method to Cotulla or one of the other primary Android Devs.... Hmm!
Any news on this? I flashed to Cyanogen 6.1. A2DP sounds much better. I now have mulitple exchange accounts working. The few issues are the Expensify receipt image capture does not work, 4G and HDMI also (know issues). I hope someone can find a fix for this.
I had a look at the bluez source code posted on HTC's developer site and I believe this is where the bitpool value is being set:
Code:
supersonic_bt.zip/external/bluetooth/bluez/liba2dp.c:
static uint8_t default_bitpool(uint8_t freq, uint8_t mode)
...
case BT_SBC_SAMPLING_FREQ_44100:
switch (mode) {
case BT_A2DP_CHANNEL_MODE_MONO:
case BT_A2DP_CHANNEL_MODE_DUAL_CHANNEL:
return 31;
case BT_A2DP_CHANNEL_MODE_STEREO:
case BT_A2DP_CHANNEL_MODE_JOINT_STEREO:
return 53;
default:
ERR("Invalid channel mode %u", mode);
return 53;
}
Changing the "return 31;" to "return 53;" and recompiling -or- hex editing the binary liba2dp.so on the phone ought to do the trick.
The same code block also appears in ipctest.c, pcm_bluetooth.c, sink.c, and source.c, so one or more of those files may also need to be modified.
I just got my Evo and I don't know enough about it yet to try this myself, but if someone else is able to then I think we'd all appreciate it if you could give it a shot. (Not all of us are interested in running a custom ROM just to fix this one problem.)
Edit: Another way may be to just force your desired min and max bitpool settings in the function bluetooth_a2dp_init():
Code:
cap->min_bitpool = min_bitpool;
cap->max_bitpool = max_bitpool;
Disregard that last post of mine. I had another look at liba2dp.c as well as some D/A2DP log output. All of the log output I could find posted online contains "channel_mode: JOINT STEREO", which according to default_bitpool() means the "default" bitpool should be 53. I originally thought the problem might be the bitpool setting of 31 referenced in that function, but I could not find any log output that contained "channel_mode: DUAL CHANNEL". (It shouldn't be too hard to verify this.)
So why is a lower bitpool value used? Look at this code snippet from bluetooth_a2dp_init():
Code:
min_bitpool = MAX(MIN_BITPOOL, cap->min_bitpool);
max_bitpool = MIN(default_bitpool(cap->frequency,
cap->channel_mode),
cap->max_bitpool);
cap->min_bitpool = min_bitpool;
cap->max_bitpool = max_bitpool;
The max_bitpool value is set to the lower of 1) the "default" bitpool and 2) the max bitpool reported by the audio sink (ie. your headset). If your headset reports a max bitpool of 32, then that is what will be used since it is less than 53. My understanding of the bluetooth spec is that audio sinks are supposed to accept bitpool values higher than 32 in order to support up to 512 Kb/s audio. Lower bitpool settings are more reliable, though, so perhaps that is why many headsets are configured to report artificially low values.
The actual bitpool value used is simply max_bitpool. See bluetooth_a2dp_setup():
Code:
data->sbc.bitpool = active_capabilities.max_bitpool;
The a2dp code isn't set up to take bitpool parameters from a configuration file, so liba2dp.c will need to be modified and recompiled. Possible quick fixes would be to change the "max_bitpool = MIN(" line to "max_bitpool = MAX(" or to manually set your desired bitpool value (ie. "data->sbc.bitpool = 53").
Hi,
I just want to say that since unfortunately my programming capabilities are close to non-existent I'm afraid I'm not able to provide much actual help in solving this issue but i highly appreciate that there are people who are looking into this and trying to remedy what Android OS designers and phone manufacturers neglected. I've been using A2DP headsets for the past 3-4 years with Nokia E51 and E52 phones which provided very good sound quality virtually indistinguishable from a cable connection and now after buying a Samsung Galaxy S phone I'm terribly disappointed at its A2DP performance comparable to 112kbps MP3s with even the highest quality sources.
I own three different A2DP headsets manufactured by Sony Ericsson, Nokia and unnamed Chinese labourers respectively and a set of quality IEM earphones plugged into quite good and relatively trained ears. Since A2DP support on both Nokias and a Samsung Blackjack I owned shortly (and let go of just because of its pitiful A2DP performance) has not always been perfect I know a thing or two about how A2DP works and performs. So if there is anything I can do to help regarding testing, preparing and submitting logs etc. just let me know and I will be very happy to help if that's what is needed.
Thanks!
Petr
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This application is made for enhancing or changing some feature for galaxy S
Requirement
1. machine
galaxy S (all variant)
2. version
Froyo (kernel 2.6.32.9)
3. rooted phone*
(*After checking "use with unrooted" option, you can remove rooting)
Feature
1. IO scheduler change
It can change CFQ(default) to deadline for some block device.
This change affect response time of disk IO.
(If you are using the application which handle many small files. You can feel better responsive reaction)
2. LCD color adjustment
(Test version)
This can be helpful to adjust so blue or yellow LCD.
3. Sound (3D, Hardware Equalizer)
It affect all system sound. so, If you change some parameter, all system sound(music, movie, radio..) will be affected.
How to test.
When you are hearing the music, As soon as changing the parameter, you hear different sound.
4. Memory Manager
Because It is controlled by kernel and android framework, It is more powerfull and efficient then memory killer.
for more info visit this link (thank to androcheck)
http://forum.xda-developers.com/showthread.php?t=622666
5. Over Clock (1.2Ghz)
OC feature is harmful to your phone. so, I put some restriction for preventing abuse.
(OC kernel user do not use this feature. I didn't consider OC kernel. and, I don't know about OC kernel)
6. Firmware(kernel) writing
you can write kernel(zImage) directly. and. can enter into recovery,download mode via this app.
7. use this app with unrooted
(Fort this. you must check "use with unrooted" option. before unrooting)
8. Bad block check (for ext filesystem)
If There are bad blocks on your ext filesystem. You can experience lag,abnormal app exit,slowness
9. key(Button) remaping Feature added
Volume Up,down key can be remapped to other key. (This is tested on M110S)
10. Touch gesture
It can map total 6 key button with Touch gesture.
11. Orientation Fix (especially Landscape mode)
It is helpful to view Landscape lying
How to download
search with this keyword on the market (galaxy tuner or d.w.kim)
Technical note
* LCD color and Sound function is accessing chipset resister directly.
* because, I don't have mDnie(LCD), wm8994(Sound) datasheet. I could not implement many feature.
* all system changing is volatile. so, If you reboot your phone. all system state is identical to original state
* OC function in this app change governor(performance, conservative..) policy. so, consider changing governor policy from like set cpu app
* running without rooting is a little tweak. It still require root privilege.
* more detail technical note
http://blog.naver.com/dowkim10/120122503306
* more about sound Howto
http://forum.xda-developers.com/showthread.php?t=921736
(Thanks to supercurio and studiominal)
Version note
1.3
The first version for all galaxy variant.
1.4
memory manager feature added
1.5
- color, sound (on boot adoption)
- memory manager (add some reinforced feature)
- bug fix for voodoo 5.2 patched kernel user (previous user must reboot once or reinstall for working)
1.6
OC (Over Clock 1.2Ghz) feature added
1.7
working on unrooted state.
1.8
Firamware(kernel) writing Feature added.
1.9
Bad block check(ext) Feature added
2.0
key(Button) remaping Feature added
fix bug (running Galaxy Tuner service at any time)
2.1
Orientation Fix (Feature added)
Sound (add option)
(it will clear user sound profile)
Memory Manager (Enhancement)
bug fix (on boot adoption is not worked sometimes)
2.2
Memory Manager (add VM control)
Key mapping( more button mapping added)
2.3
key mapping(Power key as Power+ headsetHook)
touch gesture feature added
Bug note
beta test version note
It is pre version for testing bug fix and add-on feature before releasing market
try attached file
Thanks dw kim. The app is amazing. I tried it with a couple of Mr Big songs. Is it like a parametric equaliser? Anyway, it's amazing how bassy it can achieve. The color temperature is great, I've always thought colours of my pictures were way too greenish, now I can adjust it to look more natural. Any way we can save it as boot settings?
Thank you very much.
I'm very happy It's working on your phone.
(You are first user except korean)
According to wm8993 manual(I don't have wm8994 manual). It is parametric equalizer.
It does not support on boot setting.
(but, I consider this function. I suggest you saving and loading user profile)
Haha, I am glad I am the first customer. Yes, the user profiles helps a lot.
Well, I think Supercurio, maker of Voodoo kernel, (maybe you already know him) has the Wolfson WM8994 manual? You could try ask him, he has a thread about sound here.
http://forum.xda-developers.com/showthread.php?t=806195
Btw, my phone is the international I9000.
Thanks a lot.
but, I don't have update plan right now, and I know him as very famous people.
so, I don't want to bother him.
No worries, dw kim, he's super helpful guy! Okay, relax, that app will make many ears happy already.
Btw, my favourite settings is +9, +6, +5, +7, +11. I think it's perfect. Using stock SGS earpiece.
It is too high gain.
How about extracting constant value on every band. and, volume up. (maybe same effect)
Too high value can make sound noisy
3d sound doesn't seem to work. o_0
one more thing: I'm using bluetooth A2DP.
stfudude said:
3d sound doesn't seem to work. o_0
one more thing: I'm using bluetooth A2DP.
Click to expand...
Click to collapse
This application access Sound chipset register directly. It is not software Equalizer.
If sound stream is transfered via bluetooth devcie. (without path of sound chipset)
you can not experience sound effect.
How about earphone or headphone ?
What is your phone model?
Great app!!!
Is there any posilibity to make it "autostart"...?
every time i reboot my phone I have to turn the settings on...
pandomu said:
Great app!!!
Is there any posilibity to make it "autostart"...?
every time i reboot my phone I have to turn the settings on...
Click to expand...
Click to collapse
I am considering. It is not difficult to implement.
(IO scheduler menu has this option)
but, I am afraid to add this option (LCD, Sound)
because, It handle hardware.
If There is no special case (after changing Sound, Phone is died)
I will add on boot option.
This application is not background application or service.
After setting a sound parameter, you can kill or remove from memory.
Just reporting that it works perfectly well with international GT-I9000 version.
For me, CFQ scheduler works best.
Thanks very much, i haven been waiting months for this
Hi Dowkim,
Thank you very very much. I have been waiting months for an application to adjust LCD color, but i had to either flash a kernel or accept that the camera stopped working. Your app works perfectly, thank you!
A suggestion: in the screen when adjusting color, you could add a colour testpattern so one can see the effect of the changed colors immediately.
Galaxy 9000 International Speedmod Rom
pwhooftman said:
Hi Dowkim,
Thank you very very much. I have been waiting months for an application to adjust LCD color, but i had to either flash a kernel or accept that the camera stopped working. Your app works perfectly, thank you!
A suggestion: in the screen when adjusting color, you could add a colour testpattern so one can see the effect of the changed colors immediately.
Galaxy 9000 International Speedmod Rom
Click to expand...
Click to collapse
Thanks. That is good idea.
I'll try. (but, I am poor at android programming)
dowkim10 said:
(but, I am poor at android programming)
Click to expand...
Click to collapse
I didn't notice for sure
Awsome work on this app. The music controls all work perfectly and make a huge difference in volume which i always thought was to low.
Hi dowkim10, this is interesting work.
I thought a lot about how to design the Voodoo sound driver and the consequences of the design chosen.
I took a different approach than yours: coding also a new driver, not as an independent .ko but using hooks in the actual source of the sound drivers to stay portable.
I believe a few limitations of the design you use are :
- It will be hard to add improvement like the microphone input auto-gain I prepare for the next version.
- Same thing for the FM radio bass solution
- Next to impossible for the upcoming audio jitter issue resolution
- Pretty hard and encumbered for adjusting other various input/ouptut gains/levels here and there
As kernel modules, like the scolor.ko and ssound.ko have a lot of power, in theory everything is possible but Galaxy S devices have so much different versions that implementing a module overriding some functions from the actual driver without breaking anything on a device or another will probably lead to very dirty code and headaches to maintain.
I thought of implementing everything using the wm8994_write dynamic register rewrite technique described here, also by inserting .ko modules like you do.
But here is what's in Voodoo sound source code:
https://github.com/project-voodoo/l...-voodoo/Kernel/sound/soc/codecs/wm8994.c#L215
https://github.com/project-voodoo/l.../Kernel/sound/soc/codecs/wm8994_voodoo.c#L270
By sniffing sequences of register address / value pairs, you should be able to recognize some patterns and add custom changes into it to extend your implementation.
But again, quite a dirty design
Good think of course it's the awesomeness of not requiring a custom kernel.
Of course my approach requires to publish every single piece of Kernel work as GPL and convince a lot of kernel developer to apply these patches, including eventually Samsung and Google.
But it's how I like it
As you distribute and insmod .ko modules, you're not forced to release source for them, but I advocate for Open Source.
Also, you will find a lot more code and ideas you will be able to re-use in the next Voodoo sound versions, about how to handle the parametric EQ and avoid saturation, and a lot of things like that.
Again, GPL will be a lot preferable.
bug report: mDNIe settings you use are lost after running Video player, Camera application (every app sending new mDNIe settings affecting the color response)
PS: don't be afraid to contact me, I am 70% of the time connected to IRC to discuss with and provide support to users and developers in real time.
dowkim10 said:
This application access Sound chipset register directly. It is not software Equalizer.
If sound stream is transfered via bluetooth devcie. (without path of sound chipset)
you can not experience sound effect.
How about earphone or headphone ?
What is your phone model?
Click to expand...
Click to collapse
International I9000
supercurio said:
Hi dowkim10, this is interesting work.
I thought a lot about how to design the Voodoo sound driver and the consequences of the design chosen.
I took a different approach than yours: coding also a new driver, not as an independent .ko but using hooks in the actual source of the sound drivers to stay portable.
I believe a few limitations of the design you use are :
- It will be hard to add improvement like the microphone input auto-gain I prepare for the next version.
- Same thing for the FM radio bass solution
- Next to impossible for the upcoming audio jitter issue resolution
- Pretty hard and encumbered for adjusting other various input/ouptut gains/levels here and there
As kernel modules, like the scolor.ko and ssound.ko have a lot of power, in theory everything is possible but Galaxy S devices have so much different versions that implementing a module overriding some functions from the actual driver without breaking anything on a device or another will probably lead to very dirty code and headaches to maintain.
I thought of implementing everything using the wm8994_write dynamic register rewrite technique described here, also by inserting .ko modules like you do.
But here is what's in Voodoo sound source code:
https://github.com/project-voodoo/l...-voodoo/Kernel/sound/soc/codecs/wm8994.c#L215
https://github.com/project-voodoo/l.../Kernel/sound/soc/codecs/wm8994_voodoo.c#L270
By sniffing sequences of register address / value pairs, you should be able to recognize some patterns and add custom changes into it to extend your implementation.
But again, quite a dirty design
Good think of course it's the awesomeness of not requiring a custom kernel.
Of course my approach requires to publish every single piece of Kernel work as GPL and convince a lot of kernel developer to apply these patches, including eventually Samsung and Google.
But it's how I like it
As you distribute and insmod .ko modules, you're not forced to release source for them, but I advocate for Open Source.
Also, you will find a lot more code and ideas you will be able to re-use in the next Voodoo sound versions, about how to handle the parametric EQ and avoid saturation, and a lot of things like that.
Again, GPL will be a lot preferable.
bug report: mDNIe settings you use are lost after running Video player, Camera application (every app sending new mDNIe settings affecting the color response)
PS: don't be afraid to contact me, I am 70% of the time connected to IRC to discuss with and provide support to users and developers in real time.
Click to expand...
Click to collapse
Hello supercurio
First, I am honored to meet you.
I know someone in korea said existence of this application. and, talked with you.
I also know you did very great job on galaxy kernel.
When I saw your sound code and mDnie code. I think you developed all passion and soul with many trial and error.
Absence of document maybe a excuse.
I have worked for ten years on embed linux. and treating many architecture(arm, ppc,mips,x86.) and treating kernel from 2.2 (now 2.6)
and, a few years ago, I ported android kernel to many board(arm v5,6,7 and xscale) and implemented HAL layer(GPS, alsa, bluetooth..) (android 1.0 around)
but, now I don't have relation Android in my job. so, I am doing this for my hobby. (I don't have enough time)
I know the risk of kernel module. wrong code or accessing bad address can cause system dieing.
but, basically, built-in and kernel module is same.
And, I didn't use your code. this module is treating only a few register.
Anyway, I am very nice to meet you. and many thanks for your advice.
( I hesitated to contact you. I'm a little shy)
If I keep my composure. I'll contact you via IRC.
Thank you.
dowkim10 said:
Hello supercurio
First, I am honored to meet you.
I know someone in korea said existence of this application. and, talked with you.
I also know you did very great job on galaxy kernel.
When I saw your sound code and mDnie code. I think you developed all passion and soul with many trial and error.
Absence of document maybe a excuse.
I have worked for ten years on embed linux. and treating many architecture(arm, ppc,mips,x86.) and treating kernel from 2.2 (now 2.6)
and, a few years ago, I ported android kernel to many board(arm v5,6,7 and xscale) and implemented HAL layer(GPS, alsa, bluetooth..) (android 1.0 around)
but, now I don't have relation Android in my job. so, I am doing this for my hobby. (I don't have enough time)
I know the risk of kernel module. wrong code or accessing bad address can cause system dieing.
but, basically, built-in and kernel module is same.
And, I didn't use your code. this module is treating only a few register.
Anyway, I am very nice to meet you. and many thanks for your advice.
( I hesitated to contact you. I'm a little shy)
If I keep my composure. I'll contact you via IRC.
Thank you.
Click to expand...
Click to collapse
Hi! be sure the honor is shared.
Thanks for your answer,
I see you not only speak Korean and English languages with ease but also I2C at least
Yes the absence of any sign of documentation about mDNIe forced to use the reverse-engineering approach ^^ as I had no experience in Kernel development a few months ago it was a lot of trial and error.
Now Samsung have given a little details in their new source code release about mDNIe controls, which is definitely a move in the right direction.
I'll try to get the doc for this chip.
I agree the first Voodoo sound implementation was crude, that's why I never activated and rewrote it from scratch for the release.
You're a much more experienced kernel and embedded developer than me!
Come on, don't be so shy, I'm just a rookie compared to you
See ya!
Hey guys !
Recently i have built a newer build of 6.5.3.23137 for Samsung i600. It's not tested now cause i've a 64bit Windows 7, and where's no driver available for 64bit 7. So i'm asking you to test and report for problems !
The main change is Titanium experience ! Also as many asked me i have installed YouTube and Ateksoft CoolCamera (unfortunelly only russian language interface) Need good english and polish translations
Also pay atentions that phncan.dll aka PhoneCanvas where deleted due to graphical problems
Adobe Flash Light didn't word at all so i've deleted it to.
PDA_i600_ChristmasEdition.zip
Thanx for all and waitin for quick reports !
Screen Shot
please include Screen Shot
screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM
whether the bar can be transparent?
and can be more screen shots?
Camera?
UPDATE: The camera did not work, but now its ok with a hard reset. But I have the following issues:
1) Changing the ring tone from the start menu, after clicking save I get error "cannot save setting".
2) When in english language, in the start menu instead of the word "Settings" i see "Nastroiki"
build problems
The camera will not work with other language than En-Us because of there's no mui files in this build.
Desided not to add in a reason of:
there's no Polish mui (0415)
There's no Ukrainian mui (0422)
But i promise to add all of them when i will done the translation mui files.
Also i need help with creation of changing keyboard layout menu.
FE like PY8 did with boot animation, sms other settings etc.
What's about "Nastroiki". I will correct this bug.
It's an old bug (from Shabudabu builds). There were no possibility to translate that card, that's why he overwritten xml file. This problem does not resolves with choosing another MUI language.
Transparent bar is real for BJ. But it's a huge work. Currently i have:
no time
no will
too little knowledge
Another problem with modifin' titanium/slidin' panels. Thorn_Pl reports 'bout the disability of modifin' panels order.
PsyClip-R said:
Also i need help with creation of changing keyboard layout menu.
Click to expand...
Click to collapse
Hi.
Maybe add Folder "Keyboard" in Start menu with 2* .reg files, eg: European_layout.reg and Ukrainian_layout.reg ?
Simple and easy
Code:
HKLM\System\CurrentControlSet\Control\Layouts\e0010409\
European: MappingID 1040
Ukrainian: MappingID 1049
edit:
PsyClip-R said:
Desided not to add in a reason of:
there's no Polish mui (0415)
There's no Ukrainian mui (0422)
Click to expand...
Click to collapse
Polish MUI here: http://forum.xda-developers.com/showthread.php?t=943602
Best regards
I've done keyboard layout menu during the first start.
in a few days will release newer build. fixed problems with chome settings tab disp as "nastroiki", fixed some translation (still not full)
It's possible to revert to the previous version after installing your rom?
Something like backup?
Tipika said:
It's possible to revert to the previous version after installing your rom?
Something like backup?
Click to expand...
Click to collapse
What do you mean to a prev. ver. ?
All the files, settings etc ?
Or maybe you mean prev. OS build ?
In this case you can - all you need - just to reflesh your device with an older build that you have used before update
both, restore the files and revert to the stock 6.0 ROM
and, how to flash this .bin?
use MTTY.exe to flash bin file, while the guide How to flash bin file can you look at http://forum.xda-developers.com/showpost.php?p=1438320&postcount=3
Tipika said:
how to flash this .bin?
Click to expand...
Click to collapse
Disable USB connections in Active Sync
Put smartphone in Bootloader Mode
Connect USB cable and use SHG-i600 Image Downloader (WCE Downloader) to flash (section PDA)
http://th0rn.wrzuta.pl/sr/f/0oscp9Gibf6/wcedownloader
Basic cooking manual released !!! more in the first post
Noticed that you fell back to the generic D3D driver (super slow). It took my some time to find a working D3D from TI as a file (not modules) - if you want to try, get it here: http://www.mediafire.com/?mkpquqq46xmij
tobbbie said:
Noticed that you fell back to the generic D3D driver (super slow). It took my some time to find a working D3D from TI as a file (not modules) - if you want to try, get it here: http://www.mediafire.com/?mkpquqq46xmij
Click to expand...
Click to collapse
yes tobbbie, i did that. you can find ti driver in windows folder
i haven't delete it in any of my builds.
as for me, generic driver is much more energy efficient. also it can be slow because it's not a module, just like it was with r2vs_wm6 driver 'til i've converted it to a module.
i can do menu to choose a driver.
How can you judge energy efficiency?
The driver does nothing until the time you ask for D3D actions. This hardly ever happens!
The performance of the TI driver is much(!) better than the generic MS driver (SW only). So I expect the MS driver to eat 100% CPU for a low performance while the TI driver lets the TI HW work that is designed to do that. Just pick the performance tests in the folder I listed.
You should not confuse "slow performance" (TI driver vs. generic driver) with "slow loading" (module vs. file). I would not care for the latter as you will hardly ever notice a difference.
Did you measure power consumption of the device while rendering D3D - with generic and with TI driver?
Have you any applications that actually USE the D3D interface and profit from the drivers? I have not seen any. I use that stuff on my old HTC devices (Tornado mostly) so they just have an OMAP 850) - so maybe it is different for the SGH-i600.
tobbbie said:
How can you judge energy efficiency?
The driver does nothing until the time you ask for D3D actions. This hardly ever happens!
The performance of the TI driver is much(!) better than the generic MS driver (SW only). So I expect the MS driver to eat 100% CPU for a low performance while the TI driver lets the TI HW work that is designed to do that. Just pick the performance tests in the folder I listed.
You should not confuse "slow performance" (TI driver vs. generic driver) with "slow loading" (module vs. file). I would not care for the latter as you will hardly ever notice a difference.
Did you measure power consumption of the device while rendering D3D - with generic and with TI driver?
Have you any applications that actually USE the D3D interface and profit from the drivers? I have not seen any. I use that stuff on my old HTC devices (Tornado mostly) so they just have an OMAP 850) - so maybe it is different for the SGH-i600.
Click to expand...
Click to collapse
So you're a master of Samsung i600 development process ?
Maybe in your country it's a normal to talk in such way with ppl. but remember -- there's mental difference between you country and mine.
This make me confused !
Hm, did not intend to be offensive, sorry if you feel pissed.
I wanted to evaluate your statement of energy efficiency regarding the TI driver - that is all. There is no reason to pull the work you have done and stop to share it with other SGH-i600 users. I don't have this device - so you punish the others and not me...
If you feel the need to discuss - let us do it via PM.
tobbbie said:
How can you judge energy efficiency?
The driver does nothing until the time you ask for D3D actions. This hardly ever happens!
The performance of the TI driver is much(!) better than the generic MS driver (SW only). So I expect the MS driver to eat 100% CPU for a low performance while the TI driver lets the TI HW work that is designed to do that. Just pick the performance tests in the folder I listed.
You should not confuse "slow performance" (TI driver vs. generic driver) with "slow loading" (module vs. file). I would not care for the latter as you will hardly ever notice a difference.
Did you measure power consumption of the device while rendering D3D - with generic and with TI driver?
Have you any applications that actually USE the D3D interface and profit from the drivers? I have not seen any. I use that stuff on my old HTC devices (Tornado mostly) so they just have an OMAP 850) - so maybe it is different for the SGH-i600.
Click to expand...
Click to collapse
Actualy, I don't know which's the processor of the Samsung i600, and I don't know how much it differ from Omap1030, and of course I don't know how much they differ from Omap850 (besides frecuency), but the MS Driver really improve the FPS over D3DM. The MS Driver even let you to run some things on D3DM that the TI driver doesn't, and in my opinion the system doesn't lags or anything.
Here's 2 pictures of the D3DMDemo app (developed by TI), showing the performance of MS Driver and their driver (TI driver)....Of course the picture with the low FPS is using TI and the high FPS picture is using MS...
PsyClip-R, continue with your work! Glad to see you cooked a rom for your device using that build, mine is "taking dust" on the hard drive, I have no time for such things now!
I have a HTC Trophy, coming from a HTC Touch Pro 2. The speaker phone was awsome on the TP2 and on the trophy, if there is small noises in the room (even a low computer fan) with the phone on mute, you can bearly hear the people on the phone. It's so low that with any low background noise, it's hard to hear.
Is it possable to increase the volume on the speaker phone on WP7 higher than 10 (maybe up to 15 or so) ???
Thanks !
TP2 has the best spekaer phone ever! It is highly unlikely that Trophy (or any other, I have HTC 7 Pro and spekaer phone is not as good as TP2) can reach it, maby by changing rege, but it can only harm the speaker since it will be overloaded.
I, too, miss TP2 speaker phone and talking in the car without jelling...
DavidinCT said:
I have a HTC Trophy, coming from a HTC Touch Pro 2. The speaker phone was awsome on the TP2 and on the trophy, if there is small noises in the room (even a low computer fan) with the phone on mute, you can bearly hear the people on the phone. It's so low that with any low background noise, it's hard to hear.
Is it possable to increase the volume on the speaker phone on WP7 higher than 10 (maybe up to 15 or so) ???
Thanks !
Click to expand...
Click to collapse
There is a registry edit to increase the # of increments, but it doesn't increase volue at all. It just adds more "steps". Haven't found anyway to increase the volume. It seems to be a driver issue on all HTC devices. HTC needs to get their act together & issue a patch to fix this. It's almost impossible to hear music/videos/movies. Any background noise & you can't hear ****.
I think I just fixed this. I saw a registry edit for WM 6 & it the directory still exists.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories, change the InitVol value to 100. I notice some were 100 already while others were 85 or even 65. I think this means 100% volume/85% volume/65% volume. Change them all to one value & you'll equalize the volume across the board.
drkfngthdragnlrd said:
I think I just fixed this. I saw a registry edit for WM 6 & it the directory still exists.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories, change the InitVol value to 100. I notice some were 100 already while others were 85 or even 65. I think this means 100% volume/85% volume/65% volume. Change them all to one value & you'll equalize the volume across the board.
Click to expand...
Click to collapse
Doesn't this just, like you said, increse the step but, not give a higher volume ?
SHould I be opening a ticket with HTC about this ?
DavidinCT said:
Doesn't this just, like you said, increse the step but, not give a higher volume ?
SHould I be opening a ticket with HTC about this ?
Click to expand...
Click to collapse
No, this is different. I just found it. The registry value I was talking about before is;
HKCU\ControlPanel\Volume\
MaxInCallUIVolume & MaxSystemUIVolume
I just did this new edit I just found (this one in the above post) & now I can hear youtube videos over my pc with tv playing on it lol.
thanks, I just gota figure out how to edit the registry with mango and I'll give it a shot.
drkfngthdragnlrd said:
No, this is different. I just found it. The registry value I was talking about before is;
HKCU\ControlPanel\Volume\
MaxInCallUIVolume & MaxSystemUIVolume
I just did this new edit I just found (this one in the above post) & now I can hear youtube videos over my pc with tv playing on it lol.
Click to expand...
Click to collapse
LG quantum here:
this is what it reads (dword)
HKCU\ControlPanel\Volume\
MaxInCallUIVolume = 10
MaxSystemUIVolume = 30
you set yours to 100?
also, I am not sure from your two posts, which one was necessary to get your volume up to max - entries from both posts?
with MFG I am not able to see the subcategories you mention in the post before under "SoundCategories". So I would have to query "blind" keys. too many to type them here?
thanks
derausgewanderte said:
LG quantum here:
this is what it reads (dword)
HKCU\ControlPanel\Volume\
MaxInCallUIVolume = 10
MaxSystemUIVolume = 30
you set yours to 100?
also, I am not sure from your two posts, which one was necessary to get your volume up to max - entries from both posts?
with MFG I am not able to see the subcategories you mention in the post before under "SoundCategories". too many to type them here?
thanks
Click to expand...
Click to collapse
No, that is the "steps". It just adjust how many increments you have. It's the other post.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories,
InitVol = 100
You can adjust the volume done for those who complain about the volume being too loud by entering a lower value.
drkfngthdragnlrd said:
No, that is the "steps". It just adjust how many increments you have. It's the other post.
HKCU\ControlPanel\SoundCategories\
In each of it's sub directories,
InitVol = 100
You can adjust the volume done for those who complain about the volume being too loud by entering a lower value.
Click to expand...
Click to collapse
thanks, problem with the MFG registry editor is that it does not show the sub directories. One would have to enter them before they can be edited, therefore one would need to already know the names of the sub categories.
thanks again
derausgewanderte said:
thanks, problem with the MFG registry editor is that it does not show the sub directories. One would have to enter them before they can be edited, therefore one would need to already know the names of the sub categories.
thanks again
Click to expand...
Click to collapse
Alarm\
DTMF\
InCall\
InCall2\
Notification\
Reminder\
Ring\
RingPreview\
System\
SystemNotification\
SystemVibrate\
drkfngthdragnlrd said:
Alarm\
DTMF\
InCall\
InCall2\
Notification\
Reminder\
Ring\
RingPreview\
System\
SystemNotification\
SystemVibrate\
Click to expand...
Click to collapse
terrific and thank you
what is DTMF? default on the LG is 65
(System = 85, SystemNotification = 85, SystemVibrate = 85, the rest is on 100)
derausgewanderte said:
what is DTMF? default on the LG is 65
(System = 85, SystemNotification = 85, SystemVibrate = 85, the rest is on 100)
Click to expand...
Click to collapse
I have no clue what DTMF is. I believe the value stands for % of max volume. I set them all to 100. Now I may just be hearing things, but it sure sounds louder to me. I had the TV playing on my PC & the YouTube video on my HD7 droned out the TV. (heard YouTube Video clearly, but couldn't here TV). Now keep in mine I have 200 Watt RMS Logitech 2.1 Speakers w/a Sub Woofer on my PC & they were at 33% volume.
as most are on mango now...
so the subcategories are named...can you name the keys to edit?
even better would be a *.reg-file we can provxml
diboze said:
as most are on mango now...
so the subcategories are named...can you name the keys to edit?
even better would be a *.reg-file we can provxml
Click to expand...
Click to collapse
see drkfngthdragnlrd's post #9, they key is the same for all:
InitVol = 100
change the number you find to 100. Most of them are already on 100.
drkfngthdragnlrd said:
I have no clue what DTMF is. I believe the value stands for % of max volume. I set them all to 100. Now I may just be hearing things, but it sure sounds louder to me. I had the TV playing on my PC & the YouTube video on my HD7 droned out the TV. (heard YouTube Video clearly, but couldn't here TV). Now keep in mine I have 200 Watt RMS Logitech 2.1 Speakers w/a Sub Woofer on my PC & they were at 33% volume.
Click to expand...
Click to collapse
DTMF (dual tone multi frequency) is the signal to the phone company that you generate when you press an ordinary telephone's touch keys. In the United States and perhaps elsewhere, it's known as "Touchtone" phone (formerly a registered trademark of AT&T). DTMF has generally replaced loop disconnect ("pulse") dialling. With DTMF, each key you press on your phone generates two tones of specific frequencies. So that a voice can't imitate the tones, one tone is generated from a high-frequency group of tones and the other from a low frequency group.
:http://searchnetworking.techtarget.com/definition/DTMF
derausgewanderte said:
see drkfngthdragnlrd's post #9, they key is the same for all:
InitVol = 100
change the number you find to 100. Most of them are already on 100.
Click to expand...
Click to collapse
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
PanNet said:
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
Click to expand...
Click to collapse
I do understand. if you want to inject this into the registry via provxmal then you need to convert this into code for the registry, no?
[HKEY_CURRENT_USER\Control Panel\SoundCategories\Alarm\]
"InitVol"=dword:00000064
or
"InitVol"=hex(b):64,00,00,00,00,00,00,00
(100 dec = 64 hex). I am sure the programmers here know exactly what to do with it.
and the same for
DTMF\; InCall\; InCall2\; Notification\; Reminder\; Ring\; RingPreview\; System\; SystemNotification\; SystemVibrate\
but maybe I am missing something....
PanNet said:
Hi,
You did not understand. After update to Mango there is no possibility to edit registry yet. So we need a full code to do it by provxmal. If you have access you can do it for us.
Click to expand...
Click to collapse
EDIT: Speaking of which, I found another registry that deals with how audio is handled. Attached is the provxml for it. This CustClear.provxml has all the volume registry edits I have done. It give you 50 steps for volume in call & default system.
derausgewanderte said:
I do understand. if you want to inject this into the registry via provxmal then you need to convert this into code for the registry, no?
[HKEY_CURRENT_USER\Control Panel\SoundCategories\Alarm\]
"InitVol"=dword:00000064
or
"InitVol"=hex(b):64,00,00,00,00,00,00,00
(100 dec = 64 hex). I am sure the programmers here know exactly what to do with it.
and the same for
DTMF\; InCall\; InCall2\; Notification\; Reminder\; Ring\; RingPreview\; System\; SystemNotification\; SystemVibrate\
but maybe I am missing something....
Click to expand...
Click to collapse
Hi,
Thanks. Can you write default settings for InCall, InCall2, Ring, RingPreview.
This post would contain a list of applications that can be run under Win86emu with the instructions on getting them running.
As I can't test all of the applications in the world - feel free to post your findings here.
SilverHedgehog made a list of compatible programs in a form of a spreadsheet, that can be edited by anyone: https://docs.google.com/a/silverblo...1vlWDspVdERIZlFHcnVhLV9EaDZIOEpqN2tQT1E#gid=0
Please do not post your problems here and do not ask questions. This thread should contain only the list of working apps and instructions on getting them running.
Ask questions and post your problems in this thread: http://forum.xda-developers.com/showthread.php?p=36622756
When instructions tell to edit registry - use native (i.e. Windows RT) registry editor unless explicitly stated to use the x86 one.
Version 0.05:
Might and Magic VI. There is a fixed MM6.EXE file here: http://forum.xda-developers.com/showthread.php?p=40959944#post40959944, use it to avoid crashes.
Fallout 2. Notes are here: http://forum.xda-developers.com/showthread.php?p=41292319#post41292319
Version 0.04:
WinAmp 2.95. Installs fine, music is playing correctly. Bugs: winamp browser is not working, visualization plugins crash, "stop bugging me" is not saved.
WinRAR 4.20, 7Zip 9.22. Both install and work, but are too slow.
Pinball from Windows 95. Works fine, but the picture is small (you may lower the desktop resolution to make it look larger).
Heroes of Might and Magic III. Instructions are here: http://forum.xda-developers.com/showthread.php?p=40924235#post40924235
Age of Empires 1. Instructions are here: http://forum.xda-developers.com/showthread.php?p=40924456#post40924456
IrfanView. Checked by GoodDayToDie here: http://forum.xda-developers.com/showthread.php?p=40954195#post40954195, some hints here
Might and Magic VI. Instructions are here: http://forum.xda-developers.com/showthread.php?p=40959944#post40959944
Reserved.
Reserved.
Reserved.
Heroes of Might and Magic III
Both the original and complete/gold editions are working.
You can install a game from the ISO image or copy the installed directory from a PC.
To play in a high resolution - use the heroes 3 hd mod: https://sites.google.com/site/heroes3hd/eng/download, it also contains a no-cd patch. I recommend to set "color mode"=standard, as this should provide the best speed.
If you prefer to play in the native 800x600 resolution and observe large black space on the right and bottom sides of the screen - this is due to a problem in recent Nvidia tegra3 video driver. It no longer provides the 800x600 mode, so the emulator sets the nearest available mode (probably 1024x768).
To enable the 800x600 mode you'll need to edit the registry. Warning: editing the registry incorrectly may make your device unbootable!
Run regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{D7F0B22A-58DF-4A4D-AAA5-B7766CED7EFE}\0000 key. Edit the value "NV_Modes", it looks like: "{*}S 1024x768x32,64 1280x720x32,64 1280x768x32,64=1;". Add the 800x600 32 and 64 bit mode, so that the line would look like "{*}S 800x600x32,64 1024x768x32,64 1280x720x32,64 1280x768x32,64=1;". Then reboot the device.
This hack would work only on Tegra 3 devices! I don't know how to enable 800x600 mode on Qualcom-based tablets.
Known problems:
- network games are not working
- no MP3 music
- the game may hang. This is due to a bug in mss32.dll, the same bug is present on a desktop PC too. To increase the stability - disable the music and sound effects or add this compatibility setting to registry:
Code:
[HKEY_CURRENT_USER\Software\x86node\Compatibility\Heroes3.exe]
"SetProcessAffinityMask"=dword:00000001
This would force the EXE file to run on only one CPU core and mss32.dll would be happy. But this would decrease the overall game speed.
Age of Empires 1
Tested on the AOE Gold with the expansion pack.
Installer is not working. You'll need to copy the game files from your PC.
Known problems:
Only the 1024x768 display mode is supported.
No network game.
Palette issues - you may get the unreadable text on buttons.
If the game don't find CD-ROM - edit the registry key:
Code:
[HKEY_CURRENT_USER\Software\x86node\HKLM\Software\Microsoft\Games\Age of Empires\1.00]
"CDPath"="E:\\"
Here E: - the drive letter of the mounted ISO file.
I'll try my version of AOE II when I get a chance and let you know how it goes... My patch could be different, but who knows.
EDIT: Doesn't really work. Still tries to launch a single-player game, then crashes. Campaign says there's no disc inserted... and of course multiplayer doesn't even show up. But the auto-run is AMAZING! Great work as always!
The Powder Toy (legacy exe) runs, but even on an empty level you get ~2.50 fps.
C-Lang said:
I'll try my version of AOE II when I get a chance and let you know how it goes...
...
Campaign says there's no disc inserted...
Click to expand...
Click to collapse
Regarding the AOE2 no-cd crack, there is a note in the comments on russian site: http://habrahabr.ru/post/168269/
There is a bug in the no-CD, it checks for the installation drive letter in registry and if it is not present - no-cd code returns error. I have not checked that myself yet, but you should try to edit the registry.
SilverHedgehog said:
The Powder Toy (legacy exe) runs, but even on an empty level you get ~2.50 fps.
Click to expand...
Click to collapse
empty level only gives 20fps on my 2ghz Intel Celeron laptop so that was hardly unexpected. Dunno if it would be a candidate for porting though.
IrfanView (a popular image file viewer/resizer/basic editor) works for the most part. Install it (from http://irfanview.com) on a Windows PC, then copy the installed files over to the RT device. It actually may be possible to use the installer with the lasted emu version; the one I last tried with didn't work. It's definitely slower than on native x86, but for reasonably-sized images the difference isn't important (I've been using this app since 400MHz single-core Pentium 2 CPUs from circa 2000; it's not performance-intensive but manages to run very, very fast). I haven't tested all the features or plugins yet. Configuring it to automatically open the relevant file types doesn't currently work (probably due both to registry redirection and to the fact that the OS can't directly invoke the iview.exe program).
Might and Magic VI
Tested on the Might and 6 Limited Edition.
Game installer is 16-bit, so it cannot be run with my emulator or on desktop x64 Windows.
Install the game on 32-bit desktop Windows, then apply the GrayFace MM6 Patch from here: https://sites.google.com/site/sergroj/mm and copy files to your device. You don't need to export registry.
Game asks for CD2. To mount it on RT you'll need to extract the data track as an ISO file and mount that ISO on your device. I've used Nero. Or you may try to use USB CD-ROM (never tried that myself), or use the no-CD built into GrayFace's patch.
There is an incompatibility that causes the game to crash when you enter buildings. Use the EXE file from the attached archive to fix that. This EXE requires the GrayFace's patch to be installed.
Introduction is choppy, but overall game speed is fine.
Game uses the 640x480 mode that cannot be set on Asus VivoTab due to a limitation in Tegra 3 drivers. To enable the 640x480 you'll need to edit the registry as described in the HOMM3 post: http://forum.xda-developers.com/showthread.php?p=40924235#post40924235 but the modified string should look like this: "{*}S 640x480x32,64 800x600x32,64 1024x768x32,64 1280x720x32,64 1280x768x32,64=1;". Be careful while editing registry!
GoodDayToDie said:
Configuring it to automatically open the relevant file types doesn't currently work (probably due both to registry redirection and to the fact that the OS can't directly invoke the iview.exe program).
Click to expand...
Click to collapse
This is due to registry redirection. I "protect" the OS native registry from being trashed by emulated programs. You can override this by adding this compatibility setting:
Code:
[HKEY_CURRENT_USER\Software\x86node\Compatibility\iview.exe]
"UseDirectRegistry"=dword:00000001
This setting is not tested and may cause side effects, so be careful.
It is safer to manually associate iview.exe with needed file extensions.
Oh, I'm quite familiar with using assoc and ftype, or indeed manually tweaking the registry, to set file associations. However, unless you've already implemented the "automatically use the emulator for x86 programs" feature, that won't work. I suppose I could point it at a script that launches the emulator pointing at iview.exe and passes along the argument (file name) that the script itself received, though.
Thanks for this great piece of work!
GoodDayToDie said:
Oh, I'm quite familiar with using assoc and ftype, or indeed manually tweaking the registry, to set file associations. However, unless you've already implemented the "automatically use the emulator for x86 programs" feature, that won't work. I suppose I could point it at a script that launches the emulator pointing at iview.exe and passes along the argument (file name) that the script itself received, though.
Thanks for this great piece of work!
Click to expand...
Click to collapse
That feature is apparently implemented and it is working like a charm, all you need to do is to run the c:\x86node\windows\autostart_x86.cmd after the jailbreak. I was unable to do it automatically because I haven't found a way to schedule a task after another task completes. If you manage to schedule it to run automatically after the jailbreak, please share your solution.
How about we use something like a spreadsheet for this? A thread is pretty hard to navigate.
Here, I made a spreadsheet on Google Drive everyone can edit:
https://docs.google.com/a/silverblo...1vlWDspVdERIZlFHcnVhLV9EaDZIOEpqN2tQT1E#gid=0
Jimm98y said:
That feature is apparently implemented and it is working like a charm, all you need to do is to run the c:\x86node\windows\autostart_x86.cmd after the jailbreak. I was unable to do it automatically because I haven't found a way to schedule a task after another task completes. If you manage to schedule it to run automatically after the jailbreak, please share your solution.
Click to expand...
Click to collapse
Herp derp, I can't read changelogs. Thanks for pointing that out. As restitution, I shall attempt to get the automatic launching of the automatic launching working. I'm betting I can do it by tinking with the jailbreak task itself.
The jailbreak will run commands that are either put in its startup folder or added to the registry keys:
HKLM\Software\Jailbreak\RunOnBoot\
HKCU\Software\Jailbreak\RunOnBoot\
Add them as REG_SZ values, you can set the name to whatever and set the value to the command you want to execute.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Like that.
Edit: Now that I look at it the 'RunOnBoot' name isn't the most accurate, but whatever, it works.
Fallout 2
Tested on a Russian localized version by 1C.
Game installs fine, but you can't change the installation folder.
Game requires 640x480 mode, so on Asus VivoTab RT with the recent video driver update you'll need to edit registry as noted here: http://forum.xda-developers.com/showpost.php?p=40959944&postcount=12
High resolution Fallout2 patch is useless. It works, but the game speed becomes too slow to be playable. To try hires mod - copy d3dx9_31.dll from a recent DirectX distribuition to the same directory as a patched fallout2.exe (D3D mode is not working, this DLL is needed by the patch to load), or you may use the attached DLL.
Keyboard hotkeys should be working in Win86emu 0.06+. The attached DLL is not needed since 0.06 for HiRes mod. Only the "normal" hires mode is available due to bug, it would be fixed later.
Double note: hires mode is too slow to be playable.
Thank you very much, it works! How exactly were you able to run the game with the High Resolution patch? I tried it, but the emulator gives me a message that it could not run the exe and then starts the game without the patch. Does it need the DirectX 9 redistributable? The timestamp of the file changes each time I configure it in the high resolution patch configurator - I have the version 1.02US.