In custom Android ROM (latest crDroid), fix "Streamed Install" adb bug
Budget: €30 – €250 EUR
!͟!͟ ͟R͟I͟G͟H͟T͟ ͟U͟P͟ ͟F͟R͟O͟N͟T͟:͟ ͟t͟h͟i͟s͟ ͟p͟l͟a͟t͟f͟o͟r͟m͟ ͟d͟o͟e͟s͟n͟'͟t͟ ͟a͟l͟l͟o͟w͟ ͟a͟ ͟c͟u͟s͟t͟o͟m͟ ͟b͟u͟d͟g͟e͟t͟ ͟l͟i͟m͟i͟t͟.͟ ͟M͟y͟ ͟l͟i͟m͟i͟t͟ ͟f͟o͟r͟ ͟t͟h͟i͟s͟ ͟p͟r͟o͟j͟e͟c͟t͟ ͟=͟ ͟t͟h͟e͟ ͟u͟p͟p͟e͟r͟ ͟b͟i͟d͟d͟i͟n͟g͟ ͟l͟i͟m͟i͟t͟ ͟f͟o͟r͟ ͟y͟o͟u͟ ͟i͟s͟ ͟€͟/͟ ͟U͟S͟ ͟$͟ ͟6͟0͟ ͟!͟!͟
I'm facing some trouble using crDroid 10.2 custom ROM with my Nokia 6.1 (PL2). There's an issue when I use adb to install APKs via Terminal, verified in Windows and macOS. There are no error messages, but 'adb install any.apk' command in Terminal gets stuck at the 'Performing Streamed Install' stage. However, it works well with:
- other very similar Android 14 ROMs for the same phone incl. the slightly older crDroid 10.0 version
- LineageOS 21 which crDroid is based upon
- my Samsung A8 phone
I'm seeking a freelancer with a good grasp on:
- the Android system
- adb commands and functionality
- Proficiency in troubleshooting with either macOS or Windows (Linux not tested)
Further requirement to be met on your side is a Android phone with unlocked bootloader onto which you can install the latest crDroid 10.2+ - compatibility see https://crdroid.net/downloads, or an unofficial 10.2+ build, to see if you can reproduce this issue
The task here is to identify the anomaly and fix the issue so even the latest crDroid custom ROM for my Nokia 6.1 can again communicate and function seamlessly via adb with my Intel Mac running macOS Monterey 12.7.4. In-depth knowledge in the anatomy of Android and adb are required towards fixing this issue.
In your job offer, first and above all include the following information:
1. Which Android phone do you have (Model + exact model identifier)?
2. Have you unlocked your phone's bootloader so you can install a custom ROM to it (Y/N)?
3. Can you install crDroid to it for testing, e.g. if it's an A/B device so you can install it into the inactive slot (Y/N)?
!! ????: ?? ??????? ???????????? ????/ ????? ?????? ???-??? ???-??????, ?????? !!
Though not required, desired OS on your computer for optimal debugging would be macOS, preferably (but also not required) a) Intel, and b) Monterey 12.7.4 (or higher). If it's Windows or Linux, we can hope that if you managed to solve this adb streamed install issue with your production OS, that I can also report it solved with macOS.
All technical Details from my side:
- Device: Nokia 6.1 "2018" (PL2) TA-1043 https://www.gsmarena.com/nokia_6_1-8972.php
- ROM: latest crDroid 10.2 2024-03-18 build from https://crdroid.net/PL2/10 (all older 10.2 builds from https://sourceforge.net/projects/crdroid/files/PL2/10.x/ are affected by this bug, too)
- adb: latest v.35.0.1-11580240 in both, macOS and Windows
- 'adb devices' correctly issues:
List of devices attached
PL2GAR9842318434 device
- all other adb commands I tested work
- MacBook arch: Intel
- OS: my daily driver is still Monterey latest 12.7.4, but the bug also occurs in macOS Sonoma and in Windows 11
Steps which did not help:
- rebooting both, Nokia and Mac/ Computer
- using all possible USB ports and several cables
- adding the -r switch 'adb install -r path/to/some/android-app.apk'
- trying the install command in a different user account
- adb: downgrading version-by-version down all the way to 5 versions before the current one, and regardless if installed from Google or via homebrew (Mac) and choco (Windows)
- tried all the hints and tips from https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300 and https://stackoverflow.com/questions/31638582/android-adb-devices-unauthorized, to no avail
- adb logcat -d -b main -b system -b events -v time > logcat.txt
- install and root the ROM with Magisk 27.0
Not affected closely akin ROMs:
- "crDroid 10.0 UNofficial for Nokia 6.1 (PL2)" from https://xdaforums.com/t/rom-unofficial-14-pl2-crdroid-10-vanilla.4645786/
- "[OFFICIAL] LineageOS 21 for the Nokia 6.1 (2018)/6.1 Plus", tested latest nighly from https://download-static.lineageos.org/PL2
Steps to reproduce:
Mobile device:
1. enable dev options > USB debugging
2. connect your device to your Mac via USB > confirm authentication
Computer:
1. install adb
2. in Terminal: adb devices && adb install -r path/to/some/android-app.apk (adapt the path)
Does it get stuck at "Performing Streamed Install", or finish with "Success"?
I've posted this issue into the XDA-forum topic, the Nokia 6.1 PL2 crDroid Telegram group and the general crDroid group, but haven't received feedback (let alone support) yet, so at this point cannot even tell if this bug affects all of crDroid 10.2 in general, or only this particular crDroid 10.2 for Nokia 6.1 build.
Desired Solution:
Find the file(s) in the ROM that require(s) editing to solve this bug
Alternative solutions:
- either update the crDroid 10.0 UNofficial ROM (link see above) to crDroid 10.2(+) and verify resolution of the issue
- or mod/ patch the latest "LineageOS 21 for Nokia 6.1 (2018)/6.1 Plus" into crDroid 10.2(+)
I'm facing some trouble using crDroid 10.2 custom ROM with my Nokia 6.1 (PL2). There's an issue when I use adb to install APKs via Terminal, verified in Windows and macOS. There are no error messages, but 'adb install any.apk' command in Terminal gets stuck at the 'Performing Streamed Install' stage. However, it works well with:
- other very similar Android 14 ROMs for the same phone incl. the slightly older crDroid 10.0 version
- LineageOS 21 which crDroid is based upon
- my Samsung A8 phone
I'm seeking a freelancer with a good grasp on:
- the Android system
- adb commands and functionality
- Proficiency in troubleshooting with either macOS or Windows (Linux not tested)
Further requirement to be met on your side is a Android phone with unlocked bootloader onto which you can install the latest crDroid 10.2+ - compatibility see https://crdroid.net/downloads, or an unofficial 10.2+ build, to see if you can reproduce this issue
The task here is to identify the anomaly and fix the issue so even the latest crDroid custom ROM for my Nokia 6.1 can again communicate and function seamlessly via adb with my Intel Mac running macOS Monterey 12.7.4. In-depth knowledge in the anatomy of Android and adb are required towards fixing this issue.
In your job offer, first and above all include the following information:
1. Which Android phone do you have (Model + exact model identifier)?
2. Have you unlocked your phone's bootloader so you can install a custom ROM to it (Y/N)?
3. Can you install crDroid to it for testing, e.g. if it's an A/B device so you can install it into the inactive slot (Y/N)?
!! ????: ?? ??????? ???????????? ????/ ????? ?????? ???-??? ???-??????, ?????? !!
Though not required, desired OS on your computer for optimal debugging would be macOS, preferably (but also not required) a) Intel, and b) Monterey 12.7.4 (or higher). If it's Windows or Linux, we can hope that if you managed to solve this adb streamed install issue with your production OS, that I can also report it solved with macOS.
All technical Details from my side:
- Device: Nokia 6.1 "2018" (PL2) TA-1043 https://www.gsmarena.com/nokia_6_1-8972.php
- ROM: latest crDroid 10.2 2024-03-18 build from https://crdroid.net/PL2/10 (all older 10.2 builds from https://sourceforge.net/projects/crdroid/files/PL2/10.x/ are affected by this bug, too)
- adb: latest v.35.0.1-11580240 in both, macOS and Windows
- 'adb devices' correctly issues:
List of devices attached
PL2GAR9842318434 device
- all other adb commands I tested work
- MacBook arch: Intel
- OS: my daily driver is still Monterey latest 12.7.4, but the bug also occurs in macOS Sonoma and in Windows 11
Steps which did not help:
- rebooting both, Nokia and Mac/ Computer
- using all possible USB ports and several cables
- adding the -r switch 'adb install -r path/to/some/android-app.apk'
- trying the install command in a different user account
- adb: downgrading version-by-version down all the way to 5 versions before the current one, and regardless if installed from Google or via homebrew (Mac) and choco (Windows)
- tried all the hints and tips from https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300 and https://stackoverflow.com/questions/31638582/android-adb-devices-unauthorized, to no avail
- adb logcat -d -b main -b system -b events -v time > logcat.txt
- install and root the ROM with Magisk 27.0
Not affected closely akin ROMs:
- "crDroid 10.0 UNofficial for Nokia 6.1 (PL2)" from https://xdaforums.com/t/rom-unofficial-14-pl2-crdroid-10-vanilla.4645786/
- "[OFFICIAL] LineageOS 21 for the Nokia 6.1 (2018)/6.1 Plus", tested latest nighly from https://download-static.lineageos.org/PL2
Steps to reproduce:
Mobile device:
1. enable dev options > USB debugging
2. connect your device to your Mac via USB > confirm authentication
Computer:
1. install adb
2. in Terminal: adb devices && adb install -r path/to/some/android-app.apk (adapt the path)
Does it get stuck at "Performing Streamed Install", or finish with "Success"?
I've posted this issue into the XDA-forum topic, the Nokia 6.1 PL2 crDroid Telegram group and the general crDroid group, but haven't received feedback (let alone support) yet, so at this point cannot even tell if this bug affects all of crDroid 10.2 in general, or only this particular crDroid 10.2 for Nokia 6.1 build.
Desired Solution:
Find the file(s) in the ROM that require(s) editing to solve this bug
Alternative solutions:
- either update the crDroid 10.0 UNofficial ROM (link see above) to crDroid 10.2(+) and verify resolution of the issue
- or mod/ patch the latest "LineageOS 21 for Nokia 6.1 (2018)/6.1 Plus" into crDroid 10.2(+)