Log In
Developer Network
Technologies
Join the Network
Member Services
Events & Community
Java MIDlet API (JMAPI) Developer Center
Overview
Documentation
Community
Wiki
Java MIDlet API Forums
Message Boards Home
Recent Posts
Statistics
Answer
(
Unmark
)
Mark as an Answer
« Back to Technical Discussion
Handheld Phone debug output
Threads [
Previous
|
Next
]
Post New Thread
Russell Mitchell
Posts:
14
Join Date:
10/6/10
Recent Posts
Handheld Phone debug output
Answer
11/3/10 8:25 PM
Mark as an Answer
Submit
Reply with Quote
Quick Reply
I'm looking for a way to store debug output to a file, along with a simple method to retrieve the file from the phone. Is it possible for a midlet to write to the system messages file?
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Russell Mitchell
Posts:
14
Join Date:
10/6/10
Recent Posts
RE: Handheld Phone debug output
Answer
11/3/10 9:43 PM as a reply to Russell Mitchell.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
System.err.println prints to the messages file.
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Vinayak Kagalkar
Posts:
3
Join Date:
9/29/10
Recent Posts
RE: Handheld Phone debug output
Answer
11/4/10 9:25 PM as a reply to Russell Mitchell.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
System.err.println prints to the messages file.
Currently, MIDlet can use
System
.
out
.
println() and system.err.println() to write traces/logs. We do not provide separate API/location to store api. All the ourputs of System.out.println() and System.err.println() goes to device syslog messages Those syslog files can be extracted using device Web intetrface.
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Russell Mitchell
Posts:
14
Join Date:
10/6/10
Recent Posts
RE: Handheld Phone debug output
Answer
11/5/10 1:54 AM as a reply to Vinayak Kagalkar.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
As of a couple hours ago, I'm no longer seeing my System.err.println messages in the system messages file, and for the life of me I can't figure out what I've done wrong. Any ideas on how to get em back?
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Conrad Price
Posts:
11
Join Date:
5/2/08
Recent Posts
RE: Handheld Phone debug output
Answer
11/25/10 1:11 AM as a reply to Russell Mitchell.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
Although a midlet does have some access to storage space in the phone, I don't think that is accessible from the web page for down load. Normally if people want to keep the syslog fils on the phone, you enable the "Preserve logs" setting on the trace settings page, and then any log files would be written to nvram and can be downloaded later
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
David Staudt
Posts:
15
Join Date:
6/4/08
Recent Posts
RE: Handheld Phone debug output
Answer
1/6/11 6:37 AM as a reply to Russell Mitchell.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
By default the phone is configured to reset all tracing (i.e. back to 'error' level), is it possible you reset the phone between tracing sessions? If you so you may need to re-configure tracing and/or make the settings persist.
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Quick Reply
Overview
Documentation
Community
Wiki
Go
By API/SDK:
Select an API
Application eXtension Platform (AXP)
Network Management - Active Network Abstraction (ANA)
Network Management - IP Solution Center (ISC)
Network Management - Network Analysis Module (NAM)
Network Management - Cisco Transport Manager (CTM)
Network Management - Managed Services Management Solution (MSMS)
Cisco Headset/Handset API
Cisco Unified Application Environment (CUAE)
Cisco Unified CM Administration XML (AXL)
Cisco Unified CM Call Detail Records (CDR)
Cisco Unified CM Extension Mobility API
Cisco Unified CM JTAPI (JTAPI)
Cisco Unified CM Log Collection
Cisco Unified CM Performance Monitoring
Cisco Unified CM Real-time Device & CTI Information
Cisco Unified CM Service Control
Cisco Unified CM Servicability XML
Cisco Unified CM SIP (SIP)
Cisco Unified CM SNMP/MIB
Cisco Unified CM TAPI (TAPI)
Cisco Unified CM Web Dialer (WebDialer)
Cisco Unified Communication Express Services Interface
Cisco Unified Presence (CUP)
Cisco Unified TCL IVR/Voice XML API
Cisco Unified Gatekeeper TMP API (GKTMPAPI)
Cisco Unity Connection Provisioning Interface (CUPI)
Cisco Unity Connection Messaging Interface (CUMI)
Computer Telephony Integration (CTI) Server C-API
Computer Telephony Integration (CTI) Server Protocol (GED 188)
Computer Telephony Integration (CTI) Object Server
Contact Center Enterprise/Hosted/ICM IVR PG Protocol (GED-125)
Contact Center Reporting (CCR)
Contact Center TCL IVR/Voice XML API
Customer Voice Portal (CVP)
Enterprise Contact Center Scripting (ECCS)
Enterprise Application Gateway Protocol (AGP)
Hardware eXtension Platform (HXP)
IP Phone Services (IPPS)
Mobility – Cisco Compatible Extensions Program
Mobility – Context-Aware Mobility(Location)
Mobility – Guest Access (GAP)
Mobility – Solution Verification
Meetingplace SOAP API (MPSA)
Smart Business Portal (SBP)
Unified Contact Center Express CTI (UCCXCTI)
WebEx - Connect
WebEx - Meeting Services