Gesture Control (root) - Acer Iconia Tab A100

I'm developing application that allows you to control tablet with gestures. Root access is needed. Currently it allows to execute following gestures: Back, Home, Show/Hide status bar
Try it out and let me know what you think. What other features or actions would be helpful?
All differences from other devices fixed. Please visit main thread.
http://forum.xda-developers.com/showthread.php?t=1535740

This sounds quite awesome. Does this potentially work on all HC tablets, or just the A100 and A500?

This does not work properly. It always says "Root failed" even when I grant it Superuser permissions. The only fully working feature is the "hide status bar" option. This app still seems to have potential though.

willverduzco said:
This sounds quite awesome. Does this potentially work on all HC tablets, or just the A100 and A500?
Click to expand...
Click to collapse
Potentially it works on all tablets, I just need a little bit of information. It even works on my SGS2 phone when I build it with decreased SDK requirements.
Could anyone test version (updated) from first post and send me logcat?

StupidIdea said:
Could anyone test version (updated) from first post and send me logcat?
Click to expand...
Click to collapse
Tested - It still does not work properly. Logcat attached.

Thanks, that explains the problem. I don't recognize multitouch properly on this device. Could you execute
from shell
su -c "getevent"
or from adb that would be
adb shell su -c "getevent"
make a few multitouch and send me output.

Added single touch option. Multitouch gestures not supported on this device at the moment.
Can anyone confirm that singletouch gestures are working on A100?

StupidIdea said:
Added single touch option. Multitouch gestures not supported on this device at the moment.
Can anyone confirm that singletouch gestures are working on A100?
Click to expand...
Click to collapse
I'll give it a try .
EDIT: Single touch gestures work perfectly .
StupidIdea said:
What other features or actions would be helpful?
Click to expand...
Click to collapse
You could add a gesture to disable the backlight (turn off screen). You could also add gestures to open certain apps (like browser, etc.) and possibly make them configurable.

Theonew said:
I'll give it a try .
EDIT: Single touch gestures work perfectly .
Click to expand...
Click to collapse
Good. Still need to investigate where multi touch disappeared.
Could you execute
from shell
su -c "getevent"
or from adb that would be
adb shell su -c "getevent"
make a few multitouch and send me output.

New version
1.2.1
- Added check for USB Debugging
Still want to need information in order to fix multitouch. See post above.

StupidIdea said:
Good. Still need to investigate where multi touch disappeared.
Could you execute
from shell
su -c "getevent"
or from adb that would be
adb shell su -c "getevent"
make a few multitouch and send me output.
Click to expand...
Click to collapse
StupidIdea said:
Still want to need information in order to fix multitouch. See post above.
Click to expand...
Click to collapse
Log attached . Hope the format isn't too new for you .

Thanks, I fixed it. Updated first post. Can you confirm, that multitouch works now?

good job
Any chance at getting touch to wake to work with this app
Sent from my HTC EVO 3D using XDA

StupidIdea said:
Change log:
1.2.2
- Fixed multitouch on A100 (and probably similar devices) - Thanks to Theonew
Click to expand...
Click to collapse
StupidIdea said:
Thanks, I fixed it. Updated first post. Can you confirm, that multitouch works now?
Click to expand...
Click to collapse
It works perfectly now. Great job, great app, and no problem for my help .

Theonew said:
It works perfectly now. Great job, great app, and no problem for my help .
Click to expand...
Click to collapse
Great app! Wonderful developer with whom to work. Kept in touch and fixed all the issues as promised. I hope he writes more apps.

Thanks everyone for help. I published update to market.
All differences are fixed now, so further discussion moving to the main thread:
http://forum.xda-developers.com/showthread.php?t=1535740"]http://forum.xda-developers.com/showthread.php?t=1535740[/URL]

Related

Mobile Shell 3.01 no freezing

Mobile Shell 3.01 seems to fix the freezing when pressing the panel x key
Amazing program
T
AnthonyByrne said:
Mobile Shell 3.01 seems to fix the freezing when pressing the panel x key
Amazing program
T
Click to expand...
Click to collapse
Where do you find 3.01? The website is still showing 3.0.
Also, any other changes between 3.0 and 3.01?
Thanks for your help.
ring-bearer said:
Where do you find 3.01? The website is still showing 3.0.
Also, any other changes between 3.0 and 3.01?
Thanks for your help.
Click to expand...
Click to collapse
Sorry, I forgot that I was able to google
Here's the link.
Seems also no delay on camera
It's awesome. No delay when switching to landscape.
It's really perfect now.
It seems that in first day it works well then suddenly the keys on front of xperia doentr work even the shutdown key is not working
It seems nice and smooth. Thank alot.
its just a trial for 15days ......how to get its registration key?.....
If You like Spb Shell..
jinnn_1989 said:
its just a trial for 15days ......how to get its registration key?.....
Click to expand...
Click to collapse
If you like the spb shell i suggest that you buy it!
Support them by buying like we all should if we like it!
Obalia73
if i install it over my 3.0 version will i have to set up all my widgets again or not?
Also, is there a way to change widget's icons just like in pocket+ by installing icon packs?
Thanks!
alex_mib said:
if i install it over my 3.0 version will i have to set up all my widgets again or not?
Thanks!
Click to expand...
Click to collapse
.........No
if we've got shell 3 already and instal this will we have to purchase it again or will it work like an upgrade/update?
daiash said:
if we've got shell 3 already and instal this will we have to purchase it again or will it work like an upgrade/update?
Click to expand...
Click to collapse
Nope. I had 3. Upgraded to 3.01. It did not ask for the key again.
awesome so far
just updated mine, camera is super fast and rotation is almost instant (most the time)
.............?
so, anybody knows about icons, i asked before?
Could the icons of the gadgets be changed?

[GUIDE] - EASY - Check your display type without root - Terminal Emulator method

If you like this tutorial and find it useful, LINK OTHER PEOPLE TO IT.
This is NOT my discovery and I'm not taking credit for it, I'm merely posting because I see this question asked over and over and wanted to make a more visible guide than the ones that are buried inside other threads.
This is very easy.
1. Download Terminal Emulator from the Market.
2. Reboot. (to clear memory)
3. Open Terminal and type DMESG, then press enter. (Does not require root.)
--3a. If you type dmesg | grep panel it should reduce the output and make it easier to find! (Might require root.)
persiansown said:
dmesg | grep panel
Click to expand...
Click to collapse
4. Scroll all the way back up to the top. Might take a minute.
5. Look for the line that reads something to the effect of <7>0000000 tag panel parsing panel type = (1 is bad, 2 is good)
6. Profit.
That's it! Very simple and easy and it will get you a definitive answer without rooting your phone.
If you like this tutorial and find it useful, LINK OTHER PEOPLE TO IT.
dmesg | grep panel
Thanks....
Sent from my HTC Glacier using XDA App
I have a 1 which is bad, what can I do?
Mine just says:
msmfb: turning on panel
glacier_panel_unblank +
glacier_panel_unblank -
Foo_Blyat said:
I have a 1 which is bad, what can I do?
Click to expand...
Click to collapse
Warranty exchange?
Sent from my HTC Glacier using XDA App
Please note that this does not work on rooted devices. I don't know why, but if your device is rooted the panel type does not show.
Sent from my HTC Glacier using XDA App
mr.tenuki said:
Please note that this does not work on rooted devices. I don't know why, but if your device is rooted the panel type does not show.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This isn't true, it works perfectly on my rooted device. The main key is to reboot just before you do this or you won't be looking at the right section of information.
Jeffmeister said:
Mine just says:
msmfb: turning on panel
glacier_panel_unblank +
glacier_panel_unblank -
Click to expand...
Click to collapse
Not sure what this is about... reboot the device and try again. Tell me exactly what you're putting into Terminal.
Mine says 1.... /cry
Sent from my HTC Glacier using XDA App
Phateless said:
This isn't true, it works perfectly on my rooted device. The main key is to reboot just before you do this or you won't be looking at the right section of information.
Click to expand...
Click to collapse
Again, I tried it with 2 different ROMs, after reboot and used "dmesg | grep -i panel" ( the -i option in grep command ignores case). All I got was the same lines as the previous comment.
In the original thread out is also mentioned that this method is not intended for rooted devices as it doesn't always work.
Sent from my HTC Glacier using XDA App
mr.tenuki said:
Again, I tried it with 2 different ROMs, after reboot and used "dmesg | grep -i panel" ( the -i option in grep command ignores case). All I got was the same lines as the previous comment.
In the original thread out is also mentioned that this method is not intended for rooted devices as it doesn't always work.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
That's your problem. Type ONLY "dmesg." I just tried it again specifically for your benefit and it worked fine.
Ok, now it worked after reboot and I'm a little puzzled. The grep command does work and you should add it to the guide as you don't need to search the output, so this wasn't the issue. Not sure why I didn't get it previously
Sent from my HTC Glacier using XDA App
mr.tenuki said:
Ok, now it worked after reboot and I'm a little puzzled. The grep command does work and you should add it to the guide as you don't need to search the output, so this wasn't the issue. Not sure why I didn't get it previously
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I believe it but I'm not familiar enough with Linux to ensure I list the command correctly. If you can figure out how to get it to work consistently I'll add it to the first post.
If I had known about that command I would have been stoked. You wouldn't believe how much time I wasted looking through lines of gibberish to find the panel type before I figured out I had to reboot, lol.
#2! That just made my morning
confirmed #2! ..... on a rooted device. Tried typing it dmesg after having phone on all night and it didnt work. Rebooted it and typed dmesg again and it worked
Thanks for this! Can also confirm it worked on my rooted device AFTER A REBOOT. Unfortunately I have panel type 1, which I already knew and it was no surprise to me, but I now have a replacement device on its way!
Wooohooo, got a 2! I wouldn't of hit the thanks button if it read 1 LOL j/k. Thanks for the informative post, phate!
thanks found mine is a 1 but its ok i got mt4g cheap at ebay
Phateless said:
I believe it but I'm not familiar enough with Linux to ensure I list the command correctly. If you can figure out how to get it to work consistently I'll add it to the first post.
If I had known about that command I would have been stoked. You wouldn't believe how much time I wasted looking through lines of gibberish to find the panel type before I figured out I had to reboot, lol.
Click to expand...
Click to collapse
I develop in Unix platform for living, the grep command is the right one. 2nd post in this thread also mentions it
Sent from my HTC Glacier using XDA App

Testing help required!

Hey folks, I've had a report from the Play Store that my app is crashing on Glides, but I can't get a log from the users. If any of you would be so good to test out the function and see if you have issues, and then grab me a log of the crash, I would be really grateful.. Will increase your thanks meter of course.
My app thread is here and the latest release is in post #3
When the app opens there is the option at the top to go to Android TTS settings. Apparently, clicking on this causes a crash.
Thanks in advance
brandall
See below
Looks like photo didnt attach... Trying again
Sent from my SAMSUNG-SGH-I927R using xda premium
Aquethys said:
Looks like photo didnt attach... Trying again
Click to expand...
Click to collapse
Thank you. I'm wondering if the problem is only with stock, unrooted, but there aren't too many of those on XDA..!
brandall said:
Thank you. I'm wondering if the problem is only with stock, unrooted, but there aren't too many of those on XDA..!
Click to expand...
Click to collapse
Indeed. Right when I opened the app it requested su access.
Btw, good work
Sent from my SAMSUNG-SGH-I927R using xda premium
Aquethys said:
Looks like photo didnt attach... Trying again
Sent from my SAMSUNG-SGH-I927R using xda premium
Click to expand...
Click to collapse
Aquethys said:
Indeed. Right when I opened the app it requested su access.
Btw, good work
Click to expand...
Click to collapse
Thank you If root is detected, su access is requested for advanced functions. Full busybox commands by voice are in the making!
I downloaded the one from the appstore and that one is working well as well. Got it to learn my name and tell me the time and toggle WIFI on and off. Working fine so far. Yes it does ask for SU. No crashes so far. Is the beta any different?
No problems here. Runs smoothly and recognizes commands.
Running stock rooted.
Tested it on a used Glide I just bought and haven't had time to root yet. Running stock 2.3.5 that was factory reset a couple of days ago. No problems accessing any menu or sub-menu item. Guess I just haven't had time to put enough crap on it to make it unstable.
dudejb said:
I downloaded the one from the appstore and that one is working well as well. Got it to learn my name and tell me the time and toggle WIFI on and off. Working fine so far. Yes it does ask for SU. No crashes so far. Is the beta any different?
Click to expand...
Click to collapse
Pyho said:
No problems here. Runs smoothly and recognizes commands.
Running stock rooted.
Click to expand...
Click to collapse
oldnoob said:
Tested it on a used Glide I just bought and haven't had time to root yet. Running stock 2.3.5 that was factory reset a couple of days ago. No problems accessing any menu or sub-menu item. Guess I just haven't had time to put enough crap on it to make it unstable.
Click to expand...
Click to collapse
Thanks guys, it's appreciated - strange that the crash can't be replicated - there must be some other issues on the devices that are having problems.
The beta release is still a while away and will contain many more advanced features for full device control by voice. It's strange bug reports like this that slow me down! At least I can move on from this one now.
Thanks again, your thanks meters have increased.
brandall
Maybe the user who posted about the crash removed the Pico service
brandall said:
Thanks guys, it's appreciated - strange that the crash can't be replicated - there must be some other issues on the devices that are having problems.
The beta release is still a while away and will contain many more advanced features for full device control by voice. It's strange bug reports like this that slow me down! At least I can move on from this one now.
Thanks again, your thanks meters have increased.
brandall
Click to expand...
Click to collapse
1 one feature I would love to see is the ability to add something in the calendar via voice. I hear Siri can do that and would love to see that on Android.
Nardholio said:
Maybe the user who posted about the crash removed the Pico service
Click to expand...
Click to collapse
I should have code to catch that and stop the crash - Why I'm even more puzzled that a crash could happen at all....
dudejb said:
1 one feature I would love to see is the ability to add something in the calendar via voice. I hear Siri can do that and would love to see that on Android.
Click to expand...
Click to collapse
This feature is working well on my test devices - it'll make an appearance in a couple of releases time, after I've had chance to test it on multiple users calendars and multiple calendar apps.
Ok I just tested my theory. With Pico TTS uninstalled it tries to open settings, which freezes and FCs, and it dumps you right back in your app. Your app does not crash. Honestly if this is the bug, I'd say it's user error and not your fault.
Nardholio said:
Ok I just tested my theory. With Pico TTS uninstalled it tries to open settings, which freezes and FCs, and it dumps you right back in your app. Your app does not crash. Honestly if this is the bug, I'd say it's user error and not your fault.
Click to expand...
Click to collapse
Good work Thank you. I assume the crash also may extend to the Pico engine (or perhaps any other) having installation corruption of some kind.
Thanks again to everyone who replied and tested, it's really appreciated. I think I can safely say 'not guilty!'.
Cheers
brandall

[Req / Ask] 2 way voice recording

Hi guys,
Did you know app or mod or something else that could record voice or phone conversation from both side i mean my voice and opponent voice like xiaomi feature. I tried several app from play store but they just record my voice
Thank you
barcodevii said:
Hi guys,
Did you know app or mod or something else that could record voice or phone conversation from both side i mean my voice and opponent voice like xiaomi feature. I tried several app from play store but they just record my voice
Thank you
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=polis.app.callrecorder
Seems to work
Download skyvalex callrecorder
Sent from my G8142 using XDA-Developers Legacy app
I have been using skvalex for years but this beta was buggy oz XZP (I've tried it month ago). Now I am using ACR and it is working like a charm.
AJHutchinson said:
https://play.google.com/store/apps/details?id=polis.app.callrecorder
Seems to work
Click to expand...
Click to collapse
Mangtas_666 said:
Download skyvalex callrecorder
Sent from my G8142 using XDA-Developers Legacy app
Click to expand...
Click to collapse
denkem said:
I have been using skvalex for years but this beta was buggy oz XZP (I've tried it month ago). Now I am using ACR and it is working like a charm.
Click to expand...
Click to collapse
Super.
Will try one by one and let see which better
Why you don't use the native call recording feature?
@serajr has ported it. Ask him if he can please make a version for oreo
lebigmac said:
Why you don't use the native call recording feature?
@serajr has ported it. Ask him if he can please make a version for oreo
Click to expand...
Click to collapse
First of all I need an device running oreo stock fw, which it's not my case, unfortunately (I've bought an XZ1 for my wife, but it will remain locked)! Till there, I can't help out!!
There's also a couple of interesting settings available via adb on the ZX1c which may also be present on the XZP.
adb shell settings get system somc.call_recording
adb shell settings get system somc.call_recording_beeptones
The defaults are:
somc.call_recording=0
somc.call_recording_beeptones=1
But both can be changed with:
adb shell settings put system somc.call_recording 1
adb shell settings put system somc.call_recording_beeptones 0
I don't get any call recording options when I activate them on the XZ1c, but maybe the XZP's dialer is different.
pbarrette said:
There's also a couple of interesting settings available via adb on the ZX1c which may also be present on the XZP.
adb shell settings get system somc.call_recording
adb shell settings get system somc.call_recording_beeptones
The defaults are:
somc.call_recording=0
somc.call_recording_beeptones=1
But both can be changed with:
adb shell settings put system somc.call_recording 1
adb shell settings put system somc.call_recording_beeptones 0
I don't get any call recording options when I activate them on the XZ1c, but maybe the XZP's dialer is different.
Click to expand...
Click to collapse
These settings need this to work. Just enabling them will not give you the call recording feature.
Dialer looks for these settings first, and then if some packages are installed and working. These packages (apps) are not part of sony stock firmware anymore!
serajr said:
These settings need this to work. Just enabling them will not give you the call recording feature.
Dialer looks for these settings first, and then if some packages are installed and working. These packages (apps) are not part of sony stock firmware anymore!
Click to expand...
Click to collapse
I see..
I haven't figured out how to deodex the Oreo framework jars yet, so I haven't been able to get too deep into the underlying code.
That does explain why I didn't see any recording options in the phone related APK's.
Thanks for the post. I didn't even realize skvalex wasn't working with Oreo after upgrading (even though most people say it didn't work with Nougat, it worked fine for me). Just installed the unreleased beta and everything is working fine again.

Control your AOD (LED alternative - Automate flow)

Hi all,
I am also missing a notification LED for incoming messages et al.
Well, the following might be of interest for some of you. Let me explain: I took a closer look at Automate and the flows provided by the user community there. Unfortunately all the flows for controlling the AOD there do support Samsung and LG devices only. By chance I stumbled across the correct name for the Huawei-specific variable that needs to be triggered. So, I took a working flow for LG, simply replaced the variable's name and voila, a working flow, without the need for root or something.
And it works like this: each time an incomming message (or something similar) triggers a notification, the stock AOD gets switched on, showing you the usual clock and notification icon. As soon as you are disabling the notification (by reading the message etc. pp.) the AOD gets switched off again. This works quite well, saves some battery (compared to having AOD constantly on), and you can clearly see when a new message arrives. I also didn't need to put Automate in the battery white list, it simply works as intended.
The necessary steps to get this working are as follows:
Install Automate from play store
Install the Automate extensions "network permissions", "settings permissions" and "superuser permissions" (the latter does not need root for granting the permissions indeed)
Enable "superuser permissions" via adb:
Code:
adb shell pm grant com.llamalab.automate.ext.superuser android.permission.WRITE_SECURE_SETTINGS
Switch off the AOD functionality in your devices settings
Download the (zipped) flow I have attached to this post and install it
Start the flow and grant the permissions you are asked for
If you use flow v01 switch off the logging of that flow, there are tons of data generated while the device is plugged in via USB, flow v02 works fine with loggin enabled
Enable "Automate" in Settings -> Accessibility features -> Accessibility -> Downloaded Services
I have been running this solution since late November. For me it runs smoothly, stable and battery friendly. Maybe it's also helpful for some of you. Just let me know when you have questions.
Disclaimer: I have published the flow on 25th November at android-hilfe.de and in the Automate community only recently.
Cheers.
Update:
@RoteDose has been so kind and had a closer look at the old flow and completely reworked the power charging check, so there's no log flooding anymore. So he created a v02, that I have attached here now. Thanks a bunch for your support, mate!
To do: research for AOD icons to be refreshed after disabling the notification
- Found a list of Huawei specific settings here.
- And you can list the settings by
Code:
adb shell settings list system|global|secure
Hi. I tried this for the Mate 20 X and got the following error when trying to enable superuser permissions using Terminal Emulator:
adb: inaccessible or not found
I am not rooted - any idea what the issue might be?
praveen6585 said:
Hi. I tried this for the Mate 20 X and got the following error when trying to enable superuser permissions using Terminal Emulator:
adb: inaccessible or not found
I am not rooted - any idea what the issue might be?
Click to expand...
Click to collapse
Hi. I would recommend to use adb from your PC. Here's a XDA how-to: https://www.xda-developers.com/install-adb-windows-macos-linux :good:
beggar23 said:
Hi. I would recommend to use adb from your PC. Here's a XDA how-to: https://www.xda-developers.com/install-adb-windows-macos-linux :good:
Click to expand...
Click to collapse
Thanks.. I'll try this and revert
Hi can you please give more details on no. 5, 6 and 7?
galaxy16 said:
Hi can you please give more details on no. 5, 6 and 7?
Click to expand...
Click to collapse
You can download to your phone the file "Huawei AOD switch.zip" I attached and unpack it to a path of your choice. In the Automate app you can import the unpacked "*.flo" file through the dots menu on the top right. You are then able to give permissions, switch logging and start/stop the flow.
Hope this helps. Just let me know. Cheers.
Is there anything else to do after the upload? Unfortunately, it doesn't work for me. I get a notification and nothing happens. But when I turn on the screen and lock the AOD shows. But that's not how it's supposed to work.
beginner user said:
Is there anything else to do after the upload? Unfortunately, it doesn't work for me. I get a notification and nothing happens. But when I turn on the screen and lock the AOD shows. But that's not how it's supposed to work.
Click to expand...
Click to collapse
Have you switched off AOD before starting the flow?
beggar23 said:
Have you switched off AOD before starting the flow?
Click to expand...
Click to collapse
Yes, it's still off.
beginner user said:
Unfortunately, it doesn't work for me. I get a notification and nothing happens. But when I turn on the screen and lock the AOD shows. But that's not how it's supposed to work.
Click to expand...
Click to collapse
Alright. Let's check some things. First question: How do you know, that you got a notification, when the screen or AOD doesn't light up?
beggar23 said:
Alright. Let's check some things. First question: How do you know, that you got a notification, when the screen or AOD doesn't light up?
Click to expand...
Click to collapse
I was writing a message from my wife... Generally speaking, now it's working. I don't know what was wrong before. That's great
beginner user said:
I was writing a message from my wife... Generally speaking, now it's working. I don't know what was wrong before. That's great
Click to expand...
Click to collapse
Glad to hear that! :good:
Its not working o my P30, Emui 10. I followed instruction everything allowed, AOD stock deactivated, but nothing......Automate works fine, flow is active, but...… What could be wrong......
First of all, thank you for this solution.
But I have a little problem. I don't know why, but for me doesn't work :/
AOD switched off -> started the flow (granted all the permissions) -> lock the screen -> i got a message (the phone vibrated), but the AOD doesn't switch on -> unlock the phone, just to the home screen (doesn't read the message) and lock again -> and now the AOD is switched on
The problem is solved.
Just need to enable this:
Settings -> Accessibility features -> Accessibility -> scroll down and enable Automate
razer91 said:
The problem is solved.
Just need to enable this:
Settings -> Accessibility features -> Accessibility -> scroll down and enable Automate
Click to expand...
Click to collapse
Thank you for that. I will add it to the OP.
Alexxxx1 said:
Its not working o my P30, Emui 10. I followed instruction everything allowed, AOD stock deactivated, but nothing......Automate works fine, flow is active, but...… What could be wrong......
Click to expand...
Click to collapse
Let's stop, switch on logging and restart the flow. Try enabling Automate in "Downloaded Services" as @razer91 described below your post. Maybe the log info will then help you finding out what goes wrong. Just let me know.
beggar23 said:
Let's stop, switch on logging and restart the flow. Try enabling Automate in "Downloaded Services" as @razer91 described below your post. Maybe the log info will then help you finding out what goes wrong. Just let me know.
Click to expand...
Click to collapse
Thank You very much! It works, great!
I hope that Automata will not affect on battery life.
Alexxxx1 said:
Thank You very much! It works, great!
I hope that Automata will not affect on battery life.
Click to expand...
Click to collapse
I don't think so. At least here it's all fine. Automate is not even in the battery saver white list, and going to sleep perfectly. Also, I detected no CPU wakelocks.
Yes, I checked too. The consumption of battery by Automata is minor.
Excellent work man [emoji106][emoji108]
Sent from my ELE-L29 using Tapatalk

Categories

Resources