Fix the BT SampleRate from '16000' to 'KHZ_16'
in "mmap-playback bt-sco-wb".
Fix the path name from "mmap-buffer-playback hdmi"
to "mmap-playback hdmi".
CRs-Fixed: 2278484
Change-Id: I44ae1d02cb214555967e3f1f42b0cd022e5c4bfe
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
Allocate dedicated pcm node for in call recording, this can
avoid conflicting with generic audio recording for concurrent
recording scenarios
Change-Id: If81aa994409161c526fbbcb95dbcb0397fa9e36b
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
* this forces android to display "charging rapidly" whenever our
proprietary 33w charger is connected, based on the value of
this node (0/1)
Change-Id: I2a36ccb62621672e480e4b25a335410044fbb372
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
* fixes crashes and absurdly high CPU usage while using dolby
Co-authored-by: Woomymy <woomy@woomy.be>
Change-Id: Ib72b775dae677f3085d0b0e2afcbb709d8690063
Signed-off-by: basamaryan <basam.aryan@gmail.com>
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
In the before-times of June 2019, an intrepid AOSP reviewer named
"fbechet45@gmail.com" reported:
> typo error:
> line 311 : "volatage" should be written "voltage"
After a short series of hops, this bug landed in my todo list.
My first thought was, "Easy! I'll fix this on my internal git,
Lets go, in-and-out, 20 minute adventure." But, that would deny the
original reporter of seeing the solution for some large number of
months.
So, I decide "I will fix this in AOSP. But, oh no, Coral has the
same copy-paste error! Let me just wait until October 2019 when
Coral goes public, then I'll fix those two at the same time."
(Little did I know this would continue to get copied and pasted, and
now there are 20+ instances of this on our internal repository.)
Fast forward to 2020: The pandemic gripped our nation, and I was
busy baking bread and posting pictures of it on Facebook. I have
some great recipes I can share. Let me know if you need some of my
artisinal sourdough starter.
Now, in 2021, after multiple automated-and-human reminders, this
has become my #1 priority issue to solve. I still have the "can't
fix all the errors" on AOSP problem, but if I don't fix crosshatch
now, it will be too late to land it into the 2021 dessert release,
which may be the last supported release for crosshatch. Oh no!
I am determined not to mark this bug as "Won't Fix / Obsolete"
and yet not so determined to act on it quickly. So, I will fix
crosshatch internally, and then fix the rest of the projects on our
internal master branch.
I hope this patch finds you well and remember to take care of
yourself in these tough times.
With regards,
Chris
Bug: 132925372
Bug: 135906639
Bug: 77804134
Change-Id: I2d088bcbdfbc758eed5054f0413ab02aa5e57e4c
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
- from device/google/sunfish@441168f
- correct battery capacity and cpufreq for sweet
- update Radio related values, gps.on value & wifi.batchedscan values
- based on stock power profile
- values taken from resource-overlay
Signed-off-by: Pulkit077 <pulkitagarwal2k1@gmail.com>
Change-Id: Ie393df152ead4ea50327315c57ce1d3a8b540da7
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
If the device only have 60 and 120 Hz in the config group, 60 Hz won't be
used when watching a 24 fps video and instead 120 Hz will be used because
it is perfectly divisible by 24.
This is a publicly documented AOSP behavior [1], but it simply does not
make any practical sense and trades off significant amount of power for a
very-hard-to-notice jitter-free experience.
Set debug.sf.frame_rate_multiple_threshold to 60 by default to limit this
behavior to 60 or lower fps.
[1] https://source.android.com/devices/graphics/multiple-refresh-rate
Change-Id: I66353abc46ad16e63b2c9188794469ad71f2192e
Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
This not only saves a lot of build time when building with
TARGET_USERIMAGES_SPARSE_EXT_DISABLED and/or
TARGET_USERIMAGES_SPARSE_F2FS_DISABLED which is required
on A14, but also removes the need for the build system to
temporarily create a 40+GB userdata image.
Which means that less free space is required to start the
build.
Change-Id: Ibf48e7cdf566a4653e85352a79170b354d917234
As of 14 QPR2 this is broken, let's remove it instead of updating it
every 3 months. breakfast is the way to go.
Change-Id: I097bd54b894d9a49c7ce8b1ab6f343349e268fd8
