Replacement Vodafone V1620 problem - MDA III, XDA III, PDA2k, 9090 General

This is my second V1620 in about three weeks: the first replacement was after about nine months because the SD card slot stopped working. The replacement suffered severe touchscreen drifting and needed alignment every five minutes so they swapped it for me.
No complaints about Blue Angels or Vodafone: here's my problem. I use SPB Backup and am very careful about this to restore my system so that TomTom continues working OK. However after restoring my system today I find that TT (Navigator 5.21) is now coming up with a different device ID than before so my continuity is broken.
Does anybody know why this would be? I have checked the ROM version and there is no change there, although I am in desperation about to flash using the same version. I have no logical reason to this but I am clutching at straws!
All suggestions gratefully received, and many thanks in anticipation.
Jonathan

Strange.. My Vodafone v1620 has a deviceid of PH20B2, check if yours is like this, using GetDeviceData

Thanks xan, that is quite correct. The thing is that every pocket PC generates an unique system ID every time you do a hard reset. This is stored in software and can be overwritten by restoring a backup. In this way programs that are keyed to that ID such as TomTom will continue working even after a hard reset. If you do not take a complete backup, using Activesync or any other tool, then you would find that they stop working which is the situation in which I find myself now.
The strange thing is that I have made hard resets and restores many times over the months without a problem, hence my appeal for help!

Do you know where this id is stored?

No idea, I'm afraid. All I know is that if you make a full restore then it reverts. I believe that it may be referred to as System ID or SID as under W2K and WXP.

Related

How I made my XDA IIs more stable....thanks to Wilesd

I saw a post on here about the progs in the windows/startup folder. Someone mentioned that removing the "connections" executable file had made their XDA more stable. It seems to be the exe that places the O2 icon on the task bar at the top of the screen.
I tried just that...moved the file out of startup to a temp backup folder and did a soft reset.
That was a couple of days ago and I haven't had to reset since Previously I was having to reset 3 or 4 times a day just through very light use!
Thanks for the suggestion Wilesd
Hmm not sure what .exe you are talking about in the windows\StartUp folder.
All I have there are:
Code:
aPerSaveStark.lnk
Camera_Detect.lnk
CheckAutoRun.lnk
ChgDfLnk.lnk
cPerSaveStar.lnk
IA_Caller_ID.lnk
nPerSaveStar.lnk
O2 Connect.lnk
poutlook.lnk
RegNotify.exe
Run_BTTrayCE_10.lnk
Spb GPRS Notify.lnk
STK.lnk
tPerSaveStar.lnk
As you can see.. The only .exe I have is the RegNotify.exe.
The closest that I get to O2 is the O2 Connect.lnk shortcut..
Is that the one you moved?
I don't have the "02 Connect" link in my startup. The file I moved was called "Connections". I can't see on my pda what the file extension is so I don't know if it was a .lnk or a .exe. The mention in the previous post I got the info from was that it was an executable though.
THIS is the post I saw it in.
Maybe it's a country specific thing ?
After all the crashing I was getting with the 1.31 ROM and O2 Active which I never used I decided to do the Corporate install that does not put on the O2 Active rubbish. My phone has not crashed since before I was getting at least 4-5 lockups a day!
Glad I could help, anyway I had to hard reset mine after i installed some dodgy camera upgrade Cab file so decided to give the "Corporate" option ago this time, just select Corporate during the Boot up and type 0506 when it asks for a corporate code.
No looking back now, basically you get a clean WM2003SE install without ANY O2 rubbish but all the GPRS configs etc.. intact. I have not had to do a single reset since.
Recommend this method to any fed up with the O2 active stuff screwing up your IIs. I can honestly say I can't fault the device now.
Thanks for the info guys.
I been holding back from doing the ROM update on my XDAIIs due to everyone saying they have to keep sot reseting their device.
I've just removed the connections.exe from startup folder on my existing setup - make sure i'm happy to carry on without the O2 icon at the top.
Will let you know how I get on.
Thanks again.
Great I shall try this tomorrow.
I've been getting regular crashes on my XDA 2s since I upgraded to the latest ROM.
D
Thanks, removed the O2 connections as suggested 2 days ago and have not needed to reset since.
Was having to reset 2 or 3 times a day since I'd upgraded.
difference between corporate and personal
Whats the difference between corporate and personal mode?
Corporate mode basically doesnt install O2 Active at all so you're left with the default windows screen (presumably so you could customise with your own corporate guff)
numanoids said:
Corporate mode basically doesnt install O2 Active at all so you're left with the default windows screen (presumably so you could customise with your own corporate guff)
Click to expand...
Click to collapse
Thanks and what do you mean "0506" as corporate code?
thanks ...yellow screen?
thanks guys the corp version seems to do the trick, look very stable now. who need o2 crap. however i can't fail that notice that the screen is slightly yellow from certain angles. it look whitish when you are right in front of it but from any other angle it looks yellowish...anyone else with similar screens? don't remember this to be the case with my previous trusted xda 2...it's a nice device though...
yanni
It seems to be a thing with the latest XDA2 "s" and "i" models as it didn't happen on the original XDA2. I did read that the original had Sony screens but the newer ones are made by someone else.
Regardless of this minor inconvenience, I do think the new screens are much brighter that the previous ones...Just my opinion of course :roll:
It seems to be a thing with the latest XDA2 "s" and "i" models as it didn't happen on the original XDA2. I did read that the original had Sony screens but the newer ones are made by someone else.
Regardless of this minor inconvenience, I do think the new screens are much brighter that the previous ones...Just my opinion of course :roll:
increase brightness levels
yes they are brighter indeed...also, the xda2s by default reduces the light of the screen to conserve power when used on a battery...if you fix this the yellowish feel goes almost away...why can't they get their sceens right, same probs with bloody apple products, don't they understand that their screen are the most important interface with their devices...
y
connections.exe in start up
I removed the connections as advised in my XDA IIs and yes it did improve the stability, but after several days I found that even though the PDA was working well the phone would not work properly, either the phone would lock or it would not dial out, or you would answer a call but the caller could not be heard. On two occasions my blue tooth connection was lost. though this only happened on the first day. This was solved by a soft reset. So I have come to the conclusion that yes connections is the trigger but also it dose serve some purpose. I am therefore going to use the corporate mode which seems to be a common solution on many forum topic subjects. I hope this feedback helps others.
I have only just got an XDA2s & noticed that I was resetting 5 or more times per day. I have now removed connections.exe from the startup folder and also removed all references to O2 Active from the Today program and the Start Menus
I'll post results in a few days
Re: connections.exe in start up
fvau72 said:
I removed the connections as advised in my XDA IIs and yes it did improve the stability, but after several days I found that even though the PDA was working well the phone would not work properly, either the phone would lock or it would not dial out, or you would answer a call but the caller could not be heard.
Click to expand...
Click to collapse
I tried corporate mode with removed connections.exe and installed beta of the new today screen.
I have noticed an issue with losing connections too, and your comment about not hearing caller reminds me that happened to me but I thought nothing of it at the time.
I have noticed a bit of a pattern to the not dialling out issue
Basically if the phone loses all connection for a while (not sure how long) then it seems to not get it back when you get to an area you can receive. A soft reset sorts this out.
But this is highly annoying for me, I live in London and go to work on the underground (subway to you yanks) and when I come out if I forget to reset my BA it will not receive calls or dial out.
XDA IIs Stability
What ROM version or versions are you all using?
I'm also having to reset my XDA a couple of times of day and would like to improve on the stability of the device. I've looked in my \Windows\startup and have various links (one is O2 Connect) and two executables (CommLoader.exe and RegNotify.exe).
Also, when I have had to do a hard re-set I have never gotten the option of 'Corporate or Personal'. Probably because of different ROM versions.
Also have any of you experienced problems with the Bluetooth no starting because of low memory on a regular basis?
Do any of you have an O2 XDA IIs from Asia?
Thanks
No resets in 3 days now I've removed connections.exe & stop using O2 Active UI Not using corporate mode though - I'm not brave enough yet to try upgrading my ROM

My new xdaIIs locks up about 5 to 10 times a day.

I just had to have my old xdaII replaced with the XDAIIS. Im not sure this is a good thing. I felt a better replacement would have been the XDAIIi , but the insurance wouldn't go for it. After getting it, I found it to be better than expected. I didn't like the keyboard feature at first and still havn't used it. I can say it does have a pretty blue lighted keypad, which I will probably never use.
What I don't like is the fact it locks up 5 to 10 times a day and has to be reset.. There seems to be no reson for this. I do use the old xdaII case, which might come in contact with some of the buttons ( not sure) probably not. I have ordered a new hard case that is made for this pda, in hopes this will solve the problem.
Has anyone else had this lockup problem???
Dave
David Vinyard said:
I just had to have my old xdaII replaced with the XDAIIS.
<snip>
Has anyone else had this lockup problem???
Dave
Click to expand...
Click to collapse
Have you loaded any other apps or today screen plugins etc?
Is it a vanilla device that is just locking up?
You'll get lots of people teeling you it's the O2 software - but mine works fine with it running.
I had exactly the same problem. The device would usually hang while I was using Wi-Fi or GPRS, and I'd have to reset at least 3 or 4 times a day.
The o2 active software constantly monitors the status of these types of connections, and is most likely the culprit. Believe me, you are much better off without it.
After removing the o2 software I've not had to reset device at all. Just disable the o2aui today plugin by unticking the item in the Today settings dialog. You'll also need to delete the shortcut called Connections in the \Windows\StartUp folder.
Let us know if this helps with the lock-ups.
-no1
how to remove the O2 software.
thanks very much

artemis can't answer calls!

Hi I have had this phone for just over a month and sometimes when it rings I can press a key to answer it but sometimes it will not respond. I have tried using both hard keys and the screen buttons but it won't answer the call! Sometimes it then launches co pilot instead! I have tried a soft reset but it has not worked. It is on o2 and I have tried thier data support but they are USELESS!!! all they offered was to send it off for repair (which will take two weeks!) any advice greatfully recieved.
Do a hard reset - look in the manual or wiki on how to. Something has got corrupted and this is the best way to fix. Backup you data and pim first.
Software conflict for artemis using co pilot
Hi, i tried taking out the sd card and removing the co pilot software from the phone. I then tried ringing the phone. It worked fine so I have reinstalled the co pilot and will see if it works OK over the next few days. Has anyone else had this problem and if so what causes it? cause I want to stop it happening again. Is it corruption or software conflict?

8525 freezes, soft reset, then "No GSM"

Recurring 8525 problem since upgrading to WM6 ROM (AT&T version). The phone will freeze completely (clock doesn't advance, screen and buttons and keyboard don't accept input, display freezes at on or off). When restarted by soft reset, the phone will frequently come back up with no GSM. When that happens, sometimes if I remove the battery and leave the phone off for a few hours then GSM will come back and will work for a while and then lock up again.
When it comes back with GSM service all of the network logon info for GPRS, my Wi-Fi networks with their auth info is gone.
Also email accounts are gone from the account picker and can't be re-created with the same names even though they have completely disappeared. I assume the settings are still in the registry but accounts just aren't showing. One account still shows on the Today screen, but isn't in the account picker.
A hard reset "fixes" things for a while. I've experimented with only installing a few of the most necessary 3rd party apps, without finding any "smoking gun" program that's causing problems. I've also re-seated the SIM card multiple times. I'm thinking it might be a hardware problem.
Today I flashed the radio to 1.54 and it has worked for a couple of hours without needing to be reset.
I'd be interested to hear what possible diagnostic paths I should look at before I call AT&T and begin the rigmarole required by tech support. Anyone with a very similar situation?
Thanks in advance.
I'm having the same problem. I was thinking of going to AT&T to get a new SIM, thinking that was the problem. Any solution yet?
-Pete
I started having the same problem with mine last week.
Sometimes it locks up, sometimes it gets stuck at the windows logo durring boot, always displays no gsm rom on boot.
Take a look at the how to unbrick thread. no gsm rom msg is one of the types of brick.
I installed hard spl ( already had it actually ). Flashed os, but it didn't help. Flashed GSM and no gsm msg went away. The phone is still acting strangely.
remember, just because the rom came from your carrier DOESNT mean that it doesnt have problems. Alot of people seem to have problems with upgraded rom versions from their carrier and end up either downgrading to previous rom or flashing cooked roms. try the previous rom or another cooked rom and see if that fixes the problem before blaming the hardware. It will save you a major headache trying to troubleshoot something that is working perfectly....
Please remember to do a bit of reading and hard spl your device before going off and bricking your Hermes. 10 minutes of reading might prevent hours, days or weeks of hair pulling, nail biting insanity to find the answer. Cheers.
hello people,
I have my SVP M3100, original from orange spain - but CID unlock to work with portuguese carrier, now I live and work in Hereford UK, and I use a sim from Three and other from Lebara the three sim is to have net on my pc and the lebara sim is to make low cost international call, and i switch many times the sim's to make calls and to have internet, now i have the same problem that you have, i try to upload the HTC original rom that have IPL. BOOTLOADER, SPLASH SCREENS EXTROM GSM, but lock at 12% I try upload ongly radio rom and the same a think that somekind of hardware problem caused by to many sims switch, if any body have one solution please tell me
Sometimes it locks up, sometimes it gets stuck at the windows logo durring boot, always displays no gsm rom on boot."
Same thing happened to me. Tried to reflash original ATT ROM , Radio Only, OS only. Gonna send it for the repair. Phone is not under warranty anymore hope that the price of repair will be less than price of new phone.
BTW, is there any way to remove Hard SPL from the phone?
how much was the price of repair?
Try changing you radio to a new one. i have had the same problems in the past with different radio roms and rom versions. so i am using radio 1.54.30.10 with pdavet roms and have had no isuue.
Ray_jai said:
how much was the price of repair?
Click to expand...
Click to collapse
Got my phone back fixed. They charged me for shipping only $19
only $19!?
What if I don't have ATT anymore?
do you know?
i had the same issue check for my previous posts i think no GSM is a common error there is method flashing himalaya rom on hermes to erase GSM sector.
if you cant find the link PM me .
i hope it solves your problem.
tracylynnt said:
Recurring 8525 problem since upgrading to WM6 ROM (AT&T version). The phone will freeze completely (clock doesn't advance, screen and buttons and keyboard don't accept input, display freezes at on or off). When restarted by soft reset, the phone will frequently come back up with no GSM. When that happens, sometimes if I remove the battery and leave the phone off for a few hours then GSM will come back and will work for a while and then lock up again.
When it comes back with GSM service all of the network logon info for GPRS, my Wi-Fi networks with their auth info is gone.
Also email accounts are gone from the account picker and can't be re-created with the same names even though they have completely disappeared. I assume the settings are still in the registry but accounts just aren't showing. One account still shows on the Today screen, but isn't in the account picker.
A hard reset "fixes" things for a while. I've experimented with only installing a few of the most necessary 3rd party apps, without finding any "smoking gun" program that's causing problems. I've also re-seated the SIM card multiple times. I'm thinking it might be a hardware problem.
Today I flashed the radio to 1.54 and it has worked for a couple of hours without needing to be reset.
I'd be interested to hear what possible diagnostic paths I should look at before I call AT&T and begin the rigmarole required by tech support. Anyone with a very similar situation?
Thanks in advance.
Click to expand...
Click to collapse
I've got exact the same symtoms. No GSM, network and auth settings gone, opera registration lost etc. It started a few days a go, in the beginning I had a working GSM most of the time, but it became less and less and now it doesn't have service at all anymore.
Currently device information shows:
ROM version: K's Rom v1.21
ROM date: 10/03/07
Radio version: NONE
Protocol version: NONE
Model No.: HERM300
IMEI: <empty>
Does anyone know a permanent solution?
I have the SAME PROBLEM!
I was about to get radio to work 3 days ago, and now the radio says none.
it's like the radio removed itself.
ok this doesn't make sense, I used the hima rom to remove the radio.
and now the radio is back! wtf?
Hm I tried everything but I can't seem to reflash the radio. About every version I try hangs at 0%. Sometimes when I flash from SD card it hangs at arount 10%.
Tried different SPL versions as well
Damn you radio!!!
BTW, I have no idea what they did to my phone there, but after returning from the AT&T Repair center the Call timer was zeroed and Device ID is now different from what it was before in Skyscape software
Any solutions yet? Im having the same issues.
The reason why Active Sync restarts
For many people the Workaround "not a hack or registry at all" does not work is because of a event based notification that runs the program anytime the time changes. Since your phone updates from the cell tower, it updates the time alot even if by mere seconds well this update runs activesync. Get yourself MemMaid
run it in advanced mode then Jump to Databases then select Notification Queue you will see a list of 3 types of Queues; Time Based, Classic Time Based, and Event based. Go to the event based queue, you should see at the end of this list 3 listing for repllog.exe with the active sync icon. Click on them individualy and read what shows up in the window below put a check mark next to the listing that describes the event as "apprunaftertimechange" it is normaly the last one on list
Also make sure there is no repllog.exe listed in any other queue for a time based event. Leave the other instances of repllog.exe since you still want your device to sync when its connected to the computer. Once you select all events that desribe running repllog.exe after a time change or at a certian time and date press the delete button.
This worked for me on my 8125 and the tilt and if i would of figured this out before i had ATT replace my 8525 i probably would of not got the tilt but lol they gave me tilt free cause all the problems i had with 8525.
let me know if this works for you guys that still see activesync running after the fake server WORKAROUND.
This should work
memmaid is not free but i think its free to try and if all you do with it is fix this problem then great or find a way to register it cause it does help has cool tricks and tweaks
Wow, still no real fixes for this problem, bummer
running memmaid work
running memmaid works and fixes the random start of activesync and once the random start of activesync is fixed the device will not lock up because of activesync this not to say if some other program you may have installed locking you up as well

New XDA Zest firmware

There's a new Zest firmware available for download from http://www.my-xda.com/. The filename is Xda_Zest Firmware Update_V7.7.0S.WWE20.00_M4.6.5.P7_V2.1.4 GBR20, which seems to be updates to most of the roms inside the zest. It's installing at the moment, and the upgrade interface on the phone is displaying "GalaxyMini5 Eboot (3.33.0). Since this appears to be a codename for the P565, I guess this is more evidence that the XDA Zest is simply an underclocked P565 and more evidence that P565 firmware may well work on it.
Warning, this firmware does not appear to contain the O2 menu software, or the free GPS software that comes with the phone (although maybe the latter can be re-installed from the SD card). Shame - I rather liked the O2 menu interface.
what improvements does it have? Is it actually worth upgrading?
Thanks.
The only things I can see that I don't remember seeing before are a couple of new or updated control panel entries. Video calling is probably the really important one.
You seem to lose the RSS reader, the O2 auto settings, the O2 menu and the GPS s/w (although the latter was only a demo). I have no idea if using the SD card that came with the Zest will restore these, as I don't have it. (If the software is all on there somewhere, and someone could bung me a copy, I'd be really grateful.)
It does make me wonder how the P565 firmware compares. I understand it has a nice touch interface on it.
It seems odd that the new firmware would remove all the o2 specific bits. Great if you want to use it on another network I suppose, but I quite like the mobile shell or o2 menu.
The satnav software isn't on the sd card - only the maps.
The instructions say:
Please note that if you already have CoPilot satellite navigation software on your Xda, refer to the Xda Zest user manual before upgrading your device software.
Click to expand...
Click to collapse
I couldn't see anything of significance in the user manual.
Interesting. I actually have Tomtom for GPS on a different SD card, which is related to the reason I don't have the original SD card. Tomtom autoinstalls from the SD card, so I thought it might be that the O2 software installed itself from the SD card provided by O2. I guess that if it's only maps on the SD card then that's not the case, and the new firmware does strip out all the O2 extras, which seems like a peculiar decision to say the least.
Still, it did get me to try the new SPB mobile shell 3, which is what the O2 menu is based on, but nicer. I'm trying to decide whether it's worth the $35 for just a flashy finger driven interface. The weird thing is, it actually might be.
I'm actually going to upgrade my firmware to new one which is currently available in O2 site. What I want to know is if upgrade mine to the latest what would be the changes I may seen... Is it worth upgrading by loosing all the software?
So far I've seen nothing to write home about. The only reason might be if you can't already make video calls and want to do so. (I never make them, so I have no idea whether or not they're supported in the original firmware.)
I just upgraded mine to new firm ware. It worked fine for me. I didn't lose any O2 extras inc O2 menu. It was Oki but haven't tried yet to make video calls.. I will install iGO8 and will uninstall the co-pilot.
SPB Mobile shell 3.0 Rocks working smoothly with my Omnia and Xda Zest
I've just updated, and I didn't lose any O2 extras either (including Copilot). I backed up the Program Files\Copilot folder on the device to my PC before updating, and copied it back over after the update and voila, I've still got my fully activated version of Copilot. It did still prompt for allowing it to connect to the net during the 14-day trial the first time I ran it, but the license screen confirms it's the full version.
aDe
I have a working theory that the autorun on my Tomtom SD card might have run in preference to some autorun that might otherwise have run the first time the OS booted. I could test this by re-installing the firmware, but it's kind of a pain to have to put all the data on again.
Having played around some more and browsed the Extended ROM on my device, this does appear to be what happened, as all the CAB files are present. Fortunately this is a bonus for me, since I'm not on O2, and most of these files are useless to me, and I can therefore just pick and choose the apps I'd like to install.
This might be useful to other Zest users - the hack to make the Extended ROM visible:
Use your favourite Registry Editor to make HKLM\System\StorageManager\Profiles\ONDisk2\FATFS\MountHidden set to 0 (default is 1)
You can then browse to \ASUS_ROM\ in Total Commander to view your Extended ROM partition. The ROM does not appear to be write protected, so you can now put all the packages *you* want re-installed on a hard reset in there. Neat.
I contacted O2 support about this issue, and they replied saying that:
On occasions the O2 menu can drop off after a ROM upgrade, but this would usually be resolve by either hard resetting or running the upgrade again. The o2 menu is still installed on the new ROM.
Click to expand...
Click to collapse
I have now done this upgrade and have retained the 02 menu. The radio reception seems a bit better as I now get HSDPA at home, which I didn't previously, so the radio upgrade seems to be worth it.
ringer
ive got the zest and am happy with it so far apart from the last 2 days i cannot hear it when i get a call everything else works ie.system sounds,core player etc but the actual phone wont ring it just vibrates ive reset it a million times and checked system settings etc but nothing so if anyone has any ideas i would be very grateful, also how do you know if you are getting hdspa or not is there a setting for it or something, cheers guys.
The connectivity icon at the top right of the screen shows what communication protocol is being used by showing a symbol (usually just a single letter) in a solid square. The letters I have seen so far are:
G - GPRS (2G)
E - EDGE
3G - 3G (this is the odd one out with the two letters squashed together)
H - HSDPA
It's worth mentioning that on my train ride home I see all four protocols at different points, and the hand-off between them is very smooth.
thanks for quick reply i will keep an eye on it, still no joy with my ringer though its very strange. never had a problem like it on my orbit. i will keep investigating ,also do you know if anyone will be coming up with a rom for zest as i miss manila 2d although mobile shell v3 is good.
Have you checked:
Start->Settings->Sounds & Notifications
On the Notifications tab you can select the "Ring type", one possible choice of which is "Vibrate", which will make the phone only vibrate on incoming calls. Just guessing.
yes ive tried all that it might be affected by software ive installed recently i will try unistalling them one by one and see if that helps, failing that il do a hard reset i guess, anyone know how to hard reset the zest? thanks for your help.
There is a contortional key sequence for this, but you can also reset it by going to:
Start->Settings->System Tab->Default Settings
cheers managed to sort it , i installed mini lyrics software and ticked all in associating files which for some reason stopped the phone from ringing
thanks for your help.
Failure of firmware upgrade
Ive just had a power failure whilst upgrading the firmware on my new xda Zest and all it it shows when turning on is "OS Update failed! Please update again". Is there anything i can about this or will it need to be returned to O2. Any suggestions. thanx

Categories

Resources