<feed xmlns='http://www.w3.org/2005/Atom'>
<title>frameworks_base, branch replicant-10</title>
<subtitle>Fork of frameworks/base
</subtitle>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/'/>
<entry>
<title>Allow HW bitmaps with software rendering</title>
<updated>2020-06-25T11:55:01+00:00</updated>
<author>
<name>Joonas Kylmälä</name>
<email>joonas.kylmala@iki.fi</email>
</author>
<published>2019-09-01T17:30:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=10f48c0f9ed6c9c40891c879fe41b16d9e3db811'/>
<id>10f48c0f9ed6c9c40891c879fe41b16d9e3db811</id>
<content type='text'>
Fixes "E AndroidRuntime: java.lang.IllegalArgumentException: Software
rendering doesn't support hardware bitmaps"

Signed-off-by: Joonas Kylmälä &lt;joonas.kylmala@iki.fi&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fixes "E AndroidRuntime: java.lang.IllegalArgumentException: Software
rendering doesn't support hardware bitmaps"

Signed-off-by: Joonas Kylmälä &lt;joonas.kylmala@iki.fi&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: QS Details: Fix layout issues</title>
<updated>2020-06-23T14:43:57+00:00</updated>
<author>
<name>Michael W</name>
<email>baddaemon87@gmail.com</email>
</author>
<published>2020-06-20T14:05:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=d6c4b2398721e6f77dd3c1ffcd28e755b60596c8'/>
<id>d6c4b2398721e6f77dd3c1ffcd28e755b60596c8</id>
<content type='text'>
* Remove bottom padding:
  * It shifts the content up unnecessarily
  * It leaves a small white line at the bottom
* Introduce a new background color for the switch bar: derived from
  textColorPrimary because that is basically the exact opposite of the
  background color so it allows us to get a slightly brighter overlay
* Also change the qs detail's background: use the same color as for the
  rest of the qs backgrounds - now it doesn't look different from the rest
  anymore (was a slightly darker shade of white on light theme and a
  brighter grey on dark. This was more noticeable on a dark theme and is
  basically also the reason that we noticed the wrong padding
* For zen tile (dnd), remove all background color references and apply
  qs_background_primary for the whole panel at once. Applying the
  color manually is required because the panel is inflated separately
  and not using the color that is assigned to the original content.
  Removing all separate references allows to define and change the color
  in one place
* In order to make the buttons also look good on dark background,
  assign a color (similar to the one for the switchbar, see above)
  manually
* Also remove the min height and add top/bottom paddings so the buttons
  are not as huge as currently
* Remove start and end padding from QS detail header xml, because they are
  a) a mixture of left and end, which should really be start/end or
     left/right
  b) Not used anymore, as QSDetail.java applies them in
     onApplyWindowInsets programmatically

The alpha values of 5% and 8% for our newly defined colors were determined
by trying various values until it looked good on all themes

Test: Open every qs tile on both light and dark themes and see if
 they look proper

Change-Id: I5be8bf97582e877bdb1af1f3aedc88c00d134c16
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Remove bottom padding:
  * It shifts the content up unnecessarily
  * It leaves a small white line at the bottom
* Introduce a new background color for the switch bar: derived from
  textColorPrimary because that is basically the exact opposite of the
  background color so it allows us to get a slightly brighter overlay
* Also change the qs detail's background: use the same color as for the
  rest of the qs backgrounds - now it doesn't look different from the rest
  anymore (was a slightly darker shade of white on light theme and a
  brighter grey on dark. This was more noticeable on a dark theme and is
  basically also the reason that we noticed the wrong padding
* For zen tile (dnd), remove all background color references and apply
  qs_background_primary for the whole panel at once. Applying the
  color manually is required because the panel is inflated separately
  and not using the color that is assigned to the original content.
  Removing all separate references allows to define and change the color
  in one place
* In order to make the buttons also look good on dark background,
  assign a color (similar to the one for the switchbar, see above)
  manually
* Also remove the min height and add top/bottom paddings so the buttons
  are not as huge as currently
* Remove start and end padding from QS detail header xml, because they are
  a) a mixture of left and end, which should really be start/end or
     left/right
  b) Not used anymore, as QSDetail.java applies them in
     onApplyWindowInsets programmatically

The alpha values of 5% and 8% for our newly defined colors were determined
by trying various values until it looked good on all themes

Test: Open every qs tile on both light and dark themes and see if
 they look proper

Change-Id: I5be8bf97582e877bdb1af1f3aedc88c00d134c16
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: Fix issue with Bluetooth tile</title>
<updated>2020-06-23T10:04:39+00:00</updated>
<author>
<name>Michael W</name>
<email>baddaemon87@gmail.com</email>
</author>
<published>2020-06-21T15:22:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=027d8103d43b4fde345267541103cff2266a2471'/>
<id>027d8103d43b4fde345267541103cff2266a2471</id>
<content type='text'>
* Currently: Pair a device
* Open BT tile details ("details"), device is shown
* Disable bt via the switchbar, close the details via the "done" button
* Reopen the details -&gt; the list is empty, neither "empty" text nor
  actual devices are shown

After this patch: Reopening the details turns on bt which in turn makes
 devices visible again

Change-Id: I1a0a5ebdcaca50bc821b0180f2109d00091eaa1c
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Currently: Pair a device
* Open BT tile details ("details"), device is shown
* Disable bt via the switchbar, close the details via the "done" button
* Reopen the details -&gt; the list is empty, neither "empty" text nor
  actual devices are shown

After this patch: Reopening the details turns on bt which in turn makes
 devices visible again

Change-Id: I1a0a5ebdcaca50bc821b0180f2109d00091eaa1c
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: Fix QS Detail Header</title>
<updated>2020-06-20T14:03:02+00:00</updated>
<author>
<name>Michael W</name>
<email>baddaemon87@gmail.com</email>
</author>
<published>2020-06-16T10:13:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=24656a53072e0a723ac27ef5f89ef3b9885deaad'/>
<id>24656a53072e0a723ac27ef5f89ef3b9885deaad</id>
<content type='text'>
* Commit eff2c740e55668a4fdf427e64a8970a751830991 introduced some padding
  in case of an existing corner cutout (e.g. a camera in the corner of a
  display), so applies the size of the cutout as padding left/right
* it tries to keep top/bottom padding as-is by calling
  get[Top|Bottom]Padding while re-applying start and end paddings to
  restore the case with corner padding (e.g. after testing from developer
  settings) but fails to do so by calling it on the current view instead
  of the one of interest
* Fix that by getting the actual top/bottom paddings from the relevant
  header view
* Also fix the right padding - it should be qs_panel_padding according
  to the layout file

Test: QS Detail looks like before r37 merge
Test: Activate corner cutout and see if the inset applies properly,
  then deactivate it and see if the original layout restores
Change-Id: I5ba57deff1784fc4ea16649256965ad42dd78239
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Commit eff2c740e55668a4fdf427e64a8970a751830991 introduced some padding
  in case of an existing corner cutout (e.g. a camera in the corner of a
  display), so applies the size of the cutout as padding left/right
* it tries to keep top/bottom padding as-is by calling
  get[Top|Bottom]Padding while re-applying start and end paddings to
  restore the case with corner padding (e.g. after testing from developer
  settings) but fails to do so by calling it on the current view instead
  of the one of interest
* Fix that by getting the actual top/bottom paddings from the relevant
  header view
* Also fix the right padding - it should be qs_panel_padding according
  to the layout file

Test: QS Detail looks like before r37 merge
Test: Activate corner cutout and see if the inset applies properly,
  then deactivate it and see if the original layout restores
Change-Id: I5ba57deff1784fc4ea16649256965ad42dd78239
</pre>
</div>
</content>
</entry>
<entry>
<title>Add a LineageOS clock</title>
<updated>2020-06-16T22:53:44+00:00</updated>
<author>
<name>gnumdk</name>
<email>gnumdk@gmail.com</email>
</author>
<published>2020-06-03T14:07:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=257a6821cbc2802265b20c3631fdae5505cd983a'/>
<id>257a6821cbc2802265b20c3631fdae5505cd983a</id>
<content type='text'>
    Here a custom clock for ClockPlugin showing LineageOS logo
    https://i.ibb.co/4N8gZrT/clock.png

Change-Id: I7e29eba21357ab740dae20a738ef34c18f1a594e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
    Here a custom clock for ClockPlugin showing LineageOS logo
    https://i.ibb.co/4N8gZrT/clock.png

Change-Id: I7e29eba21357ab740dae20a738ef34c18f1a594e
</pre>
</div>
</content>
</entry>
<entry>
<title>AODTile: Rewrite AOD setting handling</title>
<updated>2020-06-10T21:30:25+00:00</updated>
<author>
<name>Bruno Martins</name>
<email>bgcngm@gmail.com</email>
</author>
<published>2020-06-09T20:47:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=f730abf925a48c48953eb7177af7f06cd7c76a09'/>
<id>f730abf925a48c48953eb7177af7f06cd7c76a09</id>
<content type='text'>
This fixes the tile status on clean installs, which was showing as
active despite AOD being disabled.

Change-Id: I148cfb34938165395bc52c830d1f2e374b5427df
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This fixes the tile status on clean installs, which was showing as
active despite AOD being disabled.

Change-Id: I148cfb34938165395bc52c830d1f2e374b5427df
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: set no hint overlay to highest priority</title>
<updated>2020-06-10T21:29:40+00:00</updated>
<author>
<name>Jesse Chan</name>
<email>jc@lineageos.org</email>
</author>
<published>2020-06-02T05:59:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=230e19d9f7719dd67e6b4e47be75ccedc23cada0'/>
<id>230e19d9f7719dd67e6b4e47be75ccedc23cada0</id>
<content type='text'>
As overlays are also used to apply navigation mode, it is needed to set
our customization overlay to highest priority to ensure it is applied.

Change-Id: I41ca4b7ea99fea9f62d2e8ece5114f682e8e7fe9
Signed-off-by: Jesse Chan &lt;jc@lineageos.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
As overlays are also used to apply navigation mode, it is needed to set
our customization overlay to highest priority to ensure it is applied.

Change-Id: I41ca4b7ea99fea9f62d2e8ece5114f682e8e7fe9
Signed-off-by: Jesse Chan &lt;jc@lineageos.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: Long press Caffeine for infinite duration</title>
<updated>2020-06-08T20:14:22+00:00</updated>
<author>
<name>chillger</name>
<email>alexander.loskutov@gmail.com</email>
</author>
<published>2020-05-22T11:16:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=ac2040adcbf3ae05058d204cd1001297e065034f'/>
<id>ac2040adcbf3ae05058d204cd1001297e065034f</id>
<content type='text'>
Change-Id: Ic49539dcda6d7d6b1dab362eb8ec168d2ec65b07
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: Ic49539dcda6d7d6b1dab362eb8ec168d2ec65b07
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: Resolve faulty keyguard clock logs outputs</title>
<updated>2020-06-08T15:25:10+00:00</updated>
<author>
<name>Adrian DC</name>
<email>radian.dc@gmail.com</email>
</author>
<published>2020-05-17T18:08:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=1e64ed2b6aa91080be86a2d85a2e206aab52b853'/>
<id>1e64ed2b6aa91080be86a2d85a2e206aab52b853</id>
<content type='text'>
 * Enforce Android logs outputs against special chars, example:
    "KeyguardClockSwitch: Updating clock: 1057"

Change-Id: I2642eb50276a2e3d99af696f25ddc1eafbfc3b4e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
 * Enforce Android logs outputs against special chars, example:
    "KeyguardClockSwitch: Updating clock: 1057"

Change-Id: I2642eb50276a2e3d99af696f25ddc1eafbfc3b4e
</pre>
</div>
</content>
</entry>
<entry>
<title>SystemUI: Adapt screenshot sound to ringer modes</title>
<updated>2020-06-08T15:23:21+00:00</updated>
<author>
<name>Ashwin R C</name>
<email>ashwin2001achu@gmail.com</email>
</author>
<published>2020-05-27T10:26:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/frameworks_base/commit/?id=aa9fbad20ad63940358f8461879bd34ec5d216f3'/>
<id>aa9fbad20ad63940358f8461879bd34ec5d216f3</id>
<content type='text'>
Change-Id: I381c351131241e45ddb6049706d6c302c2eee946
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: I381c351131241e45ddb6049706d6c302c2eee946
</pre>
</div>
</content>
</entry>
</feed>
