377
Appendix/Troubleshooting
Error messages
If error message appears mentioned below
・
The "(number)" or "(xxx)" in error messages is a code used to distinguish the error sent from i-mode Center.
●
All locked.
All lock is ON.
→
P100
●
Apply secret attribute to mail address and SMS?
This message appears when external phonebook
entries with secret attribute set are loaded or when
secret attribute is set for phonebook entries.
→
P108
●
Authentication type is not supported.(401)
The authentication type is not supported and
connection to the specified site or website is
disabled.
●
Call cost reached limit. Call disconnected./Call cost
reached limit. Call on-hold disconnected./Call cost
already reached limit. Unable to call.
Reset the total calls cost.
→
P300
●
Cannot execute because of other tasks.
When updating pattern data, terminate all other
functions in advance.
●
Caution! This SMS includes Phone Nos. or URLs. Be
careful if you do not recognize the sender.
With Message scan of Set scan set to "Valid", you
make an attempt to display SMS containing a phone
number and/or URL description. (It does not appear
when mopera mail or voice mail reception
notification is received in SMS.)
●
Certificate is rejected.(tampered)
The site certificate has been altered. Connection is
suspended.
●
Cessation of broadcast.
The selected channel is stopped.
●
Check address.
An incorrect or no mail address was input to the mail
group.
●
Check SMS center setting.
Setting of SMS Center in SMS settings is incorrect.
→
P150
●
Connection failed.(403)
Failed to connect to the site for a certain reason such
as connection rejection.
●
Connection failed.(562)
Failed to connect to the i-mode Center. Please retry in
a place with good radio wave conditions.
●
Connection interrupted.
Please retry in a place with good radio wave
conditions. If the error persists, retry later.
●
Content length exceeds maximum size for i-motion.
Download has suspended because the data exceeds
savable size while downloading i-motion.
→
P172
●
Continue using i-
α
ppli and transmit data? Yes/
Terminate i-
α
ppli
After "Data transmission is frequent. Continue
transmission?" appears, an attempt was made by i-
α
ppli to make communications.
●
Corrupted data or microSD.
Accessing microSD card is disabled due to a problem
in data saved in the microSD card or the card itself.
Install a new microSD card, or format or restore the
data.
→
P269, 275
●
Corrupted data or microSD. Saving to phone
memory.
When "microSD" is the destination for saving still
images or movies and the microSD card cannot be
accessed, the destination automatically switches to
"Phone".
●
Corrupted data.
i-
α
ppli cannot be started from invalid data read with
Bar code reader.
●
Corrupted data. Restore default setting?
Functions cannot be started until selecting "Yes" to
return the default setting.
●
Current UIM is not registered as IC owner.
Unable to run/download/update.
Details are given in IC owner in Osaifu-Keitai Menu
This message appears when UIM is replaced after
registering as IC owner and an attempt is made to
download, update or activate Osaifu-Keitai
compatible i-
α
ppli.
→
P247
●
Data in IC card is full. Unable to run/download/
update. Delete service?
Memory space in IC card is insufficient when starting,
upgrading or downloading Osaifu-Keitai compatible
i-
α
ppli. Delete data from IC card according to
instructions on the screen and delete the Osaifu-
Keitai compatible i-
α
ppli.
→
P240
●
Data transmission is frequent. Continue
transmission?
This message appears when communications using
i-
α
ppli are made very frequently in a predetermined
period of time. Select "Yes" to continue using, "No" to
continue without communications or "Terminate i-
α
ppli" to stop.
●
Delete software and IC card data?
Osaifu-Keitai compatible i-
α
ppli which also deletes
data in the IC card is included in the i-
α
ppli. Select
"Yes" to delete the i-
α
ppli and the data in the IC card.
Summary of Contents for F-08A
Page 256: ......
Page 328: ......
Page 344: ......
Page 362: ...360 Appendix Troubleshooting Pictogram Reading Pictogram Reading...
Page 363: ...361 Appendix Troubleshooting Pictogram Reading Pictogram Reading...
Page 364: ...362 Appendix Troubleshooting Pictogram Reading Pictogram Reading...
Page 365: ...363 Appendix Troubleshooting Pictogram Reading Pictogram Reading...
Page 400: ...398 MEMO...
Page 401: ...399 Index Quick Manual Index 400 Quick Manual 408...