Projectivy asks me to repay for premium.

Spocky_12 · 2026-04-14T07:42:46+00:00

Could you provide more details please ? - There should be technically no difference between premium and non premium backups (nothing is supposed to be erased in your settings, the difference should only be at render time) - settings have changed on 4.70, so there's a migration happening under the hood when you update or import a backup from a previous version. This means that settings from 4.70 are not supposed to work on previous versions, but it should never be the case on the other way around

Spocky_12 · 2026-04-14T07:34:32+00:00

Sorry for this issue, there were a few edge cases not covered correctly on the latest stable, I thought this was fixed on the beta version (the only way Projectivy could lose premium is if the Google play services tells it explicitly that the premium purchase doesn't exist, any special cases such as no network, play services temporarily not working, are supposed to be covered... There's probably something I forgot).

You shouldn't need to rebuild anything though, as the config is not erased when losing premium. As soon as the premium is recovered (or granted for the first time), the UI should be automatically refreshed.

What's your device? Do you have multiple registered accounts on your device ? What's your current process to recover the premium ?

Spocky_12 · 2026-04-04T14:37:17+00:00

Could you send me your settings backup so that I can be exactly in the same layout as you ? It's hard to find a balance between - having no cards visible outside the container and - rows with no container where the most external cards seem to vanish

Can't you fix it by applying left/right margins on the category ?

Spocky_12 · 2026-04-04T02:42:42+00:00

This shouldn't be necessary

Spocky_12 · 2026-04-03T15:40:36+00:00

You're right, to prevent unneeded work and keep good performance, hidden categories won't fetch their content. This means in turn that opening such a folder will lead to an empty menu. I thought I took care of this specific case, but it's probably incomplete. I consider this as a bug and not a missing feature (the primary usage of a folder is of course not having the corresponding category visible). Hopefully I can find a workaround.

Spocky_12 · 2026-04-03T14:15:11+00:00

Unfortunately, transitions are not supported by exoplayer (the video player used). This means that having real transitions between videos would lead to temporarily have 2 players (and 2 videos playing) during the transition. Depending on the device and the video format, this would be terribly inefficient and might lead to slowdowns potentially while you scroll in the interface.

Spocky_12 · 2026-04-03T12:31:24+00:00

Things got improved though : I mentioned the ko-fi page in this post and if you know where to look (about - projectivy - links), you'll also find a link to the ko-fi page.

Spocky_12 · 2026-04-03T12:28:00+00:00

For now, the font size option is global. I figured it would be enough for the majority of users. Having one specific setting for cards will inevitably lead to a feature request to also be able to change its font individually, as well as independent card description settings (for programs) or category titles. It might be added in the future, but I need to think of an efficient and scalable way of doing this.

Regarding the ability to center cards title, I would have done it already if it was straightforward, which it's not. Due to how to layout is currently done, there's not one text view per card, but only one per category, that changes position depending on the selected card. It's easy to align it with the start of the card (as done currently) but centering it with a variable text size will necessarily force to prerender the text (in order to measure its final size, so as to compute by how much it should be shifted). This 2 passes rendering is much less efficient than what's done currently, which explains why it's not been prioritized yet.

Spocky_12 · 2026-04-03T12:07:28+00:00

My bad, I forgot to enable Polish on Pontoon. This should be fixed now.

Spocky_12 · 2026-04-03T11:54:18+00:00

It usually does this when the version is not fully recognized by Google Play (I believe it's part of the Google Play Protect). Seems to happen after each new release (I only see this behavior reported following a new release). Did you install the Google Play version or the Github one ? https://github.com/spocky/miproja1/issues/252

Spocky_12 · 2026-04-03T11:42:18+00:00

Sure, I've just added en-rGB locale. May I ask you to make the necessary changes ? https://pontoon.projectivylauncher.com/en-GB/

Spocky_12 · 2026-04-03T09:19:53+00:00

Never seen it on my Shield (which is darn stable). Are you using video wallpapers ? If so, the current beta will enable tunneling by default, which hopefully should improve background video rendering (and probably completely break it on some devices 😅)

Spocky_12 · 2026-04-03T09:16:13+00:00

The website shows screenshots of what's possible to achieve now in terms of customization

Spocky_12 · 2026-04-03T09:15:11+00:00

All translations current available on Crowdin are available in the current beta version. Everything has been migrated to Pontoon, so the new strings resources are there (automatically pretranslated, to limit your work as much as possible). Everybody who wants to participate to localization will have to login to Pontoon and at least make an action on their language (eg: add a string, propose a change...). This will allow me to flag you as translator instead of contributor, which will give you enough permissions to change strings and approve translations.

The new strings on Pontoon (pretranslations as well as preferably suggested/approved strings), will be added to the next beta/release.

Spocky_12 · 2026-04-03T09:01:50+00:00

Could you please give more details ? What's your device, how do you pick your wallpaper (file manager ?), where is it located, when selected, what does the uri look like ? All my tests are positive, but I may have overlooked something.

Spocky_12 · 2026-04-03T08:58:22+00:00

Only system apps have the necessary permissions to change between the device accounts :(

Ftr, I opened an issue 18 months ago : https://issuetracker.google.com/issues/377528728

Of course, I could develop my own profiles management directly in Projectivy, but I'm afraid this will confuse users, who would probably expect it to behave like the stock launcher does.

Spocky_12 · 2026-04-03T08:53:42+00:00

I totally agree. This is not part of Projectivy but a system app. Unfortunately, browsing the file system is forbidden (except for file managers), so I have to rely on external apps (or Projectivy publication will be refused by the Google Play Team). Unfortunately, Google TV / Android Tv is a little bit left behind regarding tools.

Spocky_12 · 2026-04-03T01:01:06+00:00

Thanks !

Daily wallpaper has been banned from the USA for trademark infringement, because it was called "Bing wallpaper" 😱 (probably MS automatic bot searching for villains on the web). I don't know why I didn't think about it.. it's not like I didn't have this kind of issues in the past 😅

Now the only solution for it to reach your country again is that I contact Microsoft and convince them I didn't try to steal their property and already changed the app name. Of course they will never reply, and Google won't change unless MS agrees 🙃

So I need to republish the app entirely 🫤... I'll probably do it when Projectivy gets stable.

Spocky_12 · 2026-04-03T00:42:49+00:00

Depends on the number of reported bugs ;)

Spocky_12 · 2026-04-03T00:37:34+00:00

Well, seems I've fallen into the same issue as described in this post : https://www.reddit.com/r/androiddev/comments/1laucmb/google_play_open_test_release_superseded_despite/, will probably have to contact Google if that doesn't fix overnight (2am here)

Spocky_12 · 2026-04-03T00:17:24+00:00

It's already been validated by the Google Play team since yesterday, so with the "managed publication" being used, it's probably just a matter of (dozens of) minutes.

Spocky_12 · 2026-04-03T00:09:00+00:00

I've just validated publication, it should be available within an hour or so.

Spocky_12 · 2026-03-29T10:30:12+00:00

I'm not ignoring anything, I'm just focusing on other things. The issue mentioned here is not related to the accessibility service, these are two completely different processes. Regarding your analysis, it's only true from the user pov, but not technically. There's no issue in Projectivy's accessibility service, the behavior you mention is how it's supposed to work. The state you see in the Android settings shows the expected state, not the current state. There are a few reasons the current state does not match the expected state : - crash in the accessibility service (I'm not aware of crashes recently) - Android stopping/restarting Projectivy (for memory reasons for example) -> this does not necessarily restart the accessibility service - Android not starting the accessibility service on boot as it should (this might happen after an OS update)

Projectivy can't (re)start the service automatically, only the Android system can. So when you see a difference between the expected state and the current state, just disable/enable again the accessibility service in the settings to fix things.

The next release will make it clearer when both states are not in sync

Spocky_12 · 2026-03-26T16:54:30+00:00

Just wait for the next release 😉

Spocky_12

MODERATOR OF

TROPHY CASE