[Android Apps and Games] spocky12:
Thanks ! The notification feature is still a bit experimental in that using "standard" code for managing notifications leads in many unwanted messages I need to filter out (it seems that many android tv apps developers who want their background service kept in memory add a "service" notification there.).

Could you give me some examples of apps supporting the "now playing" feature in the stock launcher but not displaying it as notification in Projectivy ?

Anyways, along with standard notification, there's also a "real" Android Tv "now playing" feature that I need to support in a future version.

To be as effective as possible, the "home replacement" feature (using the accessibility service) needs to consume the "home" button event, making it unavailable to the system. I'll try to add support without breaking the current feature too much ;)

I think you're using the experimental "shutdown when hdmi signal is lost". It's unfortunately not compatible with all devices. As this event is not shared by the system, I had to find another way of detecting it.

As of now, it detects when the HDMI input app loses focus without the user interacting with the remote control. This usually means that it self closed.

Unfortunately, there's a bug on FengOs : the volume button events can't be catch by any accessibility service. This means that when Projectivy's accessibiltiy service detects that the input app has lost focus (which it did, because the volume indicators are managed by another app that overlays over the current app), it's not informed that a button has been pressed by the user, and thinks that's because HDMI signal has been lost.

Here's the issue that led to this version : https://github.com/xbmc/xbmc/issues/16271

I don't think it's possible as it's not how it works internally in the mediatek framework.

Yeah, sorry for that. The settings holding the categories/cards data has been changed. I developped a migration feature upon start, but a last minute change broke it :/

Future versions will have an export settings feature.

Regarding the "launcher override" no longer working correctly, I'm not aware of that issue. Could you please give me a detailed explanation of what worked before (options enabled in the settings, accessibility service state, device model...) that doesn't works in the 4.2x ?

Tv Inputs shortcuts carrying to other launchers should still be there. You need to execute them at least once inside Projectivy, so that the shortcuts are enabled (I had to make it dynamic as without this in-app detection, it would mean that the shortcuts were always present, even if the device doesn't have HDMI inputs).

As for the CCwgtv controlling the HDMI inputs of the device it's plugged into, I was not aware this was possible. I suppose I'll have to buy one to check this ;)

Not sure I understand exactly which "launcher selection menu" you're talking about. if this menu doesn't belong to Projectivy but is provided by another app, the renamed inputs won't be present there. I know some android devices support renaming hdmi directly from the OS settings. If your device supports it, this is the way to go as this should be reflected in Projectivy Launcher as well.

I can't promise anything, but I've added your request to my todo list.

1- not sure this is possible with the components I'm using but I'll think about it

2- this was the case before 4.2x. Unfortunately, there's a bug in the "Leanback" framework developped by Google (well, no, there are _many_ bugs, and the last update was 18 monthes ago :/). The optimizations I added in 4.2 required me to remove the dirty workaround I was using. It's still noted on my bugs list, though. So I'll eventually find a workaround.

3- I'm mostly testing on my Shield 2019 and didn't find any issue. Let me rephrase : "It's not a bug, it's a feature" ;) A I wrote before in this thread, multi-rows categories will never be taller than the screen remaining space. If more rows are required, an internal scroll will be added to this category. The only layout glitch I'm aware of is when cards with different dispaly ratio (square and rectangle) are in the same multi-row category. Then, depending on the scroll state and currently displayed cards, the layout may change to keep the currently on-screen cards aligned. If you have another issue, don't hesitate to send me screenshots and give me more details so that I can reproduce it.

As I wrote above, this was not intended. And believe me, spending time developping a migration feature that doesn't run when it should makes me feel a bit unconfortable ;)

I just need to find the best way to import/export data (on a smartphone, there's always an email app, along with a least one cloud service such as onedrive, google drive...). As these features are generally not installed on AndroidTv and external storage management is a mess on android, the most compatible way I could think of is writing it on the internal storage. But this means that users will have to install a file manager or use ADB-like tools to export/import the file in/out of the device.

If you're talking about the block google play self-update feature in Projectivy, it works by making the google play app readonly. It worked when I developped it, but I don't know if Google made changes to overwrite read-only files since then.

Regarding your black screen issue, I understand that it happens when an HDMI device is plugged in. When does the screen get black exactly ? Do you see the Xiaomi logo at boot ? The launcher for a few seconds ? You say that with no HDMI connected, you're able to access settings. If you connect an HDMI device later on, does it automatically lead to a black screen ?

That's an issue I've only seen on FengOs, which is due to a bug related to the customizations they made on the OS. Not sure it's the same for Sony. Anyways, it should only happen with the Accessibility service running so you might need to turn that off. You can also that the "alternate accessibility config", that might (or might not) fix this issue. To help debuggin this issue, you can also install Button Mapper and enable its accessibility service. If the same behavior is visible, then the issue lies on the OS (and its accessibility service management) and there's not much I can do on my side.

"Classic" Android Wallpaper Manager (which is the system component displaying live allpapers) is not supported on Android Tv. Not sure I can find a workaround.

No :'(

Icon packs support is planned. Unfortunately, most icon packs don't support Android Tv and most (if not all) of their icons are square-shaped. I might develop support and add a small Tv-ready pack, but then, it will be up to the community.

Amazon is doing all their possible to block the users into their OS...

Channel support is broken (advertised as programmatically supported, but not returning anything), Home button events are taken by the system to prevent override, custom accessibility services aren't displayed, their system wide settings are baked inside of they launcher app so that users can't disable it without disabling the system settings

However you can still enable the accessibiliy service manually (until a future update ?) with ADB : adb shell settings put secure enabled_accessibility_services com.spocky.projengmenu/com.spocky.projengmenu.services.ProjectivyAccessibilityService

I'm using Glide, a well known lib responsible of loading, displaying and managing image cache. The only reason I could see them disappear is if the system is running low on memory. But even then, I couldn't experience it myself.

To get logs, you need to install ADB on a computer, connect it wirelessly with "adb connect [your shield IP]" and run "ADB logcat > logs.txt"

That will be in a future update ;)

Regarding file manager, I think I tested with Solid Explorer successfully.