Microsoft Portrait 3.1 released - General Topics

It was a half year ago (see review HERE) that Microsoft released the first beta of their VoIP / video phone / SIP program Microsoft Portrait. Microsoft has, in the meantime, released version 3.1.
I was very eager to check it out as 3.0 didn’t support front cameras on any Pocket PC’s, which would be essential for TCP/IP-based video phoning.
To make a long story short, unfortunately, the new version doesn’t support video phoning using front cameras either. It still only lists CAM1: (the rear camera) on all my Pocket PC models with two built-in cameras: the HTC Universal and the HTC Trinity (p3600). This is certainly bad news.
Furthermore, as far as the MS Smartphone compliance is concerned, it didn’t work on either the WM6 QVGA HTC Vox (s710) or the WM5 AKU3 HTC Oxygen (s310). On the former, it just displayed the “Initialize Portrait control failed” and, then, the “Get camera resolutions failed” info messages; on the latter, nothing has happened at all. Both phones are SIM / app unlocked and I’ve tried making Portrait work on them several times (yes, after resetting too).
All in all, it’s still useless for video phoning over traditional TCP/IP. Only get it if you only need it for voice / textual communication on Pocket PC's only (again, it seems it's completely incompatible with MS Smartphones, regardless what the product page states.)

I'm using WM6 on a wizard and am happy to report it did work for me. Pretty fantastic actually. True, the camera is on the back and it's upside down, but it's good enough. I can finally check "video chat from my PPC" off the list!

is it really chat when you can see the other person at the same time as they can see you ?
and is the grps of wizard fast enough to use it prob?

i have an HTC Touch Diamond. And tried this with my MSN. But my contact list was empty. and when i called myself from pc it gave error about my msn version.
With a wireless connection this software can be great. Also it did not use my 3G camera and when i checked in cameras section there is only one option named CAM1.
Anyone else tried?

Tried this on a HTC Titan (Sprint Mogul) and it does work for me either with the same results as the previous poster. Any one have this working anymore?

Related

What's so great about WM6?

Hi,
While I am waiting for my MDA Pro to arrive, I have been reading a lot in the Universal section (have a BA myself).
May I ask for some valid reasons why someone would want to use homebrewed WM6 releases instead of official/customized WM5?
I do understand the fun it is to try out new things, but is it really worth it? I did not find many posts that would clear this question.
Thanks,
vma
WM6.0...
The new look and a lot faster device...
Is there any feature that won't be available with WM6, that did work fine in WM5?
Thanks,
vma
Video call isn't working yet.
Rolud said:
The new look and a lot faster device...
Click to expand...
Click to collapse
The way I see it, WM6 may or may not work for you and may or may not do it for you. Try it. You can always go back to WM5. Most people don't.....
Well .... the simple answer is that I did a lot of searching and reading, and finally tried it out for myself.
I asked this very question a while ago right here:
http://forum.xda-developers.com/showpost.php?p=1130569&postcount=88
And came to the follwowing conclusion:
http://forum.xda-developers.com/showpost.php?p=1155497&postcount=89
In the conclusion, the thing about the Bluetooth Stack / Voice Command - it was actually Voice Command that was the problem and this issue was fixed in Jrwightmcps' 2.02.00 WWE http://forum.xda-developers.com/showthread.php?t=297256
Crossbow ONLY!
Tell you the truth... i see the new WM6 is better eye-catching GUI not to mention the enhancement in the functionality and other usability such as email related functions. I know that MS wont just upgrade for no obvious reason nor for desktop OS compatibility.
Yet i reckon i wont -never- go back to magento! Crossbow ONLY!
@nvatvani:
Indeed your posts where the only ones I read, that contained some usefull info about the subject.
No offense to all the other members of course!
I was simply wondering about what to do when my MDA Pro arrives: replace the German firmware with a WWE WM5 one or go straight ahead to WM6 without even looking at WM5.
Also, I had some problems with my Blue Angel, when I tried WM5 on it: it may have been a coincidence, but one day after the upgrade the screen went mad and totally messed up. Only 1 Hardreset in about 100 tries would bring it back to normal for some period of time and even reflashing it with WM5 or 2003SE would not make it work normal again. The screen would get messed up suddenly for no particular reason. At the end I had to send it in for repair, which was actually a good thing, as I complained about the loose stylo and bad working hardkeys, all within warranty. I got a new key-pcb, backside and they reflashed the device with 2003SE. I posted this issue in the BA forum, but got no usefull hint. This means I am a little scared of upgrading to unofficial releases.
Other than that, I have no problems with flashing, as I do that on my other hobby (satellite receivers) frequently, including JTAG-operations for repairing bricked devices. The same applies to games consoles. (Note: I do not sell or benefit commercially from that activity and my goal is not to get illegal software or TV - not that you guy's get the wrong idea about me).
Anyway, thanks for your replies!
Cheers,
vma
What Windows Mobile 5.0 AKU 2.0 has and Windows Mobile 6 (the cooked ones, having tried them all) doesn't have, according to my experiences:
1. Videocalling - at least not a proper one
2. Bluetooth Dial Up Networking (the DUN profile)
3. Wireless Modem (yet some WM6 ROM's have it, although without shortcut in the start menu)
4. Cyberon Voice Dial by default (some WM6 ROM's have it by default, others will need a 500kB CAB to activate it)
The reason why I went back to "good old" WM5 is mainly the reliability. Ok, the OS may be a bit slower here and there, but it has all the functionality (e.g. videocalls and Bluetooth DUN), and NEVER hangs. It just always works and that's what I desperately need right now.
---
The things Windows Mobile 6 has for me that 5.0 hasn't which I miss the most:
1. High resolution browsing in the normal Internet Explorer (I don't want to use alternatives)
2. HTML email support
3. The impressive speed of the OS
Applications like WM6's Windows Live and the superb Remote Desktop Client are also available for WM5, so I don't need to miss those, otherwise I sure would, and then I might have sticked with WM6.
The new sounds and GUI are great, but I don't really miss them, since that's not a true functional thing.
Having WM5 up and running again, without freezes and memory leaking and with full HTC Universal functionality, is enough for me to be happy with it and to stick with it. If there ever will be a ROM that actually ADDS Windows Mobile 6 on top of all of this (without a single registry tweak or CAB fix needed), then it's the time for me to upgrade again.
If such a ROM will ever see the daylight, since it won't be officially available for the Universal, I don't know. I think the HTC X7500 (Athena) will be there sooner (April 2007 over here), and that one will have a official WM6 upgrade for sure. That'll be my next one, so until then: WM5 for my Universal!
So far for my opinion.
why do I use WM6
vma said:
Hi,
While I am waiting for my MDA Pro to arrive, I have been reading a lot in the Universal section (have a BA myself).
May I ask for some valid reasons why someone would want to use homebrewed WM6 releases instead of official/customized WM5?
I do understand the fun it is to try out new things, but is it really worth it? I did not find many posts that would clear this question.
Thanks,
vma
Click to expand...
Click to collapse
To be honest, I used them all and later delteted them after 5 2 hours. They leak a lot, ram is at minimum and useless third party applications, and a lot fo thing sodn't really work or missing (I just want a vanill aone without 3rd party applications).
Except for one rom, Darkforce, it is fast and furious, and so far I have using it for two days; battery usage is good, and no leaks. However, no video calling, and no way to set com ports for bluetooth devices. any1 has this problem?
However, common to all ROMS, no video calling, old calculator, speed dial messed up (some work and some don't), wireless connection bubble missing (yes you can install a cab but I don't want to do that).
<Mind you, contrary to other reports, I never had any freezes with any rom.
The thing that attracts me is HTML in email, High resolution mode in explorer, better remote desktop connectivity.
So I thhink I am sticking with DarkForce ROM, so far so good.
Thx

Windows Mobile Device Center 6.1

Sadly this new version still screws up my favourites when it syncs and there is still no option to sync contact categories. A great feature that got removed in 3.8
I guess you mean active sync 3.8. And one wonders if anyone had actually taken the time to write to MS or start a petition? That was a good feature and it seems odd that after all this time it still hasnt been reinstated.
Then again, VGA devices have been around for years and were now only getting VGA resolution support in WM6 so.
Still biggest improvement with this update is for WM6 users and Vista users.
Yea, 3.8!
I've written to them a millions times.

Dial-up Networking Via Bluetooth Under WM5 AKU3 / WM6: WORKING at last!! A MUST!!!

Guys and gals, sorry for not re-editing the entire article so that I can incorporate the update into the main body of the article. Hope it’ll be still be understandable.
UPDATE (10/02/2007): there is an even better, easier-to-install and, what is more, even MS Smartphone (Windows Mobile Standard)-compatible hack. Just download the CAB file linked from THIS post (I’ve also mirrored it HERE, just to be on the safe side, should you not want to register at XDA-Dev to access the download), install it (by simply clicking it on your handheld), power down your device (if it’s a Pocket PC – in order to make sure the Registry changes are all flushed) and restart it.
This hack will add full BT DUN to both platforms. I’ve thoroughly tested it on both my WM6 HTC Universal (a Pocket PC) and WM6 HTC s710 / Vox (a Smartphone) and found it excellent. Note that the traditional, BT PAN-based Internet Sharing will still work alongside with the added BT DUN (tested on both devices).
Note that it has a minor annoyance. After you terminate the connection, you will still be unable to access the Net on the Pocket PC or Smartphone that you used as a modem (also see THIS and THIS for similar bug reports). The solution to this is pretty simple: instead of (lengthy and/or awkward) soft resetting your handheld, just make sure you tap either the data connection icon in Comm Manager (this seem to be sufficient with Smartphones) or, as with, it seems, with Pocket PC’s (like the Universal), just dis- and, then, re-enable the phone connection itself (or, alternatively, en-, and, then, re-disable Flight mode). This all makes this small bug easy to live with.
Finally, Smartphone users: remember NOT to long-press the Red dial button to lock your device – it’ll also terminate the call. Instead, use the standard lock menu accessible via the Power button.
There is also a tutorial on making USB connection work with Modem Link HERE, should it be messed up. Also, the entire thread might be worth giving a read, should you still have problems.
Thanks for FX Belloir for pointing out this hack!
(end of update, the now-outdated original article follows. This means you’ll want to prefer the new hack explained above, NOT the old one I still keep for historical purposes only. It's only the first sections, which explain what this is all about, are worth reading for casual users.)
Anyone having read my article New dial-up networking model of the WM5 AKU3 – a must if you use your WM phones as modems knows WM5 AKU3 (and, of course, WM6) has dramatically changed the way dial-up networking is handled – not necessarily in the good direction. (Please DO read the article if you don’t have a clue what I’m referring to and you have ever wanted to use your Windows Mobile handheld as a cellular modem!)
Microsoft, so far, haven’t really done anything to the problem, except for publishing an article (also discussed for example HERE). Therefore, hackers needed to concentrate their forces on solving the problem. After the first failed attempts (for example mine, as is explained in the first-linked article), at last, some excellent XDA-Developers folks have managed to enable this feature with a comparatively easy-to-do hack. I’ve developed the hack further, making it compatible with several handheld models and ROM versions (the previous version available at XDA-Developers doesn’t support the Universal, Wizard and, probably, several other models because it doesn’t do any forced Registry import – it might only be compatible with the P3600.)
The hack makes it possible to use most WM5 AKU3 / WM6 devices in the traditional (pre-WM5 AKU3) DUN dial-up method, in addition to the new, in WM5 AKU3 introduced Internet Sharing.
This means you can use BOTH technologies and can have the advantages of BOTH approaches. With the “traditional” DUN dial-up, you still have the freedom of NOT having to manually start / reconnect Internet Sharing AND the ability to use clients not supporting the BT Personal Area Network (PAN) profile required by the new Internet Sharing. And, as Internet Sharing is still supported, you can still have a real internet sharing approach, making it possible to use the Internet on both the Windows Mobile device acting as a modem and the client that connects to it (and can still have the other goodies Internet Sharing also offers: for example, the accessibility of the phone even with an ongoing Internet session.)
Again, it’s almost impossible to emphasize how important, how revolutional this hack is! If you’ve EVER tried to use your WM5 AKU3 / WM6 Windows Mobile phone as a modem you know Internet Sharing can be a REAL pain in the back, particularly if the client you’d like to use it from doesn’t support BT PAN.
Installation
Import THIS registry import file (via, say, the brand new, EXCELLENT desktop-side Registry editor of SOTI’s Pocket Controller 6) and copy the contents of THIS file to the \Windows directory of your Windows Mobile device. Soft reset your device and voliá: after this, clients discovering the Bluetooth services your device provides will also see it offering the DUN service (in addition to the PAN one) as can also be seen in HERE.
After this, everything will work just great – as in the pre-AKU3 days. Follow for example THIS tutorial on using DUN modems if you don’t know how it’s done.
Problems
It’s incompatible with some HTC Wizard ROM versions, namely, the official AKU 3.3 T-Mobile ROM – see THIS. It, however, has no problems with mfrazzz's XDA Mobile 6 Release 2a Full at all.
It seems it’s incompatible with WM6 MS Smartphones (Windows Mobile Standard). I’ve tested this on my HTC Vox (S710).
Compatibility
In my tests, it worked just great on my HTC Universal and HTC Wizard. A lot of people have reported other success stories; for example, with the AKU3 HTC Trinity (P3600).
Verdict
Again and again: if you EVER plan to use your handheld as a modem, this hack is a MUST!
UPDATE (11/02/2007): There's a version specifically meant for the T-Mo Dash is at http://forum.xda-developers.com/showthread.php?t=340762 .
Note that if you have a MS Smartphone (as opposed to a Pocket PC), it MUST be application unlocked for the hack to work. See for example See for example http://www.pocketpcmag.com/blogs/index.php?blog=3&p=2004&more=1&c=1&tb=1&pb=1 for more links on application unlocking. Note that app unlocking is absolutely legal.
Error on a StarTrek
Hey all,
I get the following error after installing:
"Alert
Can't find 'ATCIUI' (or one of its components). Make sure the path and filename are correct and that all the required libraries are available."
Any ideas? All the components are there...
qnonsense said:
Hey all,
I get the following error after installing:
"Alert
Can't find 'ATCIUI' (or one of its components). Make sure the path and filename are correct and that all the required libraries are available."
Any ideas? All the components are there...
Click to expand...
Click to collapse
Which one did you try? "Technology"'s CAB? Mine?
Menneisyys said:
Which one did you try? "Technology"'s CAB? Mine?
Click to expand...
Click to collapse
I tried both CABs, as well as simply copying the files into the Windows directory, all to no avail. My phone is application unlocked and I've verified that the registry entries are all in place... Very confusing.
Motorola Q9c
I couldn't get it to work on the Motorola Q9c either. Any chance there is a way to get it to work with this device?
What Are You Trying To Do
mabmarc1 said:
I couldn't get it to work on the Motorola Q9c either. Any chance there is a way to get it to work with this device?
Click to expand...
Click to collapse
If you have bluetooth on your device, then I believe it will work on your device! If you are trying to configure the bluetooth {"DUN"} dial-up configuration setup on your Motorola Q9c, then it will never work. Just install the bluetooth Dun.cab on your Motorola Q9c to the MAIN MEMORY! (NOT IN THE WINDOWS FOLDER)! Soft reset your device. Next turn the bluetooth on, pair the two devices, now the Motorola Q9c is ready to be use as a "modem" for bluetooth {"DUN"} dial-up. Nothing else is to be done to the Motorola Q9c. The bluetooth {"DUN"} dial-up configuration setup should already be on the other device (PDA, Laptop, ect...) that you paired with the Motorola Q9c............! The directions that I'm giving you are for the bluetooth Dun.cab in my thread only............!
VZW Moto Q not working
Okay so I tried the .cab file and stupid me forgot to back up my device before hand. Yeah now I don't have any working Bluetooth.
2 questions.
1) Could someone please provide me with the files from a WM5 AKU3 phone?
ATCIUI.exe
ATCIUI.lnk
atcmdint.dll
bthatci.dll
2) If I can't get these files from someone will a Master Reset get my device back to normal or will it leave the broken files still in place.
This worked great on my Treo 750 w/ATT used it on my TomTom 920. THanks!
Anyone got luck using this on a HTC S730?
I'm trying to access the internet from my QTek 9000 (HTC Universal) through my HTC S730 phone. No luck.
On QTek 9000 (with crossbow's WM6) no clientside PAN is supported and on HTC S730 I cannot get DUN working...
Yes bmorg, master reset will revive your device
user 888
user888
matey did you make any progress with your query?
user888 said:
Anyone got luck using this on a HTC S730?
I'm trying to access the internet from my QTek 9000 (HTC Universal) through my HTC S730 phone. No luck.
On QTek 9000 (with crossbow's WM6) no clientside PAN is supported and on HTC S730 I cannot get DUN working...
Click to expand...
Click to collapse
Your quest is similar to one I have. I have a T-Mobile Dash with HTC-S620 WM6.1 Smartphone ROM and EDGE data that I want to access the internet from a SE TM506 with HSDPA 3G data. There is no clientside BT PAN on the S620 and no way to BT DUN to the TM506. I have clientside serial port on the S620 to the TM506 but no app to take advantage.
So far quest was futile.
http://forum.xda-developers.com/showthread.php?t=433074
Help for WM6 GSM dial-up internet connection
Hello,
can anyone help me?.
I would access internet with my cell phone (Samsung SGH i780 os WM6) without having any kind of fast data connections with my provider, like gprs edge or hsdpa.
In other word I would connect to the service with a dial-up gsm connection at 9600bps, but WM6 seems to haven't capability to connect to internet this way.
I found here: http://www.modaco.com/content/smartp.../#entry1048254 some related like informations, think to understand that this post tells about to connect a BT device like gps, trough BT connection of a WM6 cell phone, via DUN to internet; someone think this could also be useful for me? If so how?
Please forgive me my english I hope it could have be understandable.
Tankyou.
Roberto Ruvinetti
Edit/Delete Message

Call recording supported on some new HTC handsets (e.g., the Touch HD)?!

Up until now, very few Windows Mobile handsets have supported call recording, which has also resulted in, after giving my call recording-capable HTC s310 to my wife, my sticking to a Symbian S60 phone (the Nokia N95) for plain phoning purposes.
Fortunately, some XDA-Developers forum members discovered the HTC Touch HD running Asian ROM’s do have built-in support for flawless (read: no need to rely on “sound bleeding” from the speaker to the mike to record the other party) call recording, while non-Asian ROM’s didn’t have this feature. They have quickly ripped the app so that others can also install it.
Currently, only few WinMo models and ROM versions do support call recording; for example, the
Touch HD, the Kaiser and the Raphael (CDMA-specific thread HERE; reported success with for example the new 5.05 leaked WWE ROM). (Click the links for additional info.)
Note that I’ve started and will (try to) maintain a list of the supported models and ROM versions. It’s available HERE.
On my HTC Universal running Tomal 8.5 WM 6.1 (tested with the plain registry import, the original CAB file linked to in the first post of the Kaiser thread and Monx’s repack – it’s the latter two that you should try first after reading thru at least the Touch HD thread – yes, I know it’s long and quite hard to read, but it still has a lot of nice info), it doesn’t work. The second did show up the “Record conversation” menu item while talking; the third didn’t at all. Nevertheless, nothing resulted in recording the other party, other than the sound bleeding from the speaker.
Wow! This is good news! Anything that I could use on X1 to do the same thing? I've been looking far and hard and unable to find anything in the market for this ability on WinMo 6.1 phones. The rest of the recording utilities have to rely on loudspeaker mode and once you are on hands-free, it does not work at all.

Windows Mobile Revolution: call recording supported on almost all handsets!

Up until now, very few smartphone platforms allowed for recording calls: most notably, Symbian S60 (but not UIQ). Windows Mobile (WinMo), apart from some models (HTC s310 / Oxygen, x7500 / Athena etc.) didn’t allow this. The BlackBerry platform and the iPhone don’t allow this either. (Albeit, with the release of iPhone OS 3.0 and the voice recorder coming with it, it’s not guaranteed the situation will remain the same.)
Note that the reason WinMo can’t record calls has always been different from BlackBerry and the (2.x OS-based) iPhone. The latter two in no way allow for running any voice recorder apps while a call is taking place (I’ve VERY thoroughly tested this on both platforms and, on the iPhone, with several third-party voice recorder apps); WinMo has always done so – it did allow for running a sound recorder app while, at the same time, the same handset was taking place in a conversation. It’s just that not at an acceptable quality – so far, you had to rely on the sound bleed from the speaker to the microphone to record the other party. Recording your voice, of course, has always worked (with the exception of some very rare models like the O2 Flame, where the situation was the opposite: the other party’s voice was recorded, but not yours) as the mike easily picked up your voice – after all, it’s way more loud than the other party’s thin voice bleeding from the speaker of the phone. Sure, enabling speakerphone helped the situation (more advanced call recorder apps like Resco and VITO AudioNotes automatically do this if you instruct them to do so) to some degree, but the resulting quality was still a long cry away from that of, say, recorded calls on the Symbian S60 (mostly, Nokia) platform. And, of course, you can’t use speakerphone all the time; for example, if you don’t want the people around you know what you’re being told – or don’t want to disturb them with a loud phone.
It can’t much enough be stressed the importance of this hack. With call recording enabled on most handsets, the usability of the platform as a “plain” phone has greatly been increased. This is also bad news for the BlackBerry and iPhone folks – Windows Mobile has turned out to be better in this respect (too) ;-)
Previous hacks
It was just a few days ago that I’ve explained the (then, current) hacks that might work on some handsets to enable call recording. In the meantime, a new, much easier (Registry-only) hack has become available, with which you can really easily, without having to waste hours on reading through some ICR-dedicated threads. That is, you don't need to give a try to the methods outlined in my previous article; you don't need to read the linked (e.g., Touch HD) threads either to learn how to set up the previous hacks, what they do, what their restrictions are etc.
Installation
You only have to download and execute the CAB file linked from the first post of THIS thread (I've also mirrored it – just click the link, save the CAB file and execute it on your handset). Note that it’s both compatible with the touchscreen-enabled Windows Mobile Professional (aka Pocket PC) and the touchscreen-less Windows Mobile Standard (aka MS Smartphone) platforms.
Compatibility
This application (more specifically, a registry hack) seems to be compatible with a lot of phone models and a lot of (both factory and “cooked”) firmware versions; for example, the HTC Kaiser with a lot of different ROM’s, the HTC Wizard also with tons of ROM’s (I’ve tested it with character’s AMP), the HTC Vox (s710) WM Standard smartphone running the official, non-cooked ROM etc. (This also means it's compatible with both WM Standard and WM Professional.)
There, however, are phone models? phone models running a specific firmware version? that don’t seem to work with the hack (read: they don’t allow for recording the other party at a tolerable volume); for example, the HTC Universal running Tomal’s 8.5 cooked WM 6.1 ROM. This, however, doesn’t necessarily mean the Universal won’t be able to record calls with any else ROM.
Make sure you check out THIS thread (and, most importantly, the compatibility list in the first post) for more info on which models are surely supported. Also, please post (let us know about) your experiences in the thread (no private messages / mails to me!) or here.
What apps can you record calls with?
After this, you can test / start recording calls easily with, for example, the built-in Notes application (don’t forget you need to explicitly enable the Recording Toolbar in it!) or, on the WM Standard platform, Voice Notes. Note that this application (as with HTC’s ICR) can only start recording manually; there aren’t automatic call recording capabilities.
Should you want something better (that is, apps with automatic call recording, storing the caller/called name/phone number and the date), get one of the following apps (note that there are quite a few other, [automatic] call recording-capable titles; nevertheless, these are the ones I recommend the most):
* PMRecorder by Motoblast. Note that it also has an online tutorial HERE. This app is free, unless you want to use its online upload and accessibility capabilities. (To get rid of the latter, just untick the two checkboxes under “1800message.com” in Options.) Unfortunately, this also means you can’t record high-quality, but compressed recordings with PMRecorder: only AMR (which has very bad sound quality) is supported. (Sure, you can use uncompressed WAV files instead, but they do take a lot of storage.)
Note that, as has also been explained in my previous, pretty big article on the app,
1. if you want to listen to your recordings on any other (for example, desktop / notebook) computer or simply outside PMRecorder you’ll want to download PMRBackup.zip (I’ve also mirrored it HERE). Unzip it, start the EXE and select “Select file(s)” if you’ve already transferred the .rcwv files from your handset; otherwise, press the “Get from device” button. After conversion, the original recordings will be saved as standards-compliant ones and will be named after the other party's name / number and the timestamp of the conversation.
2. create a link file to \Program Files\PMRecorder\PMRecorder.exe from \Windows\Startup so that it is always auto-loaded at boot time (this works on both platforms too). Otherwise, it won’t – unlike the commercial alternatives below.
* Resco Audio Recorder (WM Standard version HERE). It’s much more expensive than VITO’s app (the third recommended title) but it may also turn out to be better, particularly if you want to minimize storage usage (and, therefore, stick to some, compared to MP3, highly advanced speech coding format – in this case, Speex). For example, on my HTC s710 WM Standard phone, VITO’s Audio Notes is always maximized at startup (assuming you’ve enabled it to automatically record calls – this must be made by hand!), making it necessary to manually minimize it.
Note that if you want to stick to MP3 (or AAC), you will want to purchase the Resco Codec Pack too - the built-in MP3 encoder in Resco Audio Recorder is really-really bad. This, however, won’t be an issue if you, as recommended, use Speex instead.
* VITO AudioNotes (the linked version supports both WM Professional and Standard). A very cheap, but still capable app. If you want to record into MP3 and don’t want to pay some $35 for the Resco Audio Recorder + Resco Codec Pack combo, this app should be the first you check out. Note that it has a slightly more advanced (and considerably more expensive) version, Audio Notes Touch. If you love finger scrolling, this should be the one you check out, not the stylus-only “basic” AudioNotes. Otherwise, for plain phone call recordings, AudioNotes works pretty great. Also note that, as has already been mentioned, you’ll need to explicitly enable it to record calls (Menu / Record / Calls autorecord)
Please also see my dedicated articles for more info on all these apps. In addition to my PMRecorder article, you might want to read my article on VITO’s AudioNotes (note that the chart in the article isn’t correctly rendered; see THIS for the image representation), my remarks on the 4.x series of Resco’s app HERE and, last but not least, the Windows Mobile Audio Recording Bible. Note that the latter isn’t specifically call recording-specific. It, however, explains a lot of things you may find useful, particularly if you plan to use manual recording only. Then, you’ll certainly welcome for example the one-button recording remarks (see the “Buttons: One-button recording? Does it need to show the app window?” row in the chart). No need to manually invoke other apps and search in menus if you want to start recording – just press a pre-assigned button and you’re set.
Legal notes
Please consult THIS for more info on which American states allow for call recording without the other part’s knowing of this.
Addendum (for hackers only!)
I’ve tested whether the HTC Oxygen (s310), one of the very few WinMo phones to support call recording, has the same registry values as the three entries in the hack. Interestingly, it doesn’t (below is the s310 registry dump of the related registry keys; hope it helps hackers to find out why the s310 is able to record calls and, in the Registry, what makes this possible).
1. "HKLM\Software\HTC\AUDIOGAIN\AUDIO_DEBUG_FLAG = 0 (and not 64)
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AUDIOGAIN]
"DeviceID"="Generic_Oxygen_1.9"
"AUDIO_DEBUG_FLAG"=dword:00000000
"ENABLE_AUGA_CARKIT"=hex:00
"ENABLE_AUGA_HEADSET"=hex:00
"ENABLE_AUGA_EMBEDDED"=hex:01
"EXTERNAL_RECORDING_GAIN"=hex:06
"INTERNAL_RECORDING_GAIN"=hex:17
"CODEC_GAIN_CARKIT"=hex:00
"CODEC_GAIN_HEADSET"=hex:03
"CODEC_GAIN_EMBEDDED"=hex:00
"EAC_GAIN_CARKIT"=hex:67
"EAC_GAIN_HEADSET"=hex:67
"EAC_GAIN_EMBEDDED"=hex:70
"TTY_UPLINK_VOLUME"=hex:09
"EARPHONE_UPLINK_VOLUME"=hex:19
"HEADSET_UPLINK_VOLUME"=hex:12
"SPEAKER_UPLINK_VOLUME"=hex:10
"RECEIVE_UPLINK_VOLUME"=hex:1A
"CARGTTYSIDETONEVOLUME"=hex:08,08,08,08,08,08
"CARGEARPHONESIDETONEVOLUME"=hex:08,08,08,08,08,08
"CARGHANDFREESIDETONEVOLUME"=hex:08,08,08,08,08,08
"CARGHEADSETSIDETONEVOLUME"=hex:08,08,08,08,08,08
"CARGCARKITSIDETONEVOLUME"=hex:08,08,08,08,08,08
"CARGRECEIVESIDETONEVOLUME"=hex:02,06,0C,0C,0D,0D
"CARGTTYVOLUME"=hex:06,06,06,06,06,06
"CARGHANDFREEVOLUME"=hex:63,20,23,26,29,2C
"CARGHEADSETVOLUME"=hex:63,20,23,26,29,2C
"CARGCARKITVOLUME"=hex:61,64,21,24,27,2A
"CARGRECEIVEVOLUME"=hex:60,63,20,23,26,29
2. HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL\ RingingAddressId doesn’t exist:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Radio Version"="4.1.13.20_02.41.90"
"LASTUSEDICCID"="986302004041001548F5"
"RESETINFO1"=hex:1D,C2,3C,9A,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00
"RESETINFO2"=dword:00000004
"OperatorEccList"=hex(7):31,00,31,00,32,00,00,00,39,00,31,00,31,00,00,00,00,00
"GPRSAutoAttach"=dword:00000000
"IMEI"="notyourbusiness"
"ResetWhenRadioOffTimeout"=dword:00000001
"AutoNetSelAfterReboot"=dword:00000000
"EnableRIL86Rollback"=dword:00000001
"EnableSmspFromSim"=dword:00000001
"SIMPollingTimerForRemoveDetection"=dword:000000B4
"CwsAtntTreatSpecialPatternAsDial"=dword:00000000
"DelayKeyEventTimeout"=dword:000007D0
"GsmVersion4131xx"=dword:00000001
"MOAbortGPRSSleepCount"=dword:00002000
"HTCGPRSBlockMOWorkaround"=dword:00000001
"EnableWorkaroundForFTA"=dword:00000000
"EnableSStoATD"=dword:00000001
"EnableEcc"=dword:00000001
"DumpGsmThreadLogPeriod"=dword:00003600
"EnableNdisMpdpDebugLog"=dword:00000000
"ImmediateCBMSupport"=dword:00000001
"EnableATAbortSTKCall"=dword:00000001
"EnableDifferGprsEdgeIcon"=dword:00000001
"CsqResendTimeout"=dword:00003A98
"EnableEngineerModeQueryAMR"=dword:00000001
"EnableOverrideVmailAlphaIdFromSIM"=dword:00000000
"BarringIncomingCallStatus"=dword:00000000
"EnableCallBarringPatch"=dword:00000001
"EnableDTMFSupport"=dword:00000001
"DisableRoamingIndicator"=dword:00000000
"GPRSAutoDetach"=dword:00000000
"FDNPINEnable"=dword:00000000
"NIEnable"=dword:00000000
"CPIEnable"=dword:00000001
"CREGLocationUpdate"=dword:00000001
"NITZEnable"=dword:00000000
"Index"=dword:00000001
"Order"=dword:00000004
"Prefix"="RIL"
"Dll"="rilgsm.dll"
3. HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev\ VocRecPath doesn’t exist:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
"Order"=dword:00000002
"Index"=dword:00000001
"Dll"="wavedev.dll"
"Prefix"="WAV"
Now if we can only find a registry hack to fix the crappy camera HTC likes to put in their phones lol. HTC TouchPro 2 with a 3.2MP Camera and no flash?? CRAZYY!!
Im glad we finally fixed the 2 way recording problem that has ALWAYS been blamed on hardware limitations and claimed that this would never be possible. All it took was 3 little registry entrys haha!!
Good job with the write up
mskip said:
Now if we can only find a registry hack to fix the crappy camera HTC likes to put in their phones lol. HTC TouchPro 2 with a 3.2MP Camera and no flash?? CRAZYY!!
Im glad we finally fixed the 2 way recording problem that has ALWAYS been blamed on hardware limitations and claimed that this would never be possible. All it took was 3 little registry entrys haha!!
Good job with the write up
Click to expand...
Click to collapse
Cool! BTW, to fix the incompatbility issues with some models, can anyone look into the s310 registry export and file system? (Why it's capable of recording while it certainly doesn't have the registry edntries.) As I also have an s310, I can give you help in this.
Menneisyys regarding your first post here you said Universals on Tomal's WM6.1 dont record 2 way.
I'm using Universal, Tomal's 6.1, v8.7 with Radio 1.17 and using Vito Audio Notes, my 2 way recording is perfect.
PMrecorder is just very soft recording the opposite side on my HTC P3600 with WM6, (Trinity) hard to hear when I play the recording back I can hear myself very clearly. But I am more interested in what the other has to say to record.On the P3600 I am using the "ADW version 1.1 NLD and WWE (OS 5.2.1908 Build 18508.0.7.0) ROM-date: 06 Oct 2007", dutch
hendrixus said:
PMrecorder is just very soft recording the opposite side on my HTC P3600 with WM6, (Trinity) hard to hear when I play the recording back I can hear myself very clearly. But I am more interested in what the other has to say to record.On the P3600 I am using the "ADW version 1.1 NLD and WWE (OS 5.2.1908 Build 18508.0.7.0) ROM-date: 06 Oct 2007", dutch
Click to expand...
Click to collapse
Which cab did you use to try to get the 2-way recording to work?
mskip said:
Which cab did you use to try to get the 2-way recording to work?
Click to expand...
Click to collapse
Good question. Lemme get my device, moment........................."mskip 2way recording", Two way or 2-way plus?
hendrixus said:
Good question. Lemme get my device, moment........................."mskip 2way recording", Two way or 2-way plus?
Click to expand...
Click to collapse
If the incoming voice is very very faint then its probably just picking up the incoming voice that your mic is picking up and recording that. If the registry edit works then you would at least be able to hear the incoming voice clearly which I can only assume means its not working for you. Try upgrading to a custom WM6.1 Rom if you can as the stock roms dont seem to work at all.
mskip said:
If the incoming voice is very very faint then its probably just picking up the incoming voice that your mic is picking up and recording that. If the registry edit works then you would at least be able to hear the incoming voice clearly which I can only assume means its not working for you. Try upgrading to a custom WM6.1 Rom if you can as the stock roms dont seem to work at all.
Click to expand...
Click to collapse
OK, i'll try the registertrick first. The ROM ia'm using is a custom rom. But WM6
it didn'et work on y xperia.
please let's know if any one could make it work on Xperia?
The registry fix does not seem to work on the LG Incite. Too bad, I was hoping it would. Thanks for all the effort though.
Stock Samsung Jack with the security removed and 2 way call CAB installed. Still getting no calls recorded with Vito AudioNotes 1.37.
Anything else I can try?
I seem to be limited to about 45 seconds of recording. Is there a way around this? I changed the "save to" destination to my 8 gig storage card, so memory isn't the issue.
Thanks!
TG01 2 way call rec without speakerphone
Any solution for 2 way call recording on TG01 without the speakerphone on?
Cristian
crissstian said:
Any solution for 2 way call recording on TG01 without the speakerphone on?
Cristian
Click to expand...
Click to collapse
what rom are you running?
TG01 2 way call rec without speakerphone ??
I'm not sure, the original Orange ROM, I suppose.
I don't know how to access ROM.
WM6.1
This "Revolution" doesn't work on HTC HD2 (Leo).
SpiritRC said:
This "Revolution" doesn't work on HTC HD2 (Leo).
Click to expand...
Click to collapse
Pretty much everyone knows that by now
Mark.
I have toshiba g810 and 2way ....cab not work. I have a windows mobile profesional 6.1. What can I do??Please help

Categories

Resources