• 0 Posts
  • 76 Comments
Joined 3 years ago
cake
Cake day: August 3rd, 2023

help-circle


















  • Android will never be a serious desktop operating system, and the reasons are pretty fundamental. You don’t have admin rights by default, which means you can’t truly control your own machine the way you can with any real desktop OS. Everything has to go through Java interfaces in the end, even when you try to use the NDK for native code. There’s this constant layer of middleware sitting between you and what you actually want to do, adding overhead and limiting what’s really possible.

    Compare this to Linux, Windows, or macOS where applications can directly access system resources when needed. You can compile native code that runs at full speed without virtualization layers. You can modify system files, install kernel modules, and actually own your computing environment. Android treats you like a guest on your own device. But the real dealbreaker is the complete lack of proper driver support. Try plugging in a WiFi dongle, a professional scanner, a printer that isn’t mainstream, or a racing wheel. You simply can’t install drivers for custom devices the way you can on Windows, Linux, or macOS.

    Android’s driver model is closed and locked to specific devices, not open to the kind of hardware ecosystem that desktop users have always relied on. On a real desktop OS, manufacturers can write drivers, users can compile them, and the community can support obscure hardware for decades. Android doesn’t work that way and never will.

    The whole architecture was designed for mobile consumption, not desktop creation. Professional software needs low-level system access and real performance without layers of abstraction getting in the way. Desktop OSes give you real file systems you can navigate freely, package managers or installers that put files where they need to go, and proper background processes. Android hides all of this behind its sandboxed app model. People keep talking about Android on desktops, but bolting on some desktop features doesn’t fix these fundamental architectural problems. It’s a mobile OS, and that’s what it will always be.


  • I will leave just this info here

    Technical Data

    Subject of Investigation: Google Play Services
    Number of Permissions: 277
    Operating System: Android 4.4.2 and above

    List of Permissions

    3.1. Automotive Systems Control

    Access to data and control of vehicle components via Android Auto/CarPlay:

    • Power windows
    • Tire pressure monitoring system
    • Rearview mirrors
    • Power system
    • Mileage data
    • Central door locking
    • Driving mode management
    • Seat adjustment
    • Vehicle speed data
    • Lighting system (headlights)
    • Battery
    • Climate control

    3.2. User Interface Manipulation

    • Embedding into application activities
    • Application substitution
    • Application icon modification

    3.3. “Chimera” Component

    System component of undetermined purpose.

    3.4. SMS Management

    Complete control of text messaging functions:

    • Sending messages
    • Receiving messages
    • Reading messages
    • Creating messages

    3.5. Root-Level System Privileges

    Complete device control at root-access level.

    3.6. Application Data Access

    • Access to all activities
    • Ability to embed into activities
    • Access to contacts

    3.7. USB Management

    Control of USB connections and data transfer.

    3.8. Identifier Access

    Access to all system and user device identifiers.

    3.9. Screen Lock Management

    Disabling keyguard (screen lock system).

    3.10. Mail Services Access

    • Access to email
    • Access to voicemail

    3.11. Network Function Management

    • Enabling/disabling network interfaces
    • Background data download
    • Modification of network settings

    3.12. Wi-Fi Management

    • Access to saved Wi-Fi passwords
    • Wi-Fi password transmission

    3.13. Audio Recording

    • Microphone audio recording
    • “Capture audio hotword” function (keyword capture)
    • Continuous audio stream monitoring for hotword detection

    3.14. Geolocation

    Complete control of location functions:

    • Location determination by all available methods
    • Independent enabling/disabling of geolocation services
    • “Allocate aggressive” mode (aggressive resource allocation for location determination)

    3.15. Payment Information Transmission

    Sending payment data without specified recipient restrictions.

    3.16. Camera Control

    Access to device camera.

    3.17. Telephony Function Management

    • Making calls
    • Access to call history
    • Control of telephone connections

    3.18. Permission Management

    Manipulation of other applications’ permissions:

    • Permission backup
    • Permission sharing
    • Permission revocation
    • Permission restoration

    3.19. Device Lock Management

    • Device locking
    • Device unlocking
    • Password protection bypass

    3.20. Biometric Authentication

    Complete control of biometric identification systems:

    • Fingerprint scanner
    • Facial recognition (Face ID)

    3.21. Notification Management

    Manipulation of system notifications:

    • SMS notification substitution
    • Call notification modification
    • Messenger notification modification

    3.22. Telephony Function Access

    • Access to telephony module
    • Call management

    3.23. Bluetooth Management

    Control of Bluetooth connections.

    3.24. Security Key Management

    • Encryption key substitution
    • Password reset

    Google Play Services is one of many pre-installed Google system components. A standard Android installation contains 30-50 additional Google applications with similar or complementary permission sets.

    IMG_20251111_032718_114 IMG_20251111_032717_685 IMG_20251111_032718_240 IMG_20251111_032717_935 IMG_20251111_032717_569 IMG_20251111_032717_629