Hasty Briefsbeta

All tags

#android

123 stories total

Bilingual

Google confirms it's 'combining' Chrome OS and Android into a single platform
10 months ago
- Google executive confirms plans to combine Chrome OS and Android into a single platform.
- The initiative was first reported in November, with Chrome OS being merged into Android.
- Android 16 introduces desktop-themed features, supporting the merger.
- Google is gathering feedback on laptop usage to refine the project.
- Concerns include potential impacts on Chromebook updates and hardware requirements.
Shizuku: Unlocking Advanced Android Capabilities Without Root
10 months ago
- Shizuku is an Android app that allows other apps to use system APIs with elevated privileges without requiring full root access.
- It works by starting a Java process with app_process using ADB for non-rooted devices or root privileges for rooted devices.
- Shizuku can be started via Wireless ADB (Android 11+), using a PC with ADB, or directly on rooted devices.
- Popular apps that work with Shizuku include Android Debloater, VolumeManager, PhoneProfilesPlus, and Termux.
- Setting up Termux with Shizuku involves using 'rish' for elevated ADB-level privileges.
- Cybersecurity use cases include listing running processes, network monitoring with netstat, viewing Wi-Fi passwords, and accessing logcat.
- NetGuard is a firewall solution that can be used with Shizuku to control internet access per app.
- Shizuku is a powerful tool for Android power users, enabling advanced functionality without full root access.
Google confirms it's merging ChromeOS and Android
10 months ago
- Google confirms merging ChromeOS and Android into a single platform.
- ChromeOS has supported Android apps via a VM, but full integration is new.
- Concerns about merging two distinct OS designs for different use cases.
- ChromeOS is seen as secure and immutable, while Android is customizable.
- Business perspective suggests ChromeOS lacks profitability compared to Android.
- Educational sector heavily relies on Chromebooks, raising concerns about transition.
- Technical challenges include running foreign OS/programs on Android.
- User frustrations with Chromebook limitations and locked-down hardware.
- Android's global presence vs. ChromeOS's US-centric adoption.
- Potential future moves by Alphabet to restructure and bundle assets.
Google Keeps Making Smartphones Worse
10 months ago
- Google has been gradually reducing Android's open-source capabilities over the past decade.
- Modern smartphones, despite advanced hardware, often make users feel powerless due to excessive notifications and intrusive AI like Gemini.
- Android initially allowed users to modify and share its code freely, enabling privacy-focused and environmentally conscious alternatives like LineageOS and GrapheneOS.
- Google has started locking away source code, delaying competitor development, and moving key features to proprietary versions.
- The Play Store is filled with predatory apps and games designed to exploit users financially and psychologically.
- Excessive smartphone use is linked to mental health issues like depression, anxiety, and insomnia.
- Consumers are increasingly turning to 'dumb' phones to escape the toxic smartphone environment.
- There is a demand for a truly open-source mobile OS that prioritizes user needs over corporate profits.
I want an iPhone Mini-sized Android phone (2022)
10 months ago
- Eric Migicovsky announces the Small Android Phone project to rally support for a premium small Android phone.
- Current premium Android phones lack options with displays under 6 inches, creating a gap in the market.
- The ideal small phone prioritizes size (under 6 inches), premium build quality, and stock Android, with flexible other specs.
- Target price range is $700-800, acknowledging the niche market's willingness to pay more for desired features.
- The project aims to gather at least 50,000 interested buyers to convince manufacturers to produce the phone.
- Eric has a background in hardware (Pebble smartwatch) and connections in the industry to potentially lead the project if necessary.
- The discontinuation of the Sony Xperia Compact line has left no alternatives for small premium Android phones.
- Eric switched to iPhone due to the lack of small Android options but criticizes iOS for its notification system and file management.
- The iPhone Mini's potential discontinuation could open a market opportunity for a small Android alternative.
- Community support is crucial to pressure manufacturers into considering the production of a small premium Android phone.
Billions of phones can detect and warn about nearby earthquakes
9 months ago
- Google's Android Earthquake Alerts system uses 2.3 billion devices as a global earthquake-detection network.
- The system detects earthquakes via accelerometers in Android phones and smartwatches, providing alerts for magnitudes of 4.5 or greater.
- It supplements traditional seismometer-based systems, especially in regions lacking early-warning infrastructure.
- The network has issued alerts for 1279 seismic events with only three false alarms as of March 2024.
- Users receive two types of alerts: urgent 'Take Action' warnings and less intrusive 'Be Aware' notifications.
- The system is as accurate as established programs like ShakeAlert in the US and Japan's Meteorological Society.
- Alerts are available in 98 countries, focusing on high-risk areas without existing warning solutions.
Android Earthquake Alerts: A global system for early warning
9 months ago
- Android Earthquake Alerts system uses smartphone accelerometers to detect earthquakes and provide early warnings.
- The system detects initial P-waves, analyzes data from multiple phones, and sends alerts before damaging S-waves arrive.
- Two types of alerts: BeAware for light shaking and TakeAction for stronger shaking, which takes over the phone screen.
- Since 2021, the system has detected over 18,000 earthquakes and sent 790 million alerts in nearly 100 countries.
- The system has increased access to earthquake early warnings from 250 million to 2.5 billion people globally.
- Improvements in magnitude estimation have reduced median absolute error from 0.50 to 0.25, matching or surpassing traditional seismic networks.
- Examples include a M6.7 quake in the Philippines (2.5M alerts), M5.7 in Nepal (10M alerts), and M6.2 in Turkey (11M alerts).
- User feedback shows 85% find alerts helpful, with 79% appreciating alerts even if no shaking is felt.
- TakeAction alerts effectively prompt life-saving actions like 'Drop, Cover, and Hold On.'
- Future goals include improving prediction models and providing rapid post-earthquake information to emergency responders.
Graphene OS: a security-enhanced Android build
9 months ago
- GrapheneOS is a security-enhanced Android build that started as CopperheadOS, later rebranded after a dispute between founders.
- It focuses on hardening Android against threats and enhancing user privacy, based on the Android Open Source Project but with significant modifications.
- Supported devices are limited to Google Pixel 6 through 9, with some support for Pixel 4 and 5, emphasizing security features like hardware memory tagging.
- Installation can be done via web-based or command-line methods, with the web method noted as more reliable.
- GrapheneOS offers a minimalist setup with its own apps like Vanadium (a hardened Chromium fork) and a privacy-focused camera app, avoiding Google apps by default.
- It includes sandboxed Google Play for compatibility, allowing apps to run without special privileges, though some apps may refuse to work due to integrity checks.
- Security features include enhanced app permissions, storage and contact scopes, a duress PIN for data wiping, and frequent updates.
- Governance is opaque, with a foundation supporting development but little public information on operations or contributors beyond founder Daniel Micay.
- Users report positive experiences with GrapheneOS, appreciating its security and privacy controls, though some proprietary apps may still be necessary for full functionality.
You can run Doom and other graphical apps in Android's Linux Terminal
9 months ago
- Android’s Linux Terminal app now supports graphical Linux apps in the latest Canary build.
- A new 'Display' button enables a graphical environment, allowing users to run desktop apps not available on Android.
- Hardware acceleration can be enabled for better performance, expanding possibilities for running Linux software and games.
- The Terminal app runs Debian in a virtual machine, offering full-fledged Linux app support.
- Graphical app support was previously only available by compiling Android from source.
- Weston, a Wayland compositor, is preinstalled and can be launched with the 'weston' command.
- Hardware acceleration requires creating a specific file in the '/sdcard/linux' directory.
- Graphical app support is a significant step toward merging Chrome OS and Android.
- The feature's release timeline for Beta or Stable channels is uncertain, with hopes for Android 16's December update.
Setting up Android phone to work with Apple Watch and iMessage
9 months ago
- Purchased an old iPhone with a physical SIM card to facilitate the setup process.
- Transferred data from the existing iPhone to the old iPhone, managing storage constraints.
- Visited AT&T store to transfer the phone number to the old iPhone and ensure Apple Watch functionality.
- Moved the SIM card to the Android phone, confirming calling and SMS worked.
- Waited for Apple to deregister the phone number from iMessage after detecting no active iPhone.
- Returned to AT&T to get a new SIM card for the old iPhone and reactivate the number.
- Enabled RCS Messaging on the Android phone and ensured iMessage synced with iCloud.
- Performed a tricky SIM card swap and editing process on the iPhone to maintain iMessage functionality.
- Used BlueBubbles.app to bridge iMessages to the Android phone, requiring a Mac (rented from MacInCloud.com).
- Set up BlueBubbles server on the rented Mac and installed the client on the Android phone for full iMessage functionality.
Injecting Java from native libraries on Android
9 months ago
- Android presents unique challenges for Rust developers due to limited access to certain OS functions compared to desktop platforms.
- Advanced phone capabilities, like Bluetooth control, are only accessible via Android's Java SDK, not through native libraries like libc or the NDK.
- JNI (Java Native Interface) allows Rust to interact with Java APIs, enabling the use of Java classes and methods from native code.
- Previously, it was believed that Rust on Android couldn't create new Java classes, only instantiate existing ones, limiting functionality.
- For app developers, adding necessary Java classes isn't an issue, but it's problematic for Rust library developers whose users might not know to include these classes.
- Android's JNI documentation states that `DefineClass` isn't supported, but using `DexClassLoader` allows injecting pre-compiled Java classes at runtime.
- Rust crates can embed and inject Java classes (via `classes.dex`) into the JVM, making the process seamless for users.
- The process involves compiling `.java` files into `.class` files, converting them to `classes.dex`, embedding them in the Rust library, and loading them at runtime.
- This technique, though not widely known, enables modular Rust libraries on Android, similar to the ease of iOS development with C or ObjC interfaces.
- Examples include the `slint` and `netwatcher` crates, which use this approach to provide Java helpers without user intervention.
Google to require developer verification to install and sideload Android apps
8 months ago
- Google will require verified developers for app installations on certified Android devices starting in 2026.
- The rule applies to all installation methods, including third-party stores and sideloading.
- Google aims to reduce malware and financial scams by verifying developer identities.
- A new Android Developer Console will be created for non-Play Store developers.
- Students and hobbyists will have a separate verification process.
- The requirement starts in September 2026 in Brazil, Indonesia, Singapore, and Thailand, then globally from 2027.
- Government authorities in these countries have provided positive feedback on the initiative.
Google to require developer verification for Android apps outside the Play Store
8 months ago
- Google is tightening security measures for Android app distribution by verifying developer identities, starting next year.
- The verification will apply to all certified Android devices, with a gradual global rollout.
- Developers can still distribute apps outside the Play Store, but anonymity will no longer be an option.
- Google aims to reduce malware, financial fraud, and data theft by requiring developer verification.
- Early access for developers to test the system will begin in October 2025, with full rollout by March 2026.
- By September 2026, apps in Brazil, Indonesia, Singapore, and Thailand must meet the new requirements.
- Global rollout of the requirements will start in 2027.
- Developers must provide legal name, address, email, and phone number, potentially pushing independents to register as businesses.
- Student and hobbyist developers will have a separate Android Developer Console account option.
- Similar to Apple's EU App Store changes, Google's move aligns with increasing regulatory demands like the DSA.
Google feedback form for Android developer verification requirements
8 months ago
- The text is a form for submitting questions or feedback about new Android developer verification requirements announced in August 2025.
- Users can learn more about the requirements in the Android developer verification guide and sign up for early access.
- The form requires users to log in with Google to save their responses.
- It asks for the user's email address and the platforms or methods they use to distribute their apps (multiple options provided).
- Users are also asked to describe their question, feedback, or issue in detail.
- The form includes a note about not sending passwords via Google Forms and mentions that the form was created within Google.com.
- There are links to privacy policies, terms of service, help, feedback, and contacting the form owner.
Conversations 2.19.4 released – open-source Jabber/XMPP client for Android
8 months ago
- Conversations is a Jabber/XMPP client for Android 5.0+ smartphones, optimized for mobile use.
- Supports file sharing, image embedding in chats, and end-to-end encryption for privacy.
- Features read receipts, message history loading, and multi-device synchronization.
- Easy group chat creation with automatic server-side group setup and contact invitations.
- Independent of Google’s push messaging system (GCM), with minimal battery impact.
- Open-source under GPLv3, available on Codeberg for review and modification.
- Uses XMPP, a federated protocol with TLS encryption for secure communication.
- Supports OMEMO and OpenPGP for end-to-end encryption.
- Compatible with various XEPs for improved reliability and user experience.
- Includes features like Stream Management, Client State Indication, and Message Carbons.
- Allows profile picture uploads and integrates with Android address book (F-Droid version only).
- Supports secure video calls via Jingle and WebRTC.
- Offers professional support and customization services.
- Available for purchase on Google Play Store with beta access.
- Recommends using or hosting your own XMPP server for better control and privacy.
Is it possible to allow sideloading *and* keep users safe?
8 months ago
- Google's new policy requires Android apps to be digitally signed by developers registered with Google, potentially ending sideloading.
- The debate centers on user freedom versus security, with concerns about scams and malware from sideloaded apps.
- Banks and game developers may restrict app usage on rooted or modified devices to mitigate risks.
- Google argues that sideloaded apps pose significant security risks, citing high malware rates compared to Play Store apps.
- Despite warnings, users often ignore security prompts, leading to scams and financial losses.
- Google's policy will initially roll out in Brazil, Indonesia, Singapore, and Thailand, targeting high-fraud regions.
- Critics argue Google's move is a power grab, limiting developer freedom and open-source projects.
- Potential solutions include better user education, alternative trust stores, or AI-based scam detection.
- Comments highlight concerns about Google's gatekeeping and the balance between security and user freedom.
Meta and Yandex Disclosure: Covert Web-to-App Tracking via Localhost on Android
8 months ago
- Meta and Yandex use localhost sockets on Android to track users by linking web browsing data with native app identifiers.
- This tracking method bypasses privacy protections like Incognito Mode, cookie clearing, and Android permissions.
- Meta's Pixel script sends the _fbp cookie via WebRTC to Facebook and Instagram apps listening on specific UDP ports.
- Yandex Metrica script sends HTTP/HTTPS requests to localhost ports, collecting device IDs and linking them to web activity.
- Both methods operate without user consent, even on sites without explicit cookie consent forms.
- Malicious apps can eavesdrop on browsing history by listening to the same localhost ports used by Meta and Yandex.
- Meta Pixel is embedded on over 5.8 million websites, while Yandex Metrica is present on close to 3 million sites.
- Browser vendors like Chrome, Firefox, and Brave have implemented or are developing mitigations against this tracking method.
- No public documentation from Meta or Yandex explains this tracking technique, raising transparency concerns.
- The tracking affects Android users globally, with no evidence of similar abuse on iOS or other platforms yet.
Google Will Require Developer Verification
8 months ago
- Google will require developer verification for all apps on certified Android devices, including sideloaded apps and those from alternative stores like F-Droid.
- Verification will involve submitting government ID and contact information, similar to current Google Play Store requirements.
- The changes will be trialed starting October 2025, with global rollout expected by 2027.
- Critics argue this move will eliminate Android as an open alternative to iOS, harming hobbyists and open-source developers.
- Suggestions to use de-googled Android ROMs and open-source alternatives like Linux, Matrix, and Mastodon are provided.
- Comparisons are made to Linux distribution models, highlighting issues with central repositories and maintainer bottlenecks.
- Concerns about privacy, government surveillance, and the erosion of digital freedoms are raised.
- Potential workarounds like using Termux or creating custom repositories are discussed, though with noted limitations.
- The impact on piracy, old apps, and independent developers is questioned.
- The broader trend of tech companies tightening control over devices and software is criticized.
FreeDroidWarn
8 months ago
- Google will require developer verification for Android apps outside the Play Store from 2026/2027.
- Developers must submit personal identity details to Google for apps to work on certified Android devices.
- This app will not comply with the new requirement and will stop working on certified devices after 2026/2027.
- Add the JitPack repository to your root build.gradle file.
- Include the library dependency 'com.github.woheller69:FreeDroidWarn:V1.3' in your build.gradle.
- Call 'FreeDroidWarn.showWarningOnUpgrade(this, BuildConfig.VERSION_CODE);' in your app's onCreate method.
- The library is licensed under GPLv3.
This blog is running on a recycled Google Pixel 5
8 months ago
- The blog is hosted on a recycled Google Pixel 5, showcasing the use of an Android phone as a server.
- Inspiration came from Mastodon posts about running sites on minimal hardware like ESP32 microcontrollers and Android devices with solar panels.
- The Pixel 5 was chosen for its USB-OTG support, ethernet capability via docks, and being the most updated phone available to the author.
- The blog is solar-powered using a 100w panel connected to a Jackery power station, aligning with permacomputing principles.
- Termux, a terminal emulator for Android, was used to set up the blog with Hugo, git, and other utilities without needing a full Linux environment.
- The setup includes SSH for remote management, cron jobs for automatic blog reloading, and rsync for backups to desktop and NAS.
- The author highlights the simplicity and reliability of running a blog on an Android phone, with performance comparable to traditional servers.
- Future plans include maintaining the current setup unless issues arise, with openness to feedback and further write-ups on specific components like dufs for file management.

first prev2next

About|Login

#android

Google confirms it's 'combining' Chrome OS and Android into a single platform

Shizuku: Unlocking Advanced Android Capabilities Without Root

Google confirms it's merging ChromeOS and Android

Google Keeps Making Smartphones Worse

I want an iPhone Mini-sized Android phone (2022)

Billions of phones can detect and warn about nearby earthquakes

Android Earthquake Alerts: A global system for early warning

Graphene OS: a security-enhanced Android build

You can run Doom and other graphical apps in Android's Linux Terminal

Setting up Android phone to work with Apple Watch and iMessage

Injecting Java from native libraries on Android

Google to require developer verification to install and sideload Android apps

Google to require developer verification for Android apps outside the Play Store

Google feedback form for Android developer verification requirements

Conversations 2.19.4 released – open-source Jabber/XMPP client for Android

Is it possible to allow sideloading *and* keep users safe?

Meta and Yandex Disclosure: Covert Web-to-App Tracking via Localhost on Android

Google Will Require Developer Verification

FreeDroidWarn

This blog is running on a recycled Google Pixel 5

Is it possible to allow sideloading and keep users safe?