Many Android enthusiasts make it a point to root and unlock the bootloader of new smartphones after they are released. Following this, there is often a flood of development in the form of modified kernels, custom ROMs, and other modifications. One may argue that until the shackle (read: “locked bootloader”) has been completely removed, a device’s existence at XDA hasn’t really started. That journey can begin right away for the Nothing Phone 1 community!
You’ll be happy to learn that the Nothing Phone 1’s bootloader can be unlocked in a matter of seconds, and rooting your smartphone only takes a few minutes. If you’ve ever rooted and unlocked the bootloader of a non-carrier Google Pixel or OnePlus handset, you shouldn’t have any trouble doing so on your elegant Nothing Phone 1. Here is a tutorial to help those of you who need a refresher on the procedure.
Since the Nothing Phone 1’s kernel sources and device tree are already available for download, it was inevitable that aftermarket development activity and custom customizations would begin to increase for the gadget. However, in order to boot any third-party software, you must first unlock the bootloader. How to begin going is as follows:
Unlock the Nothing Phone 1’s bootloader
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the latest version of ADB and Fastboot binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command:adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command:adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command:fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards:fastboot flashing unlock_critical
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command:fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader! You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Rooting the Nothing Phone 1 with Magisk
With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
At the time of writing this tutorial, the latest available software for the Nothing Phone 1 is Nothing OS 1.0.2. The full OTA ZIP for this build can be downloaded from here.
In case you don’t want to download the whole OTA file, you can separately download the boot image from XDA forums. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
The software power in image and video processing is one of Google and its products’ most intriguing potentials. The ports of the Google Camera are therefore much sought after by other Android smartphone manufacturers. In actuality, a lot of customers like installing and utilizing the Google Camera ports over the Stock Camera applications developed by other manufacturers.
Google Camera (Gcam), often known as Pixel Camera, is an Android camera phone application. It is evident that GCAM creates images that are more faithful to the source and have a wider dynamic range than the typical camera. It is renowned primarily for its incredible features that enable users to generate “Photo Spheres,” 360-degree panorama photos, etc.
How to download GCam 8.5.3 on your device
The latest version of the GCam, 8.5.300, is available thanks to the developer BSG one of the most active since the beginning in the attempts to make the software available for non-Pixel devices; given that you meet the aforementioned requirements. In reality, for the attempted series it does not harm, the application could be functional even with devices equipped with previous Android versions.
You only need two requirements: run Android 10 or higher and have the Camera2 API. The main requirement for using the mod is that the device supports the Camera2 API. You can check this using a special application.
Disclaimer: This application provided by BSG. If the application is not installed on your mobile or there is any problem with your mobile being installed then we will not be responsible for it. [Install own your risk]
Changelog:
First release 8.5.300
General settings are added: “Interface”, “Hardware Level”, “Activate HDRNET”, google AWB and DEV settings.
Added settings divided into modules: “model”, “preview format”.
If you meet both requirements, you have almost everything done. Installing the GCam 8.5.3 is something extremely easy that you can do in a few steps:
Once the APK has been downloaded, you can install it.
Open the GCam app installed on your smartphone and you’re done
The process is as simple as downloading the APK and installing it. You shouldn’t do anything else. Of course, depending on the device you have, you will be able to access some functions or others of the GCam. Not all sections are compatible with all smartphones.
Over 3,000,000 people downloaded a new Android malware family from the Google Play Store that discreetly subscribes users to premium services.
Maxime Ingrao, an Evina security researcher, found the malware, known as “Autolycos,” in at least eight Android applications, of which two are still downloadable from the Google Play Store as of this writing.
The two apps still available are named ‘Funny Camera’ by KellyTech, which has over 500,000 installations, and ‘Razer Keyboard & Theme’ by rxcheldiolola, which counts over 50,000 installs on the Play Store.
The remaining six applications have been removed from the Google Play Store, but those who still have them installed risk being charged with costly subscriptions by the malware’s activities.
Vlog Star Video Editor (com.vlog.star.video.editor) – 1 million downloads
Creative 3D Launcher (app.launcher.creative3d) – 1 million downloads
Wow Beauty Camera (com.wowbeauty.camera) – 100,000 downloads
Freeglow Camera 1.0.0 (com.glow.camera.open) – 5,000 downloads
Coco Camera v1.1 (com.toomore.cool.camera) –1,000 downloads
During a discussion with Ingrao, the researcher told Droid Tools that he discovered the apps in June 2021 and reported his findings to Google at the time.
Although Google acknowledged receiving the report, it took the company six months to remove the set of six, while two malicious apps remain on the Play Store to this day.
After so much time had passed since the initial reporting, the researcher disclosed his findings publicly.
In place of using Webview, Autolycos uses stealthy malicious behavior to execute URLs on remote browsers and then include the results in HTTP requests.
This behavior is intended to hide its actions from users of infected devices so that they won’t be noticed.
When malicious apps were installed on a smartphone, they frequently asked for authorization to view SMS content, which gave them access to a victim’s SMS text messages.
The Autolycos owners launched various social media advertising campaigns to draw in new users to the apps. Ingrao discovered 74 Facebook ad campaigns for the Razer Keyboard & Theme alone.
Additionally, while some fraudulent apps on the Play Store received unavoidably bad reviews, some with less downloads continue to have positive user ratings thanks to fake reviews.
Android users should have Play Protect activated, monitor background internet data and battery usage, and attempt to install the fewest number of apps possible on their handsets in order to protect themselves against these attacks.
So far, Google has launched two developer previews and eight betas for Android 13, with the eighth beta landing on July 13. These were early versions of the operating system. However, the latest beta is a release candidate, which means it is very nearly complete.
Given how far along the program has progressed, you could feel eager for the remainder of the Android 13 timetable and the release date of the stable version.
We’ve put all the information we currently know about Android 13’s release timetable below.
The approximate Android 13 schedule you see above was provided to us by Google. Overall, it’s a far quicker schedule than what we observed for Android 12 the previous year. Google has so far adhered closely to the plan, accomplishing each milestone. Therefore, unless there are any small point enhancements that might be released, this month’s beta should be the final.
If there are no significant setbacks, Android 13’s stable release should occur around August 2022.
The stable release of Android 12 took place on October 19, 2021, for comparison’s sake. But there was a big change from Android 11 to Android 12. Given that the transition from Android 12 to Android 13 doesn’t seem to be as severe, it’s extremely likely that Google will move.
In the meantime, here are the significant Android 13 schedule milestones we’ve seen so far:
Every year it appears as though Asus has regained its position as the ruler of gaming smartphones, and this year is no different. The flagship ROG Phone 6 Pro for gamers offers the best mobile gaming experience, but it also costs €1,299 (about $1,300 with taxes in the States). Is this astronomical price justified? In this comprehensive examination of the Asus ROG Phone 6 Pro, I offer you my assessment.
On July 5, 2022, the Asus ROG Phone 6 Pro was introduced in France, and pre-orders for the device began on August 1. It is available in a single 18/512 GB version that costs about $1,300 (plus taxes, of course).
We concur that your wallet will suffer as a result. With the same storage, it is less expensive than the Samsung Galaxy S22 Ultra ($1,400) and the iPhone 13 Pro Max ($1,690).
I don’t think it’s wise to get a smartphone that pricey and specialized. On the other hand, the ROG Phone 6 Pro unquestionably provides the industry’s greatest gaming experience in 2022. And when you take into account that many of its features and advantages are present on the entry-level ROG Phone 6, which begins at
Design
The Asus ROG Phone 6 Pro has a futuristic design evoking the fuselage of a spaceship. It features backlit LEDs as well as a small PMOLED add-on display on the back.
Pro:
Great Storm White color scheme with matte finish.
The small screen ROG Vision is a nice gimmick.
3.5 mm jack and finally an IPX4 rating.
The haptic triggers are always so responsive.
Cons:
Massive form factor and bulky weight.
No microSD port.
Storm White is the only shade of white available for the Asus ROG Phone 6 Pro. Black and light blue metallic screen prints contrast with the matte glass surface, which is very pleasant to the touch. The words “Dare to play” are written on a small backlit LED that is located on the rear. The tiny ROG Vision PMOLED display, which is located directly beneath, shows 60 contextual animations (time, notifications, etc). It’s gimmicky, but cool nonetheless, and that’s all that counts.
You can of course disable all of this to preserve your battery. The camera module is slightly off-center on the left but remains centered enough while not sticking out too much to prevent the smartphone from feeling wobbly when laid flat. The screen of the ROG Phone 6 Pro is quite flat with 2.5D edges and the grip is frankly good despite its massive dimensions of 173 x 77 x 10.3 mm and its weight of 239 g.
The ROG Phone 6 Pro boasts an IPX4 grade for water and dust protection for the first time. A 3.5 mm jack is also included, which is always a delight. To increase the storage, however, there is no microSD connector. The Corning Gorilla Glass Victus on the front and Gorilla Glass 3 on the rear of the ROG Phone 6 Pro provide protection.
Asus is also one of the few manufacturers that understands that a USB-C cable is the enemy of mobile gamers because it hinders the grip when holding the smartphone in landscape mode. That’s why the manufacturer offers two USB-C ports, one on the bottom cross slice (USB 2.0) and one on the left side slice, at the bottom in landscape mode (USB 3.1).
Finally, we find the classic haptic triggers (called Air Triggers) that are still as responsive and offer more possibilities for your touch controls.
Screen
he Asus ROG Phone 6 Pro packs a 6.78-inch Amoled display with a Full HD+ resolution of 2400 x 1080p with a variable refresh rate of up to 165 Hz, a touch sampling rate of 720 Hz and a maximum brightness of 1200 nits.
Pro:
The refresh rate goes up to 165 Hz.
Colorimetry well calibrated by default.
Response time of 1 ms and touch latency of 23 ms.
Cons:
The refresh rate not adaptive enough.
The 720 Hz touch sampling rate is a bit weak compared to some competitors.
The ROG Phone 6 Pro’s Amoled screen is ideal for gaming and multimedia use. To the unaided eye, the standard colorimetry is extremely accurate. The display has a 1ms response time (the time it takes for a pixel to change color) and a very low touch latency of 23ms. It is also HDR 10+ certified. This delay, when coupled with the 720Hz touch sampling rate, enables extremely responsive touch controls.
The refresh rate is adaptive, but Asus has not integrated the LTPO 2.0 technology. So it doesn’t vary much according to the different usage scenarios you can subject it to. By default, I was stuck at 120 Hz in the interface, even when I wasn’t touching the screen. On YouTube, I never went above 60 Hz, no matter what the framerate of the video in question was. And in games, I had to activate the X mode to go from 120 to 144 Hz.
By the way, oddly enough, I could only force the settings to 165 Hz by turning off auto refresh rate. Stranger still, when I turned on the X mode, which is supposed to improve performance, I automatically dropped back to 144 Hz.
In fact, Asus seems to voluntarily block the refresh rate at 144 Hz with the X mode. Maybe the manufacturer thinks that 165 Hz is not very useful since no game runs at 165 FPS and it is better to keep performance to allocate to other tasks. But this is quite counterintuitive.
UI – based on Android 12 and X mode
The Asus ROG Phone 6 Pro runs on the ROG UI overlay, a gaming version of ZenUI, Asus’ Android 12-based interface, and the manufacturer promises a fairly limited update policy.
Pro:
ZenUI and ROG UI are lightweight Android interfaces.
Android 12 features are well implemented.
The Armoury Crate menu is as complete as ever.
The ability to switch between ROG UI (gaming design) and ZenUI (more sober design) very easily.
Cons:
The too limited update policy.
Some bloatware (Facebook, Instagram, Messenger, Netflix).
The ROG UI is a customized and gaming-oriented version of ZenUI, Asus’ overlay based on Android 12. This interface is basically very light and close to stock Android. Asus has implemented the dynamic themes of Android 12 as well as the Privacy Dashboard.
And, apart from a few typically gaming stylistic effects on the icons and wallpapers, ROG UI does not push the envelope too far and remains quite sober.
Asus also offers a very basic update policy, guaranteeing only two major Android versions and at least two years of security updates.
The highlight of ROG UI is still the Armoury Crate menu, which allows you to manage the different performance modes: X mode, balanced mode and ultra durable mode. The X mode is the one that allows you to boost all the performance to concentrate the computing power of the CPU and GPU, the allocation of RAM, and your network to the game.
The Game Genie pop-up pane lets you control the refresh rate, enable haptics, control the strength of the external fan, and display specific information like the phone’s temperature or framerate in real time. It also lets you rapidly access many in-game settings.
Nothing very groundbreaking, but this menu is still pretty comprehensive. And the ability to separately create presets for each of your games is really nice. Additionally, you may turn on several filters and features to enhance graphics and, in particular, alter the thermal throttling threshold to push the smartphone as far as you want.
Asus really wants to give the user a level of control and performance customization that comes close, admittedly, to what you can do on a PC. And I think that’s great.
Performance
The Qualcomm Snapdragon 8+ Gen 1 SoC and Adreno 730 GPU, along with 512GB of UFS 3.1 storage and 18GB of LPDDR5 RAM, power the Asus ROG Phone 6 Pro. Additionally, Asus updated its GameCool cooling system.
Pro:
X mode really works and really boosts performance.
Zero overheating in real use.
The hyperefficient external fan.
Cons:
Overheating on a 20-minute benchmark with X mode enabled.
Since the ROG Phone 6 Pro is among the first smartphones to be released in Europe with the premium Snapdragon 8+ Gen 1 SoC, some benchmarks will naturally take some time to adjust. Because of this, 3D Mark’s results on the Wild Life benchmark, which simulates one minute of intensive use, weren’t very informative. The ROG Phone 6 Pro was merely flagged as being overly powerful by 3D Mark at the end of the test, despite the fact that the smartphone did not at all overheat.
However, what is intriguing are the outcomes with the well-known X mode, which improves performance. On the 3D Mark Wild Life Stress Test benchmark, this was accurate (simulating intense gaming use for 20 minutes). A considerable improvement in raw performance is visible. However, the smartphone was actually on fire.
However, the smartphone maintained its steadiness, hovering about 70%. To put it another way, the X mode only lowers the point at which the smartphone will begin thermal throttling. There is little to no throttling present if the smartphone heats up yet the framerate stays constant.
In real-world use, you will be able to run your games without any graphic concession. Even Apex Legends Mobile, a game that is not 100% optimized, runs full speed at 60 FPS with graphics and framerate at maximum. I didn’t experience any slowdowns and above all, no overheating in real conditions, even when I left the X mode on for several hours.
I’ve put a short excerpt of gameplay for you to see. This demonstration of my talent was recorded in 1080p at 120 FPS (the screen recorder settings do not allow more).
Camera
The Asus ROG Phone 6 Pro features a triple camera module on the back, with the well-known Sony IMX766 sensor for the main 50 MP lens, a 13 MP ultra-wide angle lens and a 5 MP macro lens. As for the selfie camera, it offers a 12 MP resolution.
Pro:
The Sony IMX766 which has proven itself both day and night.
The light photo processing and the natural colorimetry.
Cons:
Exactly the same ultrawide angle and macro lenses as the ROG Phone 5.
No dedicated telephoto lens, digital zoom too limited.
Average selfies.
I’m really going to skim over the photo part because Asus has absolutely not messed around this year. It’s exactly the same photo module as on last year’s ROG Phone 5.
It has proven itself and offers a very good level of detail overall, with shots rich in sharpness—a good dynamic range in short—I feel like I wrote the same thing in 5 other different tests.
The ultrawide angle images are a little underwhelming because they lack detail and are quite bland. It should come as no surprise that the digital zoom is constrained after the magnification multiplier reaches x2. The macro sensor, too? It is a macro sensor, I suppose. I don’t really care if I have 2 or 5 MP.
Overall, I think Asus’ software processing is pretty minimal, which results in a colorimetry that feels quite natural. However, occasionally, when there isn’t enough light, the images can be a little too plain for my tastes. Simply said, I have zero enthusiasm for this photo module. And I recognize that a gamer may not necessarily be searching for an advanced photo smartphone.
But the photo remains one, or maybe THE, essential purchase criteria for many users. It’s a shame to see Asus neglect this part when you know that with the computing power of the ROG Phone 6 Pro, there would be plenty to do.
In video, the ROG Phone 6 Pro can record up to 8K at 24 FPS with its main rear lens. The ultrawide angle is limited to 4K at 30 FPS maximum. As for the selfie camera, it can produce videos in 1080p at 60 FPS. I’ll leave you the clips below to get an idea.
Battery
A 6000 mAh battery on the ROG Phone 6 Pro enables 67 watts of wireless charging. There you have it, and it is more than enough.
The dual-cell battery in the ROG Phone 6 Pro charges utilizing the MMT (mid-mid-top) protocol. In essence, the cells don’t charge linearly from one end to the other; instead, they charge from the centre to the ends. Most manufacturers have perfected this technique.
Pro:
Big ass 6000 mAh double cell
67W fast charging does the job
Excellent battery life
USB-C charger included in the box
Cons:
–
On our PC Mark benchmark with the display set to an auto refresh rate and brightness set to 200 nits, the ROG Phone 6 Pro took 19:17 to drop below 20% remaining battery life. That’s an excellent score. Personally, I consider that a battery life is very good from 15 to 16 hours minimum. Here, the ROG Phone 6 Pro does very well when you consider that it powers a very greedy SoC, a large 6.78-inch AMOLED screen and all the LEDs as well as its auxiliary screen.
With a wattage of 67 watts, quick charging is more conventional. The bundled USB-C charger has the advantage of working with Qualcomm’s Quick Charge 5 standard as well as USB PD 3.0 and PPS. It works with the majority of your gadgets.
The ROG Phone 6 Pro, on the other hand, does not support wireless or reverse wireless charging. I was able to charge this large 6000 mAh battery completely in less than 45 minutes overall. And in any case, the ROG Phone 6 Pro’s edge-mounted USB-C connector enables you to play peacefully by connecting it to the power source without being bothered by the
So if the ROG Phone 6 Pro seduced you after this test but, like me, you are not ready to drop $1,300 dollars, then go for the ROG Phone 6. And if you can afford it, if you’re blowing your nose in 100’s of dollars, then PLEASE buy the ROG Phone 6 Pro, the best gaming smartphone of the year.
Which of the various Samsung flagship phones you receive depends on where you reside. While Exynos chips produced in-house are available in some markets, Qualcomm’s Snapdragon CPUs are available in others. And this has been the case for years, with a few extremely rare exceptions like the Galaxy S6 in 2015, which was Exynos-only. Despite having on paper comparable or even superior specifications than their Snapdragon counterparts, Exynos chips are generally thought to be inferior. You’ll be relieved to learn what Samsung might accomplish in the coming year if you reside in Europe and have been envious of those in North America and China who have Snapdragon phones.
Famous supply chain expert Ming-Chi Kuo claims that the Samsung Galaxy S23 may completely exclude Exynos CPUs in favor of Snapdragon processors in all markets next year (via 9to5Google). Even for users in Europe, Qualcomm would end up being the exclusive source of chips for Galaxy S23 smartphones.
Samsung has been experimenting with Snapdragon a lot more recently, most notably by introducing the Galaxy S22 with the Snapdragon 8 Gen 1 in India, a country that has historically favored Exynos. If this change is real, everyone in the world will receive a Galaxy S23 with a Snapdragon processor.
What justifies this? It appears like Samsung is simply coming clean to avoid more embarrassment in 2019. Exynos 2300, which is expected to launch as the Snapdragon 8 Gen 2, will not be able to compete with the SM8550 chip because Qualcomm built it to conform to TSMC’s design specifications. Although embarrassing would be a strong word, the Exynos 2200 launch was a bit of a disaster, and this year’s Exynos-powered Galaxy S22 phones received a ton of unfavorable press. Samsung appears to be trying to avoid that happening again.
Does this indicate that Samsung has finished producing chips? Most likely not. A custom, Galaxy-only SoC is allegedly being created by the firm, but that won’t be available until the Galaxy S25 in 2025, according to rumors. While Samsung Semiconductor refocuses its efforts on that unique chip, it’s possible that we’ll see a few generations of Samsung phones that only use the Snapdragon processor over the course of the next couple of years. But as of right now, all of this is just conjecture. We’ll have to hold off and see.
The most recent version of the well-known software build tool used in Android development and other areas, Gradle 7.0, provides support for Java 16 and faster incremental builds.
To speed up incremental builds, file system watching is now enabled by default in the Gradle 7.0 version, which was released on April 9. Gradle 6.5 offered the functionality as an opt-in feature, and Gradle 6.7 declared it production-ready.
When file system watching is enabled, Gradle keeps its knowledge of the file system in memory between builds instead of reading it during each build. The input and output files are examined during an incremental build to determine what needs to be rebuilt. The I/O overhead added by this capability, which typically saves a significant amount of time but also adds some, can be felt in large projects when little has changed since the previous build.
To upgrade to Gradle 7.0, developers can update their wrapper:
For Android, performance has been improved for incremental changes in projects, especially those using the Jetifer tool to migrate libraries.
Gradle now supports running on and building with Java 16, or Java Development Kit (JDK) 16, which was released on March 16. To support JDK 16, Gradle has been upgraded to use the Groovy 3 language in Groovy DSL build scripts.
Native support is offered for Apple Silicon systems, with every feature now supported using a native Arm JDK. Previous Gradle versions could run on Apple Silicon Macs but there were disadvantages, such as some Arm JDK features had to be disabled while an Intel JDK would run at about half speed through the Rosetta2 compatibility layer.
Version catalogs are introduced as an experimental capability, enabling build authors to centralize dependency coordinates (group, artifact, versions) of their third-party dependencies in a conventional configuration file and declare dependencies in a type-safe way.
An experimental feature for project assessors provides type safety and enables code completion in IDEs.
Build reliability improvements have been made, such as now executing a task without the benefit of parallel execution if a task is failing input/output validation.
Dependency locking, a mechanism to ensure reproducible builds when using dynamic dependency versions, has been improved. The release defaults to the improved dependency locking file format that results in fewer lock files in most projects.
The Intelligence Bureau (IB), India’s domestic spy agency, issued a warning to soldiers not to use certain Chinese eavesdropping Android apps as a matter of national security.
42 Chinese Android apps, including some well-known ones like We Chat, True Caller, UC Browser, and UC News, have been listed by the IB as purportedly gathering crucial data about the Indian security installations.
According to the report, the Intelligence Bureau in a November 24th advisory directed the soldiers assigned on Line of Actual Control (LAC) to uninstall these Chinese spying Android apps from their smartphones and also format the device after uninstallation as it may compromise national security.
However, China has a history of snooping on people using Android apps. Many complaints were made in the past concerning UC Browser’s dubious methods for gathering user data and sending it back to China. Now that the issue has received considerable attention, the administration has advised the troops to delete these risky apps in order to prevent eavesdropping by Chinese eyes.
Just keep in mind that by using these apps, you might unwittingly turn against your country because you never know what information these terrible Chinese espionage applications are sending to China.
To give early customers a chance to test the future software release before the stable deployment, OnePlus released the first Android 13 beta update for the OnePlus 10 Pro last month. The previous build, however, had a number of flaws, thus OnePlus is currently distributing a new Android 13 beta release for the OnePlus 10 Pro. Although OnePlus asserts that the new build is more stable than the previous one, we still don’t advise installing it if you use your OnePlus 10 Pro every day.
The new Android 13 beta release is rolling out as part of OnePlus’ Android 13 Developer Preview Program. It gives developers and advanced users a chance to experience the upcoming version of OnePlus’ custom Android skin ahead of the stable rollout. If you wish to try it out on your OnePlus 10 Pro, check out the full changelog and known issues in the section below.
Android 13 beta changelog:
System
[Fixed] the issue that Data usage cannot display
[Fixed] the issue of crash when turning off/on 5G network
[Fixed] the issue that unable to close all background programs
[Fixed] the issue that the lock screen password was required to enter the launcher after restoring factory settings
[Updated] Android security patch to 2022.05
Camera
[Optimized] the overall shooting effect of the camera, improved the user experience
Known issues:
UI display sometimes might be abnormal
Music playing cannot be paused normally via wired headphones
Occasional abnormal response for gesture operation when the screen was off
No response when tapping the video call button
Auto brightness sometimes works abnormally
Crash issue when setting the Fingerprint animation in Personalizations
Lagging issue caused by switching screen refresh rate
Some applications might be lost after upgrading
ownload: Android 13 beta build for the OnePlus 10 Pro
You can download the region-specific update packages for the latest Android 13 beta build from the links provided below. Make sure you take a full backup of your data before flashing the build.
Kotlin 1.7.0, an update to the JVM, web, and mobile programming language from JetBrains, includes an alpha version of the ground-breaking K2 compiler.
K2 is designed to accelerate the creation of new language features, unify the platforms that Kotlin supports, and offer an API for compiler modifications in addition to enhancing performance. However, the alpha version is restricted to JVM projects. And only the kept plugin for annotation processors currently works with it.
Kotlin 1.7.0, an update to the JVM, web, and mobile programming language from JetBrains, includes an alpha version of the ground-breaking K2 compiler.
K2 is designed to accelerate the creation of new language features, unify the platforms that Kotlin supports, and offer an API for compiler modifications in addition to enhancing performance. However, the alpha version is restricted to JVM projects. And only the kept plugin for annotation processors currently works with it.
Definitely non-nullable types have been promoted to stable. These provide better interoperability when extending generic Java classes and interfaces.
Builder inference, a type inference that is useful when calling generic builder functions, is automatically activated if a regular type inference cannot get enough information about a type without specifying the -Xenable-builder-inference compiler option introduced in Kotlin 1.6.0 last November.
Opt-in requirements are now stable and do not require additional compiler configuration.
An underscore operator for type args can be used to automatically infer a type of argument when other types are specified.
Implementation by delegation to an inlined value of an inline class is enabled. Developers now can create lightweight wrappers that do not allocate memory in most cases.
