PDF Version Support
Incident Properties
Question
Dear Team,
We tried to print PDF files with pdf version 1.7 and it was unsuccessful - we see Format Error while printing.
Does Ricoh support PDF Version 1.7 ?
SmartSDK Maintenance Signature
Incident Properties
Question
I have a fix for the next release of our SmartSDK solution that will require a maintenance signature.
1. We are still supporting devices containing a Smart Operation Panel with SmartSDK version 2.10 and later.
2. AppManager.zip, Authentication.zip, and SecureDelivery.zip are the modified apps.
3. The .dalp files are not modified.
Changes:
1. Fixed issue by setting targetSdkVersion to 23.
Regards
Bryan
REQUEST FOR MAINTENANCE SIGNATURE FOR V3.8.6
Incident Properties
Question
Request for maintenance signature, bug fixes and other enhancements.
MAINTENANCE SIGNATURE FOR SMARTSHARE - 1.1.9
Incident Properties
Question
Hello.
As agreed in the last incident (#4981), we need this version (1.1.9) to be signed to fix a critical issue on our client.
- Fixed problem capturing device information (serial number and MFP host)
Therefore, we will send this version for Compatibility Test. However, we are not finding the first compatibility test incident for productID = 1711276263, so we can attach the PDF of the previous RiDP Test, and after submit the request for a new Compatibility Test.
How can we proceed with this doubt?
We count on your understanding and await the signed version.
Best Regards,
Domingos.
Request maintenance signature RicohSOP 1.3.0.6 FIX19548 (PCC 5.3)
Incident Properties
Question
Hi
Our customer requires an improving to support specific character in username and password for PCC5 installation.
FR 19548 - Aetna Inc. - Premier - Aetna - PCC5 deployment fails when device password contains special characters.
Please help to create a maintenance signature on this RicohSOP/PCC5
Thank you.
Ngoc
SmartScanEx please wait screen on Ricoh MP C6004
Incident Properties
Question
Hi
The customer meets an issue on MP C6004, click on Scan button, it shows smartScanEx screen but Please wait screen shows forever and the scanner did not pull the paper from the feeder. (see the attached Testing 8-30.docx)
There are about 15 other MFDs that are working properly, including other MP C6004 devices. They have checked the SP mode and Special SP mode settings on a working MP C6004ex device and the non-working MP C6004 device and could not find any differences.
You can analyze the attached log around time: 08-30 13:38:16 for starting scan action
08-30 13:38:16.162 3429 5492 I System.out: 2023.08.30 13:38:16.170 [DEBUG]: epm-exec-AndroidEventProcessingService-1: (RicohScanScreenFacade) RicohScanScreenFacade Broadcasting intent from StartScan:action: jp.co.ricoh.isdk.sdkservice.function.AppLink.APP_LINK_REQUEST data: null extras: UI.setting.job.originalOrientation.enabled=true UI.setting.job.originalPreview.visibility=invisible UI.setting.job.manualDensity.enabled=true UI.setting.job.originalOrientation.visibility=visible UI.setting.job.fileSetting.fileFormat.visibility=visible UI.setting.job.originalPreview.enabled=false UI.setting.job.originalSize.enabled=true UI.setting.job.scanColor.enabled=true ACTION=scan_job PACKAGE_NAME=com.nuance.ndi.neuf.ricohsmartsdk UI.setting.job.fileSetting.multiPageFormat.visibility=visible UI.setting.job.scanMethod.enabled=true SOURCE_INTENT=Intent { cmp=com.nuance.ndi.neuf.ricohsmartsdk/com.nuance.ndi.neuf.ricohplatform.scan.RicohScanActivity } UI.setting.job.fileSetting.multiPageFormat.enabled=true UI.setting.job.originalSide.visibility=visible UI.setting.job.originalSide.enabled=true UI.setting.job.scanResolution.visibility=visible UI.setting.job.scanColor.visibility=visible UI.setting.job.manualDensity.visibility=visible UI.setting.job.originalSize.visibility=visible UI.setting.job.fileSetting.fileFormat.enabled=true SCAN_JOB_SETTING={\"scanResolution\":\"200\",\"scanColor\":\"monochrome_text\",\"originalSize\":\"auto\",\"autoDensity\":true,\"pdfSetting\":{\"digitalSignaturePdf\":false,\"pdfA\":false,\"highCompressionPdf\":false},\"scanMethod\":\"normal\",\"fileSetting\":{\"compressionMethod\":\"none\",\"fileNameTimeStamp\":false,\"multiPageFormat\":true,\"fileFormat\":\"tiff_jpeg\"},\"originalSide\":\"top_to_top\",\"originalPreview\":false,\"manualDensity\":0,\"originalOrientation\":\"readable\"} UI.setting.job.scanMethod.visibility=visible UI.setting.job.scanResolution.enabled=true
...
08-30 13:38:17.482 5551 5551 I SSE:AL : startActivity(Intent { cmp=jp.co.ricoh.advop.smartscannerex/.ui.main.MainActivity (has extras) },Intent { cmp=com.nuance.ndi.neuf.ricohsmartsdk/com.nuance.ndi.neuf.ricohplatform.scan.RicohScanActivity },true) start
Could you please help to analyze device logs for the reason of the issue of SmartScanEx? It is running SmartScanEx v1.06.
Thank you
Ngoc
Hints for device installation error codes
The development kit documentation discusses some of the error codes that can be raised when installing SOP application to devices via WIM. See: Smart Operation Panel > Start Guide > Installation > 05. Installation/Uninstallation of the Product Version Application
While these error codes are correct (and should always be shared with RiDP in situations where SOP installations are failing) they may not be as detailed as we like. Here are some hints that might explain a specific error code you are receiving.
Not getting proper output for different paper sizes
Incident Properties
Question
Hi,
I am developing an application that supports scan and copy functionality. Now, when I am trying to scan or copy a large-sized document to a small-sized one (say, A3 to A4), the output gets cropped. Similarly, when I am trying to scan or copy a small-sized document to a large-sized one (say, A4 to A3), the output layout does not completely fit within the document.
So what settings do we need to pass while the scan or copy job starts?
Thanks
Stop button issue
Incident Properties
Question
We have a client who had an issue scanning through our application. I have device logs when this happened, and I noticed these logs in the client device logs:
09-07 14:28:51.514 1082 1082 I Launcher.Model: onReceive intent=Intent { act=jp.co.ricoh.advop.banner.PRESSED_STOP_BUTTON flg=0x10 (has extras) } |
09-07 14:28:51.514 1082 1082 I Launcher:LinkActivityReceiver: onReceive jp.co.ricoh.advop.banner.PRESSED_STOP_BUTTON,state=2 |
09-07 14:28:51.524 1082 1082 I Launcher: receive StopKeyAccept, return :true |
09-07 14:28:51.524 1082 4350 I Launcher.LinkActivityService: onHandleIntent event=6 |
09-07 14:28:51.525 1082 4350 I Launcher.LinkActivityService: onPressedStopButton |
Do these logs mean the stop button on the device was pressed? It almost looks to me like the device was reset during the scan.
Because the scan was not canceled correctly, this caused the scan problems reported by the client.
I am concerned with what happened during thie timeframe.
Can anyone explain what happened from this log information?
I am attaching the full log.
SmartSDK 10-day Demo Signature
Incident Properties
Question
Hello Team,
While tried to get demo signature build from Ricoh.
Browser replies with the below error. Can you help out of this? Package file and screenshots are shared in the attachments.
Error Message : Apk File Already Signed