ColorOS problem with tiles on Android 11

Mobile Apps Home Assistant Companion for Android
1

Hi there,

I have a problem setting up the tiles on my oppo reno 4 pro (android 11).
What I can do in the companion app is setting up the tiles and link them to my scripts.
then I try to put the tile into the notification bar and click on it. Everytime I get an error message called the service could not be send.
On the Redmi Note 9S of my wife with MIUI 11 it works like a charm, same on my Xiaomi Pad 5.

But on my Oppo I tried everything but had no luck. Restarting the companion app, setting up new tiles, writing new scripts, setting up running in background on Android, restarting the phone and so on.
What can I do? Why its not working for me? The function is very useful for me not to start the app everytime I want to switch on/off a scene.

2

check logs in app configuration to see teh traceback for the error

3

That is the problem, the log is empty. I have no idea where to look at.

4

App configuration > show and share logs should not be empty. If its empty then thats a pretty big issue with the ROM itself as it uses standard ADB logcat commands to show those logs. Your best bet would be to use ADB logcat from a PC or an app like Logcat Reader. Both of which will require you to plug in your device to grant specific permissions.

5

--------- beginning of main
750)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
12-19 14:10:55.191 31931 25304 E SensorReceiver: Caused by: retrofit2.HttpException: HTTP 410 Gone
12-19 14:10:55.191 31931 25304 E SensorReceiver: at retrofit2.KotlinExtensions$await$2$2.onResponse(KotlinExtensions.kt:53)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:161)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
12-19 14:10:55.191 31931 25304 E SensorReceiver: at java.lang.Thread.run(Thread.java:923)
12-19 14:10:55.199 31931 32092 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=dc7840b1-614b-4aea-9cb5-00150543d423, tags={ io.homeassistant.companion.android.sensors.SensorWorker } ]
12-19 14:10:55.203 31931 31931 I WM-SystemFgDispatcher: Stopping foreground service
12-19 14:10:55.245 31931 31931 I Choreographer: Skipped 3 frames! The application may be doing too much work on its main thread.
12-19 14:10:55.696 31931 31931 D ActivitySM: Received activity update.
12-19 14:10:57.279 31931 31931 D ViewRootImpl[SettingsActivity]: processMotionEvent MotionEvent { action=ACTION_DOWN, actionButton=0, id[0]=0, x[0]=690.29297, y[0]=1190.0391, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=931698781, downTime=931698781, deviceId=4, source=0x1002, displayId=0 }
12-19 14:10:57.279 31931 31931 D ViewRootImpl[SettingsActivity]: dispatchPointerEvent handled=true, event=MotionEvent { action=ACTION_DOWN, actionButton=0, id[0]=0, x[0]=690.29297, y[0]=1190.0391, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=931698781, downTime=931698781, deviceId=4, source=0x1002, displayId=0 }
12-19 14:10:57.323 31931 31931 D ViewRootImpl[SettingsActivity]: processMotionEvent MotionEvent { action=ACTION_UP, actionButton=0, id[0]=0, x[0]=690.29297, y[0]=1190.0391, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=931698828, downTime=931698781, deviceId=4, source=0x1002, displayId=0 }
12-19 14:10:57.325 31931 31931 D ViewRootImpl[SettingsActivity]: dispatchPointerEvent handled=true, event=MotionEvent { action=ACTION_UP, actionButton=0, id[0]=0, x[0]=690.29297, y[0]=1190.0391, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=931698828, downTime=931698781, deviceId=4, source=0x1002, displayId=0 }
12-19 14:10:57.343 31931 31931 D TestOverScroll: getScaledOverscrollDistance: b
12-19 14:10:57.343 31931 31931 E OplusCustomizeRestrictionManager: getInstance
12-19 14:10:57.359 31931 31931 I Choreographer: Skipped 1 frames! The application may be doing too much work on its main thread.
12-19 14:10:57.375 31931 31931 I chatty : uid=10375(io.homeassistant.companion.android) identical 4 lines
12-19 14:10:57.377 31931 31931 E OplusCustomizeRestrictionManager: getInstance
12-19 14:10:57.400 31931 28503 D LogcatReader: Read logcat for pid 31931

That’s what the log is showing. But I can’t get useful information of that. You?

6

retrofit2.HttpException: HTTP 410 Gone looks like you need to start fresh

7

yeah I got it!
Thank you really for your fast help.
I have 3 devices under mobile app in my list, but I only deleted the oppo, then deleted all data on my android and it worked like a charm.
Really useful now.
I wish you Merry Christmas!