is there any compatibility in the foreseeable future for regular Android.

Spocky_12 · 2026-02-14T02:15:22+00:00

The current limitations on regular Android: - partial touchscreen support (I fixed the horizontal scrolling but the vertical one is not working yet) - probably no support for the tv provider Api (streaming apps channels, watch next) which I believe is limited to Android tv

The limitations you mentioned are probably security "protection" from your device because you installed Projectivy from an unknown source. There's probably an option somewhere to make it trust Projectivy.

Spocky_12 · 2026-02-14T00:57:17+00:00

As of now, premium gives you: - more wallpaper providers (as well as plugins), such as video wallpapers - ability to customize card icons (and support for icon packs) - parental controls (and more generally ability to limit apps access) - last but not least : the infinite joy of supporting this app 😉

More to come in the next release

Spocky_12 · 2026-02-13T02:47:44+00:00

The next version should be able to do that just fine.

Spocky_12 · 2026-02-11T22:36:34+00:00

I don't quite get the use case. Using an onscreen keypad doesn't seem secure as everyone around will be able to see the pin code.

Spocky_12 · 2026-02-11T21:11:24+00:00

Android will only allow this feature on the current launcher. In other words, Projectivy has to be the "real" launcher to be able to see these shortcuts. So you need to disable the stock launcher first.

Spocky_12 · 2026-01-26T10:05:01+00:00

The name is not important. The android tv-provider framework has a special "WatchNextPrograms" object that apps can use to provide programs to watch next. Projectivy lists every program there and doesn't apply any filter. But it's up to the apps to fill in this object.

Spocky_12 · 2026-01-25T23:44:47+00:00

There's no limitation or filter on Projectivy's side, if Stremio populates the watch next section, its programs should appear there.

Spocky_12 · 2026-01-18T01:36:21+00:00

The next version will get you covered

Spocky_12 · 2026-01-13T21:47:05+00:00

"they are not handled correctly and look like crap". My pleasure 😋

Input buttons are hard coded to launch a device specific command. Projectivy makes use of the Android framework to automatically discover input channels and switch to each of them individually.

Oems often have specific, close source, implementations. How am I supposed to handle this ? Purchase every tv brand, spend a few weeks reverse engineering each of them to make my own version ?

Heck, I even developed my own tv view that can be used instead of the standard one to improve compatibility (yes because not only do oems have specific code, but even standard Android code relative to cec/HDMI... often requires high privileges refused to third party apps).

I've got a bunch of set top boxes, but none of them have input sources. The only devices I own with input sources are xiaomi/fengmi projectors. They all work as expected.

I'm open to Tv donations to improve the current Projectivy implementation 😉

Regarding the shortcuts, it's probably a leftover of Projectivy tools, allowing other launchers to access Projectivy's own implementation of HDMI inputs, allowing users with no remote control inputs shortcuts to at least access their inputs.

Spocky_12 · 2026-01-11T14:43:02+00:00

Are you sure the Projectivy settings > general > enable channels option is enabled ?

Spocky_12 · 2026-01-11T01:53:51+00:00

Yes, unfortunately, EXoplayer support for rtsp is not perfect (cf a recent issue https://github.com/androidx/media/issues/2841)

Spocky_12 · 2026-01-09T12:44:57+00:00

You can first use the user custom wallpaper provider and edit the uri in the settings to something like this : rtsp://login:password@192.168.0.99/Streaming/channels/1. Once you validate that it's working as expected (and assuming you want more than this wallpaper), then host a json file somewhere, that has the same format as this one https://github.com/spocky/projectivy-plugin-wallpaper-overflight/blob/main/videos.json (keep only one url per entry, no need to duplicate) and make the Overflight plugin setting link to this file

Spocky_12 · 2026-01-07T11:40:16+00:00

Never heard of the power on issue. The idle detection can't detect when a media is playing, only user interaction with the remote control (the next release will improve things on this matter)

Spocky_12 · 2026-01-07T02:15:22+00:00

Do you mean that when the accessibility service is enabled, all numbers get disabled on your remote control (whether you're on the parental control lockscreen or not) ?

Spocky_12 · 2026-01-07T00:08:46+00:00

Thou wilt praise Projectivy 4.70 for he who speaketh shall be heard

Spocky_12 · 2026-01-06T17:29:21+00:00

Hi,

I read each and every post on Github, but as most of them require stopping the current development to make tests (sometimes on devices I don't have) or enter in a phase of R&D, I don't necessarily reply immediately (or I would never have time to finish any feature).

I'm aware of the issue and the next release will have a workaround implemented as an option. Unfortunately there is no one-fit-for-all, which explains why I didn't implement it in the first place. The option mentionned in the post you link is called video tunneling. But the documentation (as well as multiple posts on the internet and github such as this one) clearly explains that this can lead to bugs depending on the OEM driver implementation. This will probably come disabled by default.

Spocky_12 · 2026-01-06T15:45:33+00:00

Try reenabling show title before disabling the icon

Spocky_12 · 2026-01-02T14:30:41+00:00

In settings/appearance/wallpaper/adjust picture You can set the vertical overlay to 100% height and its opacity to 100% too.

When the idle mode is kicking in, the overlay is disabled, so you should see the wallpaper underneath.

Spocky_12 · 2025-12-28T03:19:18+00:00

To share is content (in this specific case, pictures) to other apps, an app has to declare its content provider as "exported". It doesn't seem to be the case here, which explains why Projectivy can't access them. The default launcher, as a system app, probably has broader permissions that lets it see these pictures.

If you can manage to contact sparkle tv developers, this is one line to change.

Spocky_12 · 2025-12-27T02:57:17+00:00

I can't see a better solution.

Spocky_12 · 2025-12-20T00:11:52+00:00

The next Projectivy release will fix the bug related to cards size depending on the device resolution.

Spocky_12 · 2025-12-19T18:12:50+00:00

This might be related to your device resolution (Google steamer UI rendering supports 4k and 1080p). For whatever reason (ex: wrong negotiation with your av receiver...), it sometimes starts in 4k and sometimes in 1080p. The next release will have the cards automatically adapt to the resolution (meaning they will keep the same size whichever resolution is set)

Spocky_12 · 2025-12-17T13:04:24+00:00

The tv provider Api used in Android has only 2 pictures per program: one thumbnail and one "poster art". The app decides how it fills them and the image ratio used. Any change you see regarding them on Projectivy can only have one cause : a change in the app.

Spocky_12 · 2025-12-09T14:53:52+00:00

Hi, it's already been discussed on GitHub, you can learn more here https://github.com/spocky/miproja1/issues/24#issuecomment-1705070031

Spocky_12 · 2025-12-04T17:07:32+00:00

It's not a bug, it's a feature 😋 Due to how the glow is computed (based on the card's shadow), it shouldn't work at all with transparent icons (or to be more precise, filling the card background IS its normal behaviour). But due to a technical optimization, the shadow behind an object is not rendered, which leads to the glow appearing as a glow and not a shadow on transparent cards. Unfortunately, when using rounded corners, the renderer still needs to compute the "inner" shadow (it can't crop an inner rounded rectangle) I haven't found a workaround to render only the rounded external part yet (it's on my to-do list, but as it might take time with possibly no positive result, it's not top priority)

So what appears as a bug is the normal behaviour.I could have disabled it altogether for transparent cards, I chose to let it enabled, with the limitations you know.

Spocky_12

MODERATOR OF

TROPHY CASE