Android device update software

XDA Basics: How to Check and Update the Android Version on your phone

If you’re trying to find out the Android version of your smartphone or wondering how to update it, we can help. It’s actually quite easy to check the Android device’s software information. In this guide, we’ll talk about exactly how you can check the Android version or install a new update on your phone, presuming that your device OEM has provided an official update.

How to check the Android version of your device

• Open the Settings app on your phone or tablet.
• Scroll down, and tap on System.
• You’ll now see an option called About phone (or About tablet) — tap on it. If you don’t see the About phone option, you may have to tap on something like Software Information, depending on your device. On some phones, you might find the About phone option right on the main setting page.
• On the About phone screen, you’ll see all the details, like the Android version, as well as your device manufacturer’s software version. This page will also give details about the Android security patch level, baseband version, kernel version, and build number.

Until a couple of years ago, Google used to name the Android versions after a dessert or a sweet. But now, the Android versions just include numbers. So depending on your device’s Android version, you can see a name, or a version number and a name, or just a version number.

How to update your Android phone

• Open the Settings app on your Android phone.
• Scroll down to System, and tap on it.
• Now, tap on the System update option under Advanced. In some cases, the Software update option may be present right under the main settings.
• After you’ve tapped on System update, your phone will search if an update is available for your phone. If there’s no update, you’ll be informed that your phone is up to date. If there’s an update, you can follow the on-screen instructions to download and install it.

On Pixel phones, you can also check for Security and Google Play system updates by going to Settings > Security > Security update.

This is how you can check the Android version of your phone and update it officially. As mentioned, the options may be at different places on devices from different manufacturers. Note that if your phone manufacturer has not provided any updates, you will not see any updates available as this method is only checking for officially provided updates.

If your phone is too old and outdated, and you’re looking to upgrade, check out our recommendations on the Best Phones, the Best Android Phones, and the Best Cheap Android Phones.

Источник

Samsung Firmware Downloader is a free cross-platform tool to download software updates for Galaxy devices

There are a lot of reasons to manually download firmware for your device. Maybe you’re trying to root it and need to modify the stock firmware before flashing it. Or maybe you just want to download software updates early. Unfortunately, companies don’t often make it easy to actually download that firmware in an easily-installable way.

The problem with downloading Samsung firmware

Samsung especially likes to make it hard to manually download software updates. For one, there’s no Fastboot mode on Samsung devices. To flash firmware, you have to go into Download Mode and use Samsung’s proprietary flashing tool, Odin. Then, you have to actually get the firmware file to flash. If you try to download the firmware directly from Samsung, it’ll be encrypted.

Luckily, that encryption isn’t very strong, and the process of downloading and decrypting firmware directly from Samsung has been recreated many times. One notable example of this is the SamFirm program for Windows. SamFirm no longer works, but there are alternatives, like Frija, which are still functional.

The only problem with most of these downloader programs is that they’re all for Windows. What if you want to download software updates for your Galaxy device from your Mac or Linux PC? Well, you could use one of the many firmware downloader websites out there. Those sites serve decrypted Samsung firmware for basically any Samsung device. You can browse for firmware by device model, filter by region, and even view the history of firmware versions.

But storing all those files gets expensive. To be maintainable, most downloader sites will restrict the download speed unless you pay for an account. Since Samsung’s firmware packages are pretty big (recent devices are as large as 7GiB), downloading on a throttled connection can be pretty annoying. You could always pay for unlimited speeds, but not everyone’s willing to do that.

My solution: Samsung Firmware Downloader

So back to square one. How can you download firmware directly from Samsung if you don’t have a Windows PC? Enter Samloader, a command-line program that runs on anything where Python 3 is installed. You can use Samloader to check for the latest update for your device, download that firmware, and even decrypt already-downloaded firmware, as long as you know the correct model, region, and firmware string.

Samloader is pretty great since it’s a properly cross-platform solution to downloading Samsung firmware. But not everyone likes to use the command line. It can get confusing trying to install Python on macOS, for instance, and keeping track of all the needed command-line arguments can be tricky.

So I made a GUI. TheВ very originally-named Samsung Firmware Downloader is a cross-platform graphical firmware downloader for Samsung. In spirit, it’s a graphical wrapper around Samloader, but all of the logic has been rewritten in Kotlin. There are also some additional features.

Samsung Firmware Downloader is a cross-platform GUI program.

Samsung Firmware Downloader Features

That was a lot of lead-up for this, but hopefully, it was at least somewhat helpful. Let’s talk about Samsung Firmware Downloader, starting with the name.

Naming

Samsung Firmware Downloader is a terrible name. It’s way too generic, and it’s also way too long. If anyone has suggestions, I’d love to hear them.

Platform Support

Like I said earlier, Samsung Firmware Downloader is cross-platform. That means it should run on Windows, Linux, macOS, and even Android. To do this, I’m using a combination of Kotlin Multiplatform, Android’s Jetpack Compose, and JetBrains Compose for Desktop. Kotlin Multiplatform and JetBrains Compose are still in pretty early development, but they’re functional enough for a simple GUI.

Currently, JetBrains Compose can only build executables that target the platform they were built on. That means that I can’t currently release any macOS builds since I don’t have access to a Mac. If you have a Mac, and you want to help out, let me know. Eventually, JetBrains Compose should let me build for Mac from a Windows machine but now isn’t eventually.

Source Code

If you followed any of the links above, you may have noticed that Samsung Firmware Downloader is open source. It’s licensed under MIT and is completely free to use and modify.

Features

So what can Samsung Firmware Downloader do? I talked a bit about it above, but here’s some more detail.

Check for Updates

Put your model and region into the corresponding fields in the Downloader view and hit “Check for Updates.” The app will query Samsung’s server and return the latest firmware version available, along with which version of Android it is.

You can check for the latest firmware for your device and region.

Download software updates

If you just checked for updates in the Downloader view, you can then hit the Download button to start downloading that firmware. Choose a destination, and the app will download and decrypt the firmware automatically.

If you know the firmware you want to download, toggle the “Manual” checkbox and enter it, along with the model and region. Then you can hit “Download” and the app will take care of the rest.

One thing to note is that the encrypted firmware won’t be automatically deleted after it’s decrypted. You’ll need to do that manually.

Samsung Firmware Downloader also modifies the name of the firmware file slightly to include the firmware version, model, and region it represents, but you can set it to anything you want.

And finally, Samsung Firmware Downloader will automatically resume downloads. If your device crashed or you accidentally closed the program, just put in the details again, hit “Download,” choose the same directory (confirming any potential replacement prompts), and your download will resume where it left off.

You can download any valid firmware using this tool.

Decrypt

If you have an encrypted firmware file, you can use Samsung Firmware Downloader to decrypt it. Enter the model, region, and firmware version corresponding to the encrypted file, then select the file to decrypt, hit the “Decrypt” button, and the app will take care of the rest.

Decrypt pre-downloaded firmware.

History

This is an experimental feature that may be removed later on. The History view shows the complete list of firmware versions available for a given model and region. It then displays them to you.

If you want to download a specific firmware from the list, hit the “Download” button. You’ll be redirected to the Download view with the information already filled in. Then you can just hit “Download.”

If you have a file to decrypt, you can find the corresponding firmware in this list and hit the “Decrypt” button. You’ll be redirected to the Decrypt view, where you’ll just need to choose the right file and hit “Decrypt.”

Samsung Firmware Downloader can list all available firmware versions for your device and region.

Downloads

So how do you get Samsung Firmware Downloader? Check out the releases page on the GitHub repository. Each release has assets for Android, Windows, and Linux (and eventually macOS).

On Android, just download the APK and install it. On Windows, download the ZIP, extract it, and run the EXE. On Linux, download and extract the ZIP, go into the bin directory, open a terminal, and run ./Samsung\ Firmware\ Downloader .

Hopefully, Samsung Firmware Downloader makes your experience downloading software updates even easier. I’m always looking for suggestions for new features (within reason), so be sure to head over to the issues page and request a feature or report a bug if you don’t see it there already.

Источник

Implement In-app Update In Android

Make sure every user of your app is on the new version.

Apr 6, 2020 · 8 min read

In this article, we will learn about the In-app update feature in Android what is all about In-app update, what are the benefits of using the In-app update in your android application. Recently I’ve been working on a product in which I need to Implement an In-app update Why we need to Implement this?.

As a Developer we always want our users to have the updated version of their application but there are a lot of people who actually turned off their auto update from google play store and he/she doesn’t know about any update available or not.

To overcome the problem Google Introduced this feature called In-app update from this feature you can easily prompt the user to update the application and with the user permission you can update the application also while updating the app user can be able to interact with the application. Now the user doesn’t need to go to google play store to check there is any update available or not.

What is In-App Update:

An In-app update was Introduced as a part of the Play Core Library, which actually allows you to prompts the user to update the application when there is any update available on the Google Play Store.

There are two modes of an In-app update.

• Flexible Update
• Immediate Update

Flexible Update:

In Flexible update, the dialog will appear and after the update, the user can interact with the application.

This mode is recommended to use when there is no major change In your application like some features that don’t affect the core functionality of your application.

The update of the application is downloading in the background in the flexible update and after the completion of the downloading, the user will see the dialog in which the user needs to restart the application. The dialog will not automatically show, we need to check and show to the user and we will learn how later.

Benefits:

The major benefit of the flexible update is the user can interact with the application.

Источник

SDK Platform Tools release notes

Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb , fastboot , and systrace . These tools are required for Android app development. They’re also needed if you want to unlock your device bootloader and flash it with a new system image.

Although some new features in these tools are available only for recent versions of Android, the tools are backward compatible, so you need only one version of the SDK Platform-Tools.

Downloads

If you’re an Android developer, you should get the latest SDK Platform-Tools from Android Studio’s SDK Manager or from the sdkmanager command-line tool. This ensures the tools are saved to the right place with the rest of your Android SDK tools and easily updated.

But if you want just these command-line tools, use the following links:

• Download SDK Platform-Tools for Windows
• Download SDK Platform-Tools for Mac
• Download SDK Platform-Tools for Linux

Although these links do not change, they always point to the most recent version of the tools.

Revisions

31.0.3 (August 2021)

• fastboot
  • Support flashing vbmeta_vendor.img for fastboot flashall / update.

31.0.2 (April 2021)

• adb
  • Support forwarding to vsock on linux.
  • Fix bug in adb track-devices where devices over wireless debugging wouldn’t immediately receive updates.
  • Implement preliminary support for mDNS device discovery without a separately installed mDNS service. This is currently disabled by default, and can be enabled by setting the environment variable ADB_MDNS_OPENSCREEN to 1 when starting the adb server.
• fastboot
  • Don’t fail when unable to get boot partition size.
  • Derive device locked state from property instead of parsing the kernel command line.

31.0.1 (March 2021)

• adb
  • Reduce TCP keepalive interval.
  • Improve incremental installation performance.
• fastboot
  • Add support for compressed snapshot merges.
  • Restore legacy A/B support.

31.0.0 (February 2021)

• adb
  • Disable compression on pull by default.

30.0.5 (November 2020)

• adb
  • Improve performance of adb push when pushing many files over a high-latency connection.
  • Improve adb push/pull performance on Windows.
  • Fix adb push —sync with multiple inputs.
  • Improve performance of incremental apk installation.
  • Improve error handling for incremental apk installation.

30.0.4 (July 2020)

• adb
  • Fix fallback to non-incremental apk installation on pre-Android 11 devices.
  • Fix adb install-multi-package .
  • Fix some more crashes related to adb wireless pairing.
  • Improve some error messages.
• fastboot
  • Improve console output on fastboot oem commands.
  • Fix fastboot flashall on older devices such as Nexus 7.

30.0.3 (June 2020)

• adb
  • Fix installation of APKs signed with v4 signature scheme on pre-Android 11 devices.
  • Fix crash when authenticating without ADB_VENDOR_KEYS .
  • Fix crash when using adb -H .

30.0.2 (June 2020)

• adb
  • Improve adb wireless pairing.
  • Fix hang in adb logcat when run before a device is connected.
  • Add adb transport-id to allow scripts to safely wait for a device to go away after root/unroot/reboot.

30.0.1 (May 2020)

• adb
  • Disable adb mdns auto-connection by default. This can be reenabled with the ADB_MDNS_AUTO_CONNECT environment variable.
  • Improve performance of adb install-multi on Android 10 or newer devices.
  • Fix timeout when using adb root/unroot on a device connected over TCP.
  • Update support for wireless pairing.

30.0.0 (April 2020)

• adb
  • Add initial support for wireless pairing.
  • Add support for incremental APK installation.
  • Implement client-side support for compression of adb when used with an Android 11 device.
  • Improve performance of adb push on high-latency connections.
  • Improve push/pull performance on Windows.

29.0.6 (February 2020)

• adb
  • 64-bit size/time support for adb ls when used with an Android 11 device.
  • Support listening on ::1 on POSIX.
  • Client support for WinUSB devices that publish a WinUSB descriptor (required for Android 11) should no longer require a USB driver to be installed.
  • Fix hang when using adb install on something that isn’t actually a file.

29.0.5 (October 2019)

• adb
  • Slight performance improvement on Linux when using many simultaneous connections.
  • Add —fastdeploy option to adb install , for incremental updates to APKs while developing.

29.0.4 (September 2019)

• adb
  • Hotfix for native debugging timeout with LLDB (see issue #134613180). This also fixes a related bug in the Android Studio Profilers that causes an AdbCommandRejectedException , which you can see in the idea.log file.

29.0.3 (September 2019)

• adb
  • adb forward —list works with multiple devices connected.
  • Fix devices going offline on Windows.
  • Improve adb install output and help text.
  • Restore previous behavior of adb connect without specifying port.

29.0.2 (July 2019)

• adb
  • Fixes a Windows heap integrity crash.
• fastboot
  • Adds support for partition layout of upcoming devices.

29.0.1 (June 2019)

• adb
  • Hotfix for Windows crashes (https://issuetracker.google.com/134613180)

29.0.0 (June 2019)

• adb
  • adb reconnect performs a USB reset on Linux.
  • On Linux, when connecting to a newer adb server, instead of killing the server and starting an older one, adb attempts to launch the newer version transparently.
  • adb root waits for the device to reconnect after disconnecting. Previously, adb root; adb wait-for-device could mistakenly return immediately if adb wait-for-device started before adb noticed that the device had disconnected.
• fastboot
  • Disables an error message that occurred when fastboot attempted to open the touch bar or keyboard on macOS.

28.0.2 (March 2019)

• adb
  • Fixes flakiness of adb shell port forwarding that leads to «Connection reset by peer» error message.
  • Fixes authentication via ADB_VENDOR_KEYS when reconnecting devices.
  • Fixes authentication—when the private key used for authentication does not match the public key—by calculating the public key from the private key, instead of assuming that they match.
• fastboot
  • Adds support for dynamic partitions.
• Updated Windows requirements
  • The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package.

28.0.1 (September 2018)

• adb
  • Add support for reconnection of TCP connections. Upon disconnection, adb will attempt to reconnect for up to 60 seconds before abandoning a connection.
  • Fix Unicode console output on Windows. (Thanks to external contributor Spencer Low!)
  • Fix a file descriptor double-close that can occur, resulting in connections being closed when an adb connect happens simultaneously.
  • Fix adb forward —list when used with more than one device connected.
• fastboot
  • Increase command timeout to 30 seconds, to better support some slow bootloader commands.

28.0.0 (June 2018)

• adb:
  • Add support for checksum-less operation with devices running Android P, which improves throughput by up to 40%.
  • Sort output of adb devices by connection type and device serial.
  • Increase the socket listen backlog to allow for more simulataneous adb commands.
  • Improve error output for adb connect .
• fastboot:
  • Improve output format, add a verbose output mode ( -v ).
  • Clean up help output.
  • Add product.img and odm.img to the list of partitions flashed by fastboot flashall .
  • Avoid bricking new devices when using a too-old version of fastboot by allowing factory image packages to require support for specific partitions.

27.0.1 (December 2017)

• adb: fixes an assertion failure on MacOS that occurred when connecting devices using USB 3.0.
• Fastboot: On Windows, adds support for wiping devices that use F2FS (Flash-Friendly File System).

27.0.0 (December 2017)

• Re-fixes the macOS 10.13 fastboot bug first fixed in 26.0.1, but re-introduced in 26.0.2.

26.0.2 (October 2017)

• Add fastboot support for Pixel 2 devices.

26.0.1 (September 2017)

• Fixed fastboot problems on macOS 10.13 High Sierra (bug 64292422).

26.0.0 (June 2017)

• Updated with the release of Android O final SDK (API level 26).

25.0.5 (April 24, 2017)

Fixed adb sideload of large updates on Windows, manifesting as «std::bad_alloc» (bug 37139736).

Fixed adb problems with some Windows firewalls, manifesting as «cannot open transport registration socketpair» (bug 37139725).

Both adb —version and fastboot —version now include the install path.

Changed adb to not resolve localhost to work around misconfigured VPN.

Changed adb to no longer reset USB devices on Linux, which could affect other attached USB devices.

25.0.4 (March 16, 2017)

• Added experimental libusb support to Linux and Mac adb

To use the libusb backend, set the environment variable ADB_LIBUSB=true before launching a new adb server. The new adb host-features command will tell you whether or not you’re using libusb.

To restart adb with libusb and check that it worked, use adb kill-server; ADB_LIBUSB=1 adb start-server; adb host-features . The output should include «libusb».

In this release, the old non-libusb implementation remains the default.

fastboot doesn’t hang 2016 MacBook Pros anymore (bug 231129)

Fixed Systrace command line capture on Mac

25.0.3 (December 16, 2016)

• Fixed fastboot bug causing Android Things devices to fail to flash

25.0.2 (December 12, 2016)

• Updated with the Android N MR1 Stable release (API 25)

25.0.1 (November 22, 2016)

• Updated with the release of Android N MR1 Developer Preview 2 release (API 25)

25.0.0 (October 19, 2016)

• Updated with the release of Android N MR1 Developer Preview 1 release (API 25)

24.0.4 (October 14, 2016)

• Updated to address issues in ADB and Mac OS Sierra

Download Android SDK Platform-Tools

Before downloading, you must agree to the following terms and conditions.

Terms and Conditions

1. Introduction

2. Accepting this License Agreement

3. SDK License from Google

4. Use of the SDK by You

5. Your Developer Credentials

6. Privacy and Information

7. Third Party Applications

8. Using Android APIs

9. Terminating this License Agreement

10. DISCLAIMER OF WARRANTIES

11. LIMITATION OF LIABILITY

12. Indemnification

13. Changes to the License Agreement

14. General Legal Terms

Download Android SDK Platform-Tools

Before downloading, you must agree to the following terms and conditions.

Terms and Conditions

1. Introduction

2. Accepting this License Agreement

3. SDK License from Google

4. Use of the SDK by You

5. Your Developer Credentials

6. Privacy and Information

7. Third Party Applications

8. Using Android APIs

9. Terminating this License Agreement

10. DISCLAIMER OF WARRANTIES

11. LIMITATION OF LIABILITY

12. Indemnification

13. Changes to the License Agreement

14. General Legal Terms

Download Android SDK Platform-Tools

Before downloading, you must agree to the following terms and conditions.

Источник