Enable Samsung DeX using Taskbar 6.0 on some Android Devices.
Android 10’s most exciting feature was desktop mode but it is still widely unknown. Samsung DeX is an extension of Android N’s Multi-Window mode which allows your device to cast a PC-like experience to the big screen with the same apps you use on your phone every day.
Android 10 added a secondary launcher which comes into play when an Android device with support for display output is hooked up to an external display. This Secondary Launcher activity is shown on the external display. This Secondary Launcher is barebones, it’s not useful as a productivity tool.
XDA Senior Member farmerbb has replaced the stock launcher on the external display and implemented it in Taskbar 6.0. The taskbar is an open-source Android app that puts a floating start menu and recent apps on top of any screen.
Taskbar supports launching Android apps freeform multi-window. Previously, farmerbb released a fork of the open-source Lawnchair launcher with Taskbar integrated into it but it had some issues. Now, farmerbb has updated Taskbar to version 6.0 to address all of the previous issues.
Desktop Mode with Taskbar 6.0
Setting up Taskbar’s desktop mode-
In Developer Options, turn on “enable freeform windows” and “force desktop mode” and then reboot your device. (The latter may be unavailable on some OEM software like ZenUI/ROG UI, but don’t worry if it’s not there.)
Install Taskbar 6.0 (older versions won’t work) from Google Play.
Open Taskbar’s settings and go to “Desktop Mode.” Enable it and grant the app permission to “display over other apps” as this is required for the app’s floating start menu to appear. Then, set the app as your default home app. Don’t worry, though, as the next prompt will ask you to set your preferred/primary launcher app, so Taskbar won’t be hijacking your home screen. (Note that on some devices, changing the default launcher will disable Android 10’s full-screen navigation gestures.)
Next, I highly recommend you follow the instructions to “enable additional settings” for desktop mode. This will allow you to lower the DPI so UI elements aren’t enormous on the external display, to hide the navigation bar, and to even dim the phone’s screen to save battery life while it’s connected to the external display. You’ll have to set up ADB access on your PC and run the following command:
adb shell pm grant com.farmerbb.taskbar android.permission.WRITE_SECURE_SETTINGS
(If you are using Taskbar’s “Donate” version, replace “com.farmerbb.taskbar” with “com.farmerbb.taskbar.paid” in the above command.)
Finally, check to make sure that “usage access” has been enabled for Taskbar. Doing so will allow the app to show a row of your recently used applications in the start menu.
Now, simply connect your phone to your external display using a USB Type-C to Type-C cable (if your external display supports Type-C input) or via a USB Type-C to HDMI adapter.
Once connected, you can use the start menu to launch apps, search for apps, add app icons to the home screen, open some system menus, and more. You can tap the icon next to the start menu to add/show widgets. You can launch multiple instances of windows and in some cases like Google Chrome, have multiple tabs.
There are loads of other options and changes in Taskbar 6.0, read the full changelog available here.
Download Taskbar 6.0
If you have one of the following smartphones, try this app:
Ashok Mor (also known as TechiBee) owns a YouTube channel named TechiBee. He has been providing various tips, tricks and latest tech videos in the world of smartphones.
Samsung Galaxy S26+ is shaping up to be one of the most unexpected releases in Samsung’s 2026 flagship lineup.
Samsung Galaxy S26+ is shaping up to be the most compromised model in Samsung’s upcoming flagship lineup, according to fresh reports from South Korea. New details suggest that the device will miss out on a major display upgrade due to last-minute internal decisions during development.
As per industry insiders cited by The Elec, Samsung Electronics initially planned a different lineup strategy. The company was working on a Galaxy S26 Edge model, which was later scrapped late in the development cycle. To fill the gap, Samsung brought back the Galaxy S26+—but the timing appears to have caused several compromises.
Samsung Galaxy S26+ Production and Display Decisions Explained
Originally, Samsung intended to reuse the newly developed display panel from the cancelled S26 Edge for the S26+. However, this plan was reportedly dropped at the last moment. With no time left to engineer or source an alternative panel, the Galaxy S26+ is now expected to ship with a display that is almost identical to the one used on the Galaxy S25+. The only notable change may be the use of a newer protective glass layer, rather than a fundamentally improved panel.
For many users, the lack of a Samsung Galaxy S26+ display upgrade could make the Plus model less appealing compared to other variants.
Interestingly, the base Galaxy S26 is not facing the same issue. Reports indicate that it will feature a new 6.27-inch display, slightly larger than the 6.16-inch panel on the Galaxy S25. This suggests that Samsung prioritized upgrades for the entry-level model while the Plus variant took a back seat.
The situation is very different for the Galaxy S26 Ultra. The Ultra model reportedly entered mass production as early as last month. Samsung appears to have prioritized component sourcing and manufacturing capacity for its top-tier flagship, which aligns with early production targets.
Current estimates suggest initial production of around 3.6 million Galaxy S26 Ultra units, compared to 700,000 standard Galaxy S26 models and just 600,000 Galaxy S26+ units. These figures are expected to be revised in February, with Samsung likely increasing output for the vanilla plus models while reducing Ultra volumes.
Overall, the Samsung Galaxy S26+ appears to be a strategic compromise rather than a fully refreshed flagship.
The Galaxy S26 series is rumored to launch on February 25, slightly later than last year’s timeline, though official confirmation is still pending.
Google Fast Pair vulnerability has raised serious concerns after security researchers revealed a flaw that could allow hackers to take control of Bluetooth audio devices, including access to microphones. The issue, dubbed WhisperPair, affects 17 certified headphones and speakers from major brands, highlighting risks associated with improper Fast Pair implementation.
The Google Fast Pair vulnerability highlights serious security gaps in Bluetooth audio devices that rely on improper Fast Pair implementation.
Due to the Google Fast Pair vulnerability, attackers within Bluetooth range can potentially hijack headphones without user interaction.
Updating firmware is currently the most effective way to reduce risks associated with the Google Fast Pair vulnerability.
Google Fast Pair Vulnerability Explained
Researchers from KU Leuven discovered that some audio accessories using Google’s Fast Pair protocol fail to restrict new connections properly. Under normal circumstances, Fast Pair should only allow pairing when a device is in pairing mode. However, due to faulty implementation by certain manufacturers, attackers within Bluetooth range could hijack devices in seconds using just the model number.
According to the researchers, this exploit can enable microphone access, audio injection, and even location tracking. The findings were first reported by Wired, which detailed how attackers could silently pair with headphones already in use.
Affected Brands and Devices
The vulnerability impacts devices from Sony, Jabra, JBL, Marshall, Xiaomi, Nothing, OnePlus, Soundcore, Logitech, and Google. Google confirmed that affected Pixel Buds have already been patched. All impacted products had previously received Google Fast Pair certification.
Google’s Response and Ongoing Risks
Google stated that it shared recommended fixes with hardware partners in September and updated its certification and validation tools. While the company claims there is no evidence of real-world exploitation beyond lab testing, researchers warn that many users may remain exposed due to outdated firmware.
A particularly concerning scenario involves unpaired accessories. If a device has never been linked to a Google account, an attacker could pair it to their own account and track it using Google’s Find Hub network. Although Google says it patched this loophole, researchers reportedly found a workaround shortly after.
How Users Can Protect Themselves
Security experts strongly advise users to update their Bluetooth audio devices to the latest firmware. This often requires installing the manufacturer’s companion app—something many users skip. Keeping Bluetooth off when not in use and avoiding pairing in public spaces can also reduce risk.
Android 16 QPR3 Beta 2 is now rolling out, and it marks a significant step forward in Google’s ongoing effort to refine the Android experience on Pixel smartphones. The update arrives shortly after the previous beta, showing Google’s aggressive pace in polishing the upcoming Quarterly Platform Release. It is available in two build versions: CP11.251209.007 for the Pixel 6 and Pixel 7 series, and CP11.251209.007.A1 for all other supported Pixel models.
Android 16 QPR3 Beta 2 focuses on performance, stability, and usability
Android 16 QPR3 Beta 2 brings a wide range of under-the-hood improvements aimed at fixing some of the most common issues faced by Pixel users in recent builds. According to Google, this release addresses multiple stability, performance, and usability issues, making daily usage smoother and more reliable.
Users who have been dealing with random app crashes, system freezes, or lag should notice a clear improvement after installing this update. Battery performance has also been optimized, with fixes targeting excessive battery drain and inconsistent charging behavior. These changes are expected to be especially noticeable during extended screen-on time and overnight standby.
Connectivity has received a strong boost as well. Android 16 QPR3 Beta 2 improves Wi-Fi reliability and speed while also enhancing call stability, reducing dropped calls and network-related interruptions. Alongside these changes, Google has refined parts of the user interface, resulting in smoother animations and more consistent system behavior.
Google has shared a detailed changelog for this beta, and some of the most notable improvements were highlighted directly by the company on Reddit, giving early testers a clear idea of what to expect.
How to try Android 16 QPR3 Beta 2 on your Pixel
If you are interested in testing Android 16 QPR3 Beta 2, you can enroll your compatible Pixel device in the Android Beta Program. Before installing, it is strongly recommended to back up all important data, as beta software can still contain unresolved bugs.
Overall, Android 16 QPR3 Beta 2 feels like a mature and meaningful update, bringing Pixel devices closer to a stable and polished Android 16 release.
Setting up Taskbar’s desktop mode-
