Saridnours’ AKU 3.5+ Rom. Current 3/19 v3.5pr5 w/SP1

[saridnour]

bacspasm: Think of the rom as what it is, a read only mass of a set size (all roms take the same pre-defined amount of space). This read only mass has all the vc files except the exe. So when you re-install, you are installing the same files again but these will take up storage space and mask or "pretend" to be in the same directory as the originals (or at least some are copied to the virtual windows dir) so technicaly they are both there, although you only see the ones copied in. It's not that big of deal, but vc does take up some storage space. Since the files are initaly all in the rom (not taking storage space) all you really need is the exe. On a fresh rom install, if one was to copy the voicecommand.exe to the windows dir it would only use up as much storage space equal to the size of the exe and not the lump sum of all of the installed bits (couple meg if I recall). One would then just need to run the exe and it should be good to go (may need to place a link to the exe in the windows\startup folder if running the exe does not do it for you, can't recall right off).

Also just adding the vc's exe will not casue the button 5 issue as it's not being installed, it's already in place correctly (the installer breaks it).

-saridnour

[eman]

Originally Posted by rlith

Sarisnour,

I've removed the registry keys, and the startup link this morn, and it was still loading. I did a fresh flash tonight as a test. Installed Wisbar lite then ran the uninstall and cleared any registry entries. Then installed WA2. WA2 now loads, but because of the presense (sic) of the wisbar lite files, WA2 doesn't load the theme I've picked at start. I now have to exit WA2 and restart it to get the theme to load. After testing this I did another fresh flash. Disabled the startup and registry keys for Wisbar Lite and did a hard reset, then loaded WA2... Same thing. Due to the presence of WBlite files, the initial startup of WA2 won't load the picked theme. You have to exit then restart wa2 to get the theme going...

Set your delay times in settings for 10 seconds.....That workd for me, I was going through the same problem....Also I disabled wisbar lite by setting it to not load after a soft reset.

[vtigre]

Hola friends. Im sorta new, just been reading and reading and having no life, addicted to the possibliities.

I just have a few questions, comments, that i want to ask to make sure im getting the right idea.

Things in this rom cannot be removed, but i can stop them from loading everytime i soft reset or turn off/on the unit by taking out the shortcut from the startup folder? I ask because i have purchased the licenses to all the trials in this rom and i would def not want to use the trial versions.

Do i have to uninstall or get rid of the trial versions? Is it ok to leave them there since the rom installed them? Just install the official versions on top of those trial versions?

My biggest concern is those trials.

I'm not quite sure on the whole voice command and the button 5 thing that everyone is talking about, i am just about to get the full version and use it as it seems very useful to me but if someone could elaborate what the deal is with this button 5 thing i would be very thankful.

Oh yea, when people say put this or that into the windows directory, do they mean the windows directory on the phone? so everything that goes on is on the phone right? i mean, this seems obvious, but im just covering ground.

I know , I just newbed myself very bad with this post, but yea, but that just means im on my way to coming back and helping others.

TIA.

[Ken B]

Hi Saridnour or anyone else,

I have applied the registry setting:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAGExtModule"="\\windows\\vcbthag.dll"

And I still do not have VC activating when I push the bluetooth button on my headset. The audio gateway opens (I can hear a littlle fuzzy noise, but no VC icon on the top line of the PPC). I can press the "notes" button and the VC icon will appear and can voice call thru the phone but not the BT headset. Any other registry settings that I need to do?

Thanks, Ken B

[saridnour]

Ken B: Did you soft reset after appling the new reg key? Did you verify that the key stuck after reset? It is verified working for me at least and should be back to what others saw in my earlier rom.

vtigre: If you pirchased the apps, the you should just be able to enter the reg code for the ones that allow this (wisebar for example). This will up the trial to full. The others you may just need to copy the exe to the devices \windows directory and have it mask (look to have overwritten) the origianl trial app. To get the full programs exe you can use a cab extractor (read on here about cecabmanager) or install the app(s), copy the main aplliction exe's and save them all to the storage card or pc. Then hard reset (loosing all data) then re-sync and copy your saved exe's back to the devices windows dir. This should give you the full apps. Method two takes more time, but may be easier unless you understand cabs and the tools.
The button 5 issue is a problem that the vc instller casues by erasing a registry key that button five needs to have for both the "press" and "press and hold" fetures to map to another application. By just copying the Voicecommand.exe as described above, you will not have the issue. If you install vc the installer will casue the issue (a hard reset will clear the problem and set it working so copying the exe back at that point will not casue any problems).

-saridnour

[pumpedpittbull]

Saridnour great work very impressive. (using rom 3.5 version 4) The question i have is with the MENU under programs.... they dont show up in a full window with large icons. Is there a way to see them like the real windows mobile 6 pro shows it?

[fesstech]

My contacts are now flickering/disappearing as well. Everything was fine for 2 days. I previously synced up and everything used to work great.

The only thing I just did was pull the battery out to change it. When the phone came back on, the contacts would not work. Also when ppl call, the numbers do not have names attached. Now when i try to usb sync up, I get the "there is not enough memory on your device to synchronize." I notice this same issue with 3.5pr1 and 3.5pr4

(i did not do any type of restore at anytime)


I also notice with 3.5pr4 and previous versions, the "Note" button does not work while in a phone call.

[jendand]

Originally Posted by fesstech

My contacts are now flickering/disappearing as well. Everything was fine for 2 days. I previously synced up and everything used to work great.

The only thing I just did was pull the battery out to change it. When the phone came back on, the contacts would not work. Also when ppl call, the numbers do not have names attached. Now when i try to usb sync up, I get the "there is not enough memory on your device to synchronize." I notice this same issue with 3.5pr1 and 3.5pr4

(i did not do any type of restore at anytime)


I also notice with 3.5pr4 and previous versions, the "Note" button does not work while in a phone call.

Originally Posted by saridnour

jendand: I think I see your problem. DO NOT USE the images information to hard reset, it is wrong! To hard reset press both soft buttons (on the face of the unit by the 4-way) at the same time and hit the reset button. It should prompt you with a Yes No to clear message.


-saridnour

Did you notice saridnour's reply to me. (above) Hard resetting correctly got rid of my flickering contacts.

[fesstech]

I was just able to pull my contacts back up.

The process i did, whether or not it actually worked:

1. plugged my phone into usb activesync
2. clear temp, All
3. soft reset from clear temp

now the Contacts show up and do not flicker, and activesync works again.

odd!

(this post was just an fyi for troubleshooting purposes, thanks for all your work Saridnour)

[fesstech]

I just confirmed that pulling the battery out while the phone is on and no usb connection, then replacing the battery and booting back up causes the Contacts to flicker.

My aforementioned process, again corrected the Contact flicker without a hard reset.