From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 1252D85CA3 for ; Tue, 21 Dec 2021 10:36:49 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 05C59275E3 for ; Tue, 21 Dec 2021 10:36:49 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3FC56275D8 for ; Tue, 21 Dec 2021 10:36:48 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 11AC8453E0 for ; Tue, 21 Dec 2021 10:36:48 +0100 (CET) Message-ID: <3443637a-4705-59b9-ed79-8c6c19d3bf8b@proxmox.com> Date: Tue, 21 Dec 2021 10:36:46 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Thunderbird/96.0 Content-Language: en-GB To: Aaron Lauterer , Proxmox VE development discussion References: <20211220153839.537253-1-a.lauterer@proxmox.com> <3f42d312-9021-5d83-6e8b-92c07dcb10d8@proxmox.com> From: Thomas Lamprecht In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 1.067 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -2.012 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [android.com] Subject: Re: [pve-devel] [PATCH futter_frontend 1/2] fix android splash screen logo X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2021 09:36:49 -0000 On 21/12/2021 10:27, Aaron Lauterer wrote: > On 12/20/21 20:37, Thomas Lamprecht wrote: >> On 20/12/2021 16:38, Aaron Lauterer wrote: >>> The new splash screen that came with Android 12 has stricter rules >>> regarding the size and form of the logo in the splash screen [0]. >> >> oh, do you have an actual reference to the strict rules you found, as [0] >> >> As I read [0] quite closely and basically all mentions regarding the >> drawable are IMO the opposite of strict, e.g.: >> >>> The app icon (1) should be a vector drawable, and it can be static or animated. >> >> And all other references are similarly vague and imply multiple times that >> any drawable should work. > > I think the following line below figure 2 is the important one: >     "As with adaptive icons, one-third of the foreground is masked (3)." > > Hinting at the #3 in the figure, which is the area outside the circle. Taking a closer look at the current splash screen, one will see that the drawable is masked in a circular shape. Depending on how it is scaling, the circular mask will be easier or harder to spot. ack, thanks for clarifying this to me. > >> >>> >>> We do need to have a drawable that is a square with the logo / icon in >>> the center. That means the current approach with the png image resulted >>> in it being scaled to the full width and the circular mask cut if off. >> >> hmm, the bitmap used sets `android:gravity` to `center` though, which is >> documented as: >> >>> Place the object in the center of its container in both the vertical and >>> horizontal axis, not changing its size. >> >> -- https://developer.android.com/guide/topics/resources/drawable-resource#XmlBitmap > > That probably explains why it did look quite different on your phone than on mine regarding how large and cutoff it appeared, depending on how they are set up regarding the px to dp (device independent pixel) conversion. > yeah, could make sense, anyhow if the vector graphic works everywhere I'm glad to switch over to that one.