Whilst we didn't need to modify min/target SDK levels like previous versions of the app,
unfortunately, HDR10 video recording is still broken for us so we must disable it
Change-Id: I8d5b8d260fb288aedfa0941a79435ad86543b2da
• Prior to this, the icons were not aligned to the camera cutout.
• Seems like motorola had set status_bar_padding_top_portrait but
we don't have that. However, status_bar_padding_top is configurable
so use the same value there.
Change-Id: Ife06be11a66098c8e84a94b1f11efd2c2280b9f3
* All necessary SystemUI values are on res/values.
* Landscape values is on Frameworks/res/values folder.
Change-Id: I718363ae388af49180c5321bdae1667be54016b5
Signed-off-by: Fraaxius <franthekillaz@gmail.com>
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
Unfortunately, QPR2 seems to cause this app to randomly crash when checking
for aux cameras and I don't currently see a fix, so let's drop it for now
until a solution can be found
Change-Id: Ife2b51aac6c1f77b59cce498e29cd105a5564658
These use the front camera frequently but aren't critical to
functionality, so we don't need to disrupt 5G services.
Change-Id: I0d23c3bfec936ddefcabb93e6a579a5eb11b3574
We don't need to disable 5G entirely during front camera usage, because
apparently only N78 band in SA 5G (Jio) is affected. Lower bands, such
as N28, does not break front camera so let's just disable the offending
band via RIL OEM commands when front camera is active.
Reversed the band editing mechanism from stock qcom-moto-telephony-ext.
Inspired by 70eebccf64
Change-Id: I6ccb247a5d1b1521e1828304f5570269d9e3f221
On some network(s) (confirmed on Jio), the usage of 5G kills front
camera and crashes the camera app. Logs reveal hardware or firmware
issues related to interference or bandwidth, which is out of my
expertise:
[ 63.301897] CAM_ERR: CAM-ISP: cam_ife_csid_irq: 5016 CSID:2 RX_ERROR_LANE0_FIFO_OVERFLOW: Skew/Less Data on lanes/ Slow csid clock:300000000Hz
Until this can be actually fixed (if ever), a temporary workaround.
Inspired by a860cc8189
Change-Id: Ifefb36cf113a5f25feda771ea7729418553e74ed
Unfortunately it seems dubai's MotCamera4 from Android 13 is a very early version and
seems to hate Android 14, so let's switch to eqs's A12 version as it contains the proper
asset configurations for dubai where-as eqs 13 and up does not
Change-Id: I7d134648aac68bf7bb666cd36b0796899e945cfc
This device uses an NXP chip
and supports Mifare tags. This adds the xml file
to make NXP's apps work properly.
Change-Id: I9f2f04d3c5c211185bf2ab0d5a797070c49d4b98
The default thermal-engine-dubai.conf is way too agressive with throttling that the performance
is way too low for any users trying to play 3D games on a Snapdragon 778G+ runs slower than
a SD 778G, so let's swap to the dubai-game-perf config as when we compared the configs it
allows for a better performance to thermal balance. We also checked dubai-perf but that one
was more of a "let's get the highest scores in a benchmark and turn the device into a
handwarmer" kind of thermal config.
Change-Id: Id5c991a198ef6be61009a9785b5e8604aa1fdc91
