An average person makes ~5 calls per day, resulting to a call log going back only  about 3-4 months. This is simply too low in my opinion. There is no harm to keeping an unlimited call log, just like we have an unlimited SMS log.

Change-Id: If8d19cfc47cf1ee0141bc35caebeeb8a476d0bd0

Change-Id: I15c3500f069f2bee40b7272f3eaa65cb320de50a
Signed-off-by: cjh1249131356 <cjh1249131356@gmail.com>

In android U, the timeout was increased. Backporting this change to this branch to allow tests to pass for partner devices.

Bug: 281653513

Test: Partner device (b/281653513#comment29)
Google: 2617830
Change-Id: I0859bdd7005638e16b6d265f33132d17b47b7d0a

Bug: 337174893
Test: manual, connect to paired but just factory reseted headset
Flag: EXEMPT, xml file change
Change-Id: I3ff5698f896b7b8caee02bf2d5f7b398c6fad418

While this offers minimal savings, there's no real reason to opt out of
optimization (the default for app targets).

Test: m + check APK diff
Bug: 203241149
Google: 3110298
Change-Id: Ib1bba31a95afa87f37aedb0251796bdb31ab65c0

Bug: 308095054
Change-Id: If7f34f23f2df0de1a63c9cfe4770a291cebe8692
Flag: EXEMPT Minor timeout change

Test: OEM monkey test
Bug: 341658103
Change-Id: Idfc3db1c0ea3be536cad82bf98fab6d668d26a36

 * TYPE_KEYGUARD_DIALOG was below volume and navbar and would
   have caused cause issues when HBM was enabled

 * BiometricPrompt uses different layer which again is below
   navbar and causes bright volume and navbar

Change-Id: Ia37930ffd7a28fc8785f26ada3b69a02df0d4891

* It fixes DT2W enables & disables microphone permissions everytime when unlocking device using double tap.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Improves the UX while dragging the brightness slider.

[someone5678]: Adapt to current brightness slider changes

[neobuddy89]: Add null check

Change-Id: I79d9d8fd1133a9e166821ff8f7135ccb761edd58
Signed-off-by: Vaisakh Murali <mvaisakh@statixos.com>
Signed-off-by: someone5678 <nemui3353@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Respectively
Could save some taps for some users

Change-Id: I1c3a2e9b37d7ea07d8d1ba2bee26998bd3c8ac02
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Q: don't skip the new Bubbles (the circular popping up notifications
like the Dialer one when a call is active and you press the home button)
Reference: https://github.com/ezio84/abc_frameworks_base/commit/c3d6f7d386286a4e55a3e0644782827705db7168#diff-c38ee79f64d8dc57e7757863d741be46



Allow to show heads up only for dialer and messaging
app when they are not in foreground

neobuddy89:
* Added clock app too in whitelist.
* Adapted and squashed for A12.

Stallix:
* Adapted logging for A13.

Squashed:

    From: Pranav Vashi <neobuddy89@gmail.com>
    Date: Wed, 14 Dec 2022 08:22:21 +0530
    Subject: Slightly optimize less boring apps check for heads up

    * We do not want to keep checking packages everytime
      when this option is disabled or device is dozing.

    From: minaripenguin <minaripenguin@users.noreply.github.com>
    Date: Thu, 9 Mar 2023 12:06:30 +0800
    Subject: Less boring heads up: Don't skip heads up for most messaging apps

    From: Rushab Shah <rushabshah32@gmail.com>
    Date: Sun, 30 Apr 2023 00:22:42 +0530
    Subject: LessBoring: fixup LessBoring preventing bubbles

    From: minaripenguin <minaripenguin@users.noreply.github.com>
    Date: Tue, 26 Sep 2023 11:40:59 +0800
    Subject: SystemUI: Less boring headsup enhancements and fixes

    * cleanup methods and use AOSP's headsup observer

    test: call/messaging while toggling reticker/less boring headsup feature on/off

    attempt to fix: whitelisted notification apps skipped when using reticker/less boring headsup feature

Change-Id: I26ecd6ca36db09ee662210b386c031f90016ddc4
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

* changed on chatgpt app v1.2024.170+

Change-Id: I2817c6134bebd95268ca5ad39f2f18a27a8ca2fc
Signed-off-by: aswin7469 <aswinas@pixysos.com>

* 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 <minaripenguin@users.noreply.github.com>

* Wtf google?

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

* Now it matches "Done" button with that in Internet Dialog.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Description:
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: Process: com.android.systemui, PID: 10252
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: java.lang.IllegalStateException: Existing input consumer found with name: pip_input_consumer, display: 0
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: 	at android.os.Parcel.createExceptionOrNull(Parcel.java:2382)
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: 	at android.os.Parcel.createException(Parcel.java:2358)
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: 	at android.os.Parcel.readException(Parcel.java:2341)
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: 	at android.os.Parcel.readException(Parcel.java:2283)
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: 	at android.view.IWindowManager$Stub$Proxy.createInputConsumer(IWindowManager.java:5175)
04-10 13:50:21.197 1010145 10252 10252 E AndroidRuntime: 	at com.android.systemui.shared.system.InputConsumerController.registerInputConsumer(InputConsumerController.java:165)

Crash is occurring. If two users are present. Open any app in PIP. Then keep on moving it to PIP to non-PIP and non-PIP to PIP.
Eventually crash will happen because onActivity Pinned is getting called 2 times. pip_input_consumer that is already present, is getting created again.

Fix: Do nothing if user is different.

Change-Id: Ie49d7ed525b5c5583c96f54ed3fb0901ff76c6ec
Signed-off-by: pioush garg <pioushkumar1992@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

When a transport returns TRANSPORT_ERROR, cancel the backup right away
instead of waiting five minutes for a timeout before canceling.

Co-authored-by: Torsten Grote <t@grobox.de>
Change-Id: Ie2c305d89e66176f14d99d92b04f1390d9d9b1ed

Current locking mechanism in LmkdConnection which synchronizes socket
reads and writes with socket destruction and replacement can result in
a deadlock because both read and write synchronize on the same lock.
That creates a possibility of a deadlock if the data pipe between AMS
and LMKD is full. AMS sends data to LMKD and blocks until LMKD reads
older data from the pipe to free some space for the new data. LMKD
is busy sending data to AMS and also blocks until AMS read some data
from its end of the pipe. AMS is trying to read the data from LMKD but
blocks because send operation is holding the lock they both are
synchronized on.
Change this synchonization mechanism to use two separate locks, one for
reads and one for writes so that concurrent send and receive can succeed
while preventing concurrent modifications to the socket itself.

Bug: 349702703
Google: 3157258
Change-Id: Icd4b9a2862bca8f18e213cf216d019231e0dbd2f

The odm partition is an extension of the vendor partition,
so the targetSdkVersion of an overlay package pre-built in
odm partition should not below the SDK level required by
vendor overlays, other than required by system overlays.

Bug: 350902133
Test: presubmit
Google: 3159156
Change-Id: I8ea561c80f66f5534d7a2f1ccf52c79e1edb0ffd

If the cellular network is in service, and the data network name is not
available for some reason, rather than falling back to the default
network name of "No service", use the carrier name.

Issue: calyxos#2256
Change-Id: Ibf02f67b70cfc5d4804e9d6a3f53a9d112811d1d

* Some prebuilt camera apps try caching tag before setting value.
  When tag is not found, it crashes the app.

Log:

time: 1719773472448
msg: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
stacktrace: io.reactivex.exceptions.OnErrorNotImplementedException: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
	at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Unknown Source:2)
	at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Unknown Source:2)
	at io.reactivex.internal.observers.LambdaObserver.onError(Unknown Source:13)
	at io.reactivex.internal.observers.LambdaObserver.onNext(Unknown Source:25)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(Unknown Source:47)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(Unknown Source:8)
	at io.reactivex.internal.schedulers.ScheduledRunnable.run(Unknown Source:13)
	at io.reactivex.internal.schedulers.ScheduledRunnable.call(Unknown Source:0)
	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at com.xiaomi.camera.rx.CameraSchedulers$2.run(Unknown Source:16)
	at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
	at com.android.camera2.vendortag.VendorTagHelper.handleException(Unknown Source:35)
	at com.android.camera2.vendortag.VendorTagHelper.trySetValue(Unknown Source:11)
	at com.android.camera2.vendortag.VendorTagHelper.setValue(Unknown Source:2)
	at com.android.camera2.compat.MiCameraCompatQcomImpl.applySaturation(Unknown Source:23)
	at com.android.camera2.compat.MiCameraCompat.applySaturation(Unknown Source:2)
	at com.android.camera2.CaptureRequestBuilder.applySaturation(Unknown Source:10)
	at com.android.camera2.CameraConfigManager.lambda$setSaturation$25(Unknown Source:6)
	at com.android.camera2.CameraConfigManager.OooOo(Unknown Source:0)
	at OooO0OO.OooO0O0.OooO0O0.o0000.accept(Unknown Source:4)
	at java.util.Optional.ifPresent(Optional.java:178)
	at com.android.camera2.CameraConfigManager.setSaturation(Unknown Source:39)
	at com.android.camera.module.Camera2Module.updateSaturation(Unknown Source:49)
	at com.android.camera.module.Camera2Module.consumePreference(Unknown Source:175)
	at com.android.camera.features.mode.capture.CaptureModule.consumePreference(Unknown Source:0)
	at com.android.camera.module.BaseModule$ModuleConsumer.accept(Unknown Source:125)
	at com.android.camera.module.BaseModule$ModuleConsumer.accept(Unknown Source:2)
	at io.reactivex.internal.observers.LambdaObserver.onNext(Unknown Source:8)
	... 10 more
Caused by: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
	at android.hardware.camera2.impl.CameraMetadataNative.nativeGetTagFromKeyLocal(Native Method)
	at android.hardware.camera2.impl.CameraMetadataNative.setBase(CameraMetadataNative.java:1919)
	at android.hardware.camera2.impl.CameraMetadataNative.set(CameraMetadataNative.java:524)
	at android.hardware.camera2.impl.CameraMetadataNative.set(CameraMetadataNative.java:528)
	at android.hardware.camera2.CaptureRequest$Builder.set(CaptureRequest.java:882)
	at com.android.camera2.vendortag.VendorTagHelper.trySetValue(Unknown Source:6)
	... 25 more

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

launcher3 permission

 * Fixes

------ beginning of crash 02-07 13:32:34.640 1020 1020 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main 02-07 13:32:34.640 1020 1020 E AndroidRuntime: java.lang.IllegalStateException:
Signature|privileged permissions not in privapp-permissions allowlist:
{com.android.launcher3 (/system_ext/priv-app/Launcher3QuickStep):
android.permission.REGISTER_STATS_PULL_ATOM}

Change-Id: I6f3f370f4ec4e1fe5586e3e54c78f777899b5459
Signed-off-by: karthik1896 <karthik1896@outlook.com>
Signed-off-by: Dmitrii <bankersenator@gmail.com>
Signed-off-by: Sipun Ku Mahanta <sipunkumar85@gmail.com>

* Kind of an oddly specific use case here but to reproduce:
  - Enable CRT Screen Off Animation
  - Start playing a video from Netflix
  - Turn off screen using  power key, you should see the crash then

Co-authored by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: Matt Filetto <matt.filetto@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Fade (default), CRT, and Scale

Credit and respect to xplodwild for paving the way
back in the KitKat days!

History of the ElectronBeam class can be found here
https://github.com/DirtyUnicorns/android_frameworks_base/commits/kitkat/services/java/com/android/server/power/ElectronBeam.java



*** Changes for Android 10 by bigrushdog ***
Various updates needed for Surface related API in the ElectronBeam animation class

[AgentFabulous | POSP]
- Rebase and rewrite ElectronBeam class on top of ColorFade
- Add usage of class-common Transaction instance
- Add support for respecting wide-color and protected-content
- Fixup for new API

neobuddy89:
Updated for Android 14.

Change-Id: I58d269d44c901a8c0471807e3cf05c2054205d28
Co-Authored-By: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Signed-off-by: minaripenguin <minaripenguin@users.noreply.github.com>

* Also apply it to NotificationAttentionHelper

And don't launch camera when camera is in use.

Change-Id: I55a96d6c777104155d879251400956713cb119b5
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

[someone5678] Unify style with Brightness slider haptic

Change-Id: Ieb2dc23eb1e8237b230591066901acbb19c94fd6
Signed-off-by: someone5678 <nemui3353@gmail.com>

java.lang.NullPointerException: Attempt to invoke interface method 'void com.android.systemui.shade.ShadeViewController.resetViews(boolean)' on a null object reference
	at com.android.systemui.statusbar.phone.StatusBarKeyguardViewManager.reset(StatusBarKeyguardViewManager.java:860)
	at com.android.systemui.statusbar.phone.StatusBarKeyguardViewManager.show(StatusBarKeyguardViewManager.java:662)
	at com.android.systemui.keyguard.KeyguardViewMediator.handleShow(KeyguardViewMediator.java:2780)
	at com.android.systemui.keyguard.KeyguardViewMediator.-$$Nest$mhandleShow(KeyguardViewMediator.java:0)
	at com.android.systemui.keyguard.KeyguardViewMediator$12.handleMessage(KeyguardViewMediator.java:2498)
	at android.os.Handler.dispatchMessage(Handler.java:107)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.app.ActivityThread.main(ActivityThread.java:8527)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:555)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)

Signed-off-by: minaripenguin <minaripenguin@users.noreply.github.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Fixes: https://github.com/crdroidandroid/issue_tracker/issues/371


Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

IPv6-only networks that support 464XLAT use CLAT to access IPv4
addresses, but the traffic that occurs over the CLAT interface is
tracked separately; it is not reflected at all in the stats of the
underlying interface, so prior to this change, IPv4 traffic on
applicable IPv6-only networks is not reflected in the network traffic
monitor, either.

While there is no exposed API to retrieve stacked interfaces, we can
still try to grab the stats for a CLAT interface (which always starts
with "v4-"), just in case it exists, and if so, add in those stats.

Test: Manual: While connected to an IPv6-only network, such as a
T-Mobile cellular data connection, attempt to load https://1.1.1.1


in a browser while the network traffic monitor is enabled. Reload
the page / choose different languages to cause traffic to occur,
and it should be reflected in the traffic monitor.

Issue: calyxos#792
Co-authored-by: Oliver Scott <olivercscott@gmail.com>
Change-Id: Ida768ebe73a47bb06da53aeb7b5c6882f0090e75
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

* On theme change, status bar icons are re-added.
  This re-called registerNetworkCallback everytime leading to
  "too many requests" and systemui crash.
* Prevent it by register callback when attached to window.
  Also, unregister callback when detaching.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>