Showing posts with label sensor. Show all posts
Showing posts with label sensor. Show all posts

10 April 2015

Doms diagnostic tools v5.3 released!

Doms diagnostic tools
v5.3


 You can download from here:

I added support for new version for Android and fix 

CHANGES:
  1. add support for Android 5.1 and all screen
  2. update battery info
  3. fix keyboard issue
  4. fix nfclab appear in menu
  5. fix bt issues
  6. clean a code and various refactoring

Twitter: 
Blog:

8 March 2015

Doms diagnostic tools v5.2 released!

Doms diagnostic tools
v5.2

 You can download from here:

I am focus on improvements of existing tests and add new information 

CHANGES:

  1. add more informations in general info in informations
  2. add more information in telephony info in informations 
  3. minor improvements
  4. fix minor bugs



3 March 2014

Doms diagnostic tools v4.4 released!

Doms diagnostic tools
v4.4

 You can download from here:

Fix some bugs

Changes:

  1. # fix java.lang.IndexOutOfBoundsException
  2. # fix problems  with General Info 
  3. # flashlight bugs
  4. # vibration UI issue
  5. # fix minor fixes

19 February 2014

Doms diagnostic tools v4.3 is released.

Doms diagnostic tools
v4.3

 You can download from here:

Improve UI and add few little things

Changes:
  1. Add stereo to audio test
  2. Simplify UI (however work still in progress)
  3. improve results information on the end of test
  4. Fix few ANR issues (however most of them are unresolvable as problems was caused by Android OS issues).
  5. Fix java.lang.IllegalStateException issue in Audio Test
  6. Fix java.lang.NullPointerException in Sensor Scanner
  7. wifi Scanner
  8. add warning about brightness
  9. Summary contains information from General and Phone Info
  10. improve mutlitouch
  11. clean code and other minor fixes

19 November 2013

Doms diagnostic tools v4.2.3 is released.

Doms diagnostic tools
v4.2.3

 You can download from here:

Quick bug fix release .As user loves switch off screen and panic,so i decided to add automatic solution

Changes:
  1. brightness back to medium brightness when user left brightness test(so even,if user switch off lights,it can recover from this mistake : ) .Thank you Steve for feedback.

9 November 2013

Doms diagnostic tools v4.2.2 is released.

Doms diagnostic tools

 You can download from here:

This is an improvement  release.I focus on improve stability of application and feature like jack plug detection..

Changes:
  1. add detection for Android 4.3 and Android 4.4
  2. add wifi scanner
  3. detection of sqllite version used on your device
  4.  improve wifi test 
  5. Jack plug detection
  6. update admob
  7. update appBrainImprove battery information
  8. remove unused code
  9. add GPS Test to full diagnose.Thanks to Diaman Z for feedback
  10. fix minor bugs
  11. add commander,so some user can run experimenal feature

8 July 2013

Doms diagnostic tools v4.2.0 is released.

Doms diagnostic tools


This is a quite big bug fix release.I focus on improve stability of application and some improvements 'behind the scenes' to improve overall functionality.

Changes:
  1. Update AppBrain
  2. Update about me.
  3. Improve brightness test
  4. Major redesign , refactoring  behind the scenes (for stability and improvements reasons)
  5. Application can be install internal storage only.
  6. Fix shameful android.util.Log$TerribleFailure 
  7. Fix minor bugs, correct mistakes and etc.
  8. Advice for temperature appear only,if temperature sensor is on device.(before it always displayed)
  9. Few fixes for wifi test.I temporary blocked remove all wifi networks ,but they will back in next release
  10. Add admob

9 July 2012

How to solve problem NoSuchMethodError for Sensor.getMinDelay() ?

you wrote a awesome app that using sensor and method getMindDelay() ,but when you test on various devices ,then you notices that .... on some devices,it crashes and on some not.
You see error which looks more less like that:

java.lang.NoSuchMethodError: android.hardware.Sensor.getMinDelay
 at dms.pastor.diagnostictools.activities.diags.ProximitySensor.doMagic() at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1069)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2751)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2803)
at android.app.ActivityThread.access$2300(ActivityThread.java:135)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2136)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:144)
at android.app.ActivityThread.main(ActivityThread.java:4937)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(Native Method)

Problem:

This method is supported from SDK 9(Android 2.3) and above,so if you run app in Android 2.2 ,then you will see above exception.

Solution:
Use if else statement using  Build.VERSION.SDK_INT

if(Build.VERSION.SDK_INT >= 9) {
  minDelayValue =  String.valueOf(epicSensor.getMinDelay());
}else{
  minDelayValue =  "You are using an ancient Android ,LOL";
  }

Source:
http://developer.android.com/reference/android/hardware/Sensor.html#getMinDelay()