If you experience similar problems as many other users of Meizu here : https://issuetracker.google.com/issues/111465510 , I just tried this “poor man fix” and it seems to work on my device.
1. On this link http://en.miui.com/thread-309446-1-1.html – 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 – https://en.miui.com/thread-4783894-10-1.html, 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:
PS: BuildProp Editor requires root access.
Thanks everyone that found out and let us have our phones back + shame on you Xiaomi.
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.
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.
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 – https://www.sno.phy.queensu.ca/~phil/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 :)
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 :
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) :
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 :
All requests from that point will get 200.
Hope this helps guys.
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 : https://azure.microsoft.com/en-us/blog/using-app-service-web-apps-continuous-deployment-with-github-organizations/ 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 :
but Authorized OAuth Apps is now the tab where you should go.
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):
Now in http://portal.azure.com you could see something like this :
I just ported my blog to Microsoft Azure and I would like to say I am sorry to all linkers from my previous sub domain blog.rostacik.net, but I can’t redirect any of the old links to my current links.
The reason is simple – Azure still does not support second level sub domains in 2017.
More on the topic here : https://feedback.azure.com/forums/169385-websites/suggestions/7026845-support-double-wildcard-custom-domains
Shame on you Microsoft….
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) –
- Modal window will appear where you can click Settings and you are good –
Plan B is to change setting during call :
Hope this helps.
We had a small problem I would like to share today. We have Windows 2012 R2 with Jenkis as one of means to build our stuff (I know, W2012 man… others in our company use different CI systems and there was also some other reason for W2012 R2, but if I had the choice I would definitely pick some newer OS).
Some days ago, our IE tests started to fail. The reason from Jenkis : Timeout. Wait, what? We didn’t changed anything in the build and test process!!! Indeed there were code changes but no one touched the build pipeline.
After short investigation, the reason to this was quite simple (as always) :
It seems like there was some update that changed IE or touched it’s settings and it wanted me to confirm security setting when I ran tests from my account.
Something like this :
OK, let’s suppose that IE timeouted for the same reason on Jenkins job. But Jenkins runs as service, as special privileged Local System Account. How can I run IE like this account?
This link helped : https://marckean.com/2010/12/17/run-internet-explorer-as-the-local-system-account/
You need to :
- download PsExec from this URL : https://technet.microsoft.com/en-us/sysinternals/bb897553
- execute this command : psexec -s -i “%programfiles%\Internet Explorer\iexplore.exe”
- IE will open
- make IE happy
- close it
- never touch it again
The tests should be good again :)
Thanks to the author of aforementioned blog for this time saver.
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 – https://github.com/StyleCop. 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 https://github.com/DotNetAnalyzers/StyleCopAnalyzers 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.