Shamil's Blog. Software Engineering Processes, Android, CI, Devops.

Here's what I use for android instrumented tests pipeline: project with Android emulator in Docker image with VNC access. This is new variant of less convenient one (it was forked from Agoda). It wasn't nice to use, but gave me good example. This one is better. Usage:

$ make build-base && make build && make start

. This provides emulator device waiting to run your tests.

PS I am not a big fan of building in docker, however it's possible using avd-base image from same project. I will cover this later.

Labels: android, docker, emulator

It's a surprisingly common belief of using one ViewModel class in several views (screens) in modern Android Jetpack-based MVVM architecture style. In reality ViewModel cannot be shared. There're lots of arguments against reusing ViewModel. Most obvious one is that it mixes data processing logics of different screens which increases complexity of implementing and testing of ViewModels.

Do not create huge ViewModels, keep it simple. Yes, it's more classes per view, however your support and development costs are closer to linear in time.

Labels: android, architecture, mvvm, software architecture, view, viewmodel

Project repository. For how to install app see below "How to install app" section.

WhatsThat app privacy policy:

No user data is collected by app.

P.S. Actually it's completely offline app: contains no networking code at all.

Project summary

Summary of what's done is below, also see (more in repository readme):

• Android app in kotlin with MVVM and JetPack, TensorFlow image classifier for CameraX preview.
• Tests: unit (Robolectric JVM-based) and instrumented (uses Android emulator to run).
• Repository: Gitlab with safe workflow: development is done in feature branch, merge requests to master with Build/Test CI pipeline checks before able to merge to the master branch.
• CI: Gitlab integrated with Jenkins. Build is executed for any push to feature branch.
• Project tracking: Jira with Kanban. All commit messages are automapped to Jira tickets using "smart commit messages". Merge of MR leads to automatic Jira ticket state change (move to Done)
• CD: publishing is done to Artifactory (artefacts repository)
• Set up separate Jenkins slave to run project tests which require Android emulator for instrumented testing.

For my own projects I sometimes use non-standard coding conventions for XML (indents = 2 + special attributes order), and some for Java/Kotlin (indent = 2). However for team workflow I believe it's better to use a standards if there's no team decision otherwise. Also for larger teams >5 people it's better to always stick to standards (helps onboarding).

How to install app

• How to test: send me google account email to be added to internal testing group. Once confirmed a link will be sent and app can be installed. (Sorry for inconvenience, it's Google Play rules).
• How to install (for hackers: developer settings must be enabled and unsafe unknown sources installs option enabled there): download file, add .apk extension and upload to phone with adb install release.apk. Link to the latest master build: in Artifactory.

Update 10 Dec:
- Implemented unit and instrumented tests
- Added unit test to CI pipeline
- Started adding dockerized android for instrumented tests (problem: server does not provide /dev/kvm, so emulator needs to be tunes to use ARM system image)
- Added user to Jira, Jenkins, Artifactory. Will share credentials tomorrow in a task report.
- Todo: Add Jenkins-slave with kvm to run instrumented tests.
Update 9 Dec: 
- Added MVVM with Jetpack to easily bind image classification with UI output
- Added dagger2 to more simple load of components
- TensorFlow model now works fine
- Project repo: https://gitlab.gotalkmobile.com/shamilg1/image-classifier
Update 7 Dec: 
- Added Jira/Gitlab/Jenkins/Artifactory integrations and set up CI pipeline with CD to Artifactory.
- Added planned tasks to Jira (Kanban-based).
- Basic kotlin CameraX implementation is done.
- Tomorrow todos: set up basic quantized image analysis integration and further experiment with models.

5 Dec 2019. I've got assignment for the interview with a nice startup on ML image classification using existing pre-trained model. The aim of this project is to share my skills and experience in dealing with project, specifically an Android app.

Labels: android, artifactory, dagger2, docker, espresso, interview assignment, jenkins, jetpack, jira, kotlin, machine learning, mvvm

Upgrade involves:

1. dependency versions chain upgrade: studio -> gradle plugin -> kotlin version
2. solving mysterious problems with desugaring D8 (add "android.enableD8.desugaring=false" to gradle.properties)

I'm not very happy when I'm unexpectedly forced to spend 3h+ on infinite chain of tasks. This repeats itself for most of the Android Studio upgrades.

Labels: android, android studio, kotlin, upgrade

In case while building there's flood of "symbol not found: DataBindingComponent" errors (which are fake), try to increase max number of errors with adding javacOptions after dataBinding into app gradle file:

    dataBinding {
        enabled = true
    }
    kapt {
        javacOptions {
            // Increase the max count of errors from annotation processors.
            // Default is 100.
            option("-Xmaxerrs", 500)
        }
    }

Labels: android, build, data binding, databinding, error, gradle, java, kotlin

In order to fix it open Settings -> Window Manager Tweaks -> Focus tab -> select the Do nothing (When a window raises itself)

Labels: android, emulator, gui, linux, UI

Recently I don't see almost any diagrams in software docs. It seems like the nowadays developers cannot also create any ascii-graphics like this BufferStrategy class doc written 10+ years ago. None of such I've seen in Android docs (point me out to any please?).

Moreover some talented developers seems don't want to document at all. Check out this one, very complex UI behaviour class AppBarLayout.Behavior. It says: "The default AppBarLayout.Behavior for AppBarLayout. Implements the necessary nested scroll handling with offsetting." That's all. What exactly is necessary?

Yes, I've heard many times that mantra of idlers "code source is the best documentation for itself". Without docs it requires sometimes hours or even days to know all the nuances of implementation. In total it requires additional man*years if some popular framework is poorly documented and decreases overall experience of developers and users for using such piece of technology.

So my friend, let's start documenting the sources we write with something more than the usual "f%ck off I'm busy"-style docs and comments that we see in so many docs by adding the details of implementation and side effects. And diagrams!

Labels: android, API, computer science, diagram, docs, documentation, framework, programming

Last week I downgraded Google Play using "Uninstall updates" button (on android ver 2.3.4), so I got fast Market app back (v. 2.3.4). Old Market app worked good and installed apps without problems, but when I needed to test In-app-billing, it for sure did not work :-) (Google requires ) So I tried to force it autoupdate (usually Market and Play apps updated automatically). I even installed all-hated Google Services Framework and Play Services, hoping that they will help Market to autoupdate. They did not. I followed recommendations to clear Market cache and data, but it only cleared list of "My apps". $%$#$&!

So the only way was to manually update Market to Play. As this is original apk signed with Google keys, all went OK. IAB working now.

Labels: android, autoupdate, downgrade, evil, framework, google, market, play, services, update, upgrade

If you have same main account on more than one android device, C2DM delivery will only work for last logged in device (seems that google acc logon happens on system restart). This is a problem for testing park devices for which is hard to create and support unique google accounts :-(

Labels: android, c2dm, google, opensource, push, shit

Just another bookmark:
http://developer.android.com/resources/samples/ApiDemos/src/com/example/android/apis/animation/Rotate3dAnimation.html

http://stackoverflow.com/questions/3452687/better-implementation-of-rotate3danimation-in-android-viewflipper

Labels: android, bookmarks, java, ui

just a bookmark for myself
http://www.helloandroid.com/tutorials/progressbar-updating-using-message-handler

Labels: android, bookmarks, java, links

Please note that I've tested this XML patch only for russian hw keyboard.

FN-keys in cyanogen-mod are awful (especially on russian version kb) and no fix from xda-developers forum works!
So I've finished manually edited english layout file (FN-keyboard section) which you can download:
qwerty-en.xml
You should move it using root explorer to

/system/usr/keyboard-config/layouts/

then change owner to root (id=0) and group to root (id=0) and change permissions to RW-R--R-- and restart phone.

Don't forget to backup original file and, by the way! I'm not responsible for any side effect ;)

Labels: android, fix, keyboard, mini pro, sk17i, sony ericsson, xperia

This is not full coverage nor review, just some key impressions just for me.

Windows 7 phone (Lg E900):
- ugly ui, but surprisingly very useful :-) usability on high grade, seems designers were not allowed to give any recommendations :-))) This is the way, ppl!
- Very small number of apps: does not have any ssh/telnet terminal in marketplace
- search in marketplace gives artists, songs and albums instead of APPS! go to hell with all that paid bad music :-) i can make noise myself on guitar :)))

Android (HTC G1, HTC Desire Z):
- [android all] every app want access to everything (no way to manage permissions as it is for J2ME)
- very small (desire z) text
- it is not phone, nor SMART: messaging takes TIME to load! Every simple phone (from nokia 1100 up to sony ericsson k750) loads sms inbox very fast, to call one just start typing number. But in android you first FIND phone app... then wait it to load :-) suxx
- samsung galaxy tab: it HAS GPRS via SIM card, but does not have phone app and no way to install it without root-ing and firmware replace.
- Android officially is open-source, but very closed still (no access to ussd, no way to install native apps without rooting)
- by the way, every app with permission for messaging can read ALL incoming sms!
- NO GOOGLE EARTH FOR GOOGLE PHONE?! WTF!

iPhone:
- same as android trouble with finding 'phone' app, slow messaging load
- good screen for iphone 4 (ips matrix)
- closed proprietary platform: recently apple stopped posting security updates to iphone 3G. "Don't hold it..." ...anymore. Buy new one?!

Labels: android, iphone, mobile, phones, windows 7 phone

--
Update: this works until device disconnect only. After reconnect IDE could hang up :-)
Update: added string for HTC Desire Z
--
Ubuntu 10.04/android sdk 7(9? where the f%%k is sdk version? no version in readme! opensource sometimes is such an opensource.)

When you see such f%%% sh%%%:

./adb devices
List of devices attached
???????????? no permissions

To be able to deploy to samsung galaxy tab do the following:
1) create new file (51 is just some number below 99):
sudo vi /etc/udev/rules.d/51-android.rules
and put there:

SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

04e8 is samsung id
18d1 is for HTC Desire Z
2) restart adb daemon:
sudo ./adb kill-server
sudo ./adb devices
you now should see this:

* daemon not running. starting it now on port NNNN *
* daemon started successfully *
List of devices attached
10001c18352d device

If above still doesn't help add more detailed description for usb device in 51-android.rules like this

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c91", MODE="0666"

here 0c91 is the HTC Desire Z product id. You can watch these details using 'lsusb' command:

Bus 002 Device 011: ID 0bb4:0c91 High Tech Computer Corp.

Labels: android, desire, desire z, galaxy tab, htc, linux, opensource, samsung, shit, ubuntu, уебунту

When I put another operator's SIM card into G1 immediately I started to receive strange SMS (every minute!) from short number 684 with text "Service is temporarily unavailable". A little investigation shows that 684 is operator's aggregation paid short number (operator provides some paid SMS services via that number). More: any outgoing SMS to that number cost $0.16.
So, G1 usage cost $0.16 per minute.
It's of course not so bad as downloading Android updates via 3G (which ate 5$ in 3 minutes for me when I first switched G1 on). But: sending some SMS to network without my permission is not good.
Note that this is not some third-party app: I check every app when installing for permissions and I'm sure that nothing was set up with SMS sending permission.
Some threads (english translation) indicate that this is because G1 has some low-level T-mobile locks (although mine is officially unlocked one from singapore).
By the way, user has no way to officially way to rebuild and reflash its (open-source!) android OS.

Labels: 684, android, g1, sms

Yesterday I tried to call through wifi via skype using iphone client. Works great, talked for more than 15 minutes and quality is just like when using GSM! Also tried to install the Android skype client, but is said that I MUST enter my phone number and it will (WTF?!) be used when calling (all calls are paid, it said! callback?). Seems that Skype beta in Android is very strange thing: it cannot use 3G/Wifi connection for free skype2skype calls. Yes, just found quote from comments from here: http://share.skype.com/sites/skypegear/2009/01/video_skype_lite_on_android.html
Sad that receiving any phone calls, even from a skype caller, skype credit is used.
and more:
No calls can be made, no free calls received even when in WI-FI spot. This application is not ready for prime time ... If I wanted to IM, I would use another application. Please make Skype like it is on computers. Free calls computer-to-computer (or phone-to-skype_contact) over wifi or carrier's data plan.
Else is is useless.
This is it. iPhone is better :-)

Labels: android, iphone, skype, voicecall, wifi