Develop Reference

Xiaomi, Redmi, Android. Error in Logcat: W PowerChecker.Controller: autoKillApp, calling ProcessManager uid = 10289, pkg = com.termux

Xiaomi Redmi 7A with MIUI 12.5 keeps killing background service / application (Telegram SMS and Termux) when the phone is not connected to charger. Logcat log:
01-06 10:45:57.787 1892 1892 I MiuiChargeManager: notifyBatteryStatusChanged: status: 3 isPlugged: 0 level: 70 wireState: -1 chargeSpeed: 0 m
WiredChargeType: 0 mWirelessChargeType: 0 chargeDeviceType: -1
01-06 10:50:15.716 4344 4652 W PowerChecker.Controller: autoKillApp, calling ProcessManager uid = 10289, pkg = com.termux
01-06 10:50:15.716 1580 2093 I ProcessManager: Kill reason AutoPowerKill from pid=4344
01-06 10:50:15.829 1580 2093 I ProcessManager: AutoPowerKill: kill com.termux Adj=200 State=5
01-06 10:50:15.830 1580 2093 I ActivityManager: Killing 13234:com.termux/u0a289 (adj 200): AutoPowerKill
01-06 10:50:15.875 4344 4652 W PowerChecker.Controller: autoKillApp, calling ProcessManager uid = 10305, pkg = com.qwe7002.telegram_sms
01-06 10:50:15.876 1580 2093 I ProcessManager: Kill reason AutoPowerKill from pid=4344
01-06 10:50:15.877 1580 2093 I ProcessManager: AutoPowerKill: kill com.qwe7002.telegram_sms:command Adj=200 State=5
01-06 10:50:15.878 1580 2093 I ActivityManager: Killing 23378:com.qwe7002.telegram_sms:command/u0a305 (adj 200): AutoPowerKill
01-06 10:50:15.880 1580 2093 I ProcessManager: AutoPowerKill: kill com.qwe7002.telegram_sms:battery Adj=200 State=5
01-06 10:50:15.880 1580 2093 I ActivityManager: Killing 23348:com.qwe7002.telegram_sms:battery/u0a305 (adj 200): AutoPowerKill
01-06 10:50:15.961 1580 1848 I ProcessManager: remove no clear notification:StatusBarNotification(pkg=com.termux user=UserHandle{0} id=1337 tag=null key=0|com.termux|1337|null|10289: Notification(channel=termux_notification_channel pri=1 contentView=null vibrate=null sound=null defaults=0x0 flags=0x62 color=0xff607d8b actions=2 vis=PRIVATE))
01-06 10:50:15.968 1580 3450 W ActivityManager: Scheduling restart of crashed service com.termux/.app.TermuxService in 1000ms
01-06 10:50:15.973 1580 1665 W ActivityManager: setHasOverlayUi called on unknown pid: 13234
01-06 10:50:15.977 1580 4023 W ActivityManager: Scheduling restart of crashed service com.qwe7002.telegram_sms/.battery_service in 10992ms
01-06 10:50:15.983 1580 1848 I ProcessManager: remove no clear notification:StatusBarNotification(pkg=com.qwe7002.telegram_sms user=UserHandle{0} id=2 tag=null key=0|com.qwe7002.telegram_sms|2|null|10305: Notification(channel=Chat command pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x62 color=0x00000000 vis=PRIVATE))
01-06 10:50:15.984 1580 4019 W ActivityManager: Scheduling restart of crashed service com.qwe7002.telegram_sms/.chat_command_service in 20984ms
01-06 10:50:16.650 23510 23510 E ExtAssistant: Error occurred processing removal of StatusBarNotification(pkg=com.termux user=UserHandle{0} id=1337 tag=null key=0|com.termux|1337|null|10289: Notification(channel=termux_notification_channel pri=1 contentView=null vibrate=null sound=null defaults=0x0 flags=0x62 color=0xff607d8b actions=2 vis=PRIVATE))
How to fix this?

Need to lock application in Recents menu:
Go to Security app > tap settings (gear on top right) > Boost speed >
Lock apps > Lock the app you need to keep running. This replaces the
"padlock" icon (App pinning from the recents menu) that no longer is
visible in MIUI 12.
Source

Kivy aplication crashes on splash screen

I have a simple app for android written in python 2.7.12 32-bit, kivy 1.9.1 on ubuntu 16.04 64. I am able to build the app with buildozer debug deploy but the app won't start. It crashes while loading itself but stays in the 'background'. I inspected the logcat and there seems to be only one error:
build.xml: Failed to find version-tag string. File must be updated.
In order to not erase potential customizations, the file will not be automatically regenerated.
If no changes have been made to the file, delete it manually and run the command again.
If you have made customizations to the build process, the file must be manually updated.
It is recommended to:
Copy current file to a safe location.
Delete original file.
Run command again to generate a new file.
Port customizations to the new file, by looking at the new rules
file located at /tools/ant/build.xml
Update file to contain version-tag: custom to prevent file from
being rewritten automatically by the SDK tools.
I have been searching for the solution and even found some related topics but none of them seems to be related to building with buildozer. I would do what the above list instructs but i was unable to locate the /tools/ant/build.xml.
I am adding the output of terminal where app dies or at least I think it happens here:
12-25 09:58:34.762 1142 1153 I ActivityManager: Start proc 4509:org.test.localmapper:python/u0a220 for activity org.test.localmapper/org.renpy.android.PythonActivity
12-25 09:58:34.920 1142 1152 I ActivityManager: Killing 4384:com.sonymobile.android.addoncamera.styleportrait/u0a67 (adj 15): empty #17
12-25 09:58:35.120 1142 1162 I WindowManager: Focus moving from null to Window{d1f6d91 u0 org.test.localmapper/org.renpy.android.PythonActivity}
12-25 09:58:35.121 1142 1162 I WindowManager: Gaining focus: Window{d1f6d91 u0 org.test.localmapper/org.renpy.android.PythonActivity}
12-25 09:58:35.140 1142 2380 I ActivityManager: Start proc 4532:com.swiftkey.swiftkeyconfigurator/u0a178 for broadcast com.swiftkey.swiftkeyconfigurator/.PackageRemovedReceiver
12-25 09:58:35.144 1142 2380 I ActivityManager: Killing 4399:com.sonymobile.cameracommon/u0a27 (adj 15): empty #17
12-25 09:58:35.265 1142 2140 I RuntimeSkinInfo: com.sonymobile.runtimeskinning.LAF_VERSION in android blocks runtime skin from being applied, version value=2
12-25 09:58:35.265 1142 2140 I RuntimeSkinInfo: com.sonymobile.runtimeskinning.LAF_VERSION in com.android.systemui blocks runtime skin from being applied, version value=2
12-25 09:58:35.343 1142 1568 W ActivityManager: Skip forceProcessStateUpTo() to newState 11
12-25 09:58:35.367 1142 1152 I ActivityManager: Killing 3951:com.android.exchange/u0a36 (adj 15): empty #17
12-25 09:58:35.436 1142 2383 I NetworkIdentity: buildNetworkIdentity:
12-25 09:58:35.436 1142 2383 I NetworkIdentity: networkId = GNX324C50
12-25 09:58:35.448 1142 1357 I ActivityManager: Start proc 4562:com.sony.nfx.app.sfrc/u0a182 for broadcast com.sony.nfx.app.sfrc/.SocialifeUpdateReceiver
12-25 09:58:35.633 1142 1152 W ActivityManager: Skip forceProcessStateUpTo() to newState 11
12-25 09:58:35.918 1142 2144 I ActivityManager: Start proc 4584:com.google.android.apps.photos/u0a132 for broadcast com.google.android.apps.photos/.backgroundsignin.BackgroundSignInBroadcastReceiver
12-25 09:58:35.920 1142 2144 I ActivityManager: Killing 4053:com.sonymobile.runtimeskinning.core/u0a185 (adj 15): empty #17
12-25 09:58:36.077 1142 2146 W ActivityManager: Skip forceProcessStateUpTo() to newState 11
12-25 09:58:36.522 1142 1569 I RuntimeSkinInfo: com.sonymobile.runtimeskinning.LAF_VERSION in android blocks runtime skin from being applied, version value=2
12-25 09:58:36.522 1142 1569 I RuntimeSkinInfo: com.sonymobile.runtimeskinning.LAF_VERSION in com.android.systemui blocks runtime skin from being applied, version value=2
12-25 09:58:36.720 1142 1152 I WindowState: WIN DEATH: Window{d1f6d91 u0 org.test.localmapper/org.renpy.android.PythonActivity}
12-25 09:58:36.721 1142 1152 W WindowManager: Force-removing child win Window{56b40f7 u0 SurfaceView} from container Window{d1f6d91 u0 org.test.localmapper/org.renpy.android.PythonActivity}
12-25 09:58:36.729 1142 1568 W WindowManager: Failed looking up window
12-25 09:58:36.729 1142 1568 W WindowManager: java.lang.IllegalArgumentException: Requested window android.os.BinderProxy#8ea04f6 does not exist
12-25 09:58:36.729 1142 1568 W WindowManager: at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:9194)
12-25 09:58:36.729 1142 1568 W WindowManager: at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:9185)
12-25 09:58:36.729 1142 1568 W WindowManager: at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1209)
12-25 09:58:36.729 1142 1568 W WindowManager: at android.os.BinderProxy.sendDeathNotice(Binder.java:566)
12-25 09:58:36.729 1142 1568 I WindowState: WIN DEATH: null
12-25 09:58:36.731 1142 2146 I ActivityManager: Process org.test.localmapper:python (pid 4509) has died
12-25 09:58:36.731 1142 2146 W ActivityManager: Force removing ActivityRecord{1afe009 u0 org.test.localmapper/org.renpy.android.PythonActivity t1334}: app died, no saved state
12-25 09:58:36.742 1142 1162 I WindowManager: Focus moving from Window{d1f6d91 u0 org.test.localmapper/org.renpy.android.PythonActivity} to null
12-25 09:58:36.742 1142 1162 I WindowManager: Losing focus: Window{d1f6d91 u0 org.test.localmapper/org.renpy.android.PythonActivity}
12-25 09:58:36.767 1142 1162 I WindowManager: Focus moving from null to Window{93f1d2e u0 com.sonyericsson.home/com.sonymobile.home.HomeActivity}
12-25 09:58:36.767 1142 1162 I WindowManager: Gaining focus: Window{93f1d2e u0 com.sonyericsson.home/com.sonymobile.home.HomeActivity}
12-25 09:58:36.777 1142 2377 W InputMethodManagerService: Got RemoteException sending setActive(false) notification to pid 4509 uid 10220
12-25 09:58:36.925 1142 1568 W BroadcastQueue: Permission Denial: broadcasting Intent { act=android.intent.action.USER_PRESENT flg=0x24000010 } from com.android.systemui (pid=14393, uid=10068) is not exported from uid 10048 due to receiver com.sonymobile.mx.android/.receivers.StopMessageReceiver
12-25 09:58:36.947 1142 2146 I ActivityManager: Start proc 4613:com.sonymobile.ree/u0a52 for broadcast com.sonymobile.ree/.service.UserPresentReceiver
12-25 09:58:37.122 1142 2382 W ActivityManager: Skip forceProcessStateUpTo() to newState 11
12-25 09:58:37.221 1142 1569 I ActivityManager: Killing 4066:com.sonyericsson.updatecenter/u0a71 (adj 15): empty #17
12-25 09:58:37.334 1142 2377 I ActivityManager: Start proc 4633:deezer.android.app/u0a200 for broadcast deezer.android.app/com.deezer.push.BootParseBroadcastReceiver
12-25 0
Thank you!

Sounds like version string in buildozer.spec
Explained here, answer by eviltnan : https://stackoverflow.com/a/20898873/7153696

MVVMCross 3.5.1 and xamarin android does not work

I have a question: is there somebody that use MVVMCross 3.5.1 with Api level android 21 and xamarin studio 5.9.3? I have a problem: I reference mvvmcross in an android app. I have a splashscreen and a firstview. When I tried to start with emulator I don't have any problem with level 15 emulator but when I tried it with the last version (Api 21) the app after splashscreen is closed without any error (not open the firstview).
Is there a solution?
UPDATE
I tried with logcat. In the following I attached the log:
W/AudioTrack( 394): AUDIO_OUTPUT_FLAG_FAST denied by client
I/ActivityManager( 394): START u0 {act=android.intent.action.MAIN cat=[android.
intent.category.LAUNCHER] flg=0x10000000 cmp=com.nowhere.nowhere/md51f5aeae0dbe3
fa3acab67292d41114d1.SplashScreen (has extras)} from uid 10007 on display 0
I/Choreographer( 824): Skipped 67 frames! The application may be doing too muc
h work on its main thread.
I/art ( 1716): Not late-enabling -Xcheck:jni (already on)
I/ActivityManager( 394): Start proc com.nowhere.nowhere for activity com.nowher
e.nowhere/md51f5aeae0dbe3fa3acab67292d41114d1.SplashScreen: pid=1716 uid=10056 g
ids={50056, 9997, 3003} abi=armeabi-v7a
I/Choreographer( 394): Skipped 32 frames! The application may be doing too muc
h work on its main thread.
F/MonoDroid( 1716): shared runtime initialization error: dlopen failed: library
"/data/app/Mono.Android.DebugRuntime-1/lib/arm/lib/libmonosgen-2.0.so" not found
I/Zygote ( 66): Process 1716 exited cleanly (1)
I/ActivityManager( 394): Process com.nowhere.nowhere (pid 1716) has died
I/art ( 1731): Not late-enabling -Xcheck:jni (already on)
I/ActivityManager( 394): Start proc com.nowhere.nowhere for activity com.nowher
e.nowhere/md51f5aeae0dbe3fa3acab67292d41114d1.SplashScreen: pid=1731 uid=10056 g
ids={50056, 9997, 3003} abi=armeabi-v7a
F/MonoDroid( 1731): shared runtime initialization error: dlopen failed: library
"/data/app/Mono.Android.DebugRuntime-1/lib/arm/lib/libmonosgen-2.0.so" not found
I/Zygote ( 66): Process 1731 exited cleanly (1)
I/ActivityManager( 394): Process com.nowhere.nowhere (pid 1731) has died
I/art ( 1746): Not late-enabling -Xcheck:jni (already on)
I/ActivityManager( 394): Start proc com.nowhere.nowhere for activity com.nowher
e.nowhere/md51f5aeae0dbe3fa3acab67292d41114d1.SplashScreen: pid=1746 uid=10056 g
ids={50056, 9997, 3003} abi=armeabi-v7a
F/MonoDroid( 1746): shared runtime initialization error: dlopen failed: library
"/data/app/Mono.Android.DebugRuntime-1/lib/arm/lib/libmonosgen-2.0.so" not found
I/Zygote ( 66): Process 1746 exited cleanly (1)
I/ActivityManager( 394): Process com.nowhere.nowhere (pid 1746) has died
W/ActivityManager( 394): Force removing ActivityRecord{27f513c9 u0 com.nowhere.
nowhere/md51f5aeae0dbe3fa3acab67292d41114d1.SplashScreen t8}: app died, no saved
state
W/WindowManager( 394): Failed looking up window
W/WindowManager( 394): java.lang.IllegalArgumentException: Requested window and
roid.view.ViewRootImpl$W#3c7a1def does not exist
W/WindowManager( 394): at com.android.server.wm.WindowManagerService.wi
ndowForClientLocked(WindowManagerService.java:8412)
W/WindowManager( 394): at com.android.server.wm.WindowManagerService.wi
ndowForClientLocked(WindowManagerService.java:8403)
W/WindowManager( 394): at com.android.server.wm.WindowManagerService.re
moveWindow(WindowManagerService.java:2558)
W/WindowManager( 394): at com.android.server.wm.Session.remove(Session.
java:186)
W/WindowManager( 394): at android.view.ViewRootImpl.dispatchDetachedFro
mWindow(ViewRootImpl.java:2920)
W/WindowManager( 394): at android.view.ViewRootImpl.doDie(ViewRootImpl.
java:5390)
W/WindowManager( 394): at android.view.ViewRootImpl$ViewRootHandler.han
dleMessage(ViewRootImpl.java:3223)
W/WindowManager( 394): at android.os.Handler.dispatchMessage(Handler.ja
va:102)
W/WindowManager( 394): at android.os.Looper.loop(Looper.java:135)
W/WindowManager( 394): at android.os.HandlerThread.run(HandlerThread.ja
va:61)
W/WindowManager( 394): at com.android.server.ServiceThread.run(ServiceT
hread.java:46)
W/InputMethodManagerService( 394): Window already focused, ignoring focus gain
of: com.android.internal.view.IInputMethodClient$Stub$Proxy#14f4aa0b attribute=n
ull, token = android.os.BinderProxy#5c9e508
I/Choreographer( 824): Skipped 56 frames! The application may be doing too muc
h work on its main thread.
D/TaskPersister( 394): removeObsoleteFile: deleting file=8_task.xml
UPDATE 2
The bind does not work. Inside the view..
UPDATE 3
I put the code in this repo:
https://onedrive.live.com/redir?resid=1E563B1D1AD8A1C!15847&authkey=!AII01sfuzToQiUQ&ithint=file%2czip
I used this configuration for the test:
1. Nexus 5,
2. Android 5.0-API Level 21,
3. CPU/ABI, I have chosen Google APIs Intel Atom(x86_64),
4. Use Host GPU.
UPDATE 4
new link for code: http://1drv.ms/1MZWf45
Thanks
Alessandro

I found the problem. The problem was the emulator. I tried to change the configuration and now run without problem.
Thanks
Al.

Using WeakSubscribe from MvvmCross

I need to subscribe to INotifyPropertyChanged of one of my models in my ViewModel. My research led me to: How do I update the parent viewmodel when child viewmodel is updated.
I tried using WeakSubscribe as suggested in #3 but after entering and leaving the view several times my whole application either freezes or crashes.
Here's my code from Init() in the ViewModel:
foreach (var sale in Model.Sales)
{
sale.WeakSubscribe(delegate
{
Model.CalculateSalesTotals();
});
}
when the app is crashing, I'm getting SIGSEGV:
I/mono-stdout(30334): mvx:Diagnostic:227.00 Showing ViewModel InvoiceAuthorizationViewModel
I/ActivityManager( 391): START u0 {flg=0x10000000 cmp=com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView (has extras)} from pid 30334
I/mono-stdout(30334): mvx:Diagnostic:227.19 Loading new ViewModel from Intent with Extras
D/dalvikvm(30334): GC_EXPLICIT freed 783K, 5% free 17252K/18068K, paused 2ms+8ms, total 53ms
I/mono-stdout(30334): MvxBind:Warning:227.59 Unable to bind: source property source not found Cirrious.MvvmCross.Binding.Parse.PropertyPath.PropertyTokens.MvxPr
opertyNamePropertyToken on null-object
I/mono-stdout(30334): MvxBind:Warning:227.61 Unable to bind: source property source not found Cirrious.MvvmCross.Binding.Parse.PropertyPath.PropertyTokens.MvxPr
opertyNamePropertyToken on null-object
I/mono-stdout(30334): MvxBind:Warning:227.63 Unable to bind: source property source not found Cirrious.MvvmCross.Binding.Parse.PropertyPath.PropertyTokens.MvxPr
opertyNamePropertyToken on null-object
I/dalvikvm(30334): Jit: resizing JitTable from 4096 to 8192
I/ActivityManager( 391): Displayed com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView: +755ms (total +1s259ms)
I/ActivityManager( 391): Displayed com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView: +1s279ms
I/ActivityManager( 391): Process com.android.vending (pid 30179) has died.
E/mono-rt (30334): Stacktrace:
E/mono-rt (30334):
E/mono-rt (30334):
E/mono-rt (30334): =================================================================
E/mono-rt (30334): Got a SIGSEGV while executing native code. This usually indicates
E/mono-rt (30334): a fatal error in the mono runtime or one of the native libraries
E/mono-rt (30334): used by your application.
E/mono-rt (30334): =================================================================
E/mono-rt (30334):
I/ActivityManager( 391): Process com.desco.escMobile (pid 30334) has died.
I/WindowState( 391): WIN DEATH: Window{42cf2e60 u0 com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView}
W/ActivityManager( 391): Force removing ActivityRecord{42e05b20 u0 com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView}: app died, no saved st
ate
I/WindowState( 391): WIN DEATH: Window{427bfbf0 u0 com.desco.escMobile/escmobile.android.views.DispatchListView}
I/WindowState( 391): WIN DEATH: Window{42b32b50 u0 com.desco.escMobile/escmobile.android.views.InvoiceDetailsView}
I/WindowState( 391): WIN DEATH: Window{43003e48 u0 com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView}
I/WindowState( 391): WIN DEATH: Window{42aea920 u0 com.desco.escMobile/escmobile.android.views.DispatchDetailsView}
D/dalvikvm(30434): Late-enabling CheckJNI
I/ActivityManager( 391): Start proc com.desco.escMobile for activity com.desco.escMobile/escmobile.android.views.InvoiceAuthorizationView: pid=30434 uid=10086
gids={50086, 3003, 1015, 1028}
D/Zygote ( 129): Process 30334 exited cleanly (255)
Any suggestions?

Application restarts when user data for contacts app is cleared

My application works with standard android contacts, so I have following permissions in my AndroidManifest.xml:
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
Alas, when I clear user data for standard Contacts application ( Settings -> Applications -> Manage Applications -> All -> Contacts -> Clear data ), my application com.example.dialer restarts:
04-05 15:39:21.161 I/InstalledAppDetails( 9019): Clearing user data for package : com.android.providers.contacts
04-05 15:39:21.181 I/Process ( 252): Sending signal. PID: 8774 SIG: 9
04-05 15:39:21.181 I/Process ( 252): Sending signal. PID: 8761 SIG: 9
04-05 15:39:21.181 I/Process ( 252): Sending signal. PID: 8368 SIG: 9
04-05 15:39:21.181 I/ActivityManager( 252): Force stopping package com.android.providers.contacts uid=10017
04-05 15:39:21.181 I/ActivityManager( 252): Kill com.sonyericsson.android.socialphonebook (pid 8774): provider com.android.providers.contacts.SemcContactsProvider2 in dying process android.process.acore
04-05 15:39:21.181 I/ActivityManager( 252): Kill com.example.dialer (pid 8761): provider com.android.providers.contacts.SemcCallLogProvider in dying process android.process.acore
04-05 15:39:21.231 D/dalvikvm( 9019): GC_CONCURRENT freed 1572K, 52% free 3798K/7815K, external 4576K/5694K, paused 1ms+4ms
04-05 15:39:21.251 E/InputDispatcher( 252): channel '2b440330 com.example.dialer/com.example.dialer.Dialer (server)' ~ Consumer closed input channel or an error occurred. events=0x8
04-05 15:39:21.251 E/InputDispatcher( 252): channel '2b440330 com.example.dialer/com.example.dialer.Dialer (server)' ~ Channel is unrecoverably broken and will be disposed!
04-05 15:39:21.251 I/WindowManager( 252): WINDOW DIED Window{2b440330 com.example.dialer/com.example.dialer.Dialer paused=false}
04-05 15:39:21.261 I/ActivityManager( 252): Process com.example.dialer (pid 8761) has died.
04-05 15:39:21.261 W/ActivityManager( 252): Scheduling restart of crashed service com.example.dialer/.ContactsService in 5000ms
04-05 15:39:21.281 I/InstalledAppDetails( 9019): Cleared user data for package : com.android.providers.contacts
Is it possible to prevent this and update my app's state instead?

AFAIK, if your app contains CONTACT related permissions, means your app is associated with contact app somehow and is dependent on that.
When user cleared the contact app data, whole Contact package is restarted by the system(you can see in logs). That means all applications having CONTACTS related permissions will be restarted.
So I don't think you can stop this.