- Enable bluetooth debugging on watch (tap build number 5 times to enter developer mode)
- Enable bluetooth debugging in Android Wear app on phone
- cd ~/Library/Android/sdk/platform-tools
- ./adb forward tcp:4444 localabstract:/adb-hub
- ./adb connect 127.0.0.1:4444
Alexey Rudakovsky's Weblog
Saturday, 26 March 2016
Connect Android Wear device via adb over Bluetooth
Sunday, 17 August 2014
Solution to INSTALL_FAILED_INSUFFICIENT_STORAGE on Android
Since upgrading to KitKat I often face the problem which prevents me of installing or updating my apps:
Here is how I cope with it. I clear the cache of media via ADB:
INSTALL_FAILED_INSUFFICIENT_STORAGEThis error may occur even when there is more than 400 MB free on internal memory of my phone.
Here is how I cope with it. I clear the cache of media via ADB:
adb shell pm clear com.android.providers.mediaNotice: negative effect will be loss of thumbnails, ringtone, etc..
Wednesday, 21 May 2014
How to boost your mobile app reviews
It is always challenging to keep high user rating of your mobile app.
Satisfied users are reluctant to give you five. At the same time disappointed users are eager to spoil your app's rating with shitty star. Often with no comments at all..
I'd like to share my experience of fixing this issue by asking happy users to give app review at the right time.
Let's take this simple game called "Eatables?" as an example. A set of pictures will be shown. User has to decide if they are eatable or not. Goal is to make as many right decisions as possible. Game is over after 30 seconds or when you fail 3 times. Game measures user's speed of making decisions and gives ability to share highscore with friends.
You are struggling to make your app better, you are attentive to user reviews, you improve functionality and try to deliver better user experience. But nevertheless if you see your app rating decreasing and you think that it is not fair then you can feel may pain.
How can we guess which user is satisfied? When shall we ask to give our app a review?
My hypothesis to be tested: when user gets achievement it's likely to receive positive feedback.
In my case there is some score threshold. Let's say 30 points which is equal to speed of making one decision per second. User has to invest some time to develop such quickness. Thus I expect him to feel satisfaction on reaching this target.
Is it the right time to prompt?
My experiment shows that users feel comfortable to support developers taking a moment to rate app on this kind of trigger. Keep in mind not to bother with this twice. At least once per version.
Here is statistics of rating highlighting the date of deploying release with this app review prompt plugin.
Also installs growth can be observed.
Satisfied users are reluctant to give you five. At the same time disappointed users are eager to spoil your app's rating with shitty star. Often with no comments at all..
I'd like to share my experience of fixing this issue by asking happy users to give app review at the right time.
Let's take this simple game called "Eatables?" as an example. A set of pictures will be shown. User has to decide if they are eatable or not. Goal is to make as many right decisions as possible. Game is over after 30 seconds or when you fail 3 times. Game measures user's speed of making decisions and gives ability to share highscore with friends.
You are struggling to make your app better, you are attentive to user reviews, you improve functionality and try to deliver better user experience. But nevertheless if you see your app rating decreasing and you think that it is not fair then you can feel may pain.
How can we guess which user is satisfied? When shall we ask to give our app a review?
My hypothesis to be tested: when user gets achievement it's likely to receive positive feedback.
In my case there is some score threshold. Let's say 30 points which is equal to speed of making one decision per second. User has to invest some time to develop such quickness. Thus I expect him to feel satisfaction on reaching this target.
Is it the right time to prompt?
My experiment shows that users feel comfortable to support developers taking a moment to rate app on this kind of trigger. Keep in mind not to bother with this twice. At least once per version.
Here is statistics of rating highlighting the date of deploying release with this app review prompt plugin.
Also installs growth can be observed.
Friday, 13 April 2012
Enable logging for java application in Google App Engine in order to use console
Configuring java.util.logging in appengine-web.xml is not enough.
You have to specify a log level for your package. For example:
/war/WEB-INF/logging.properties
# Set the default logging level for all loggers to WARNING
.level = WARNING
com.rudakovsky.smoke.server.level = INFO
You have to specify a log level for your package. For example:
/war/WEB-INF/logging.properties
# Set the default logging level for all loggers to WARNING
.level = WARNING
com.rudakovsky.smoke.server.level = INFO
Rolling back your Google App Engine deployment
If you failed to deploy your app to GAE successfully (i.e. lost connection while uploading) you can recover it using a rollback option:
java -cp "<path_to_jar>\appenginetools-api.jar" com.google.appengine.tools.admin.AppCfg rollback "<path_to_project>\war"
then enter your email and password
After that you can try to deploy your app once again.
java -cp "<path_to_jar>\appenginetools-api.jar" com.google.appengine.tools.admin.AppCfg rollback "<path_to_project>\war"
then enter your email and password
After that you can try to deploy your app once again.
Sunday, 1 April 2012
Timezone GAE issue
Failed to start Google App Engine in Eclipse after updating java to 1.7 - timezone issue. Returned to java 1.6
Subscribe to:
Comments (Atom)




