SmartSDK

Hi RiDP Team

We have updated our application for an Enhancement Request below:

Enhancement Request 696503: RicohAndroid client is not certified for co-existence with RicohSOP

+ No permission to delete scanned images from Document Server when using with RicohSOP.

+ Upgrade using aaa 2.1.0 client

Please help to provide maintenance signature for the attached Ricoh Android Client.

Thank you very much.

-Ngoc

Hi RiDP,

Please help to create a maintenance signature for the attached version (25.2.0.0.917)

This version includes the following user stories implementation:

About Screen Update

• The ABOUT SCREEN will display the name of the Unified Client and version number as Tungsten Unified Client™ 25.2.x (where x is the build number) for Ricoh.
• The ABOUT SCREEN will display the standard company copyright text and years shown will be applicable to release year (example: © 2014-2025 Tungsten Automation. All rights reserved)

Online help screen

• It will display a 'help' button that is assessed from the hamburger menu that opens a new 'help' overlay screen that contains a QR code that links to the Ricoh Unified Client online help.

Display TLS level on Server Status Screen

• TLS column is shown on the Server Status Screen with the TLS level that is being used by the device and server components.

Update Kofax Branding for UC

• The Unified Client is updated to show new Tungsten Automation branding.

Print Preferences in Output Manager can be applied to multiple print jobs

• Allow all selected print jobs to have print preferences changed.

Add Blank Page Removal Option & Erase Center/Border Option

Additional RRTs

Thank you

Could you please clarify the recommendations in "always-connection Setting to support USB swipe and wake up the device?  Is this still the recommended approach for ensuring that the network and USB connections are not disabled when the device goes into sleep mode, in order to ensure users can swipe to login from a sleeping device?

What is the difference between enabling the aways-connection setting and implementing sleep lock?  Is the sleep lock supported on all G2/G2.5/G3 models and recommended approach?  Is there any down-side with enabling this lock for customers who do not use card readers?

Thank you.

Hi,

Please find attached version 3.2.9 of the PaperCut MF application for a maintenance signature.

The changes are described as follows:

• Added support for advance scan action

(Please note that we need a SHA-1 signature only, as our app runs on some older devices that do not support SHA-256.)

Request for maintenance signature, bug fixes and other enhancements.

Hello,

I am attempting to get a card reader working on our IM C2510 (G3) device. I have the VID and PID values successfully set in the USB device list, but can't get a card to swipe.

Looking at the device tracelog, I see the following:

04-08 09:16:57.255 2833 3337 E UsbPortManager: port status enquiry failed
04-08 09:16:57.256 2833 3106 I UsbHostManager: keystroke reader is attached
04-08 09:16:57.257 2833 3337 E UsbPortManager: port status enquiry failed
04-08 09:16:57.254 0 0 I : usb_set_configuration bmAttributes[000000E0/00000080] status[00000001]
04-08 09:16:57.254 0 0 I : usb_set_configuration parent hub is self power
04-08 09:16:57.273 2833 3106 D UsbHostManager: USB device attached: vidpid 0c27:3bfa mfg/product/ver/serial RFIDeas/USB Keyboard/10.70/null hasAudio/HID/Storage: false/true/false
04-08 09:16:57.290 2833 3106 I UsbHostManager: check UsbDevice device is supported

[[1772]]17'23"561 606 04-08 09:16:57.291 2833 3106 D UsbHostManager: Added device UsbDevice[mName=/dev/bus/usb/003/006,mVendorId=3111,mProductId=15354,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=RFIDeas,mProductName=USB Keyboard,mVersion=10.70,mSerialNumberReader=com.android.server.usb.UsbSerialReader@69a9bae,mConfigurations=[
04-08 09:16:57.291 2833 3106 D UsbHostManager: UsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=50,mInterfaces=[
04-08 09:16:57.291 2833 3106 D UsbHostManager: UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=3,mSubclass=1,mProtocol=1,mEndpoints=[
04-08 09:16:57.291 2833 3106 D UsbHostManager: UsbEndpoint[mAddress=129,mAttributes=3,mMaxPacketSize=8,mInterval=10]]]]
04-08 09:16:57.293 4323 4323 I CIServ : Reader Setting: 0C27,3BFA,Usb Card Reader,KSR
04-08 09:16:57.293 4323 4323 W CIServ : plugin[jp.co.ricoh.advop.cisplugin.keystroke] is not bound
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventReceiver: onReceive - action: android.hardware.usb.action.USB_DEVICE_ATTACHED
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventHandler: deviceAttached - deviceName: /dev/bus/usb/003/006
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventHandler: deviceAttached - deviceClass: 0
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventHandler: deviceAttached - vendorId: 3111
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventHandler: deviceAttached - productId: 15354
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventHandler: checkPermission - vendorId: 3111
04-08 09:16:57.295 4242 4242 I Authentication: app.auth.usb.UsbEventHandler: checkPermission - productId: 15354
04-08 09:16:57.296 2833 2833 I UsbHostManager: SupportInfo name[/dev/bus/usb/003/006] is Supported
04-08 09:16:57.296 2833 2921 D UsbDeviceManager: Clear notification

[[1773]]17'23"620 177 04-08 09:16:57.297 2833 3348 W UsbService: reject requestDevicePermission for keystroke reader

The device (or Android system) is rejected our request for permission to the reader.

Any ideas why this is happening? I vaguely recall this happening a long time ago, but can't recall how we resolved the issue.

Regards
Bryan

Hi

Our SmartSDK app "RicohAnroidClient" is using old AAA client.

Today, we are upgrading to use newest AAA client v2.1.0, but we face an issue on physical device and Simulator.

When initialing AAASmartSDKAuthenticationManager, the app is stopped by issue from AAA client: "NoClassDefFoundError" of "Lorg/slf4j/LoggerFactory"

We have included the "slf4j-api-1.7.9.jar" then the application works as well

Question: Should we include slf4j-api-1.7.9.jar to use "aaa-client-2.1.0.jar" as a requirement?  or any missing from me?

We do not see any mention about slf4j-api in the AAA 2.1.0 document guide.

Please advise!

----------- logs ----------

04-02 10:23:30.621  1445  1445 W DeviceAAAListener: Init device AAA AuthenticationManager...
04-02 10:23:30.632  1445  1445 D AndroidRuntime: Shutting down VM
04-02 10:23:30.635  1445  1445 E AndroidRuntime: FATAL EXCEPTION: main
04-02 10:23:30.635  1445  1445 E AndroidRuntime: Process: com.kofax.app.scan, PID: 1445
04-02 10:23:30.635  1445  1445 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/slf4j/LoggerFactory;
04-02 10:23:30.635  1445  1445 E AndroidRuntime:     at com.ricoh.auth.manager.AAASmartSDKAuthenticationManager.<clinit>(AAASmartSDKAuthenticationManager.java:21)
04-02 10:23:30.635  1445  1445 E AndroidRuntime:     at com.kofax.app.scan.application.DeviceAAAListener.Start(DeviceAAAListener.java:42)
04-02 10:23:30.635  1445  1445 E AndroidRuntime:     at com.kofax.app.scan.activity.MainActivity.onCreate(MainActivity.java:184)

Thank you

Ngoc

Can we please get access to the new Ricoh Log Analyzer portal and could this be added to all papercut accounts.

Hello;

We are experiencing intermittent but frequent issues with excessive slowness when using the MP C3504 printer, particularly during the session transition from our authentication process to logging into the printer.

The issue occurs throughout the day, and after the printer generates the error "Client Android has stopped responding," the process of initiating a session on the machine becomes significantly slower. This delay is noticeable compared to the other printer in use. The application becomes unresponsive, and this happens repeatedly during the day. In some cases, the only way to resolve the issue is to restart the printer using the physical reset button.

We would like to mention that the application worked normally with these MP C3504 printers before, and we suspect that a recent update might be causing this issue.

The logs we have collected are attached for your reference. Could you please assist us in diagnosing and resolving these problems?