Click here to Skip to main content
12,304,721 members (63,151 online)

Comments by Mike Barthold (Top 12 by date)

Mike Barthold 5 days ago View
   
That hint might come late - but always have a backup of your keystore OFFLINE (on a usb stick for instance) that is kept secure and far away of all OS-updates, file system changes, IDE updates, etc.
With this you can always get your "original" keystore back.

Unfortunately this will not help in your situation, because you'd have restored your keystore already if you had such a backup.
Richard Deeming is right. You can't.
Would make all keystores and security completely obsolete if you would be able to reinitialize a keystore with a new password without telling the old one first.
Mike Barthold 5 days ago View
   
if proguard is used right, it obfuscates your apk, so all your classes and methods are named like a.aa.aba.a(x,xx,xzzx) and no one can read it.
Also release-sign your apk with a keystore and private key. You need to do that anyway before you can put your app to the play store.

Please follow the guidelines by Google.
https://developer.android.com/studio/publish/app-signing.html
Mike Barthold 5 days ago View
   
https://github.com/tesseract-ocr/tesseract/wiki

Tesseract is the most widely used OCR software. Yes you have to compile it yourself but it is very very powerful (even Google uses it, as far as I know).
Mike Barthold 5 days ago View
   
Beside my approach of using an Asyntask below, I'd like to add that you are maybe just missing a .runOnUIThread call?
Looks to me as you have messed up some things in threading. What does the constructor of IceCream do? any UI/Handler/Message related stuff that needs to run in the UI thread?
Instanciate it in UI thread.
I hope I got it right :)
Mike Barthold 5 days ago View
   
Sorry, answering questions with xml content messed my answer up... the two xml files are corrupted.

in the first xml block (the progress dialog), this code is missing:


<ProgressBar
android:id="@+id/simple_progressbar"
style="?android:attr/progressBarStyleLarge"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:progressDrawable="@drawable/simple_progress_circular"
android:visibility="visible"
/>


</LinearLayout>

in the second block, only the closing tag is missing
Mike Barthold 3-Jan-16 12:11pm View
   
This looks like what I have been searching for - onTaskRemoved - didn't know the manifest flag so far - thank you very much!
Mike Barthold 1-Jan-16 6:16am View
   
Thanks for the quick reply :)
Unfortunately onDestroy on the Main activity does not help - it even gets called whenever Android thinks, it needs resources.
I need the point, where the "user" takes a "conscious action" of killing the app *now*.
I am not really sure, if this is possible in a way the product owners want it.
Mike Barthold 1-Jan-16 5:11am View
   
Why jdk8_65 and not 66? (Not, that it matters for your driver problem - just curious).

@Driver - Have you tried downloading the "original" directly from intel's website?
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager

One thing you can try is to check whether there are problems with other intel-services on your machine:
type win+r (run) - "msconfig" go to the "services" tab, click "hide all microsoft services" to have a shorter list and then look for the "Intel(R) dynamic application loader host interface service" - clear the checkbox from this service.
Reboot your machine and try to re-install - it worked for me.
(I had not exact your error message, but i DID have problems installing HAXM - so maybe diabling this service might help you as well).
My machine works without any noticable differences, whether this service is enabled or not.

cheers, mike
Mike Barthold 26-Dec-15 13:02pm View
   
Reason for my vote of 5 \n Thanks! Good, sweet and short listing
Mike Barthold 30-Sep-15 12:39pm View
   
Did you change the target framework to 4.6? Or still at 4.5?
Mike Barthold 11-Aug-15 15:58pm View
   
Reason for my vote of 3 \n A bit deep into win32 api for my taste, as it is a matter of a few minutes with wcf/pipes or plain pipes in .net

even a localhost udp would be a matter of less than 20 lines of code if you do not want to use pipes for whatever reason (but that would let the local firewall popup a dialog so it's not the way to go imho - users would ask what the program is sending... no need for that).

as a matter of compliance/code analysis -> microsoft recommended rules tell you to put those invoke declarations in a class named NativeMethods, SafeNativeMethods or UnsafeNativeMethods.

see rule CA1060 https://msdn.microsoft.com/en-us/library/ms182161.aspx
and the attributes assigned to those classes - so consider to place them properly.

BR mike
Mike Barthold 5-May-15 2:07am View
   
Reason for my vote of 5 \n Good read - I agree with most of your statements.

I only would add that XML Comments that are only auto-generated (by GhostDoc for example) and not even grammar-correct can also be a mess if the developer has nothing more to say.

But even I try to comment 100% of the public visible properties for the sake of tooltips and intellisense. (And I *do* generate my wiki pages from the xml-comments so mine are often more content-intensive and contain all the and tags and even :)

But I have seen many bad examples for xml-doc too out there...
If you comment something, the DO IT RIGHT. not half-hearted.

Advertise | Privacy | Mobile
Web01 | 2.8.160530.1 | Last Updated 1 Jan 1900
Copyright © CodeProject, 1999-2016
All Rights Reserved. Terms of Service
Layout: fixed | fluid