Category Archives: How to

How to fix Xiaomi Redmi Note 2 Google sync problems

If you experience similar problems as many other users of Meizu here : , I just tried this “poor man fix” and it seems to work on my device.

1. On this link – download tools and root your phone. There is maybe 1 small thing to note. When you restart your phone to Fastboot (via volume down + power button), you must connect your phone with USB cable and then run the .bat file. (indeed, if you are power user and already have root, skip this)

2. In this thread –, there is a discussion about how to fix the problem. For me these steps worked :

1- Download & Install BuildProp Editor
2- Go to menu > + New
3 – add these two properties:

Name: dalvik.vm.dex2oat-filter
Value: interpret-only

Name: dalvik.vm.image-dex2oat-filter
Value: speed

PS: BuildProp Editor requires root access.

Thanks everyone that found out and let us have our phones back + shame on you Xiaomi.

Visual Studio 2017 update 15.9.0 – Package ‘Microsoft.Azure.Storage.Emulator.Msi, version=5.7.0’ failed to install.

Yesterday I had the pleasure to install latest update of VS 2017 15.9.0. Unfortunately at the end I was notified about minor problem I reported here :

The problem with solution is, that I had nothing more running on my machine (I installed after hours, at home, not to trash bandwidth at work) and that the solution was for a different package. MS guys closed the problem tagging it as duplicate and pointed me to older error report that is closed with result : its already fixed. Thank you MS, very helpful!

While looking at the error, you can see this path :


I was looking for the package all over the internet, but I was not able to find standalone installer of Microsoft Azure Storage Emulator with version 5.7.0 (maybe just me and there is a common place to find all these packages).

But, if you peek in this folder (with version number at the end), you should be able to find installer there, yay!!!
You won, if you have the problematic installer and can install it by hand :)
Hope this helps.

Kde nájdem informáciu o zvyšnej veľkosti predčasnej splátky bez poplatku v internet bankingu mBank

Chcel by som sa s vami podeliť o jednu drobnosť (iste ide len o glitch) v UX IB mBank ktorá sa zhodou okolností vyskytuje na mieste, kde by ste ju najmenej čakali. Hádate správne, na mieste zistenia výšky sumy ktorú ešte môžete splatiť do konca aktuálneho výročia. V mBank totiž podľa aktuálnych pravidiel môžete splatiť 20% istiny ročne.

OK, takže without further ado, hľadajte tu :

v sekcii Detaily o účte musíte kliknúť na UX element ktorým sa zväčša reordrujú items v liste (červený rámček).

Hľadaný údaj nájdete ako posledný v liste.


How to convince Facebook to display your panorama pictures like 360 ones

Facebook for some time now has the possibility to upload and display your pictures as 360 ones. But you don’t need to have 360 photos from some special HW camera. All you need to do is to make a big enough photo and tell Facebook to display the photo as 360 one.

I am not sure about the minimal size of picture that could be displayed as 360 but all my old panoramas were OK when I tested.

I found not much relevant articles about this problem but here is one from FB itself that will explain much.

Tool you need :

exiftool –

How to :

exiftool -Make=”Apple” -Model=”iPhone 6s” your_photo.jpg

This will add EXIF information to the file, claiming it was created by iPhone with model iPhone 6s. Now I haven’t really investigated about models that are fine for FB. I suppose from before mentioned FB page, FB would be also fine with some 360 camera makers EXIFs.
It is really funny that pictures that are OK in all ways are not displayed as 360 just because of this EXIF.
Maybe some day we will get a checkbox to display our pictures as 360 from some size.

Hope this helps somebody :)

Don’t forget to Automatically Authenticate calls when using Fiddler

I tend to forget some simple things I just don’t use that often.

One of these is when working with some ASP.NET apps which are using Windows Authentication with 401 HTTP Challenge (Kerberos) set like this in IIS manager :

asp dot net iis windows auth sample

For bigger HTTP debugging “jobs” I am using Fiddler, as most of us do. So, if you want to forge a new HTTP request in Composer and see something like this (401 in the lines 14-21) :

calls without automatically authenticate

You clearly need to check Automatically Authenticate in Composer Options tab.

So what do we see here. This is a random session on my dev box. My browser undergo 401 challenge in the step 1 and 2. From there, everything had 200 because we are authenticated. This is done by the browser, “automagically”. I drag and dropped POST request on position 12 to Composer and not checked Automatically Authenticate (I forgot to) and I got all those nice 401s from 14 to 21.

Please note, that even if you drag and drop some request from browser that got 200 from IIS,  the Fiddler will not get 200 also. Fiddler is for IIS just another client, just replaying the very same request will not make it authenticated. This is by design, not a bug.

If you allow automatically authenticate, you will see that you will get 401 at first, but Fiddler will do it’s job and issue another request, which will get 200 this time. Something like this :

calls with automatically authenticate

All requests from that point will get 200.

Hope this helps guys.

Using Azure App Service Web Apps continuous deployment with GitHub organizations

I am using happily deployments from GitHub to Azure functions, but I wanted to use a repo I have in another Organizations collection.
I came across this article : which is currently just partially true, because GitHub UI changed a bit.

In Installed GitHub apps where the Azure Management Portal app should be I see 0 apps :
installed github apps

but Authorized OAuth Apps is now the tab where you should go.

authorized oauth apps

and clicking on the name of app (Azure Management Portal) you will now see a list of your organizations that could be granted to be listed in your account (here I already granted access for one ogranization):
github granted permissions

Now in you could see something like this :
azure github with organizations

Where to find audio settings for Skype built into Windows 10

I will just leave this small “note to self” here also for others to ease their pain.

Find out where to change audio settings in built Skype in Windows 10 is not as easy as it looks like.

So here are the steps :

  • Click on your icon in the top left corner (alternatively you can use CTRL+I) – skype_w10_icon
  • Modal window will appear where you can click Settings and you are good – skype_w10_settings

Plan B is to change setting during call :


Hope this helps.

How to run StyleCop as opt-in feature with msbuild from command line

The tool :

So everyone knows wonderful tool from Microsoft, named StyleCop. StyleCop is a tool that runs against C# code (not against IL assemblies – already build code) and based on rules saved either per machine, or per project (we will show us how to save them per project) gives you feedback , if you violated some of these rules. StyleCop started on codeplex (MS take on similar portal like github) and currently moved to GitHub – If you see closely, on GitHub we have two projects :

We will go down the free path and take a look at first option. There are two plugins I will speak about today :

(please note that in StyleCop repo there is a note about recommendation to use Roslyn based StyleCop from repo)

So, you can add NuGet StyleCop.MSBuild package and now running msbuild from command line will trigger analysis. Which is what we want on CI server, but not for builds from Visual Studio. You can try to run build from VS and see what happens.

How to turn off StyleCop.MSBuild for VS builds :

After some search on the interwebz I found out, that there is a property StyleCopEnabled in StyleCop.MSBuild.Targets that is set to true if nothing is specified, which we need to set to false as default. So you need to edit your .csproj (or any other .proj file) and insert


in some PropertyGroup.

This will enable you to do following thing :

  • run msbuild to trigger just plain old build
  • run msbuild  /p:StyleCopEnabled=true to pass parameter to msbuild that will do the analysis after the build.

If you guess that the first will be “used” when building from VS and second to get analysis on your CI server, you are right :)

And if you questioned yourself, “why not to pass  /p:StyleCopEnabled=false” from VS build, then AFAIK from VS also in 2017 we cant just pass parameters to msbuild. Shame, I know.

How to handle async functions inside constructors in TypeScript

In this post we will discuss some options you have with calling async functions in constructor of your TypeScript classes.

So, first of all – why would you do this? Well, maybe you need some data from a web API to fill the object with data, or you need some input from user, or some API in code from a colleague is async. Reasons may vary, but the problem is still the same :
in TypeScript, you can’t have await statement in constructor, because constructor returns instance of object, not Promise<yourObjectType>. (All of this indeed is tied to current version of TypeScript 2.2. maybe in future with native async/await keywords in JS, things will change).

So, possible solutions depend on what happens in your async functions and if you need results from this call / calls at the time you return the object.

Solutions :

1. Try to avoid async stuff in constructor. As said earlier, constructor is a function, that should initiate the object in some way and return it immediately, not return a promise that has to be awaited. That is considered a bad practice and TypeScript doesn’t allow this. More on this problem here

So in some sense, need for async stuff in your constructor might be considered code smell, you are doing too much in constructor. Refactor your code.

2. If you want your async code to stay in constructor for some reason, do you need results from async calls? If not and you want to call them and let them just execute, you might consider calling async functions without await. In this way you will unfortunately be unable to receive (await) the result from these calls (values passed back via resolve).
Please note, that this might result in some non deterministic issues because of how JS handles async code and I really don’t recommend this. Also another downside is, that if you would wrap everything inside constructor with try, promises that would be rejected (analogy with throwing exception in async sense will be not caught but become unhandled exceptions).

Your constructor might then look like this :

class SomeClass1 {
  constructor() {
    getConfirmAsync("1 - 1");
    getConfirmAsync("1 - 2");
    getConfirmAsync("1 - 3");

Sample with try/catch block might look like this :

class SomeClass2 {
  constructor() {
   try {
   } catch (e) {

No awaits means that code will continue to run and your constructor will finish and hand over new instance of your class sooner than code triggered from constructor will finish its execution. Scary, right? Don’t do it!!!!

Another take on this same approach is to leave an async self executing function in constructor like this :

class SomeClass3 {
  constructor() {
    console.log("SomeClass3 - entry");
      (async () => {
        try {
          await delayAsync(3000);
          await delayAsync(1000);
          await delayAsync(2000);
        } catch (e) {
          console.log(`catch triggered with exception ${e}`);
      console.log("SomeClass3 - exit");

Again, object would return from constructor but it would still lack calls to all async functions but this time, with proper async function, await and try/catch will work. So if for some reason first function would throw, all the others will not be hit (you can try to change the first call from 3000 to 2999 and see the results). Again, this is not recommended!

3. Simple “factory” function :

This is a way you might potentially want to go because it’s the safest one. All calls will be awaited and instance of you class will be in the state it should be.
All logic from constructor would have to be removed and stored in function that will have the logic of preparing object to the right shape. But, it is OK to separate the logic of creation from class to different function/files that knows what to do to make the object “right”?
Also you might want for safety reasons to “hide” somehow the class itself to prevent from instantiation without the factory function.
This could be done by exporting (from module) only interface of the object and “factory” function and not the class itself. Downside is, that all functions that are called in “factory” function need to be also public because “factory” function is not inside the class itself, but it is a separate function.

//exporting interface so we can work with the object outside
export interface ISomeClass {
	stringPublic: string;
	numberPublic: number;
//not exported = not visible
class SomeClass implements ISomeClass {
	public stringPublic: string;
	public numberPublic: number;
	private somePrivateFn() {
		console.log("this is private fn");
export async function createSomeClassAsync(): Promise<SomeClass> {
	let res = new SomeClass();
	await delayAsync(1000);
	await getConfirmAsync("1");
	await delayAsync(3000);
	await getConfirmAsync("2");
	await delayAsync(2000);
	res.numberPublic = 1;
	res.stringPublic = "aa";
	// res.somePrivateFn(); since we are not inside function this would fail
	return res;

This is TS that has export and import statements, but in my examples on GitHub I have this implemented without export and import. I can make a sample for you that is using modules (like the one above) but I decides to cut complexity for my readers and not use any bundling tool like webpack or browserify (I recommend webpack over browserify but that is just a matter of taste).
5. You want to hook a browser event inside the constructor , like some ready event or some other that will trigger some async functions once it happened.

Your constructor might look like this :

function ready(fn) {
    if (document.readyState !== "loading") {
    } else {
        document.addEventListener("DOMContentLoaded", fn);

class SomeClass {
    constructor() {
        console.log("SomeClass5 - entry");
        ready(async () => {
            try {
                await delayAsync(3000);
                await delayAsync(1000);
                await delayAsync(2000);
            } catch (e) {
                console.log(`catch triggered with exception ${e}`);
        console.log("SomeClass5 - exit");

I am using a helper function from to avoid adding jQ to the project, but you get the point.

If my samples doesn’t make sense for you, please to to my GitHub repo, you can find all the code I made as examples can be found there : .

If  you have TypeScript installed as global npm package, just type


in the root. If you dont have TypeScript installed, you just need to do to install npm packages :

npm install

and run TypeScript compiler to build all .ts files :


Feel free to ask or discuss in the comments :)

How to filter particular TypeScript errors in build result

Hi interwebz.
I just want to share this short poor man’s fix when migrating TypeScript to filter out some particular errors in TypeScript build.

Why the hell you (might) need it?

So what would be the common use case , why to bother mask/mute errors on build? Compile is the first test our code need to undergo, like first pass of “unit tests”.

Our situation : currently we have a lot of .js files that let’s say most of the time worked and we need to iterate on way to migrate fully from JavaScript only to TypeScript only. So we rename .js to .ts and then we ran into errors like (among others) :

  1. error TS2365 Operator ‘>=’ cannot be applied to types ‘string’ and ‘number’.
  2. error TS2365 Operator ‘==’ cannot be applied to types ‘string’ and ‘number’.
  3.  error TS2345 Argument of type ‘number’ is not assignable to parameter of type ‘string’.

Yes indeed these are against the “logic” of TypeScript – bring types to JavaScript. But I know I want it there for some short timespan. Just to test. I don’t want to wade through 1500 same errors I know I will have to fix, but among them TypeScript also tells me big and real problems, but buried under many same errors about types.

We are not alone in this, more ppl write about it here :

and also here

Solution :

So the solutions vary from custom branch of TypeScript as such to stupid grep on the command line output. And since I am on Windows 10 (my dev box) , I chose to stick with PowerShell so this is snippet that should do the job.

Lets say we want to mute TS2365 and TS2345 errors and your TS build gulp task has name someTSBuildTaskName.

PS script – output to some file :

node .\node_modules\gulp\bin\gulp.js someTSBuildTaskName --color | Select-String -NotMatch "TS2365" | Select-String -NotMatch "TS2345" | Out-File "grepts.txt"

PS script – output just to console (just drop the last part after pipe) :

node .\node_modules\gulp\bin\gulp.js someTSBuildTaskName --color | Select-String -NotMatch "TS2365" | Select-String -NotMatch "TS2345"

PS: I am calling here the gulp task without gulp installed with -g flag (global) so you can just call

gulp someTSBuildTaskName

with globally installed gulp and you are also good to go.

Found any better solution? Pls let us know in comments! :)

AD: you can also use this console log parser on Jenkins:

Regular Expression :


Mapping Script :

import hudson.plugins.warnings.parser.Warning

String fileName =
String line =
String category =
String message =

return new Warning(fileName, Integer.parseInt(line), "TS Error", category, message);

and plug this into your build pipeline.