New Crowdin updates #1282
Open
New Crowdin updates #1282
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
And also Get rid of old and unused detail adapter Some other minor improvements
Signed-off-by: Anushek Prasal <[email protected]> Change-Id: I21b475316155862e43fb9a8bc81225b215809bbe Signed-off-by: Pranav Vashi <[email protected]>
* reference: https://t.me/MishaalAndroidNews/1414 * chatgpt is only temporary, additional ai assistant will be added once we found another ai assistant that is launchable via activity. Change-Id: I7be6ff0577eed41d714ac87bb2ddac0eb78d6a49 Signed-off-by: minaripenguin <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
* changed on chatgpt app v1.2024.170+ Change-Id: I2817c6134bebd95268ca5ad39f2f18a27a8ca2fc Signed-off-by: aswin7469 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
Will toggle private DNS between off and last used mode If no mode was selected will toggle to opportunistic Shows the active mode in subtitle text as such: Off for off Automatic for opportunistic and the hostname string for manual Signed-off-by: Pranav Vashi <[email protected]>
Co-authored-by: ShevT <[email protected]> Signed-off-by: cjh1249131356 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
- Requires config_voiceCapable to be false for this check to validate - Fixes QS tiles editing
Signed-off-by: Pranav Vashi <[email protected]>
* Iterating the mutable listeners list during configuration dispatch causes below crash 12-09 21:15:07.361 D/AndroidRuntime(2214): Shutting down VM 12-09 21:15:07.361 E/AndroidRuntime(2214): FATAL EXCEPTION: main 12-09 21:15:07.361 E/AndroidRuntime(2214): Process: com.android.systemui, PID: 2214 12-09 21:15:07.361 E/AndroidRuntime(2214): java.util.ConcurrentModificationException 12-09 21:15:07.361 E/AndroidRuntime(2214): at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1111) 12-09 21:15:07.361 E/AndroidRuntime(2214): at java.util.ArrayList$Itr.next(ArrayList.java:1064) 12-09 21:15:07.361 E/AndroidRuntime(2214): at kotlin.collections.CollectionsKt.filterNotNull(Unknown Source:16) 12-09 21:15:07.361 E/AndroidRuntime(2214): at com.android.systemui.statusbar.phone.ConfigurationControllerImpl.onConfigurationChanged(go/retraceme d43d4e7a8dd5b2e7eba70ac5852a31df7ec95eb6ed6791527c5ce29550f31e4c:30) 12-09 21:15:07.361 E/AndroidRuntime(2214): at com.android.systemui.SystemUIApplication.onConfigurationChanged(go/retraceme d43d4e7a8dd5b2e7eba70ac5852a31df7ec95eb6ed6791527c5ce29550f31e4c:36) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ConfigurationController.performConfigurationChanged(ConfigurationController.java:261) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ConfigurationController.handleConfigurationChangedInner(ConfigurationController.java:235) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ConfigurationController.handleConfigurationChanged(ConfigurationController.java:154) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ConfigurationController.handleConfigurationChanged(ConfigurationController.java:129) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ActivityThread.handleConfigurationChanged(ActivityThread.java:6948) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.servertransaction.ConfigurationChangeItem.execute(ConfigurationChangeItem.java:56) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.servertransaction.TransactionExecutor.executeNonLifecycleItem(TransactionExecutor.java:133) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:103) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2831) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.os.Handler.dispatchMessage(Handler.java:110) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.os.Looper.dispatchMessage(Looper.java:315) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.os.Looper.loopOnce(Looper.java:251) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.os.Looper.loop(Looper.java:349) 12-09 21:15:07.361 E/AndroidRuntime(2214): at android.app.ActivityThread.main(ActivityThread.java:9047) 12-09 21:15:07.361 E/AndroidRuntime(2214): at java.lang.reflect.Method.invoke(Native Method) 12-09 21:15:07.361 E/AndroidRuntime(2214): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:596) 12-09 21:15:07.361 E/AndroidRuntime(2214): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929) Signed-off-by: Pranav Vashi <[email protected]>
…inance * using luminance for caption decor background color results to a lot of visual issues, making the buttons hard to see. * this change follows OEM bevahiour like hyperOS/nothingOS etc. Signed-off-by: minaripenguin <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
Change-Id: I03ebd2e0e175f91fbc83fb9221724d7be5daf7ca Signed-off-by: Adithya R <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
neobuddy89: Create package to include in fwb base itself. Change-Id: Icb3933846fc38f7fe1679e7f1fd916c2c137671d Signed-off-by: Pranav Vashi <[email protected]>
Required by LMOFreeform. Change-Id: I97143a8b35af1432b9b12319bab5c1dfec9f9b34 Signed-off-by: Pranav Vashi <[email protected]>
Change-Id: I743aba4200a4d8786c09811de8a2cf5c574b885f Co-authored-by: Pranav Vashi <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
* The previous approach turned out to break Miracast screen mirroring, because of the windowing mode. * Instead of hardcoding desktop, use FLAG_SHOULD_SHOW_SYSTEM_DECORATIONS to detect our custom display, as it's impossible for that flag to be set on a non-default display on AOSP. * Make InputManagerCallback check desktop mode per-display, to match new behaviour. Change-Id: I4a701a2cb219e49d3f89aac35720a3ea5e37ec52 Signed-off-by: Dmitrii <[email protected]>
Since our floating window is created as a separate display, don't force them into desktop mode too when the developer setting is enabled. Change-Id: I341a4929294d0919499e8be115f76de722d6d00d Signed-off-by: Dmitrii <[email protected]>
…cal apps The reason for the flashing screen is that when starting a horizontal application from a vertical application, the application relaunch Bug: 390049399 Test: 1.turn on Auto_rotate 2.enter the vertical application 3.launching a horizontal application from a vertical application Google: 3452389 Change-Id: If1654352818686e6b6fe4310425652099aff5573
Signed-off-by: minaripenguin <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
…rvice instance is null
* this shouldn't be happening at all, so I'm just gonna add a null check here
* here's the stack trace
E SensorManager: Exception dispatching input event.
E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.rotationresolver.RotationResolverInternal.resolveRotation(android.rotationresolver.RotationResolverInternal$RotationResolverCallbackInternal, java.lang.String, int, int, long, android.os.CancellationSignal)' on a null object reference
E AndroidRuntime: at com.android.server.wm.WindowOrientationListener$OrientationSensorJudge.onSensorChanged(WindowOrientationListener.java:1193)
E AndroidRuntime: at android.hardware.SystemSensorManager$SensorEventQueue.dispatchSensorEvent(SystemSensorManager.java:886)
E AndroidRuntime: at android.os.MessageQueue.nativePollOnce(Native Method)
E AndroidRuntime: at android.os.MessageQueue.next(MessageQueue.java:335)
E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:161)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread.java:44)
E AndroidRuntime: at com.android.server.UiThread.run(UiThread.java:45)
Change-Id: I5e6f9c4af8bb9fba2e9d85696958232878c7a815
Signed-off-by: jhonboy121 <[email protected]>
Signed-off-by: Pranav Vashi <[email protected]>
…ower key double-click On a Pixel phone, open com.google.android.calculator and repeatedly press the power key twice in a short period of time, the calculator app will be shown on the keyguard, then click the power key twice again, we will find the screen is dark, caused by KEYGUARD_UNOCCLUDE Transition timed out for display not ready Reproduce the Method: 1. Open com.google.android.calculator 2. Continue to click the power key twice in a short period of time 3. When the top app is calculator, click the power key twice again Test result: UI is dark when powered on Change-Id: If7461b1c5827a6dc132ef70af38a78f86c3fe7d6
Thanks to Tobi to figure out the fix for FaceSense needing a reboot to work after registering a face model.
Also thanks to someone5678 for fixing compile on QPR1.
neobuddy89: Updated for A15.
Squashed:
From: COSMIC <[email protected]>
Date: Fri, 13 Dec 2024 13:38:26 +0530
Subject: services: Adapt face sense to A15-QPR1
Signed-off-by: Pranav Vashi <[email protected]>
Change-Id: I1b83429a793a50fba292a38dbf5aa8a54ae5ace3
Co-authored-by: Adithya R <[email protected]>
Co-authored-by: Tobias Merkel <[email protected]>
Co-authored-by: someone5678 <[email protected]>
Co-authored-by: aswin7469 <[email protected]>
Signed-off-by: Pranav Vashi <[email protected]>
* We allows devices to use their own FaceService as ParanoidSense has weak modality * To make above impl complete, conditionally add ParanoidSense and un-comment AIDL provider support Change-Id: I7321580b87499f4020d3b080779e2f9cb1a6fce6 Signed-off-by: Pranav Vashi <[email protected]>
Signed-off-by: minaripenguin <[email protected]>
Co-authored-by: jhenrique09 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
Signed-off-by: Pranav Vashi <[email protected]> Signed-off-by: AnierinB <[email protected]>
mnri: move face indicator to top, rewrite code and fix inconsistencies niv: Update for U QPR3 Co-authored-by: jhenrique09 <[email protected]> Co-authored-by: someone5678 <[email protected]> Co-authored-by: Alvin Francis <[email protected]> Signed-off-by: Pranav Vashi <[email protected]> Signed-off-by: minaripenguin <[email protected]> Signed-off-by: Alvin Francis <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
Change-Id: I59238cc73de96dad43429ba1dcdb583232772633 Signed-off-by: rmp22 <[email protected]>
Change-Id: Id216d9b6675e05d929d1ef61e5d76a8f43a4c27e Signed-off-by: rmp22 <[email protected]>
* It seems that AOSP code migration has some pending clean up which creates issue of not honoring setConfirmationRequired(false) for biometric prompt. * Let's disregard app setting and follow only user setting whether or not confirm face unlock prompt is required. Signed-off-by: Pranav Vashi <[email protected]>
* Current AOSP implementation checks if HIDL/AIDL configs available and skips registering providers if configs not available. * Fix NPE case in BiometricScheduler by replicating old path. Signed-off-by: Pranav Vashi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.