jp.co.ricoh.isdk.sdkservice.function.print.AsyncJobEvent.JOB_EVENT not triggering
Incident Properties
Question
I am successfully tracking Copy, Scan & Fax JobEvents with the following AndroidManifest.xml entries
<receiver
android:name="jp.co.ricoh.ssdk.softlog.app.auth.tracking.SoftlogJobEvent"
android:permission="jp.co.ricoh.isdk.sdkservice.common.SdkService.APP_EVENT_PERMISSION"
android:exported="true">
<intent-filter>
<action android:name="jp.co.ricoh.isdk.sdkservice.function.copy.AsyncJobEvent.JOB_EVENT" />
<action android:name="jp.co.ricoh.isdk.sdkservice.function.scan.AsyncJobEvent.JOB_EVENT" />
<action android:name="jp.co.ricoh.isdk.sdkservice.function.fax.AsyncJobEvent.JOB_EVENT" />
<action android:name="jp.co.ricoh.isdk.sdkservice.function.print.AsyncJobEvent.JOB_EVENT" />
</intent-filter>
</receiver>
This is for Copy, Scan and Fax jobs generated by the user on the copier.
However the print.AsyncJobEvent.JOB_EVENT never triggers for print jobs that are submitted external to the copier, e.g. Windows print jobs from a users desktop.
Is this expected behaviour or are extra settings needed?
nb.
DETECTION_EVENT events *do* trigger for external print jobs
Thanks - Lindsay
SmarkSDK App Evaluation Testing
Incident Properties
Question
Hi,
We have been reviewing the SmartSDK AppEvalSpec documentation. There are a number of testing requirements that need to get completed for application approval. We would like to ensure that we meet the requirements in order to streamline the testing and ensure that we understand the document. There are a number of questions that we did have regarding the document. Would you be able to provide some additional guidance on the following:
Common Test Items:
- 'Confirm that the SmartSDK application can be installed' – The procedure mentions installing the application according to the "delivery type." Could you please explain what "delivery type" refers to? Additionally, I need guidance on how to install the SmartSDK application and would appreciate specific installation steps or a guide on what I should do. Also, once the application is installed, how can I confirm that the installation was successful?
- 'Confirm the lock and release of the transition to offline mode functions correctly' – I need guidance on how to verify the conditions specified in the procedure, particularly if these checks are done at the system level (via the Smart Operation Panel or device settings) or if code-level handling is required. For Step 4, where it’s confirmed that "the SmartSDK application is locking the mode transition," how can I verify this? Similarly, for Steps 5, 6, and 7, where it confirms actions like buzzer feedback, offline mode prevention, and whether the application is locking offline transitions, how can I confirm these conditions? If code-level handling is required, could you please guide me on where I can find the relevant instructions or code to perform that handling?
- 'Shut down to reboot, and confirm that the application runs correctly' – The procedure mentions “Using the application, perform operations involving the following processing: Perform processing accessing HDD.” Could you clarify which specific operations should be performed that involve accessing the HDD? Are there particular tasks in the SmartSDK application that require HDD access? Your guidance on this would be greatly appreciated.
Print Test Items:
- 'Confirming paper jam detection in the SmartSDK application' – I have a couple of questions regarding Step 1 and Step 3. In Step 1, the test mentions that the "Status Check LED is turned off." Is this LED part of the device settings, Smart Operation Panel, or should it be handled within the SmartSDK application? If it’s handled in the application, where can I find the instructions for this in the code? In Step 3, the test condition says “The error status other than paper jam does not occur.” How can I check for error statuses, and should this be handled at the code level? If so, where can I find the necessary instructions? Also, the confirmation mentions that “The Status Check LED turns on, and the alert is processed according to the application specification.” Should this be managed through the application code or handled automatically by the device/panel?
- 'Confirm that paper jam is detected and handled when the SmartSDK application is not the screen owner' – The procedure mentions that the “native scanner screen is visible and print job of SmartSDK application is still executing.” Could you clarify what is meant by “native scanner” and how to confirm that the native scanner screen is visible while the SmartSDK print job is still executing? Also, could you explain what is meant by ‘when the SmartSDK application is not the screen owner’? Does this mean the device or another application takes control of the screen while the SmartSDK application is still managing the print job? Any guidance on how to verify this would be helpful.
- 'Confirm that paper shortage is detected and handled appropriately' – In Step 2, the procedure mentions “Limitless print is not performed” and instructs to set a paper size different from the configuration. How should I handle this — should I manually set a different paper size via the SmartSDK application or through the device settings? In Step 3, it says “The target feeder tray becomes empty.” How can I confirm the tray is empty, and should this be checked through the SmartSDK application, device settings, or the Smart Operation Panel? Also, how can I verify that “the error status other than paper empty does not occur,” and if it requires code-level handling, where can I find the necessary instructions?
- 'Confirm that paper empty is detected and handled appropriately' – I have a question regarding Step 4. The confirmation mentions that I need to “Confirm that alert process according to application specification is taken.” Could you clarify what this means, and how and where I should confirm that the alert process is being handled according to the application specification? Should this be verified in the SmartSDK application, Smart Operation Panel, or elsewhere? If it needs to be handled at the code level, could you guide me on where to find the instructions to manage it?
- 'Confirm that toner shortage is detected and handled appropriately' – I have a few questions regarding the test conditions. The procedure mentions that “Some device becomes 'Unit not set correctly' status at this point,” and that “Evaluation of this evaluation item is not necessary when a 'Unit set defect error' occurs.” Could you clarify what "Unit set defect error" refers to, where I should look for this error, and how to handle it if it occurs? Also, in Step 2, the test condition states “Errors, e.g. 'Unit not set correctly', do not occur.” How can I confirm that such errors do not occur? Additionally, if code-level handling is required for any of these issues, where should I look, and where can I find the instructions to handle them?
- 'Confirm that feeder tray not set is detected and handled appropriately' – I have a question regarding the confirmation in Step 2. The procedure mentions that I need to “Confirm that the Status Check LED turns ON, and Printer feature becomes unavailable.” Could you clarify where and how I should check for this? Should this be verified through the SmartSDK application, Smart Operation Panel, or device settings? Also, how can I confirm that the Printer feature becomes unavailable when this happens? Is there any code-level handling required for this, and if so, where can I find the instructions to handle it?
- 'Confirm that unsupported print service necessary can be detected and handled appropriately' – I have a few questions. In Step 2, the test condition mentions “Request print of file type not supported by print service.” Could you clarify how the SmartSDK application detects unsupported print file types and handles them? How should I confirm that the application correctly notifies the user when attempting to print an unsupported file? Additionally, the procedure mentions “Confirm that SmartSDK application detects the print service does not support the file type beforehand.” How can I verify that this detection process works as expected, and what should I look for in the SmartSDK application or device settings to confirm it? If code-level handling is required, where can I find the necessary instructions to implement this?
Scan Test Items:
- 'Confirm that scanning is proper in platen mode' – I just want to confirm if any code-level handling is required to pass this test. If yes, what exactly needs to be handled and where can I find the relevant documentation or guidance?
- 'Confirm that scanning is proper in ADF mode' – I just want to confirm if any code-level handling is required to pass this test, specifically for detecting no originals beforehand with notification, and for ensuring originals are fed one at a time from DF/ADF and properly scanned. If yes, what exactly needs to be handled and where can I find the relevant documentation or guidance?
- 'Confirm that paper jam at the original scan is detected and handled appropriately' – I want to confirm how to verify the test conditions and confirmations, specifically regarding checking the Status Check LED status (on/off), ensuring ADF is loaded with originals, confirming no error status other than paper jam occurs, and handling alerts for paper jam errors. Also, is any code-level handling required to detect and manage these states in the SmartSDK? If yes, please guide me on what exactly needs to be done and where I can find the relevant documentation.
- 'Confirm that DF door open is detected and handled appropriately' – Could you please guide me on how to verify the test conditions and confirmations related to the Status Check LED behavior, error handling for cover open, and paper jam alerts? I also want to confirm if any code-level handling is required. If so, please guide me on how it should be implemented and where I can find the related documentation or instructions.
- 'Confirm that no original is detected and handled appropriately' – The test mentions conditions and confirmations for scenarios when no original is set on the platen or DF/ADF. Could you please guide me on how these confirmations (like "no original alert" display and retry/cancel behavior) can be verified? Also, is any code-level handling required for these behaviors? If yes, please guide me on how to implement that and where I can find the related documentation or instructions.
Fax Test Items:
- 'Confirm that transmission is possible by any of the G3/G4/IP fax lines' – The procedure mentions confirming that the “Communicating” LED turns on at the start of transmission, checking the result in the standard fax application's result screen (including date, destination, number of pages sent, etc.), and ensuring the image is received properly by the receiving device. I want to confirm how these points can be verified through the SmartSDK. Are there any APIs, logs, or UI outputs available to check the LED status and transmission results? Also, is any code-level handling required for this? If so, please guide me on how to implement it and where I can find the related documentation. Additionally, could you clarify what is meant by the “standard fax application” in this test?
- 'Confirm that transmission can be canceled' – The procedure mentions confirming that the transmission cancel result can be obtained and that the receiving device has not received the document, across G3, G4, and IP fax lines. Could you please clarify how to confirm these points using the SmartSDK? Specifically, is there any API, log, or UI indication that shows the cancel result? Also, how can I verify on the receiving device side that the document was not received? Is any code-level handling or event listening required to detect or manage transmission cancellation? If so, please guide me on how to implement this and where to find related documentation. Additionally, are there any status LEDs or indicators related to cancellation that need to be checked, and how can those be accessed or handled via code?
- 'Confirm that fax undelivered message can be handled' – The procedure mentions confirming that the SmartSDK application detects fax transmission failure, shows an undelivered alert according to the application specifications, and allows successive operations to be performed properly. Could you please explain how to confirm these items? Specifically, how can I detect fax transmission failure and display the undelivered alert? Are there specific APIs, events, or UI elements I should check? How should the application handle successive operations programmatically after a failure? Is any code-level handling required to manage these cases? Also, how do I verify that the fax cable is unplugged? Are there status LEDs or other indicators that need to be monitored at the code level? Please provide guidance on implementing and testing these features effectively.
- 'Confirm that reception is available by G3, G4, IP fax, and Internet fax' – Could you please clarify how to confirm that the SmartSDK application properly receives fax reception notifications and correctly imports reception information, are there specific APIs, events, or UI elements to monitor for these confirmations? Also, how can I verify that successive operations proceed properly according to the application’s specification, does this require any code-level handling or event listening? For applications supporting deleting received documents, how can I confirm the delete operation functions correctly within SmartSDK? Since the test involves different line types such as G3, G4, IP fax, and Internet fax, are there any line-specific handling or configuration details I should consider? Additionally, the test mentions status LEDs or indicators related to fax line status, where and how can these be checked both physically and programmatically? Is there any need for code-level handling to monitor these status indicators or manage related events? Please guide me on the best approach to implement and verify these points thoroughly.
Memory Test Items:
- 'Confirm that the application can retrieve a file even if the power is turned off while reading a stored file' – The procedure mentions turning the main power off and on during file acquisition and confirming that the SmartSDK app starts normally and the file is acquired correctly. Could you please clarify how to confirm these points using SmartSDK? How can I detect recovery after power off and on and verify file acquisition success? Are there specific APIs, events, or UI elements to monitor? Also, how should the app handle cases when the main power cannot be turned off during acquisition? Is code-level handling required for these scenarios, and if so, how should it be implemented? Where can I find guidance or documentation for this? Finally, could you clarify which device’s main power is referred to in this test? Are there any status LEDs or indicators related to power or file acquisition that need monitoring physically or programmatically? Please advise on the best way to implement and verify these features.
- 'Confirm that the application can delete a file even if the power is turned off while deleting a stored file' – The procedure mentions turning the main power off and on during deletion and confirming the app restarts normally and the file is deleted as specified. Could you clarify how to confirm these using SmartSDK? How can I verify recovery after power cycling and confirm file deletion? Are specific APIs or events involved? Also, if the main power cannot be turned off during deletion, is code-level handling needed? Where can I find guidance on this? Are there status LEDs or indicators to check physically or programmatically? Lastly, which device’s main power is referred to here?
- 'Confirm the application can retrieve a file even if the screen is switched to the [User Settings] screen' – The procedure mentions retrieving the stored file while switching screens and confirming the file is correctly retrieved and available in the SmartSDK application. Could you please clarify how to confirm this behavior during testing? Are there specific APIs or events to verify file retrieval across screen changes? Also, is any code-level handling required to maintain the retrieval process when switching screens, and where can I find guidance on that? Additionally, are there any status LEDs or indicators to check physically or programmatically during this test? Lastly, any tips on how to perform this task effectively would be appreciated, as I currently don’t have a clear idea.
- 'Confirm the application can delete a file even if the screen is switched to the [User Tools] screen' – The procedure mentions deleting stored files and handling conditions like HDD being full, with alerts displayed when no more files can be stored. Could you please clarify how to confirm these behaviors during testing? Specifically, how to verify file deletion and alert display? Also, is any code-level handling needed to manage file deletion or alerts when switching screens, and where can I find guidance on that? Additionally, are there any status LEDs or indicators to check physically or programmatically during this test? I’m not sure how to perform this task and would appreciate any advice.
- 'Confirm that power mode transition does not occur while HDD is used' – The procedure mentions confirming that Sleep mode transition is rejected when accessing the HDD, and checking touch panel light, power LED behavior, and recovery when not accessing the HDD. Could you please clarify how to confirm these conditions during testing? Specifically, where and how to verify the Sleep mode rejection and LED status? Also, is any code-level handling required to manage power mode transitions or LED status, and if so, where can I find guidance for that? I’m not sure how to perform this task and would appreciate your advice.
- 'Confirm that Offline mode transition does not occur while HDD is used' – The procedure mentions starting the SmartSDK application, accessing HDD, entering configuration mode via [System Settings], and pressing keys. How do I confirm that the Offline mode transition happens properly when HDD is not accessed? Also, when HDD is accessed, how can I verify that the buzzer beeps on key press and the device does not switch to Offline mode? Where should I check these confirmations? Are there specific UI indicators, logs, or hardware signals like LEDs or buzzers? If any code-level handling or logging is required to detect or prevent Offline mode transitions during HDD use, could you please provide guidance or examples? I am unsure how to perform these checks and would appreciate your support.
- 'Power mode (the engine turned off) does not have side effects' – The test procedure involves starting the device and SmartSDK app, switching to Sleep mode, verifying that the touch panel turns off and the power LED flashes slowly, recovering to the Home screen by touching the panel, and performing HDD operations. How can I properly confirm each of these steps? Specifically, where should I check for the touch panel and power LED status? Are there any UI indicators, logs, or hardware signals to observe? If code-level handling or logging is required to detect or manage these power mode transitions and HDD operations, could you please provide guidance or examples? I am not sure how to perform these confirmations and would appreciate your support.
Network Test Items:
- 'Confirm operation after the network setting is changed' – The procedure involves operating with network functions, changing the device’s IP address via system settings, and verifying operations before and after the change. How do I confirm that the operations are processed properly both before and after the IP address change? Also, how can I verify that the device’s IP address has actually changed as expected? Are there specific UI screens, logs, or network commands I should use for these confirmations? If any code-level handling or monitoring is required to detect or manage network setting changes within the SmartSDK, could you please provide guidance or examples? I’m not sure how to perform these checks and would appreciate your support.
Concurrence Test Items:
- 'Confirm that SmartSDK Application does not affect Web Image Monitor feature of the device' – The procedure involves checking Web Image Monitor access when the SmartSDK app is both the screen owner and not. Could you clarify whether the app should be launched locally or via the remote panel, and how we confirm its screen ownership state during the test? Also, should the proxy settings be handled only in the browser, or is any SDK-side configuration involved? For both ownership states, where exactly in the Web Image Monitor should we check to confirm the correct device status is displayed? And if any code-level handling is required to avoid conflicts or ensure proper visibility, where in the sample app or documentation can we find the relevant handling or references?
- 'Confirm that SmartSDK Application does not affect SNMP feature of the device' – This test requires verifying the SNMP status through the print queue monitor when the SmartSDK application is both displayed and not displayed. Could you please advise where the SmartSDK app should be launched, whether locally on the device or via the remote panel, and how to determine when it is considered not displayed? Additionally, could you guide me on how and where to access the print queue monitor to check the SNMP status and what specific device configuration we should verify or adjust during this test? If any code-level handling is necessary to ensure accurate SNMP reporting, please direct me to the relevant implementation or documentation within the SDK or sample application.
- 'Confirm that SmartSDK Application does not affect FTP feature of the device' – The procedure describes starting FTP printing from the Windows command prompt by specifying the device IP and logging in either as “anonymous” or as a user with print permission. Could you clarify where I should obtain the necessary FTP user credentials? Also, the confirmation step requires verifying that the test file prints correctly. Where and how should this be confirmed? The test involves checking FTP printing when the SmartSDK app is both displayed and not displayed on the device or via remote connection. Could you provide guidance on how to perform this test properly, including how to access the FTP print functionality and what device configurations need to be checked? Lastly, if any code-level handling is required to ensure FTP printing works correctly alongside SmartSDK, could you direct me to the relevant implementation or documentation?
- 'Confirm that SmartSDK Application does not affect the feature to store image from client PC on the Document Server of the MFD' – The procedure involves printing from Notepad and Word using the “Document Server” job type and specifying a User ID. Could you please clarify where to set or obtain this User ID and any required credentials? Also, how should we confirm that the document is properly stored on the Document Server and later printed correctly? The test covers both when the SmartSDK app is displayed locally and when it is not or accessed remotely. Could you guide me through the correct way to perform these steps, and let me know if any specific device settings need to be checked? Lastly, if any code-level handling is necessary to ensure proper storage or printing integration, where can we find the relevant code or documentation within the SDK or sample apps?
- 'Confirm that SmartSDK Application does not affect LPR print feature of the device' – The test involves performing LPR printing from a Windows client PC while the SmartSDK application is either displayed or not displayed on the device. The prerequisites mention adding an LPR port through Windows settings, but could you clarify what specific port needs to be configured for this test and where to obtain the required port information? Also, is the LPR port setup described in the prerequisite sufficient on its own, or are there any additional configuration steps required before performing the test? How should we confirm that the LPR print job has completed successfully? Lastly, if any code-level handling is required to avoid interference with LPR printing, where can we find the relevant implementation or documentation?
- 'Confirm that SmartSDK application and other concurrent scanner operations perform properly under high load' – The test involves running scan jobs via SmartSDK application while simultaneously performing tasks such as printing many images to “Store to Document Server,” printing from the prior tray (PostScript if possible), receiving numerous fax originals in small or micro letter mode, and rotating paper in the prior tray for continuous printing. The test requires using the maximum number of originals or image files with varied sizes, settings, and color types to generate a high load. Please advise on how to set up and execute these operations, prepare the necessary files, confirm successful completion without errors, and if any code-level handling is recommended, kindly point me to relevant documentation or code examples.
- 'Confirm that operation using Scanner is unavailable from standard embedded or native applications when SmartSDK Application is using Scanner' – I need your guidance on a few points. The test refers to a native or standard application using the scanner feature. Could you clarify what this application refers to and where it can be accessed? Also, during scanning via the SmartSDK Application, how is access blocked or restricted from other applications, and what triggers the buzzer or message alert mentioned in the confirmation? If any code-level handling is required for managing conflicts or switching between scanner operations, please advise where to find the related code or documentation.
Authentication Test Items:
- 'Confirm the screen is displayed correctly according to the display control' – I want to confirm whether the actions mentioned, such as pressing the "Status Check" key, "Home" key, "Stop" key, and Login button, should be done through the Smart Panel operation accessible via the remote panel. Also, I’d like clarification on how to observe the screen transitions, where to check for the expected behavior, and if any code-level handling is necessary, where can I find the relevant information to implement it? I’m not sure how to perform these checks and would appreciate your guidance.
- 'Confirm that user login/logout from the operation panel can be executed' – The procedure mentions performing the login and logout actions, including handling auto logout based on the configured settings. I’m unsure how to confirm these actions, specifically where the login and logout screens should appear, and how to validate the behavior when the device is idle or when the auto logout is triggered. Could you confirm that these actions should be done through the Smart Panel operation, accessible via the remote panel? Additionally, if any code-level handling is required for these steps, where should I look or make the necessary adjustments? Could you guide me on how to perform these checks and what code-level changes might be needed to handle these actions correctly? Thank you for your support.
- 'Administrator login/logout can be executed' – The procedure mentions performing login and logout using the administrator's credentials, accessing the User Tools icon, and confirming that the application enters and exits the logout state. I'm unsure where exactly these actions should be performed, whether on the Smart Panel accessed via remote access, and how to confirm that the login/logout was successful. Also, if any code-level handling is required for detecting logout state or enabling login/logout functionality, could you guide me on where those changes should be made and where I can find the relevant reference code in the SmartSDK or related documentation? Your support in clarifying how to perform and validate these steps would be appreciated.
- 'Login to/logout from Web Image Monitor can be executed' – The procedure includes opening a web browser, entering the IP address of the test device to access the Web Image Monitor, and performing login and logout actions using registered user credentials, as well as checking login failure with incorrect or unregistered users. I’m unsure how to confirm whether these actions are successful or failed, and how to verify that the login screen or failure messages are correctly displayed. Also, could you please confirm where to find the correct IP address to use in this test and if any specific configuration is required on the device beforehand? I would appreciate your guidance in understanding how to perform and validate this test correctly.
- 'Login/logout from remote can be executed' – The procedure involves executing print jobs from a computer on the same network as the MFP with various authentication cases like correct credentials, wrong passwords, and unspecified user IDs. I’m unsure how to confirm whether the print job is executed or canceled in each case and where to verify these results on the device or interface. Also, could you confirm if “remote” here means remote panel operation accessed via the Web Image Monitor? Additionally, if any code-level handling is required to support remote login or print job authentication, please advise on what to implement and where to find related reference code. Your guidance on how to perform and validate this test would be greatly appreciated.
- 'Authentication can be performed with a card' – The procedure mentions test conditions involving the authentication app’s login screen and card reader actions such as unregistered cards, registered cards, and login failures. I’m unsure how to perform these tests, where and how to use the card reader, and how to confirm alerts like "card not registered" or "login fails." Where should I look to verify these behaviors on the device screen, Web Image Monitor, or elsewhere? Also, if any code handling is needed, where can I find the relevant code? Please provide guidance as I have no experience with these card reader tests.
- 'Tracking and upper limit control functions are enabled' – The procedure includes registering a user, performing copy and print jobs, and checking job records via the tracking collection system. I’m not sure what this tracking collection system is or how to access it to confirm proper data collection after logout. Also, I need help understanding how to set and reset the printing upper limit for copying – should this be done on the printer’s operation panel or through remote panel access using Web Image Monitor? Additionally, how can I verify that copy jobs are blocked when the limit is reached and allowed again after resetting? Since I am unfamiliar with this test, I would appreciate your detailed instructions on how to carry it out and information on whether any SmartSDK code changes are needed, as well as where to locate the related materials.
- 'Authentication state is properly controlled after rebooting the operation panel or only main machine' – The procedure involves installing an application that triggers a reboot via Web Image Monitor or remote tools, with login/logout confirmation checks afterward. I’m not sure how to validate these behaviors or what exactly should happen during reboot. I also don’t know whether the SmartSDK needs to handle this through specific settings like need_reboot, or where to check this in the sample code. Could you please guide me on how to proceed, how to confirm the expected results, and where to find the relevant documentation or examples?
Home Key Test Items:
- 'When the Home key assignment function [general mode] is active, confirm that each key works effectively' – I’m unclear about the meaning of the “Home key assignment application” and the phrase “Flicker does not occur at screen transition.” Could you please explain what these refer to, how to confirm them during testing, and if any code handling is required, then where to find what that is? Also, I don’t know how to perform this test and would appreciate detailed guidance on the steps involved. Thank you for your support.
- 'When the Home key assignment function [UI change mode] is active, confirm that each key works effectively' – The procedure includes confirmations such as “The Ricoh Home screen is displayed,” “The screen of the Home key assignment application is displayed correctly,” and “Flicker does not occur at screen transition.” Could you please explain how to confirm these points during testing and what exactly is meant by “Home key assignment application” and “Flicker” in this context? Also, if any code-level handling is required to pass this test, could you guide me on where to implement it or where to find related documentation? I don’t have prior experience with this test and would appreciate detailed guidance on how to perform it. Thank you for your support.
Resource Test Items:
- 'Check whether repeating screen switching and application switching causes any memory leaks' – The procedure involves launching the SmartSDK app, using the DeveloperTool to collect memory usage, switching between the Home screen and the SmartSDK app repeatedly, and then reviewing memory metrics like PSS Total and Dalvik Heap. I’m not sure how to confirm these steps—such as where to see the memory data, how to determine if a leak is present, or whether I need to handle anything in the code to support this. I need guidance on how to properly carry out this test, what to check to confirm there’s no memory leak, and whether any code-level support or logging is needed.
- 'Confirm that continuous operation of normal process does not cause memory leak' – The procedure involves starting the SmartSDK app, using the DeveloperTool to collect memory usage data, repeatedly switching screens and performing operations, then checking whether the memory consumption is saturated to rule out memory leaks. I’m not sure how to confirm that memory saturation has been achieved, where exactly to observe this in the DeveloperTool output, and whether any code-level logging or monitoring needs to be implemented to support this test. Could you please guide me on how to validate each step correctly and let me know if any changes are required in the application code to help with confirming memory stability?
- 'Confirm that the application neither accesses the HDD nor writes on NAND' – The procedure refers to the "Operation Manual HwAccessCheck for SmartSDK application" for detailed testing steps and confirmation criteria. Could you please let me know where I can find or access this manual? Additionally, I’m unsure how to perform this test properly and would appreciate more detailed guidance. Also, is there any code-level handling required for this test? If so, could you please provide guidance on what needs to be done and where I should check or implement such handling? Thank you for your support.
Image Trimming Test Items:
- 'Check that image trimming feature can be used properly' – The procedure mentions performing image trimming on a selectable trimmable image file and confirming that the trimmed image is saved to the specified destination. Could you please guide me on how to perform this test? Specifically, how do I select a trimmable image file and verify that the trimmed image is saved correctly? Are there UI indicators, logs, or code-level handling I should check? If any code-level handling or logging is required to confirm or support this feature, could you please provide guidance or examples? I would appreciate your detailed support as I am unsure how to proceed.
- 'Check that image trimming feature completes properly' – The procedure mentions selecting a trimmable image file and confirming that the trimmed image is saved in the specified destination. How can I confirm these steps? Are there specific UI indications, logs, or code-level checks I should use? Also, how do I verify that the device enters sleep mode with the touch panel light off and the power LED blinking slowly, then returns to the home screen and restarts the SmartSDK application properly? I don’t have much experience with these tasks, so detailed guidance or code examples would be appreciated.
- 'After using image trimming feature, check that it does not affect power mode transition control in the device' – The procedure includes performing image trimming, confirming that the trimmed image is saved in the specified destination, putting the device into sleep mode (where the touch panel light turns off and the power LED blinks slowly), waking the device, and ensuring that the SmartSDK application resumes and continues properly. How can I confirm each of these steps? Are there UI indicators or logs I should rely on, or are code-level hooks or event handlers required to track and handle these transitions? If so, where and how should I implement them using Ricoh’s SmartSDK? I’d appreciate guidance on how to perform this test accurately.
- 'After using image trimming feature, check that it does not affect application offline mode transition control of the device' – The procedure involves starting the SmartSDK application, performing image trimming using a trimmable image file, confirming that the trimmed image is saved in the specified destination, and navigating to the System Initial Setting Screen via the device’s panel. I’m not sure how to confirm these steps in practice, such as verifying that trimming completes successfully or whether it impacts the device's offline mode behavior. Where should these confirmations be checked in the application or on the device? Do I need to handle anything in the code using SmartSDK to support or verify these actions? If so, please guide me on what needs to be implemented and how I can test and confirm it accurately.
Media Access Test Items:
- 'Check if SD card is accessible' – The procedure states that the SD card should be inserted into the media slot and confirmed as mounted, followed by checking whether the application can read and write to it. Could you confirm if any code-level handling is required to detect the SD card insertion or to access its contents? If so, where can I find the relevant implementation or sample code that demonstrates how to handle these operations?
- 'After accessing the SD card, check if the SD card can be removed from the media icon in the system banner' – The procedure mentions removing the SD card from the media icon once the application is not accessing it, and confirming the card is removable. Could you please clarify how the system detects that the SD card is safe to remove? Does this require any specific code-level handling? If so, could you point me to the relevant implementation or sample code?
- 'After accessing the SD card, check if the device can transit to the power mode' – The procedure includes mounting the SD card, verifying read/write access, then pressing the Energy Saver key to stop SD card access, followed by checking the operation panel light and power LED status. Could you clarify if any code-level handling is required to properly release the SD card before switching to power mode? If so, please point me to the relevant code or documentation. Also, how is the device detecting when it is safe to enter power mode after SD card use?
- 'While accessing the SD card, check that the access ends when an application goes to the background' – The procedure explains that when the app is accessing the SD card and the Home screen button is pressed, access to the card should be canceled. I’d like to ask if any code-level handling is required to detect the transition to background and release the SD card properly. If so, could you point me to the relevant implementation details or sample code?
- 'While accessing the SD card, check that the access ends when the device shuts down' – According to the procedure, when the device’s main power is turned off while the application is accessing the SD card, the access should be properly terminated. I’d like to ask whether any specific shutdown or cleanup handling is needed in the application code to ensure the SD card is safely released in this situation. If such implementation is required, could you please advise where to find the related documentation or provide a sample for reference?
Servlet Test Items:
- 'Make sure that Servlet starts' – The procedure involves starting the device and accessing the target Servlet URL from an external device like a PC. How can I confirm that the target SmartSDK application has a Servlet properly installed and running? Also, how do I verify that the response returned from the Servlet matches the expected specifications? Are there specific tools, logs, or UI elements to check this? If any code-level handling or monitoring is needed to ensure the Servlet starts and responds correctly, could you please provide guidance or examples? Actually, I don’t have much idea about how to perform these checks and would really appreciate your support.
Device is not able to initiate the connection back to the server after network Outage
Incident Properties
Question
Hi Team,
We are facing a continuous loader issue on some printers present in a network after network outage. The printers are not able to initiate a connection back to the server. There are some other printers which are able to connect to the same server. We can see through the developer tool logs that it is calling health check URL repeatedly with multiple reset events occuring.
Attaching the developer tool logs from the non working device.
It looks like it might not be network issue, please confirm if that is the case. Also, Please let us know what suggestions you have.
USB Tracking Issue on IMC3510
Incident Properties
Question
I would like to reopen the below ticket:
Subject: USB Tracking Issue on IMC3510
Incident ID#: 5547
USB Tracking Issue on IMC3510 | Ricoh Developer Program (RiDP)
Earlier RiDP has suggested to reach out to https://www.ricoh-usa.com/en/support-and-download/contact-us#customersupport for further information and support about Factory applications.
Please see the below response from Ricoh USA. And also, could you please raise this to the Hardware Engineering team ASAP?
Thanks for the clarification, I am not sure who provided you with that information, but it is incorrect . RiDP would reach out to the Hardware Engineering team they have a direct line. I do not support native applications of the MFD.
Benny Lastella
Engineer II, Problem Management. Centralized Services
Escalation and Problem Management. Software Engineering
RICOH Digital Services
Ricoh USA, Inc.
Hotline - 888-424-1573 option 2, 1
From: Krishna Chaitanya <krishna.chaitanya@kofax.com>
Sent: Monday, July 14, 2025 9:41 AM
To: Benny Lastella <benny.lastella@ricoh-usa.com>
Cc: Rajesh Nagwekar <rajesh.nagwekar@tungstenautomation.com>; Subhash Chander <subhash.p@tungstenautomation.com>; Raghu Vakkalagadda <raghu.vakkalagadda@tungstenautomation.com>; Santhosh Kumar <santhosh.kumar@tungstenautomation.com>
Subject: Re: [EXTERNAL] RICOH - INC0015321137 - SOP USB port not tracking in Unified Client
Hi Benny,
This issue was raised because the Ricoh RiDP team has confirmed that they do not have control over factory-installed applications and advised us to reach out to you instead.
Here is the Incident ID#: 5547 for the ticket I have raised with them.
Thanks,
Krishna
Krishna Chaitanya
Associate Software Engineer
Tungsten Development Pvt Ltd
V IT Park, Capella Building, Floor 6, Plot No. 17, Software Units Layout
Hyderabad, Madhapur 500081
India
krishna.chaitanya@tungstenautomation.com
.
From: Benny Lastella <benny.lastella@ricoh-usa.com>
Sent: Friday, July 11, 2025 8:36 PM
To: Krishna Chaitanya <krishna.chaitanya@kofax.com>
Cc: Rajesh Nagwekar <rajesh.nagwekar@tungstenautomation.com>; Subhash Chander <subhash.p@tungstenautomation.com>; Raghu Vakkalagadda <raghu.vakkalagadda@tungstenautomation.com>; Santhosh Kumar <santhosh.kumar@tungstenautomation.com>
Subject: Re: [EXTERNAL] RICOH - INC0015321137 - SOP USB port not tracking in Unified Client
Hi Krishna,
Thank you for clarifying in regard to your statement. I am not aware of any Flaw "bug" with the im 3510 model that source reported as "diprint" and not "sdk" as expected. However, you will need an official response from the Ricoh RiDP dev team (Ricoh Developer Program). This is done via the
the RiDP portal at https://ricoh-ridp.com . I am unable to open a case directly for you. I do know that Tungsten is Premier member.
Let me know if you have any further questions
Benny Lastella
Engineer II, Problem Management. Centralized Services
Escalation and Problem Management. Software Engineering
RICOH Digital Services
Ricoh USA, Inc.
Hotline - 888-424-1573 option 2, 1
Enforce the file format to be multiPage TIFF
Incident Properties
Question
- Title:
Can we enforce the file format to be multiPage TIFF when triggering a Ricoh ScanEx scan, if 'color' is selected as the scanColor?
- Device model:
Ricoh MP C407
- Test steps
Refer to the attached sample video "Ricoh Go-2025.4.mp4"
- Log into the Printix Ricoh Go app and start a ScanEx scan from flatbed.
- When the color mode is changed from 'Black & White: Text / Line Art' to any color mode (e.g., Full Color: Glossy Photo, Full Color: Text/Photo, or Auto Color), ScanEx will automatically update the file setting to multiPage PDF from multiPage TIFF.
- Question:
We understand that the Ricoh Scan GUI Service Developer's Guide contains information about fileSetting. However, we would like to confirm with Ricoh if there is a way to enforce this setting on the device, so that even when a color mode (e.g., Full Color: Glossy Photo, Full Color: Text/Photo, or Auto Color) is selected, the file setting remains as multiPage TIFF.
401 installation problem
Incident Properties
Question
There is a device in my lab that seems to be failing our install.....as though the install call doesn't even execute. I'll share the pertinent code fragment:
if (useHttp) { RicohJavaDevice.setUseHttps(false); } else { RicohJavaDevice.setCertlessHttps(true); } RicohJavaDevice mRicohJavaDevice = RicohJavaDevice.CreateDevice(mMachineAddress, remotePassword, username, password, null, null); mRicohJavaDevice.install(mAppZip[0], false);
Based on the log files that we see, I'm not sure the .install call ever executes - more precisely, the function this code is in desn't appear to finish executing. After I checked the device's web page, I didn't see the app installed when I went to the "unistall" list, so that makes me assume that .CreateDevice "timed out" or .install "timed out". There is a try/catch with an RxopException surrounding this code, but that catch didn't run because I didn't see any signs of any of our logging statements.
In regards to the if else, useHttp is false.
Is it possible that either of those 2 functions could start to execute, and not finish? Something to keep in mind is that SP modes have been set by the time code runs, the installer waits for 30 seconds after setting the SP modes. This is a 401, so it should be pretty fast. The last I checked the device had up to date firmware according to the tool.
I've included the .tar file and the decoded/analyzed tar file to see if you can see any evidence of those calls. I can try to dig into this tomorrow and add additional debug logging to see if either of those function actually executed.
MAINTENANCE SIGNATURE - NDDPRINT CLIENT 5.13.2
Incident Properties
Question
Hello,
I would like to get the maintenance signature of our NDD Print Client application.
The application is compatible with 11x and 12x devices that support the SmartOp panel.
Changes:
- Resolved the crash issue that occurred when accessing native application icons within our solution
Note: The package is unsigned and its passing all the tests in ssdkpkg_checker tool.
Best regards;
Maintenance Release Sign in issue
Incident Properties
Question
Maintenance release. Discovered a bug reported from a customer where they could not sign into the machine when the machine was brought in for maintenance. Fixed the issue when it can not connect to the Service Client it would time out to home page.
External Authentication Request Not Triggered for Usernames with Spaces
Incident Properties
Question
Hi Team,
As part of the FAR (Flexible Admin Role) authentication process, when a user attempts to log in to the Operation Panel with a username that contains a space, we do not receive the External Authentication Request (SDKService → Auth app). Is there any limitation in this scenario?
Clarification on Submitting Multiple Pull Print Jobs Simultaneously
Incident Properties
Question
Hello Team,
We are currently working on implementing pull printing in our application.
We have already completed the workflow for single job pull printing, where we share a print URL to the printer, and it processes the job successfully.
Now, we are extending this to support multiple print jobs. We would like to know:
Instead of sending each job one by one, is it possible to submit multiple job URLs at once to the printer for processing?
Please confirm if this is supported, and if so, kindly let us know the recommended method or API approach to achieve this.