Tutorial: Gear S for Tab Active 2 - Samsung Gear S

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?

Related

com.android.systemui keeps crashing when charging level at 100%

Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961

[1.117.0306] Latest Gear Fit Manager non-Samsung + Endomondo [4.x/5.x compatible]

Hello,
I've patched the current version of the Gear Fit Manager (v. 1.117.0306) built on 2015, March 06 and released at the end of March.
Links updated on 2015, April 19. Calls are fixed. I'm investigating on the issue with Lollipop 5.1 .
Test version for 5.1 : https://mega.co.nz/#!bEdXAQhb!i5hxkgyzEI43fBWa6ThfIiPUI2U2V2gdVeXY5AGWHg8 [Test 1 - try to use the 5.1 API]
https://mega.co.nz/#!GFcHUAhI!snmHX91S4PJwJZlPtCTMDUjOv36EKeaaKrS54UX2PtY [Test 2 - try to bypass one section]
This version is based on the last official Samsung version compatible with Lollipop. I patched the apk to be compatible with non Samsung phones. To install this version you need to install the following packages (I advice you to install in that order).
Gear Fit Manager and requirements
This firmware to update with Odin: R350XXU0BOA2
https://mega.co.nz/#!qUskxIDL!wexEZQTZ6t6wk0jO6dv1JDsdT6oCDYBxlegMb-MS6qc
This apk which is the main application: Gear Fit Manager
https://mega.co.nz/#!nI0UyJJD!zYFvTolgxAgL39ydX9ZgHCson5K2TJxMx9_-BKOa--A
This apk which contains required components: Gear Fit Installer (it's actually embedded into the second apk but it has to be installed manually)
https://mega.co.nz/#!mFknlTZB!iIB7DWPQC5ECiPlNcum0JXpcJRuE4XmI7v6Drchgk3Y
Your build.prop must NOT contain "samsung", just keep the default values for your device.
App Connect Applications :
Endomondo 11.0.3:
https://mega.co.nz/#!Kd82hawL!lGt2pJbBCfvO7bQ52fI4VgtOufMHLQVEozqWt7ziY84
To connect via Facebook you need to delete the app from your profile (https://www.facebook.com/help/170585223002660) if you already used it before, else you will have a login loop. The normal login via mail also works.
Endomondo is not able to use the Heart Rate monitor from the watch, this is normal (https://support.endomondo.com/hc/en-us/articles/201784416-SmartWatches#gear).
Calculator 2.0:
https://mega.co.nz/#!jFNDQDoJ!oIqRjQY_4oBrCMbygSB4HZfsAt7K1AWW2gg7KvTx1UA
I'll try to keep this topic up to date with the last version available on :
http://forum.xda-developers.com/showthread.php?t=2789503
I guarantee that the software is 100% safe. I will detail the reverse engineering done to make the new versions of the manager to work properly on non-Samsung devices.
Working :
Bluetooth connection
Clocks
Notifications
Media control
Custom clocks
Heart Rate
Reject Calls
SMS Quick Reply
Find my phone
Partially working :
App Connect (the manager cannot be signed properly so you will always get the "You should install Gear Fit Manager application first" message. This can be fixed but no so easily (the app have to be patched to not check the signature). If you want an app, post the apk here and I will patch this app.
Not working :
Anything related to SHealth / Weather as it requires Touchwiz (Endomondo is a good SHealth alternative)
Updates
19/04/2015 : Added Endomondo and Calculator apps.
19/04/2015 : Crash when receiving calls fixed.
Thanks for baking this. I can live without the weather, but I miss the caller ID notifications.
This isn't working on my 5.1 Nexus 6. I get a force close upon opening it. Firmware is at BOA2 and I installed the smaller file, then the first. Anything I can do to help troubleshoot this? It was a clean install on this phone.
It should work with 5.0.2 (tested with my OnePlus One with OxygenOS). I never tried with 5.1 yet. Could you send me a logcat please ? If it's a force close on launch I think it should be fixable.
koalala said:
Hello,
I've patched the current version of the Gear Fit Manager (v. 1.117.0306) built on 2015, March 06 and released at the end of March.
This version is based on the last official Samsung version compatible with Lollipop. I patched the apk to be compatible with non Samsung phones. To install this version you need to install :
- This firmware with Odin (R350XXU0BOA2) :
https://mega.co.nz/#!WFF2XaAD!slUq8FE4D3cvTCIMrI4THnOPlR2GBttRLRyOgm379r8
- This apk which contains required components : Gear Fit Installer (it's actually embedded into the second apk but it has to be installed manually)
https://mega.co.nz/#!mFknlTZB!iIB7DWPQC5ECiPlNcum0JXpcJRuE4XmI7v6Drchgk3Y
- This apk which is the main application : Gear Fit Manager
https://mega.co.nz/#!WFF2XaAD!slUq8FE4D3cvTCIMrI4THnOPlR2GBttRLRyOgm379r8
Your build.prop must NOT contain "samsung", just keep the default values for your device.
I'll try to keep this topic up to date with the last version available on :
http://forum.xda-developers.com/showthread.php?t=2789503
I guarantee that the software is 100% safe. I will detail the reverse engineering done to make the new versions of the manager to work properly on non-Samsung devices.
Working :
Bluetooth connection
Clocks
Notifications
Media control
Custom clocks
Heart Rate
Reject Calls
Find my phone
Partially working :
App Connect (the manager cannot be signed properly so you will always get the "You should install Gear Fit Manager application first" message. This can be fixed but no so easily (the app have to be patched to not check the signature). If you want an app, post the apk here and I will patch this app.
Not working :
Anything related to SHealth / Weather as it requires Touchwiz
Click to expand...
Click to collapse
So great. I waiting for a long time
Will re-install Lolipop on my 6653 and feedback to you soon.
Again, thanks you
Update: Could you please update the frimware link? My gear fit running R350XXU0BNG2 and CAN NOT pair with my Sony Z3 D6653
Thank you for the remark I didn't see that the hyperlink was broken. It's corrected now, you can download the last firmware.
works
wish endomondo can be work in this version could u plz patch this app?? ... btw thank you for your big help:good::good::good:~ it works on my android 5.0 phone. i flash my gear firm by odin3.0.9.5 in csc bar
Log Cat from Stock 5.1 Nexus 5
koalala said:
It should work with 5.0.2 (tested with my OnePlus One with OxygenOS). I never tried with 5.1 yet. Could you send me a logcat please ? If it's a force close on launch I think it should be fixable.
Click to expand...
Click to collapse
Code:
D/AndroidRuntime(19780): Shutting down VM
E/AndroidRuntime(19780): FATAL EXCEPTION: main
E/AndroidRuntime(19780): Process: com.samsung.android.wms, PID: 19780
E/AndroidRuntime(19780): java.lang.RuntimeException: Unable to create service com.samsung.android.wms.service.WingtipManagerService: java.lang.ClassCastException: int[] cannot be cast to long[]
E/AndroidRuntime(19780): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2771)
E/AndroidRuntime(19780): at android.app.ActivityThread.access$1800(ActivityThread.java:151)
E/AndroidRuntime(19780): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1386)
E/AndroidRuntime(19780): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(19780): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(19780): at android.app.ActivityThread.main(ActivityThread.java:5254)
E/AndroidRuntime(19780): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(19780): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(19780): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
E/AndroidRuntime(19780): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
E/AndroidRuntime(19780): Caused by: java.lang.ClassCastException: int[] cannot be cast to long[]
E/AndroidRuntime(19780): at com.samsung.android.wms.service.notification.CallAdapterForLollipop.registerPhoneStateListener(CallAdapterForLollipop.java:150)
E/AndroidRuntime(19780): at com.samsung.android.wms.service.notification.CallAdapterForLollipop.onCreate(CallAdapterForLollipop.java:110)
E/AndroidRuntime(19780): at com.samsung.android.wms.service.WingtipManagerService.initAdapters(WingtipManagerService.java:1641)
E/AndroidRuntime(19780): at com.samsung.android.wms.service.WingtipManagerService.onCreate(WingtipManagerService.java:1275)
E/AndroidRuntime(19780): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2761)
E/AndroidRuntime(19780): ... 9 more
W/ActivityManager( 738): Force finishing activity 1 com.samsung.android.wms/.app.base.ContentsActivity
I/WindowManager( 738): Screenshot max retries 4 of Token{26383230 ActivityRecord{b658373 u0 com.samsung.android.wms/.app.base.ContentsActivity t689 f}} appWin=Window{2394e09a u0 com.samsung.android.wms/com.samsung.android.wms.app.base.ContentsActivity} drawState=1
I/OpenGLRenderer( 738): Initialized EGL, version 1.4
W/ActivityManager( 738): Activity pause timeout for ActivityRecord{b658373 u0 com.samsung.android.wms/.app.base.ContentsActivity t689 f}
W/LocationOracleImpl(17839): Best location was null
W/ResourceType( 1111): No package identifier when getting value for resource number 0x00000000
W/PackageManager( 1111): Failure retrieving resources for com.samsung.android.wms: Resource ID #0x0
D/TaskPersister( 738): removeObsoleteFile: deleting file=687_task_thumbnail.png
D/PhoneStatusBar( 1111): disable: < expand ICONS* alerts SYSTEM_INFO* back home recent clock search >
D/NuPlayerDriver( 188): stop(0xb590d8e0)
W/MessageQueue( 1111): Handler (android.media.MediaPlayer$EventHandler) {36f23de2} sending message to a Handler on a dead thread
W/MessageQueue( 1111): java.lang.IllegalStateException: Handler (android.media.MediaPlayer$EventHandler) {36f23de2} sending message to a Handler on a dead thread
W/MessageQueue( 1111): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:325)
W/MessageQueue( 1111): at android.os.Handler.enqueueMessage(Handler.java:631)
W/MessageQueue( 1111): at android.os.Handler.sendMessageAtTime(Handler.java:600)
W/MessageQueue( 1111): at android.os.Handler.sendMessageDelayed(Handler.java:570)
W/MessageQueue( 1111): at android.os.Handler.sendMessage(Handler.java:507)
W/MessageQueue( 1111): at android.media.MediaPlayer.postEventFromNative(MediaPlayer.java:2670)
D/NuPlayerDriver( 188): reset(0xb590d8e0)
D/NuPlayerDriver( 188): notifyResetComplete(0xb590d8e0)
I/ActivityManager( 738): Process com.google.android.apps.docs (pid 17663) has died
D/PhoneStatusBar( 1111): disable: < expand icons* alerts system_info* back home recent clock search >
koalala said:
Hello,
I've patched the current version of the Gear Fit Manager (v. 1.117.0306) built on 2015, March 06 and released at the end of March.
Click to expand...
Click to collapse
Thank you very much. It works on my Nexus 4 with 5.0.1 stock.
I think my logcat is saying the same thing as the previous one.
[Nexus 6 w/ 5.1 ROM]
Code:
[ 04-10 18:34:15.309 4238: 4238 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.samsung.android.wms, PID: 4238
java.lang.RuntimeException: Unable to create service com.samsung.android.wms.service.WingtipManagerService: java.lang.ClassCastException: int[] cannot be cast to long[]
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2771)
at android.app.ActivityThread.access$1800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1386)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.ClassCastException: int[] cannot be cast to long[]
at com.samsung.android.wms.service.notification.CallAdapterForLollipop.registerPhoneStateListener(CallAdapterForLollipop.java:150)
at com.samsung.android.wms.service.notification.CallAdapterForLollipop.onCreate(CallAdapterForLollipop.java:110)
at com.samsung.android.wms.service.WingtipManagerService.initAdapters(WingtipManagerService.java:1641)
at com.samsung.android.wms.service.WingtipManagerService.onCreate(WingtipManagerService.java:1275)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2761)
... 9 more
Working on Xperia Z2 android 4.4.2 stock/rooted
This is my first attempt to make the gear fit work on a non-samsung device and it's working as informed. Was hoping to get endomondo working thru appconnect, so I'm also looking forward for that patch. Congratulations koalala on this accomplishment and keep up the good work!
This seems to be working on my Nexus 5. Thanks a bunch!
bugs found
Incoming call notify doesn't work. Gear fit will disconnect when there is incoming call and so as the gear for manager
Hi man! You have my all attention
I have Lenovo A806 with Mediatek and Android 4.4.2. It's not possible to connect. Pairing is ok. Logcat is included and I will help you as much as I can, so don't hesitate contact me.
Logcat from line 2381 I think.
Thank you very much!!
Hi, I´m trying to use the app "gear fit share", but i don´t know how i can signed (it show "the manager is not signed" message).
How can i do it?
Is there any tutorial for this?
Thanks!!!
Search tutorial in thread "gear fit manager on non Samsung devices" on xda
Sent from my nexus 4 using XDA Free mobile app
1.117.030622
I have stock rooted Sprint phone and got the 1.117.030622 update and it won't connect anymore. I tried resetting everything still no luck.
hi
followed instructions and the firmware B02 by odin
installed apks, paired with my phone, but it stays on "connect to the device" when in the app, it cant go to the gear
any idea?
logcat joined if any help?
Incoming call notify doesn't work,nexus 4 aicp 5.0.2
hi, i want to use the app "gear fit launcher" to launch tasker shortcuts.
It was hard to find the apk because it isn't available at the playstore anymore.
sadly if i try to activate the app it says "manager not signed"
is there any way to get around this?
if you need the apk, i can upload it for you
adrian_cwchow said:
Incoming call notify doesn't work. Gear fit will disconnect when there is incoming call and so as the gear for manager
Click to expand...
Click to collapse
I have the same problem with my sony xperia z3 compact with 5.0.2

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 .

Mystery Lenovo K6 acting weird with stock firmware, need help

Hello,
I have recently purchased a refurb Lenovo K6, it came with an Android 6.0 rom.
Off the bat it had some weird reboots and app crashes, updating and system restore solved nothing; the problem worsened, so I ended up using the official Lenovo tools to perform a system recovery, which flashed a stock Nougat rom (K33_USR_S223_1706101140_Q00440_ROW).
This didn't stop sudden app crashes and system restarts however; even at initial system setup, many apps including Google Play Services would stop responding.
Since then I've lost count of re-flashes, data and cache wipes, permission resets etc. that I've performed.
I've attempted to root the phone with KingRoot in order to wipe the Dalvik Cache but could not complete the process.
I got plenty of logs via logcat, wish you could help me understand what's going on using them; here is a small one (Error level treshold) that I got, includes crashes of Firefox, Lenovo Launcher and I think Google Play Services.
pastebin. com/sZkDYPXi
I got other bigger ones, as well.
Mainly I notice a lot of "no such file or directory" errors, such as:
Code:
07-24 14:46:13.852 1447 1667 E QCOM PowerHAL: Error opening sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: No such file or directory
and a lot of SELinux permission denials:
Code:
07-24 14:31:22.373 474 474 E SELinux : avc: denied { find } for service=android.hardware.fingerprint.IFingerprintDaemon pid=2905 uid=10112 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:fingerprintd_service:s0 tclass=service_manager permissive=0
In another log with Warning treshold I was getting a lot of PackageManager warnings such as these:
Code:
07-22 19:34:36.255 5135 5135 W PackageManager: Not granting permission android.permission.ACCESS_FINE_LOCATION to package com.skype.raider because it was previously installed without
Code:
07-22 19:31:12.912 1422 1595 W PackageManager: Permission com.google.android.googleapps.permission.GOOGLE_AUTH from package com.google.android.gsf in an unknown group android.permission-group.ACCOUNTS
I'd rather try to fix the problem myself if at all possible, rather than returning the phone...
Thanks a lot for your help.
I now suspect there has been a failed root attempt on this device, as many errors have to do with denied permissions.
Also I managed to get a new logcat from many Firefox/Google Play Services and a system reboot, and the following line appears:
Code:
07-24 19:12:21.346 10637 10647 F art : art/runtime/gc/collector/mark_sweep.cc:448] Attempting see if it's a bad root
Also firefox crashes report this:
Code:
07-24 19:10:16.979 6598 6954 E InputDispatcher: channel '28475f0 org.mozilla.firefox/org.mozilla.gecko.BrowserApp (server)' ~ Channel is unrecoverably broken and will be disposed!
and apparently can't read session files:
Code:
07-24 19:10:42.340 10412 10426 E GeckoApp: An error occurred during restore, switching to backup file
07-24 19:10:42.340 10412 10426 E GeckoApp: org.mozilla.gecko.GeckoApp$SessionRestoreException: Could not read from session file
and the backtrace reports failure of some sort with async threads...
I really am banging my head against a wall here :crying:
bumpity bump bump

What process causes "Invalid Battery"

Hello.
If booting magisk-patched image, my old LG K3 K100 (doing it for fun) shuts down with "invalid battery" pop-up. It works fine when booting stock boot.img so my question is:
how to find what process/config/apk forces the phone to shut down?
My guess: from adb use ps or top or logcat or pm uninstall --user 0 an apk or browse files in root directory, sadly I have like 20 seconds of which 10 are taken to grant root permission, making it hard to guess.
I'm new so cannot post normal links.
pastebin.co m/eWz7FZ2W - pm list packages
pastebin.co m/eMGSMfSM - ps
pastebin.co m/qh1ysb2j - top
pastebin.co m/YS3exaCY - logcat
likely interesting starting from the line below:
08-01 10:12:25.763 1114 1714 I ActivityManager: START u0 {act=android.intent.action.ACTION_REQUEST_SHUTDOWN flg=0x10000000 cmp=com.lge.shutdownmonitor/.LGShutdownActivity (has extras)} from uid 10045 on display 0
Update: when booting to rooted magisk image, there are more packages, namely NFC ones, despite the phone has no NFC
com.lge.NfcSettings
com.lge.ims.rcsstarter
com.lge.rcscall
com.lge.ims.rcsprovider
com.android.nfc
Removing them during that 20 second frame doesn't help, and they are reinstalled on boot.

Categories

Resources