Status Update
No update yet.
Comments
vi...@google.com
That's working as expected. Let's consult with Javier about his thoughts.
ag...@google.com
Did we get any input from Javier for this?
ar...@google.com
The current implementation after the fix is aligned with the foundation API AnchoredDraggable - I think it makes sense to provide an optional parameter for devs to provide the initial anchor to use, as it's hard to provide a reasonable default.
Let me know if you have different thoughts. : )
da...@google.com
I think it makes sense to provide an optional parameter for devs to provide the initial anchor to use, as it's hard to provide a reasonable default.
That sounds reasonable to me. Is there a separate bug for that or should I file one?
One thing that I think will be weird is that the size of the panes can come from that anchor or from PaneScaffoldDirective defaultPanePreferredWidth (possibly influenced by the hinge?). In an ideal world, I think we would have the sizes all come from anchors, but that wouldn't work today with three panes visible. I'll add a note to the doc on this.
en...@google.com
We don't have a separate bug for that but it's already being supported via:
rememberPaneExpansionState(
...
initialAnchoredIndex = i,
)
You raised a very good point about having parallel ways to set up pane sizes.
To me it's sort of reasonable as there are actually referring to different use cases and have different priorities -
- Hinge policies always have the highest priority.
- Pane expansion (and its anchors) are associated with layout splits, but less with the "roles" of the panes that occupy those splits.
Modifier.preferredWidthalways has the lowest priority - more like a fallback default.
I guess we can have more detailed explanation in the doc if this can be confusing?
ar...@google.com
Oh, it's in the remember call, perfect!
Yeah, it seems reasonable debating about the use cases, but I worry if it's reasonable for a developer who doesn't consider all that and just wants to show two panes? It's also even more nuanced since 2 only applies for two panes (e.g., if your app shows two panes in portrait on a Samsung Ultra tablet and three panes in landscape). Maybe in the kdoc we should have something similar to what you listed here and in DAC we can provide more context around these.
en...@google.com
Yeah that sounds good to me. I plan to have some time to refine our kdoc and samples no matter what. Let's maybe work on this in the upcoming alpha/beta period.
xa...@google.com
retriaging this to Raju.
I think these are packaged from a prebuilt managed by the renderscript team.
I do agree with Dan that we should probably look at using the NDK instead but it's a bigger change.
Elliott, not sure what link you are talking about?
en...@google.com
xa...@google.com
da...@google.com
That was enh :) I don't think the NDK and build-tools are currently coupled, and that would yet another dimension to the test matrix. It's probably better to keep the RS tools on whatever linker they build/test against. We're going to be replacing the linker in the NDK somewhat soon.
ar...@google.com
As for requiring NDK, I think we want to be mindful of requiring a 800+ MB download for a linker when previously this was not required.
en...@google.com
the little blue hyperlinks for "update Studio" or "update Gradle" or "regenerate something" or "install the NDK". seems like you could have one of those at least for "i need a linker from the NDK to build renderscript"?
> As for requiring NDK, I think we want to be mindful of requiring a 800+ MB download for a linker when previously this was not required.
do we have numbers on how many folks use renderscript with Studio? i'd guess that you're actually hurting regular users more by shipping three mostly-unused linkers. (but i don't _really_ want you to switch to the NDK --- i'm assuming that renderscript won't work with lld, so when the NDK removes the legacy linkers there won't be anyone to fix renderscript now they're all working on NNAPI instead.)
sr...@google.com
ra...@google.com
en...@google.com
dg...@google.com
en...@google.com
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
the other bit is just a warning that mips isn't supported at all.
ka...@gmail.com
I have a case where we have pre bundled native libraries both (32 and 64 bit libraries ) so in last module we have abifilters for 32 and 64 bit architecgtures
and I set gradlew to build rederscript by using these flags in build.gradle. In latest mac update we are unable to build for 32 bit.
renderscriptTargetApi 21
renderscriptSupportModeEnabled true
question : When this is enabled in gradlew can android copy pre built native libs for 32 instead of building using ndk as java will be build for 64 anyway?
Thanks
Karthik K.
zy...@gmail.com
First, thank you for all your effort. Really been enjoying Android programming :)!
I was wondering if there was an estimate as to when this issue will be fixed? It is causing issues in 3 of our major projects and we have no work around for it for now.
Thank you!
to...@gmail.com
ja...@specialized.com
We are seeing a similar issue for one of our projects. Downgrading OS is not really a workable solution for us.
Thanks!
je...@google.com
da...@google.com
This is the build-tools renderscript stuff, so it's not tied to the NDK release.
[Deleted User] <[Deleted User]>
da...@google.com
On Wed, Nov 6, 2019, 04:43 <buganizer-system@google.com> wrote:
dg...@google.com
dg...@google.com
$ file *ld
aarch64-linux-android-ld: Mach-O 64-bit executable x86_64
arm-linux-androideabi-ld: Mach-O executable i386
i686-linux-android-ld: Mach-O executable i386
mipsel-linux-android-ld: Mach-O executable i386
x86_64-linux-android-ld: Mach-O 64-bit executable x86_64
Why is Studio picking i686-linux-android-ld rather than x86_64-linux-android-ld?
dg...@google.com
dg...@google.com
ja...@specialized.com
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3
Please check and update your BuildTools.
warning: Linking two modules of different data layouts: '/home/circleci/code/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/home/circleci/code/app/build/generated/res/rs/staging/debug/raw/bc32/yuv420888.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /home/circleci/code/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/home/circleci/code/app/build/generated/res/rs/staging/debug/raw/bc32/yuv420888.bc' is 'armv7-none-linux-gnueabi'
:app:compileStagingDebugRenderscript FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileStagingDebugRenderscript'.
> A problem occurred starting process 'command '/home/circleci/code/sdk/build-tools/28.0.3/arm-linux-androideabi-ld''
ra...@google.com
um...@gmail.com
dg...@google.com
je...@google.com
We are currently testing a solution for this. There will be a fix released to both build tools and AGP soon.
dp...@gmail.com
kh...@gmail.com
js...@gmail.com
en...@google.com
are you seeing issues with anything other than just Renderscript? if so, please report them so we can look at them more urgently.
co...@zuricate.net
je...@google.com
Hi all, thank you for your patience and help.
We already have a solution ready and as are just trying to sync the release between AGP and build tools to get it out to you.
um...@gmail.com
js...@gmail.com
um...@gmail.com
an...@gmail.com
js...@gmail.com
[Deleted User] <[Deleted User]>
je...@google.com
The fixes have been published.
You must update your gradle plugin version to 3.6.0-rc02 or 4.0.0-beta1, and your build tools version to 29.0.3.
I'm closing this bug, but feel free to re-open it or submit a new one if you have additional problems.
mu...@gmail.com
mu...@gmail.com
wa...@gmail.com
an...@google.com
Release Track: (
Created: 2020-03-05 06:40:41.389592+00:00
Changes: ag/10486776, ag/10486797, ag/10448494, ag/10447464
an...@google.com
to...@gmail.com
03-25 07:29:20.025 18646-18760/? E/AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-1
Process:
androidx.renderscript.RSRuntimeException: Loading of ScriptC script failed.
at androidx.renderscript.ScriptC.<init>(ScriptC.java:83)
at com.airapp.ScriptC_rotator.<init>(ScriptC_rotator.java:34)
at com.airapp.utils.RenderScriptUtils$initialize$1.invokeSuspend(RenderScriptUtils.kt:27)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
It works on other devices
zy...@gmail.com
I had the same issue. I think I managed to fix it (steps to follow), but then still get that error for the Xiomi Redmi Go (which is SUPER weird cause its Android 8.1).
This is what I had to do:
1. Update your gradle to have
renderscriptTargetApi 22. <<< Was needed to be this high to have 64bit support (i think?)
renderscriptSupportModeEnabled false. << Was needed to fix the Android 6 issue, but it scares me a bit :P
2. Where you use it, change the imports to NOT be AndroidX, example:
import android.renderscript.Allocation;
import android.renderscript.Element;
import android.renderscript.RenderScript;
import android.renderscript.ScriptIntrinsicBlur;
From:
Sorry, I hope its allowed to post some solutions on this ticket? Not sure what the rules are for IssueTracker :(
Also, Please if there is a solution to get it to work on Xiomi Redmi Go as well, I would really appreciate the help! (OR if the above solution actually doesnt work, and coincidently my Android6 users just havent used the app since I updates - also let me know, cause them we both have a lot to panic about).
mi...@google.com
Could you try with build-tools 3.0.0rc1?
zy...@gmail.com
zy...@gmail.com
Crashed using AndroidX, crashed using android.support.v8.renderscript.RenderScript (so no android x in the whole project) and crashed using android.renderscript.RenderScript with the rest of the project on AndroidX.
E/RenderScript: Couldn't load libRSSupportIO.so
xa...@google.com
mi...@google.com
mi...@google.com
an...@google.com
he...@gmail.com
In build.gradle of app:
- ext.gradle_version = '3.5.3'
+ ext.gradle_version = '4.0.0'
And in gradle/wrapper/gradle-wrapper.properties:
-distributionUrl=https\://
+distributionUrl=https\://
bu...@gmail.com
Hi
[Deleted User] <[Deleted User]>
I updates my macOS to Catalina and suddenly RenderScript is not compiling.
Its complaining that some required components can not be found in Build-Tools 28.0.3.
Here is the full error print out:
The error Im getting is:
A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3 Please check and update your BuildTools. warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
Task :translation:compileDebugJavaWithJavac Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationResources.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationInterceptor.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details.
Task :data:generateDebugRFile
Task :commons-lang:compileJava Note: /Users/tobias/Repositories/app-android/commons-lang/src/main/java/tat/org/apache/commons/lang3/ArrayUtils.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details.
FAILURE: Build failed with an exception.
- What went wrong: Execution failed for task ':app:compileMinSdk19DevDebugRenderscript'.
A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
-
Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
BUILD FAILED in 5s
sr...@google.com
required components not found in Build-Tools 28.0.3 Please check and update your BuildTools.
I think you should update your BuildTools first, since 28.0.3 may not have all of the necessary fixes to support Catalina.
dg...@google.com
ta...@gmail.com
required components not found in Build-Tools 28.0.3 Please check and update your BuildTools.
I think you should update your BuildTools first, since 28.0.3 may not have all of the necessary fixes to support Catalina.
ta...@gmail.com
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
BUILD FAILED in 5s
is...@gmail.com
Eo
ba...@gmail.com
All security restricted off
sh...@gmail.com Restricted
ma...@gmail.com
[Deleted User] <[Deleted User]>
aa...@gmail.com
sh...@gmail.com
sh...@gmail.com
fa...@hotmail.com
<intent-filter ... > <action android:name="android.intent.action.EDIT" /> <action android:name="android.intent.action.INSERT" /> <action android:name="android.intent.action.DELETE" /> ... </intent-filter>
Description
Its complaining that some required components can not be found in Build-Tools 28.0.3.
Here is the full error print out:
The error Im getting is:
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3
Please check and update your BuildTools.
warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
> Task :translation:compileDebugJavaWithJavac
Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationResources.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationInterceptor.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
> Task :data:generateDebugRFile
> Task :commons-lang:compileJava
Note: /Users/tobias/Repositories/app-android/commons-lang/src/main/java/tat/org/apache/commons/lang3/ArrayUtils.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileMinSdk19DevDebugRenderscript'.
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at
BUILD FAILED in 5s