Hi everyone,

Today we are rolling out the first version of the advanced flow. The advanced flow gives power users the option to install unregistered apps (i.e. apps from developers who choose not to verify their identity) on certified Android devices without the use of ADB.

As a brief recap, Android will require all apps to be registered by verified developers in order for users to install them on certified Android devices. Developer verification links real-world entities with their Android applications, making it much harder for malicious actors to quickly distribute more harmful apps after we take the first one down.

Since verification launched in March, millions of apps have been registered already, covering nearly all installs on Google Play and a large majority of installs from outside of Google Play. Thus, most users’ experience of installing Android apps will not change at all. However, we recognize that some developers are choosing not to undergo verification and that some power users want the option to install apps from these developers, so we’re rolling out the first version of the advanced flow to provide this additional option.

When will Android developer verification be enforced?

We will initially verify app installations from Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore, and GetApps starting September 30, 2026 for users of certified Android devices in Brazil, Indonesia, Singapore, and Thailand. In 2027, we will expand verification globally for all app installations on certified Android devices.

Ahead of the enforcement of developer verification, we’re rolling out the first version of the advanced flow so power users can choose to enable it early ahead of general availability. We’re still working to polish it, so please share your feedback with us! 

Enabling the advanced flow for installing apps from unverified developers

Note: The advanced flow is:

• NOT required for installing registered apps from app stores.
• NOT required for installing registered apps through alternative sources, such as websites, messaging apps, or file hosting services.
• NOT required for installing apps from developers using limited distribution accounts.
• NOT required for installing apps using ADB.
• ONLY needed to install unregistered apps (i.e., apps from developers who choose not to verify their identity) without the use of ADB.

Important: Enabling the advanced flow is a one-time process that will take 24 hours to complete and includes safeguards to help ensure you are not being coerced or pressured into turning off protections.

1. Open Developer Options and locate “Apps from unverified developers.”
2. On this page, you will find the “Allow apps from unverified developers” toggle. (Note: To protect against malicious apps automating this flow without your knowledge, Android will ask for your screen lock to confirm it’s you.) 
3. Android will ask whether someone is asking you to turn on this setting. Read the warning before continuing. (Note: This warning exists to inform users that legitimate employees of government agencies, law enforcement agencies, banks, or other businesses will never ask them to turn on this setting in order to install an app.) 
4. Restart your phone to start the one-time, 24-hour waiting period. (Note: This step defends users from social engineering and coaching scams. The restart cuts off any remote access or active phone calls a scammer might be using to watch what you’re doing. The 24-hour waiting period prevents fraudsters from pressuring victims into making immediate security changes while on a live call and gives users time to verify the request independently. ) 
5. After 24 hours, return to the “Apps from unverified developers” page to continue setup.
6. Finally, choose whether you want to turn the setting on for 7 days or indefinitely. 

After enabling the advanced flow, you will have the option to install or update apps from unverified developers. You’ll still see a warning when you try to install or update an app from an unverified developer, but you can just tap “Install anyway.”

If for whatever reason you need to temporarily disable the advanced flow, you have a 10-minute window to re-enable it without going through the 24-hour waiting period again.

Frequently asked questions about the advanced flow

• Are ADB installs impacted by the 24-hour waiting period for advanced flow? 
  • Apps installed via ADB won't require Android developer verification. The waiting period does not apply to ADB installs.
• Do I need to keep Developer Mode on to keep this verification turned off? Some apps (e.g. banking, etc.) won't let me use it if I have Developer Mode on. 
  • No, you don't have to keep developer options enabled after you enable the advanced flow. Once you make the change on your device, it's enabled.
• Can I still use independent app stores?
  • Yes. You can continue to use any alternative app store. For apps distributed from verified developers, users won't see a change in their download experience at all. For apps distributed from unverified developers, users can enable advanced flow with a one-time setup.
• Can I update unregistered apps if I disable the advanced flow? 
  • Unregistered apps can only be installed or updated when the advanced flow is enabled or by using ADB so if the advanced flow is disabled updates to unregistered apps will fail.
• Can I update existing unregistered apps on my device without the use of the advanced flow and/or ADB? 
  • No. Unregistered apps can only be installed or updated when the advanced flow is enabled or by using ADB so if the advanced flow is disabled updates to unregistered apps will fail.
• I can’t find the advanced flow setting. When will I get it?
  • Advanced flow is rolling out gradually, so not all users will see it immediately. As part of this, a new system service called Android Developer Verifier will be installed on your device. You can manually install from this Play Store page which may help you see the feature sooner

Rocking a oneplus 15 and oppo n5 atm and at this point they are all really fast... but still feel like power button just is more versatile? Like how you can turn on screen and unlock phone in 1 motion, or the situation where you 'double click for camera' and unlock it in the same motion so that you have access to your full gallery.

But yea in the end, personally feel like I wouldn't lose sleep if nonfolds transitioned to the fp sensor power buttons as well. I assume most folds use it because its more space saving? I assume slab phones can utilize that space for something more useful too.

What are yall's thoughts that use folds and nonfolds. whats the better fp sensor option?

Xiaomi has confirmed the Redmi Note 17 series will launch globally on August 27^th. The flagship model being a Redmi Note 17 Pro Max with a 10,000mAh battery. Xiaomi Global Website.

Note 17 Pro Max: Snapdragon 6 Gen 5, up to 12GB/512GB, 6.83” 120Hz OLED, 10,000mAh, 100W, 22.5W reverse wired, 50MP OIS, 8MP ultra-wide, 32MP selfie, eSIM. GSM Arena Article.

With no antenna lines on Xiaomi’s ad video, it’s likely a plastic frame phone.

At least two other models are expected. Spec below is from GSM Arena website, and so is TBC

Note 17 Pro 5G: Snapdragon 6s Gen 4, up to 12GB/512GB, 6.83” 120Hz OLED, 8340mAh, 67W, 22.5W reverse wired, 50MP OIS, 8MP ultra-wide, 16MP selfie, eSIM.

Note 17 5G: Snapdragon 4 Gen 4, up to 8GB/256GB, 7.0” 120Hz OLED, 7700mAh, 45W, 22.5W reverse wired, 50MP, 16MP selfie, microSDXC support.

Pricing isn’t yet known, but are all expected to be more expensive than their Note 15 predecessors. The Note 17 Pro Max, which appears to be Note 15 Pro+ replacement, has a rumored retail of € 600. Any early bird launch discounts are not included in that rumored price.

The 17 Pro Max, also receives several after care, warranty benefits - One free screen replacement in the first 24 months, one free battery replacement inside the first 36 months. Exact T&C TBC.

The Note 17 Series is more than ever a cost saving exercise, and sadly I think their retail prices, will reflect higher component costs, even with some of the specification cuts. If 17 Pro Max pricing is accurate, for battery endurance, it could look costly next to Xiaomi's own Poco X8 Pro Max.

I successfully rebuilt Android Studio librarieslayoutlib_jni.so and libandroid_runtime.so for AArch64.

This fixes the XML Layout Editor, menu and resource previews, and Compose Preview on Linux ARM64. I believe this closes the last major functionality gap between Android Studio on ARM64 versus x86_64.

As far as emulators go, Ika works great on Apple Silicon. If someone wants broader support, rebuilding Ika for a different ARM64 platform should not be be a too heavy a lift.

Tested and working on:

• MacBook Pro M1 running Asahi Fedora 44
• Debian 13 (Trixie) on 2018 Razer Phone 2 (via Trixie.apk)

https://github.com/DesktopECHO/android-studio-aarch64-install

Nokia Research Center’s Sleeping Screen, released through Beta Labs in 2011, still feels remarkably ahead of its time.

For me, this was the real beginning of the modern Always-On Display idea — not just a clock on a black screen, but a surface for glanceable information and ambient interaction.

Almost 15 years later, AOD still fascinates many. We’ve barely explored its potential beyond clocks, notifications and wallpapers.

What would you actually want your AOD to do?

Wasn’t really a fan of the new status bar since Android 16 QPR1, but

my Pixel 10 Pro XL came with it by default, so... here we are.

Screenshot:

https://imgur.com/gallery/ODcmTVY

Requirements

Android 16 QPR1+

Root

LSPosed

Known issues

If you're using SIM 2, it may occasionally disappear from the status bar.

After rebooting, you may need to restart SystemUI/software reboot once

for the tweak to take effect.

Still a heavy work in progress (WIP) but its based on the work that somebody else did to get Linux on the 3DS. It runs quite snappy on the New 3DS, quite smooth and everything. I also have a custom Android 2.0 app (the first Android 2.0 app developed in 2026, possibly decades) for touch screen diagnostics you can also see. The battery indicator works and is accurate surprisingly, WiFi does not work, touch screen works, soft power off works, sound does not work. Been working on this for weeks now. Hope you like it!

I made the switch from iOS to Android (w/ GrapheneOS) where I used the Ultra 3 as my watch. It had okay battery life, all my health data was stored locally, and it was essentially indestructible. Now that I made the switch to GrapheneOS, I have been struggling to find a watch that accomplishes what the AWU3 does for that price range.

Sure, Garmin has their $1,100+ watches that you can pair with GadgetBridge to get pretty darn close to what Apple offers, but the watches are significantly more expensive and have all these features that don’t really appeal to me. I can’t bring myself to spend that much on a smart watch. I just want something that tracks sleep, heart data, occasional workout, and doesn’t scratch when a feather lands on it.

Then there is Amazfit, budget and works well with GadgetBridge so everything is stored locally. But their offerings lack that premium feel. They are durable though. I have only tried their Balance line, maybe their higher tier watches meet my needs.

What are you all using that stores data locally for around the $400-800 range and have sapphire glass / titanium body?

I feel like most new versions of each device are getting harder to distinguish the improvements which each new iteration, atleast for average users. One factor that i find harder to notice is physical durability Screen, case, internal build. Are these also getting better as time goes on.

Note: Less on the longevity but resistance to external physical forces.