Tasker issue trying to automate Airplane Mode - Xiaomi Mi Pad 4 Questions & Answers

Hi Guys,
Running EU 10.1 and trying to configure tasker to automatically activate Airplane mode, I get the following message:
18.17.38/E Airplane Mode: 0 -> 1
18.17.38/E Airplane Mode: curval: 0 new: 1
18.17.38/E Airplane Mode: putInt airplane_mode_on/1 failed
18.17.38/E wait for 100ms
18.17.38/E wait finished
18.17.38/E result: stop task (error)
18.17.38/E Error: 1
18.17.38/MacroEdit action finished exeID 1 action no 0 code 333 status: Err next 0
Profile becomes active but task won't execute. Have not tried any other commands yet..
Any ideas as to what may be the issue?

Hi , I am sorry I am user of automagic and I can not help you. There is not the best place to ask about it. Could you try to ask on tasker forum or tasker thread on xda ?

indo_matic said:
Hi Guys,
Running EU 10.1 and trying to configure tasker to automatically activate Airplane mode, I get the following message:
18.17.38/E Airplane Mode: 0 -> 1
18.17.38/E Airplane Mode: curval: 0 new: 1
18.17.38/E Airplane Mode: putInt airplane_mode_on/1 failed
18.17.38/E wait for 100ms
18.17.38/E wait finished
18.17.38/E result: stop task (error)
18.17.38/E Error: 1
18.17.38/MacroEdit action finished exeID 1 action no 0 code 333 status: Err next 0
Profile becomes active but task won't execute. Have not tried any other commands yet..
Any ideas as to what may be the issue?
Click to expand...
Click to collapse
Yes, are you running as root and have set Tasker to always grant root access...?

Related

[Q] How To root Iball Slide Tablet 2.3 ?

Can some one please guide how to root Iball slide tablet. Iball Tab information is given below
OS
Browser UserAgent : Mozilla/5.0 (Linux; U; Android 2.3; en-gb; iBall Slide i7011 Build/GINGERBREAD) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
Android ID : acbc4627cc4a9253
Uptime : 0 days, 1 hours, 53 minutes, 26 seconds
Uptime (without sleeps) : 0 days, 1 hours, 53 minutes, 26 seconds
BuildInfos
Android version : 2.3
Release Codename : REL
API LEVEL : 9
CPU ABI : armeabi-v7a
Manufacturer : unknown
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : smdkv210
Radio : unknown
Board : smdkv210
Brand : generic
Device : smdkv210
Display : MID Serials 2.3 GINGERBREAD 20110830.164011
Fingerprint : generic/full_smdkv210/smdkv210:2.3/GINGERBREAD/20110830.164011:eng/test-keys
Host : urbetter-linux01
ID : GINGERBREAD
Model : iBall Slide i7011
Product : full_smdkv210
Tags : test-keys
Type : eng
User : raymanfeng
Battery
Not charging...
Level : 50 %
Technology : Li-ion
Temperature : 20.0 °C (68.0°F)
Voltage : 7626 mV
Memory
Download Cache Max: 100MB/ Free: 86.45MB
data Max: 488MB/ Free: 367MB
External storage Max: 6.55GB/ Free: 6.26GB
Total RAM: 361MB
Free RAM: 159MB
Threshold RAM: 24.00MB
Low Memory Killer Levels
FOREGROUND_APP:__ 8.00MB
VISIBLE_APP:_________ 12.00MB
SECONDARY_SERVER: 16.00MB
HIDDEN_APP:________ 24.00MB
CONTENT_PROVIDER: 28.00MB
EMPTY_APP:__________ 32.00MB
Telephony
Data Activity: DATA_ACTIVITY_NONE
Data State: DATA_DISCONNECTED
IMEI(or MEID): null
IMEI/SoftVer: null
MSISDN: null
Registered MCC:
Registered MCC MNC:
Registered Operator Name:
Network Type: NETWORK_TYPE_UNKNOWN
Phone Type: PHONE_TYPE_GSM
SIM Country Code: us
SIM MCC MNC: 310004
SIM Operator Name: Verizon
SIM Serial Number: null
SIM State: SIM_STATE_UNKNOWN
Subscriber ID(IMSI): null
VoiceMail number:
Roaming: false
No Cell detected
Networks
Background Data Usage: true
type mobile[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type WIFI[]
state CONNECTED/CONNECTED
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable true
type mobile_mms[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type mobile_supl[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type mobile_hipri[UNKNOWN]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type Network3gDataStateTracker[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
type NetworkEthDataStateTracker[]
state UNKNOWN/IDLE
reason (unspecified)
extra (none)
roaming false
failover false
isAvailable false
Wifi
State: WIFI_STATE_ENABLED
CPU
Processor ARMv7 Processor rev 2 (v7l)
BogoMIPS 998.15
Features swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer 0x41
CPU architecture 7
CPU variant 0x2
CPU part 0xc08
CPU revision 2
Hardware SMDKV210
Revision 0000
Serial 0000000000000000
Frequency Stats (time):
Screen
Resolution: 800 x 480
Refresh Rate: 68.0
X factor for DIP: 1.25
Density: 200 dpi
Pixel per inch X: 144.0 dpi Y: 144.0 dpi
OpenGL
As retreiving opengl infos can crash some device, it is not enabled by default. If you wish to, go in settings menu.
Sensors
mma7660-accel: 0.2 mA by urbetter
Gravity Sensor: 0.2 mA by Google Inc.
Linear Acceleration Sensor: 0.2 mA by Google Inc.
Rotation Vector Sensor: 0.2 mA by Google Inc.
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: mounted
External Storage Directory: /mnt/sdcard
Medias Directories
Alarms: /mnt/sdcard/Alarms
DCIM: /mnt/sdcard/DCIM
Downloads: /mnt/sdcard/Download
Movies: /mnt/sdcard/Movies
Music: /mnt/sdcard/Music
Notifications: /mnt/sdcard/Notifications
Pictures: /mnt/sdcard/Pictures
Podcasts: /mnt/sdcard/Podcasts
Ringtones: /mnt/sdcard/Ringtones
Features
android.hardware.location.network
android.hardware.wifi
android.hardware.nfc
com.google.android.feature.GOOGLE_BUILD
android.hardware.location
android.hardware.sensor.gyroscope
android.hardware.bluetooth
android.hardware.touchscreen.multitouch.distinct
android.hardware.microphone
android.hardware.sensor.light
android.software.live_wallpaper
android.hardware.telephony
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.sensor.barometer
android.software.sip
android.hardware.touchscreen.multitouch
android.hardware.sensor.compass
android.hardware.camera
android.software.sip.voip
android.hardware.sensor.proximity
android.hardware.location.gps
android.hardware.telephony.gsm
android.hardware.telephony.cdma
android.hardware.camera.front
android.hardware.sensor.accelerometer
android.hardware.touchscreen
glEsVers=2.0
JavaProperties
java.vendor.
java.class.path: .
java.class.version: 46.0
os.version: 2.6.35.7
java.vendor: The Android Project
user.dir: /
user.timezone: null
path.separator: :
os.name: Linux
os.arch: armv7l
line.separator:
file.separator: /
user.name:
java.version: 0
java.home: /system
Mount points
MountPoint
Name Type Options
- /
rootfs rootfs rw
- /
ubi0:rootfs ubifs rw,relatime
- /dev
tmpfs tmpfs rw,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /proc/bus/usb
none usbfs rw,relatime,devmode=666
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /data
/dev/block/mmcblk0p3 ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
- /cache
/dev/block/mmcblk0p2 ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
- /sys/kernel/debug
/sys/kernel/debug debugfs rw,relatime
- /mnt/sdcard
/dev/block/vold/179:1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/secure/asec
/dev/block/vold/179:1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/sdcard/.android_secure
tmpfs tmpfs ro,relatime,size=0k,mode=000
- /mnt/extsd
/dev/block/vold/179:8 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.UCMobile.intl-1
/dev/block/dm-0 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.skype.raider-1
/dev/block/dm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.opera.mini.android-1
/dev/block/dm-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.eamobile.nfsshift_na_wf-1
/dev/block/dm-3 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.guidedways.iQuranPro-1
/dev/block/dm-4 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.dolphin.browser-1
/dev/block/dm-5 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/kz.mek.DialerOne-1
/dev/block/dm-6 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.adobe.reader-1
/dev/block/dm-7 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.google.earth-1
/dev/block/dm-8 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.electricsheep.asi-1
/dev/block/dm-9 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/com.joeykrim.rootcheck-1
/dev/block/dm-10 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
I tried ginger break but of no use superuser is install but not working, Here is the feedback from root Checker
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /system/busybox/bin /system/busybox/sbin /system/busybox/usr/bin /system/busybox/usr/sbin /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
-rwsr-sr-x 1 2000 2000 22228 Feb 28 2008 /system/bin/su
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
ls: /sbin/su: No such file or directory
Alternate su type binary location: ls -l /system/xbin/sudo:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your iBall Slide i7011 device by Root Checker version 3.9 from joeykrim in the Android Market
Please guide
Thanks in advance
any help from anyone regarding rooting iball slide i7011 android 2.3 tab. I have tried gingerbreak and also tried superoneclick as per guide but of no use.
both of them reports that the tab is rooted but when i try su command superuser wont give permission. its a mess up right now. and when i try to remove superuser its not done saying its a system app. and when i go to /system/apps/superuser its mounted as r/o.
can anyone help this ?????
I have tried almost all process from single click app to rooting via adb, bt failed. So I have changed its firmware, which includes a custom ROM...So using my iball slide with much more functions..
Bt there is one problem..The camera is not working..may be the device driver is not working, I am trying to develop this issue, and will be back when I will debug that..
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
ffarhan.s said:
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
first of all a big thanks to ffarhan.s.... thanks bro ur guide was fantastic and worked like charm. i rooted my tab without any glitch. thanks a lot buddy.
but something more to say for the newbies,
1. download gingerbreak.apk and save it in ur tab's sd card(which means internal 8gb memory)
2. ADB composite device may not show up in device manager so dont worry. but android adb interface must be shown in the path computer > Manage>device manager>android phones>android adb interface (its very necessary)
3. .. as ffarhan wrote > Then type [space cd space platform-tools] , without bracket.. its actually the path of your android sdk folder. assuming u have downloaded the sdk folder under c:\
so the path will be c:\android-sdk\platform-tools
then type adb devices press enter. the result may show like this :
List of devices attached
MID_serials devices
.... below this blank.dont worry its fine.
the main part is point 16 - 22. these should work as ffarhan wrote otherwise repeat the process from start.
anywyz, once again thanks ffarhan.s for the entire process. take care bro.
have a nice day
I have done this, bt for my case it was a temporary root..I think it has to be made permanent...
will "root explorer" go ?my i7011 is ok(Root Explorer 2.17).
it can mount / or other partitions as ro or rw?
btw, can u mail me the file "/system/bin/wpa_supplicant" , thanks a lot, [email protected]
ffarhan.s said:
8.Connect tab to your computer with OTG, wait until driver are installing
9.To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
Click to expand...
Click to collapse
the device manager on my computer does show any ADB interface or android Composite ADB interface. What am i doing wrong ?
New problem !!
ffarhan.s said:
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
on performing step 16, the $ sign pops up immediately and for the remaining steps i keep getting 'cannot find'. plz help me out.:fingers-crossed:
vivdutta said:
on performing step 16, the $ sign pops up immediately and for the remaining steps i keep getting 'cannot find'. plz help me out.:fingers-crossed:
Click to expand...
Click to collapse
That's not a bring problem . And the correction in 21st step that it is rm system not rm/system. Hope u get it
ffarhan.s said:
Rooting Iball Slide tab
DISCLAMER you do all this on your own risk if you break your tab don’t blame me. You may want to backup some files before messing around...
1. Full charge your slide, as we required to on/off it many times
2. Download Gingerbrak.apk , saved it to the root of you SD card
3. Make sure Unknown source and USB debugging is enable
4. One file manager and install gingerbreak.apk
5. One Gingerbreak.apk, wait until your device is off
6. Press power button, let the devices start, go to application if you see Superuser Icon there, you half work is done
7. If Superuser is not install, manually install it from market
8. Connect tab to your computer with OTG, wait until driver are installing
9. To check if deriver is install or not
Right click computer > Manage>Devices Management
And check for ADB Interface and android Composite ADB Interface if it is there that means your tab is ready for next step
10. Again on your tab click gingerbreak application, wait until your mobile is off, let it be in off for now
11. Type CMD in search, Click and run as administrator
12. Type CD.. until you reach to C:\
13. Then type [space cd space platform-tools] , without bracket
14. Power on your device, wait until you see slide boot screen than
15. type [space adb devices] enter it will show you message and List of devices attached, don’t worry even if it doesn’t shows serial no of your devices , if message come as “device not found” than you need to install OTG driver manually
16. Now enter [space adb space shell]
17. Wait for few second and type [ cd/system/bin], now you would see $ sign
18. Wait till device is completely started, unlock screen
19. And type [ ./su] that is DOT /SU
20. Now check the screen, Superuser application should ask you for permission , Click allow
21. Type [rm/system/busybox/bin/su].
22. Type exit , Exit again, Wala now you are rooted
Download root check application to check whether is rooted or not
If it doesn’t happened repeat the process again, if you have any question, just put in comment, I would love to answer it
Click to expand...
Click to collapse
well i have a few problems...i have ADB interface...that means the the drivers are installed right?but when i open gingerbreak..it does the process...but my tab shuts off...i switch it on and superuser is also there...then i connect with OTG and i guess my drivers are installed...then i dont understand what you mean by Type CD.. until you reach to C:\...what exactly am i supposed to do??can u please post screenshots...or even better...if it is not too much trouble a video on how u did it!! i really want to root my tab...but i just cant get through to it!! :|
how to root iball slide with jelly bean (6309r)
can anybody please help me and tell how to root iball slide with jelly bean (6309r):crying:
This Procedure Works for every Iball Slide Tablets
http://forum.xda-developers.com/showthread.php?p=43037172#post43037172

SOLVED: Tasker: ScreenRecord toggle task in Lollipop

Hi,
I am trying to create a set of tasks in Tasker to start and stop the screenrecord process in Lollipop.
The individual tasks to start and stop the recording work fine, but I'm trying to create a single task that starts the recording if not currently recording and stop the recording if currently recording. This works fine in starting the recording, but the stop recording part doesn't execute.
I'm calling the individual tasks for starting and stopping the recording in this unified task.
I'm trying to get the pid of the screenrecord process and based on that start or stop the recording. Any suggestions are appreciated.
Code:
---------------------------------------------------------
TASK: ScreenieOpen
---------------------------------------------------------
Variable Set
%isRunning = 0
Run Shell
command pidof screenrecord
Use Root
Store Output In -> %%isRunning
Store Errors In -> %%isRunning
Continue Task After Error
If %isRunning ~ 1 OR %isRunning ~ 0
Then
Perform Task
ScreenieStart
Stop
Else
Perform Task
ScreenieStop
End If
---------------------------------------------------------
TASK: ScreenieStart
---------------------------------------------------------
Variable Set %ScrFile to S-%DATE-%TIMES.mp4
Secure Settings
Configuration -> Show Touches Enabled
Flash
Text - Recording Started
Run Shell
command screenrecord /storage/sdcard0/DCIM/ScreenRecord/%ScrFile
Use Root
---------------------------------------------------------
TASK: ScreenieStop
---------------------------------------------------------
Secure Settings
Configuration -> Show Touches Disabled
Run Shell
kill -2 $(pidof screenrecord)
Flash
Text - Recording Stored @ /storage/sdcard0/DCIM/ScreenRecord/%ScrFile
Got it
Got it . Instead of checking for the PID, I've just used a variable for the status.
Code:
---------------------------------------------------------
TASK: ScreenieOpen
---------------------------------------------------------
If %isRunning = 0
Then
Perform Task
ScreenieStart
Stop
Else
Perform Task
ScreenieStop
Stop
End If
---------------------------------------------------------
TASK: ScreenieStart
---------------------------------------------------------
Variable Set %ScrFile to S-%DATE-%TIMES.mp4
Secure Settings
Configuration -> Show Touches Enabled
Variable Set %isRunning to 1
Flash
Text - Recording Started
Run Shell
command screenrecord /storage/sdcard0/DCIM/ScreenRecord/%ScrFile
Use Root
---------------------------------------------------------
TASK: ScreenieStop
---------------------------------------------------------
Secure Settings
Configuration -> Show Touches Disabled
Run Shell
kill -2 $(pidof screenrecord)
Variable Set %isRunning to 0
Flash
Text - Recording Stored @ /storage/sdcard0/DCIM/ScreenRecord/%ScrFile

Nexus 5 reboots every other minute since yesterday

Hi guys,
my problem is that my Nexus 5 is rebooting all the time since yesterday. My roommate had the same problem yesterday, but now its suddenly gone. My Android version is 6.0.1 and I can tell you the last few logs before the restart occures:
Code:
03-12 15:17:51.221 203-924/? D/NuPlayerDriver: reset(0xb60585e0)
03-12 15:17:51.221 203-924/? D/NuPlayerDriver: notifyListener_l(0xb60585e0), (8, 0, 0)
03-12 15:17:51.221 203-7815/? D/NuPlayerDriver: notifyResetComplete(0xb60585e0)
03-12 15:17:51.222 812-826/? I/ActivityManager: Killing 4914:android.process.acore/u0a2 (adj 15): empty #17
03-12 15:17:52.052 1908-4068/? W/ctxmgr: [AclManager]checkPermissionTypeStatus: no inject permission for { uid=10010, packageName=com.google.android.gms }. Returned permission was: PACKAGE_NOT_WHITELISTED for context name=POWER_CONNECTION, account=account#-517948760#
03-12 15:17:52.054 1908-4068/? W/ctxmgr: [AclManager]checkPermissionTypeStatus: no inject permission for { uid=10010, packageName=com.google.android.gms }. Returned permission was: PACKAGE_NOT_WHITELISTED for context name=POWER_CONNECTION, account=account#-517948760#
03-12 15:17:52.055 1908-1908/? E/ctxmgr: [PowerConnectionProducer]Could not write powerInfo=Plug state: 2 BatteryLevel: 0.77, status=Status{statusCode=unknown status code: 7503, resolution=null}
01-01 00:00:00.000 0-0/? E/Internal: device 'XXXXXXXXX' not found
I really have no idea where to start looking for the problem. I mean, the log does not tell me much about a fault or something like that and as far as I know Android does not provide crash logs on reboot.
Do you have any hints?
Ah and by the way: The only app I installed recently before the problem occured was runtastic, but removing it did not change anything.
Best regards,
Arma
Ok, it was the power button...
I would get a case that protects the power button .

[BIP] patial disconnection issues // loss of functions

My BIP irrecoverably disconnects from my iPhone every 24 - 36 hours. Strangely app notifications still work. Only way of reconnecting it to the MiFit app for syncing is to unpair, factory reset, and repair - with data loss every time.
Any ideas?
The Mi Fit log shows the following issues:
13341|1545138664421|3|BLE|-[BLETask localRunTask]- 0115 -|orBand.wait.cp.noitfy.auth -> (null)
13342|1545138664421|3|BLE|-[BandProConnectLogic waitSendCiperDataReturn]- 0295 -|wait send cipher failed.
13343|1545138664421|3|BLE|-[BandProConnectLogic startAuth]- 0177 -|等待加密数据返回失败,
13344|1545138664421|3|BLE|-[BandLogic BandConnectLogic:ConnectFailWithError:]- 1367 -|XXXX connect binded band failed with error: 54 , current oper type: 2
13345|1545138675633|3|BLECORE|-[HMBLECoreManager centralManager:didDisconnectPeripheral:error:]- 0281 -|
bluetooth did disconnect <CBPeripheral: 0x1d0315d50, identifier = 36E113F8-26F5-27BF-9223-89DEBC4BFA5D, name = Amazfit Bip Watch, state = disconnected> with :Error Domain=CBErrorDomain Code=6 "The connection has timed out unexpectedly." UserInfo={NSLocalizedDescription=The connection has timed out unexpectedly.}
13346|1545138675634|3|BLE|-[BandLogic deviceConnectDidDisconnected:withError:]- 0319 -|did disconnect: <CBPeripheral: 0x1d0315d50, identifier = 36E113F8-26F5-27BF-9223-89DEBC4BFA5D, name = Amazfit Bip Watch, state = disconnected> Error Domain=CBErrorDomain Code=6 "The connection has timed out unexpectedly." UserInfo={NSLocalizedDescription=The connection has timed out unexpectedly.}
13347|1545138695588|3|BLE|-[BandConnectLogic connectToPeripheral:]- 0638 -|connect <CBPeripheral: 0x1d0315d50, identifier = 36E113F8-26F5-27BF-9223-89DEBC4BFA5D, name = Amazfit Bip Watch, state = connecting> error Error Domain=HMBLEErrorDomain Code=5 "Time out" UserInfo={NSLocalizedDescription=Time out}
13348|1545138695588|3|BLE|-[BandConnectLogic connectToPeripheral:]- 0641 -|base connect failed.
13349|1545138695588|3|BLE|-[BandLogic BandConnectLogic:ConnectFailWithError:]- 1367 -|XXXX connect binded band failed with error: 53 , current oper type: 2
13350|1545138695590|3|BLECORE|-[HMBLECoreManager centralManager:didConnectPeripheral:]- 0263 -|
bluetooth did connected: Amazfit Bip Watch (36E113F8-26F5-27BF-9223-89DEBC4BFA5D)
13351|1545138697527|3|BLE|-[BandProConnectLogic readConnectIntervalParameter]- 0483 -|Read Connect Interval: min:24,max:24,latency:0,timeout:72
13352|1545138697940|3|BLE|-[BLEOperatingRoom waitNotify:]- 0293 -|等待任务 wait.cp.noitfy.auth 失败(<100307>) 或者超时(5000).
13353|1545138697940|3|BLE|-[BLEDeviceOperatingRoom doOPWait:]- 0287 -|task failed: [MF]-orBand-wait.cp.noitfy.auth-5(s)-(null), -, [SD]-
(null)
FEE1
00000009-0000-3512-2118-0009AF100700-notifying=1
(null)
{
kNotifyCompareType = checkResult;
}
, [RD]-
13354|1545138697940|3|BLE|-[BLETask localRunTask]- 0115 -|orBand.wait.cp.noitfy.auth -> (null)
13355|1545138697940|3|BLE|-[BandProConnectLogic waitSendCiperDataReturn]- 0295 -|wait send cipher failed.
13356|1545138697940|3|BLE|-[BandProConnectLogic startAuth]- 0177 -|等待加密数据返回失败,
13357|1545138697940|3|BLE|-[BandLogic BandConnectLogic:ConnectFailWithError:]- 1367 -|XXXX connect binded band failed with error: 54 , current oper type: 2
13358|1545138770014|3|public|+[HMBGFetchWeatherTask startFetchingAndWriteWeatherWithCompletion:]- 0018 -|starting weather data requesting.....

Tutorial: Gear S for Tab Active 2

Work in progress to make it work on a samsung tablet running android 7.1.1
Can get the watch to be seen by gear manager but it fails during set up.
This is a list of trial and errors at the moment - please add any ideas you have.
Install magisk /root
Install Magiskhide props config
Install terminal emulator
install busybox via magisk downloads
terminal emulator -> props
Add new custom value
ro.product.model
Was SM-T395
Set to GT-N7105 (note 2)
1. default (current)
y
Boots OK
Safetynet pass
download wear
download amaze file manager
navigate to /data/data/com.samsung.android.app.watchmanager/files/rules.xml
edit to allow tablets=true
set it read only(!)
restart
Safetynet pass
run gear wearables & connect
--------------Beyond this it's a bit of a guess. Trying gearmanagerstub.apk but no luck yet.
--------------Currently fails after 5-10 seconds of 'connecting to gear', which displays on phone and watch.
Sees watch and connects also shows connecting on the watch but then the app bombs back to a list of devices. So it passes the initial device checks at least, but gear2splugin is failing somehow
Maybe I need gearmanagerstub Will try downloading Note 8 7.1.1 firmware see if there is a gearmanagerstub. Yes it has one.
& use magisk app systemiser module....
terminal -> systemize
option 3
enter path of gearmanagerstub.apk e.g. /sdcard/GearManagerStub.apk (where I put mine)
where to install? 1. /system/app
Nothing shows in /system/app... watchmanager bombs again
try restart
Interesting it keep updating rules.xml now.... it is back to supports tablet=false. Both after restart, and then after starting watchmanager. (I edited it after boot then checked again)
fix is set rules.xml to read only.
So perhaps an older version of gearmanagerstub would do the trick.. (I'm using the oldest note 8 one)
run terminal ->systemize
revert app - select 1- (null??)
install note 3 5.0 gearmanagerstub.apk same process
After another failure to connect it got further to ELUA screen before bombing.
I see it thinks my watch is installed now...
It connects for maybe 10 seconds hits "back up and restore" and immediately bombs. The app acts like it is working but the gear says it's not "failed to connect"
Suddenly pops up "error your gear is disconnected" on the restore page.
Now it's back to failing after 5 seconds / 10 spins.
tried copying gearmanagerstub to /system/app and reinstalling all, no difference
This did not trigger safetynet.
Try setting to SM-950F... no change.
Try setting fingerprint to note 8 (SM-950F) (8.0 although I am running 7.1.1)
try ro.build.characteristics=phone,emulator (currently tablet,emulator)
This gives a different list of devices (watches not just earphones) when I reinstalled gear manager.
Still bombs, also the icon is still a tablet when connecting, not a phone.
If anyone has figured this out already I'm all ears
could try non samsung next
https://forum.xda-developers.com/showpost.php?p=79230009
or other ideas
https://www.youtube.com/watch?v=nKH1ykQR4iQ
Update- bluetooth crash in logcat
Looking at logcat and the apks it appears that watchmanager only checks to see if the watch is 'non samsung'. How it decides that an GT-N7105 magically makes it a samsung product but a T395 is not, I can't figure it out.
Interestingly modifying rules.xml and simply adding supportsnonsamsung = true seems to work.
In any case logcat shows a bluetooth error/crash. Why it crashes I don't know.
It looks like the trigger is
11-14 13:35:56.237 4853 4853 E SACalendarProvider::Service: CALENDAR_HOSTMANAGER_CONNECT
Shortly after this a lot of data seems to be sent over bluetooth. A few seconds later the data stops, and 200ms later an error:
11-14 13:35:59.786 3525 3609 E bt_hci : command_timed_out [BT_CORE] hci layer timeout waiting for response to a command. opcode: 0xffff
Nothing interesting happens in logcat in the 2 seconds of data transfer.
A while later the app detects that the watch is disconnected
and eventually bombs. A few seconds after that the watch reports setup fail.
Here is a list of interesting error codes
11-12 12:18:58.417 31815 31832 E BluetoothDataManager: getUartErrorInfo 000 000 000 000
11-12 12:18:58.417 31815 31832 E BluetoothDataManager: "LO_MFN":"29","LO_LMP":"8","LO_SUB":"602","LO_FWV":"BTFM.TF.1.3-00036-QCATFSWPZ-1","ERROR_REASON":"225","UART":"000 000 000 000"
11-12 12:18:58.599 22777 31958 E SABtServerListener: SA_ERROR: IOexception in UUID xxx-xxx-xxx-xxx-xxx ::Exiting Now
11-12 12:18:58.601 3600 4901 I ActivityManager: Process com.android.bluetooth (pid 31815) has died(68,798)
Here is a list of things that crashed
11-12 12:18:58.611 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.btservice.AdapterService in 1000ms
11-12 12:18:58.612 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hdp.HealthService in 11000ms
11-12 12:18:58.614 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hid.HidService in 10997ms
11-12 12:18:58.617 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.map.BluetoothMapService in 10994ms
11-12 12:18:58.618 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.a2dp.A2dpService in 10993ms
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.gatt.GattService in 10992ms
11-12 12:18:58.619 22777 22808 D SADiscoveryCore: handling msg: DEVICE_ACCESSORY_LOST...
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/com.samsung.ble.BleAutoConnectService in 20992ms
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hid.HidDevService in 30992ms
11-12 12:18:58.620 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 30991ms
11-12 12:18:58.620 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.sap.SapService in 30991ms
I am not sure what causes this error.
I tried many versions of gear2plugin which contains the apks such as SAproviders / SAcalendarprovider code..
It seems that the bluetooth process under hostmanager-connectionmanager-databuilder works for "single chunk" but with fragmented data it receives 12 chunks of 61k (or so) before dying.
any ideas?
Just FYI
The same T395 tab-phone works pairing a Gear S3 which uses a different plugin 'gearoplugin', with rules.xml edited to say support tablet = true and set to read only. No other tricks are needed I think as supportnonsamsung is already true, all connected to the internet etc. Obviously you need root to edit rules.xml.
= Gear S plugin V2.2.03.19032541N
= Galaxy Wearable V2.2.27.19083061
The gear s uses gear2smodule. I tried the latest version I could find 2118120361, which didn't work.
aka GearModule Version 2.2.02.18120361
Does anyone have a later version?

Categories

Resources