I've been playing with different ROMs now for the past couple of weeks, and am very impressed - they all seem far less prone to the lock-ups I experienced with my OEM WM2003.
But I can't get NotifyLink (used by my company to push emails) to work with *any* of the pre-made ROMs I've been using. I've not been able to complete the registration process - although I'm told that my authentication string has been accepted, I never successfully receive the "registration messages" that are then sent. These are needed to create an account on my PDA, without which I'm unable to proceed. [I've always wondered what form these registration messages are - when received on a WM2003 device the icon is similar, but clearly distinct from the standard SMS icon]. The application seems to die after approx. 10 seconds, with no error message, and certainly no indication of the expected messages being received.
I have a working GPRS connection - I can load pages using Mobile IE.
I'm hoping that someone may be able to help, although I've not seen much mention of NotifyLink in these forums! I don't want to have to go back to Wm2003 ;-(
Further information - I originally got error messages from the application on attempting to find calls from Microsoft.WindowsMobile.Status. I found a ZIP containing this DLL within another thread - having dumped these DLLs in the same application as the executable, these errors disappeared. I also have found that the application and the MS SQL database have to be installed on the Device rather than on RAMdisk. I'd investigate this more should I be able to get a working system.
Many thanks for *any* help!
Resolved by move to WM6
matkinson said:
But I can't get NotifyLink (used by my company to push emails) to work with *any* of the pre-made ROMs I've been using. I've not been able to complete the registration process - although I'm told that my authentication string has been accepted, I never successfully receive the "registration messages" that are then sent.
Click to expand...
Click to collapse
Just in case anyone ever suffers the same fate...
Never did get this fixed with any WM2005 ROM, but I don't suffer this problem with helmi_c's Tofclock dedicated WM6 ROM. I don't claim to understand why - one notable difference is that the .Net CF calls were resolved, so I didn't have to supply the DLLs.
All now working well, if I could stop my battery losing 60% over night!
Related
Morning all... I've been researching an issue I'm having with activesyncing my 8125 through bluetooth, since my latest upgrade to the SUPER cooked wm6 v4! Before the upgrade, while using v3, I had no issues connecting via bluetooth, now the device will not allow me to create an incoming port, only outgoing, and activesync is not in the bluetooth services list on the device. Also if I attempt to pair the devices by initiating it from the PC instead of the PDA, it errors out saying that the connection was denied. It has worked in the past, and my Dell Axim x30H synched with no problems. I even deleted the partnership with the Axim and recreated it, and again it synched with no problems.
It seams that the entire problem is stemming from the pda not giving me the option to create an incoming port, and of course it will not sync through an outgoing port. I have verified the com ports, deleted the partnerships multiple times and recreated, and gone through the registry to try and find anything there that I can tweak to be able to obtain the ability to create an incoming port.
I've searched the forums and have found multiple people with the same issue, across multiple roms, and basically no response for how to obtain the ability to create the incoming ports. That part kinda gets skimmed over. What I'm seeing is either you have the ability or you don't.
Anyone ran across this and found a work around? Or have ideas that I can try next?
I would Flash back to the T-Mobile wm 5 rom and see if it works with that rom. Just my 2 cents worth.
Hi to everyone,
probably this has already been investigated and/or solved (or not), I don't know, but I was not able to find anything related and I believe it is quite strange...
I was used (using WM6.0) to search contacts using keywords being present in the record in the following way:
- Open contact application (the application opens with the first line ready for input);
- place some text in the first line, such as "Richard"
- being presented from the application a list with ONLY contacts containing the word "Richard", either in the name, company name, address, notes, etc.
Well, I find this being impossible with my brand new VODAFONE TOUCH PRO (Raphael) I recently got:
- I open contact application (nothing strange till here...)
- I type just one letter (i.e. "R")
- the PDA immediately switches to PHONE MODE, placing a call to my first contact (I think so, havent been able to double check yet) whose name starts with "R" letter...
- I obviously have to immediately abort as I don't want to place an unwanted call...
This way the only chance I have to search my contacts is to PARSE them by hand, but having more than 2000 it's a really waste of time, beside the fact I can select the first letter the name starts with (and so no chances to find the keyword appearing in other fields...).
Is anyone else reporting the same problems ???
Is there some kind of setup setting I'm forgetting of ???
Really considering not to trash my BB...
Ciao
I wonder myself being the only one reporting such a problem and/or not being receiving any answer...
So I try raising my message up to your attention...
I've got the same problem. Its actually a little weirder than you wrote. Most letters work fine.
Pressing 'r', however, automatically dials whatever name you are on. Pressing 'w' inserts 'w*', which breaks the search (you can delete the * and then continue).
There may be other letter problems too. This is on a Sprint Touch Pro.
Anyone else?
BTW, the hard keyboard works fine.
I wonder if this problem exists also in other applications such as SMS??
i sometimes face a problem while writting an SMS, i press a character but suddenly i find the dialer activated...!!!
does this has anything to do with special characters?
"R" and "W*" on Sprint Touch Pro Contacts Search
I wish I had a solution, but can only chime in that I have had two Sprint Touch pro's and both have the same problem. If you call sprint, they haven't heard anything about it (supposedly) but it seems to be a problem with all sprint touch pros.
I have the same problem with my Sprint HTC Touch Pro. Don't know how to fix it. Can anyone help?
Hi everyone!
I've been going through this ENTIRE forum, and countless others on top of dozens upon dozens of google searches, and I still haven't found a solution to my SMS timestamp error.
All the solutions offered up by people seem seriously promising, because they seem to help a lot of people, and that is what's kept me hopeful: that someone out there/in here can help me fix this problem.
Basically, I have an unlocked Fido Motorola Q9h, that is being used on the Rogers network. Never delved into flashing my device, cuz I was happy with WM6. Not to mention I'd got it tweaked to a very lovely point
Then a week ago, my phone locked up after I'd put my phone into airplane mode (I'd done this countless times before with no issue), and just would not let me turn the antenna back on. Nothing I tried worked, so of course I eventually caved and did a hard reset. That was when I figured I would give WM6.1 a try, seeing as how my device was gonna be starting from scratch anyway.
I flashed to an unlocked AT&T WM6.1 ROM, and went ahead with all the registry tweaks to remove all the bloatware. Phone is pretty damn clean if I do say so myself. I've got PHM on there, GPSID, CHome COnfigurator, and that's really about it.
After all that was said and done, and I got my first SMS, I realized the message was timestamped 4 hours behind. Every single SMS from every single contact shows timestamped 4 hours earlier. In the threaded SMS stream, my messages are timestamped correctly, but the other peoples' aren't.
Example:
Me (7:37): Send me a text to see if this timestamp issue's been fixed.
Steph (3:37): Okay =)
The strange thing is that MMS messages come in with the correct timestamp, and that is something that seriously boggles my mind.
Please, please, PLEASE. If anyone out there has some kind of suggestion, I would absolutely love to hear it. Here are the remedies I've tried that have had no effect:
-Installed DST cab from Microsoft.
-"TrustTimeZoneField" w/DWORD value of "0" minus quotations of course
-"TrustTimeZoneField" wDWORD value of "1" to allow the device to trust the provider's time just in case my phone was screwing up.
-"RcvTimeStamp" w/DWORD value of "1"
-tweaked some "NetworkTimeSync" (or something along those lines) entry to a value of "1" instead of its current value of "0," but nothing.
I'm at the end of my rope here guys and girls, so please, anything you can suggest that I haven't already tried would be infinitely appreciated
Thanks in advance everybody
although i dont know the answer ive got a thing for you to try
in the setting section make sure you regional settings are set correctly
Thanks Pilot, will double check those settings. Well, as per your instructions, I've double-checked the settings, and they're correct. Have my locale set as English (Canada), and nothing. Even changed it to English (United States) just to see, but to no avail.
*sigh*
I am almost at my wits end...Is there no one out there with a Q9h running the unlocked AT&T WM6.1 ROM, that's having the same issue??? Or even better, someone out there who's SOLVED the issue?
I've even called Rogers and they suggested a new SIM card, seeing as how I have the original SIM from Rogers, and I'm waiting on it. I've even tried my sister's SIM which is a new one, but nothing. Figure it HAS to be the ROM
Found a solution to timestamp issue with q9 & wm6.1!!!
Hi everyone!!!
I can't believe I'm actually going to be the person posting the solution to this problem, but I guess it's true that perseverance pays off
This post is in regards to the sms timestamp issue that I've noticed several people are having with the moto q9 once they upgrade to wm6.1 and are on a Canadian service provider.
***This solution involves modifying your device's registry, so if you do not feel comfortable or are unfamiliar with the process, please do not proceed with the modification. I will not be held responsible for any bricked/malfunctioning devices as a result of this tweak***
Use a reg editor (I used the free PHM registry editor), and navigate to:
-HKLM (HKey Local Machine)
-Software
-Motorola
-RilDrv
Now that you're in the RilDrv Folder, there should be a few more folders in here...don't navigate to any specific one, just click the "values" softkey (whatever it may be for your devices), and somewhere in the values that become visible, you should see one that says "LocalizedTimeStamp." Open that value and modify it's value to "0" (without the " " of course)
Reboot your device, wait 10 seconds, cross your fingers and toes, and restart your device. Once your device is fully booted, and seems to be functioning normally, send yourself a text message, and check the received timestamp. It *should* be correct (ie. a minute or two or less in the future of your sent timestamp). To be sure it isn't just for your own texts, ask someone to text you anything, and hopefully the result it yields will be the same.
I have only tested this solution on an unlocked Motorola Q9h from Fido, running the unlocked AT&T WM6.1 ROM on Rogers.
I serached for close to a month with no real viable solution, so I just kept poking and prodding at my registry. Yeah, kinda dangerous I know, but I was at my wits end with this little bug. Finally though, the time and investigation paid off
Hope it goes well for all of you out there who are having the same problem!
I've had my Touch Pro for a while now but I've always had one problem with it that is pretty darn annoying, & that is that the phone seems to auto-unlock when I'm receiving calls. And so, many times the phone has answered the call in my pocket & I've had no idea. Or worse yet, it's cancelled the phone call without me getting round to even take the phone out of my pocket. I wondered if there was any fix for this.
I'm pretty damn sure that I've seen this problem before when roaming around here & PPCgeeks but after spending the past half hour or so trying to look for a fix, I just can't seem to find one. And so, I knew that if I just posted a thread that someone would most likely be able to help me & it'd all be alot easier than me spending all day trying to find whatever it is I need.
Oh, & before you ask, I've not got any custom ROMs or anything on my phone. I've installed apps from here, & some other stuff, but it's all just on the standard XDA Serra ROM.
you could install the Tachi dialer which gives a sliding mechanism if answering the phone
or swtich on auto lock after backlight dim
Free program called slide to unlock "s2u2" will work, also, you can download the program Advanced Configuration, and there is an option to allow the default slide lock that is built into windows mobile. The screen will still light up, but, unless you unlock the screen, it won't answer the call.
S2U2 Thread on XDA>>>> http://forum.xda-developers.com/showthread.php?t=527523
Advanced Configuration Utility Thread on XDA>>>>> http://forum.xda-developers.com/showthread.php?t=317070
I tried the Advanced Configuration Utility program but whenever I try to load the program (obviously after installing it), I get an error message saying:
An unexpected error has occured in AdvancedConfig.exe.
Select Quit & then restart this program, or select Details for more information.
This application requires a newer version of the Microsoft .NET Compact Framework than the version installed on this device.
Click to expand...
Click to collapse
Clicking 'Details' doesn't seem to do anything, except give me the 2nd paragraph from above (about the .NET framework).
Where can download this ".NET Compact Framework", or does anybody know of any other programs/applications/utilities/whatever which can help me with this problem.
Oh, & yeah, thanks for the help guys.
Net Compact Framework v3.5
http://forum.xda-developers.com/showthread.php?t=432470
Alright well I installed that & I'm still getting error messages when trying to load the Advanced Configuration Utility program. However this time instead I just get:
An unexpected error has occured in AdvancedConfig.exe.
Select Quit & then restart this program, or select Details for more information.
Click to expand...
Click to collapse
And then if I click Details I get:
AdvancedConfig.exe
Exception
at
Microsoft.AGL.Common.MISC.HandleAr()
at
System.Windows.Forms.ImageList.ctor()
at AdvancedConfig.□.□()
at AdvancedConfig.□..ctor()
at AdvancedConfig.□.□()
Click to expand...
Click to collapse
So yeah, there's still some kind of problem. Though what it is exactly, I do not know.
try attached CAB and have a look at below thread.
http://forum.xda-developers.com/showthread.php?t=425650
Google Pocketshield. Great program.
Hi all,
I own an HD7 device with DFT ROM 7720 (Mango).
When I bought my device, the push notifications worked fine.
A few months ago I started experiencing some weird behavior of the Push notifications service.
When I'm supposed to receive a push notification, there is a 95% chance that I will receive it in a about 15 minutes instead of right away.
In about 5% of the push notification I receive, I get them immediately to my phone.
This is frustrating because I cannot use any push notifications software (I have to hit refresh every time to receive notifications).
This has happened to me before I had the Custom ROM by DFT, it happened with Mango shipped ROM as well.
I tried the followings to solve the problem:
1. Re-install my ROM.
2. Use Shipped ROM instead.
3. Reset to factory defaults.
4. Switch between Data connection (Cellular) and Wifi.
Did anyone experienced the same problem? If so, did you solved it?
Thanks,
Lidan.
mine works with e.g. whatsapp, mail, but twitter push isn't working.
Wich push isn't working at you??? (app)
I would guess by the fact it's 15 minutes means it will be all apps that aren't working for push. When the phone can't maintain a push channel (as seems to be the case with yours) it 'falls back' to polling the push server every 15 minutes to check if it's missed any messages. Pre-mango that used to be every 60 minutes.
One thing to make sure of (you've probably already checked this) is that the battery level is more than around 30% as that can affect push reliability (the phone can turn the push channel off when the phone transitions into a lower power state).
Another thing to try is to take the battery and sim card out and leave it like that overnight and then put it all back together the next day. Other people have said this kind of 'power cycling' helps when push isn't working.
Microsoft said in one forum it may also be down to some mobile phone operators cutting off the push channel data connection too quickly - but I don't know how true that is, or if there's anything you can do about it (maybe worth ringing them). The other thing you might try (make sure you put all the original stuff on first) is HTC customer care - I needed to use them recently (touch screen failed) and they were fantastic.
Mango seems to have made push a lot more reliable for most people so it's a shame it's had the opposite effect for you. It was very unreliable when WP7 first came out for a lot of people - it would work ok whilst the screen was on and other connections were being used, but if you left it (i.e. to go into standby with the screen off for a few minutes) push would stop working / the channel would be lost. I guess you have already but maybe worth reinstalling all the original shipped rom, and double checking you've got exactly the same spl / radio / etc. that it shipped with, and then just using the official updates via zune to get to Mango just in case the custom rom affected something.
I hope you manage to fix it.
Ian
I'm having the same issue with my HD7. I know that push worked at one time. But it is not now. Any solutions out there?
same problem with me, On lumia 800, funkyrom, fb twitter whatsapp push notification not workinh