Edited by ZenBalancer at 5-10-2017 16:51 |
There are user reports, confirming that "unallowed" spreading of for example BIOS versions considered unofficial by Chuwi, still providing the seeked solution according to the user:
http://forum.chuwi.com/forum.php ... 23599&fromuid=19651
This program works perfectly!
-- Post #19 - Cursor jumping while typing
I have got a pm from Jurgen, that the bios update diden't solve the jumping cursor problem
What seems clear though, that there is no change log, nor clear liability if something goes wrong. Why can't unofficial files be shared publicaly for what the file is, so that we can gather feedback if it's worth the risk, for how many users, or not? Or to get any tips about the files.
Because otherwise we would not be limiting unnecessary risks, making things worse for some, while others experienced good results.
Basically, currently here at the Chuwi forums remains a clear divide between those "in the know" and those not. While instead we need to have a clear divide, a clear line, between file versions that are certainly safe, and unofficial "experimental" or limited support ones that still might be worth it. And adding to the overview of relevant experiences in those regards.
Until then, you'll have to decide for yourself, what is worth it to you.
I don't know what the worst case thus far has been.
Has there been ever a bricked Chuwi device by an unofficial file, that Chuwi refused to provide or being unable to provide a working solution to de-brick?
How about warranty situation? Does Chuwi really pay-attention to how a device was bricked if so?
It is not the responsibility of any Moderator nor any user to take on that much liability for trying to remain responsibly helpful.
I think Chuwi would be wise to allow us more transparency, instead of leading to "back channeling"/PMs/etc.. for genuine Chuwi customers to continue enjoying their Chuwi devices after any change in the previously working situation.
Users and Moderators should be allowed to set a disclaimer on the shared files, and for themselves and everyone add their feedback and testing results, to change the status of such files. Perhaps from experimental, to tested. And from Unofficial to Official. Depending on what it fixes, and how much that would help Chuwi's reputation and sense of responsibility.
Currently, the community process is hampered in that regard. Relevant experiences and knowledge about such files are fragmented and not easily constructive.
This needs a consensus by as many as possible, for Chuwi to reconsider their position on community participation. That's the least that can do, if they won't go fully open source on their code bases within all the relevant licenses.
It might seem that I'm mixing issues, rest assured I'm not. It's about what Chuwi supports as a community process, that might be considered as officially supported, after it goes through the community process.
First the said community process must be allowed to be developed, by the community, under Chuwi's observation.
I'm learning from a conceptual page out of the Java community process, but perhaps the Linux kernel community process is much older, but at the moment still alien to me.
Edit: typo, adjustment, clarity, edit addition + update.