Your search did not match any results.
We suggest you try the following to help find what you’re looking for:
These release notes describe the new features, platform requirements, installation, known issues, and limitations for Java Development Kit for ARM Release 8u33 (JDK 8u33 for ARM).
This document contains the following topics:
JDK 8u33 for ARM includes the features and bug fixes of Java SE 8 Update 31. To review these features, see Java SE 8 Update 31 Release Notes.
In addition, JDK 8u33 for ARM contains the following change:
See the JDK for ARM Downloads page to see which ARM devices are supported.
Refer to the JDK 8u33 for ARM README for installation instructions.
This section describes known problems and issues in this release that are specific to JDK 8u33 for ARM. See also Java SE 8 Update 31 Release Notes for known issues, many of which also affect embedded platforms.
4.1 Java SE API Documentation for the javax.crypto Package
Because of a bug, the current Java SE API documentation for the
javax.crypto package does not include compact profile information, but all classes and interfaces in the
javax.crypto package are available with all compact profiles.
4.2 Raspberry Pi Power Supply
The minimum power supply rating to use on the Raspberry Pi is 800mA. However, unless a higher-rated power supply is used, some problems can occur when the CPU or GPU are under heavy load. For example, USB ports can lose power or the device can suddenly reboot. We recommend the use of a 2A power supply.
4.3 Raspberry Pi Input Events
If you run into problems with dropped input events, try reducing the USB bus speed. First, update the Raspberry Pi firmware:
$ sudo apt-get update $ sudo apt-get install raspberrypi-bootloader --reinstall
/boot/cmdline.txt in an editor. On the same line as the other options add
dwc_otg.speed=1. Save the file, run
sudo sync, and reboot.
This option drops USB speeds from 480Mb/s to 12Mb/s, which resolves issues with a variety of USB devices on the Raspberry Pi.
4.4 AWT Graphics Bug
This bug applies to AWT graphics on certain configurations when rendering is performed through the xrender pipeline. There are some platform X11 bugs that can cause empty or partially empty windows running AWT (not Swing) applications.
As a workaround, xrender is disabled by default in Oracle Java SE Embedded. If you want to test your AWT application to see if it runs without an issue, you can force xrender on with the systems property
-Dsun.java2d.xrender=true when you launch the application. For example:
$ java -cp AWTApp.jar -Dsun.java2d.xrender=true awtapp.AWTApp
For more information see the following bug at:
This section describes limitations of JDK for ARM.
5.1 Native Memory Tracking Support is Limited
java command line option
-XX:NativeMemoryTracking=detail is not supported for ARM targets (an error message is displayed). Instead, use the following option: