Nothing Phone (2a) owners are seeing an Android 15 beta path that includes a feature branded as Shared Widgets. If you’re curious—or already receiving the update—this guide walks you through what to expect, how to install safely, and how to troubleshoot the most common widget-sharing problems.
Because beta software can be a little less predictable than stable releases, the goal here is simple: get you to a working update with Shared Widgets enabled, without losing data or wasting time on avoidable missteps.
What’s new: Android 15 beta and Shared Widgets
Android 15 beta typically brings early platform changes (system behavior, security model adjustments, background execution changes, and new APIs). Those changes can affect apps and widgets even if the widget itself didn’t change.
Shared Widgets is the headline feature for Nothing Phone (2a) beta testers. In practical terms, it’s meant to let your widget-related UI (think homescreen cards) be shared or synchronized across devices where you’re signed in and allowed to share that content. The exact implementation details can vary by build, but the setup pattern is usually the same: connect devices, grant widget permissions, then mark certain widgets as shareable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Unlocked for All GSM Carriers Only (Excluding Verizon, Sprint, US Cellular), No CDMA. Dual SIM, Networks: 2G GSM, 3G, 4G LTE, 5G
- 6.7" inch, Flexible AMOLED, 1084 x 2412 (394 PPI), 240 Hz, Corning Gorilla Glass 5
- 128GB Storage, 8GB RAM
- MediaTek Dimensity 7200 Pro, Octa Core, Up to 2.8 GHz
- Nothing OS 2.5 Powered by Android 14
Who should install the Android 15 beta on Nothing Phone (2a)
Install the beta if you meet one of these profiles:
- You have a primary device that you can tolerate being slightly less stable for a short time.
- You want to test widget sharing (Shared Widgets) and report issues with reproducible steps.
- You rely on development tools or need early compatibility with upcoming Android platform changes.
Skip the beta if you need guaranteed reliability for work or you can’t troubleshoot basic issues like permission resets, app updates, or widget refresh delays.
Prerequisites before you update
Before flashing or installing anything labeled beta, confirm you have the basics covered. You’ll save time later.
- Backup: Use Google backup where possible, and manually back up anything irreplaceable (photos, authenticator codes, key documents).
- Battery: Keep your Nothing Phone (2a) at least 50% battery (preferably 80%+).
- Storage: Free up at least 5–8GB if the update is OTA and might need temporary space.
- Network stability: Use Wi‑Fi for the download/install when possible to avoid partial downloads.
- App readiness: Make sure your key apps are updated from the Play Store right before the beta, so widgets won’t break due to outdated widget providers.
How to check if your Nothing Phone (2a) has the Android 15 beta
Even if the feature announcement is circulating, your specific device might not have the build yet. Check first so you don’t install the wrong package.
Recommended Free Tools
Verify your current build
- Open Settings.
- Go to About phone.
- Find Android version and Build number.
Look for signs it’s beta software: a beta tag in the build metadata, a different version naming pattern, or an Android version indicator showing Android 15.
Check for the beta OTA notification
- Open Settings.
- Go to System > System update.
- Tap Check for updates.
If you see Android 15 beta listed, confirm that the release notes mention Shared Widgets (or that the widget-sharing option appears in the UI after install).
How to install the Android 15 beta (Shared Widgets included)
There are a few ways beta builds get to devices. Use the one that matches what your update screen offers.
Method 1: OTA update from Settings
- Connect to Wi‑Fi.
- Open Settings > System > System update.
- Tap Check for updates.
- Select the Android 15 beta update (if shown).
- Tap Download, wait until it completes.
- Tap Restart to install (wording may vary).
After reboot, give the phone a few minutes for background optimizations. Then check Settings > About phone again to confirm you’re on the expected Android 15 beta build.
Free tools Windows power users keep installed
One-click scans. No signup required.
Method 2: If you’re enrolled in a beta program
If Nothing (or Google/partner channels) enrolled your device, the beta might appear only after you opt in.
- Open Settings > System > System update.
- Look for an option like Beta, Update program, or Receive beta updates.
- Enable it, then return to the update screen and run Check for updates.
If the option isn’t present, your device may not be eligible yet, or the beta may be staged by batch.
Method 3: If Nothing provides a beta package/installer
Some betas ship as a package (OTA/manual). If Nothing posts a beta build file, follow their exact instructions rather than guessing.
- Download only from the official channel linked by Nothing.
- Verify file integrity if the instructions provide a checksum.
- Follow the device-specific update steps (often “tap the package from storage” or use an update tool inside Settings).
- Reboot and confirm the Android 15 beta build number in About phone.
If you can’t confirm the source or checksum, don’t install. Beta rollbacks and recoveries get harder when the base doesn’t match.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #2
- Nothing OS 2.0: A new visual identity. Customise everything from app labels and grid design to widget size and colour themes. Now with new folder layouts. Create widgets for quick settings functions or save time by adding key widgets directly to your lock screen. The new Glyph Interface: Key information, in a flash. Assign different light and sound sequences for each contact and notification type. Use the lights to track progress or create your very own ringtones with the Glyph Composer.
- Camera: We’ve upgraded the camera’s internal software entirely so photos and videos are more dynamically accurate than ever. A new bigger 32 MP front sensor captures picture-perfect portraits. Dual rear 50 MP main + 50 MP ultra-wide camera effortlessly captures real life with smart tuning effects like Advanced HDR, Motion Capture 2.0 and Night Mode. New 2x Super-Res Zoom preserves a scene's finest details. Video: 4k 60fps videos on the main rear camera and 1080P at 60fps on the front camera.
- Display: 6.7” LTPO OLED display with 1600 nit peak pixel brightness and Gorilla Glass 5 (front and back). With LTPO, Phone (2) can intuitively adapt its 120 Hz refresh rate to preserve power when you're not on your phone. A killer display that doesn’t murder battery life. NOTE: AT&T (full support), T-Mobile (full support) - THIS DEVICE IS NOT COMPATIBLE with CDMA carriers such as Cricket, Verizon, Sprint, Boost Mobile, US Cellular, etc.
- Battery: At 4,700 mAh, Phone (2) houses our longest lasting battery yet. Charge fully in just 55 minutes. Lasts up to 22.5 hours. Compatible with 15W Qi wireless charging. Phone (2) also doubles as a 5W wireless charger so you can power accessories like Ear (2) on-the-go. Chipset: With the Snapdragon 8+ Gen 1 chipset, Phone (2) boasts an 80% improvement on performance over its predecessor. Now with rapid speed, the best in-house heat management, and advanced camera capabilities.
- Sustainability: 100% recycled aluminium mid-frame, 100% recycled tin on 9 circuit boards, 100% recycled copper foil on the main circuit board, and over 90% recycled steel on all 28 steel stamping parts. Plus, 80% of the plastic parts are sustainably sourced. The packaging for Phone (2) is entirely plastic free with 60% of the paper included coming from recycled sources.
Setting up Shared Widgets after the update
Shared Widgets usually depends on two things: (1) your device setup (accounts, permissions, widget provider compatibility) and (2) a share/sync mechanism for homescreen content.
Connect the devices that should share widgets
- On the primary device, verify you’re signed into the same core account that the feature expects (commonly your Google account).
- On the secondary device, sign into the same account.
- Confirm both devices have up-to-date Play Store services and the widget provider app installed.
If Shared Widgets requires an internal Nothing account flow, it will show during setup after you place or configure a widget.
Choose which widgets are shareable
After the update, add a widget as you normally would, then look for widget-level controls like “share”, “sync”, or “available on other devices”.
- Long-press on the home screen.
- Tap Widgets (or equivalent).
- Add a widget from a supported app.
- Tap the widget (or open widget settings) to find sharing controls, if present.
If you don’t see any widget sharing option, ensure the widget app is updated and granted required permissions.
Customize layout, sizing, and refresh behavior
Shared Widgets often prioritizes the content and updates more than exact pixel layout. After you add a shared widget, check:
- Widget size options (small/medium/large) on both devices.
- Whether the widget refreshes automatically or only on foreground.
- Notification and background data permissions for the widget provider app.
Test with a single widget before sharing broadly
Start with one widget from one app (for example, a news, calendar, or utility widget you know updates reliably). Once it appears on the other device and stays correct for 10–30 minutes, expand to additional widgets.
Best practices for stable Shared Widgets performance
- Update the widget provider app on both devices right after the beta install.
- Keep permissions consistent: background data, notifications, and battery optimization settings should match closely.
- Avoid aggressive battery savers while testing. Beta builds can be more sensitive to background execution restrictions.
- Don’t mix widget providers that are outdated or in conflict with new Android 15 behavior.
Troubleshooting: what to try when Shared Widgets fails
When something breaks, don’t guess randomly. Use this order: refresh state, check permissions, verify widget provider, then reset the feature’s configuration.
Widgets don’t appear on the other device
- Confirm sign-in: both devices should be signed into the same account the feature uses.
- Wait 5–15 minutes after making a change. Some widget sync is not instantaneous on first setup.
- Update the widget app on the receiving device.
- On the receiving device, go to Settings > Apps > find the widget provider > check permissions (notifications/background data).
- Restart both devices once (yes, it’s boring, but it clears stale sync states).
If you still don’t see it, remove the widget from the source device and add it again, then attempt sharing once more.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Shared widgets show stale or blank data
- Open the widget provider app and refresh its content normally.
- Disable Data Saver for the widget provider app if it’s enabled.
- Check Battery > Battery optimization and exempt the widget provider app from optimization for testing.
- Verify the widget’s network access: Wi‑Fi/cellular restrictions can cause blank states.
Beta builds can delay background updates. If the widget updates only after you open the app, that points to background execution limits rather than widget setup.
Updating breaks widget sharing
After a beta OTA, some apps need an additional update cycle. Try:
- Reboot after the update (if you didn’t already).
- Open Play Store > Manage apps > update anything related to the widget provider(s).
- Remove and re-add the widget from the home screen.
- Re-enable widget sharing controls in the widget settings (if present).
Battery drain after enabling shared widgets
- Check which app is refreshing most. Look at Settings > Battery > battery usage stats.
- Reduce the number of shared widgets while you test.
- For the widget provider app, confirm notifications/background data are enabled only if needed.
If drain is severe, disable shared widgets for the offending widget provider and wait for the next beta build or app update.
Permissions or notification prompts keep reappearing
This usually happens when an app’s permission is being reset by the beta update or when the permission state conflicts with the widget provider’s expected flow.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- Ultra-high Performance Chipset: This cell phone is equipped with a powerful and efficient Snapdragon 8s Gen 4 chip, using 4nm technology and a full-core 3.2GHz CPU, supporting 24GB LPDDR5X memory + UFS 4.0 flash memory, and equipped with an AI engine, with comprehensive performance upgrades.
- Revolutionary 50MP Quad Camera System: This smartphone is equipped with All 50MP four camera system: Including a Main Camera, a Periscope, an Ultra-wide Camera, and a ultra-clear Front Camera; this cell phone support Ultra XDR 4K video, Auto Tone, Portrait Optimiser, Motion Capture Mode, Night Mode; Whether you're a photographer, vlogger, or social media enthusiast, with the pro-grade camera system and AI enhancements, this Nothing phone can ensure every shot is masterpiece-ready.
- One-Touch Control, AI-Powered Organization:ESSENTIAL KEY: A new button on the side of your device.Press once to capture your screen, long-press to record voice and ideas, and double-press to access Essential Space; ESSENTIAL SPACE: Everything in one place, organised the way you want it to be,AI mobile phones helps organise your captures, generating suggestions, and staying on top of what matters; Explore more AI features, Let AI enrich your life
- GLYPH INTERFACE: Where Light Speaks; The Glyph Matrix transforms your phone into an interactive playground—smart animations turn notifications, tools, and games into living light experiences; NFC: An animation comes to life when NFC is triggered; Glyph Button: Quick-tap to browse Glyph Toys, long-press to launch—from utilities to games; Smarter Alerts: Notifications now speak in light and sound, blending visuals with meaning; Beyond illumination; This is interaction, redefined.
- Larger and Brighter FHD Display: 6.67" FHD+ 1.5K AMOLED flex screen with 1.07B colors & 120Hz adaptive refresh for ultra-smooth visuals; Vs Nothing Phone (2)/(3a): Phone (3) boasts 181.2% brighter (4500 nits), 16.7% sharper (460 PPI), and 316% faster touch response (1000Hz); IP68-rated—tough enough for any adventure.
- Go to Settings > Apps > select the widget provider.
- Check permissions like Notifications and Background data.
- Turn them on, then restart the widget provider app.
- If prompts continue, remove and re-add the widget.
Common mistakes to avoid
- Skipping backups and then discovering the beta update loop requires a wipe.
- Installing the beta while storage is low, causing failed downloads or repeated recovery prompts.
- Expecting instant sync on day one. Some sync queues only reconcile after the first background job completes.
- Using outdated widget provider apps. Android 15 changes can break widget update behavior.
Roll back or recover if you hit a beta wall
It’s smart to plan for rollback before you install any beta, even if you never need it. Widget-sharing features can be fixed quickly, but unstable builds sometimes require a return to stable.
Before you roll back: identify your current build and backup status
- Record About phone > Build number.
- Confirm your backup completed (photos, downloads, and critical app data).
- Note which widgets and apps were failing so you can retest after recovery.
What recovery options usually exist
Depending on how the beta was installed, options often include:
- Return to stable via OTA if Nothing provides a downgrade or stable enrollment switch.
- Recovery mode update using an official package (only if Nothing provides the correct file for your exact model/region).
- Service-center recovery if the device becomes unbootable or recovery can’t match the expected base version.
Don’t use unofficial firmware packages. For rollbacks, the base build matters—wrong packages can lead to boot loops or broken radios.
Android 15 beta vs stable builds: what to expect
Beta builds tend to be fine for testing, but they can include changes that affect:
- Background behavior (timing of sync and widget refresh)
- Permission handling (notifications, background data, widget binding)
- App compatibility (widget provider apps may need updates)
- Battery optimization (what’s allowed to run in the background)
If Shared Widgets feels “near correct” but inconsistent, that’s often an app-compatibility or permission issue rather than a widget feature failure.
FAQs about Android 15 beta and Shared Widgets on Nothing Phone (2a)
Will Shared Widgets work with every app widget?
No. Only widget providers that implement the right behavior (and are updated for the Android 15 beta environment) will reliably share. If a widget doesn’t show sharing options, it may not support it yet.
Do I need the same Nothing OS version on both devices?
Shared Widgets can be more reliable when both devices are on compatible software builds. If one device is stable and the other is on Android 15 beta, expect occasional sync delays or feature limitations.
Will my existing widgets automatically become shared?
Often they won’t. After an update, you may need to remove and re-add the widget so it gets bound to the new sharing logic. Then check the widget settings for sharing controls.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11How do I report a bug for Shared Widgets?
Use Nothing’s official feedback channel and include: your build number, the widget provider app name/version, what you expected, and a short reproduction path (for example: add widget on device A, wait 10 minutes, check device B, observe missing data).
Is it safe to keep Shared Widgets enabled on the beta?
It’s reasonable to keep it enabled while testing, but reduce risk by limiting the number of shared widgets, keeping apps updated, and monitoring battery usage. If something becomes unstable, disable the feature for the specific widget provider that’s misbehaving.
Bottom Line
If your Nothing Phone (2a) is getting the Android 15 beta with Shared Widgets, the best outcome comes from preparation: back up first, install via OTA when possible, update widget provider apps immediately, and test sharing with one widget before going broad.
When Shared Widgets doesn’t behave as expected, the fix is usually permissions, background execution, or app compatibility—not a mystery feature failure. Work through the troubleshooting steps in order, then decide whether you want to stay on beta until the next update improves stability.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




