Skip to content

Conversation

@MarcaDian
Copy link

@MarcaDian MarcaDian commented Oct 1, 2025

Fix incorrect icon logo, #1124 and Splash screen is a broken in light mode from #1191 (comment)


Round/Adaptive icon

Before (xxhdpi) After (xxhdpi)
ic_launcher ic_launcher

Monochrome icon

Screenshot_2025-10-02-18-29-17-092_app.lawnchair-edit.jpg


Splash screen

Dark Light
Screenshot_2025-10-04-08-35-24-375_app.revanced.manager.debug_signed.jpg Screenshot_2025-10-04-08-35-53-276_app.revanced.manager.debug_signed.jpg

@MarcaDian
Copy link
Author

MarcaDian commented Oct 1, 2025

@Ushie
Copy link
Member

Ushie commented Oct 1, 2025

Which one is in our revanced-branding repository?

@LisoUseInAIKyrios
Copy link
Contributor

LisoUseInAIKyrios commented Oct 2, 2025

@Ushie both files are in the branding repo.

Somehow two slightly different designs exist there, and nobody has noticed until now.

We should make a decision, then delete/fix the incorrect icons in that repo.

@LisoUseInAIKyrios
Copy link
Contributor

LisoUseInAIKyrios commented Oct 2, 2025

It seems this file is the only file with the conflicting design (sharp edges and not rounded).

Since all the other branding image resources use rounded edges, I think was can say this the rounded design used by the 7 other files is the correct design.

So the solution is to use the rounded design here, and open a new issue in the branding repo so that incorrect file can be fixed/deleted?

@MarcaDian
Copy link
Author

MarcaDian commented Oct 2, 2025

The second logo (the sharp one) has been used as the icon in the manager for 2 years, although with incorrect proportions of the foreground area of the adaptive icon.

Because of this, we updated the icons in the custom branding patch for YouTube, since we thought this was the actual icon.

It’s very strange that there are 3 different icon designs in the ReVanced projects, and it seems that no one ever noticed this - but as soon as we fixed it, questions started to arise.

IMG_20251002_092210.jpg

@LisoUseInAIKyrios
Copy link
Contributor

LisoUseInAIKyrios commented Oct 2, 2025

It seems everytime the icons are touched there is some kind of controversy.

Well, do we stick with the "wrong" sharp icon here that's been used with Manager for the past 2 years? Or do we change to the rounded (and make another PR in Patches to change to that)?

Patches repo could add one or two additional preset icons for the custom branding patch. One preset with the color ring, and maybe another with an expanded ring that was available with the prior icon design that worked with odd launcher icon shapes. But that is unrelated to the question of which icon to use.

@LisoUseInAIKyrios
Copy link
Contributor

If we can't come to a decision then we should merge what is currently here, because it is the icon style Manager has already been using the past 2 years.

@Ushie
Copy link
Member

Ushie commented Oct 2, 2025

Use the rounded ones, an issue should be opened for the sharp one to be fixed

@MarcaDian MarcaDian changed the base branch from compose-dev to dev October 2, 2025 15:42
@oSumAtrIX
Copy link
Member

I don't understand whats going on here. What issue does the branding repo have? They are all svgs, I dont understand what you mean with sharp/not sharp.

The PR body shows the diamond scaled more than current. Please use the scaling thats also used in the logo from the branding repo.

@oSumAtrIX
Copy link
Member

@oSumAtrIX Look at these 2 icons and finally decide which one to use? rounded or sharp?

ReVanced/revanced-branding@main/assets/revanced-logo/revanced-logo.svg

ReVanced/revanced-branding@main/assets/revanced-logo/revanced-logo-shape.svg

image

I do not understand what you mean. The links you sent are two different things. The shape is ONLY the shape, the round one is the full logo with the ring.

You should use the shape in scenarios where the background is configured separately, in other words:

  1. Create an adaptive icon background
  2. Extract the shape from the FULL logo from the branding, make sure the scaling is kept
  3. Use the extracted shape in that scale as the adaptive icon foreground

I am not sure if android does additional scaling processing so you'll have to compare with the android spec. If they do not apply any additional scaling, the final logo should look exactly like the logo from the branding.

@LisoUseInAIKyrios
Copy link
Contributor

LisoUseInAIKyrios commented Oct 2, 2025

@oSumAtrIX look carefully at those two images. They are not the same. One has rounded corners, the other is "sharp" corners. Look at the bottom point of the inner small V. The two images are different.

#2762 (comment)

The non rounded icon image in the branding repo must be a mistake, because all other images are rounded. It should be fixed there, but also fixed here.

The logo here has no round circle background, since there isn't a cut shape for adaptive icons. The old manager icon did not use the correct scale and went against android guidelines. This PR fixes all of this for Manager.

@oSumAtrIX
Copy link
Member

I see the problem and I know why it happens.

Affinity Design handles roundness based on the canvas size. I think when I created the shape, I did those steps:

  1. Remove the background layer
  2. Scale the shape to fit the canvas

Step two scales the shape, but it does not scale the rounding value.
A simple fix is to scale down the canvas to the size of the shape. This way the shape fills the entire canvas but attributes like the roundness remain correct. I will fix this.

@oSumAtrIX
Copy link
Member

And yes, the full logo is the "correct" one. All variations are derrivates of it

@oSumAtrIX
Copy link
Member

Ok seems it was caused by https://github.com/ReVanced/revanced-branding/pull/10/files

@oSumAtrIX
Copy link
Member

Fixed now ReVanced/revanced-branding@41c7155

@MarcaDian MarcaDian marked this pull request as ready for review October 2, 2025 20:38
@MarcaDian
Copy link
Author

I think ic_launcher_round.png can be deleted, since it is not used anywhere, it just takes up space

@LisoUseInAIKyrios
Copy link
Contributor

LisoUseInAIKyrios commented Oct 2, 2025

They can still be used in some edge cases, so I think they should be kept Edit: Legacy round icon can be deleted.

The files are too small to make any difference.

@MarcaDian
Copy link
Author

It has an unusual size of 400 by 400, while xxxhdpi has a maximum of 192

@LisoUseInAIKyrios
Copy link
Contributor

LisoUseInAIKyrios commented Oct 2, 2025

400x400 looks like it's much larger than needed.

But the manifest is missing the android:roundIcon declaration.

If it's gone this long and nobody has noticed it's missing in any of the edge cases, then that image should be deleted because the file isn't doing anything without the manifest declaration.

@MarcaDian
Copy link
Author

Also fix Splash screen is a broken in light mode from #1191 (comment)

@MarcaDian
Copy link
Author

Default 30%

Dark Light
Screenshot_2025-10-04-08-35-24-375_app.revanced.manager.debug_signed.jpg Screenshot_2025-10-04-08-35-53-276_app.revanced.manager.debug_signed.jpg

@MarcaDian
Copy link
Author

MarcaDian commented Oct 4, 2025

I also tried 40%

Dark Light
Screenshot_2025-10-04-08-50-50-199_app.revanced.manager.debug_signed.jpg Screenshot_2025-10-04-08-51-23-588_app.revanced.manager.debug_signed.jpg

Leaving 30%?

@Ushie
Copy link
Member

Ushie commented Oct 5, 2025

30% looks perfect

@oSumAtrIX
Copy link
Member

Isn't there an android standard for the size

@MarcaDian
Copy link
Author

MarcaDian commented Oct 5, 2025

There’s no strict standard size defined for splash screens.
The system uses the same scaling as the launcher adaptive icon - the foreground layer is 72dp within a 108dp area (66% scale).
Everything else is adjusted automatically depending on device density.

Splash screen dimensions
The splash screen icon uses the same specifications as adaptive icons, as follows:

Branded image: this must be 200×80 dp.
App icon with an icon background: this must be 240×240 dp and fit within a circle 160 dp in diameter.
App icon without an icon background: this must be 288×288 dp and fit within a circle 192 dp in diameter.
For example, if the full size of an image is 300×300 dp, the icon needs to fit within a circle with a diameter of 200 dp. Everything outside the circle turns invisible (masked).

@MarcaDian
Copy link
Author

MarcaDian commented Oct 6, 2025

@validcube hello, according to this comment, the old "correct" scaling for the monochrome icon needs to be restored, which means this issue is open again.
Should I make these changes or leave the current scaling?
And I see that there is no consensus on this issue in the team. If we return it, then this issue should be closed so as not to cause confusion.

@validcube
Copy link
Member

validcube commented Oct 15, 2025

@validcube hello, according to this comment, the old "correct" scaling for the monochrome icon needs to be restored, which means this issue is open again. Should I make these changes or leave the current scaling? And I see that there is no consensus on this issue in the team. If we return it, then this issue should be closed so as not to cause confusion.

Sorry for the slow reply, I did not receive any notification from GitHub at all.

Edited, sorry I missed understand your point.

Edited again, yeah, you should leave it...

Copy link
Member

@validcube validcube left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥞💄 LGTM!

Verified with Android Studio, personally I would make the icon bigger by resizing it to 115% or 130% to account for optical alignment slightly outside the circle or touching the smallest square grid because our logo's a V but an decision has already been made so that's fine by me (or not, there's like 5 episodes of this discussion).

Image

Haven't verified with an actual device because I can't disable Google Play Protect, it won't let me do it for some reason.

@ILoveOpenSourceApplications

I'm confused here from all the screenshots, but is the monochrome icon slightly bigger than the original icon?

@oSumAtrIX
Copy link
Member

Yes

@LisoUseInAIKyrios
Copy link
Contributor

Monochrome icons don't have a background. The sizing here matches Android design specs and is correct .

See #1124

@validcube
Copy link
Member

Assuming no pushback, I'm merging this by tomorrow.

@oSumAtrIX
Copy link
Member

To confirm, is the shape scaled according to the official logo & is the monochrome icon scaled according to androids size standard? Are the scalings guessed by eye or calculated?

@LisoUseInAIKyrios
Copy link
Contributor

Scaling is correct for both brand guidelines for color icons and Android spec for monochrome. Nothing is eyeballed.

@oSumAtrIX
Copy link
Member

Last time I tried scaling, I had to eyeball it. What's the formula you used to scale?

@@ -1,30 +1,40 @@
<!-- Copyright 2024 ReVanced. Not licensed under GPL. See https://github.com/ReVanced/revanced-branding -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I would state the warning right away in readme or do both, also I don't think adding years make sense as that can be outdated every year or probably raises weird loophole legality questions in the future. (I'm not a lawyer)

Copy link
Contributor

@LisoUseInAIKyrios LisoUseInAIKyrios Oct 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2024 is the year of the logo redesign (the origin of that particular branded resources). But it could be the year the project started. I don't think it makes any difference which year is used (or if no year at all is used).

See the patches repo for the open PR that adds a simple text file explaining the branding isn't GPL. After it's merged Manager could add the same file.

I don't think the "brand identity is not GPL" is needed in the readme. All the major open source projects I've come across that have copyrighted non open source files have the disclaimer somewhere on the files, or they go one step further and separate the branding into a separate project (such as Chromium and the Chrome browser).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants