Known Issues on Android 5.0/5.1
Moderator: Martin
Re: Known Issues on Android 5.0/5.1
Hi Sam,
A problem with the lock screen or a daydream could explain this. There have been many internal changes to Android in the lock screen area for Android 5, there are also some known unresolved bugs in this area (even in Android 5.1) so it sounds very plausible to me.
However I've not run into the issue your experiencing myself yet so if you find a way to reproduce this, I would be highly interested to know the steps to do so.
Are you using apps that force full screen/immersive mode or screen filters of some sort? Some apps can be invisible but still grab input focus which blocks access to the visible app in the 'background'.
Regards,
Martin
A problem with the lock screen or a daydream could explain this. There have been many internal changes to Android in the lock screen area for Android 5, there are also some known unresolved bugs in this area (even in Android 5.1) so it sounds very plausible to me.
However I've not run into the issue your experiencing myself yet so if you find a way to reproduce this, I would be highly interested to know the steps to do so.
Are you using apps that force full screen/immersive mode or screen filters of some sort? Some apps can be invisible but still grab input focus which blocks access to the visible app in the 'background'.
Regards,
Martin
-
- Posts: 10
- Joined: 24 Sep 2015 12:22
Re: Known Issues on Android 5.0/5.1
Hey.
I'm new here, because not so long ago bought your application. So I welcome all.
What you read is unfortunately a product of Google Translate, I do not have much time to think over my grammar.
But to the point, I discovered a small error in one Trigger. It is a condition of "Battery Level" in the "full".
When I charged the phone to complete or up to 100%, the condition should be satisfied, but not according to the program.
I use the Nexus 5 with Rotem (LMY48I).
I take this opportunity to ask what is better for the battery, one big flow, or several smaller?
Regards.
I'm new here, because not so long ago bought your application. So I welcome all.
What you read is unfortunately a product of Google Translate, I do not have much time to think over my grammar.
But to the point, I discovered a small error in one Trigger. It is a condition of "Battery Level" in the "full".
When I charged the phone to complete or up to 100%, the condition should be satisfied, but not according to the program.
I use the Nexus 5 with Rotem (LMY48I).
I take this opportunity to ask what is better for the battery, one big flow, or several smaller?
Regards.
Re: Known Issues on Android 5.0/5.1
I have used that condition in couple of different phones. All of them drop the battery percentage to 99 after a couple of seconds when I unplug the phone. The same happens even if plugged if I'm using resource heavy programs. Dropping the condition value from 100% to 99% solved my problems.
Basically it doesn't matter if you divide one big flow to several smaller. The number of elements as a whole is the critical thing, you'd usually want to keep as low as possible, battery vice. Also, some actions does not really matter at all, while some eats a lot of battery. There's no simple answer for this, as the optimizations must be done flow by flow depending on their purpose.
Basically it doesn't matter if you divide one big flow to several smaller. The number of elements as a whole is the critical thing, you'd usually want to keep as low as possible, battery vice. Also, some actions does not really matter at all, while some eats a lot of battery. There's no simple answer for this, as the optimizations must be done flow by flow depending on their purpose.
Re: Known Issues on Android 5.0/5.1
I found 2 small issues:
1. When I have only 1 custom widget and I delete it from Automagic,then when I reboot phone widget reappears in Automagic. I have to delete manualy widgets.xml from Automagic folder.
2. If I have disabled Automagic "show status icon" and then I turn off "handle existing NFC tags", the status icon reappears.
1. When I have only 1 custom widget and I delete it from Automagic,then when I reboot phone widget reappears in Automagic. I have to delete manualy widgets.xml from Automagic folder.
2. If I have disabled Automagic "show status icon" and then I turn off "handle existing NFC tags", the status icon reappears.
Re: Known Issues on Android 5.0/5.1
Thanks for reporting! I can confirm both issues (independent of Android version).
Both issues should be fixed in the next update.
Regards,
Martin
Both issues should be fixed in the next update.
Regards,
Martin
Re: Known Issues on Android 5.0/5.1
Hi Martin,
Any luck in fixing the Init Variable Network Traffic issue?
I have this problem on a Samsung S4 with Android 5.0.1.
When I'm connected to WiFi the reported mobile data traffic is 0 (zero).
When I'm connected to mobile data the reported mobile data traffic is ok.
Regards,
Traian
Any luck in fixing the Init Variable Network Traffic issue?
I have this problem on a Samsung S4 with Android 5.0.1.
When I'm connected to WiFi the reported mobile data traffic is 0 (zero).
When I'm connected to mobile data the reported mobile data traffic is ok.
Regards,
Traian
Re: Known Issues on Android 5.0/5.1
Hi,
I've implemented a workaround quite some time ago. Are you using the latest version of Automagic? Unfortunately I don't have an S4 available for tests.
When you enable 'Debug Log' in the preferences of Automagic and execute the action, is there anything printed in the log?
Regards,
Martin
I've implemented a workaround quite some time ago. Are you using the latest version of Automagic? Unfortunately I don't have an S4 available for tests.
When you enable 'Debug Log' in the preferences of Automagic and execute the action, is there anything printed in the log?
Regards,
Martin
Re: Known Issues on Android 5.0/5.1
No. There is nothing strange in the log.
I paste the log here.
24.11.2015 17:56:44.725 [Flow1] Starting to execute flow 'Flow1' with Context{global{global_volume_ring=7,global_profil=Acasă,global_diminuareSunetApel=false,global_ringer_mode=2,global_utilizareDate_shutDown=2353666,global_acasa=2,global_utilizareDate_reset=2100200,global_plat=0,global_calendar90zile_id_start_end=[476, 1439354700000, 1439390700000],global_WiFi=Vodafone,global_bWaze=false},local{flow_name=Flow1,triggertime=1448380604724,trigger=Manual}}
24.11.2015 17:56:44.726 [Flow1] Start executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:44.785 [Flow1] End executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:44.823 [Flow1] Flow continues executing with the next step.
24.11.2015 17:56:44.824 [Flow1] Start executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:44.859 [Flow1] Object 'Flow1' Showing toast text '2382080'.
24.11.2015 17:56:44.872 [Flow1] End executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:45.051 [Flow1] Flow ended.
24.11.2015 17:56:45.069 Removed wake lock tracker [Flow1]
24.11.2015 17:56:45.070 Releasing wake lock tracker [Flow1]
24.11.2015 17:56:55.670 [Flow1] Starting to execute flow 'Flow1' with Context{global{global_volume_ring=7,global_profil=Acasă,global_diminuareSunetApel=false,global_ringer_mode=2,global_utilizareDate_shutDown=2353666,global_acasa=2,global_utilizareDate_reset=2100200,global_plat=0,global_calendar90zile_id_start_end=[476, 1439354700000, 1439390700000],global_WiFi=Acasă,global_bWaze=false},local{flow_name=Flow1,triggertime=1448380615665,trigger=Manual}}
24.11.2015 17:56:55.672 [Flow1] Start executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:55.728 [Flow1] End executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:55.753 [Flow1] Flow continues executing with the next step.
24.11.2015 17:56:55.754 [Flow1] Start executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:55.790 [Flow1] Object 'Flow1' Showing toast text '0'.
24.11.2015 17:56:55.794 [Flow1] End executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:55.850 [Flow1] Flow ended.
24.11.2015 17:56:55.863 Removed wake lock tracker [Flow1]
24.11.2015 17:56:55.864 Releasing wake lock tracker [Flow1]
I paste the log here.
24.11.2015 17:56:44.725 [Flow1] Starting to execute flow 'Flow1' with Context{global{global_volume_ring=7,global_profil=Acasă,global_diminuareSunetApel=false,global_ringer_mode=2,global_utilizareDate_shutDown=2353666,global_acasa=2,global_utilizareDate_reset=2100200,global_plat=0,global_calendar90zile_id_start_end=[476, 1439354700000, 1439390700000],global_WiFi=Vodafone,global_bWaze=false},local{flow_name=Flow1,triggertime=1448380604724,trigger=Manual}}
24.11.2015 17:56:44.726 [Flow1] Start executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:44.785 [Flow1] End executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:44.823 [Flow1] Flow continues executing with the next step.
24.11.2015 17:56:44.824 [Flow1] Start executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:44.859 [Flow1] Object 'Flow1' Showing toast text '2382080'.
24.11.2015 17:56:44.872 [Flow1] End executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:45.051 [Flow1] Flow ended.
24.11.2015 17:56:45.069 Removed wake lock tracker [Flow1]
24.11.2015 17:56:45.070 Releasing wake lock tracker [Flow1]
24.11.2015 17:56:55.670 [Flow1] Starting to execute flow 'Flow1' with Context{global{global_volume_ring=7,global_profil=Acasă,global_diminuareSunetApel=false,global_ringer_mode=2,global_utilizareDate_shutDown=2353666,global_acasa=2,global_utilizareDate_reset=2100200,global_plat=0,global_calendar90zile_id_start_end=[476, 1439354700000, 1439390700000],global_WiFi=Acasă,global_bWaze=false},local{flow_name=Flow1,triggertime=1448380615665,trigger=Manual}}
24.11.2015 17:56:55.672 [Flow1] Start executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:55.728 [Flow1] End executing action 'Init Variables Network Traffic: total_transmitted_bytes, total_received_bytes, mobile_transmitted_bytes, mobile_received_bytes'
24.11.2015 17:56:55.753 [Flow1] Flow continues executing with the next step.
24.11.2015 17:56:55.754 [Flow1] Start executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:55.790 [Flow1] Object 'Flow1' Showing toast text '0'.
24.11.2015 17:56:55.794 [Flow1] End executing action 'Notification on Screen: {mobile_transmitted_bytes+mobile_received_bytes}'
24.11.2015 17:56:55.850 [Flow1] Flow ended.
24.11.2015 17:56:55.863 Removed wake lock tracker [Flow1]
24.11.2015 17:56:55.864 Releasing wake lock tracker [Flow1]
Re: Known Issues on Android 5.0/5.1
I'm out of ideas. Could you please take a bug report: System settings->Developer options->'Take bug report' and send it to info@automagic4android.com?
Re: Known Issues on Android 5.0/5.1
I can't take a bug report. The phone doesn't generate it. I've waited a couple of hours but I didn't got any report. I've tried both ways from Developer Menu and from Power Menu. No luck.
To test my problem I've created a simple test flow with three actions. First, I have Init Variables Network Traffic, then I have a Script where I calculate total mobile data (as sum of mobile_received_bytes and mobile_transmitted_bytes) and total data (as sum of total_received_bytes and total_transmitted_bytes). Then, I display the two sums on screen.
Now, when I'm connected to mobile network the total mobile data is ok and the total data is ok. When I'm connected to WiFi the total mobile data is zero, but total data is ok (the same value as when I'm connected to mobile network).
The Android version is 5.0.1.
I hope I've explained my problem clearly enough.
To test my problem I've created a simple test flow with three actions. First, I have Init Variables Network Traffic, then I have a Script where I calculate total mobile data (as sum of mobile_received_bytes and mobile_transmitted_bytes) and total data (as sum of total_received_bytes and total_transmitted_bytes). Then, I display the two sums on screen.
Now, when I'm connected to mobile network the total mobile data is ok and the total data is ok. When I'm connected to WiFi the total mobile data is zero, but total data is ok (the same value as when I'm connected to mobile network).
The Android version is 5.0.1.
I hope I've explained my problem clearly enough.