<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Viktor Mukha on Medium]]></title>
        <description><![CDATA[Stories by Viktor Mukha on Medium]]></description>
        <link>https://medium.com/@viktor.mukha?source=rss-7ac49f590be8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kEgX_lrRbEJikOyzAlUtSQ.jpeg</url>
            <title>Stories by Viktor Mukha on Medium</title>
            <link>https://medium.com/@viktor.mukha?source=rss-7ac49f590be8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:14:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@viktor.mukha/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building Apps for Cars in 2026: Android Auto, AAOS, and Vehicle Data APIs]]></title>
            <link>https://medium.com/paradox-cat-tech-hub/building-apps-for-cars-in-2026-android-auto-aaos-and-vehicle-data-apis-ac627ba9fc8e?source=rss-7ac49f590be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac627ba9fc8e</guid>
            <category><![CDATA[android-auto]]></category>
            <category><![CDATA[vehicle-properties]]></category>
            <category><![CDATA[carpropertymanager]]></category>
            <category><![CDATA[car-app-library]]></category>
            <category><![CDATA[androidautomotiveos]]></category>
            <dc:creator><![CDATA[Viktor Mukha]]></dc:creator>
            <pubDate>Wed, 10 Dec 2025 15:42:10 GMT</pubDate>
            <atom:updated>2026-07-20T09:06:29.308Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*18cdbcy2x6vmiq8b41YeAQ.jpeg" /><figcaption>Source: <a href="https://www.press.bmwgroup.com/deutschland/photo/detail/P90626683/der-neue-bmw-ix3-50-xdrive-space-silver-12/2025">https://www.press.bmwgroup.com/</a></figcaption></figure><p>In this article, we will discuss car infotainment ecosystems from the perspective of an application developer, covering their past, present, and future.</p><p>We will also explore how to interface with a car and retrieve information, such as vehicle speed, from its network.</p><h3>Do cars need software applications?</h3><p>When cars first went into mass production, they did not have radios. The driving experience was exciting enough on its own.</p><p>The very first commercial radio appeared in 1930, and it took several years for it to become an established standard equipment. People clearly saw the value of the radio, and radio stations were happy about it too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDFKmcbxres8ITSz6dVCTw.jpeg" /><figcaption>We’ve come a long way since then!</figcaption></figure><p>Today, large, colorful displays with touch and speech control are all the rage. Much as we love analog technology and physical buttons, we cannot deny that such user interfaces offer drivers far greater value.</p><p>These days, people expect cars to offer more than just a radio.</p><h3>Why now?</h3><p>Displays are now just as much a part of any new car as a radio. But why are we talking about it now? What changed?</p><p>Until recently, in order to develop an application for a car’s built-in system, you had to talk to OEMs directly (e.g., to BMW, GM, Ford, Volvo, etc.), and use their proprietary framework. This resulted in virtually no market for car-specific applications. This is still the case for most OEMs today.</p><p>However, this is changing.</p><h3>Android Auto &amp; Apple CarPlay</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6NwgWWzEpxJhVv3314F6Kg.png" /><figcaption>Apple CarPlay (source: <a href="https://www.apple.com/de/ios/carplay/">https://www.apple.com/de/ios/carplay/</a>)</figcaption></figure><p>Today, there is an established market of Android Auto and Apple CarPlay. These are so-called projection modes. Simply connect your phone to your car and enjoy your favorite apps on the go.</p><p>When it comes to developing car applications, these are clearly the best platforms to target today. That is where the users are. Consequently, it receives the most attention from both Google and Apple as a platform for automotive apps.</p><p>However, a new platform has emerged: Android OS installed directly in a car. This is the future.</p><h3>Native Android in cars</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5qY4fx6coRgfOgyfhoN7mA.png" /><figcaption>Google built-in (source: <a href="https://built-in.google/cars/">https://built-in.google/cars/</a>)</figcaption></figure><p>In the recent years there has been a dramatic shift in the technology being used for car infotainment systems. This change was enabled by the release of Android Automotive OS (AAOS), which included many useful car-specific features in the Android Open Source Project (AOSP).</p><p>Previously, most OEMs used their own customized Linux solutions; now, most support Android APIs. We will not go into motives of the change. Instead, let us focus on the opportunity to develop for it.</p><h3>What do the cars support?</h3><p>A developer who wants to build an Android application specifically for cars, or add certain in-car use cases to an existing Android application, is faced with the following choice of the target today:</p><ul><li>Cars with support for <strong>Android Auto</strong>,</li><li>Cars running <strong>Android Automotive OS (AAOS)</strong> with <strong>Google Automotive Services (GAS)</strong> —<strong> </strong>these are now marketed as “<a href="https://built-in.google/"><strong>Google built‑in</strong></a><strong>”</strong>, and</li><li>Cars which run an OS based on <strong>Android Open Source Project (AOSP) or AAOS </strong>without GAS.</li></ul><p>For a more in-depth overview of these platforms, take a look at these great articles by <a href="https://www.roa-valverde.com/">Antonio Roa-Valverde</a>:</p><ul><li><a href="https://www.roa-valverde.com/2024/10/navigating-the-android-automotive-os-third-party-app-ecosystem-a-developers-perspective/">Navigating the Android Automotive OS Third Party App Ecosystem: a Developer’s Perspective</a>,</li><li><a href="https://www.roa-valverde.com/2025/01/android-automotive-os-app-stores-understanding-the-ecosystem/">Android Automotive OS app stores: understanding the ecosystem</a>.</li></ul><h3>Car API overview</h3><p>At the highest level, Google provides an abstraction which is called <a href="https://developer.android.com/training/cars/apps">Android for Cars App Library</a>, also known as <strong>Car App Library (CAL)</strong>. It works for both Android Auto and AAOS.</p><p><strong>Ideally, all car APIs would be exposed exclusively via CAL.</strong></p><p>Unfortunately, there is still some fragmentation, even among Google’s own APIs. AAOS has certain APIs that can (or have to) be used instead of CAL.</p><p>Let’s categorize all of the Android car APIs into 3 groups:</p><ol><li>Car APIs that mirror standard Android APIs</li><li>Car-specific APIs for user interaction</li><li>Car-specific APIs for vehicle data</li></ol><h3>1. Car APIs which mirror standard Android APIs</h3><h4><a href="https://developer.android.com/training/cars/apps#carsensors">CarSensors</a> (CAL)</h4><p>Suppose you want to access an accelerometer.</p><p>Since Android Auto runs on a phone, developers have access to two accelerometers: one on the phone, and one in the car. CarSensors gives you access to the one in the car.</p><p>AAOS does not have this ambiguity. Therefore, we must use <a href="https://developer.android.com/reference/android/hardware/SensorManager">SensorManager</a> and <a href="https://developer.android.com/reference/android/location/LocationManager">LocationManager</a> there instead.</p><p>The choice is straightforward:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*yrIHFoLxpMXdOVZN_WbbcQ.png" /><figcaption>APIs for accelerometer and alike: CarSensors vs SensorManager/LocationManager</figcaption></figure><p>To target both Android Auto and AAOS, you must check which platform your application is running on at runtime, or build separate versions of the app.</p><p>The reason CarSensors returns an <a href="https://developer.android.com/reference/androidx/car/app/hardware/common/CarValue#STATUS_UNIMPLEMENTED()">unimplemented status</a> on AAOS instead of wrapping calls to SensorManager and LocationManager remains unclear.</p><h4><a href="https://developer.android.com/reference/androidx/car/app/media/CarAudioRecord">CarAudioRecord</a> (CAL)</h4><p>This is a car-specific subset of the <a href="https://developer.android.com/reference/android/media/AudioRecord.html">AudioRecord API</a>. It is minimal and integrates well with other CAL APIs.</p><p>There is also generic <a href="https://developer.android.com/reference/android/media/MediaRecorder">MediaRecorder API</a>, but its scope is different.</p><h3>2. Car-specific APIs for user interaction</h3><p>This cluster of car APIs is new to Android. Cars are not phones, and must have different standards for distraction optimization and general user interaction.</p><p>These APIs include <a href="https://developers.google.com/cars/design/create-apps/app-types/overview">App Types</a>, <a href="https://developers.google.com/cars/design/create-apps/apps-for-drivers/overview">Templates</a>, <a href="https://developers.google.com/cars/design/create-apps/media-apps/overview">Media Apps</a>, etc.</p><p>Depending on your app’s category, target platform and whether it must be usable while driving, you will see which of these APIs are available and possibly even enforced.</p><p>For a great introduction, see Section 4, “Building your App,” in the Appning Automotive Apps Market <a href="https://appning.com/developers/#documentation">developer documentation</a>.</p><p>Google has documented these APIs quite well: <a href="https://developers.google.com/cars/design/create-apps">https://developers.google.com/cars/design/create-apps</a></p><p>The libraries and documentation are both in active development, so it is best to regularly check these resources. This is also why we omit the arguably largest section of this article and focus on data APIs instead.</p><h3>3. Car-specific APIs for vehicle data</h3><p>The usage of vehicle data is an important feature that sets a car-specific Android application apart. Examples of such vehicle-data-centric use cases include:</p><ul><li>Fleet management: fuel and charge levels, pending maintenance, location</li><li>Insurance: driving performance evaluation, tire pressure, speeding and braking events, indicator usage, timely maintenance</li><li>Entertainment: driving feedback, control of peripherals such as ambient lights</li></ul><p>One specific example is the <a href="https://carchestra.com/">Carchestra</a> app. It is a media application that reacts to your driving style that was created by us at <a href="https://paradoxcat.com/">Paradox Cat</a>. It won the <a href="https://appning.com/developers/">Appning App Challenge</a>, so give it a try!</p><p>Currently, there are the following ways of accessing car data:</p><ol><li><a href="https://developer.android.com/training/cars/apps#carinfo"><strong>CarInfo</strong></a> as part of <strong>CAL</strong>. It works for both Android Auto and AAOS.</li><li><a href="https://developer.android.com/reference/android/car/hardware/property/CarPropertyManager"><strong>CarPropertyManager</strong></a>, which only works for AAOS-based cars, because it uses Car Service and Vehicle HAL.</li></ol><p>Here is how to choose:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZMcjZWqzX5mUgHGWbbfxA.png" /><figcaption>APIs for typical car data: CarInfo vs CarPropertyManager</figcaption></figure><p>From a software architecture perspective, it is questionable whether we even need a CarPropertyManager. Again: ideally, all Car APIs would be exposed exclusively via CAL. Perhaps Google will address this issue eventually, but for now, this is the current state.</p><p>Now, let’s take a deeper look at both <strong>CarInfo</strong> and <strong>CarPropertyManager</strong>.</p><h3>CarInfo</h3><blockquote>Starting with Car App API level 3, the Car App Library has APIs that you can use to access vehicle properties and sensors.</blockquote><p>This quote is about CarInfo, which does not expose as much as most use cases would require. Here’s the full list of APIs as of today:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8FYeoEe8hYbjCpxPikfQFQ.png" /><figcaption>Car data surfaced by the <a href="https://developer.android.com/reference/androidx/car/app/hardware/info/CarInfo">CarInfo</a> APIs</figcaption></figure><p>It is definitely not all the data which could be made available to Android applications. Unfortunately, even automotive OEMs cannot expose additional data via this library, because the interface is specified by Google for all cars.</p><p>From our experience of using CarInfo with Android Auto on non-Android cars, we have found that most OEMs only deliver the car model and speed. The rest of the CarInfo methods usually do not return actual data.</p><p>On AAOS, CarInfo is implemented using the CarPropertyManager API. CarInfo essentially exposes a subset of these APIs in a slightly different form.</p><p>Therefore, more data is available on AAOS cars than on non-Android cars using CarInfo.</p><p>However, AAOS directly exposes the CarPropertyManager API, so let’s explore the benefits of using it.</p><h3>CarPropertyManager</h3><p><em>Note: CarPropertyManager is an Android Automotive OS (AAOS) feature, it does not exist on Android Auto.</em></p><p>Have you ever wondered how OEMs who use the Android OS in their cars are supposed to access car data points themselves in all of their first-party applications such as Climate, Telephony, or Navigation?</p><p>The answer is: the <a href="https://developer.android.com/reference/android/car/hardware/property/CarPropertyManager">CarPropertyManager API</a>.</p><h4>What is a Car Property?</h4><p>Google also refers to them as <a href="https://source.android.com/docs/automotive/vhal/previous/properties">vehicle properties</a>. A vehicle property is a data point that represents the state of a car.</p><p>This data is sent from the automotive network to the Vehicle Hardware Abstraction Layer (VHAL), where it is mapped to properties. CarPropertyManager allows application developers to access these properties.</p><p>Properties can be read-only, write-only, or read-write.</p><p>Each property has an area (such as VEHICLE_AREA_TYPE_SEAT), a strong data type (such as Integer), and a change mode (such as VEHICLE_PROPERTY_CHANGE_MODE_CONTINUOUS) associated with it. Additionally, each property declares the necessary permissions to access it.</p><p>Below are some examples of vehicle properties:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pZZdThWawoeXU6omBNvnkw.png" /><figcaption>Vehicle Properties</figcaption></figure><p>The full list of property IDs can be found <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds">here</a>. As of today, there are over 250 different vehicle properties, which by far surpasses the number provided by CarInfo.</p><p>For more information on how it works under the hood, please refer to this <a href="https://medium.com/@mmohamedrashik/vehicle-hal-and-car-api-in-android-automotive-os-cfca60c7edd0">article by Rashik</a>.</p><h4>System Properties vs Vendor Properties</h4><p>By design, Google is expecting OEMs to provide data via a predefined set of so-called <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds">system properties</a>. This set contains over 250 properties, as shown above.</p><p>At the same time, Google recognizes that this set may not be ideal for all OEMs and provides a mechanism to extend it with <a href="https://source.android.com/docs/automotive/vhal/special-properties#vendor-properties">vendor properties</a>. It is important to note that OEMs that want to be <a href="https://source.android.com/docs/compatibility/overview">officially compatible with Android</a> must adhere to these rules:</p><blockquote>Always try to use system properties first, vendor properties should be used as a last resort when none of the system properties feeds your requirement.</blockquote><blockquote>To prevent ecosystem fragmentation, vendor properties must not be used to replicate vehicle properties that already exist in the SDK <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds">VehiclePropertyIds</a>. To learn more, see <a href="https://source.android.com/docs/compatibility/13/android-13-cdd#25_automotive_requirements">Section 2.5, Automotive Requirements</a> in the CDD.</blockquote><p>It is unclear whether all car manufacturers who use AOSP comply with this requirement.</p><p>So, there are even more vehicle data points. But who has access to them?</p><h4>Permissions: a word of warning</h4><p>If the property requires a “signature” or “signature | privileged” permission level, it means that you cannot obtain permission without the platform being updated. Each OEM must update their AOSP to whitelist your application package. You will only receive the permission when the OS image is updated in each car. Not to mention, a trusted relationship with an OEM is required.</p><p>This is a topic that we are currently addressing with many different automotive OEMs at the <a href="https://covesa.atlassian.net/wiki/spaces/WIK4/pages/39068159/Automotive+AOSP+App+Framework+Standardization+Expert+Group">Connected Vehicle Systems Alliance (COVESA)</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v5lcD_HA4uYm_9XgEhEUNg.jpeg" /></figure><p>One of the goals there is to avoid fragmentation by standardizing all vehicle APIs for Android. No need to talk to each OEM separately, flexible permission model, the ability to reuse Vehicle Signal Specification (VSS), and so on. The group is open, and software is open-source.</p><p>Given the current permissions situation, three categories of developers could use the CarPropertyManager API:</p><ul><li>OEMs developing first-party applications;</li><li>third-party application developers who are in agreement with OEMs to have their applications whitelisted to access specific properties;</li><li>third-party application developers who are only interested in properties with “normal” or “dangerous” (runtime) permissions.</li></ul><blockquote>Disclaimer</blockquote><blockquote>The following tables are merely a snapshot of the current API. Please, always refer directly to <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds">https://developer.android.com/reference/android/car/VehiclePropertyIds</a></blockquote><p>The following is a list of the 37 properties with “normal” permissions today:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2002d88ccbd8ed011f2ac6509ddae497/href">https://medium.com/media/2002d88ccbd8ed011f2ac6509ddae497/href</a></iframe><p>Below is a list of the 33 properties that require “dangerous” permissions to be granted at runtime:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7dc2e3191cd1a42212ccd2ea7aa0615/href">https://medium.com/media/e7dc2e3191cd1a42212ccd2ea7aa0615/href</a></iframe><h4>Code example</h4><p>Now that we have the permissions out of the way, we can move on to the actual code example.</p><p>At <a href="https://paradoxcat.com/">Paradox Cat</a>, we have recently released an open-source (MIT-licensed) wrapper library for the CarPropertyManager API. This library greatly simplifies integration with the Kotlin codebase and handles all connection logic out of the box.</p><p>This is how easy it makes to subscribe for car speed (omitting permission request):</p><pre>val kpm = KarPropertyManager(context, scope)<br>val speedFlow = kpm.getProperty&lt;Float&gt;(<br>        VehiclePropertyIds.PERF_VEHICLE_SPEED, 0, 60F).valueFlow</pre><p>Here is the GitHub repository: <a href="https://github.com/Paradox-Cat-GmbH/KarPropertyManager">https://github.com/Paradox-Cat-GmbH/KarPropertyManager</a></p><p>We hope you’ll find our library useful! Feel free to report any issues or suggest features you’d like to see, we would appreciate your feedback.</p><h3>Challenges</h3><p>From an application developer’s perspective, the situation is pretty dire.</p><h4>Confusing API surface</h4><p>It’s simply too much for a typical Android application developer to grasp. Just look at the size of this article, and we mostly focused on the Google experience.</p><h4>Lack of Testing Tools</h4><p>The Google landscape is more or less covered by the official Android Automotive emulator (with GAS). Additionally, one could rent cars of the following brands and expect similar experience: <a href="https://built-in.google/cars/#explore-cars">https://built-in.google/cars/#explore-cars</a></p><p>It would also be helpful to feed the emulator with real car data. There is a free demo recording provided by <a href="https://www.remotivelabs.com/blog/feeding-your-aaos-emulator">remotiveLabs</a>, but Google has not yet provided anything like that. A comprehensive car simulator that includes all displays and interaction capabilities would also be helpful.</p><p>As for non-Google OEMs using AAOS, it’s certainly difficult to find a representative platform. COVESA recognized it and we supported this by setting up a vanilla AAOS emulator CI pipeline. See <a href="https://github.com/COVESA/aosp_device_covesa_emulator">https://github.com/COVESA/aosp_device_covesa_emulator</a>.</p><p>Next steps: <a href="https://github.com/COVESA/aosp_device_covesa_emulator/issues">https://github.com/COVESA/aosp_device_covesa_emulator/issues</a></p><p>Discussions: <a href="https://github.com/COVESA/aosp_device_covesa_emulator/discussions">https://github.com/COVESA/aosp_device_covesa_emulator/discussions</a></p><p>As of this writing, further development and maintenance of this emulator has been paused due to lack of interest from automotive OEMs. Each OEM has its own emulator, but they differ, and most are not public. This makes it difficult for developers to verify whether their apps would work on non-GAS cars.</p><p>Once the issue of a standard reference emulator is resolved, non-GAS OEMs will face further challenges in standardizing their interfaces if they cannot be identical to Google’s.</p><p>With regard to the rental of non-GAS cars, we have also recognized that there is no official channel for sideloading the application for testing purposes. ADB is usually disabled.</p><p>Google has an internal test track in the Play Store, but it is only usable with GAS. Perhaps other app stores should make it publicly available too.</p><h4>OEM support of Template Host</h4><p>Whether CAL’s Template-UIs are supported depends on whether the OEM has integrated so-called <a href="https://source.android.com/docs/automotive/hmi/aosp_host">Automotive App Host</a>. Cars with Google built-in (GAS) come with the <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.automotive.templates.host&amp;hl=en">Google Automotive App Host</a>, which Google keeps up to date via Play Store updates. Without GAS, there is no guarantee that the OEM has integrated their own version of the <a href="https://source.android.com/docs/automotive/hmi/aosp_host">Automotive App Host</a> that supports the latest Car App Library version.</p><p>Fragmentation occurred when Google updated the GAS version of the Automotive App Host, but not the open-source version.</p><ol><li>OEMs running AAOS without Google Automotive Services (GAS) are stuck with Car App Library API level 4.</li><li>Some OEMs and App Stores started to extend it. Unfortunately we are not aware of any implementation of Template Host that supports the latest Car App Library APIs except for Google’s proprietary one.</li></ol><p>Hopefully, Google will continue to update the open-source Template Host to support the latest Car App Library APIs.</p><p>To ensure compatibility today:</p><ul><li><strong>Wait for OEM support:</strong> Avoid using features that require API level 5 or higher until all manufacturers have updated their systems.</li><li><strong>Build with fallbacks:</strong> If you need newer features now, check the API level at runtime and provide alternative implementations for cars running older API versions.</li></ul><h4>OEM support of Media Apps</h4><p>The MediaBrowserService and MediaSession APIs are already supported in AAOS. Therefore it is unlikely that OEMs would use something else.</p><p>However, OEMs typically implement their own media player, which may or may not function as expected.</p><h4>Access to Vehicle Data</h4><blockquote><strong>Issue #1</strong></blockquote><blockquote>Car manufacturers are not required to support all vehicle properties.</blockquote><p>Currently, even cars with “Google built-in” are <a href="https://source.android.com/docs/compatibility/16/android-16-cdd#73_sensors">only required to implement 4 (!) vehicle properties</a> out of the 70 publicly available (with “normal” and “dangerous” permissions):</p><blockquote>[<a href="https://source.android.com/docs/compatibility/16/android-16-cdd#73_sensors">7.3</a>/A-0–1] MUST implement and report <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds.html#GEAR_SELECTION">GEAR_SELECTION</a>, <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds.html#NIGHT_MODE">NIGHT_MODE</a>,<a href="https://developer.android.com/reference/android/car/VehiclePropertyIds.html#PERF_VEHICLE_SPEED">PERF_VEHICLE_SPEED</a> and <a href="https://developer.android.com/reference/android/car/VehiclePropertyIds.html#PARKING_BRAKE_ON">PARKING_BRAKE_ON</a>.</blockquote><p>Therefore, application developers cannot rely on CarInfo or CarPropertyManager to deliver more than these four properties.</p><p>Another issue is that some OEMs do not even use AAOS; they use the tablet version of AOSP, which lacks CarPropertyManager.</p><p>The solution will take time. The more apps that start using these APIs, the greater the incentive for OEMs to support them.</p><blockquote><strong>Issue #2</strong></blockquote><blockquote>The permission model is not flexible enough for OEMs to adopt.</blockquote><p>Currently, 180 out of 250 standard vehicle properties are only available with OEM signature.</p><p>There’s an initiative at COVESA to enable a better permission model with minimal AOSP changes: <a href="https://covesa.atlassian.net/wiki/spaces/WIK4/pages/262766594/COVESA+AOSP+Vehicle+Data">https://covesa.atlassian.net/wiki/spaces/WIK4/pages/262766594/COVESA+AOSP+Vehicle+Data</a></p><p>Here’s the repo manifest of a PoC, if you’d like to inspect what changes are necessary to enable this: <a href="https://github.com/COVESA/aosp_platform-manifest/blob/android-15/custom-additions.xml">https://github.com/COVESA/aosp_platform-manifest/blob/android-15/custom-additions.xml</a></p><p>Ideally, this will be merged into AOSP, which will avoid fragmentation.</p><blockquote>Issue #3</blockquote><blockquote>Most OEMs require more than Google’s set of properties.</blockquote><p>These end up as vendor properties, as indicated above, which third-party applications have no access to.</p><p>If all OEMs agreed to reuse the <a href="https://covesa.github.io/vehicle_signal_specification/">Vehicle Signal Specification (VSS)</a> or any other standard, developers would have access to more car data points without needing OEM-specific software development kits (SDKs).</p><h3>Summary</h3><p>The world needs <strong>more </strong>car-specific applications, and <strong>now</strong> is the time to develop them because almost all OEMs are using Android as the main OS for infotainment.</p><p>Begin by consulting <a href="https://appning.com/developers/#documentation">Appning’s documentation</a>, followed by <a href="https://developers.google.com/cars/design/create-apps">Google’s</a>.</p><p>Refer to this article for details on how to work with <strong>vehicle data</strong> and what to be aware of.</p><p>If you are using Kotlin, check out our <a href="https://github.com/Paradox-Cat-GmbH/KarPropertyManager"><strong>KarPropertyManager</strong></a> wrapper.</p><p>As a third-party developer you can only access the properties with <strong>“normal”</strong> or <strong>“dangerous”</strong> (runtime) <strong>permissions</strong>. Do not assume that you have access to all the data.</p><p>Both developers and car manufacturers face many challenges, but most of these will be solved once the market saturates and stabilizes.</p><p>So go ahead and develop some apps for cars! <a href="https://paradoxcat.com/kontakt/">Contact us at Paradox Cat</a> if you need any help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac627ba9fc8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paradox-cat-tech-hub/building-apps-for-cars-in-2026-android-auto-aaos-and-vehicle-data-apis-ac627ba9fc8e">Building Apps for Cars in 2026: Android Auto, AAOS, and Vehicle Data APIs</a> was originally published in <a href="https://medium.com/paradox-cat-tech-hub">Paradox Cat Tech Hub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything you need to know about Android on Raspberry Pi]]></title>
            <link>https://medium.com/paradox-cat-tech-hub/android-on-raspberry-pi-aa4b8eea72c6?source=rss-7ac49f590be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa4b8eea72c6</guid>
            <category><![CDATA[android-bsp]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[aosp]]></category>
            <dc:creator><![CDATA[Viktor Mukha]]></dc:creator>
            <pubDate>Mon, 23 Sep 2024 10:02:49 GMT</pubDate>
            <atom:updated>2024-09-24T13:44:05.590Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KAYy7AIVJ7_7UrsP" /><figcaption>Generated by AI using ChatGPT’s DALL·E</figcaption></figure><h3>In this article we are going to unveil:</h3><ul><li>4 Reasons you should use Android on Raspberry Pi</li><li>Where should you get Android for Raspberry Pi?</li><li>Which one to choose?</li><li>Future prospects.</li></ul><h3>4 Reasons you should use Android on Raspberry Pi</h3><p>Raspberry Pi is arguably one of the world’s most popular single-board computer. You probably already have one, don’t you?</p><p>Android is the <a href="https://www.businessofapps.com/data/android-statistics/#:~:text=Android%20is%20the%20most%20popular,manufacturers%20in%20the%20early%202010s.">most popular operating system in the world</a>. There is a huge variety of applications to choose from.</p><p>This popularity, combined with the increasing power of Raspberry Pi, opens up many possibilities for using Android on Raspberry Pi. Let us explore these briefly.</p><h4>Reason #1: Gaming</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C61Pzn-gWN6Ad7d9zLpcCg.png" /><figcaption>Get retro vibes from your Raspberry Pi with Android</figcaption></figure><p>Raspberry Pi with Android is one of the most affordable gaming platforms on the market, whether using a keyboard and mouse with your desktop monitor, or using controllers with your TV. Simply install an Android game as an APK or use another app to emulate one of the retro consoles.</p><h4>Reason #2: Home Entertainment</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*04hffYoSgi2BrfHq.jpg" /><figcaption>TV with bias lighting</figcaption></figure><p>Once your built-in TV functionality gets old, there are plenty of affordable ways to breathe some life back into it. You could obviously get something like a FireTV stick, Apple TV, the <a href="https://www.theverge.com/2024/8/6/24214471/google-chromecast-line-discontinued">discontinued</a> Google Chromecast, or the all-new Google TV Streamer. If you feel adventurous, you could also take a look at the myriad of chineese streamers which retail on Amazon and Aliexpress. However, none of these would give you the flexibility of a Raspberry Pi.</p><p>The Raspberry Pi opens up so many more possibilities. It is a great centerpiece for home entertainment.</p><p>You can choose an Android TV Lineage OS build or use any Android flavor and simply install an app like <a href="https://www.plex.tv/">Plex</a> to have a centralized streaming console.</p><p>Raspberry Pi officially supports Widewine, which means that Netflix, Disney+ and all the major streaming services work.</p><p>With a help of <a href="https://www.hifiberry.com/">HiFiBerry</a>, you could do multi-room audio, turn passive speakers into active ones, correct room acoustics with DSP, build a high-quality streamer, and dive deep into DYI audio.</p><p>Projects like <a href="https://github.com/shrocky2/Hyperion">Hyperion</a> enable DYI lighting solutions for <a href="https://en.wikipedia.org/wiki/Bias_lighting">bias lighting</a>.</p><p>Simply plug a Webcam into a USB port of a Raspberry Pi and your TV turns into a video-call enabled device. Due to the fact that all major videoconferencing software runs on Android phones, the chances are high that it would work really well.</p><h4>Reason #3: Low-Volume Product</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bAp2AXL8v6b5Z_RCfJij_w.jpeg" /><figcaption>Point of Sale System</figcaption></figure><p>Let’s say you need to build a point-of-sale terminal and you only need 10 of them. Maybe you already have an Android application that you could at least partially reuse. Or you could quickly deploy a solution using apps like <a href="https://squareup.com/">Square</a> or <a href="https://www.lightspeedhq.com/vend/">Vend</a>.</p><p>Not every company needs a professional and scalable hardware solution from NXP, Qualcomm, or other vendors right away. Sometimes you need a quick and inexpensive way to test your proof of concept.</p><p>Android is a great platform for an embedded solution with a touch display, that has a lot of features you would need to implement yourself in a more standard Yocto distribution.</p><p>Thus, a combination of Raspberry Pi and Android is a very lucrative option for such prototyping.</p><h4>Reason #4: Car Navigation System</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rNOjgCZLrd67yhWKyW2E6g.png" /><figcaption>Car Navigation</figcaption></figure><p>Once your car’s embedded system can not keep up with technology, the typical solution is to use your phone either directly or via a so-called projection mode such as CarPlay (for iPhones) or Android Auto, effectively projecting your phone’s screen onto the car’s display(s).</p><p>Not all cars support projection modes, so there are things you can do with Raspberry Pi and an external display to get around this.</p><p>There are many off-the-shelf solutions on the market, mostly from the Far East. However, if you want an up-to-date Android system without built-in backdoors and with some DIY capabilities, Raspberry Pi with an external touch display is a great place to start.</p><p>The main goal of the project would undoubtedly be navigation with Google Maps. But again, just like in home entertainment, you could pimp your sound system, install some ambient lighting, and configure it all to play well with your Android system.</p><h4>Bonus: Other Reasons</h4><p>There are plenty of projects which may be realized with a combination of Raspberry Pi and Android.</p><p>However, this may not be the best solution for organizations due to licensing issues or lack of hardware performance.</p><p>Feel free to contact us at <a href="https://paradoxcat.com/">Paradox Cat</a> if you have a project in mind. We can help you understand the costs and benefits involved, and we can build a custom AOSP-based solution that fits your needs precisely.</p><h3>Where should you get Android for Raspberry Pi?</h3><p>To run Android, Raspberry Pi needs an Android Board Support Package (Android BSP). This BSP is a collection of tools and drivers that allow specific hardware to boot into vanilla AOSP. Normally, it is the hardware vendor’s responsibility to create such a BSP.</p><p>However, the Raspberry Pi vendor (Raspberry Pi Foundation) only officially supports the Raspberry Pi OS.</p><p><strong>There is no official Android support for Raspberry Pi.</strong></p><h4>Unofficial Android Support</h4><p>Fortunately, Google provides the source code for the main part of the Android OS via the Android Open Source Project (AOSP). This, combined with the open source nature of most of the Raspberry Pi drivers for Linux, enabled people to build their own Android BSPs for Raspberry Pi.</p><p>The development of Android BSP for the original Raspberry Pi <a href="https://phys.org/news/2012-08-raspberry-pi-android.html">dates back to 2012</a>. After a while the developer community has been centered around the <a href="https://groups.google.com/g/android-rpi">android-rpi Google group</a>, which is still active today.</p><p>Let us take a look at the landscape of Android BSPs for Raspberry Pi today.</p><blockquote>Disclaimer</blockquote><blockquote>What follows is our humble research of available Android BSPs. We are not affiliated with any of the authors, and would be happy to be corrected. It is also difficult to determine the original authorship of the code, as some of it has often been copied without proper attribution. It seems that all the BSPs developers have been working in parallel, looking at each other’s changes and cherry-picking some, but not all.</blockquote><h4>android-rpi</h4><p>android-rpi is a developer community found on Github (<a href="https://github.com/android-rpi">https://github.com/android-rpi</a>), as well as Google Groups (<a href="https://groups.google.com/d/forum/android-rpi">https://groups.google.com/d/forum/android-rpi</a>).</p><p>The history of this community goes back to 2015 with the release of Android 5.0 on Raspberry Pi 2. The community is still active and continues to release source code of Android BSPs for new Raspberry Pi versions.</p><p>There are no binary images available for download.</p><p>The entry point for building your own image for Raspberry Pi 5, for example, can be found at <a href="https://github.com/android-rpi/device_arpi_rpi5">https://github.com/android-rpi/device_arpi_rpi5</a>.</p><p>This build is based on Android TV and comes with its own open source launcher called <a href="https://github.com/peyo-hd/RpLauncher">RpLaucher</a> and TV settings app called <a href="https://github.com/peyo-hd/LbSettings">LbSettings</a>. If you want to know more about Android launchers, we have written <a href="https://medium.com/paradox-cat-tech-hub/custom-android-launcher-why-and-how-do-i-build-one-6a1b3af89d43">another article</a> about them.</p><h4><strong>raspberry-vanilla</strong> and <strong>lineage-rpi by KonstaKang</strong></h4><p><a href="https://github.com/KonstaT">KonstaKang</a> has been consistently providing ready-to-use Raspberry Pi Android images for years. Looking at the website <a href="https://konstakang.com/">https://konstakang.com/</a> along with other devices, one would find a lot of different binary Raspberry Pi Android images for free download:</p><ul><li>Raspberry Pi 4: <a href="https://konstakang.com/devices/rpi4/">https://konstakang.com/devices/rpi4/</a></li><li>Raspberry Pi 5: <a href="https://konstakang.com/devices/rpi5/">https://konstakang.com/devices/rpi5/</a></li></ul><p>Most of the source code for these images along with build instructions, can be found in two different GitHub “organizations”:</p><ol><li>The <a href="https://github.com/raspberry-vanilla">raspberry-vanilla</a> collection of repositories has everything you need to build a vanilla AOSP for Raspberry Pi 4 or 5. You can build the kernel and the Android OS all by yourself.</li><li>The <a href="https://github.com/lineage-rpi">lineage-rpi</a> collection of repositories is used to build an Android OS distribution based on <a href="https://lineageos.org/">LineageOS</a>, which provides a little more than vanilla AOSP, including its own TV launcher.<br><em>NOTE: these repositories became private after Lineage OS 17.1, so you can only build the kernel, but not the rest.</em></li></ol><h4>GloDroid</h4><p>The project was initiated by <a href="https://www.linkedin.com/in/roman-stratiienko-03474a92">Roman Stratiienko</a> at “<a href="https://www.globallogic.com/">Global Logic</a>” with the main goal of creating a platform for training Android BSP developers [<a href="https://www.youtube.com/watch?v=Em_ITP3Y2ik">#44 Proof My Concept : GloDroid</a>]. Github profile: <a href="https://github.com/rsglobal">https://github.com/rsglobal</a></p><p>It was originally started for Orange Pi. Raspberry Pi support was recently added in 2023: <a href="https://github.com/GloDroidCommunity/raspberry-pi/commit/7c0e3b199f9c7f5a43ad76cf9688811300ce0490">https://github.com/GloDroidCommunity/raspberry-pi/commit/7c0e3b199f9c7f5a43ad76cf9688811300ce0490</a></p><p>Source code: <a href="https://github.com/GloDroidCommunity/raspberry-pi/releases">https://github.com/GloDroidCommunity/raspberry-pi</a></p><p>Prebuilt images: <a href="https://github.com/GloDroidCommunity/raspberry-pi/releases">https://github.com/GloDroidCommunity/raspberry-pi/releases</a></p><p>Project status: <a href="https://github.com/GloDroidCommunity/raspberry-pi/issues/1">https://github.com/GloDroidCommunity/raspberry-pi/issues/1</a></p><p>Discord channel: <a href="https://discord.gg/5H8cW5xA">https://discord.gg/5H8cW5xA</a></p><p>GloDroid also provides builds based on LineageOS, but you have to build it yourself using this script: <a href="https://github.com/GloDroidCommunity/raspberry-pi/blob/main/unfold_lineageos.sh">unfold_lineageos.sh</a>. See <a href="https://github.com/GloDroidCommunity/raspberry-pi/blob/main/README.md">README.md</a> for details.</p><h4>OmniROM</h4><p>OmniROM is a custom ROM distribution founded in 2013. The OmniROM distribution also founded TWRP (Team Win Recovery Project), which is included in the <strong>raspberry-vanilla</strong> and <strong>lineage-rpi</strong> builds as the default recovery partition. Android 13 builds for the Raspberry Pi 4, when tested by us resulted in an unstable experience, with frequent OS crashes and visual stuttering. Due to these unresolved issues, we would not recommend using this distribution for this particular version of Android. The latest stable release for Raspberry Pi 4 appears to be Android 12.1.</p><h4>Emteria Android OS</h4><p>Emteria customizes and maintains the Android OS for popular off-the-shelf hardware and industrial platforms, including Raspberry Pi. This BSP is closed source and commercial.</p><p>More info: <a href="https://emteria.com/">https://emteria.com/</a></p><h3>Which one to choose?</h3><p>It depends on your requirements and your use case. Here is a checklist:</p><ul><li>What version of Raspberry Pi do you target? Different versions have different hardware, and require different Android BSPs.</li><li>Can you build it yourself? Current AOSP builds <a href="https://source.android.com/docs/setup/start/requirements#hardware-requirements">require</a> a Ubuntu machine with at least 64GB ofRAM.</li><li>Do you need support for all the hardware that Raspberry Pi offers? Is anything in particular more important than the rest?</li><li>Do you want to use it commercially? Check the license.</li><li>Do you want the vanilla AOSP experience, LineageOS, or something else?</li></ul><p>As you can see, the KonstaKang and GloDroid BSPs are the most prominent AOSP distributions for the Raspberry Pi 4 and 5. However, while similar, these images are built differently and offer different experiences and are intended for different applications. To help you make your choice, we have compiled the following table with the functionality of various components:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a39075949c64eaf1081510d149d1fbf1/href">https://medium.com/media/a39075949c64eaf1081510d149d1fbf1/href</a></iframe><p>The flashing procedures also differ between the two. When flashing to an SD card, the scripts and instructions are different.</p><p>Besides using an SD card, a nice addition in GloDroid is fastboot over USB. Simply call:</p><pre>adb reboot bootloader</pre><p>and off you go, fastboot is enabled.</p><p>KonstaKang builds are using TWRP recovery partition for easy OTA updates. To enter this recovery mode, simply flip a switch in the Raspberry Pi submenu of the modified Settings app and reboot. This submenu also offers some nice features, such as the ability to view and change the screen resolution.</p><p>Another difference is that GloDroid uses U-boot, the “Universal Boot Loader”, while the KostaKang builds boot directly from the standard Raspberry Pi EEPROM bootloader.</p><h3>Future prospects</h3><p>It seems that the fragmentation of Raspberry Pi Android BSPs is mostly caused by the different goals of the projects. We do not see these projects converging in the near future.</p><p>It is also highly unlikely that the Raspberry Pi Foundation will start officially supporting Android.</p><p>Fortunately, we have the community where we can find support and play around with Android on Raspberry Pi.</p><p><em>Special thanks to </em><a href="https://medium.com/u/63d80726cb34"><em>James Gatt</em></a><em> for co-authoring this story.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa4b8eea72c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paradox-cat-tech-hub/android-on-raspberry-pi-aa4b8eea72c6">Everything you need to know about Android on Raspberry Pi</a> was originally published in <a href="https://medium.com/paradox-cat-tech-hub">Paradox Cat Tech Hub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My MacOS Tool Collection]]></title>
            <link>https://medium.com/@viktor.mukha/my-macos-tool-collection-c1ea2ccf03da?source=rss-7ac49f590be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1ea2ccf03da</guid>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[rectangle]]></category>
            <dc:creator><![CDATA[Viktor Mukha]]></dc:creator>
            <pubDate>Tue, 13 Aug 2024 07:43:36 GMT</pubDate>
            <atom:updated>2024-08-13T07:43:36.941Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAgq3nr2jhprAfEOzUnFug.jpeg" /></figure><p>I’m writing this mainly to remember it in case I have to move to another MacOS system, but I hope some people will find it useful anyway. It is mostly about external keyboard and mouse, but also about window management, terminal, and other nice extra tools.</p><h3>Change some settings first</h3><h4>“Caps Lock” as one-key language switch</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nU0HumRHfDXyD9LMlF6kZQ.png" /><figcaption>Change Caps Lock on external keyboard to “Globe” for one-key language switching</figcaption></figure><p>I like being able to switch languages with a single keystroke, and I never use Caps Lock to lock the caps, I TYPE WITH SHIFT HOLDED EVEN IF I HAVE A LOT TO TYPE.</p><h4>Switch desktops with Ctrl+1, Ctrl+2, and Ctrl+3</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YczJjtnXB2hfNH-c8wiydg.png" /><figcaption>Enable switching to desktop 1/2/3 with Ctrl+1/2/3</figcaption></figure><p>Yes, you can do it with Ctrl+Left/Right, but the animation is slower that way.</p><h4>Fix “Home” and “End” buttons</h4><p>Next, we need to fix notorious “Home” and “End” buttons, which frankly don’t work consistently even with the Apple keyboard. Here is the workaround: <a href="https://medium.com/@elhayefrat/how-to-fix-the-home-and-end-buttons-for-an-external-keyboard-in-mac-4da773a0d3a2">https://medium.com/@elhayefrat/how-to-fix-the-home-and-end-buttons-for-an-external-keyboard-in-mac-4da773a0d3a2</a></p><h4>Set a black color as your desktop image</h4><p>This way, if you use multiple monitors, your peripheral vision is not distracted by blank screens.</p><h4>Consider adding widgets</h4><p>I mostly like to see battery levels at a glance, but feel free to explore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pmMvTctCzK7XoFI0rcTOMA.png" /></figure><h3>Which tools do I use and why?</h3><h4><a href="https://rectangleapp.com/pro">Rectangle Pro</a></h4><p>Back in 2017, I used Spectacle. Now it’s Rectangle, because Spectacle is no longer supported.</p><p>This one is for window management using keyboard only. There are so many window management features I use that don’t even exist in Mac, let alone can be done with keyboard only.</p><p>The regular free version of Rectangle doesn’t have these 2 features I use, so I’m evaluating Rectangle Pro:</p><ul><li>Move windows between desktops/spaces using keyboard only.</li><li>Restore positions of all windows after lock/unlock and reboot. This one is a deal breaker. I mean, who wants to rearrange windows every time they unlock their screen?<br><em>NOTE: This does not fully work though. There are a </em><a href="https://github.com/rxhanson/RectanglePro-Community/issues"><em>bunch of ideas</em></a><em> on how to make this work, I just hope it gets implemented one day. The current workaround is to create app layouts per space and use a hotkey to restore the window positions when needed. IMHO, this must be automatic at all times. I’m looking for a workaround to automate this now, so please leave a comment if you’ve already solved this :)</em></li></ul><h4><a href="https://github.com/lwouis/alt-tab-macos">AltTab</a></h4><p>I usually want the Alt-Tab experience to be restricted to the current desktop/space. This tool solves that for me. It also gets a bonus point for Windows-like previews, these were quite handy in Windows 11.</p><p>I use Option+Tab for it, and I keep Cmd+Tab for global alt-tabbing among all spaces.</p><h4><a href="https://github.com/ther0n/UnnaturalScrollWheels">UnnaturalScrollWheels</a></h4><p>Nifty tool to fix the lack of a setting to have natural scrolling on the trackpad while having sane scrolling on a mouse with a wheel.</p><h4><a href="https://github.com/thealpa/SaneSideButtons">SaneSideButtons</a></h4><p>Somehow most applications ignored the fact that my mouse has side buttons and refused to go back and forth. This app basically maps this to a gesture, which makes it universal.</p><h4><a href="https://github.com/hovancik/stretchly">Stretchly</a></h4><p>Relieve eye strain and move your body.</p><p>I find the default timings a tad annoying, I have moved the short breaks to once every 30 minutes and the long breaks to once every 90 minutes.</p><h4><a href="https://github.com/ohmyzsh/ohmyzsh">OhMyZhs</a></h4><p>A shell extension to have a nicer MacOS shell. The thing I hate the most about the default zhs is that it lacks colors. Let us add some!</p><p>I use these settings in my ~/.zshrc:</p><pre>ZSH_THEME=&quot;cypher&quot;<br>plugins=(git vscode)</pre><p>This is what the “cypher” theme looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuC1R0FCXShrna_ost_4Gw.jpeg" /><figcaption>Screenshot from <a href="https://github.com/ohmyzsh/ohmyzsh/wiki/Themes">https://github.com/ohmyzsh/ohmyzsh/wiki/Themes</a></figcaption></figure><p>I never actually open a built-in terminal and I don’t use iTerm. Instead, I use terminal in VSCode, which also benefits from OhMyZhs. This is also why I chose a theme without Git augmentation. I simply use Git extensions in VSCode instead.</p><h3>Conclusions</h3><p>As always, there are little features that MacOS users miss here and there. Fortunately, the OS allows third party applications to implement most of them.</p><p>Thanks to all the hard work of the people who make and maintain these tools!</p><p>Please leave a comment and let me know what you use. I am always looking to improve my productivity.</p><p>Also, feel free to ask questions, I will do my best to answer them all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1ea2ccf03da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Push notifications from bash script via Home Assistant]]></title>
            <link>https://medium.com/@viktor.mukha/push-notifications-from-bash-script-via-home-assistant-852fa92f60ab?source=rss-7ac49f590be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/852fa92f60ab</guid>
            <category><![CDATA[push-notification-service]]></category>
            <category><![CDATA[build-time]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[home-assistant]]></category>
            <dc:creator><![CDATA[Viktor Mukha]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 05:07:54 GMT</pubDate>
            <atom:updated>2024-05-08T09:12:29.695Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9Bei_z2DqPLisAudrSKQQ.png" /></figure><p>Recently I had a lot of waiting time when building Android Open Source Project (AOSP) and flashing it to real hardware. As I often do, I wrote 2 bash scripts: one for building, and one for flashing. The thing is, they both take at least 3 minutes to run.</p><p>Would you wait and stare at your screen? What if you did that regularly?</p><p>So I started shifting my focus to other tasks. This is sometimes counterproductive, because we all know that context switching is very costly.</p><p>Instead of switching contexts, we can take a break: have a coffee, eat an apple, or do some exercises. The problem with this is that we want to know when the build has failed/finished so that we can quickly return to it. Enter the Push Notifications project.</p><p>I used to use <a href="https://pushover.net/">https://pushover.net/</a> for this kind of thing, but it’s not free, and you need an extra app on your phone.</p><p>There is also an option to use a Telegram or Signal bot for this, which I have not tried. Can I create a Telegram bot that runs on my own server and redirects push notifications to my phone? Please leave a comment, if you know ;)</p><p>I have my own server running Home Assistant 24/7 and an app on my phone which is capable of the same thing, so I will just use that.</p><p>Turns out, it’s not a rocket science.</p><p>First, create a long-lived access token for your scripts (I would use one for all scripts). To do this, go to <a href="https://ha.mushko.synology.me:8123/profile">https://[YOUR_HOME_ASSISTANT]:8123/profile</a> (or click on your name in the lower left corner) and click on “Create Token”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djLl9wQyYhjcdlmm9e5kIQ.png" /></figure><p>You will be presented with a token, copy it and paste it into the following script in place of [TOKEN]:</p><pre>#! /bin/bash<br>curl -X POST \<br>-H &quot;Authorization: Bearer [TOKEN]&quot; \<br>-H &quot;Content-Type: application/json&quot; \<br>-d &quot;{ \<br>    \&quot;message\&quot;: \&quot;$1\&quot;, \<br>    \&quot;title\&quot;: \&quot;REST API notification\&quot; \<br>    }&quot; \<br>https://[YOUR_HOME_ASSISTANT]/api/services/notify/[YOUR_PHONE_NOTIFICATION_ID]</pre><p>Then replace [YOUR_HOME_ASSISTANT] with your Home Assistant address.</p><p>The next step is to go and find the device ID to paste it instead of [YOUR_PHONE_NOTIFICATION_ID]. Of course, you must already have the Home Assistant app installed on your device and you must have signed in before. The easiest way I found was to go to “Settings -&gt; Automations -&gt; New” and find this entry in the “Then do” section:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1N4UMAnbK7CXNTLT4-Jhw.png" /></figure><p>On this page you can also see which fields you can have in your JSON. Note that “message” is required, the rest is optional.</p><p>You can do this even if you run Home Assistant without a frontend. Refer to the Home Assistant REST API docs: <a href="https://github.com/home-assistant/developers.home-assistant/blob/master/docs/api/rest.md">https://github.com/home-assistant/developers.home-assistant/blob/master/docs/api/rest.md</a></p><p>Save the script (e.g., as ~/Tools/scripts/push_notify.sh), make it executable (chmod +x push_notify.sh), add it to your PATH (via ~/.bashrc), and use it like this from any other script, or test it directly:</p><pre>push_notify.sh &quot;Flashing done. Go check.&quot;</pre><p>Have fun with it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=852fa92f60ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[De-mixing in audio: separating audio sources from mixed recording]]></title>
            <link>https://medium.com/@viktor.mukha/de-mixing-in-audio-separating-audio-sources-from-mixed-recording-55a9093eded6?source=rss-7ac49f590be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/55a9093eded6</guid>
            <category><![CDATA[de-mixing]]></category>
            <category><![CDATA[music-production]]></category>
            <category><![CDATA[digital-signal-processing]]></category>
            <category><![CDATA[mixing-and-mastering]]></category>
            <dc:creator><![CDATA[Viktor Mukha]]></dc:creator>
            <pubDate>Thu, 30 Nov 2023 05:31:48 GMT</pubDate>
            <atom:updated>2024-01-30T19:52:12.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_K4mCjKMNM09O57yWzO7OA.jpeg" /></figure><p>This year I attended my second Audio Developer Conference — ADC 2023. In one of the talks, the legend Andrew Scheps himself briefly touched on a concept of de-mixing that I found fascinating and quite useful, so I thought I’d share what I learned.</p><p>First off, what is de-mixing? De-mixing in audio refers to the process of separating individual components or sources from a mixed audio signal. The final mix of a song or audio recording typically combines multiple elements, such as vocals, instruments, and effects, into a single stereo or multichannel file. The goal of de-mixing is to isolate these elements to allow for more precise control or manipulation of each component. You could also remix the material and add new recordings, such as completely replacing vocals. The possibilities and applications are quite broad.</p><p>Specific software that Andrew mentioned can be found on GitHub: <a href="https://github.com/inagoy/drumsep">https://github.com/inagoy/drumsep</a></p><p>This particular software is able to split a complete drum set recorded in one file into kick, snare, cymbals, and toms. There are some broken links in there, the model is missing, but you can find it if you look in the Issues section. I gave it a try and the results are quite amazing.</p><p>Looking at the README.md we can quickly see that the base work is here: <a href="https://github.com/adefossez/demucs">https://github.com/adefossez/demucs</a> This tool is capable of splitting your track into drums, bass, vocals, and “other”. Here is the author’s quick example of what this tool can do: <a href="https://soundcloud.com/honualx/sets/source-separation-in-the-waveform-domain">https://soundcloud.com/honualx/sets/source-separation-in-the-waveform-domain</a></p><p>Try it for yourself and you will not be disappointed!</p><p>One thing to note is that these tools require some processing power, and if you want good quality, be prepared to run them for several hours, at least the drumsep one.</p><p>GPU helps, I have tried the demucs GUI here <a href="https://github.com/CarlGao4/Demucs-Gui">https://github.com/CarlGao4/Demucs-Gui</a> and it takes just couple of seconds to split a typical song on my NVIDIA GeForce GTX 1060 mobile graphics card with CUDA, with great results! Do take a look at the minimal requirements in the README though.</p><p>Of course, there are other tools like this on the market, and I have not looked at any others, but these two are so impressive that I have stopped looking. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55a9093eded6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Custom Android Launcher — Why and How do I build one?]]></title>
            <link>https://medium.com/paradox-cat-tech-hub/custom-android-launcher-why-and-how-do-i-build-one-6a1b3af89d43?source=rss-7ac49f590be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a1b3af89d43</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[aosp]]></category>
            <category><![CDATA[android-launcher]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Viktor Mukha]]></dc:creator>
            <pubDate>Tue, 07 Nov 2023 16:00:46 GMT</pubDate>
            <atom:updated>2023-11-08T11:22:40.575Z</atom:updated>
            <content:encoded><![CDATA[<h3>Custom Android Launcher — Why and How do I build one?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WdedIjmgwZnG_ys4tCoL2w.jpeg" /></figure><blockquote>Disclaimer. I have presented most of this material at DroidCon 2023 in Berlin. If you prefer a video, you can find it here: <a href="https://www.droidcon.com/2023/08/01/custom-launcher-why-and-how-do-i-build-one/">https://www.droidcon.com/2023/08/01/custom-launcher-why-and-how-do-i-build-one/</a></blockquote><h3><strong>What is a launcher?</strong></h3><p>According to the source code of Android OS, a Launcher<strong> </strong>or a Home App is an <strong>application </strong>which “replaces the home screen and gives access to the contents and features of your device”. It is usually responsible for <em>listing and starting other applications </em>and for <em>hosting widgets.</em></p><p>Here is an example of a launcher:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*oUEMJvtE-BjGo-O6e62QyQ.png" /></figure><p>Guess what your phone screen would look like without a launcher? You would only see what is called System UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*eVk-JnNDcCuYA7-evFttpw.png" /><figcaption>No launcher in system (only System UI is visible)</figcaption></figure><p>A home app is essential for any Android system. Try to start your applications without it!</p><p>Every Android device comes with a pre-installed launcher. Device manufacturers may create their own home app, or simply reuse the vanilla launcher that comes with AOSP (Android Open Source Project). Since it is Open Source, you can actually inspect the original launcher source code. For instance, Launcher 3 for Android phones can be found here: <a href="https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/Launcher3/src/com/android/launcher3/Launcher.java">https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/Launcher3/src/com/android/launcher3/Launcher.java</a></p><p>User can choose default home app: Settings — Apps — Default Apps — Home app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/1*JZrEq-9jktq3GTg1-e6NaA.png" /><figcaption>Default home app chooser</figcaption></figure><p>A default launcher will be the default “HOME” action, which can be triggered by a hardware button or a swipe-up-from-bottom gesture. The selected default home application will always be at the bottom of the activity back stack. In simple words, if you keep going “BACK”, you will always arrive at the default launcher.</p><h3><strong>Why create new launcher?</strong></h3><p>There are multiple possible reasons:</p><ul><li>Performance</li><li>Features</li><li>Usability</li><li>Design</li><li>Customization</li></ul><p>These are the reasons behind every custom launcher you see in the Google Play Store. In fact, most of today’s stock launchers features today were once only available in custom launchers.</p><p>If you check Wikipedia, you will find a table with more than 60 launchers for phones/tablets only. Obviously, not all of them can keep up with Android development and some became obsolete when their features were integrated into stock launchers.</p><p>Another reason to create a new home app is the plethora of Android devices out there: phones, foldables, tablets, TVs, cars, wearables. They all need a launcher.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*EcreQUhPPVsKM2euMAkIHg.png" /><figcaption>Source: <a href="https://www.android.com/everyone/">https://www.android.com/everyone/</a></figcaption></figure><p>There are many possible applications for Android OS. Here are just a few of them.</p><ul><li>Vending machines, coffee machines, beer machines</li><li>Public transport: entertainment, info screens, ticket machines</li><li>Shared &amp; private transportation: cars, bikes, scooters</li><li>Smart home, IoT devices</li></ul><p>Of course, not all of them run Android (yet), but if they do, they all need a launcher.</p><h3><strong>How to develop a launcher?</strong></h3><p>First of all, make your application a launcher. Add this category to your intent filter in <strong>AndroidManifest.xml</strong>:</p><pre>&lt;category android:name=&quot;android.intent.category.HOME&quot; /&gt;</pre><p>Actual meaning of this category and other related ones can be found in <a href="https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/content/Intent.java">Intents.java</a>, here are the example definitions extracted from this file:</p><blockquote><strong>android.intent.category.HOME<br></strong>This is the home activity, that is the first activity that is displayed when the device boots.</blockquote><blockquote><strong>android.intent.category.HOME_MAIN (hidden API, only for platform)<br></strong>This is the home activity that is displayed when the device is finished setting up and ready for use.</blockquote><blockquote><strong>android.intent.category.SECONDARY_HOME<br></strong>The home activity shown on secondary displays that support showing home activities.</blockquote><blockquote><strong>android.intent.category.SETUP_WIZARD (hidden API, only for platform)<br></strong>This is the setup wizard activity, that is the first activity that is displayed when the user sets up the device for the first time.</blockquote><blockquote><strong>android.intent.category.LAUNCHER_APP (hidden API, only for platform)<br></strong>This is the home activity, that is the activity that serves as the launcher app from there the user can start other apps. Often components with lower/higher priority intent filters handle the home intent, for example SetupWizard, to setup the device and we need to be able to distinguish the home app from these setup helpers.</blockquote><p>Next step in becoming a launcher is to list the apps. To get a list of apps, use <strong>Package Manager’s </strong><a href="https://developer.android.com/reference/android/content/pm/PackageManager#queryIntentActivities(android.content.Intent,%20android.content.pm.PackageManager.ResolveInfoFlags)"><em>queryIntentActivities</em>()</a> API:</p><pre>val intent = Intent(Intent.ACTION_MAIN)<br>intent.addCategory(Intent.CATEGORY_LAUNCHER)<br>val flags = PackageManager.ResolveInfoFlags.of(<br>    PackageManager.MATCH_ALL.toLong())<br>val activities: List&lt;ResolveInfo&gt; =<br>    context.packageManager.queryIntentActivities(intent, flags)</pre><p>For ease of use, map this list to your app objects:</p><pre>data class App(<br>    val name: String,<br>    val packageName: String,<br>    val icon: Drawable?<br>)<br><br>val installedApps = activities.map { resolveInfo -&gt;<br>    App(<br>        name = resolveInfo.loadLabel(packageManager).toString(),<br>        packageName = resolveInfo.activityInfo.packageName,<br>        icon = resolveInfo.loadIcon(packageManager)<br>    )<br>}</pre><p>Start an app via such object:</p><pre>fun App.launch(context: Context) {<br>    val intent = context.packageManager.getLaunchIntentForPackage(packageName) ?: return<br>    context.startActivity(intent)<br>}</pre><h3><strong>How to display applications?</strong></h3><p>Let us start by looking at the existing user interface modalities. It seems that the world has settled on multi-screen navigation with a configurable grid of icons grouped with the app names.</p><p>However, grid is not the only option. Experiment with simple flat lists, embedded search or filtering using text or speech, fast scrolling using first letters, etc.</p><p>Take a look at <a href="https://play.google.com/store/apps/details?id=bitpit.launcher&amp;hl=de&amp;gl=US">Niagara Launcher</a>’s approach:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*qUAebM-LWA_8MTLzaaFJKA.gif" /></figure><p>Or it could be as simple as <a href="https://github.com/tanujnotes/Olauncher">OLauncher</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*9K63RGiZbHZrnHiTf_h6rA.gif" /></figure><p>Also, remember to give users a way to see all of their installed apps in one place. For example using an App Drawer which one could “draw” from the bottom of the screen with a swipe-up gesture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*1Kis35V7_UnVLTqLi-KlGQ.png" /></figure><p>That said, do not limit yourself to application icons and app widgets only. <strong>Get creative </strong>and build the user interface around what your users actually need. For example, a SpaceX rocket launcher (pun intended) might look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cVdqLhPTqvtUj2HjTZwNw.png" /><figcaption><em>Source: </em><a href="https://www.figma.com/community/file/855715967691534013"><em>https://www.figma.com/community/file/855715967691534013</em></a></figcaption></figure><h3>App Widgets</h3><p>A story about launchers would be incomplete without talking about App Widgets.</p><p>This is an example of a standard clock widget:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*ML0mWWEzL2Kjty4Xebc7MA.gif" /></figure><p>I will not bother you with details on implementation or widget types, you can find great official documentation <a href="https://developer.android.com/develop/ui/views/appwidgets/overview">here</a>. If you use Jetpack Compose, check out the <a href="https://developer.android.com/jetpack/androidx/releases/glance">Glance</a> library, it is truly great!</p><p>Instead, let us discuss <strong>the uses </strong>and <strong>limitations </strong>of App Widgets.</p><p>It is clear that widgets are quite useful for applications like calendar, clock, and weather. However, if you want to have something like a fully interactive map on your home screen all the time, App Widgets unfortunately are not going to cut it.</p><p>And why is that?</p><ul><li>Interaction. Gestures are limited to only <strong>touch </strong>and <strong>vertical swipe</strong>, so as not to conflict with Home App gestures.</li><li>UI. Not all UI elements are available, so you cannot create a full-featured home screen app as an App Widget.</li><li>Battery. By default, App Widgets refresh once every <strong>30 minutes (!)</strong>. That says a lot about the design decisions.</li></ul><p>But wait a minute, isn’t that what the default launcher of Android Automotive OS does? Showing a giant interactive map in a launcher?</p><p>Yes, it does:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1TjoSrwJrD3-TZ-P3monTw.png" /><figcaption>CarLauncher in AAOS based on Android 12</figcaption></figure><p>If it is not an App Widget, what is it?</p><p>In the <a href="https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/Car/Launcher/src/com/android/car/carlauncher/CarLauncher.java">source code</a>, Google calls these widgets “Cards”. Cards are implemented in terms of lower-level window management facilities. This facility used to be an <a href="https://cs.android.com/android/platform/superproject/+/android-11.0.0_r48:packages/apps/Car/Launcher/src/com/android/car/carlauncher/CarLauncher.java;l=41"><strong>ActivityView</strong></a>, which was deprecated and eventually removed in Android 12. Now it is a <a href="https://cs.android.com/android/platform/superproject/+/main:packages/apps/Car/Launcher/src/com/android/car/carlauncher/CarLauncher.java;l=58"><strong>TaskView</strong></a>, which is rightfully a <strong>hidden platform API</strong>.</p><p>What does <strong>“hidden platform API” </strong>mean for application developers? Simply put:</p><ul><li>it should not be used by non-system applications,</li><li>it will likely change in future Android version.</li></ul><p>Yes, there are ways to expose this API to applications, but if you want your application to survive Android updates, I urge you to consider a better design alternative.</p><p>Implement the element you want to “embed” directly in the launcher. As long as you have control over the providing app, you can extract the relevant code parts into common libraries and design proper communication between the “Widget” and the “App” yourself.</p><p>That said, your launcher should probably still support embedding App Widgets as well, some users depend on it.</p><p>We have covered a lot of ground in this story. To summarize, we have learned the following.</p><ul><li><strong>Launcher</strong> is a home screen <strong>application</strong>.</li><li>The world needs new launchers that are fast and stable.</li><li>Now you know how to <strong>make an application a launcher</strong>, how to <strong>list other applications</strong>.</li><li>You should support <strong>App Widgets</strong>, but do not let them limit your design.</li></ul><p>Be creative and focus on what your users need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a1b3af89d43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paradox-cat-tech-hub/custom-android-launcher-why-and-how-do-i-build-one-6a1b3af89d43">Custom Android Launcher — Why and How do I build one?</a> was originally published in <a href="https://medium.com/paradox-cat-tech-hub">Paradox Cat Tech Hub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>