Csc V2.0.6
Fairy Dawdy
I used Process Monitor to see what is going on and noticed consistent read failures in the "c:\windows\csc\v2.0.6\namespace" folder - which I hadn't even known existed. Researching it, I found that it was used to sync files with a network server, perhaps to view network files offline.
The above failures were happening exactly before a write to file process started (not before reads), the namespace folder did not get used, I had nothing synced, and the actual writes to the network drives were successful.
So... I think my problem is I have been trying to do something I am not allowed to, and using a lot of memory to hold data while I am trying to do what I am not allowed, until I fail and finally put the data where it belongs...
Is there a way (preferably a command line that I can run in my code, or a registry entry I can modify) that can prevent my program from syncing files (if that is what is happening) or using that namespace folder when reading off a network drive ?
So what you have to do is run gpedit.msc on the machine in question and go to Local Computer Policy -> Administrative Templates -> Network -> Offline files -> "Allow or Disallow use of the Offline Files feature" set this to DISABLED (do not leave it at "Not configured").Reboot.
The lamp with updated firmware often has big delays (up to 10 seconds) between actions in the Yeelight app and actual behavior of the lamp. Please check the link to the video below demonstrating the issue:
Also, the old firmware (v1.2.8_0029) has a nice and very pleasant orange color for the night mode which looks really good in the night. Whereas the lamp with the new firmware (v2.0.6_0030) has acid yellow color for the night mode which is really bad. Could you please revert back the color for the night mode in a future firmware update?
i have lost wifi connection issue with my bedside lamp2, wifi connection lost after few hours and only thing to recover it by disconnecting lamp from power socket and re-plug it again which is very annoying for me and i am also using this latest firmware which has alot of bugs could you guys please release latest updates?
@chyhaiyuan is it really takes so long to update the firmware?? Why not just increase version number and revert back changes to the stable stage so your customers can use their devices as they expect it instead of struggling to make it work predictably? And then, when the devs fix all the issues, rollout the updated firmware that is currently broken. Please, hear and respect your users!
Why is it so ridiculously wrong?? Almost two months and nothing. There are many reports about the bad firmware, but developers keep silence like everything is OK. Is it so difficult to revert a firmware or update it as needed?? Or do we need to ditch Yeelight and look for another vendor? Your team is used to be so responsive and user oriented, but not anymore. Please hear our voices and make it great again!
on 15 Jan, I decided to factory reset my Xiaomi bedside lamp 2, and only add it to the Xiaomi app and not to Apple HomeKit.
I did that at 2am 15th Jan, and the lamp stays connected to 10pm 16th Jan. This is the first time the lamp stays connected for more than 24hrs.
I rerecord speech at 128 kbps, stereo, 44100. On v2.0.6 5 minutes speech takes 6 to 10 seconds to record on v2.1.0 5 minutes speech takes 20 to 40 seconds. This increase in time is on 2 PC both running WIN 7. what can I be doing wrong
RIDE (Robot Framework IDE) v2.0.6 is a new release with minor enhancements and bug fixes. The reference for valid arguments is Robot Framework installed version, which is at this moment 6.0.2. However, internal library is based on version 3.1.2, to keep compatibility with old formats.
The T1Autograph iOS library has been updated to v2.0.6 (build 50).This update fixes a dark mode toolbar appearance issue for the modal display view.Documentation for both the iOS and Android versions is available on the T1Autograph product page.Show release notes
Carthage update: Carthage now fully supports .xcframework files. There is no need to use a previous T1Autograph version, and no requirement to override the default Validate Workspace value in your Xcode target build settings. If you are updating from T1Autograph.framework, be sure to change the references in your project from T1Autograph.framework to T1Autograph.xcframework.
T1Autograph for Android has been updated to v2.0.6 (build 20). This version is built on Android Jetpack and includes minor bugfixes.Documentation for both the iOS and Android versions is available on the T1Autograph product page.Show release notes
The T1Autograph iOS library has been updated to v2.0.4 (build 49).This update is distributed with an XCFramework, replacing the older framework fat binary system. It is also available through Swift Package Manager.Documentation for both the iOS and Android versions is available on the T1Autograph product page.Show release notes
Carthage compatibility issue: As of January 15, Carthage has not yet added support for libraries vendored with xcframeworks. Until then we recommend forcing the previous version with "== 2.0.4" in your Cartfile. When building in XCode 12.3 or later, find "Validate Workspace" in your target build settings. It should be set to "No". However, please note the setting must be bold, indicating it is overwriting the project setting. Change the value to "Yes" and then back to "No" to accomplish this.
The T1Autograph iOS library has been updated to v2.0.4 (build 48).This minor update adapts for the new swipe-to-dismiss behavior of modal views in iOS 13. It also offers improved appearance when the device is in dark mode.Documentation for both the iOS and Android versions is available on the T1Autograph product page.Show release notes
e59dfda104