Related
Dear all,
I have installed ppc 2003 and tested its stability for 3 days. The followings are what I found bugged in this rom version.
1. For Some times the ppc won't turn on again after the screen turns off or after pushing unit turn-off button. I had to soft reset the unit to make it running again. This has happened to me quite a few times after I sync with my PC
2. My sd card was totally erased for several times, even the 'detect digital camera' option in the picture program had been deactivated.
So far, I only have these 2 inconsistencies. And after some trials here and there, here is the possibility of the error causes
1. Ppc 2003 doesn't work with window 98 even though the activesync 3.7 does. So try avoid sync through pc with ms 98.
2. I think that due to some incompatibility between the xda hardware and the inherent options in the ppc 2003 (my best guess is the bluetooth and digital cam option) that encompasses the functionality of sd slot, sometimes we'll find data in sd card being erased w/o warnings. I have also found out that programs that act itself as driver b/w the xda and other external hardware such as the external keyboard driver can also cause such a sd formatting problem.
Can anyone confirm my findouts? Any comments are extremely welcomed
Please post your ROM, RS and Protocol Versions.
dear,
I just happened to have my sd card erased again, pls help why?
rom version 4.00.01 eng
radio ver 4.21.00
protocol 32S54
please help ou
Dear all,
I think my conclusion to the screenoff problem was not valid since I still have my screen blackouts even though I am using window xp to sync. do you, mates at xda-developers, have any suggestion on how to get around the problem. Thanks
Sounds like its a Power problem to me!
So check your power settings.
OK, This is my first post. MW2003 seems to be must better that PPC2002 except for one thing. HOW DO I TURN MY XDA ON. the only way I have found so far is a soft-reset.
When the XDA screen goes blank it really isn't off because anybody calling get the ringing tone, unfortunately the phone does not ring so I cannot answer.
OK, This is my first post. MW2003 seems to be must better that PPC2002 except for one thing. HOW DO I TURN MY XDA ON. the only way I have found so far is a soft-reset.
When the XDA screen goes blank it really isn't off because anybody calling get the ringing tone, unfortunately the phone does not ring so I cannot answer.
Click to expand...
Click to collapse
Dear,
I later experienced some correlation between the system (Screen) blanks and the installation of some software that was supposed to be used in ppc 2002 (for me the program is "True Fax"). Each time after my installation of True Fax, the system simply goes blank and I have to do the soft reset to uninstall such program to revitalize the system again. Hope this does some help to you. And if you have found some similarities, please confirm my findout. Thanks
It also may help if one removes the SIM Tool Kit shortcut (stk.ink) from the Startup folder. This shortcut is also know to bring up a blank screen. So remove the shortcut and soft reset. HTH
Qman is correct. For some reason the simtoolkit launches a program called HTC SAT on startup which produces a blank screen. Doesn't appear to harm anything but I removed the link anyway and all is still well. I have detect digital unchecked in the pictures program and my sd card was erased as well anyway. Any other thoughts on this?
ROM:4.00.05 ENG
ROM Date:6/5/03
Radio: A.20.10
Siemens SX56
Ken,
Like you, I think I have founfd the cause of my Power On problem. Looks like it was caused by a the GPRS traffic monitor supplied on the o2 XDA CD. I belive the progam was called "GPRS Traffic Counter"
valheru said:
I have detect digital unchecked in the pictures program and my sd card was erased as well anyway. Any other thoughts on this?
Click to expand...
Click to collapse
This one is still a mystery to me, but I’m starting to wonder if it has something to do with certain apps. being installed on the SD card.
So lets do this, if this has happened to you can you post what apps you had installed on your SD cards at time of occurrence. Then maybe we can get a better fix on whats actually causing it. What you think!
For me I had:
Pocket Plus (which has since been removed)
SPB GPRS Monitor
PocketBIble
Resco Explorer
HPC Notes & Spell
Cash Organizer
ListPro
CodeWallet
HanDBase
I had installed:
pockeplus (since removed via hard reset):to RAM
spb gprs monitor:to RAM
that was it. no apps installed to the sd card at that time, just some text files and wavs to see if I would have an sd card erasure.
This morning I installed to the sd card:
Adobe Reader
Repligo
Lygea pocket 12c
fonix voicedial with us voice pack
Franklin Covey Plan Plus-Daily Record, Prioritized Tasks, and Activesync app
Illium eWallet
Agenda Fusion 5 w/icon pack
Sprite Pocket Backup
In RAM I have installed:
Spb GPRS monitor
MUTX RingtoneX
Isn't collaboration GREAT?
I have detect digital unchecked in the pictures program and my sd card was erased as well anyway. Any other thoughts on this?
Click to expand...
Click to collapse
Dear all,
Since I have had countless SD card reformats, I wonder whether you guys have noticed the same thing?. Every time when the system starts to wipe out your sd card, there are iterations of sd card boots. That is the system will locate your same sd card more than once and acknowledges it as multiple different sd cards. This is noticable in the "Memory" program -> SD Card Menu (under settings) which shows multiple sd cards (i.e. storage card, storage card2, storage card3 and so on) being inserted at the time even when only one single sd card is in place. I think the secret to this is to try to stop that from happening. ANd since I'm a newbie about techno thing, I wonder whether it has something to do with the registry or it just systematcally occurs at random (suggest anything, anyone?)
For the time being, I have to lock my sd card unless when installation times come. BTW, valheru & Qman, I have not installed any of the programs you have in your sd cards (besides acrobat)
Hmmmm. Call me Val, it's easier. I have not had the numerous sd card iterations you have mentioned. Knock on wood, no erasure yet though I only had one. Locking the sd card is a good idea but I agree it is a pain. Do you have the detect digital camera option in the pictures program unchecked? I have heard this does and does not work but since the xda doesnt support sdio you might as well uncheck it. Also, which version are your running?
I think the sd card detection is built into the system much like PnP so I am unsure if it can be disabled. If it is detecting the card over and over, there may be a power issue or perhaps some dust, etc. has come into contact with the pins of the card thereby intermittently blocking the signal? Might want to check to be sure....
Dear Val,
I have had the digital option unchecked since the very beginning and nothing helps. It seems that the erasure comes at random, but I just happened to witness the iterations by accident.
BTW, my version is
rom version 4.00.01 eng
radio ver 4.21.00
protocol 32S54
Valheru Eldarr
Seeker of Knowledge
Siemens SX56
ROM: 4.00.05 ENG
ROM Date: 06/05/03
Radio: A.20.10
Protocol Version: 324e4
Model No: PW10A1
Click to expand...
Click to collapse
Dear,
BTW again, is your ppc 2003 the official one for SX56, mine is not
P.S Really wish I could go back to using my 3.17 rom (the disadv far outpace the adv ones, at least for mine)
Nope, unofficial, back yard kitchen brew by Jeff's ROMKitchen.
Dear Val and others,
Just when I thought I could go to sleep, my SD card was erased again for the ......th time (I lost my counting somewhere along 10s). Up to now, I do not know what causes it. BUT I DO KNOW how to check whether your SD Cards are secure from erasures. If you have the programme called "PHM Device Manager" just go to the Storage Port and check the Device ID under it. It is supposed to be pre-assigned and stay intact. If after a while of launching programs and/or soft-reseting the unit, the Device ID (SD Port ID) numbers up, quickly lock your sd card before everything is erased. If anyone happens to know what causes changing SD Port ID, please let me know. It looks to me as if the XDA is constantly examining the SD slot and each time it does, it recognizes the same SD card as different ones.
I hope yours are still intact after such checkup cos if not..........???
I have also found out that the numbering up in Device ID (in Standard Disk Drive, DSK1) is 100% subject to how many times I have turn on/off the screen. Seems like the SD Card iteration is ignited each time the screen is turned off and on. ANyone, any clue to why?
Interesting. I'll have to check on that. I honestly never noticed the correlation. I have observed this site for a few months and I now making it a point to participate daily!
I'm thinking of upgrading from XDA I to II, has anybody else who has upgraded come across anythings that was worse on the XDA II than on the XDA I, for example battery life and using the screen outdoors? Also I find PocketPC 2002 very buggy and the phone is unreliable - have these issues been resolved in XDA II/PocketPC 2003?
some people have this issue
http://forum.xda-developers.com/viewtopic.php?t=10088
some people feel that the screen dont like like it's 65k colouer screen
http://forum.xda-developers.com/vie...postorder=asc&highlight=color+colour&start=50
some people dont like the bluetooth stack from ms which xda2 use
which are a bit limited in just about every way you can think of
http://forum.xda-developers.com/viewtopic.php?t=9618&highlight=bluetooth
Wow, wasn't aware of so many potential problems on the XDA 2... I didn't notice any problems with the color while playing with a demo unit. Next time I do get my hands on one I'll scan it more carefully.
I too am using a XDA I, but I do not plan on pouncing on the XDA 2 because there are a few new units on the horizon.. most notably the HP 6300 and MDA III.
well it's not like the colour is worse then xda1 just that some people dont think it's true 16bit colour
Everything is fine with my unit; I just don't like the MS Bluetooth Stack, doesn't let you listen to music through your Bluetooth Headset
WeatherB said:
Everything is fine with my unit; I just don't like the MS Bluetooth Stack, doesn't let you listen to music through your Bluetooth Headset
Click to expand...
Click to collapse
Will the MDA3 have this fixed?
i think when no other info is given about bluetooth stacks
then they are using the free and not all that great ms stack
Rudegar said:
i think when no other info is given about bluetooth stacks
then they are using the free and not all that great ms stack
Click to expand...
Click to collapse
Thats too bad... I may actually consider the HP63xx if this turns out to be the case...
markh said:
I'm thinking of upgrading from XDA I to II, has anybody else who has upgraded come across anythings that was worse on the XDA II than on the XDA I, for example battery life and using the screen outdoors? Also I find PocketPC 2002 very buggy and the phone is unreliable - have these issues been resolved in XDA II/PocketPC 2003?
Click to expand...
Click to collapse
I use XDA1 with WM2003 with no problems. I never use the 2002. What problems are present?
- If you lose reception it will sometimes not automatically reconnect to the network
- If you lose a GPRS connection you have to do a soft-reset to connect again
- Sometimes it won't do a GPRS connection - again a soft reset. Sometimes when it does connect can't download any information
- SPB Full Screen Keyboard sometimes doesn't work because of some fault in the OS. One has to take out the SD card and do a soft reset but when you do that you can't access the SD card
- When you put in a new SD card it won't recognise it - one has to do a soft reset.
- Sometimes the device will do a soft reset on its own, though I think that is down to a lose SIM card.
- If you have the SMS client open while in standby mode you won't get any audio alerts for incoming SMSs
- On some days I get double alarms on one alaram
- One seems to have to do a soft reset before uninstalling programs, if you don't, it tries to uninstall it but you get a busy icon forever
Some of the above are probably hardware problems though some are OS bugs. I wish the device would be a bit more reliable
do you have an xda2 ?
because your profile says xda1 ?
I use my Wallaby about 5-6 moths. (Yes I have an XDA1)
- If you lose reception it will sometimes not automatically reconnect to the network
This happends for me once. But I think the whole OS freeze, maybe from other problem, or program. I lose the network twice a day, because I travel with underground. But no problem to loging on.
- If you lose a GPRS connection you have to do a soft-reset to connect again
Oh yes, this is a roblem. I try GPRS when I bought my device, use internet for one month, and yes, it happends often for me too.
- Sometimes it won't do a GPRS connection - again a soft reset. Sometimes when it does connect can't download any information
Yes, yes. Now, I remember that problem.
- SPB Full Screen Keyboard sometimes doesn't work because of some fault in the OS. One has to take out the SD card and do a soft reset but when you do that you can't access the SD card
I don't use this program
- When you put in a new SD card it won't recognise it - one has to do a soft reset.
I used SD card rarely. Only 5-6 times, when I borrowing one from my friend. But I had no errors like this.
- Sometimes the device will do a soft reset on its own, though I think that is down to a lose SIM card.
Never happend to me
- If you have the SMS client open while in standby mode you won't get any audio alerts for incoming SMSs
Hmm. It mean, when inbox was open? I never tested it.
On some days I get double alarms on one alaram
Only happend for me, when load back a backup, and there was double everithing (contats, appointments....) when I synced with outlook. I think I make something wrong.
- One seems to have to do a soft reset before uninstalling programs, if you don't, it tries to uninstall it but you get a busy icon forever
It is a software failure I think. maybe for the wrong programmed softwares, and the OS.
I hate one thing with this MS phone:
I use startup password. When I receive a call, I can pick up the phone, without enter the password, but can't change the volume. :evil: I hate this bug well.
I think the XDA 1 is the best value phone/pda on the market today and the xda developers have made it even better value with their flashing software and bespoke roms. I use one as a phone, navigation system, book reader, mp3 player, internet explorer, pop3 email downloader, games, and much more, there is nothing that comes near to the functionality for the price. I have bought several used 64meg devices for friends and they are all amazed at the value for money, when coupled with gps and tomtom its still cheap but packed with features and options.
I have an XDA1 my only 2 problems are that it does not have a SDIO socket & Bluetooth, and as Cruisin thru said the developers here enhanced the device to be the best working PDA PHONE in the market they could just do that to the Himalaya's as well since it has all the missing features in the Wallaby but it need a lot of hard work.
Because of BT headset/handsfree profile issues, someone tells me which is the best radio ROM to use with WM2k5?
1.18?
I'm actually using 1.14
Thanks
Fernando Correia
Mine is 1.18 and everything is ok. MW 05 is working like a charm for me.
I used 1.18 on WM5 and it worked fine for me. Some persons went back to 1.17 for some reason, I don't know what reasons. I reversed back to WM2003 SE.
powerkite said:
Some persons went back to 1.17 for some reason, I don't know what reasons.
Click to expand...
Click to collapse
Radio version 1.17 has more compatibility with the turning on/off of flight mode in WM5.0.
I am using 1.17 now and so far have not encountered any problems regarding the radio version. Try it! You can revert back to 1.14 anyway
Goodluck
i use 1.08
i currently use 1.18 and it has some serious issues under buzzmobile2005. the tricky thing is, you would not recognize the issues as long as you do not have a dual sim adapter in your device. i have one with two sim cards both pin protected. whenever i soft-reset the device and put in the pin for a certain sim card everything looks fine so far. but after a while taking a look on my device i see that the sim card has been switched an i am booked into my alternative network. i mean it is annoying but no disaster for me. but there is one issue making me feeling uncertain: switching the sim card should result in asking for the alternative sim's pin code. but it skips this step. should not the sim card prevent such access when pin code is activated?
another issue is that after switching flight mode off and on again it often happens that the phone does not switch on. i check the power settings and on the wireless page i see that the phone box is not ticked. i tick it and then tap ok. but whenever i take a look on the settings page the box still remains unticked. it is not always like this, sometimes it works.
maybe this all has to do with the using of a dual sim adapter. switching to 1.17 did not solve the problem, so i switched back to 1.18.
can someone using a dual sim adapter and buzzmobile2005 acknowledge this strange behavior. maybe i am the only one having these issues. thanks a lot.
peter
Here it is a Today Screen plugin that allows the display of the IMSI code (or a custom label for it) of the current active Sim. Works for all dual Sim solutions allowing to always know which is the SIM in use.
From my personal experience I prefer the use of simple power on-off solutions because they consume the same amount of energy of a normal SIM. The digital solutions provide a nice STK application but the resource consumption is not acceptable (especially for HTC Hermes). This plugin solve the main problem of the simple power on off Dual Sim holders: knowing which is the active Sim.
Configure your custom labels in the Today option dialog for the specific item (Dual SIM Today).
Update:
Added menu to switch with a single click between the sim (works only for power on off adapter)
Added the operator name associated to the SIM
Some bugs fixed
Update 1:
Added configuration parameter to:
Activate the display of operator name
Define the Sim switch mode: traditionally with a menu or directly with a tap & hold on the today screen (with the stylus or the scroll wheel)
Some bugs fixed
Update 2:
Added an option to disable the switch functionality
Added the capabilty to open the option dialog directly from the today screen
Update 3:
Direct access to the menu with the action button (or scroll wheel) without menu gesture
Fixed bug in the highlight of the plugin
Update 4:
Fixed bugs in the management of option dialog
Update 5:
Show the last switch time
Update 6:
Fixed operator name redraw
@forum users; help me in setting the priority of the enancements; currently they:
. support for Stk adapter
. support for dialin adapter
. check sim (periodically verify that the right sim is active)
. automatic switch based on specific rules
...
If the tool is useful for you feel free to donate something
.
Pelargonium
Left blank
Some screenshots
Some screenshots for the plugin:
This is sweet! Thanks. Now just need to find a dual sim adapter that is compatible with 3G.
Plugin is brilliant. Ideal for me would be to include it in plugin existing for the Today. I do not understand of programming but I have found this in wiki:
Show Network Operator Name in today screen
Restoring Today Item: WiFi, BT and Phone Connection Status:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Today\Items]Create "Wireless" use Key
"Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
Enable clicking on the today plugin above to open Comm Manager
[HKEY_LOCAL_MACHINE\ControlPanel\WrlsMgr]Create String Value "Redirect"
"Redirect"= "\Windows\CommManager.exe"
Pardon by my English. I am Spanish. Thanks.
not happy
Hi guys
just thought I'd let you know
I've downloaded you sim today program and ran on my hermes but now cant get my phone to work!!
It hangs when trying to load the today screen - I've had to hard reset and start from scratch
As I said NOT HAPPY - beware you may get same probs
Jon
anubus12 said:
This is sweet! Thanks. Now just need to find a dual sim adapter that is compatible with 3G.
Click to expand...
Click to collapse
The one that I use works with 3G (HSDPA too) without problems.
Pelargonium said:
The one that I use works with 3G (HSDPA too) without problems.
Click to expand...
Click to collapse
Do you have a link to the dual-sim adapter you are using?
QtKiguis said:
Plugin is brilliant. Ideal for me would be to include it in plugin existing for the Today. I do not understand of programming but I have found this in wiki:
Show Network Operator Name in today screen
Restoring Today Item: WiFi, BT and Phone Connection Status:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Today\Items]Create "Wireless" use Key
"Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
Enable clicking on the today plugin above to open Comm Manager
[HKEY_LOCAL_MACHINE\ControlPanel\WrlsMgr]Create String Value "Redirect"
"Redirect"= "\Windows\CommManager.exe"
Pardon by my English. I am Spanish. Thanks.
Click to expand...
Click to collapse
I really do not understand your question. Could you please explain it better? The plugin already shows his interface in the Today screen and can be configured in the standard way. Do you want the plugin show the operator name or some other information?
HyperZ said:
Do you have a link to the dual-sim adapter you are using?
Click to expand...
Click to collapse
Sent you via PM
JPW said:
Hi guys
just thought I'd let you know
I've downloaded you sim today program and ran on my hermes but now cant get my phone to work!!
It hangs when trying to load the today screen - I've had to hard reset and start from scratch
As I said NOT HAPPY - beware you may get same probs
Jon
Click to expand...
Click to collapse
JPW, I have your same configuration in term of base software (except for Hermes, mine is an Hermes 200) and it works. Did you tried the plugin immediatly after the reset?
In order to understand what happened can you write details of the problem? when does the hermes hang? during installation, configuration, etc? What other software do you have?
Thanks and sorry for the problem.
Is it specific to Hermes somehow, or should it work on any WM5 device?
Can it be used with multi-SIM SIM cards (like 16-in-one), or it is somehow intended only for (some?) dual-SIM adapters?
Lurker0 said:
Is it specific to Hermes somehow, or should it work on any WM5 device?
Can it be used with multi-SIM SIM cards (like 16-in-one), or it is somehow intended only for (some?) dual-SIM adapters?
Click to expand...
Click to collapse
It is not related to Hermes. It uses standard Windows Mobile APIs. I tested it on Hermes and WM6 (Black 2.0 and 2.5) but it should work on every devices with WM 2003 and up.
The basic plugin should also works for every multi sim card. The functionality to switch the active card is currently working only for power "on off" dual sim card (I'm developing a version that works also for digital dual sim holder).
Pelargonium
Hello, Pelargonium
I enclose a photo to you with which I consider that he would be ideal. To integrate the DualSIm Plugin in the Wireless Plugin, since space is saved.
I have a SIMORE GOLD that works perfectly with the TYTN, although the change I have it to do with menu of own dualsim. The one of plugin does not work to me. I hope to help but that to bother, and again, pardon by my english.
QtKiguis said:
Hello, Pelargonium
I enclose a photo to you with which I consider that he would be ideal. To integrate the DualSIm Plugin in the Wireless Plugin, since space is saved.
I have a SIMORE GOLD that works perfectly with the TYTN, although the change I have it to do with menu of own dualsim. The one of plugin does not work to me. I hope to help but that to bother, and again, pardon by my english.
Click to expand...
Click to collapse
I understand your requirement but the component that you mention (netui.dll) is not customizable. Sorry.
Regarding the sim switch functionality of my plugin, I'm developing a version that works also with digital adapter.
Pelargonium
Hi, I think you're product is great, just what I've been looking for BUT... I'm afraid to say it doesn't quite work. I have an early dual sim adaptor (cut) that requires the phone to be turned off/on to switch. I'm running it on a Orange M600 (prophet) with Jesterz 2.20 rom. Your switcher switches the phone off OK and then back on... BUT it doesn't register on the network.. just gives me a "!" next to the little signal icon. It displays the right number for the sim and all just doesn't fully re-establish the signal. I have also loaded a WM5 version of WIVIT sim switcher (from this group) but as it doesn't allow me to define my own number it's no good. However, when I have WIVIT loaded and on screen, YOUR product works fine.
I would rather just use your product. Any clues on how I might be able to fix this?
Thanks
Dave.
qdavhen said:
Hi, I think you're product is great, just what I've been looking for BUT... I'm afraid to say it doesn't quite work. I have an early dual sim adaptor (cut) that requires the phone to be turned off/on to switch. I'm running it on a Orange M600 (prophet) with Jesterz 2.20 rom. Your switcher switches the phone off OK and then back on... BUT it doesn't register on the network.. just gives me a "!" next to the little signal icon. It displays the right number for the sim and all just doesn't fully re-establish the signal. I have also loaded a WM5 version of WIVIT sim switcher (from this group) but as it doesn't allow me to define my own number it's no good. However, when I have WIVIT loaded and on screen, YOUR product works fine.
I would rather just use your product. Any clues on how I might be able to fix this?
Thanks
Dave.
Click to expand...
Click to collapse
@qdavhen, I tested the plugin only on Hermes with different WM6 Rom, because I don't have other devices. let me test it on the WM5 sdk emulator and I'll give you a feedback.
Thanks Pelargonium,
I've found that after running your program if I go into phone options and select "Find Network" then the phone starts again. I've been doing some digging around and *think* it might have something to do with needing to wait longer between switching off and then back on again... hope this helps.
qdavhen said:
Thanks Pelargonium,
I've found that after running your program if I go into phone options and select "Find Network" then the phone starts again. I've been doing some digging around and *think* it might have something to do with needing to wait longer between switching off and then back on again... hope this helps.
Click to expand...
Click to collapse
Fixed and updated the first post. I've also added the name of the current operator. Please try it and give me a feedback.
Thanks
Pelargonium.
Pelargonium,
Works a treat! Thanks! A couple of small changes that would make this perfect... you have added the operator (eg. O2-UK - 123456789) I would suggest removing the minus sign AFTER the operator and just leave a space. Also rather than tapping and holding and then selecting "switch sim" is it possible to have it switch sim automatically when tapping and holding? These are just small things. Otherwise it is fantastic! Dave.
I'm not sure exactly where this goes, but I think it belongs here and I haven't been able to find any other threads about this issue.
It's going to seem like a WinMo issue, but I'm pretty sure it's Android related.
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Today, I shut down Android (properly) and turned the phone on to return to WinMo. On the 4 digit numeric PIN screen (I Activesync with Exchange at work and this is part of the security requirement; it's not the SIM or GSM PIN), I enter my pin and ... I get an error message that I've entered the wrong PIN and I just used 1 of 8 turns. I tried carefully to enter the PIN to make sure I didn't fat finger the button - strike 2. So, I open the keyboard to try using that, and still no dice. Now I'm worried about getting my device wiped and starting from scratch.
The reason I think this is Android related is that this has happened to me one other time. This problem was the main reason I stopped using BLAZN about 6 months ago. In the almost 2 years that I've had this phone, this hasn't happened when rebooting from WinMo back into WinMo.
Any suggestions or ideas about what's going on? I don't even want to touch my phone without having a plan of attack. My contacts are backed up (first thing I did before I installed FRX06), but would rather not have to re-install stuff if I don't have to.
By the way, until this little incident, Android had been running great - it's been a big improvement over where it was 6 months ago.
Thanks in advance for any help.
-David
LeStone08 said:
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Thanks in advance for any help.
-David
Click to expand...
Click to collapse
I think you need to rename/delete your data.img.
But first you need a real fresh start so don't install FRX06 on top of BLAZN. Delete the old and download the FRX06 package from the thread
Thanks for the reply. Those are some good suggestions in general, but doesn't address my immediate need: Is there any way to get past the PIN check now (maybe the PIN was reset to some default)? Or is there an explanation for what is going on? AS it is, there's nothing I can do with the phone if I don't get the PIN correct (can't reboot into Android).
Also, in order to get FRX06 to work, I did delete the data.img file, so that is fresh. Also, the first time a few months ago, I ran into this problem was on my original (clean) install of BLAZN. Until this problem happened, Android had been working great in most other respects.
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
arrrghhh said:
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
Click to expand...
Click to collapse
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
Normally, I wouldn't think Android would impact my winMo setup. But this has only happened to my twice and both times occured after shutting down Android and rebooting the phone.
No one else has access to my phone - so I can't blame anyone else.
I did install the trial version of Touchdown in my Android installation, but I don't think that's part of the problem (the last time it happened, I used the standard Exchange functionality of Android).
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
LeStone08 said:
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
Click to expand...
Click to collapse
These are questions for your IT dept I would think...
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
I would agree with rpierce99. I use MS Exchange (2007) on both wm & frx06 with password policy enforced and never experienced this issue. I chose to use a 6 digit numeric pin on both OS.
I remember having this issue. Pissed me off beyond belief. Same thing happened, booted out of android, when I tried unlocking, it kept saying the password was incorrect. For some reason I can't remember what I did to fix it... I think I just did a forced hard reset (click reset button, hold send key + end key + power key all at once). I know it's not what you want to hear but hard reset might be the only/quickest fix.
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Raa_1 said:
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Click to expand...
Click to collapse
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
slapshot30 said:
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Click to expand...
Click to collapse
You're right, it wasn't my SIM lock that was causing the problem. I don't remember if my battery was low or dying. I do know that the last thing I had running was the Youtube app that was having problems with buffering a video, then it started getting non-responsive, which was why I decided to shut down my phone and reboot.
I checked with our IT department and besides them trying not to support it because it's not an eye-phone, there were no known MS Exchange changes at our company that would have caused the problem. I did find out that the webmail client for Exchange now shows the clients that connected - I could see a listing for my WinMo install and a couple for my Android install (my original install from 6 months ago, and my current install - the different builds had different system names). There is a feature to request a recovery PIN there, but my HTC Sense simple PIN entry screen didn't have a recovery pin option that's needed - or I didn't see it in the last try I had to get my PIN correct. Maybe I'll play with that more if I start using WinMo again.
My phone did get wiped and so far, I haven't loaded anything back into WinMo - I've been running off my Android install (didn't reinstall - since my SD Card didn't get wiped) for the last 1.5 weeks.
I know it's not a large sample size, but the two times this has happened in the almost 2 year time period that I've had this phone occurred when booting out of Android. I'm glad to hear that I'm not the only one with this issue, but it would be nice to have the problem diagnosed.
I'm hoping that one of the brains doing all of this cool stuff will find the root cause and show us (at least me and Slapshot) how to avoid the problem.
Thanks. I'm still really happy about the state of the Rhodium projects.
Raa_1 said:
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
Click to expand...
Click to collapse
I've never set any type of PIN on my Android phones. What are you setting?
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Raa_1 said:
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Click to expand...
Click to collapse
I'll take your word on the SIM PIN business, as I've never actually set my SIM pin. I wouldn't do this in general, but also especially knowing that there's a conflict between SIM pins and the XDAndroid projects.
In WinMo (I believe there's a way to do this an Android also, but not quite sure), there are two ways that I know of to set up a startup PIN on your phone (at least on my Tilt2):
1) You can go into Settings, Security, Phone Lock: here you can set up your phone to lock itself after a set amount of time. You can use either a Simple PIN or a strong alpha-numeric PIN. Whenever your phone is idle for a time period exceeding the threshold you have set, the phone will lock itself so that you have to enter your PIN to access the phone again. Again, this is not the SIM pin.
2) Some of us work at companies that use this little email package called Exchange by a company called Microsoft . In order to protect employee's and (mostly) company data, some of these companies will leverage security features in Exchange to mandatorily set policies on any mobile devices that want to access the corporate email system. If you want access to the system, you have to accept whatever policies the company chooses to enforce. Some of these policies include: 1) Requiring a PIN (not a SIM pin) on your device; 2) requiring a max idle time before the phone locks itself; 3) requiring a phone reset (including data wipe) after a certain number of missed passwords; 4) allowing a phone wipe/clear on demand in case of theft; etc. My company requires all of these - there are more, but I'm not familiar with all of the options.
When I boot into Windows Mobile, Exchange sees my phone as one device and sets the policies accordingly (basically the email software has to be able to receive the policies and interpret them). When I boot into XDAndroid, Exchange sees my phone as a different device and sends the same set of polices. For my original problem, I set the PIN to be the same for both instances to make like easy for my tiny little brain.
I reiterate that this is not a SIM pin issue. I want to make it clear so we can keep this thread on topic in case anyone else has some insights into the problem. I don't want it to be derailed into a SIM PIN discussion since I'm sure there are lots of threads about that. (Now, I've probably polluted the index with that term and anyone looking for that will find this instead )
I would love to know if anyone gets any insights here.
Thanks for reading.
David
Yes I see what you mean now, and my issue is a different one (SIM not device PIN).
Since your work is issuing device policies, my thought would be it's a policy issue, and quite honestly, I wouldn't try and mess around with a device that's under I.T. direction.
Having said that, i'd likely say your problem is a corrupted WinMo password as Android has nothing whatsever to do with WinMo's side of things. And as mentioned before, it can happen with varying (mainly unknown - grr) reasons why.