Pros

• solid performance
• fast Wi-Fi
• great battery life
• fast charger included
• can work as a proper flashlight
• projector feature is worth every penny

Cons

• very heavy and unwieldy
• cameras fail to impress
• lights can run just 5 minutes at full brightness

Pros

• Premium design, IP68 certification.
• Larger and brighter OLED panel with Dolby Vision.
• Excellent camera performance, stills and videos, impressive telephoto cam.
• Fast wired and wireless charging.
• Dependable battery life
• Potent chipset.
• Feature-rich HyperOS with 5 years of major OS updates.

Cons

• No AF on the ultrawide, the selfie camera is underwhelming.
• 144Hz refresh rate is a gimmick.
• The wired charging is slightly downgraded.
• Becomes hot when chipset is pushed for long periods.

Google uses machine learning technologies to estimate a user’s age by analysing search terms and content viewed online, among others.

I am curious about the various Android Lemmy clients available, specifically which ones allow users to switch between instances or accounts. I am interested in the ability to view different local feeds across multiple instances seamlessly. If you have any recommendations, I would love to hear your thoughts!

cross-posted from: https://lemmy.ca/post/52720355

I am using neo backup often i run into storage issues so i am wondering if there is a possibility of backing data with git, root, Termux, Tasker .

Edit: solved some issues

• storage issue was fixed by not enabling unnecessary backup options. It created massive difference for most applications, eg anki was over 1 GB, now its 9 KB.
• Some application's backups were not working( After restoring applications were crashing), for them, rather than backing up whole data, we can copy relevant data. Eg for element, we can backup by

cp /data/data/im.vector.app/shared_prefs/im.vector.app_preferences.xml %ConfigBackupLocation/element

1. Does this mean sideloading is going away on Android?

Absolutely not. Sideloading is fundamental to Android and it is not going away. Our new developer identity requirements are designed to protect users and developers from bad actors, not to limit choice. We want to make sure that if you download an app, it’s truly from the developer it claims to be published from, regardless of where you get the app. Verified developers will have the same freedom to distribute their apps directly to users through sideloading or through any app store they prefer.

2. Making APKs available to your test team

If your team’s current test process relies on distributing APKs to testers for installation using methods other than adb, you will need to verify your identity and register the package. This also applies if you make APKs available to your test teams through Google Play Internal Testing, Firebase App Distribution, or similar solutions through other distribution partners.

3. Do I still need to register my apps if I’m only distributing to a limited number of users?

We recommend you register. It's a simple, one-time process that will allow anyone to download and install your app. However, if you prefer not to, we are also introducing a free developer account type that will allow teachers, students, and hobbyists to distribute apps to a limited number of devices without needing to provide a government ID.

4. What can I do to prepare for developer verification?

The best way to get ready and stay updated is to sign up for early access. We’ll start sending invitations in October.

We recommend you participate in developer verification because, even though verification is not required to develop apps with Android Studio, you will need it to distribute apps to certified Android devices. Apps installed through enterprise management tools on managed devices will also be installable without being registered.

A OnePlus spokesperson gave 9to5Google the following statement:

We acknowledge the recent disclosure of CVE-2025-10184 and have implemented a fix. This will be rolled out globally via software update starting from mid-October. OnePlus remains committed to protecting customer data and will continue to prioritize security improvements.

As for how this happened, essentially, OnePlus seemingly modified the stock Telephony app back in the Android 12 days — this bug doesn’t exist in OxygenOS 11 — to add additional content providers into the service, including the following three listings:

• com.android.providers.telephony.PushMessageProvider

• com.android.providers.telephony.PushShopProvider

• com.android.providers.telephony.ServiceNumberProvider

Modifying this package isn’t inherently bad, obviously, but when you’re dealing with something that can provide read and write access to messages stored on device, you need to take additional steps to ensure you aren’t leaving vulnerabilities — and that’s exactly what happened here. While OnePlus assigned read permissions for SMS messages to these providers, it failed to add write permissions, which, as Rapid7‘s blog post states, “may allow client apps to perform writer operations, if the relevant write […] operation is implemented within the provider.”

For now, OnePlus users should tread cautiously until that patch rolls out in mid-October. Rapid7 suggests only installing apps from known sources and removing all non-essential apps. If you receive OTP texts for 2FA logins, you’ll also want to switch to an authenticator app as soon as possible to prevent your code from being sent over SMS. Switching to a third-party chat application can also help in this regard.

I didn't find any articles about this, so I apologize if my understanding is incorrect.

Plant-it was a self-hosted gardening companion platform, similar to HortusFox. It seems that the project used to have a self-hosted backend, and due to development difficulties, they are focusing on the Android app only. If you are looking for a selfhosted option, the recommendation seems to be https://www.hortusfox.com/

Excerpts from the Changelog:

[!CAUTION] Read the following before upgrading the app.

We are thrilled to share some significant changes to our open source app project that will enhance your experience and simplify usage.

TL;DR

The app is now fully focused on the frontend, eliminating the backend. This simplifies installation and development but means the iOS and web versions are discontinued. Users will need to re-enter their data in the new version. Upgrade if you want a better app; iOS/web users should not upgrade.

Background

The previous setup of our project, which included a backend (Spring Boot) and a frontend (Flutter), has proven to be quite error-prone. The majority of issues stemmed from the backend and its complex setup, leading to unnecessary complications in our architecture. This complexity has resulted in errors and slowed down development, making it challenging to deliver a seamless experience.

Key Updates

The app is now fully focused on the frontend, eliminating the need for a backend. This means you can simply install and launch the app on your mobile device without worrying about backend deployment issues. With the codebase now exclusively in Flutter, we can develop and resolve bugs more quickly than ever before. This shift makes the project significantly simpler and more efficient.

Important Changes

While these updates bring many benefits, there are some downsides to consider:

• No More iOS/Web Version: Unfortunately, the iOS and web versions of the app will no longer be available. Although the iOS version was not accessible before, users could install the web app on iOS devices. This option is now discontinued.

• For iOS Users: We understand that some of you may be unhappy with this decision. If you are currently using the app on iOS, we recommend sticking with version 0.10.0. This version will remain available but will not receive further updates.

What Now?

You can download the first release from the release asset. Please note that you will need to re-insert all your data (plants, photos, reminders, etc.), as there is no mechanism to copy the database due to the architectural changes. We welcome your feedback to help us enhance the app further.

Who Should and Should Not Upgrade

If you want a better app and future updates, you should definitely upgrade to the new version. However, if you are an iOS or web user, we recommend that you do not upgrade.

Future Possibilities

We are actively exploring alternatives that may allow us to reintroduce iOS and web support in the future. Stay tuned for updates.

Thank you for your continued support and understanding as we make these changes. We believe these improvements will lead to a better user experience and a more robust app overall. Happy gardening! 🌱

The future of this elegant and proven system was put in jeopardy last month, when Google unilaterally decreed that Android developers everywhere in the world are going to be required to register centrally with Google. In addition to demanding payment of a registration fee and agreement to their (non-negotiable and ever-changing) terms and conditions, Google will also require the uploading of personally identifying documents[^regid], including government ID, by the authors of the software, as well as enumerating all the unique “application identifiers” for every app that is to be distributed by the registered developer.

If it were to be put into effect, the developer registration decree will end the F-Droid project and other free/open-source app distribution sources as we know them today, and the world will be deprived of the safety and security of the catalog of thousands of apps that can be trusted and verified by any and all. F-Droid’s myriad users5 will be left adrift, with no means to install — or even update their existing installed — applications.

TL; DR

Android 17 will add a 3rd companion role profile called medical profile. Apps using this profile get default access to notifications, exact alarms, bluetooth. Apps using this role will be prioritized over standard battery and memory savings of android – reduce chances of being killed.

We’ll start with the CPU; the third revision of Qualcomm’s custom Oryon CPU cores built on the Arm architecture. Qualcomm cranked the Prime core peak clock speeds up to 4.6GHz, from an already speedy 4.32GHz with the Snapdragon 8 Elite, while the Performance cores can hit 3.62GHz. Combined with some architecture and cache revisions, Qualcomm claims this can result in up to 20% better performance with 16% better power efficiency.

The performance claims hold up reasonably well against last year’s reference unit in Geekbench 6 (yes, I’ve been keeping tabs). Single and multi-core performance registers 19% gains. More impressive, though, is that if you go back two years, the 8 Elite Gen 5 is 65% faster in both tests than the Snapdragon 8 Gen 3. That’s a massive increase in peak performance in just two years — those custom CPU cores really have paid dividends.

Looking at some real handsets, we can see roughly where upcoming Gen 5 phones will sit. Qualcomm’s new chip flies past the capabilities of Google’s Tensor G5, and its multi-core score even leaves Apple’s new A19 Pro chip in the dust — it’s 25% faster. While far more performance than you need for browsing the web, this super-quick multi-core score will come in handy for video editing, gaming, and perhaps even running AI tasks directly on the CPU, especially now that the Snapdragon’s CPU supports SME.

cross-posted from: https://lazysoci.al/post/34675803

One of the biggest stories out of Qualcomm’s Snapdragon Summit in Maui isn’t just about Qualcomm — it’s how Google is finally merging Android and ChromeOS to create a new operating system for computers. Qualcomm CEO Cristiano Amon revealed that it’s finally happening, and now, a Google exec has revealed when it’s happening, too.

It’s “something we’re super excited about for next year,” said Google’s Sameer Samat, head of Android Ecosystem, at the tail end of Qualcomm’s announcement keynote.

No, I'm not excited at all