How to run Ssd1351 on Android Things? - i2c

I use android things to run the Ssd1351 on RPI 3B.
My code:
mI2cDevice = PeripheralManager.getInstance().openI2cDevice(i2cName, 0x3c);
mI2cDevice.writeRegByte(0, (byte)0xA5);
And the error:
com.google.android.things.pio.PioException: android.os.ServiceSpecificException: I/O error

Related

Error: Failed to start debug session! in vscode-ros with ROS Melodic

I am trying to debug a ROS node inside VSCode but it seems that the debugger is not working. Please see below screen recordings:
Attaching a running node
Launching nodes
I noticed that attaching a node is requesting authentication. But after providing the correct password, nothing happens. Similarly, the launching nodes show processes for a second but die/disappear immediately.
Below is the version related information:
Visual Studio Code v1.74.3
VSCode-ROS Extension v0.8.4
ROS Melodic
GCC v7.5.0
Python v2.7.17
Ubuntu OS v18.04.6 LTS
Ubuntu OS Kenel v5.4.0-137-generic
The developer tools are showing following following error:
[Extension Host] rejected promise not handled within 1 second: Error: Failed to start debug session!
[Extension Host] stack trace: Error: Failed to start debug session!
at LaunchResolver.<anonymous> (/home/ravi/.vscode/extensions/ms-iot.vscode-ros-0.8.4/out/src/debugger/configuration/resolvers/ros1/launch.js:310:32)
at Generator.next (<anonymous>)
at fulfilled (/home/ravi/.vscode/extensions/ms-iot.vscode-ros-0.8.4/out/src/debugger/configuration/resolvers/ros1/launch.js:7:58)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
Please see a screenshot below:

Android Emulator not running on M1

I cannot start the android emulator V30.9.4
I got this error message:
INFO | Android emulator version 30.9.4.0 (build_id 7759208) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
WARNING | cannot add library /Users/-/Library/Android/sdkPreview/emulator/qemu/darwin-aarch64/lib64/vulkan/libvulkan.dylib: failed
WARNING | cannot add library /Users/-/Library/Android/sdkPreview/emulator/lib64/vulkan/libvulkan.dylib: failed
ERROR | EglOsGlLibrary: Could not open GL library libGLESv2.dylib [dlopen(libGLESv2.dylib, 0x0002): tried: '/Users/-/Library/Android/sdkPreview/emulator/lib64/qt/lib/libGLESv2.dylib' (no such file), '/Users/-/Library/Android/sdkPreview/emulator/lib64/gles_swiftshader/libGLESv2.dylib' (code signature]
ERROR | EglOsEglDispatcher: Could not open EGL library libEGL.dylib [dlopen(libEGL.dylib, 0x0002): tried: '/Users/-/Library/Android/sdkPreview/emulator/lib64/qt/lib/libEGL.dylib' (no such file), '/Users/-/Library/Android/sdkPreview/emulator/lib64/gles_swiftshader/libEGL.dylib' (code signature in <5C3A]
It works with sudo privilege.
Try to use the host system's OpenGL driver:
cd $ANDROID_SDK_ROOT/emulator
./emulator -avd <Pixel_4_API_29> -gpu host
Then go to Emulator Settings -> Settings -> Advanced.
Select OpenGL ES renderer "Autodetect based on host".
Save & restart.
P.S. Get list of avds:
./emulator -list-avds
https://developer.android.com/studio/run/emulator-acceleration#command-gpu

Getting INSTALL_FAILED_UPDATE_INCOMPATIBLE error

Appium Server version: 1.7.1
OS: Windows 8
While running the code I got
org.openqa.selenium.WebDriverException:
An unknown server-side error occurred while processing the command.
Original error:
Error executing adbExec.
Original error:
'Command 'D\:\\Android\\android-sdk\\platform-tools\\adb.exe -P 8080 -s ------ install C\:\\Users\\resi\\AppData\\Local\\Programs\\appium-desktop\\resources\\app\\node_modules\\appium\\node_modules\\appium-unlock \\bin\\unlock_apk-debug.apk' exited with code 1';
Stderr: 'Failed to install C:\Users\resi\AppData\Local\Programs\appium-desktop \resources\app\node_modules\appium\node_modules\appium-unlock\bin\unlock_apk-debug.apk:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE:
Package io.appium.unlock signatures do not match the previously installed version; ignoring!]'; Code: '1'
error and Appium Setting page is opened and instant closed in real Android device instead of opening app (.apk file)
You need to cleanup the device you are using:
Go to Settings -> Apps
Delete you application under test using Uninstall for all users menu
Delete Appium Settings app
Restart your test and it should work

Ionic run on device not working - daemon issue

It was working find, however now I'm getting the below error, when I run this command:
ionic run android
ERROR running one or more of the platforms: Error: adb: Command failed with exit code 1 Error output:
adb I 3000 58815 usb_osx.cpp:259] Found vid=04e8 pid=6860 serial=41007659c88da12f
adb I 3000 58815 usb_osx.cpp:259]
error: could not install smartsocket listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
You may not have the required environment or OS to run this project

CTS_ERROR >>> Failed to execute shell command am instrument

Using the Android 2.2, API-8, SDK-r7 along with CTS-2.2_r4 suite.
Updated the SDK_ROOT environment variable with SDK_r7 tools in “android-cts/tools/startcts” script and the “SDK_ROOT/tools” also included in PATH environment variable.
Ran the “android” and created a new virtual device and started the same. This invokes the emulator named as “emulator-5554”.
Now, started the cts using the below command:
bash android-cts/tools/startcts.
start –plan android
Above command failed with:
Test package: android.app
install met failure [install_failed_insufficient_storage]
CTS_ERROR >>> Failed to execute shell command am instrument -w -r -e package android com.android.cts.app/android.test.InstrumentationCtsTestRunner on device emulator-5554
com.android.ddmlib.ShellCommandUnresponsiveException.
A few more issues are:
CTS_ERROR >>> Got exception while processing command
CTS_ERROR >>> Installing met timeout due to Unknown reason
CTS_ERROR >>> Timeout: ReferenceAppTest
CTS_ERROR >>> Timeout: getDeviceInfo
Any hint to avoid the above timeout issues? Thank you very much for anticipating a quick response from you.
I did not got this error on the CTS 2.1 r5. But I am not running the SDK test that Android but my own tests instead. There for I will use the CTS 2.1 for a while.