Android API

Hi,

Currently, our product is integrating with SmartScanEx 1.06 in order to check for its product id on the IM 300 device to install if its version on device is less than 1.06.

However, it seems the product id of the SmartScanEx on IM 300 was changed to 1680333568 which is not what we are expecting for 1679877888.

As a result, our application is trying to install SmartScanEx 1.06 to this device by  using RXOP.

Is changing product id expected from Ricoh site?

If we try to install SmartScan 1.06 to the device, is there any potential issue for scanning on this device due to the co-existence of the two versions?

Do you expect RXOP can be able to install SmartScanEx 1.06 to this device without any error?

Thanks,

Problem Description: After Installing PCC v. 5.1.30.231 on an NRG IM C300 (Ricoh Rebranded device), selecting the scan option causes the device to hang. This Partner also has a NRG IM 430 and a NRG IM C4500A and these devices work fine.

Environment Details: ControlSuite 1.1 NRG IM C300 (We have checked the firmware and it is up to date)

Prerequisite/Configuration: Single server installation. 

Based on the log message below, it looks EQ posted request to firmware to start scan activity but for unknown reason the scan activity was not started (at least the scan screen was not shown). The video showed the firmware's please wait screen at the end.

[[3526]]40'39"658 226 04-27 14:39:52.699 1581 5684 I ScanManager: neuf_ebs-19: [DEBUG]: posting event: IScanManager.StartScan...

[3565]]40'42"806 485 04-27 14:39:52.955 1581 3670 I RicohScanScreenFacade: epm-exec-AndroidEventProcessingService-1: [DEBUG]: Broadcasting intent from StartScan:action:...

[[3566]]40'42"886 412 04-27 14:39:52.969 2224 2224 I SSE:AL : State[IDLE] receive Event[APP_LINK_REQUEST_scan_job]

04-27 14:39:52.993 2224 2224 I SSE:AL : startActivityForScanJob()  

Hi,

We are trying to develop a custom authentication flow for RICOH using Android. We want to configure the application remotely for some basic details like server connection details, but we have no idea about how to do it. Here is the use case:

#Android application is going to be installed on multiple devices, and every device is expected to connect a remote server for authentication and other functionality of it. We want to provide remote server configurations to this Android app remotely once installation is done(as configurations will change from environment to environment).

Is there any web API available that allows us to put some configurations to this Android application which can be reflected within the app and can be persisted after device reboots? What is the best way to provide initial configurations to device(auth server details etc) after Android application installation.

regards

Vikash

Hello,

With regards to configuring SSL with Android. Is there an alternative solution to installing the certificate via SD card on each device manually?

Thank you,

Calvin Knight

Upland QA engineer

Hello, The customer, Schoettl GMBH, is pushing Ricoh Germany to find out what it would take to have compression level options added to the Scan Gui service.  We have told the customer that the Scan Gui service does not support this and that we were going to remove this option from our application as it shouldn't be there as found in Ridp ticket 3361. 

Ricoh Germany told the customer that they need Kofax to request from Ridp what it would take to have this added to the Scan Gui service.  

So on behalf of the customer I am requesting that compression method and compression level be added to the Scan Gui service sdk (api).

1. Issue description.

The issue is very similar to Ridp #3453 but it is for a different customer. They saw "Please Wait" message and could not log into device after entering user id. The tech at the customer site insists that the Home Key setting had already been set to PCC5 before the issue occurred.

2. Log info.

From the log I can see that looks like the Ricoh Launcher was also being started at almost the same time (11:53:37, see below).

08-15 11:53:36.654  1523  4706 I DeviceLoginController: pool-10-thread-1: DeviceLoginController Device level login succeeded, device login state: DEVICE_LOGIN_SUCCEEDED

===> User logged in

08-15 11:53:36.984  1523  1523 I LauncherScreenFactory: main: [DEBUG]: Creating launcher screen

... ...

... ...

08-15 11:53:36.993   656  1029 I ActivityManager: START u0 {flg=0x34000000 cmp=com.nuance.ndi.neuf.ricohsmartsdk/com.nuance.ndi.neuf.android.activity.LauncherActivity_ (has extras)} from uid 10097 pid 1523 on display 0

===> Trying to start the Nuance Launcher activity.

... ...

08-15 11:53:37.049   656  4112 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.DEFAULT] flg=0x10a00000 cmp=com.android.launcher/com.android.launcher2.Launcher} from uid 10006 pid 1019 on display 0

===> Ricoh Launcher was being started.

... ...

08-15 11:54:44.326  1523  1523 I RicohEventReceiver: main: [DEBUG]: onReceive : Intent { act=jp.co.ricoh.isdk.sdkservice.system.SystemManager.SYSTEM_RESET_INFO flg=0x10 cmp=com.nuance.ndi.neuf.ricohsmartsdk/com.nuance.ndi.neuf.ricohplatform.appcontrol.RicohEventReceiver }

08-15 11:54:44.326  1523  1523 I RicohEventReceiver: main: [DEBUG]: Got system reset

===> Did not see any Android lifecycle events (e.g. onCreate, onStart, onResume,...) to indicate the Nuance Launcher activity was started and displayed.

3. Questions.

a. Can Ricoh team please have a check if this issue was still related to the Home Key setting?

b. Is any further info needed for the next step?

The log info is attached (see MachineInfo_3129M141928_20190815_135443.tar and result_201908161352.zip.).

Thanks.

1. Issue description.

The customer reported this as a high priority issue. They saw "Please Wait" message and could not log into device after entering user id. This "Please Wait" message will last approximately 1 minute and then device comes back to login screen. After several unsuccessful attempts they may have to restart the device to get it recovered.

2.Cause of the issue.

Refer to attached "investigation.docx" and the full log "result106_201907090912.zip".

a. The issue started at around 12:33. When reviewing the logs I noticed that Ricoh SOP called androidContext.startActivity trying to start the Nuance Launcher activity but did not see anything to indicate the activity was really started. Because the activity was not started the "Please Wait" message showed up. Even when the logout occurred (which should be triggered by auto logout timer) the Nuance Launcher activity still did not seem to start.

06-26 12:33:50.600  1567  1567 I LauncherScreenFactory: main: [DEBUG]: Creating launcher screen

06-26 12:33:50.604   666  2871 I ActivityManager: START u0 {flg=0x34000000     cmp=com.nuance.ndi.neuf.ricohsmartsdk/com.nuance.ndi.neuf.android.activity.LauncherActivity_ (has extras)} from uid 10098 pid 1567 on display

===> Did not see any Android lifecycle events (e.g. onCreate, onStart, onResume,...) to indicate the Nuance Launcher activity was started and displayed.

b. While the previous login session (started at around 12:31) seemed to be fine and looks like in the previous login session the Nuance Launcher was started and destroyed properly.

3. Questions:

a. "startActivity" is an Android call,  and it is unclear why the Nuance Launcher activity was still not started even after the auto logout was triggered and finished, but can Ricoh team please also review the device logs and see if this issue is firmware related?

b.  What is the expected taken time to see an activity (for example, Nuance Launcher activity) is started after calling "startActivity" on the Ricoh Android platform? 

c. If this issue occurs on Nuance Launcher activity, could this issue occur on the other activities (for example, Follow You printing activity)? Actually, this is also our concern.

Symptom: PCC app started launcher activity with Intent.SCREEN_ID=18191d88-b0b4-4576-923a-55ecebfb318b. The launcher activity was started having id "723844cd-fa0b-408c-be15-5e218494b596". As id didn't match, PCC app stuck in launcher starting state and had to be restarted.

The log file is attched for your review. The problem occurred at 7:47 AM on 4/23/2019. In the log line 11357, PCC app started launcher and line 11454 reported the id of launcher started and the id of launcher PCC app tried to start didn't match. Once the launcher is created successfully, PCC app will log "Processing ILauncherScreenFactory.LauncherScreenCreated" message. I reviewed the log and found SDK logs are diferent between problematic launcher creation (between line 11357 and 11453) and normal launcher creation (between line 26079 and 26143). Please review the log and advise.

Thanks,

Richard

Sorry, previous signed build was pointing to wrong URL.  I have made changes and resubmitted it with same build number.  Sorry

Thanks