Low phone volume - 8525, TyTN, MDA Vario II, JasJam ROM Development
I have an HTC Hermes and I would like the phone volume to be higher than it is, at the highest setting it seems like it's only about mid level to other phones,
the speaakerphone works great, but not the mini phone speaker.
so how can I increase the volume on the phone part of it.
The volume level is on highest already.
I'd like that too.
It's definitly low and sometimes i have trouble to hear in noisy environement.
Summerblues and Randall, you have to give us a little more information to go on.
Have you flashed a WM6 ROM? If so, which one? Some of the WM6 ROMs were supposed to fix this low volume problem.
I use the Schaps 3.57a wm6 rom.
And the volume is lower than the stock rom imo. Is there a patch or a way to fix it ?
Thx
low volume
I'm using vp3G's WM6 Cingular/AT&T Optimized ROMs
Read the Hermes Wiki theres a post on how to fix this
http://wiki.xda-developers.com/index.php?pagename=Hermes_Registry
Do you mean this entry?
====================================
Fix low volume issue
The volume issue has 2 fixes, 1 permanent and 1 temporary.
If you disable the startup animation (see below) it permanently fixes the volume problem.
If you like the animation you can leave it, but you have to put your phone in sleep mode then bring it out of sleep mode after every reboot.
\HKEY_CURRENT_USER\ControlPanel\Volume
add: DWord value name = volume
value data = 4294967295then press power (sleep) wait 10 sec and press power again.
======================================
It basically says: "Remove startup animation and you a golden", but it does not work as advertised. I have Sleuth 3.1 ROM which does not have startup animation, but still the earpiece volume is very low.
konste said:
Do you mean this entry?
====================================
Fix low volume issue
The volume issue has 2 fixes, 1 permanent and 1 temporary.
If you disable the startup animation (see below) it permanently fixes the volume problem.
If you like the animation you can leave it, but you have to put your phone in sleep mode then bring it out of sleep mode after every reboot.
\HKEY_CURRENT_USER\ControlPanel\Volume
add: DWord value name = volume
value data = 4294967295then press power (sleep) wait 10 sec and press power again.
======================================
It basically says: "Remove startup animation and you a golden", but it does not work as advertised. I have Sleuth 3.1 ROM which does not have startup animation, but still the earpiece volume is very low.
Click to expand...
Click to collapse
I've also tried this and it does not have any effect. I'm using VP3G's WM6 AT&T Rom.
I'm kind of just pulling this out of my ass, but I have noticed that on some ROMs, there is a .exe called "set acoustic parameters" or something like that. It runs on first boot. I always assumed that it was the fix for the Hermes being too quiet.
Did your ROMs run that at start up?
larsuck said:
I'm kind of just pulling this out of my ass, but I have noticed that on some ROMs, there is a .exe called "set acoustic parameters" or something like that. It runs on first boot. I always assumed that it was the fix for the Hermes being too quiet.
Did your ROMs run that at start up?
Click to expand...
Click to collapse
Nail on the head! Its that exactly I've tested and cooked many rom's and ALL the ones that dont run "setacoustic.exe" upon a hard reset have low volume.
Here is a sample of what "setacoustic.exe" is setting up....
,Headset mode,,,,,,Speaker phone mode,,,,,,Ear-couple mode,,,,,,BT mode,Carkit mode,TTY mode,Alert call -Headset mode,,,,,,Alert call - Speaker phone mode,,,,,,Alert call - Ear-couple mode,,,,,,Alert call - BT mode,Alert call - Carkit mode,Alert call - TTY mode
Operator ID,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Patch ID,0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f,10,11,12,13,14,15,16,17,18,19,1a,1b,1c,1d,1e,1f,20,21,22,23,24,25,26,27,28,29
Volume Leve ID,0,1,2,3,4,5,0,1,2,3,4,5,0,1,2,3,4,5,0,0,0,0,1,2,3,4,5,0,1,2,3,4,5,0,1,2,3,4,5,0,0,0
codecTxGain,4000,4000,4000,4000,4000,4000,2D4E,2D4E,2D4E,2D4E,2D4E,2D4E,5A67,5A67,5A67,5A67,5A67,5A67,4000,4000,4000,4000,4000,4000,4000,4000,4000,2D4E,2D4E,2D4E,2D4E,2D4E,2D4E,4000,4000,4000,4000,4000,4000,4000,4000,4000
codecRxGain,4000,4000,4000,4000,4000,4000,5A67,5A67,5A67,5A67,5A67,5A67,4000,4000,4000,4000,4000,4000,4000,4000,4000,4000,4000,4000,4000,4000,4000,5A67,5A67,5A67,5A67,5A67,5A67,32D6,32D6,32D6,32D6,32D6,32D6,4000,4000,4000
codecSTGain,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
txVolume,E314,E314,E314,E314,E314,E314,B460,B460,B460,B460,B460,B460,A0C2,A0C2,A0C2,A0C2,A0C2,A0C2,4000,4000,4000,E314,E314,E314,E314,E314,E314,B460,B460,B460,B460,B460,B460,7FB2,7FB2,7FB2,7FB2,7FB2,7FB2,4000,4000,4000
rxVolume,4000,4000,4000,4000,4000,4000,5A67,5A67,5A67,5A67,5A67,5A67,656E,656E,656E,656E,656E,656E,4000,4000,4000,4000,4000,4000,4000,4000,4000,5A67,5A67,5A67,5A67,5A67,5A67,7FB2,7FB2,7FB2,7FB2,7FB2,7FB2,4000,4000,4000
pcm_format_ctrl,C22,C22,C22,C22,C22,C22,422,422,422,422,422,422,422,422,422,422,422,422,422,422,422,C22,C22,C22,C22,C22,C22,422,422,422,422,422,422,422,422,422,422,422,422,422,422,422
ecSwitch,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,0,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,0
ecMode,0,0,0,0,0,0,2,2,2,2,2,2,0,0,0,0,0,0,1,1,1,0,0,0,0,0,0,2,2,2,2,2,2,0,0,0,0,0,0,1,1,1
ecStartupMuteHangoverThres,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,320,320,320,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,190,320,320,320
ecFarendHangoverThres,00F0,00F0,00F0,00F0,00F0,00F0,320,320,320,320,320,320,0,0,0,0,0,0,0,0,0,00F0,00F0,00F0,00F0,00F0,00F0,320,320,320,320,320,320,0,0,0,0,0,0,0,0,0
esecDoubletalkHanoverThres,07D0,07D0,07D0,07D0,07D0,07D0,A0,A0,A0,A0,A0,A0,4B0,4B0,4B0,4B0,4B0,4B0,190,190,190,07D0,07D0,07D0,07D0,07D0,07D0,00A0,00A0,00A0,00A0,00A0,00A0,320,320,320,320,320,320,190,190,190
hecDoubletalkHanoverThres,A0,A0,A0,A0,A0,A0,A0,A0,A0,A0,A0,A0,320,320,320,320,320,320,190,190,190,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,320,320,320,320,320,320,190,190,190
aecDoubletalkHanoverThres,A0,A0,A0,A0,A0,A0,A0,A0,A0,A0,A0,A0,320,320,320,320,320,320,190,190,190,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,00A0,320,320,320,320,320,320,190,190,190
ecStartupMuteMode,0,0,0,0,0,0,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0
ecMuteOverride,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
ecStartupErleThres,7F,7F,7F,7F,7F,7F,7FFF,7FFF,7FFF,7FFF,7FFF,7FFF,5A,5A,5A,5A,5A,5A,007F,007F,007F,007F,007F,007F,007F,007F,007F,7FFF,7FFF,7FFF,7FFF,7FFF,7FFF,007F,007F,007F,007F,007F,007F,007F,007F,007F
ecForceHalfDuplex,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
esecResetThres,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300
hecResetThres,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300,300
aecResetThres,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000,3000
ecfiltInputOfset,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
rxAgcEnableFlag,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
tx_agc static gain,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65,7F65
tx_agc_Aig,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
tx_agc_exp_thres,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780,780
tx_agc_exp_slope,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A,FF9A
tx_agc_compr_thres,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C,1B0C
tx_agc_compr_slope,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333,F333
rxAvcEnableFlag,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
AvcRlinkSensitivityOffset,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00,ED00
AvcFlinkHeadroom,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
txAgcEnableFlag,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
rx_agc static
Click to expand...
Click to collapse
oh and there are 120 odd of these xml files!!
so how would we add this into a home cooked rom of our own (or tell if it is in the base rom we are using!)
??
Cheers
crazyC said:
so how would we add this into a home cooked rom of our own (or tell if it is in the base rom we are using!)
??
Cheers
Click to expand...
Click to collapse
Add this to your kitchen
Oh I forgot ..... the 120 odd xml files are already in the roms, so Ive never had any problems there.
crazyC said:
so how would we add this into a home cooked rom of our own (or tell if it is in the base rom we are using!)
??
Cheers
Click to expand...
Click to collapse
Well, the fastest/laziest way to find out if it is in the rom you are using is to ask the maker. Or, if you don't want to do that, you could do a full back up and hard reset. It should run the first boot config again after the setup.
Really though, the setacoustic.exe file takes a really long time to load. Long enough that you would probably remember it if had loaded.
How do i install that in the rom i'm using atm ?
Thx
how can we install it ?
servelle said:
how can we install it ?
Click to expand...
Click to collapse
you must cook my files into a rom for it to work.
Ratcom, I was just moving files around on my pc today, and noticed some set acc. files transferring over from some old rom dumps etc, so I took a peek, I have 61 files here including the .exe, I thought they were .xml files also, but these are .csv, are you sure on that xml? I could have some jacked up files, I didn't check a rom directly.
Also, about cooking them in, Im thinking it should be possible to just dump them in the windows directory of the rom you are currently running, and run the .exe, and then they could even be deleted afterwards, Im have not checked this for myself though.
I am also wondering if the .csv/or if its .xml count in each rom that had it is the same. If anyones cares for the files I have, lemme know, I can't post attachments through PIE atm, but Ill up them later if anyone is interested.
Btw, the .csv count jumps from setaccousticparam29 to setaccoustic100, on these files I have here, meaning nothing inbetween 29 and 100, and not having checked a few roms directly myself at the moment, Im not sure if those were intentionally left out oem.
edit: After just quickly checking the above zip, the cusTSK.exe is for setting a .tsk file aka oem preconfig theme, and isn't needed, but that's no biggie, not sure about the others, I would have to check better.
ChaoticDruid said:
Ratcom, I was just moving files around on my pc today, and noticed some set acc. files transferring over from some old rom dumps etc, so I took a peek, I have 61 files here including the .exe, I thought they were .xml files also, but these are .csv, are you sure on that xml? I could have some jacked up files, I didn't check a rom directly.
Also, about cooking them in, Im thinking it should be possible to just dump them in the windows directory of the rom you are currently running, and run the .exe, and then they could even be deleted afterwards, Im have not checked this for myself though.
I am also wondering if the .csv/or if its .xml count in each rom that had it is the same. If anyones cares for the files I have, lemme know, I can't post attachments through PIE atm, but Ill up them later if anyone is interested.
Btw, the .csv count jumps from setaccousticparam29 to setaccoustic100, on these files I have here, meaning nothing inbetween 29 and 100, and not having checked a few roms directly myself at the moment, Im not sure if those were intentionally left out oem.
edit: After just quickly checking the above zip, the cusTSK.exe is for setting a .tsk file aka oem preconfig theme, and isn't needed, but that's no biggie, not sure about the others, I would have to check better.
Click to expand...
Click to collapse
How do you run the .Exe in the windows directory ?
Tapping on it once should run it.
larsuck said:
Tapping on it once should run it.
Click to expand...
Click to collapse
it does'nt work when I tap on it in windows explorer
Related
Guide to upgrading Universal with MaUpgradeUt_noID.exe
How to update your rom to the latest I-mate version (with push email) and Radio 1.09.0 using the MaUpgradeUt_noID.exe method 1 – download the file “Universal_Upgrade_v1.30.68_radio_1.09.0.zip” from the ftp site (see bottom of post for details) 2 - double click the file and allow it to unpack into a folder 3 – right click on the active sync icon in your tasks tray on you pc (at the stage you should NOT have you universal plugged in) 4 – select connection setting then untick “allow USB connections” 5 – Now take your Universal and take out the SIM and MEMORY CARD 6 – Press light + power + reset with the phone on, this will place the universal into bootloader mode 7 – Connect your Universal via the USB cable to your computer directly i.e. not though a USB hub 8 – Now double click on the program called “MaUpgradeUt_noID.exe” (found in to folder from step 1) this will start the upgrade process, the first stage takes about 3 to 5 minutes to complete, you will then be presented with a screen showing a “Imate Jam” and some information about what you are upgrading to, don’t be worried if this screen does not show you the version numbers you have at present that is normal. 9 – Now continue with the process by clicking upgrade/next 10 – After sometime (about 20 minutes) you should be at the end screen tell you to unplug and reset you “jam” So now unplug your universal and reset it and that’s all there is to it! Note that during the upgrade process you can follow the progress by also looking at your universal screen with a light source as the backlight will be off. I hope this post helps someone as looking around the forum Im amazed by the amount of people asking “how do I upgrade my rom” or “I only get a “country id error” when trying to update” The “Universal_Upgrade_v1.30.68_radio_1.09.0.zip” file can be found here ftp://xda:[email protected]/Uploads/Universal/Universal_Upgrade_v1.30.68_radio_1.09.0.zip This file contains the latest imate beta rom v1.30.68 and the latest radio 1.09.0 plus all the tools you need Oh and if anyone thinks Ive missed something out please post and let me know!
File as been moved its now at :- ftp://xda:[email protected]/Universal_Upgrade_v1.30.68_radio_1.09.0.zip This file contains everything need to upgrade your universal
Thanks rat - very cool of you to post up a guide. How Nb is it to remove your SIM?
wamatt said: Thanks rat - very cool of you to post up a guide. How Nb is it to remove your SIM? Click to expand... Click to collapse No sure I understand the question however Ive updated before now with the sim card in however lots of people report that its important to remove both the memory & sim cards so Ive included it because its better to be safe than sorry
Thanks I'll play it sorry :/..
BTW do you have to use this NOID method if you have an IMATE too?
wamatt said: BTW do you have to use this NOID method if you have an IMATE too? Click to expand... Click to collapse No you should be ok using the orginal package, however this way will still work
I installed the ROM but after the installation is finished and I reset the device I only get a blank screen.
Piesang said: I installed the ROM but after the installation is finished and I reset the device I only get a blank screen. Click to expand... Click to collapse Blank screen but do you have the USB or SERIAL written on the Screen? Rat didn't mention in his post but it comes out in the last screen that it is supposed to be a HARD RESET which will bring about a menu where you have to press 0 (Zero) to ahrd reset the device. hope this helps
Yip, sorry, That's correct. I get the screen that says I have to press 0 to reset or X to exit. If I press 0 the screen goes blank and stays like that. I've installed the previous ROM now and it is working perfectly. It's just the new ROM on this page doesn't want to work on my Jasjar.
Piesang said: Yip, sorry, That's correct. I get the screen that says I have to press 0 to reset or X to exit. If I press 0 the screen goes blank and stays like that. I've installed the previous ROM now and it is working perfectly. It's just the new ROM on this page doesn't want to work on my Jasjar. Click to expand... Click to collapse I downloaded it straight from the first post and it installed flawlessly... Have you tried installing it from bootloader mode instead of direct update? And without SD card in the PDA? This might work. BTW, I have returned to the older ROM.... advantages don't outweigh the disadvantages. My phone keeps on hanging (for the 1st time ever after 5 months use and different ROMs) on the screen where it shows whose calling. I havent answered the call yet but it stops ringing. When i open the PDA it has ANSWER on the left softkey and pressing this doesn't do anything. Will wait for the release.. It is a lot faster thought (the test ROM)
Thanks for the info. I'm not gonna bother upgrading now. I'll wait for a decent ROM later. Thanks m8
umm - stupid question I know..... But what does this actually DO?? I understand that this will upgrade the radio stack and thus produce better reception etc - but what else will it do?? If I have an Orange M5000 will I still be able to use it on Orange's network?? Do i need to fill in any settings? Do I need to make notes of certain stuff beforehand? If so - what settings? I assume this will totally rewrite the registry and what programs are on teh device - or will it?? I suppose a lot of this information is available on the forum - but tracking it down can take a lot of time for someone who's not necessarily that 'au fait' with the working of the device.
Riceburner said: umm - stupid question I know..... But what does this actually DO?? I understand that this will upgrade the radio stack and thus produce better reception etc - but what else will it do?? If I have an Orange M5000 will I still be able to use it on Orange's network?? Do i need to fill in any settings? Do I need to make notes of certain stuff beforehand? If so - what settings? I assume this will totally rewrite the registry and what programs are on teh device - or will it?? I suppose a lot of this information is available on the forum - but tracking it down can take a lot of time for someone who's not necessarily that 'au fait' with the working of the device. Click to expand... Click to collapse I also have an orange M5000 which I would like to get off Orange to use my Vodafone SIM - would installing this new ROM be the way to go ?
not if your phone is simlocked (or network locked). new rom is only the software.
Yeah, sorry Just reading the other thread on this - sorry , am a relative newby. It looks like MachineGod and Buzz are on the case though - and with their track record........
I wanted to confirm that Ratcom's file he linked to is good (not corrupt) and his method for upgrade works. Nice work, Ratcom.
ratcom said: File as been moved its now at :- ftp://xda:[email protected]/Universal_Upgrade_v1.30.68_radio_1.09.0.zip This file contains everything need to upgrade your universal Click to expand... Click to collapse Hi , Can let me know the speed of the Os did u face any problems after upgrade. E.g Apps, Hanging , Memmory leaks. Etc. Cheers
I had no problems what so ever with this rom, the speed of the os was breathtaking.
ratcom said: I had no problems what so ever with this rom, the speed of the os was breathtaking. Click to expand... Click to collapse Does this rom work on dopod 900? Is this is final release? Cheers,
AT&T Today Screens and Splash Screens?
Looking for AT&T splash and today screens.
arluckett2002 said: Looking for AT&T splash and today screens. Click to expand... Click to collapse I would like to get my hands on these images too. The way I have been doing it is flash back to the original ROM, once stock flash the radio back to the new version you want, then flash the OS to the new ROM version. You have to pick a rom that doesn't touch the splash though. Only went through that PITA once. It would be nice in case a Cingular Rep ever got their hands on it.
Here are the Boot Splashes http://rapidshare.com/files/27766939/Cingular-ATT_BootSplash.zip.html has the PrimarySplash.nb/SecondarySplash.nb and the RUU_signed.nbh I just did and tested. I'm still looking for the today screen
Daali said: http://rapidshare.com/files/27766939/Cingular-ATT_BootSplash.zip.html has the PrimarySplash.nb/SecondarySplash.nb and the RUU_signed.nbh I just did and tested. I'm still looking for the today screen Click to expand... Click to collapse You rock! Are these the animated ones?
These were pulled from the RUU_Hermes_CINGULAR_WWE_2_1_.06.502.3_6275_1.33.31.00_108_Ship.exe You looking for the animated 3G .gif that resides in Windows? http://rapidshare.com/files/27773791/3G_Up_01_1.zip.html
At&t Splash Screen How Do You Convert Gif Files To Nb File
Seek and ye shall find - check the wiki and/or www.mrvanx.org.
Daali said: These were pulled from the RUU_Hermes_CINGULAR_WWE_2_1_.06.502.3_6275_1.33.31.00_108_Ship.exe You looking for the animated 3G .gif that resides in Windows? http://rapidshare.com/files/27773791/3G_Up_01_1.zip.html Click to expand... Click to collapse Yeah thats the one. Can I just drop and replace this one?
from the FAQ: Code: Disable/change the startup animation or sound HKLM\SOFTWARE\HTC\StartupAnimation Enabled - change from 1 to 0 to turn everything off and permanently fix the volume issue. You can also customize the animated boot up by deleting or changing 2 keys. (Doing this does not fix the volume issue) Delete the WAVFile Key to remove the sound only. Delete the GIFFile Key to remove the animation only. Put your own .GIF file or .WAV file on the phone and rewrite the 2 keys (WAVFile GIFFile) to the new file location. i.e. \My Documents\Files\CustomAnimation.gif The Gif key portion was where this .gif was linked on the original. Place it somewhere and change that key.
Daali said: from the FAQ: Code: Disable/change the startup animation or sound HKLM\SOFTWARE\HTC\StartupAnimation Enabled - change from 1 to 0 to turn everything off and permanently fix the volume issue. You can also customize the animated boot up by deleting or changing 2 keys. (Doing this does not fix the volume issue) Delete the WAVFile Key to remove the sound only. Delete the GIFFile Key to remove the animation only. Put your own .GIF file or .WAV file on the phone and rewrite the 2 keys (WAVFile GIFFile) to the new file location. i.e. \My Documents\Files\CustomAnimation.gif The Gif key portion was where this .gif was linked on the original. Place it somewhere and change that key. Click to expand... Click to collapse Strange... I don't have these entries. May be the ROM that I am using (Black 2.5) I will try adding them and seeing if that works. Thanks for the info. All of the stuff I got from the wiki pertained to cooking/converting an image.
I assume: KLM\SOFTWARE\HTC\StartupAnimation Enabled - change from 1 to 0 to turn everything off and permanently fix the volume issue. Click to expand... Click to collapse is a DWord decimal value of 1? and Delete the GIFFile Key to remove the animation only. Click to expand... Click to collapse and this is a String value to the path\file? BTW: I am now on the Dutty V2 ROM and these values do not exist. Might they only work on factory HTC/ATT "hacked" roms? I have read there might be DLL's that go with these entries.
At&t Today Screens And Splash Screens Well Has Anyone Been Able To Get The Animation Version To Work?
JERFER4294 said: Well Has Anyone Been Able To Get The Animation Version To Work? Click to expand... Click to collapse I put the entries in as above and it did not work. I ended up using the one w/o animation. I have a feeling you only have the registry entries there to be modified if you have an OEM ROM.
I have a feeling there are a few more registery entries in there then he wrote in there - would like to see a reg dump (at least of that section). There are also probably some .DLL's or other files we need to fully get it running! Maybe I'll dump a Cingular rom later to see if I don't see anything obvious I'm assuming this is in the new Cingular rom?
Yes, should even be in the one before it since when I bought my phone about 2 months ago it was animated as well.
So far from the digging, the Registry entries are: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\HTC\StartupAnimation] "Volumn"=dword:10 "WAVFile"="\\Windows\\3G_Up.wav" "GIFFile"="\\Windows\\3G Up_01_1.gif" "Enabled"=dword:1 I've not yet found any other entries related to it on a quick pass through. The animated gif and sound file I have attached but I have not yet got it to work. I did notice there is no welcomehead.96.png and I wonder if it the existence of that file on my current rom has anything to do with it. I've not been able to delete the file (part of the rom) to see if it would have any effect. This is about as much as I'll be able to figure out for right now at any rate. If anybody else has any ideas as to enabling it (is there a .DLL that needs to be loaded? Part of me wonders if there is a command to execute it built into the bootsplash within the section that is usually added as padding? Just some brainstorming.
chymmylt said: So far from the digging, the Registry entries are: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\HTC\StartupAnimation] "Volumn"=dword:10 "WAVFile"="\\Windows\\3G_Up.wav" "GIFFile"="\\Windows\\3G Up_01_1.gif" "Enabled"=dword:1 I've not yet found any other entries related to it on a quick pass through. The animated gif and sound file I have attached but I have not yet got it to work. I did notice there is no welcomehead.96.png and I wonder if it the existence of that file on my current rom has anything to do with it. I've not been able to delete the file (part of the rom) to see if it would have any effect. This is about as much as I'll be able to figure out for right now at any rate. If anybody else has any ideas as to enabling it (is there a .DLL that needs to be loaded? Part of me wonders if there is a command to execute it built into the bootsplash within the section that is usually added as padding? Just some brainstorming. Click to expand... Click to collapse Anyone? I like to know this too.. any luck yet?
chymmylt said: So far from the digging, the Registry entries are: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\HTC\StartupAnimation] "Volumn"=dword:10 "WAVFile"="\\Windows\\3G_Up.wav" "GIFFile"="\\Windows\\3G Up_01_1.gif" "Enabled"=dword:1 I've not yet found any other entries related to it on a quick pass through. The animated gif and sound file I have attached but I have not yet got it to work. I did notice there is no welcomehead.96.png and I wonder if it the existence of that file on my current rom has anything to do with it. I've not been able to delete the file (part of the rom) to see if it would have any effect. This is about as much as I'll be able to figure out for right now at any rate. If anybody else has any ideas as to enabling it (is there a .DLL that needs to be loaded? Part of me wonders if there is a command to execute it built into the bootsplash within the section that is usually added as padding? Just some brainstorming. Click to expand... Click to collapse You can delete the welcomehead.96.png by getting another file browser (like Resco Explorer or Total Commander) and changing the file permission.
some at&t today themes would be nice. i really like my WM6 Vanilla theme, but if someone could throw the new at&t logo on there somewhere id be very appreciative. maybe the bottom right corner of the today screen?
According to this forum >http://forums.wireless.att.com/cng/...ngular&message.id=41950&query.id=90285#M41950 You have to power the unit off for 10 seconds for the changes to take effect. Dont have time to check it. Can someone verift?
Vp3g's 3.62.3 Full with SetAcoustic Now Available!
Ok. So I did find all the xml files for SetAcoustic in the rom, however didn't find the EXEC line in the precofig file. So if you need more volume out of your earpiece @Vp3g: if you did add it into the rom (perhaps the extended rom) then I'm sorry and this is a waste of time. If not, d/l it and make sure to run the Volume.cc cab (attached). EDIT: http://www.megaupload.com/?d=CEDO35FA Thanks to 65coupie6 for getting it right the first time! And of course thanks to Vp3g for his wonderful rom!
Thanks a lot, that was fast.
Full ROM w/SetAcoustic enabled http://www.megaupload.com/?d=CEDO35FA
intrglctcrevfnk said: Ok. So I did find all the xml files for SetAcoustic in the rom, however didn't find the EXEC line in the precofig file. So if you need more volume out of your earpiece @Vp3g: if you did add it into the rom (perhaps the extended rom) then I'm sorry and this is a waste of time. If not, d/l it and make sure to run the Volume.cc cab (attached). edit: getting a 262 error... removing till i find the problem.... Click to expand... Click to collapse Which XML files and what EXEC are you referring to? SetAcousticParam is in the startup and there's a series of CSV files, but beyond that I don't honestly know how it all relates. And what does the CAB do?
vp3G said: Which XML files and what EXEC are you referring to? SetAcousticParam is in the startup and there's a series of CSV files, but beyond that I don't honestly know how it all relates. And what does the CAB do? Click to expand... Click to collapse The xml files I pulled out of Schaps rom. It's a lot of xml that default open on the desktop for MS Excel. Also there is a SetAcousticParam.exe that needed to be put in the preconfig.txt (in windows.nb) After Lock:Enabled EXEC:\Windows\EnableHSDPA....then the att.tsk... Then I added the EXEC:\Windows\SetAcousticParam.exe after that (sorry if syntax is a little off, doing it from the top of my head) What is odd to me (and probably why my initial try messed up) is that although I could not see the various files in the root of the extracted windows.nb; When I went to copy those files from my hard drive it asked if I wanted to overwrite those files. I said no, believing that they were there. I really think that is where I messed up. (and why installation failed.) Even after canceling the copying, I still couldn't see the setacoustic xml's... Now the Volume_CC.cab, I was just following directions from when I had learned how to do it in the first place. I believe it does some registry editing to change the 'volume earpiece uplink' settings. It's from elsewhere on the forum. Don't know exactly why it's needed, just that it is.? So anyway, love your rom. But I work in a kitchen and find that the volume is just not loud enough. (I also play in a touring cover band on the weekends, so that doesn't help either.) That's why I'm always tinkering with your roms. Thanks again.
Thanks for cooking up the volume increase into vp3g's awesome ROM config. Without the volume mod, I was pressing the phone hard on my ear to hear the other party. Now 1 or 2 clicks is plenty.
I've been using this rom for almost a week and am loving it, i don't think i'll be switching for a while.
vp3G said: And what does the CAB do? Click to expand... Click to collapse It does this (puts these values to registry): HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN EARPHONE_UPLINK_VOLUME "CC" RECEIVE_UPLINK_VOLUME "CC" HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN0 EARPHONE_UPLINK_VOLUME "CC" RECEIVE_UPLINK_VOLUME "CC" HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN1 EARPHONE_UPLINK_VOLUME "CC" RECEIVE_UPLINK_VOLUME "CC" HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN2 EARPHONE_UPLINK_VOLUME "CC" RECEIVE_UPLINK_VOLUME "CC" In combination to initial SetAcousticParam run after Hard Reset or New ROM installation it makes huge difference to the volume of incall sound. Hope to helped a bit!
intrglctcrevfnk said: What is odd to me (and probably why my initial try messed up) is that although I could not see the various files in the root of the extracted windows.nb; When I went to copy those files from my hard drive it asked if I wanted to overwrite those files. I said no, believing that they were there. I really think that is where I messed up. (and why installation failed.) Even after canceling the copying, I still couldn't see the setacoustic xml's... Click to expand... Click to collapse The setacoustic files are in the rom, they are hidden and possibly system files which is why you do not see them. SetAcoustic runs from the startup directory every time the device is reset, there is no difference if you include it in the auto config or not. I only include it in my auto config for those that believe it actually makes a difference.
I think it runs from startup directory if there is the link in the folder and ONLY once because it self deletes the ".lnk" from the startup folder I have seen this bahaviour in 4 different ROMS . Please check it for yourself if I am correct
CUSTEL said: The setacoustic files are in the rom, they are hidden and possibly system files which is why you do not see them. SetAcoustic runs from the startup directory every time the device is reset, there is no difference if you include it in the auto config or not. I only include it in my auto config for those that believe it actually makes a difference. Click to expand... Click to collapse It makes a big (!) difference, but to get it to work the SetAcousticParam command needs to be the first command (after lock:disabled) in the preconfig.txt file. The program exits immediatelly if it's not listed as the first command, but it runs ok if it is the first command. After this you need to run the volume-cab-file to have a loud and clear volume.
jgeerts said: It makes a big (!) difference, but to get it to work the SetAcousticParam command needs to be the first command (after lock:disabled) in the preconfig.txt file. The program exits immediatelly if it's not listed as the first command, but it runs ok if it is the first command. After this you need to run the volume-cab-file to have a loud and clear volume. Click to expand... Click to collapse It doesn't matter where it's located in the config.txt.... It's been in every rom I've made in the past 7 months and I have only ran it in the initial customization process on two, there was no notable difference. I would go through a standard battery every 4 hours I think that shows how much I used my hermes, I would know if there was a difference.
CUSTEL said: It doesn't matter where it's located in the config.txt.... It's been in every rom I've made in the past 7 months and I have only ran it in the initial customization process on two, there was no notable difference. I would go through a standard battery every 4 hours I think that shows how much I used my hermes, I would know if there was a difference. Click to expand... Click to collapse Strange!, my tests show otherwise. I have never used your roms, so I can't compare it with your findings. I installed Schaps 4.0 (and 4.01) and I saw on initial startup that SetAcousticParams was started and it exits almost immediatelly. So I extracted the rom (NBDump) and changed the two lines in preconfig.txt (make sure it was listed first), I also changed the SetAccousticParam*.* files to make then vissible (attrib -h -r -s) , did a rebuild (NBBuild), flashed it to my device and saw that SetAcousticParam was running for more than a minute and afterwards I noticed that the volume on my device was loud and clear (this was not the case when I used Schaps rom without modification).
I'm glad this is getting around! I should have known that they were hidden files....damn attributes.... I'm shure that Custel has to be right (at least partially), he's on the top of the list of knowledgeable cookers...but I feel better seeing it run in the initial setup.. Oh well at least it works!
Question to you guys who got the setacousticparams working: Is your speakerphone usable? Does it have the common problems of: 1. Speakerphone volume is too loud even at minimum volume setting. 2. Other party cannot hear you when using the speakerphone.
Yes, the speaker phone is usable. The volume is much better and I have no problems with the other parties hearing me. Althoguh if I remember correctly, I tried this version and the setAcoustic still did not run. I ended up adding it in the rom myself.
Help. Okay, I am a NEWBIE. I have the HTC P3600 with original WM5 ROM. And yes the IN Call Volume in my phone is freaking low!! I did downloaded the volume. cab from above link and installed it in my Trinity. It shows in Add and remove Programs so I know it installed. BUT It does not seems to make my in call volume louder. Can someone tell me what I am doing wrong??? Am I supposed to have a different ROM before installing this volume.cab? Thanks.
robjbw said: Okay, I am a NEWBIE. I have the HTC P3600 with original WM5 ROM. And yes the IN Call Volume in my phone is freaking low!! I did downloaded the volume. cab from above link and installed it in my Trinity. It shows in Add and remove Programs so I know it installed. BUT It does not seems to make my in call volume louder. Can someone tell me what I am doing wrong??? Am I supposed to have a different ROM before installing this volume.cab? Thanks. Click to expand... Click to collapse So.... in conclusion..... Will just downloading the cab file solve low incall volume or is there a series of reg edits that are required first? When i have satnav on in the car, volume at top, if I get an incoming call, the volume is too low to hear. They can hear me talking ok, but I can hardly hear them. Will this cab help? Thanks as always, Mattster.
Too early for "in conclusion..". I just flashed the CRC V11 ROM and watched for setacousticparam to load. I saw the file displayed for about one second before it moved to the next file. My previous experience with the Kin0Kin ROMS were that this file takes a rather long time to execute. Other than a qualitative evaluation (my sound isn't good, etc.), is there a way to check that setacousticparam has executed properly?
jws3 said: Too early for "in conclusion..". I just flashed the CRC V11 ROM and watched for setacousticparam to load. I saw the file displayed for about one second before it moved to the next file. My previous experience with the Kin0Kin ROMS were that this file takes a rather long time to execute. Other than a qualitative evaluation (my sound isn't good, etc.), is there a way to check that setacousticparam has executed properly? Click to expand... Click to collapse Yes I had the same observation with CRCs r11.0. Setacousticparam doesnt run properly (it quits after 2-3 seconds). At first I thought this was because it was not the first EXEC item in the 'preconfig.txt' file. From past experience rebuilding ROMs, I found that setacousticparam only runs properly if it is the first EXEC item in preconfig.txt I redid CRCs r11 ROM, changing setacousticparam to the first EXEC item in preconfig.txt. It still did not run properly. So something else in that ROM is causing it not to work. I'm now trying to do the same thing with CRCs older WM6.1 ROMs to see if I can get setacousticparam to work properly. UPDATE: Tried CRCs 9.2, 10.8 and 11.0. All couldn't run setacousticparam properly. I also tried removing the attributes -h -r -s from the .csv files. No go. Could it be that setacousticparam is incompatible with WM6.1? One thing is for sure though: If setacousticparam runs properly, it takes around 1 minute to run. If not, then it exits within 2 to 3 seconds. Conversely if setacousticparam runs for only 2-3 seconds, then it did not work.
Help - HTC TouchPro2 Sprint - Side volume up/down buttons no longer working
Anyone ever have the volume up/down buttons on the side of the phone stop functioning correctly? Looks like the buttons themselves still work (they now scroll up/down on pages instead of adjusting volume up/down). Any suggestions? I'm running Energy Rom sense 2.5, cookie hometab 1.6 and HDwalls with cookie patch. Thanks
Didy ou install the keyboard fix after installing the energy ROM?
Thanks for the response. No - was not aware of one. I can check out the energy thread for it. Odd though because this just happened yesterday (volume sidebar was working fine before then) and ive been running the rom for like two weeks now. Only new thing I did yesterday was install transparent tabs, a cookie tab fix and new wallpaper thru HD Wall. Matt
stenuine said: Thanks for the response. No - was not aware of one. I can check out the energy thread for it. Odd though because this just happened yesterday (volume sidebar was working fine before then) and ive been running the rom for like two weeks now. Only new thing I did yesterday was install transparent tabs, a cookie tab fix and new wallpaper thru HD Wall. Matt Click to expand... Click to collapse I know there are reg edits available in cab form that change the vol up/down buttons into up/down scroll buttons. Nothing in your list would be likely to include that, but it's possible...that's the only thing I can think of that would change their behavior like that.
Thanks. I might just look to isolate those two areas and try to set back. I also have that zoombar app (to use for other purposes) but dont think that would affect it, plus I didnt have the problem until days after i installed. Tried soft/hard reset as well with no avail. sirphunkee said: I know there are reg edits available in cab form that change the vol up/down buttons into up/down scroll buttons. Nothing in your list would be likely to include that, but it's possible...that's the only thing I can think of that would change their behavior like that. Click to expand... Click to collapse
stenuine said: Thanks. I might just look to isolate those two areas and try to set back. I also have that zoombar app (to use for other purposes) but dont think that would affect it, plus I didnt have the problem until days after i installed. Tried soft/hard reset as well with no avail. Click to expand... Click to collapse I'm guessing you mean just a soft-reset (rebooting)..? A hard-reset is where you wipe the memory clean putting everything in the OS back to stock settings (or back to the fresh version of a custom ROM, if you've flashed one on to your device). If you've hard-reset and this problem still persisted, then you can pretty much rule out software as a cause... Yes, my approach would be to just start uninstalling stuff in reverse order, soft-resetting and testing after each item removed.
Yep - definitely meant soft reset. I'll try your advice. Thanks so much. sirphunkee said: I'm guessing you mean just a soft-reset (rebooting)..? A hard-reset is where you wipe the memory clean putting everything in the OS back to stock settings (or back to the fresh version of a custom ROM, if you've flashed one on to your device). If you've hard-reset and this problem still persisted, then you can pretty much rule out software as a cause... Yes, my approach would be to just start uninstalling stuff in reverse order, soft-resetting and testing after each item removed. Click to expand... Click to collapse
stenuine said: Yep - definitely meant soft reset. I'll try your advice. Thanks so much. Click to expand... Click to collapse No problem! Good luck, and let us know what you find
Hi SirPhunk Deleted everything that I'd installed since the problem occured and still no luck :-/. Buttons on side of phone still scrolling up/down, instead of adjusting volume. I also tried the Sprint keyboard fix for Energy roms, but no luck there as well. Any other ideas? Do you happen to know if theres a way to search for the value in my registry? Thanks again
If you want to go searching in your resgistry for it, PHM_Regedit and Total Commander can both search for specific keys...I would just try the string "volbutton" or even just "volb*", something like that. Now, even though you didn't see the issue immediately when you installed it, I think there's still a possibility that the zoombar app could be the culprit....I would try uninstalling that too (if you haven't already) before you start doing the extra work. EDIT: It also might be easiest to just install Rhodium Keyboard Controller (attached below) and use it to manually map them back to stock function (don't ask me why I didn't think of that in the first place ). In fact, if you do that, try uninstalling RKC right after doing that mapping, and I'll bet they return to their stock function after that even without the app being needed anymore.
Sir Phunk, Thank you for taking the time to investigate and the response, Sir Phunk. I went ahead and dloaded the cab to my storage card, but cant seem to find the files in order to run and edit the keys manually. Sorry if this is a stupid question - I'm still learning the ins n' outs. Maybe this will help me fully install programs that may be hanging around (even though I went to the "remove programs" section and deleted them). Please advise if you have a chance. Again, my apologies as I am still learning. Thank you again.
stenuine said: Sir Phunk, Thank you for taking the time to investigate and the response, Sir Phunk. I went ahead and dloaded the cab to my storage card, but cant seem to find the files in order to run and edit the keys manually. Sorry if this is a stupid question - I'm still learning the ins n' outs. Maybe this will help me fully install programs that may be hanging around (even though I went to the "remove programs" section and deleted them). Please advise if you have a chance. Again, my apologies as I am still learning. Thank you again. Click to expand... Click to collapse Will do...full instructions coming first thing in the morning
Hey stenuine, let's see if we can get this working for you... First, I'm again guilty of not explaining things well enough (seriously), my apologies. That file I posted earlier is actually a .zip file, with 2 .cab files inside...it'll be easiest if you download it to your PC desktop, unzip the 2 files out of there, and then copy them over to the SD card. [TIP: I would strongly recommend creating a "cabs" folder at the root-level of your storage card, and using that to retain any cabs that you run and know that work, even if you're not still using them at the moment. That way, you'll always have easy access to any of them, even through flashes and hard-resets] The first file in that .zip is the sdkcerts cab, run that one first. It allows your phone to use many of the homebrewed apps and tweaks found here at xda. After that one's installed (do a soft-reset again if the install doesn't force that anyway, always a good habit), then you can just run the keyboard controller cab to install it. Once you have the app installed, the icon to run it is found in: Settings -> All Settings -> System (it will say "Keyboard Config"). Once you get it installed ok, here's how to use it to get your key's mapped the way you want: 1. When you first open the app, you'll see what's in the first screenshot below(pretty much a blank screen). 2. Click "Menu" in the bottom right 3. Click "Add key" from the menu 4. You'll see the dialog in the 2nd screenshot below, go ahead and tap the volume-up button 5. Now you'll see what's in the 3rd screenshot below, the setup window. There's a lot of stuff there, but we'll only need some of it for this. First, in the "Key mode" drop-down list, choose "Direct key mapping" 6. Now you see what's in the 4th screenshot. Now what you need to do is click the "Key" dropdown list, and scroll all the way down to pick "117 F6-VOL UP"...if you did all that right, it should look like the 5th screenshot. 7. Click "Ok" in the bottom left of the screen. Now, you should be back to the very first screen you saw, but now with the mapping you just created (screenshot 6). 8. VERY IMPORTANT...at this point you must remember to hit "Update config" in the bottom left, or the work you just did won't have any effect. It'll confirm for you that it updated, and that's it! You just mapped one of the volume buttons 9. Now, follow steps 2-9 again, with the following exceptions: Step 4 - tap the volume down button this time Step 6 - pick "118 F7-VOL DOWN" As long as you did all that, and hit "update config" after each one, you should now be able to close the app and have normal volume-button operation. As you noticed there's a lot of versatility in this little app, so if that still doesn't work for you, there's other ways we can try...this is just the most direct and should work just fine.
Hey SirPhunk, Thanks for your time and the very detailed breakdown. I was able to install the app and run it, but no luck re-assigning the buttons :-/. Tried re-assigning vol-up button to vol-up and vol-down button to vol-down, but no change. To test, I also re-assigned the "up" key on my flip-out keyboard to "volume-up" and still no dice. Made sure to save the registry after each change and tried with and w/o soft resets after the changes. The vol-up and vol-down buttons still just scroll up/down on the screen and up button on keybard still just scrolls up as well. I saw what you meant about other functions for this program, just not sure which to try next in order to fix this issue. Thank you again.
bumping my post...
i just ended up doin a hard reset. My best guess is it could have been the zoombar scroller v2 app that screwed with the settings.
Asus Mypal A6x6 WM6.5 rom version 2 (5-19-10)
Well, school is out for the summer, so I can focus on putting out roms again. With this release, I made another WM6.5 rom to test a new compression type that I'm working with. With the original stock compression type (XPR), I didn't have enough space to fit all the goodness of WM6.5, so I switched to a new compression type (LZX) that lets me pack in more. I'm curious to know how the new compression type performs in comparison to the old one. Does anyone notice things are faster or slower?
Thanks to Makuu (for helping to get me started), Lenny, AstainHellbring (thank you for all the nightly help sessions), the creators of the tools I used to make this rom, and anyone else that I failed to mention in name who gave me the knowledge to complete this rom.
Asus Mypal A6x6 WM6.5 version 2
Windows CE version 5.2.21892 (Build 21892.5.0.89)
This was tested on an Asus Mypal A626 (and works). It should work with the A686/A696, but the other models were not tested. Any other models not metioned above WILL NOT WORK.
Updates
1. new compression type
2. os build
3. bug fixes
Additions
1. Windows Marketplace
2. File Dialogue Changer
3. MS Office Mobile
4. Remote Desktop Mobile (has been added again)
Removals (you can reinstall these via windows marketplace)
1. Windows Live
Removals (non-Windows Marketplace)
1. PsShutXP
download: http://www.easy-share.com/1910266747/Asus_A6x6_WM65_2.rar
At this time, this will be the only download link. Mirrors will be created in the future (after I give permission).
Instructions (I have included a txt file with same instructions for offline convenience)
Before you do anything, make sure you have at least a 256mb SD card and a card reader (you can get one at a place like Radio Shack or Office Depot). You also need to install winrar (found at http://www.win-rar.com/download.html). Your SD card must be formatted with the FAT16 file system.
To format your SD Card with the FAT16 file system
Step 1: To do this insert the SD Card into the reader and go to "My Computer".
Step 1a: BACKUP YOUR FILES before you start!!
Step 2: Right-click the drive letter of the SD Card reader (differs for each computer, probably either E:\ or F:\ or G:\) and click "Format".
Step 2a: Don't worry about any of the options except for file system, choose "FAT"
Step 3: Click "Start" and wait until it is done
Step 1: Get (OS) rom image
Step 2: Extract files to any folder on hard drive using Winrar
Step 3: Go to the folder where you extracted the files in the RAR archive
Step 4: Make sure that the filename is "CANNES_A_WM6.img"
Step 4a: if the img file it's not exactly "CANNES_A_WM6.img", rename it to that
Step 5: Format the SD card if you haven't already done so using the instructions above
Step 6: Copy the img file to the SD card, see step 6a
Step 6a: Make sure that the img file is the ONLY file on the SD card after formatting
Step 7: Take SD Card out of SD Card reader and put it in the a6x6
Step 8: Make sure that the a6x6 is plugged in via ac adapter before doing the next few steps
Step 9: activate SD Loader using the following instructions {
Step 9a: Hold down the power button and enter button (that's the button in the center of the d-pad)
Step 9b: Double tap the soft reset button while holding the other 2 buttons
Step 9c: After double tapping the soft reset button, keep the other 2 buttons held until a blue screen comes up that says something like Asus Cannes flashing utility
Step 9d: Wait until the process is finished (it's near the end when it says "writing private")
}
Step 10: At this point, your a6x6 should reboot on its own
Step 11: enjoy your updated rom
If you have any questions, feel free to just post or PM me.
As I release new roms, if you have a support question, please give me the rom version so I know what rom you are working with. You can get the rom version from the filename of the rom pack.
Example: Asus_A626_WM614_1
A626 = device (most often it will be A626, will rarely be different), WM614 = os version, 1 = release #
I only added MS Office Mobile this time because the new MS Office Mobile 2010 had not been released yet. For my next release, I am not including MS Office Mobile due to the fact that you can download the new version free from Marketplace. My work is free for everyone's use, but if you feel compelled to give a donation towards my work (I am a full-time college student working on this in what little spare time I have), my paypal e-mail is "[email protected]"
Steven855 said: I only added MS Office Mobile this time because the new MS Office Mobile 2010 had not been released yet. For my next release, I am not including MS Office Mobile due to the fact that you can download the new version free from Marketplace. Click to expand... Click to collapse Some indication about free memory after 6.5 rom installation? If something wrong, is possible to reinstall the official 6.1 rom? Thanks Massimo
maxambro said: Some indication about free memory after 6.5 rom installation? If something wrong, is possible to reinstall the official 6.1 rom? Thanks Massimo Click to expand... Click to collapse Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Appropriate to glorify Steven855 said: Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6. Click to expand... Click to collapse Thank you so much for extraordinary job on rom ver. 2 !!! I was intalled this on my ASUS 696 and it went smoothly without any problems. In addition, it looks more faster as you mentioned beside rom ver. 1. The current rom taking the sum of 29.53MB from a total of 53.35MB memory (what let us 23.82MB free at the program memory section). Again you made a really holiness work due to the fact our mypals still relevant...
Steven855 said: Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6. Click to expand... Click to collapse Installed this ROM today, and performance on my A696 is not so good... First – after reboot it was stuck on Windows startup screen for 4-5 minutes. I thought the flashing process went wrong, but eventually it booted up. I haven't tested it thoroughly yet, but the first things I noticed – reaction to any user event (tapping, scrolling, etc.) is MUCH slower than on the WM6.1 I'd had before. Haven't tested the application performance yet. Also, when I tap on the battery indicator nothing happens.
v.real said: Installed this ROM today, and performance on my A696 is not so good... First – after reboot it was stuck on Windows startup screen for 4-5 minutes. I thought the flashing process went wrong, but eventually it booted up. I haven't tested it thoroughly yet, but the first things I noticed – reaction to any user event (tapping, scrolling, etc.) is MUCH slower than on the WM6.1 I'd had before. Haven't tested the application performance yet. Also, when I tap on the battery indicator nothing happens. Click to expand... Click to collapse Yeah, I forgot to mention that 1st boot time has increased with this rom. This is due to the new compression type. For the power icon, I just noticed your concern. Unfortunately, I don't have a fix for it right now. You can still view battery information by going into the settings.
If anyone knows how to flash a rom in a different language, please enlighten me. I have made an attempt at making an international rom (this time was German), but I can't get it to boot (I have an English version A626). I think the reason it won't boot is because I didn't configure the firmware right (the os is right though).
ROM working very good so far on my Asus A696. Looking forward to a German version but I could live with the US ROM. Thanks for your hard work. You could also see battery level by using the ASUS Manager Icon on the Today Screen.
Good job I would donate, for a Portuguese language rom. Thanks!
Problem with rom 2 Hi Steven, I noticed in a one small problem of rom 2 after flashed on my asus 696. The problem is that whenever i push the power button shortly and alternatively i'm trying to push it again to power on, it failes to succeed what leaves me to make an another resets for several times. Can you resolve this issue during upcoming next rom? Thanks for your good job!
Was a little slow and less responsive on the first startup, but after a soft reset it worked GREAT! Once again beautiful work Steven, thank you very much!!!!!
dj.brudo said: Hi Steven, I noticed in a one small problem of rom 2 after flashed on my asus 696. The problem is that whenever i push the power button shortly and alternatively i'm trying to push it again to power on, it failes to succeed what leaves me to make an another resets for several times. Can you resolve this issue during upcoming next rom? Thanks for your good job! Click to expand... Click to collapse Same problem. And a second issue: my A696 freezes if I work with the BT module (handsfree, file transfer) Thanks for the ROM.
When I was making the rom, I was looking for a way to delete the MS Bluetooth stack to free up some space (which is perfectly fine). I'm not sure, but I think the problem could be caused by me deleting some dll file packages related to bluetooth that are shared between the MS Bluetooth stack and the stock Broadcom stack (which is better).
Finally got around to flashing the new ROM. It appears to be working fine. I mostly use the A626 as a music player so I've had no issues so far. There is one thing that I'm not sure if its just my A626 or if anybody else has the problem but when I plug in the external AC adapter it doesn't seem to recognize the external power source... it will charge the battery it doesn't use the screen brightness and timeout settings, it will stay using the settings as if it is running on battery. Anybody else notice this? ******* Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue. ******* I switched to a different mini usb charger and now it is recgonizing that the external power is hooked up... must have a weird usb charger. I've also gone back to using 6.5 1a to see if I have the same stand by/blank screen issues.
Bluetooth handsfree I found some registry entries in a french site, with these settings we can enable the bluetooth handsfree service. I attach this file, maybe Steven will integrate in the next ROM (this service can be disabled in the bluetooth settings like any other service if you don't use). The application (which is from asus \windows\bthandsfreedevice.exe) has a little bug: can't do the synchronization of the phonebook and calllog from the phone (I tried with nokia 6233). If anybody know about a newer version of bthandsfreedevice.exe or know another (better) bthandsfree application, maybe we can make a working handsfree device from A696. brgds, imre00
bmasephol said: Finally got around to flashing the new ROM. It appears to be working fine. I mostly use the A626 as a music player so I've had no issues so far. There is one thing that I'm not sure if its just my A626 or if anybody else has the problem but when I plug in the external AC adapter it doesn't seem to recognize the external power source... it will charge the battery it doesn't use the screen brightness and timeout settings, it will stay using the settings as if it is running on battery. Anybody else notice this? ******* Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue. ******* I switched to a different mini usb charger and now it is recgonizing that the external power is hooked up... must have a weird usb charger. I've also gone back to using 6.5 1a to see if I have the same stand by/blank screen issues. Click to expand... Click to collapse I noticed these today as well, and re-flashed but wasn't able to resolve the problem. Will continue testing the ROM.
While I don't need the Microsoft entries (since they pertain to the MS bluetooth stack), but I will definitely take a look at the widcomm entries. I won't be able to work on rom building until the weekend, but I will take some time to test it (to tell you all the truth, I didn't really test bluetooth as much as I should have with this release).
bmasephol said: ******* Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue. ******* Click to expand... Click to collapse It seems that the device can't wake up only when goes in standby after applying the screen lock. Without locking, it can be powered on with the power button.
Downgrading to rom version 1 Hi steven, After several times i tried to discover what's appear to make the battery totally empty (due the fact i couldn't start my 696 on every time i shut it down or just pushed shortly the "power on" button just to make it sleeping mode) i figured that something in the rom version 2 caused the problem. I alreasy noticed (my last reply) that even the battery still ok, during trying to make the 696 go to sleeping mode it's refuse after that to power on and forced me to make couple of resets (because even after some resets the 696 still stuck without any responding). Finally i downgraded the 696 to rom version 1.