Due to high demand from our growing community, Mender.io includes the Raspberry Pi 3 as a reference device for its OTA updater for Mender 1.3 and all future versions! Mender.io is the open source project to deploy over-the-air (OTA) software updates for connected Linux devices. You can read about it on our latest blog post at Mender.io.
Related
Thursday, July 19, 2012
Google Jelly Bean SDK Updated, Full Version Open To Downloads
2:01 AM Sophia
The version of Google’s Jelly Bean SDK is officially released and available for download! Being obtainable since Google I/O in a preview state, the new version is fairly improved and brings number of patches and bug fixes.
So the latest SDK tools revision 20.0.1 is now open and moreover, it is ready for developers to download! Before you rush to get it, learn what’s new first:
SDK tools revision 20.0.1 Dependencies include the following : the SDK Tools r20.0.1 is designed for use with ADT 20.0.1 and later, so those developing in Eclipse with ADT will need to , update the ADT Plugin to 20.0.1 first. Apache Ant 1.8 or later is required for those developing outside the Eclipse. And one more thing requited is the Android SDK Platform-tools revision 12 or later.
The improvements and bug fixes brought by the SDK tools revision 20.0.1 include the following:
• Fixed wrong check on build state that forced repetitive Java code recompilation;
• Fixed problems with running more than one emulator and running multiple emulators with GPU acceleration;
• Improved resize algorithm for better rendering on scaled emulator windows;
• Fixed a bug in the lint check for unprotected broadcast receivers to ignore unprotected receivers for default Android actions;
• Fixed build issue for projects using Renderscript;
• Fixed memory leak in the emulator.
DOWNLOAD
The SDK tools revision 20.0.1 can be obtained from HERE
original thread here
....... wrong post
...wrong section :laugh:
So you just copy and paste something and post it in Development section instead of General?
So all over tech news today is the recently discovered vulnerabilty of android devices with Qualcomm chips. I downloaded the app that checks for these vulnerabilities and the links to each bug is below. There is very little that users on stock roms can do about this other than wait for Sony to release an updated version of their ROM. I expect fixes to be incorporated into OmniRom, CyanogenMod, Paranoid Android and other custom roms as and when the Open Devices team merge them in.
https://www.codeaurora.org/projects...r-binding-any-port-control-port-cve-2016-2059
https://www.codeaurora.org/use-afte...tions-kgsl-module-cve-2016-2504-cve-2016-2503
https://www.codeaurora.org/use-afte...tions-kgsl-module-cve-2016-2504-cve-2016-2503
https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340
Lol the latest ROM is merely on the May 1st Security patch, I don't think they'll ever incorporate these patches in.
These are all kernel patches so they should be easy to patch into a custom kernel
The Sony concept team is very fast with updates and security patches. So maybe Concept-Rom users don't have to wait too long for a patch?
Just don't install random **** from the Internet and you're set. Same goes for Windows devices.
There, just saved you thousands of IT budget.
From Ugoos BLOG
IMPORTANT: This BETA release based on Tablet SDK for RK3288 chipset.
Already added Ugoos Settings and Features.
Here is a short list:
CIFS & NFS Clients Support, Samba Server
Masked HDMI
Screen Rotation
Root
Hardware Monitor
Wireless Assistant
Gamepad Settings
Debug Settings
User Scripts
USB Mode Settings
Right now, we are still working on HDMI IN functionality for Ugoos UT3+, firmware for this device will be released later.
Download Link: Ugoos RK3288 NOUGAT UT3/UT3s/UM3 BETA 4.0.0b
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
why alpha? when can we expect a stable build?
shawon11 said:
why alpha? when can we expect a stable build?
Click to expand...
Click to collapse
Sorry bro but this is not my work I am just sharing good TWRP:good:
Azizbagwan said:
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
Click to expand...
Click to collapse
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
robbayani said:
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
Click to expand...
Click to collapse
Project Treble is the Answer
The reason manufacturers have such a hard time pushing out prompt updates is because of all the work that has to go into getting the operating system to communicate with the hardware.
Traditionally, it worked something like this: the OS framework and low-level software were all part of the same code. So when the OS got updated, this low-level software–technically referred to as vendor implementation—also had to get updated. That’s a lot of work.
So, starting with Android 8.x (Oreo), Google separated the two. That means the Android OS itself can be updated without having to touch the vendor implementation. That, in turn, can be updated by itself if needed.
To put that in full context, before an update can be pushed out to an Android 7.x (or earlier) device, not only does the Android OS code have to be updated, but so does the low-level hardware code, which is generally maintained by the chip maker. So, for example, if Samsung wants to push an update to one of its phones, it has to wait for Qualcomm (or whoever made the chip) to update its code to work with the new Samsung code. That’s a lot of wheels turning at once, and each one is dependent on the other.
With Android 8.x and beyond, it won’t be like this anymore. Since the core hardware code is separate from the OS code, device manufacturers will be free to update their software without having to wait for the silicon maker to also update its code.
This should dramatically speed up the update process—in theory, at least. Updating devices will still be in the manufacturer’s hands, and since the first Oreo devices outside of the Google-maintained Pixel line are just now rolling out, we haven’t yet had a chance to fully see this in practice. Hopefully, it actually makes a significant change to the speed in which updates are written and pushed out.
Will My Device Benefit from Project Treble?
Now that’s the million dollar question, right? Unfortunately, the answer isn’t so simple (surely you didn’t expect it to be). That said, here are some facts:
If your device never gets updated to Oreo, it will never get Project Treble. No way around that. Sorry.
If your device does get updated to Oreo, it’s still not required to support Treble—that’s up to the manufacturer.
If you buy a new phone that runs Oreo out of the box, it is required to support Treble out of the box.
In short: Treble support on updated systems is still up to the manufacturers, but new Oreo devices will be required to support Treble moving forward.
So, for example, the Pixel 2 already supports Project Treble. The forthcoming Galaxy S9 will also support Treble out of the box. Google also updated the Pixel 1 to support Treble, but it’s unfortunately it looks like Samsung left it out of the Oreo build for the Galaxy S8.
If you’re curious about your own device, Android Police has a running list of all devices that will get Treble support, as well as a which ones will get updated to Oreo without Treble.
Android OS updates have been a constant point of contention for many years now, so it’s good to see Google finally addressing the issue. With any luck, this will put all Android devices closer to parity with Apple in terms of device updates.
Hi,
I am opening this thread to start a discussion about LineageOS and the recently announced Project Mainline to put together a Q&A list (I will summarize the interesting questions and answers in this first post).
1. In general: will Project Mainline still work when you switch from your manufacturers stock ROM to LineageOS..? Or may there some restrictions for non-official ROMs through the Play Store?
2. Will LineageOS be able to support Project Mainline for devices that support Project Mainline in their stock ROM?
3. Will LineageOS be able to support Project Mainline for older devices? Or do old Linux kernels prevent this? Are kernel refreshs for old devices even technically feasible or is it far too much effort and too buggy in most cases?
4. These are the 14 components Project Mainline is able to update via the Play Store:
• Security: Media Codecs, Media Framework Components, DNS Resolver, Conscrypt
• Privacy: Documents UI, Permission Controller, ExtServices
• Consistency: Timezone data, ANGLE (developers opt-in), Module Metadata, Networking components, Captive Portal Login, Network Permission Configuration
I assume this doesn't cover all "components" in Android, or does it? What parts are left out and why - does anybody know?
Cheers,
carsten