Pages

Advertisement

Tuesday, November 15, 2022

[SOLVED] Portronics Sound Drum turns off every 10 mins

Sound Drum switches off automatically after 10 mins of playing. There's a glitch in the software for power saving feature. 

Due to the glitch, device turns off even if you're connect to bluetooth and playing music.

This can be fixed by upgrading the software of the device. Step by step process has been mentioned below for the upgrade.


Steps.

  1. Download this zip file (Download)
  2. Extract and copy the files on the root of an empty USB drive (formatted as exFat)
  3. Power on the speaker
  4. Input USB drive on the back of the speaker
  5. The speaker will update itself, and power off by itself (usually takes 1-3 secs)
  6. Remove the USB, and power on,
  7. Check running your device for more than 10 mins now... it won't turn off automatically now.


 

[Solved] Identity Server 4 caching not working issue

 

Hey guys, I've gone through some of the issue created on IdentityServer4 which were closed without proper solution.


"Issue: Identity Server 4 Caching is not working"

In simple words, it works like charm. If you know how the DI works then you even get this issue.


Here's a simple solution:

Make sure you add the below 4 store caching API at the end of identity store configurations.

What's the cause: If the cache DI is added before any other configuration then the Cache DI would be overwritten with the new DI.

.AddInMemoryCaching()
                .AddClientStoreCache<ClientStore>()
                .AddResourceStoreCache<ResourceStore>()
                .AddConfigurationStoreCache()
                .AddCorsPolicyCache<CorsPolicyService>();


Complete solutions:

Hope this solves your issue. 

Issues::: 

https://github.com/IdentityServer/IdentityServer4/issues/2191

https://stackoverflow.com/questions/51560620/caching-does-not-appear-to-work-in-identity-server-4

https://stackoverflow.com/questions/43858231/how-to-implement-caching-on-identityserver4

https://github.com/IdentityServer/IdentityServer4/issues/5007