Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Force Checkin does not work for Secondary Users

See original GitHub issue

I am using a secondary user profile for my everyday business. However, in a secondary user profile the force checkin via dialing *#*#CHECKIN#*#* does not work. It is just ignored, probably due to permission issues. Can you add a button in the UI that does the same thing?

As a workaround I used the following ADB commands:

adb root
adb shell am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546 --receiver-include-background

Issue Analytics

State:
Created 5 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

Generatorcommented, Jan 11, 2021

Tried with Android 11, but still unable to register

Using adb root Permission Denial

adb shell am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546 
--receiver-include-background                                                                       
Broadcasting: Intent { act=android.provider.Telephony.SECRET_CODE dat=android_secret_code://2432546 
flg=0x1400000 }                                                                                     
                                                                                                    
Exception occurred while executing 'broadcast':                                                     
java.lang.SecurityException: Permission Denial: not allowed to send broadcast android.provider.Telep
hony.SECRET_CODE from pid=13944, uid=2000                                                           
        at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService
.java:16071)                                                                                        
        at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService
.java:15929)                                                                                        
        at com.android.server.am.ActivityManagerService.broadcastIntentWithFeature(ActivityManagerService.java:16743)
        at com.android.server.am.ActivityManagerShellCommand.runSendBroadcast(ActivityManagerShellCommand.java:747)
        at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:199)
        at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
        at android.os.ShellCommand.exec(ShellCommand.java:44)
        at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:1
0520)
        at android.os.Binder.shellCommand(Binder.java:929)
        at android.os.Binder.onTransact(Binder.java:813)
        at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5093)
        at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2877)
        at android.os.Binder.execTransactInternal(Binder.java:1159)
        at android.os.Binder.execTransact(Binder.java:1123)

Root inside shell:

adb shell
willow:/ $ su
willow:/ # am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546>
Broadcasting: Intent { act=android.provider.Telephony.SECRET_CODE dat=android_secret_code://2432546 flg=0x1400000 }
Broadcast completed: result=0

What should be the result value?

Version: Android: 11 microG: 0.2.16.204713

0reactions

zellebcommented, Jul 7, 2019

Found this issue while looking for a way to run that *#*#CHECKIN#*#* command on a Tablet. After running am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546 --receiver-include-background as root GCM registered.