<?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 Abhimanyu Sharma on Medium]]></title>
        <description><![CDATA[Stories by Abhimanyu Sharma on Medium]]></description>
        <link>https://medium.com/@abhimanyu-sde?source=rss-ef272a0df89------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jRtwZZKAkwukjqyHI1kgNA.jpeg</url>
            <title>Stories by Abhimanyu Sharma on Medium</title>
            <link>https://medium.com/@abhimanyu-sde?source=rss-ef272a0df89------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:20:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhimanyu-sde/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[The Silent Weight of a Man’s Life]]></title>
            <link>https://medium.com/@abhimanyu-sde/the-silent-weight-of-a-mans-life-f26844cc2e03?source=rss-ef272a0df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/f26844cc2e03</guid>
            <category><![CDATA[fatherhood]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[family]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[time]]></category>
            <dc:creator><![CDATA[Abhimanyu Sharma]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 06:57:05 GMT</pubDate>
            <atom:updated>2026-04-28T06:57:05.486Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Unspoken Architecture of Duty</h3><p><strong>By Abhimanyu Sharma<br></strong><em>Reading time: 6 min</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3rQaxnvFbg1i3Fxu714Gow.png" /></figure><p>The alarm doesn’t care about the quality of your dreams. It doesn’t care if your mind was finally, for a few hours, untethered from the gravity of reality. It screams with a digital indifference, and before Kartik’s eyes are even open, the inventory begins.</p><p>It’s a weight he feels before he feels the floorboards. The mortgage payment due on the 15th. The school project his son mentioned last night. The pending pull request on GitHub that’s been sitting for twelve hours. The growing list of medicines his father needs.</p><p>One by one, the responsibilities land on his chest: <strong>a stack of invisible bricks.</strong> He doesn’t groan. He doesn’t hit snooze. He simply exhales, sits up, and prepares to be the foundation again.</p><h3>The Driveway Ritual</h3><p>The engine of the SUV ticked as it cooled, the only sound in the driveway other than the distant bark of a neighbor’s dog. Kartik didn’t reach for the door handle. Not yet.</p><p>In the dashboard light, his face looked tired — the kind of tired sleep doesn’t fix. On the seat beside him lay his phone, a gateway to the logic of his work world, full of GitHub notifications and urgent pings. Behind him, through the glass of the front door, he could see the warm yellow glow of his living room. He could see the blurred shape of his son running past the window.</p><p><strong>This was the ritual.</strong> The ten minutes where he wasn’t a Director, or a Son, or a Father. He was just a man in a metal box.</p><blockquote><em>“Sometimes he played a song — something fast and loud that reminded him of the ‘Freebird’ he used to be when he was twenty and the world felt like a suggestion rather than a set of rules.”</em></blockquote><p>He began the “Switch.” He consciously pushed back the millions of thoughts about the mortgage and the code. He smoothed his face, practiced a smile that reached his eyes, and exhaled. He couldn’t go in there as the Overthinker. They needed the Foundation.</p><h3>The Wish-Fulfillment Engine</h3><p>Watching his son play was like watching a version of himself that hadn’t yet learned how to carry things. The boy moved with a light, easy grace, his mind occupied only by the trajectory of a plastic cricket ball.</p><p>He had made a silent vow the day he held the boy for the first time: <em>there should be nothing he wants or wishes for that he doesn’t have.</em> It was a heavy vow. It meant Kartik had to be a machine of provision. If it meant working another hour, fixing another bug, or sacrificing another night’s sleep, he would do it. The reward wasn’t a thank you; the reward was the boy’s total ignorance of how much things cost. The reward was the boy’s freedom to just be a child.</p><h3>The Liquid Silence</h3><p>The condensation on the bottle felt like the only thing grounding him to the present. Kartik took a long pull of the beer, the bitterness cutting through the mental fog that had been building since Monday.</p><p>Through the window, he could hear the faint sounds of a cricket match on the TV — another layer of noise. But out here on the balcony, with the cold glass in his hand, he could let the “Freebird” out for a moment. He wasn’t thinking about the next app update or the school fees.</p><p><strong>He realized then that he didn’t drink for the taste; he drank for the pause.</strong> It was the only time the millions of thoughts slowed down long enough for him to catch his breath.</p><h3>The Architecture of Peace</h3><p>The millions of thoughts were still there, but tonight, they didn’t feel like a storm. They felt like the pulse of a city — steady, hummable, manageable. Kartik looked at the reflection in the glass door. He saw the toys on the floor, the remnants of a day well-lived by people who didn’t have to worry about the foundations.</p><p>He understood now that the silent weight wasn’t a prison. <strong>It was a legacy.</strong> His silence was the shield that allowed his family to dream. He was the unseen structure, the deep architecture of their lives. There was a quiet pride in that. He wasn’t just a provider; he was a creator of peace.</p><p>He finished his beer, went inside, and quietly put the last toy back in the box. He walked to the bedroom and took his partner’s hand. He didn’t say he was fine. He just said, “It was a long day, but I’m glad I’m home.”</p><h3>Epilogue: The Next Driveway</h3><p>Tomorrow at 5:45 AM, the inventory would begin again. The weight would return, the mask would be applied, and the million thoughts would start their dance.</p><p>But Kartik would be ready. Because now he knew that the weight didn’t just push him down — it kept him grounded. It made him real. And as long as the foundation held, the house would always be home…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hPtiqmLpFfkfhRQrnKWrpA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f26844cc2e03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Implementing eSIM Installation Flow in Native Android — A Complete Developer Guide]]></title>
            <link>https://medium.com/@abhimanyu-sde/implementing-esim-installation-flow-in-native-android-a-complete-developer-guide-1ad691606d55?source=rss-ef272a0df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ad691606d55</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[native-android-app]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[installation]]></category>
            <category><![CDATA[esim]]></category>
            <dc:creator><![CDATA[Abhimanyu Sharma]]></dc:creator>
            <pubDate>Fri, 10 Oct 2025 06:38:07 GMT</pubDate>
            <atom:updated>2025-10-10T06:46:34.320Z</atom:updated>
            <content:encoded><![CDATA[<h3>🚀 Implementing eSIM Installation Flow in Native Android — A Complete Developer Guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZkAz1UItvX0OlzWE_72KNA.png" /></figure><p>If you’ve ever tried integrating <strong>eSIM installation</strong> into your Android app, you probably realised something:</p><blockquote><em>⚠️ </em><strong><em>There’s almost no proper documentation on the Android Developers website!</em></strong></blockquote><p>When I faced this, I spent hours experimenting with different approaches — until I finally got it working in the simplest, most reliable way.<br> In this article, I’ll walk you through how I implemented eSIM installation in Android, what’s actually required, and how you can do it too.</p><h3>🧩 The Problem</h3><p>Android introduced <strong>eSIM support</strong> with <strong>Android 9 (API 28)</strong> via the EuiccManager API.<br> However, when you try to integrate it, you quickly notice that <strong>critical parts of the flow (like AIDL provisioning)</strong> are poorly documented or missing entirely.</p><p>This post explains how to bridge that gap with a working example.</p><h3>⚙️ High-Level Overview</h3><p>Here’s what the process looks like:</p><ol><li>Fetch the <strong>eSIM profile activation code</strong> usually looks like :</li></ol><pre>// Dummy LPA<br>LPA:1$consumer.e-sim.global$TN20241211123456784179E1</pre><ol><li>Pass it to the <strong>system eSIM installer (LPA)</strong>.</li><li>Expose it via a <strong>custom AIDL-based provisioning service</strong>.</li><li>Trigger the system activation flow.</li></ol><h3>💡 Step 1: Activity Setup</h3><p>We’ll start by launching the eSIM activation intent when it’s ready. (I assume you already have the activation code provided by your esim Carrier).</p><pre><br>@AndroidEntryPoint<br>class ESimInstaller : AppCompatActivity() {<br>  <br><br>private val launcher = registerForActivityResult(<br>        ActivityResultContracts.StartActivityForResult()<br>    ) { result -&gt;<br>        when (result.resultCode) {<br>            RESULT_OK -&gt; Toast.makeText(this, &quot;eSIM installed&quot;, Toast.LENGTH_SHORT).show()<br>            RESULT_CANCELED -&gt; Toast.makeText(this, &quot;eSIM install cancelled&quot;, Toast.LENGTH_SHORT).show()<br>            else -&gt; finish()<br>        }<br>    }<br><br>    @RequiresApi(Build.VERSION_CODES.P)<br>    override fun onCreate(savedInstanceState: Bundle?) {<br>        super.onCreate(savedInstanceState)<br>         <br>        startEsimActivationFlow(YOUR_LPA_ACTIVATION_CODE)<br>         <br>    }<br>}</pre><p>Once the data is available, we call startWithCode() to trigger the installation.</p><h3>⚡ Step 2: Trigger eSIM Installation</h3><p>Here’s the key part — launching the <strong>system eSIM installer</strong> using EuiccManager.</p><pre>private fun startEsimActivationFlow(lpaCode: String) {<br>    if (Build.VERSION.SDK_INT &lt;= Build.VERSION_CODES.TIRAMISU) {<br>        Toast.makeText(this, &quot;eSIM installation isn’t supported through the app. Please install manually from settings.&quot;, Toast.LENGTH_SHORT).show()<br>        openEsimSettings()<br>        return<br>    }<br><br>ActivationCodeStore.set(lpaCode)<br><br>    val intent = Intent(EuiccManager.ACTION_START_EUICC_ACTIVATION).apply {<br>        putExtra(EuiccManager.EXTRA_USE_QR_SCANNER, false)<br>    }<br>    launcher.launch(intent)<br>}</pre><p>We temporarily store the activation code and let the <strong>system LPA (Local Profile Assistant)</strong> handle the actual provisioning.</p><h3>🧠 Step 3: The Role of AIDL in eSIM Activation</h3><p>Now, here’s where many developers get stuck — understanding <strong>why AIDL is needed</strong>.</p><p>When you trigger the eSIM activation intent, the system’s <strong>LPA (Local Profile Assistant)</strong> tries to fetch the activation code from your app.<br> But how does it communicate with your app securely and efficiently?<br> That’s where <strong>AIDL (Android Interface Definition Language)</strong> comes in.</p><h3>👉 Why AIDL?</h3><p>AIDL defines the <strong>IPC (Inter-Process Communication)</strong> contract between:</p><ul><li>The <strong>system process</strong> (LPA) that installs the eSIM, and</li><li>Your <strong>app</strong>, which provides the activation code (LPA URI).</li></ul><p>In short:</p><blockquote><strong><em>AIDL acts as a bridge between your app and the Android system service that performs the eSIM installation.</em></strong></blockquote><p>Without it, the system has no way to get your activation code programmatically.</p><h3>🧾 Step 4: Define AIDL Interfaces</h3><p>You’ll need two AIDL files in your aidl directory and can’t directly create AIDL files as you have enable it.</p><p>Add aidl flag in your app level build.gradleorbuild.gradle.kts</p><pre>buildFeatures {<br>        aidl = true<br>    }</pre><p>After successful sync, Go to:<br><strong>File &gt; New &gt; AIDL &gt; AIDL File and create these:</strong></p><pre>// ICarrierEuiccProvisioningService.aidl<br>package android.service.euicc;<br><br>import android.service.euicc.IGetActivationCodeCallback;<br><br>interface ICarrierEuiccProvisioningService {<br>    void getActivationCode(in IGetActivationCodeCallback callback);<br>    void getActivationCodeForEid(in String eid, in IGetActivationCodeCallback callback);<br>}</pre><pre>// IGetActivationCodeCallback.aidl<br>package android.service.euicc;<br><br>interface IGetActivationCodeCallback {<br>    void onSuccess(String activationCode);<br>    void onFailure(int errorCode, String errorMessage);<br>}</pre><p>These define how your app shares the activation code with the system securely.</p><h3>🔧 Step 5: Implement the Provisioning Service</h3><p>Now we implement the service that responds to the system’s request for the activation code.</p><pre>// CarrierEuiccProvisioningService.kt<br><br>class CarrierEuiccProvisioningService : Service() {<br>    private val binder = object : ICarrierEuiccProvisioningService.Stub() {<br>        override fun getActivationCode(callback: IGetActivationCodeCallback) {<br>            val code = ActivationCodeStore.get()<br>            if (code.isNullOrBlank()) {<br>                callback.onFailure(-1, &quot;No activation code available&quot;)<br>            } else {<br>                callback.onSuccess(code)<br>            }<br>        }<br><br>override fun getActivationCodeForEid(eid: String, callback: IGetActivationCodeCallback) {<br>            val code = ActivationCodeStore.get()<br>            if (code.isNullOrBlank()) {<br>                callback.onFailure(-2, &quot;No activation code for EID&quot;)<br>            } else {<br>                callback.onSuccess(code)<br>            }<br>        }<br>    }<br>    override fun onBind(intent: Intent?): IBinder = binder<br>}</pre><p>And declare it in your manifest:</p><pre>&lt;service<br>    android:name=&quot;.CarrierEuiccProvisioningService&quot;<br>    android:exported=&quot;true&quot;<br>    android:enabled=&quot;true&quot;&gt;<br>    &lt;intent-filter&gt;<br>        &lt;action android:name=&quot;android.service.euicc.action.BIND_CARRIER_PROVISIONING_SERVICE&quot; /&gt;<br>    &lt;/intent-filter&gt;<br>&lt;/service&gt;</pre><p>When the eSIM activation flow starts, Android binds to this service automatically, calls getActivationCode(), and installs the eSIM using your provided LPA code.</p><h3>⚠️ Step 6: Handle Unsupported Devices</h3><p>Not all Android devices (or carriers) support eSIM activation through apps.<br> In those cases, redirect users to eSIM settings manually:</p><pre>private fun openEsimSettings() {<br>    val possibleIntents = listOf(<br>        Intent(&quot;android.settings.ESIM_SETTINGS&quot;),<br>        Intent(Settings.ACTION_NETWORK_OPERATOR_SETTINGS),<br>        Intent(Settings.ACTION_WIRELESS_SETTINGS)<br>    )<br><br>for (intent in possibleIntents) {<br>        if (intent.resolveActivity(packageManager) != null) {<br>            startActivity(intent)<br>            return<br>        }<br>    }<br>    Toast.makeText(this, &quot;eSIM settings not available on this device&quot;, Toast.LENGTH_LONG).show()<br>}</pre><h3>💬 Pro Tip</h3><p>🧩 <strong>Test on Pixel Devices First</strong><br> Pixel devices (Pixel 4 and above) provide the cleanest, fully compliant eSIM stack — making debugging and validation much easier.<br> Other OEMs may restrict or modify eSIM behavior through carrier locks or custom UIs.</p><p>Always ensure your activation code follows the correct format:</p><pre>LPA:1$&lt;SMDP+ host&gt;$&lt;token&gt;</pre><h3>✅ Key Takeaways</h3><ul><li>The <strong>official documentation</strong> is incomplete — especially around AIDL provisioning.</li><li><strong>AIDL is the core communication bridge</strong> between your app and the system’s eSIM installer.</li><li>Implement a CarrierEuiccProvisioningService to supply your activation code dynamically.</li><li>Use <strong>fallback logic</strong> for unsupported devices or Android versions.</li><li>The flow is clean once understood: <strong>Fetch → Store → Trigger → Respond.</strong></li></ul><h3>🎯 Conclusion</h3><p>That’s the <strong>simplest, fully working eSIM installation flow</strong> for Android.<br> You don’t need to reverse-engineer hidden APIs or rely on vague examples — this setup works cleanly with the system LPA.</p><p>If you found this helpful, share it with other Android developers who are struggling with undocumented APIs — and save them a few hours of trial and error!</p><p><strong>Author:</strong> <em>Abhimanyu Sharma</em><br> <em>Mobile Developer | Android &amp; Flutter Enthusiast</em></p><p>💬 <em>Feel free to reach out if you face any hurdles while implementing this — happy to help fellow developers!</em></p><p><em>Email</em><strong><em>: </em>abhisharma95353@gmail.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ad691606d55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireless Android Debug: Plugin to Connect Android Devices Without USB Cables]]></title>
            <link>https://medium.com/@abhimanyu-sde/wireless-android-debug-plugin-to-connect-android-devices-without-usb-cables-c7ec3d5d053f?source=rss-ef272a0df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7ec3d5d053f</guid>
            <category><![CDATA[adb]]></category>
            <category><![CDATA[plugins]]></category>
            <category><![CDATA[android-debug-bridge]]></category>
            <category><![CDATA[android-studio-plugins]]></category>
            <category><![CDATA[jetbrains]]></category>
            <dc:creator><![CDATA[Abhimanyu Sharma]]></dc:creator>
            <pubDate>Fri, 03 Oct 2025 08:16:28 GMT</pubDate>
            <atom:updated>2025-10-03T08:16:28.556Z</atom:updated>
            <content:encoded><![CDATA[<p>As Android developers, we spend a lot of time connecting devices to our machines for debugging and testing. Traditionally, this has always meant keeping a USB cable handy. But let’s be honest — USB cables are not always reliable. They break, they get loose, and sometimes you just don’t have the right one nearby.</p><p>That’s why I built the <strong>Wireless Android Debug</strong> plugin — a simple yet powerful Android Studio plugin that lets you connect your device over Wi-Fi and debug without relying on cables.</p><h3>Why Wireless Debugging?</h3><ul><li><strong>Freedom from cables:</strong> No more searching for the right cable every time.</li><li><strong>Work comfortably:</strong> Move around without being tethered to your laptop.</li><li><strong>More reliable testing:</strong> Especially useful when testing multiple devices.</li></ul><h3>Features</h3><p>✨ <strong>One-click wireless connection</strong> — Connect Android devices easily using your device’s IP address.<br> ✨ <strong>Input validation</strong> — Ensures the entered IP address is correct.<br> ✨ <strong>Error handling</strong> — Clear troubleshooting messages when something goes wrong.<br> ✨ <strong>ADB availability check</strong> — Verifies that ADB is properly configured on your system.</p><h3>How to Use</h3><p>Getting started is simple:</p><p>🚀 Available now on the <strong>Android Studio Marketplace</strong> — just search for <em>Wireless Android Debug.</em></p><p>Or</p><p>Directly download it from Jetbrains Marketplace.<br><a href="https://plugins.jetbrains.com/plugin/28549-wireless-android-debug/edit">https://plugins.jetbrains.com/plugin/28549-wireless-android-debug/edit</a></p><h3>Steps to Connect :</h3><ol><li><strong>Connect your device via USB</strong> (only for the first time).</li><li><strong>Enable USB debugging</strong> in your device’s Developer Options.</li><li><strong>Authorize USB debugging</strong> when prompted on your device.</li><li>Open Android Studio and go to <strong>Tools &gt; Connect Android Device Wirelessly</strong>.</li><li>Enter your device’s <strong>IP address</strong>.</li><li>Disconnect the USB cable and enjoy <strong>wireless debugging</strong>!</li></ol><p>🔑 Note: The USB connection is only required during the initial setup. After that, you can connect wirelessly anytime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*kV5YSrVlPpl5TMVYBrFDFw.png" /></figure><h3>Requirements</h3><ul><li>Android SDK with <strong>ADB</strong> in your system PATH.</li><li>Both your laptop and device should be on the <strong>same Wi-Fi network</strong>.</li></ul><h3>Pro Tip</h3><p>👉 Keep your Android Studio updated to the latest version. Sometimes this simple step resolves unexpected connection issues and saves you from hours of troubleshooting.</p><h3>Final Thoughts</h3><p>The <strong>Wireless Android Debug</strong> plugin is my initiative to make Android development smoother. It removes small but frequent frustrations developers face with cables and brings a more reliable wireless debugging experience into your workflow.</p><p>If you’re ready to simplify your setup and focus more on building apps rather than fighting with USB cables, give it a try!</p><p>I’d love to hear your feedback, thoughts, or ideas to make it even better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7ec3d5d053f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Support Android’s 16 KB Page Size in Android & Flutter Apps (Step-by-Step Guide)]]></title>
            <link>https://medium.com/@abhimanyu-sde/how-to-support-androids-16-kb-page-size-in-android-flutter-apps-step-by-step-guide-6b9b878e2d1c?source=rss-ef272a0df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b9b878e2d1c</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[hybrid-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Abhimanyu Sharma]]></dc:creator>
            <pubDate>Wed, 01 Oct 2025 10:58:56 GMT</pubDate>
            <atom:updated>2025-10-01T10:59:25.126Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GT0lT7VWxunpRyXBdCT3bg.png" /></figure><h3>Introduction</h3><ul><li>With Android 15, the OS can run with <strong>16 KB memory pages</strong> in addition to the traditional 4 KB pages. <a href="https://developer.android.com/guide/practices/page-sizes?utm_source=chatgpt.com">Android Developers+1</a></li><li>Starting <strong>November 1, 2025</strong>, Google Play <strong>requires</strong> that new apps and updates targeting Android 15+ must support 16 KB page sizes. <a href="https://android-developers.googleblog.com/2025/05/prepare-play-apps-for-devices-with-16kb-page-size.html?utm_source=chatgpt.com">Android Developers Blog+1</a></li><li>If your app uses <strong>native code</strong> (C/C++ via NDK or native libraries in plugins), you must ensure your .so files are aligned properly; otherwise your app may fail or misbehave on 16 KB devices. <a href="https://developer.android.com/guide/practices/page-sizes?utm_source=chatgpt.com">Android Developers+2Android Developers Blog+2</a></li><li>Apps written purely in Kotlin/Java (without native dependencies) are already compatible, but you should still test. <a href="https://developer.android.com/guide/practices/page-sizes?utm_source=chatgpt.com">Android Developers+1</a></li></ul><p>This article will guide you through:</p><ol><li>Understanding what changes are necessary</li><li>How to inspect your APK for 16 KB compatibility</li><li>Configuration changes in Gradle / NDK</li><li>Steps specific to Flutter apps</li><li>Testing in a 16 KB environment</li><li>Common pitfalls and FAQs</li></ol><h3>🔎 Step 1: Check if Your App Supports 16 KB</h3><h3>Inspect APK / AAB</h3><ol><li>Open your .apk or .aab file in <strong>Android Studio APK Analyzer</strong>.</li><li>Look for <strong>native libraries (</strong><strong>.so files)</strong>.</li></ol><p>👉 If your app has <strong>no native code</strong> (pure Kotlin/Java), you’re safe ✅.<br> 👉 If you use native code or Flutter plugins, read on.</p><h3>🛠 Step 2: Updating Native Android Projects</h3><h3>If you’re using native C/C++ or the NDK:</h3><ol><li>Update your NDK &amp; Gradle plugin</li><li>In build.gradle:</li></ol><pre>android {<br>    ndkVersion &quot;26.1.10909125&quot; // or latest<br>}<br></pre><h3>🐦 Step 3: Updating Flutter Apps</h3><ol><li><strong>Upgrade Flutter &amp; Dart</strong></li></ol><pre>flutter upgrade flutter doctor</pre><p>2. <strong>Rebuild your app</strong></p><pre>flutter clean flutter build apk --release</pre><p><strong>3. Check plugins</strong></p><ul><li>Run flutter pub outdated to see if any plugins are old.</li><li>Update them using:</li></ul><pre>flutter pub upgrade</pre><ul><li>Replace with an alternative plugin if needed.</li></ul><p>Before making changes, you should <strong>analyze your existing build</strong> to see if any libraries are misaligned.</p><h3>Using Android Studio’s APK Analyzer</h3><ol><li>Build your release APK or AAB.</li><li>In Android Studio: <strong>Build &gt; Analyze APK…</strong></li><li>Select your APK or AAB.</li><li>Look under the <em>lib / native libraries</em> section. The analyzer (and Lint) may flag .so files that are not properly aligned. <a href="https://developer.android.com/guide/practices/page-sizes?utm_source=chatgpt.com">Android Developers+2DEV Community+2</a></li><li>Note which .so files are flagged — these belong to your own native code or to some dependency.</li></ol><p>From StackOverflow (example):</p><blockquote><em>“Analyzer will show affected .so library files … copy keywords from affected </em><em>.so and run </em><em>./gradlew app:dependencies to find which dependency caused it.”</em></blockquote><h3>🪄 Pro Tip: Update Android Studio First</h3><p>Before doing any of this, <strong>make sure you’re on the latest version of Android Studio</strong>.</p><p>👉 Sometimes, simply updating Android Studio + SDK Tools <strong>magically resolves 16 KB issues</strong> without extra work.</p><ul><li>Go to <strong>Help &gt; Check for Updates</strong> (Windows/Linux) or <strong>Android Studio &gt; Check for Updates</strong> (macOS).</li><li>Update everything under <strong>SDK Tools</strong> and <strong>NDK</strong> as well.</li></ul><p>🎉 This one step might save you hours of debugging!</p><h3>Conclusion &amp; Call to Action</h3><p>Switching to 16 KB page size is a behind-the-scenes change, but it has real impact on app performance and Google Play compliance. The earlier you start, the fewer surprises you’ll face.</p><p>✅ <strong>Action list:</strong></p><ol><li>Analyze your current app build (APK Analyzer)</li><li>Upgrade to AGP 8.5.1+ and NDK r28+</li><li>Rebuild native libraries (plugins &amp; custom code) with 16 KB alignment</li><li>Refactor any hardcoded page size logic</li><li>Test thoroughly in 16 KB emulator / real device</li><li>Watch Google Play Console for alignment warnings</li><li>Address plugin or dependency bugs early.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b9b878e2d1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>