Hmm, I have the same issue - except I'm getting black bars even without any keystone correction (front projection mode, vertical keystone correction disabled as it's projecting perfectly horizontally).
Posts made by fonix232
RE: A few questions about the Halo
@Ari thanks for the quick response.
- Halo can be used as a Bluetooth speaker, please long-press the power button of remote, you'll see more options--display off
Thanks. Could you update the manual with this information? The long press power menu is not apparent, especially with a remote.
- this feature is just like the Bluetooth speaker mode, but it might consume the battery faster than the off mode, as it needs to keep the Bluetooth signal. PS: if you don't use the projector for a long time, you can long-press the power button on Halo to turn it off completely, still, please charge it once every two week to protect the battery.
The main idea for this point was to have the Halo, while connected to mains power supply, in a "semi shut down" state, where it's not projecting, but still is active. Sort of like an active standby, and most definitely not for carrying around in this state.
- the battery percentage needs the hardware optimization, so sorry it can't be added for now, we shall make it up for future models.
Uhm, you already report the battery information - otherwise the battery icon wouldn't be displayed, and other, power user tools would not display the percentage. You literally just need to tinker how the battery icon is displayed, and e.g. add the percentage text to the overlay popup that right now just says "Battery" (so it says "Battery: XX %").
Also I don't see how "we shall make it up for future models" would be something you want to say to existing customers. Reassurance that a base feature so simple to implement will come IF you purchase the next, even more expensive model, is anything but reassuring. It won't make me want to buy your next product, it will make me want to ditch the brand completely. Hopefully it's just an issue with communication (as a non-native English speaker, I too often translate, or even mis-translate, my native country's proverbs and expressions, so I understand if such thing happens, which seems to be the case here)
- We'll update the firmware every quarter of the year. It's a smart projector with official android tv system, so it'll need much more tests for the system issue and compatibility with other devices and apps.
Understandable, but nonetheless security updates should be pushed to the device in a timely manner. I'm not talking about new features, but e.g. in the June security patches, Google fixed two major Bluetooth bugs - both of them are still present in the latest Halo firmware, in basically August!
- this setup is to make sure the update can be finished successfully, if something happened to the update process, the projector would be damaged. System update consume battery faster than normal using, if it has no battery during the updating process, or power got cut out(even when plugged in), Halo might not be turned on again.
Power loss during update would be a really rare scenario, and even if that happened, as I mentioned before, the update took me about 10 minutes, and less than 10% in battery - started from 83% and ended up with 75% after the system settled.
- it's a default setup which can't be changed due to the android tv system, appreciate your understanding.
No, it isn't. All my other Android TV devices save the ADB keys properly, and only prompt about a new connection if the key wasn't saved ("remember this device" was not checked on previous connection, or there was no previous connection at all).
- thanks, I'll update it to our team.
Awesome, thanks. If you were to set up a Crowdin (or similar crowd sourced translation tool, hell, even a git repo of your strings.xml collections), I'd gladly contribute and help these small bits gets fixed.
- you mean Netflix issue? Please know we've been working on this issue for a long time, and it's not for us to say if we can get it or not. Netflix is a big request from all customers, but we are still quite new to the overseas market, it's hard to just cooperate with the third platforms, but sure we would finally get it with the support from loyal customers like you guys.
Yes, I'm talking about the Netflix issue. Certification depends on multiple factors (in my case, the company I work for requires little certification on the device as our content is not "crucial" for protection, unlike the many shows Netflix wants to keep off from leaking/getting ripped): DRM compatibility, HDR playback capability, and of course Android API certification, which you should be able to pass easily, unless you changed major Android APIs that Netflix relies on (given how pure the Android TV experience feels on the Halo, I suspect your changes are superficial additions only).
Thanks again for the support, have a nice day~
In the meantime I've got a handful of other issues I keep seeing.
Plex Media Player drops subtitle support in certain cases. Subtitles are enabled, but not rendered on-screen, if the projector goes into sleep, or if sideways projection is enabled, and keystone correction is on. This is usually fixed by a reboot (in case the projector went into sleep mode) or by disabling keystone correction (thereby rendering sideways projection unusable with Plex). This is not an issue I've observed on any other Android TV devices I have, however it only happens to Plex. Possibly you've overridden one of the APIs Plex uses for subtitle display?
The Halo loses focus while in "screen off" mode. I don't like shutting it down (due to the above ADB issue), so I just turn projection off, and let the device sleep while plugged in. Upon resuming, depending on how long the device has been sleeping, the projection will be slightly, or totally out of focus, and requires a focus trigger (switching the mode switch on the remote to focus mode and back does the trick usually). However this slight unfocusing also happens during viewing - after about 2-2.5 hours of usage, there's a visible jump as the device "focuses", only to ruin the currently established focus. The device is NOT moved during these times, and is sitting peacefully on a chest of drawers, completely stable.
HDR. The July update has disabled HDR completely, and not even workarounds like using VLC (which, in most cases, can play HDR-enabled content without it being too dark on non-HDR displays) help. The image is dark and unsaturated. As HDR is being touted as a major feature of this projector, I'd expect it to work.
Volume setting. The remote does not allow for long pressing the volume keys to quickly mute/increase volume, requiring manual clicking multiple times to set the proper volume level. The volume bar is also displayed for too long.
A few questions about the Halo
I've just received my international/UK version of the Halo, and while I'm more or less happy with it, there are a few things I'd like to see improved - most of them can be easily done by small firmware changes:
- "Screensaver" mode: I can see myself lugging around this bad boy to act as a somewhat smart speaker - with WiFi shared from my phone, or just using it even as a Bluetooth speaker. In these instances, I do not want the projector part on, as to save power (and since the Halo does not use USB-PD for charging, plopping it on a powerbank is not an option)
- Standby mode: instead of turning off the projector, a standby mode would be appreciated - projection, etc. are all off, but the OS is still running to be quickly woken up, but still consume very little power. Automatic power-off could be enabled if the device is running from battery
- Battery management improvements: first of all, it would be great if the actual percentage of the battery was made visible on the home screen. Right now it's just the arbitrary "parts filled" battery icon.
- Slightly more frequent updates, at least for security patches - the release, that was built on 4th of July, is still just the May security patch!
- Speaking of updates... Please remove the 50% battery requirement for updates, if the device is currently plugged in! It's incredibly annoying, especially since I had to do a whole discharge-charge cycle and a reboot for the system to realise the battery is charged enough. Though this bug might've been fixed in the latest update, but still, while on external power supply, why not let it update?
- Fix ADB keys not being saved. I use HomeAssistant, which requires ADB access for full integration and control - but the Halo keeps forgetting the keys, even though I check "remember this machine" every time.
- Pretty please change all the Xgimi additions' english mis-translations (mainly the "open" and "closed" bits to "on" and "off"). This should be a straightforward thing to do, and even a crowdsourced solution could be made - I'm sure a lot of members here would gladly submit translations to their native language.
- App certifications... The earliest complaints are from November 2019! You've been working on the certification process for over 8 months now! And no news apart from it being underway... I work in the industry, and have had to certify a few customised Android platforms before, the process itself is incredibly quick, unless there's some major issues in the custom OS implementation.
If at least the smaller, quick to fix issues could be attended to, that would be awesome!
RE: HALO cannot be updated
@Rasmus I had the same issue a few days ago when my Halo arrived. What helped fix it was to do an almost full cycle on the battery (unplug from mains, put a movie on, roughly two hours in I got the battery low warning), charge it full again, and attempt the update after a reboot.
Though the whole minimum battery for update thing is ridiculous when the device is connected to an external power source. Especially the 50% minimum - it's usually 20-30%, and for me, even this update (~800MB in size) was quite quick, from update start to reboot into usable state it took maybe 8-10 minutes.