- May 17, 2024
-
-
-
-
-
nift4: port to Sv2, add navbar extra keys :D Change-Id: I1b47c354f19b134af0ff39018b843c01864827bb Signed-off-by:
Joey Huab <joey@evolution-x.org> Signed-off-by:
saikiran2001 <bjsaikiran@gmail.com>
-
Change-Id: Ie08dfa88f258fa9a2894f2e362d081217b0f1514 Signed-off-by:
SagarMakhar <sagarmakhar@gmail.com> Signed-off-by:
spezi77 <spezi7713@gmx.net>
-
[nift4: use activity alias instead] Change-Id: I6204ee33d73c56bf24cc41dcfb453db536e301e2 Signed-off-by:
-
power, volup, voldown nift4: port to 13 Change-Id: I7cfcd30b5d49001e97aa85c284220f0fa7e556dc Signed-off-by:
-
- May 13, 2024
-
-
-
This partially reverts commit ffb1601d. This revert does keep Controls in QS 100% intact, but it allows the power menu to have controls as well. You can even have both, if you want. 2022/11/05 - nift4: port to T 2023/01/20 - nift4: QPR rebase trick for future rebases: for i in packages/SystemUI/res/values-*/strings.xml; do git show de1606e3:$i | grep quick_controls_subtitle && sed -i "s#</resources>#$(git show de1606e3:$i | grep quick_controls_subtitle)\n</resources>#g" $i; done 2024/04/30 - ikeramat: port to u-qpr2 Change-Id: I384b9fe5ed0422a5ec2abcedaf624252f72e19fd
-
-
* Replace deprecated methods with the ones the android doc recommends as a replacement Change-Id: I1be5ba74da6f9a8e68bed4a0478675f90c9c28c6 Signed-off-by: -
* Fixes device control crash when interacting with cat control stacktrace: java.lang.RuntimeException: java.lang.IllegalArgumentException: 0|com.android.egg|1|com.android.egg.neko:allcats|10100 Not posted. PendingIntents attached to bubbles must be mutable at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:109) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7837) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) Change-Id: I1e755ce8a38cfefb1474bbfefd307767a436e9d0 Signed-off-by:PainKiller3 <ninadpatil100@gmail.com>
-
-
- May 09, 2024
-
-
- Apr 27, 2024
-
-
Dhina17 authored
Change-Id: I234cb314662572db0c86334c6b9676fcbac50917
-
- Apr 23, 2024
-
-
As of QPR2, we can't crate a media output dialog with empty package name unless the use_media_router2_for_info_media_manager flag is enabled. When the flag is enabled, we can always show the dialog by passing the actual package name, or null if the media controller is not available. If the flag is disabled, we can only show the dialog if the media controller is available. Change-Id: Ic8d08905bf55be91b547708b316ef7c96c81c492 Signed-off-by:danielml <daniel@danielml.dev>
-
- Apr 20, 2024
-
-
- fixes the line having different curves between played and unplayed section - before https://imgur.com/a/vn4smvb - after https://imgur.com/a/7rL4jV6 Change-Id: I2d2522c66341662eff74eb7d3686be7aa6e7ac5c
-
-
When opening pre-Nougat app that did not specify resizable attribute (pre Nougat era) and also is forced to portrait orientation in freeform and then resizing its window, system_server will crash due to invalid resize. To avoid whole device going down, we just catch the crash - app will stop working (window will be empty), BUT this is a much better thing to have than whole device crashing. This fix is even more needed because since Android 13, Google saves freeform bounds, which means when you reopen the unresizable app, it will instantly crash system_server again and you cannot ever again use this app in freeform without factory reset. The proper fix is to enable force resizable in developer settings, or asking the app devs to fix it (by making the app resizable). Further Framework-side fixes for this should be done by AOSP. Change-Id: I40d48c0caa9c376160f427d27260bd6bd5f66978
-
TaskOperations object is being created with default display context so it will provide the default display id only. It causes that back button is not working on external displays. Change-Id: Ia4772e898dda20fb16ae85f2b2652a17924e9a7c
-
In desktop mode, status bar won't be shown there. so we don't have to bother about caption bar visibility based on status bar (immersive mode) there. Change-Id: I418c44cec81a7f939a617adfc22044c3aa6cf4b2
-
Also process default display first, because it needs to be first for logic to work. Fixes multi display dreaming. Change-Id: Ic2f9f48f21099de43d1067100c84f1f266175e8a
-
Huge thanks to luka177 for investigation What happens here is simple: mContext has Theme.SystemUI set, for secondary displays, it uses createDisplayContext() which unsets Theme because it's not a UI context. If we manually set theme again, resources start resolving again and navigation bar keys are no longer transparent. Dhina17: Ported to 14 QPR2 Change-Id: Ib8c9212ac0facda8e0f4eeac2d4f839748178cc9
-
Dhina17: Ported to 14 Change-Id: I8e78ad6fa8b5361104af533e70a9c7e55a609611
-
* 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
-
- Apr 18, 2024
-
-
Mohammad Hasan Keramat J authored
Change-Id: If6e4a6d2c4d7b34b029ae500bb368e5173dd1fe9
-
- Apr 10, 2024
-
-
bypassEnabled will always evaluate to false now. Introduce bypassEnabledBiometric which is only used to tell the biometric service whether we can bypass lockscreen without swipe, dependant on Settings.Secure.FACE_UNLOCK_DISMISSES_KEYGUARD. This enables full lockscreen layout when "Skip lockscreen" setting is enabled, while also fixing status bar glitches. Change-Id: Ibdbf16df18543382219a75ce1aaf4e25f3fb4ddb Signed-off-by:
Adithya R <gh0strider.2k18.reborn@gmail.com> Signed-off-by:
Mohammad Hasan Keramat J <ikeramat@protonmail.com>
-
- Apr 09, 2024
-
-
Dhina17 authored
Change-Id: I9538d06bb7294d2f1c6fa2906ceb1cbc961e11f4
-
...after using actions such as "delete" or "share". Post / Recieve the notification ID with the intent for that. Also count grouped notifications to decide when to dismiss the group summary and only close QS after all notifications are dismissed. Change-Id: I1023367412b2b737b1cf3e9935b1d268059a2a3d
-
This reverts commit 6fcdb6bf. Change-Id: I125d2aff9b406341a533cbfe80686ee473dd3e88
-
-
Change-Id: I98a7b649100fdd3fc791c1031b825c96374da664
-
Chose the profiles that best fit the ones we have in H.264 by spec Change-Id: I153858bee5b3cce1e4cac4f86f44586a272de6ab
-
Change-Id: Ia487395c733ba609f89d84fdf934801174a40505
-
Unlimited time-wise. Only limit file size to 15GiB Change-Id: Ia16045dde478f65d1bee4a5167684c403f018906
-
Hack our way around that weird formula Just devide scaled bitrate by 3 for low quality Change-Id: I7669769ca3104b3566ed38f549af384f83d92d81
-
It's very annoying setting em back for each recording Save preferences on start, load back when dialog opens Change-Id: Ic8318cdb72a64da8eeb7d0966d45314d450d2d39
-
Change-Id: Iaaece0037160df9f659a1db65a7020510dbed0b0 Signed-off-by:Pranav Vashi <neobuddy89@gmail.com>
-
We could want to stop the recording without expanding the notification panel and show sensitive info. Long pressing on the red dot moves it to the opposite side, in case the user wants not to cover specific elements on the screen. Add also a low quality option that still gives a good recording reducing a lot the final file size (useful when sharing the screenrecord on data connections). old commits ref: https://github.com/ezio84/abc_frameworks_base/commit/6092d9ca8b0949d64c1b87d6cd53d66daf002e14 https://github.com/ezio84/abc_frameworks_base/commit/b50c7caf8b46c731093b11f5647028a23346f937 https://github.com/ezio84/abc_frameworks_base/commit/91c00e8fb70cb17b8658678bf476452f96cd44d1 Change-Id: If413241c3fa533650690cf3b7df5c05fb2f8c8ed
-
Nevertheless we have an option to limit the recording by frame rate, but we still can't limit it by resolution. It's not particularly needed for the devices of today which are enough powerful and can encode/play any profile level, but there are still many old devices for which the profile level can make a big difference. Traditionally the device declares the high quality multimedia profiles for video encoding (editing, recording video via camera ecc.), but these profiles are also used for screen recording. And here comes the pitfall for weak devices: screen recording is a video encoding process + highload user tasks on foreground and background, all in total is too much for an old device. The recorded video is "laggy", because the frames are simply skipped to the detriment of system smoothness. That's why some devices will need to limit AVC codec profile level for screen recorder only, as it doesn't make sense to do it globally, because it will also affect camera and video editing. Test: record the screen using the closest profile level to the display capabilities (resolution@frame rate). Check if video max. resolution and frame rate match the selected profile level constraints [1]. In case the profile level is the right one, the quality and fluidity of the video won't be in any way different from what you normally see on your display and will be playable anywhere, including the device that recorded it. [1] https://en.wikipedia.org/wiki/Advanced_Video_Coding#Levels [neobuddy89: Added default config to 4.2 and simplified] Change-Id: I918ee8f95124a34bda80feb57494b49ed449bf7b
-
