circle_device-bp4a-userdebug or device-bp4a-userdebug?
Final Results
70%
circle_device-bp4a-userdebug
30%
device-bp4a-userdebug
Project CiRCLE/Project Kasumi Revived - Announcements pinned «circle_device-bp4a-userdebug or device-bp4a-userdebug?»
Hello everyone! So there's an interesting turn of events that impacts how Project CiRCLE 17 (2.0 PasuPare) is going to be developed.
Initially, the new Android version for CiRCLE was meant to be made solo by the lead developer, but because there's some work to be done to boot Android 17 on her device (Samsung Galaxy M34 5G), we instead decided to go a different path and outsource the testing part.
That's where YOU, the users, come in! From build errors to a fully booting and flawless build, we're looking for X6833B users to help us test the upcoming version of CiRCLE! If you don't have X6833B but another device that can boot Android 17, and it's an officially supported device, kindly request your maintainer to do CiRCLE bringup on and push the Android 17 trees to the "17.0" branch. Your maintainer should then notify us in the maintainers chat so that we know a new device is on the run. Let's do our best, shall we?
Looking forward to your input!
Initially, the new Android version for CiRCLE was meant to be made solo by the lead developer, but because there's some work to be done to boot Android 17 on her device (Samsung Galaxy M34 5G), we instead decided to go a different path and outsource the testing part.
That's where YOU, the users, come in! From build errors to a fully booting and flawless build, we're looking for X6833B users to help us test the upcoming version of CiRCLE! If you don't have X6833B but another device that can boot Android 17, and it's an officially supported device, kindly request your maintainer to do CiRCLE bringup on and push the Android 17 trees to the "17.0" branch. Your maintainer should then notify us in the maintainers chat so that we know a new device is on the run. Let's do our best, shall we?
Looking forward to your input!
🔥5
Cooking a small Easter egg for Lineage buildbots... 🤭
"No target" error is too boring, let's spice it up a little :D
yachiyo@runami-g770:/mnt/android/circle$ m bacon
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=16
CIRCLE_VERSION=1.2-20260809_135147-UNOFFICIAL-VANILLA-m34x
PRODUCT_SOURCE_ROOT_DIRS=-kernel/platform -prebuilts/misc/protobuf_vendorcompat
TARGET_PRODUCT=circle_m34x
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-2a-dotprod
TARGET_CPU_VARIANT=cortex-a55
HOST_OS=linux
HOST_OS_EXTRA=Linux-6.18.35-amd64-gxde-desktop-x86_64-GXDE-OS-25
HOST_CROSS_OS=windows
BUILD_ID=BP4A.251205.006
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/samsung/m34x vendor/samsung/s5e8825-common hardware/samsung_slsi-linaro/codec2 hardware/samsung_slsi-linaro/exynos hardware/samsung_slsi-linaro/exynos5 hardware/samsung_slsi-linaro/
graphics hardware/samsung_slsi-linaro/interfaces hardware/samsung_slsi-linaro/openmax hardware/samsung_slsi-linaro/sgpu device/samsung/s5e8825-common bootable/deprecated-ota hardware/google/interfaces hardware/goo
gle/pixel hardware/samsung hardware/samsung_slsi-linaro/exynos/cpboot_v3 hardware/samsung_slsi/libbt device/samsung/m34x
SOONG_ONLY=false
============================================
$(shell date -u +%Y%m%d_%H%M%S) was changed, regenerating...
Adding CUSTOM_LOCALES [ast_ES ckb_IQ ckb_IR gd_GB cy_GB fur_IT nn_NO] to PRODUCT_LOCALES [en_US en_US af_ZA am_ET ar_EG ar_XB as_IN az_AZ be_BY bg_BG bn_BD bs_BA ca_ES cs_CZ da_DK de_DE el_GR en_AU en_CA en_GB en_
IN en_XA es_ES es_US et_EE eu_ES fa_IR fi_FI fr_CA fr_FR gl_ES gu_IN hi_IN hr_HR hu_HU hy_AM in_ID is_IS it_IT iw_IL ja_JP ka_GE kk_KZ km_KH kn_IN ko_KR ky_KG lo_LA lt_LT lv_LV mk_MK ml_IN mn_MN mr_IN ms_MY my_MM
nb_NO ne_NP nl_NL or_IN pa_IN pl_PL pt_BR pt_PT ro_RO ru_RU si_LK sk_SK sl_SI sq_AL sr_Latn_RS sr_RS sv_SE sw_TZ ta_IN te_IN th_TH tl_PH tr_TR uk_UA ur_PK uz_UZ vi_VN zh_CN zh_HK zh_TW zu_ZA en_XC]
$(shell date -u +%Y%m%d_%H%M%S) was changed, regenerating...
[100% 2/2] initializing Make module parser
Adding CUSTOM_LOCALES [ast_ES ckb_IQ ckb_IR gd_GB cy_GB fur_IT nn_NO] to PRODUCT_LOCALES [en_US en_US af_ZA am_ET ar_EG ar_XB as_IN az_AZ be_BY bg_BG bn_BD bs_BA ca_ES cs_CZ da_DK de_DE el_GR en_AU en_CA en_GB en_
IN en_XA es_ES es_US et_EE eu_ES fa_IR fi_FI fr_CA fr_FR gl_ES gu_IN hi_IN hr_HR hu_HU hy_AM in_ID is_IS it_IT iw_IL ja_JP ka_GE kk_KZ km_KH kn_IN ko_KR ky_KG lo_LA lt_LT lv_LV mk_MK ml_IN mn_MN mr_IN ms_MY my_MM
nb_NO ne_NP nl_NL or_IN pa_IN pl_PL pt_BR pt_PT ro_RO ru_RU si_LK sk_SK sl_SI sq_AL sr_Latn_RS sr_RS sv_SE sw_TZ ta_IN te_IN th_TH tl_PH tr_TR uk_UA ur_PK uz_UZ vi_VN zh_CN zh_HK zh_TW zu_ZA en_XC]
[100% 22/22] including out/soong/late-circle_m34x.mk
Disabling ART_BUILD_TARGET_DEBUG
Disabling ART_BUILD_HOST_DEBUG
[100% 52/52] build bacon
FAILED: bacon
/bin/bash -c "vendor/circle/build/tools/lineage_build_compat.sh"
============================================
"bacon"?! What is it, a barbecue party?!
You're in CiRCLE. You have to perform a live performance to stay here.
============================================
16:53:21 ninja failed with: exit status 1
#### failed to build some targets (01:36 (mm:ss)) ####
Project CiRCLE/Project Kasumi Revived - Announcements pinned «Hello everyone! So there's an interesting turn of events that impacts how Project CiRCLE 17 (2.0 PasuPare) is going to be developed. Initially, the new Android version for CiRCLE was meant to be made solo by the lead developer, but because there's some work…»
Legacy device with Android 11 anyone?
👀4
Project CiRCLE/Project Kasumi Revived - Announcements
Legacy device with Android 11 anyone?
I'm talking about with custom Android 11 ROM btw, not stock
Channel name was changed to «Project CiRCLE/Project Kasumi Revived - Announcements»
From now on, all announcements will be tagged [Project CiRCLE] and [Project Kasumi Revived]
[Project Kasumi Revived]
The source should be all good to go, I'm currently compiling it for Teos
https://github.com/ProjectKasumi-Revived/manifest
The source should be all good to go, I'm currently compiling it for Teos
https://github.com/ProjectKasumi-Revived/manifest
❤3🤩2
[Project Kasumi Revived]
Also backported the release-keys patch, so you can drop your keys to vendor/kasumi-priv/keys and have your build signed as release-keys, enjoy
Also backported the release-keys patch, so you can drop your keys to vendor/kasumi-priv/keys and have your build signed as release-keys, enjoy
👍1
Project CiRCLE/Project Kasumi Revived - Announcements
[Project Kasumi Revived] Suffice to say, the source is buildable with the latest changes to Lineage, but there's still some work to be done (like the Discord invite).
Platform bugs so far
- QS tile tinting doesn't work (might remove the setting altogether)
- ROM info dashboard shows version as 1.4 (might remove the entry altogether)
- The Discord invite points to the old, dead, Kasumi server
- QS tile tinting doesn't work (might remove the setting altogether)
- ROM info dashboard shows version as 1.4 (might remove the entry altogether)
- The Discord invite points to the old, dead, Kasumi server
😭1
Thanks to everyone who wishes me a happy birthday! As much as I'd like to give an update to CiRCLE as my gift to you, I'm a little burnt out still, so I'll have to delay it.
To anyone who wants to give me a gift, you're not late! My brother's birthday is on August 30th, and that's the day my environment IRL will be celebrating my birthday!
To anyone who wants to give me a gift, you're not late! My brother's birthday is on August 30th, and that's the day my environment IRL will be celebrating my birthday!
🆒6🎉3😭1
[Project CiRCLE]
There's a problem where you don't get unlimited storage in the recent versions of Google Photos.
It was spotted by the YouTube channel "Random Repairs" that updating Google Photos gets rid of the unlimited storage capability on Project CiRCLE.
The workaround is to uninstall updates if you updated it, and disabling automatic updates.
I'm not planning to use a newer Pixel's feature XML since the feature XML we're using provides unlimited backup at original quality, whereas the feature XML from the newer Pixel provides unlimited backup at "high quality", which is compressed. They're not the same.
There's a problem where you don't get unlimited storage in the recent versions of Google Photos.
It was spotted by the YouTube channel "Random Repairs" that updating Google Photos gets rid of the unlimited storage capability on Project CiRCLE.
The workaround is to uninstall updates if you updated it, and disabling automatic updates.
I'm not planning to use a newer Pixel's feature XML since the feature XML we're using provides unlimited backup at original quality, whereas the feature XML from the newer Pixel provides unlimited backup at "high quality", which is compressed. They're not the same.
😭5👨💻3😁1
[Project Kasumi Revived]
There was a bug where enabling Google search bar in home settings would produce an empty space when Google app is updated. The bug has been pushed to the repos and that space should no longer stay empty.
The fix comes with a quirk though: When you install an app that overrides the detection (for example MIUI's System Launcher), that app's search bar appears instead of Google's.
There was a bug where enabling Google search bar in home settings would produce an empty space when Google app is updated. The bug has been pushed to the repos and that space should no longer stay empty.
The fix comes with a quirk though: When you install an app that overrides the detection (for example MIUI's System Launcher), that app's search bar appears instead of Google's.
😭1
What makes Project Kasumi smooth is the amount of optimizations we've inherited from other similar projects.
However, what makes Project CiRCLE smooth is the Lineage base itself.
However, what makes Project CiRCLE smooth is the Lineage base itself.
😭1