SmartSDK

Hello Team,

We are experiencing an issue with the scanner functionality on one of our Ricoh device.

Specifically, the app is intermittently failing to load the scan screen due to repeated failures when attempting to retrieve scanner capabilities from the Ricoh service endpoint.

Please note that the device is currently running firmware version 8.02, while the latest available version is 8.04. We will proceed with updating the firmware, but we’d also like to report the issue for further investigation.

I have attached the log file for your reference. 

The app attempts to fetch scanner capabilities using: GET http://gw.machine.address:54080/rws/service/scanner/capability

The service returns a 503 Service Unavailable response on two consecutive attempts.

Logs for 503 response with Timestamp:

[[248794]]51'57"169 034 04-30 14:51:43.476  5469  5553 I UPConnector: httpclient:RestHttpClient:request: GET http://gw.machine.address:54080/rws/service/scanner/capability

04-30 14:51:43.598  5469  5553 I UPConnector: httpclient:RestHttpClient:response: 503 Service Unavailable

04-30 14:51:43.598  5469  5553 I ScanActivity: RestHttpClient Shutdown

04-30 14:51:43.599  5469  5553 E UPConnector: service:FunctionMessageDis:uniprint.net.ricoh.InvalidResponseException: 503 Service Unavailable

04-30 14:51:43.603  5469  5553 I UPConnector: httpclient:RestHttpClient:request: GET http://gw.machine.address:54080/rws/service/scanner/capability

04-30 14:51:43.724  5469  5553 I UPConnector: httpclient:RestHttpClient:response: 503 Service Unavailable

04-30 14:51:43.725  5469  5553 I ScanActivity: RestHttpClient Shutdown

04-30 14:51:43.726  5469  5553 E UPConnector: service:FunctionMessageDis:uniprint.net.ricoh.InvalidResponseException: 503 Service Unavailable

Additional Reference:

We found this explanation for the 503 - Service Unavailable error in Ricoh’s documentation. It mentions the error occurs when the device is temporarily busy and suggests that retrying the request may succeed.

I have attached the image snapshot reference.

Could you please investigate and let us know:

    1. Why the scanner service might be returning 503 responses intermittently?

    2. Whether there are known issues or service logs that could help diagnose the downtime?

    3. Any recommended configurations or diagnostics we can run on our end?

Thanks in advance.

• Issue:

Sometimes there is no response when pressing the OK button on the ScanEx settings screen.
 

• Device model:

Ricoh IM C7010 (firmware updated to the latest version)

• Issue description:

After broadcasting intent with ACTION "scan_setting" to device, the Ricoh ScanEx settings screen appears. However, sometimes pressing the OK button on the ScanEx settings screen does not produce any response. This issue can also be reproduced using the Ricoh sample app ScanDataHandleExample (available at https://ricoh-ridp.com/system/files/ridp-file-download/pplus/ScanDataHandleExample.zip) to trigger the ScanEx settings screen.
 

• Steps to duplicate (refer to the attached video "Scan settings-20250430.mp4")

1. Install the Ricoh sample app ScanDataHandleExample on IM C7010.
2. Click the "Scan Setting" button on the ScanDataHandleExample app. 
3. The ScanEx Scan Settings screen shows up.
4. Press OK button on the ScanEx settings screen.
5. The screen switches back to the ScanDataHandleExample app.
6. Repeat steps 2 ~ 5.
    

• Test result:

​​​​​​At step 4, the OK button on the ScanEx settings screen sometimes does not respond.

• Information collected:

1. Video: "Scan settings-20250430.mp4" (time frame: 13:34 ~ 13:35, Apr 30, 2025)
2. Device log (MachineInfo_9504R310001_20250430_133950.tar)

Questions:

1. Can you please review the provided information and explain why the issue occurs where there is no response when pressing the OK button on the ScanEx settings screen?
2. Is this an issue with the Ricoh ScanEx app?
3. If not, what steps should be taken to avoid this issue?

Thank you.

Request maintenance signing of CPA applications.  Bug fixes for our integration with AAA Listener, and a Interface problem opening a login page.

Hello,

We are encountering an issue with Ricoh devices where they fail to enter sleep mode. This issue occurs in the following scenarios:

1. Login -> Print -> Log-out -> After 1 min, device screen still active.
2. Login -> Copy -> Log-out -> After 1 min, device screen still active.

Note: The device screen is always active even after 5mins and shows no effect even after pressing the sleep icon (moon icon). 

Surprisingly it works fine with below scenarios:

1. Login -> Log-out -> After 1min, device goes into sleep mode.
2. Login -> Scan -> After 1min, device goes into sleep mode.

When we perform a login, we are locking the device with '3' as the power mode. And below is the code which we perform to unlock device on logout:

private class PowerModeMonitor extends BroadcastReceiver {

        @Override
        public void onReceive(Context context, Intent intent) {
            if (intent.getAction().contentEquals(RicohSDKConstant.ACTION_NOTIFY_POWER_MODE_CHANGED)) {
                currentPowerMode  = intent.getIntExtra("POWER_MODE", RicohSDKConstant.POWER_MODE_OFF);
                log.i("Power mode changed to: " + currentPowerMode);
            }
        }

    }

private boolean tryUnlockPower(int mode) {
        if (!enabledSP5191001PowerMode || mode <= 0 || mode >= 5 || currentPowerMode <= 0 || currentPowerMode >= 5) {
            log.e("enabledSP5191001PowerMode " + enabledSP5191001PowerMode + " currentPowerMode " + currentPowerMode);
            log.e("tryUnlockPower received invalid power mode (" + mode + ")");
            return true;
        }
        log.e("enabledSP5191001PowerMode1 " + enabledSP5191001PowerMode + " currentPowerMode1 " + currentPowerMode);
        for (int powerMode = 4; powerMode >= mode; powerMode--) {
            final Intent intent = new Intent();
            intent.setAction(RicohSDKConstant.ACTION_REQ_UNLOCK_POWER_MODE);
            intent.putExtra("PACKAGE_NAME", androidContext.getPackageName());
            intent.putExtra("POWER_MODE", powerMode);

            androidContext.sendBroadcast(intent, null);
            log.i("Power mode (" + powerMode + ") is successfully unlocked");
        }

        return true;
    }
    
In the method tryUnlockPower,  parameter 'mode' is hardcoded to 3. We are handling the currentPowerMode's from 1 to 4 to unlock the device power mode. However, I noticed an error stating that the 'currentPowerMode' is "0" in the non-working scenario. In contrast, the 'currentPowerMode' is "2" when only a login->logout or login->scan->logout sequence is performed.

Could you please investigate the attached tar file, with the time of each action included, and help us understand why "currentPowerMode" is resulting '0' and why the device fails to sleep after a print or copy job?

I have attached the tar file and note file with the actions and timings.

Thanks,
Krishna  

Hi,

On RICOH Pro 8300S devices we are not receiving any asynchronous job events

eg: the AsyncJob events for scanning jp.co.ricoh.isdk.sdkservice.function.scan.AsyncJobEvent.JOB_EVENT

Could you please let us know why this could happen. The Smart SDK version is 2.50.

Thanks

We are trying to deploy our AAA Custom authentication application on a customer's Ricoh IM C3510 printer.  The instructions for device configuration do not match the Smart Operation Panel screens for  the customers printer.

The instructions that we have can be found here..

https://ricoh-ridp.com/system/files/ridp-file-download/techtips/Custom%20Auth%20Device%20Configuration%20version%202.pdf

It looks like we are getting stuck on step 1.3 Set Administrator Authentication.  The customers printer does not have the Administrator Authentication Management section mentioned in item 1.3.5

Are there any updated instructions in how to configure the device to use an installed customer authentication application?

Thanks,

Keith Reinig

Hi,

I am currently developing a login application for Android using smartSDK, and I would like to hide the system login/logout button. Could you please guide me on how to achieve this? If possible, I would greatly appreciate it if you could share any sample code or documentation that might help.

Please refer to the attached image for more context.

Thank you for your support.

Thanks.

Hello Team

We are experiencing a delay of approximately 1 minute and 30 seconds while loading the scan functionality.

Although logs are present during the delay period, they appear to be unrelated to our application (e.g., system or printer-related logs).

No Delay Case:

04-22 10:50:38.761 30557 30557 I UPConnector: ScanBinder:JobService.onServiceConnected
04-22 10:50:38.761 30557 30557 I UPConnector: service:ScanStMcn: Job Completed Scan Job null

04-22 10:50:38.872 30557 31125 I UPConnector: httpclient:RestHttpClient:request: GET http://gw.machine.address:54080/rws/service/scanner/capability
04-22 10:50:38.939 30557 31105 I UPConnector: httpclient:RestHttpClient:response: 200 OK

Delayed Case:

04-22 12:14:01.104 30557 30557 I UPConnector: ScanBinder:JobService.onServiceConnected
04-22 12:14:01.105 30557 30557 I UPConnector: service:ScanStMcn: Job Completed Scan Job null

→ Delay (~1.5 min)  
04-22 12:15:26.008 30557 31105 I UPConnector: httpclient:RestHttpClient:request: GET http://gw.machine.address:54080/rws/service/scanner/status

We’ve attached the relevant log file for your reference. Kindly assist in identifying the root cause of this delay.

Hi, 

We would like to ask for a maintenance signature for Smartshare Android embedded solution.

• Bug fixes for https connection with TLS;

Best regards

Anderson Palhano

Hi there,

Attached is the ZIP file for the signature. We have increased the application version from 1.5.2 to 1.5.3. In this update, we have done bug fixes found on the customer end.
Issue Highlighted- Newer Ricoh devices with 2.x firmware need to be rebooted often when the login screen fails to load
Fix for the issue- Multiple reciever's were being registered for print and scan, we have made the registeration singleton.

We have shared the unsigned .apk and dalp file and unsigned packages for certification. Please let us know if you need anything else from our side.
Thanks!