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

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

Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

this means you call CurrentApp.RequestProductPurchaseAsync not from UI thread

error code 805a0194

(in a dialog) means that you need to publish your app (maybe in beta) via Store before you can test purchases.

Labels: development, error, microsoft, programming, store, windows 8 phone, windows store, wp8

mc : segmentation fault stable bug found (pay attention to mini status). did not yet tried to find such issue in their bug db. if we press OK now, it's segmentation fault:

<─ ~ ────────────────────────────────────────────────────────────────────.[^]>┐
│Permission Nl  Owner    Group    Size   Modify time            Name           │
│drwxr-xr-x 11 root     root     UP--DIR Feb  2  2011 ..                       │
│drwxr-xr-x  6 p                                                               │
│drwxr-xr-x  2 p ┌─────────────── Listing mode ───────────────┐                │
│drwxr-xr-x  2 p │                                            │                │
│drwxr-xr-x  2 p │  ( ) Full file list                        │                │
│drwxr-xr-x  3 p │  ( ) Brief file list                       │                │
│drwxr-xr-x  2 p │  (*) Long file list                        │                │
│drwxr-xr-x  3 p │  ( ) User defined:                         │                │
│drwxr-xr-x 10 p │      half type name | size | perm     [^]  │                │
│drwx------  2 p │                                            │                │
│drwxr-xr-x  9 p │  [ ] user Mini status                      │                │
│drwxr-xr-x  3 p │      half type name | date | size     [^]  │ _backup        │
│drwxr-xr-x  8 p │                                            │                │
│drwxr-xr-x  2 p │          [< OK >]       [ Cancel ]         │                │
│drwxr-xr-x  2 p └────────────────────────────────────────────┘                │
├───────────────                                                ───────────────┤
│UP--DIR                                                                       │
└────────────────────────────────────────────────────────────── 558M/14G (3%) ─┘
Hint: The file listing format can be customized; do "man mc" for details.

Labels: bug, error, mc, midnight commander

I have Maxxtor Diamond  Max 22 500Gb (STM3500320AS model with "mx15" firmware).

The problem this model has is same as in Seagate 7200.11 series: some counters in system area overflow... and microcontroller disables all IO operations to prevent data loss (which is, of course, logicallly thinking, good idea. But the criteria does not seem to be the right). Therefore, all data is stored OK inside bricked HDD. 

Symptops: HDD BUSY led are being turned on during computers seeks for HDD on startup, this process is VERY long and ALWAYS ends with either a message "boot device not found" (if affected HDD is a system one), or system loads, but affected HDD is not detected by the system (at all, not only partitions, but THERE'S NO ANY HDD detected, even with specialized Seagate's Tools, or DriveDetect utils).

This is it, so-called "BSY" failure. The HDD is brick now :-)

Now I've restored my system partition from backup and waiting for my friend to solder the RS232-to-TTL (COM - to - service connector) signal convertor. I've also found the needed Seagate service commands to unbrick the HDD with BSY error.

Please check whether your HDD is affected and in any case: BACK your data UP regularily!

Labels: backup, BSY, error, failure, hdd, maxtor, seagate

Some time ago my office 2007 stopped work after I uninstalled custom Windows Search 4 component of Windows. Reinstalling of Office didn't work (actually, even uninstaller/installer didn't work, both have errors!).
If you have same problem, here's solution: (re)install MS C++ 2005 runtime.

Labels: 2005, C++, error, ms, office2007, winxp