You don't need to include additional libraries in your project. There are no dependency conflicts. In addition, RestFB is highly portable and can be used in both Android projects and normal Java applications.
Although we provide a standard implementation for our core components, each component can be replaced with a custom implementation. This allows RestFB to be easily integrated into any kind of project. Even Android projects are supported.
TThe RestFB API is really minimal and you only need to use one method to get information from Facebook and one to publish new items to Facebook. We provide default implementations for all the core components, so you can drop the jar into your project and be ready to go.
Our Facebook types are simple POJOs with special annotations. This configuration is designed for ease of use and can be used to define custom types very easily.
Newest Version of the
library is available from RestFB's home on Github.
View the
changelog here.
RestFB is a single JAR - just drop it into your application and you're ready to go. Download it from
Maven Central:
Oppo A9 Custom Rom
Abstract The Oppo A9 (2019) occupies a strange purgatory in smartphone history. Shipped with Android 9 (ColorOS 6) and receiving only a lackluster update to Android 11 (ColorOS 11), it was abandoned long before its hardware gave out. Unlike its Snapdragon-powered cousins, the A9 features a MediaTek Helio P35 —a chipset notorious in the modding community for locked bootloaders and a dearth of source code. This paper explores the underground war to bring Custom ROMs (like GSI and Treble) to the Oppo A9, examining why users risk bricking their devices for a few extra years of life. 1. The Paradox of the "Dead" Chipset Most custom ROM communities thrive on Qualcomm chips due to readily available kernel sources. The Oppo A9’s MT6765 is a different beast. Officially, MediaTek is the enemy of the "tinkerer." However, Project Treble (introduced in Android 8) created a loophole. The Oppo A9 shipped with Treble support, meaning the vendor implementation (VNDK) is separated from the Android framework.
Abstract The Oppo A9 (2019) occupies a strange purgatory in smartphone history. Shipped with Android 9 (ColorOS 6) and receiving only a lackluster update to Android 11 (ColorOS 11), it was abandoned long before its hardware gave out. Unlike its Snapdragon-powered cousins, the A9 features a MediaTek Helio P35 —a chipset notorious in the modding community for locked bootloaders and a dearth of source code. This paper explores the underground war to bring Custom ROMs (like GSI and Treble) to the Oppo A9, examining why users risk bricking their devices for a few extra years of life. 1. The Paradox of the "Dead" Chipset Most custom ROM communities thrive on Qualcomm chips due to readily available kernel sources. The Oppo A9’s MT6765 is a different beast. Officially, MediaTek is the enemy of the "tinkerer." However, Project Treble (introduced in Android 8) created a loophole. The Oppo A9 shipped with Treble support, meaning the vendor implementation (VNDK) is separated from the Android framework.
The development of restfb is sponsored by these great companies and individuals. If you also like to sponsor us, please check the sponsor button on our RestFB Github page or send us a short note .
Copyright (c) 2010-2025 Mark Allen, Norbert Bartels. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.