Google Android RAG SDK hiện chỉ đạt ~30% độ chính xác trên tập dữ liệu Lihua World, thấp hơn nhiều so với VecML (~75-85%). SDK này có thể chưa được tối ưu hóa, nhưng vẫn là lựa chọn đáng thử cho dev Android/iOS. #RAG #AndroidSDK #AI #GoogleAI #VecML #ỨngDụngDiĐộng

https://www.reddit.com/r/LocalLLaMA/comments/1nk4z97/google_android_rag_sdk_quick_comparison_study/

Android 16 is here

Android 16 is released, featuring updates for developers around performance, security, camera, and media to make apps more efficient and adaptive.

Android Developers Blog
The Fourth Beta of Android 16

Android 16 Beta 4, the final scheduled update, is now available with developer APIs and app-facing behaviors finalized, marking platform stability.

Android Developers Blog

So what is the Android team's intention? Should v3.1-only APKs be considered valid? Or not? My guess is they should be not considered valid since the Android team has explicitly marked that kind of signature as invalid since apksigner v30.0.0 (besides v33). Are there any plans to unified the code that verifies APK signatures?

#Android #AndroidSDK #APK #apksigner

2/2

Interesting bug in #apksigner reported to @fdroidorg: an APK with only a v3.1 signature was only considered valid by v33. <33 error out with "APK Signature Scheme v2 signature 0 indicates the APK is signed using APK Signature Scheme v3 but no such signature was found." >33 error out with "The APK contains a v3.1 signing block without a v3.0 base block". Android uses its own verify code and treats it as valid. https://gitlab.com/fdroid/fdroidserver/-/issues/1253

#AndroidSDK #APK

1/2

apksigner v33.0.x falsely verifies invalid APK which leads to wrong cert extracted for AllowedAPKSigningKeys (#1253) · Issues · F-Droid / fdroidserver · GitLab

With a specific configuration of fdroidserver and a specifically crafted APK, it is possible to bypass AllowedAPKSigningKeys. I could install the poc-v6.apk in an SDK-34...

GitLab

In the official release of the #AndroidSDK package "build-tools_r35.0.1_linux.zip", they included what looks like a hand-edited "source.properties" metadata file that is a key part of the "sdkmanager" packaging system:

```
Pkg.UserSrc=false
Pkg.UserSrc=false
Pkg.Revision=35.0.1
#Pkg.Revision=35.0.0 rc4h
```

I mean really? The Android SDK packages are not automatically generated?

https://gitlab.com/fdroid/sdkmanager/-/merge_requests/26

#android #sdkmanager

handle sloppy source.properties files (!26) · Merge requests · F-Droid / sdkmanager · GitLab

Looks like they put the intern on the v35.0.1 release, this is source.properties:

GitLab
The Second Developer Preview of Android 16

The second preview of Android 16 is available, allowing testing of new features and APIs, including richer haptics, adaptive refresh rate, and more.

Android Developers Blog

This is something I usually do during the 🎄 Christmas Holiday 🎄 ... this time I finished it a bit earlier... 👍 :

Here is the #recipe to build the #android 15 #sdk (#api #level 35) from source !

https://codeberg.org/Starfish/SDK-Rebuilds

So no need to download the binaries from G***le. Just compile by yourself. The #androidsdk is a collection of tools and binaries needed to #develop #android #apps .

Remember: #foss projects also need a free build chain.

Have fun and take care!

SDK-Rebuilds

SDK-Rebuilds

Codeberg.org
Introducing the Android XR SDK Developer Preview- Google Developers Blog

The Android XR SDK, a new platform for building extended reality (XR) experiences on Android, is now available for devs to try, and to give feedback.

(2/2)

@Suiseiseki
> GNUtoo doesn't post FUD

I'm not saying they're intentionally misleading us, rather that they may be confused. The truth of their claim seems to turn on what is meant by;

"The Android SDK is made available by Google under a proprietary license."

Maybe @fdroidorg can clarify what this means? Specifically, whether or not it translates to;

"F-Droid now uses the nonfree Google SDK to build the applications"

... as GNUtoo claims.

#AndroidSDK #FDroid #SoftwareFreedom