SmartSDK

The installer in this request uses RXOP 3.8.9.

This request concerns questions about the Ricoh Scan GUI Service. "https://ricoh-ridp.com/resources/downloads/smartsdk-scan-framework-%E2%80%93-ricoh-scan-gui-service" has some comments about G2 devices, and our experiments so far have revealed some questions as we look to enhance our installer application with Ricoh Scan GUI deployment. 

1) How do we determine if a device is a C306 or 406? We have been attempting to use "RicohJavaDevice.getDOMDeviceName() or getEXPDeviceName() but this seems to return "" for some devices. Is there another way we should be investigating? The use of getDOMDeviceName and getEXPDeviceName in the rxop docs seemed straightfoward. Sometimes it returns the wrong value - I noticed on am MP 501 getEXPDeviceName returned "MP 601". But both calls tend to return "" for most device we've tried.

We know we have to write code to determine if the scan service is already installed, and that is understood, but if it isn't, we are seeking guidance on determining the model name.

2) While looking into this question, we came upon the api: RicohJavaDevice.getSopGeneration(). This always seems to return null. Does it need to be invoked in a certain way? We may want to know if a device is G3 or G2.5 in the course of our implementation.

3) The content of the mentioned help topic made specific mention of G2 devices. Does that mean G2.5 and G3 devices are expected to have the Scan Gui Service built into the firmware? This seems to be the case - so far - with our experimentation, but we want to be sure.

Hi,

I am currently developing a login application, and I have observed that after a device restart or waking up from deep sleep, the device takes some time to transition to a functional mode. I have attached images for your reference.

Could you please guide me on how to capture all the states of the machine during these transitions?

Looking forward to your response.

Thank you.

Hello Team,

We would like to be notified and receive the firmware update well before it is released to the public.

So that, we can install it in our printers and run some testing.

This would give us enough time to do some compatibility testing and fixes if required.

Hi Team,

Regarding the previously raised incident (Incident ID#: 5411) -
Clarification Regarding Different Firmware Versions for IM C3000 and IM C3010 | Ricoh Developer Program (RiDP)

The previously mentioned FATAL EXCEPTION reported in the WIM logs shared by the customer was addressed by unregistering the receivers for Print and Scan Broadcast events before registering them at -
"at com.pharos.sentry.smartsdk.pharosauthenticator.app.auth.ui.screen.LoginRootScreen.registerBroadcastReceiver(LoginRootScreen.java:683)"

A test build with these changes was provided to the customer. However, they are still experiencing an issue where the Pharos application stops working. The issue is no longer occurring at "LoginRootScreen.registerBroadcastReceiver."

Attached are the latest WIM logs shared by the customer.

According to the latest WIM logs, we observe the following error:
"02-17 09:12:45.517  4359  4359 E AndroidRuntime: at com.pharos.sentry.smartsdk.pharosauthenticator.app.auth.print.application.AuthorizationState.<init>(AuthorizationState.java:61)"

The issue is occurring in AuthorizationState with the following FATAL EXCEPTION - Caused by: "java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 4359, callerPackage: com.pharos.sentry.smartsdk.pharosauthenticator"

It appears that too many receivers are being registered in AuthorizationState, leading to this exception.

1. Could you help us understand if this should be handled similarly to the previous issue?

Additionally, regarding the second FATAL EXCEPTION: NullPointerException:
2. Could this be caused by the previously killed Receiver thread?
3. Would resolving the first FATAL EXCEPTION also address this issue?

Based on previous testing, it seems that fixing one exception resolves it, but another exception occurs subsequently.
As it was mentioned previously "Since firmware updates could change the runtime behavior, it may be that this is an existing defect that is now exposed because of how receiver events are ordered, etc."
Is there any plan to address this in upcoming firmware updates?


We appreciate your guidance and support in resolving this issue. Please let us know if additional details are required.

Hello, 

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

• Fix severity errors;

Best regards

Domingos Neto

Hi John,

We have a UX issue with the way Abacus applications are working.

We have 2 applications.

1) AbacusLogin-Custom authentication application

2) Abacus regular application after login. (secureprint, custom scans etc..)

After login using AbacusLogin, the user sees that AbacusLogin is transitioned to device home screen and then the Abacus app opens up. There's a delay of 1-3 secs.

Is there any way to keep the Custom auth app open while the Abacus app is opening ?

Is it possible to have the Custom auth application continue to open new screens after login ?

Regards

chaitanya

Its so pity that you closed the original ticket though the token generated was not working.

https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1739890720/1517271746/5445

I got the following error when I tested the api locally.

And the token for a printer device also expires?

If yes, how can we generate a new token for the printer device?

Hi,

Our clients have informed us that they will use DHCP (Dynamic Host Configuration Protocol). Due to this, the IP addresses of Ricoh printers will change periodically. As a result, I need to send the newly assigned IP address to our Abacus server to register/identify the printer. The device IP is mandatory for our server.

I would like to know if there is any mechanism or broadcast receiver available to identify IP address changes. Kindly assist.

Thanks.

Hello Team,

We would like to upgrade the firmware to the latest. Is there any option to rollback to previous version if required?

Let us know the steps for rollback.

Thanks in advance.

Its so pity that you closed the original ticket though the token generated was not working.

https://ricoh-ridp.com/ridp/support-system/incident/ricoh-sdc-canada/1739890720/1517271746/5445

I got the following error when I tested the api locally.