Hi Everyone,
Thank you for your continued engagement and feedback, which have been invaluable in shaping the roadmap for Legion Go. I want to address some outstanding concerns that have been raised over the past few months and share our plans for ongoing improvements and updates.
Abandonment Issues
We appreciate your eagerness for updates and are committed to improving the device at a steady pace. However, I understand that our update cadence may be a little slower than some of you might expect or demand. It's understandable to want more, faster. We've come a long way but we still have a ways to go before the device is living its best life. Despite how it may 'feel', work hasn't stopped on improvements. We have updates planned for quite a while yet.
Our standard EOS (end of service) policies usually extend around 3-5 years after a device is last sold which includes continued critical updates, parts availability, etc. The EOS date is October 28, 2029 for Legion Go which is about 6 years after the original launch date, after which there are still technically paths to get support, pending parts availability if necessary. So for the next several years if/when you need to contact us you'll be connected with people who are familiar with the device and able to help.
We are also committed to this category long term. We've learned a lot from the launch of this device and your feedback has shaped our understanding and response to key issues. Resources being finite, however, we try to focus on addressing the most significant (and solvable) challenges first. While we'd love to address every concern, it's important to acknowledge that not all issues can be fully resolved due to the inherent limitations of any technology.
That said, we have secured some additional resources for our software team, created a VOC (Voice of Customer) team specifically dedicated to this product and aggregating feedback from all available sources (reddit included) and bringing that feedback directly to the Product Management, Engineering, Quality and Development Teams. The "contact us" button on the right flyout menu in the help section is being actively monitored in all languages and I've seen feedback in many languages being reviewed weekly if not daily. Please continue to use that to provide feedback directly to the dev teams.
In terms of the actual speed and cadence of updates, they are going to continue to be spaced out quite a bit (pardon the pun). Part of the reason for this is additional non-negotiable security reviews that all Lenovo software must go through in order to ensure compliance with high standards of security. This ends up necessitating more "bundling" of features and updates into bigger releases to get as much in for review as possible in order to maximize what we're putting out. Nevertheless, we are still looking at ways to improve speed and frequency of updates.
Finally, for those who may be worried about any potential future devices impacting support for this device: any improvements we make that can be implemented on this device will be. In other words, there will be a continued focus on backward compatibility to the extent possible if and when that becomes necessary.
Transparency
While many of you appreciate our openness about the development process, I understand that some may feel frustrated when plans change or are delayed. These updates are intended to keep you informed about what we're actively working on—not as firm promises, but to provide insight into our intentions and priorities. It's important to note that these plans can and do evolve based on a range of factors, which is one of the reasons this kind of transparency isn't more commonplace.
Feature Updates and Prioritization
Our hand was somewhat forced to pivot away from more pressing functional updates to the UI overhaul because our original UI was getting increasingly difficult to update. Since users were also (albeit less urgently) asking for an overhaul of the UI it made sense to get that out first to provide a better platform for future updates. The new UI will continue to be refined alongside other ongoing planned updates.
Two of the more important things we hope to have added to the next major update are fPPT and sPPT support for full TDP control and Gyro calibration. I don't know yet first-hand how robust those implementations are going to be but if there is need for improvement after release we will continue to work on it. I know those two items have been heavily featured in my previous updates and like you I wish they were already implemented, but fortunately they remain high priorities for the next big update.
Closing Some Loops
Portrait Display: Incompatibilities and functional limitations presented by a native portrait display on windows are going to persist. At this point it doesn't seem like there is anything that can be done at a SW/FW level to overcome the HW challenge presented. More on AFMF specifically below.
Mouse DPI Settings: Seems to be some confusion about implementation. You have to turn FPS mode on with the switch on the right controller for the DPI setting to appear in Space, but it is there in the configuration settings for the controllers. Trackpad DPI is not implemented though was requested. If that's still necessary I can look into requesting a higher priority look at it. While not entirely the same thing you can adjust the cursor speed in windows for the touchpad as a partial work around.
SD Card Stutter: We've worked with both SD reader vendors and our ODM and in-house engineers and just about everything that can be done about this has been: updated drivers have been released to Space/Windows Update that minimize SD card sleep/wake time, and instructions on how to disable modern standby have been made available. It's a situation where the majority of users seem to not be impacted and the ones that are, many of them have found success with the available resources.
LT / LS interference w/ Lower Deadzone Settings: This is due to the hall effect (magnetic) actuation of the LT and LS as well as their proximity on the left side with the offset joystick locations. Easiest solution is just to move the deadzone setting back % by % on the left stick until the interference is gone. It seems to be more prevalent with the lower deadzone settings (<5%) that are in most cases lower than they realistically need to be. This is another issue that is not impacting a majority of users.
Minimize Space to system tray: Currently being optimized for implementation, should be sooner rather than later though don't have an exact date.
Additional Customization Options for Space: Both cosmetically and structurally, this is of course the ultimate intended direction we're headed in but will take a back seat to other functional updates. It's an ongoing long term effort that will likely be realized gradually over time.
"Desktop Mode": Other devices that have this don't have a trackpad so it's a little less urgent on the Go. We have added the ability to map mouse clicks to buttons including triggers and the trackpad is there for mouse support as well as the FPS mode sensor. That said it's still in the plan to provide a more robust implementation just not in the super-near future.
Joystick Diagonal Input Speed: Have seen numerous posts about this, and after having looked into it more deeply with the extended teams it seems like not much can be done at a SW/FW level, a true improvement would involve hardware adjustment. Some users have found some resolution by adjusting the response curves.
BIOS Settings Accessible Through Space: I'm continuing to push for this (VRAM, charge, etc.) settings to be set and toggled in Space without the need to enter BIOS, and this is still being actively discussed. Recommendation from our engineers is to set UMA Buffer to Auto as this will leverage the logic in the AMD driver to dynamically allocate the necessary VRAM in any given scenario. The inclusion of BIOS-level settings in Space is still being actively discussed.
V35 BIOS: This version was removed for now because it changed the way the power button light is controlled and hasn’t been implemented in Space yet. This version also resets to default settings so if/when you eventually upgrade to any version equal to/higher than 35 you'll need to (one time) reset any UMA buffer settings/etc. in the BIOS. Not ideal but not avoidable. Again, recommendation from engineering team is to just set UMA buffer to auto as the best overall setting as AMD's driver has good management built in to manage the tradeoffs between system and video memory.
AFMF2: As some of you have noticed this seems to be more promising on the Go with the generic AMD preview driver than AFMF. We're working with AMD again to see if we can make some modifications at all for the Go-specific driver to get this working better, including proper rotation of the on screen display to accommodate our panel, but all of this needs further testing and co-work. Again no promises but it looks promising.
Power Savin' G: Together we mourned the loss of a real one. However, I am personally campaigning for its return in some form (as long as it doesn’t take away from more pressing issues).
Others Still Ongoing (not an exhaustive list):
Per-game profiles
Right performance menu flyout not requiring controller button press (map to other hotkey/button for kbms users) eventual implementation
Include refresh rate/resolution in custom performance modes
Change default screenshot folder in space
Add x-box button to quick settings menu quick options.
Accessories
More first party accessories are coming over the course of the rest of the year. Some more exciting than others but expect additional options to further enhance your experience.
--
On behalf of our extended team, I want to express again our sincere appreciation for your continued engagement (whether positive, constructive, or critical). Your passion for the device we all love is highly valued. We're just getting started here, and while we may not fully satisfy everyone, together we can make significant strides towards enhancing your experience. Thank you for being an integral part of our journey and looking forward to the future.
Thanks,
Ben
Disclaimer: The details provided herein are intended as a courtesy update and do not serve as a binding commitment or warranty. Lenovo cannot guarantee the accuracy or timeliness of the information and reserves the right to modify product and service plans at any time. We are not liable for reliance on the projected timelines or features, which are subject to change based on various business needs and product development considerations.