Database Users

[Q] Bluetooth Freeze system/bin/btld

Hi all,
There's a weired issue regarding bluetooth connections (Freeze, Reboots).
Now i located the process which makes the device so slow:
with 'top -n 1' comes the following result (adb shell):
Code:
User 95%, System 1%, IOW 0%, IRQ 0%
User 289 + Nice 2 + Sys 4 + Idle 9 + IOW 0 + IRQ 0 + SIRQ 0 = 304
PID CPU% S #THR VSS RSS PCY UID Name
4964 125% S 10 20332K 2152K fg bluetoot /system/bin/btld
5100 1% R 1 836K 404K fg root top
3070 0% S 9 215000K 23768K bg app_3 com.android.bluetooth
2599 0% S 8 231232K 37832K fg app_50 com.android.wallpaper
2495 0% S 58 327856K 67728K fg system system_server
6 0% S 1 0K 0K fg root khelper
10 0% S 1 0K 0K fg root async/mgr
13 0% S 1 0K 0K fg root suspend
14 0% S 1 0K 0K fg root sync_system_wor
256 0% S 1 0K 0K fg root sync_supers
258 0% S 1 0K 0K fg root bdi-default
260 0% S 1 0K 0K fg root kblockd/0
269 0% S 1 0K 0K fg root kseriod
280 0% S 1 0K 0K fg root kmmcd
287 0% S 1 0K 0K fg root bluetooth
303 0% S 1 0K 0K fg root kconservative/0
313 0% S 1 0K 0K fg root kadctsd
330 0% S 1 0K 0K fg root khungtaskd
331 0% S 1 0K 0K fg root kswapd0
379 0% S 1 0K 0K fg root aio/0
if i kill the process '4964 ' (kill -9 4964)
the system works fine again (just bluetooth doesn't until you restart it)
How to make your SGT freeze:
I've tried it with several Bluetooth devices and the BT_Serial_Tester:
Just bond your device, run BT_Serial_Tester -> Paired Devices and selcet your device. If BT Connected shows "true" then after exiting the software the sgt will freeze.
Our test devices:
RoyalTek RBT-1000
BlueSerial RS232 Adapter
firmtech btwin RS232 Adapter
So here's the mighty question: Is it possible to restart the /system/bin/btld process in a secure way?
Or are there other ROMs which have fixed the issue?
thanks in advance
Tom

From my experience, all Galaxy based devices have sometimes troubles when loading firmware in hciattach. There are some patches floating that try to rest bluetooth before loading firwmare, but none of that seems to fix anything for my CyanogenMod7 builds. I modified the code that starts bluetooth to stop hciattach service (which calls brcm_patchram_plus) after a timeout so BT can be restarted manually.
See https://github.com/cmsgs/android_device_samsung_galaxytab/blob/master/patches/bluetooth.c.patch

Thanks for your reply.
So am i right that:
- there's a bluetooth issue regarding several devices (for me is the SPP important)
- no fix availble
- the only 'workaround' is to kill the btld process and manually restart bluetooth.
Ok that's really bad news i think. On my HTC desire HD there's no such problem (nevertheless there are some Errors regarding Bluetooth in the LogCat)
thanks
Tom

t3e said:
Thanks for your reply.
So am i right that:
- there's a bluetooth issue regarding several devices (for me is the SPP important)
- no fix availble
- the only 'workaround' is to kill the btld process and manually restart bluetooth.
Ok that's really bad news i think. On my HTC desire HD there's no such problem (nevertheless there are some Errors regarding Bluetooth in the LogCat)
thanks
Tom
Click to expand...
Click to collapse
If you are using official Samsung ROM you should complain to them about it.
As for Inspire 4G (same thing as Desire HD), it's cool but the battery life sucks, especially compared to the Tab ;-) I am running Revolution 3.2 ROM on my Inspire and the gps is broken -;(

I have the same bug with the original ROM from Bell
I am able to reproduce the bug most of the time with Sports tracker after about 10-20min with my Zephyr HxM
with CM7 there's no problem

I think i got a solution for us
We've designed our software to exit it when the user hit "Exit".
(System.exit(0) surely not recommended) So and thats why the SGT starts to freeze.
now we don't kill our process and the SGT don't freeze.
But the annoying part is, when you're debugging..
Each time you want to debug your software, the running app is killed on the SGT and the issue is back on...

[Q] 10.1v does not recognize any SIM anymore

the following now happened for the third time in 2 weeks:
suddenly there is no Internet connection via UMTS/GSM anymore. When I shutdown / restart the tablet, I don't get a prompt for the SIM-PIN anymore. No Internet connection is possible.
The first two times I factory reset the device and things were fine again for a few days. Now it happened again ...
Some facts:
- a standard Vodaphone Galaxy Tab 10.1v,
- no firmware changes,
- not rooted,
- lots of space on the /sdcard
Code:
Filesystem Size Used Free Blksize
/dev 363M 32K 363M 4096
/mnt/asec 363M 0K 363M 4096
/mnt/obb 363M 0K 363M 4096
/system 251M 193M 58M 4096
/cache 188M 4M 184M 4096
/data 14G 3G 10G 4096
/efs 11M 8M 3M 4096
/mnt/sdcard 14G 3G 10G 4096
Any ideas are very welcome

I got Root for my Fire TV Stick 5.0.5.1!

I just got a Pixi 7 from T-mobile on thursday, and there is a app on the Play Store called Kingo ROOT that I used to root my Pixi. So I used AGK Fire, and loaded it onto my Fire Stick, and ran it. I also had to put SuperUser on the Fire Stick. Now I have root, and disabled the Blacklist, and ota updates.
If this is known, and a guarded secret, please let me know
I was surprised that it worked

Which Kingo root app (imagine you type in Kingo root) is it the first selection? from the playstore did you use? Im wanting my fire stick 5.0.5.1 Rooted also. Cheers

@jaminmc
do you mean that one? https://www.kingoapp.com/

Tried 5 times now and I get root failed. Im using the one downloaded straight from www.kingoapp.com. Maybe he used a different version?

sconnyuk said:
Maybe he used a different version?
Click to expand...
Click to collapse
He used the play store version

Rooting app in playstorw? That won't last long. Lol
Sent from my iPhone using Tapatalk

Yes I read that he used playstore version but when I try to get the playstore version I cant seem to find it, so went directly to the website of the app he used. I tried v3.1 and no success.

@jaminmc Can you link us to the play store app?

Im currently waiting on a replacement fire tv stick to arrive tomorrow and im wondering if its going to come on 5.0.5 or 5.0.5.1 any idea people?

Tried all 3 versions of Kingo root. 2.5, 2.9 and 3.1. None have been successful in rooting 5.0.5.1. I can only assume the op is mistaken.?

Here is the exact APK I used. I also had to have the app "Rotate screen orientation " lock all apps in landscape mode, as kingo wants to open in portrait.
Below should be all you need...
You will need a mouse, or I just used "RemoteMouse" with my iPhone.
The first time I ran it, I thought it froze, and I held the center, Play-pause buttons to reboot the Fire Stick, and on reboot, I ran it again, and it worked. While it was rebooting, the progress bar started moving. SuperUser needs to be installed for it to work.

I Installed BusyBox, as uname isn't on the Fire Stick by default. I also did the Home button double-press disable as proof that it is on 5.0.5.1
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # uname -a
Linux localhost 3.0.31+ #3 SMP PREEMPT Sun May 15 01:19:40 UTC 2016 armv7l GNU/Linux
[email protected]:/ # cat /proc/cmdline
console=none androidboot.hardware=montoya androidboot.selinux=enforcing [email protected] lpj=12001280 androidboot.serialno=70940507607XXXXX s.irdrop=534 silicon.type=Typical_Fast usb_charge_type=wall_charger uboot_timestamp=2015-11-12
[email protected]:/ # pm disable com.amazon.venezia/com.amazon.venezia.list.AppsLibraryDeeplinkEventReceiver
Component {com.amazon.venezia/com.amazon.venezia.list.AppsLibraryDeeplinkEventReceiver} new state: disabled
[email protected]:/ # top
User 10%, System 4%, IOW 0%, IRQ 0%
User 51 + Nice 11 + Sys 29 + Idle 521 + IOW 0 + IRQ 0 + SIRQ 0 = 612
PID PR CPU% S #THR VSS RSS PCY UID Name
144 0 3% S 18 57844K 4144K fg system /system/bin/surfaceflinger
3091 1 3% S 74 1055380K 42464K fg u0_a23 com.waxrain.airplaydmr
5361 0 2% S 40 1099740K 54800K fg amz_u0a4 com.amazon.bueller.photos
3235 0 1% S 70 1047828K 41356K bg amz_u0a3 com.amazon.whisperlink.core.android
5782 0 0% R 1 2500K 984K fg root top
51 0 0% S 1 0K 0K fg root VCHIQ-0
29 1 0% S 1 0K 0K fg root ksmd
1225 0 0% S 1 0K 0K fg root usb-thread
3148 0 0% S 1 964K 180K fg u0_a23 /data/data/com.waxrain.airplaydmr/files/wdog2
52 0 0% S 1 0K 0K fg root VCHIQr-0
1167 0 0% S 22 989300K 28336K fg system com.amazon.device.services
1060 1 0% S 91 1076764K 65484K fg system system_server
15 1 0% S 1 0K 0K fg root i2c_master_rese
16 1 0% S 1 0K 0K fg root i2c_master_rese
17 1 0% S 1 0K 0K fg root knllog
18 0 0% S 1 0K 0K fg root sync_supers
19 0 0% S 1 0K 0K fg root bdi-default
20 1 0% S 1 0K 0K fg root kblockd
21 0 0% S 1 0K 0K fg root kworker/0:1
22 0 0% S 1 0K 0K fg root khubd
23 1 0% S 1 0K 0K fg root cfg80211
24 1 0% S 1 0K 0K fg root kworker/1:1
25 1 0% S 1 0K 0K fg root rpciod
26 1 0% S 1 0K 0K fg root bcm_hsotgctrl_e
27 1 0% S 1 0K 0K fg root khungtaskd
28 1 0% S 1 0K 0K fg root kswapd0
30 0 0% S 1 0K 0K fg root fsnotify_mark
31 1 0% S 1 0K 0K fg root nfsiod
32 1 0% S 1 0K 0K fg root crypto
50 0 0% S 1 0K 0K fg root VCHIQka-0
53 1 0% S 1 0K 0K fg root VCHIQs-0
54 0 0% S 1 0K 0K fg root vc-watchdog
55 1 0% S 1 0K 0K fg root kworker/u:1
62 1 0% S 1 0K 0K fg root dwc_otg
63 1 0% S 1 0K 0K fg root DWC Notificatio
64 1 0% S 1 0K 0K fg root f_mtp
65 1 0% S 1 0K 0K fg root file-storage
66 1 0% S 1 0K 0K fg root kinteractiveup
67 1 0% S 1 0K 0K fg root SPUM proc threa
68 1 0% S 1 0K 0K fg root SPUM done threa
73 1 0% S 1 0K 0K fg root SPUM proc threa
74 1 0% S 1 0K 0K fg root SPUM done threa
79 1 0% S 1 0K 0K fg root binder
80 1 0% S 1 0K 0K fg root irq/156-caph-in
81 1 0% S 1 0K 0K fg root AudioCtrlWq
82 1 0% S 1 0K 0K fg root VC-FB-Read
83 0 0% S 1 0K 0K fg root SMIO
1 1 0% S 1 920K 404K fg root /init
85 0 0% S 1 0K 0K fg root mmcqd/0boot0
86 0 0% S 1 0K 0K fg root mmcqd/0boot1
87 0 0% S 1 0K 0K fg root mmcqd/0rpmb
88 0 0% S 1 900K 212K fg root /sbin/ueventd
90 0 0% S 1 0K 0K fg root jbd2/mmcblk0p15
91 1 0% S 1 0K 0K fg root ext4-dio-unwrit
94 1 0% S 1 0K 0K fg root flush-179:0
98 0 0% S 1 0K 0K fg root jbd2/mmcblk0p18
99 1 0% S 1 0K 0K fg root ext4-dio-unwrit
100 0 0% S 1 0K 0K fg root jbd2/mmcblk0p17
101 0 0% S 1 0K 0K fg root ext4-dio-unwrit
112 0 0% S 1 0K 0K fg root jbd2/mmcblk0p5-
113 0 0% S 1 0K 0K fg root ext4-dio-unwrit
121 0 0% S 1 1148K 496K fg root /system/bin/sh
139 0 0% S 5 6548K 776K fg logd /system/bin/logd
140 1 0% S 1 1588K 148K fg root /sbin/healthd
141 0 0% S 1 2392K 648K fg root /system/bin/lmkd
142 0 0% S 1 1248K 464K fg system /system/bin/servicemanager
143 1 0% S 3 5820K 1084K fg root /system/bin/vold
145 1 0% S 7 8540K 576K fg system /system/bin/mcDriverDaemon
153 0 0% S 9 10816K 952K fg root /system/bin/netd
157 0 0% S 1 1816K 516K fg root /system/bin/debuggerd
158 1 0% S 1 1944K 608K fg install /system/bin/installd
162 0 0% S 2 21404K 2824K fg root /system/xbin/vitals_collection_agent
164 0 0% S 11 42528K 2740K fg media /system/bin/mediaserver
165 1 0% S 11 31636K 2336K fg system /system/bin/tvserver
169 0 0% S 5 6392K 752K fg system /system/bin/vclmk
176 1 0% S 5 6296K 768K fg system /system/bin/cecdaemon
177 0 0% S 1 4364K 1160K fg keystore /system/bin/keystore
178 1 0% S 6 966408K 29072K fg root zygote
179 1 0% S 3 4028K 832K fg media_rw /system/bin/sdcard
180 0 0% S 1 1324K 308K fg root /system/bin/btremoted
182 0 0% S 8 7728K 252K fg shell /sbin/adbd
245 1 0% S 1 0K 0K fg root kauditd
289 1 0% S 1 0K 0K fg root mc_log
338 0 0% S 1 0K 0K fg root kworker/0:2
462 0 0% S 5 19892K 3296K fg drm /system/bin/drmserver
562 0 0% S 1 1064K 164K fg root daemonsu:mount:master
744 1 0% S 3 3116K 268K fg root daemonsu:master
760 0 0% S 1 19892K 3296K fg drm /system/bin/drmserver
1221 1 0% S 1 0K 0K fg root wlfc-mon-thread
1224 0 0% S 1 0K 0K fg root wl_event_handle
1363 1 0% S 12 983240K 25584K bg amz_u0a6 com.amazon.tv.ime
1412 0 0% S 1 5120K 1660K fg wifi /system/bin/wpa_supplicant
1420 1 0% S 14 976792K 23916K bg amz_u0a5 com.amazon.precog
1432 1 0% S 15 984600K 25028K fg amz_u0a7 com.amazon.vizzini
1444 0 0% S 16 984768K 24252K bg amz_u0a1 com.amazon.device.logmanager
1471 1 0% S 20 985444K 33868K bg amz_u0a4 com.amazon.imp
1499 1 0% S 25 997252K 33224K bg amz_u0a6 com.amazon.tcomm
1526 0 0% S 43 1063040K 43428K bg amz_u0a6 com.amazon.tv.launcher
1606 1 0% S 47 1016240K 29824K bg amz_u0a2 com.amazon.client.metrics
1631 0 0% S 18 983648K 25428K bg amz_u0a2 com.amazon.device.settings
1755 0 0% S 1 972K 352K bg amz_u0a5 logcat
1819 1 0% S 21 996956K 32564K bg amz_u0a6 com.amazon.tv.launcher:MediaBrowseServiceProcess
1836 1 0% S 15 987772K 31968K bg amz_u0a5 com.amazon.kso.blackbird:BlackbirdServiceProcess
1849 1 0% S 1 1112K 340K fg nobody /system/bin/dnsmasq
1870 1 0% S 1 1040K 400K bg amz_u0a2 logcat
1888 1 0% S 1 1108K 384K fg root /system/bin/sh
1980 0 0% S 51 1085684K 50744K bg amz_u0a3 com.amazon.avod
2006 0 0% S 12 974432K 25608K bg u0_a2 com.amazon.device.controllermanager
2029 1 0% S 24 1002908K 32408K bg amz_u0a6 com.amazon.tv.launcher:GlobalNavProcess
2135 1 0% S 1 1112K 364K fg dhcp /system/bin/dhcpcd
2136 1 0% S 1 1116K 200K fg root /system/bin/sh
2137 1 0% S 1 1108K 180K fg root /system/bin/sh
2166 0 0% S 1 1012K 332K fg root /system/bin/ping
2167 1 0% S 1 2428K 568K fg root grep
2197 1 0% S 1 0K 0K fg root kworker/1:2
2410 1 0% S 27 1000832K 26080K fg bluetoot com.android.bluetooth
2419 0 0% S 1 1292K 656K fg root /system/bin/sh
2763 0 0% S 28 1001428K 35632K bg u0_a30 com.kingouser.com
2812 1 0% S 1 3116K 204K fg root daemonsu:10030
3672 1 0% S 20 993760K 41456K fg u0_a15 de.belu.firestopper
3695 0 0% S 32 1002416K 32272K fg u0_a22 com.guidology.android.remotemouseforfiretv
3740 0 0% S 13 993576K 26520K bg u0_a29 net.loadinghome.rotatescreenorientation
3809 1 0% S 2 5168K 448K fg root daemonsu:0
3870 1 0% S 10 972256K 22728K bg u0_a2 com.amazon.device.controllermanager:BluetoothReceiver
3896 0 0% S 53 1045076K 46868K bg amz_u0a7 com.amazon.venezia
3958 1 0% S 14 983116K 28788K bg amz_u0a1 com.android.providers.downloads
4255 1 0% S 10 981540K 22468K bg amz_u0a5 com.amazon.kso.blackbird
4283 0 0% S 10 972264K 22368K bg u0_a2 com.amazon.device.controllermanager:WifiReceiver
4347 0 0% S 1 1116K 560K fg shell /system/bin/sh
4363 0 0% S 1 1064K 472K fg shell su
4366 0 0% S 1 5176K 580K fg root daemonsu:0:4363
4370 1 0% S 1 1120K 564K fg root tmp-mksh
4509 1 0% S 21 1005348K 37920K bg amz_u0a5 com.amazon.kindle.cms
4570 0 0% S 16 989604K 32044K bg amz_u0a6 com.amazon.storm.lightning.services
4619 1 0% S 11 975212K 26652K bg amz_u0a7 com.amazon.sync.service
4849 1 0% S 10 974256K 26656K bg amz_u0a5 com.amazon.securitysyncclient
5405 1 0% S 22 1000016K 34880K fg amz_u0a4 com.amazon.bueller.photos:core
84 0 0% S 1 0K 0K fg root mmcqd/0
2 0 0% S 1 0K 0K fg root kthreadd
3 0 0% S 1 0K 0K fg root ksoftirqd/0
5 0 0% S 1 0K 0K fg root kworker/u:0
6 0 0% S 1 0K 0K fg root migration/0
7 1 0% S 1 0K 0K fg root migration/1
9 1 0% S 1 0K 0K fg root ksoftirqd/1
10 1 0% S 1 0K 0K fg root khelper
11 1 0% S 1 0K 0K fg root netns
12 1 0% S 1 0K 0K fg root suspend
13 1 0% S 1 0K 0K fg root i2c_master_rese
14 1 0% S 1 0K 0K fg root i2c_master_rese

Did someone try this on a FireTV 1 with 5.0.5.1? I am not at home right now, so I can't try.

I will try it today... Did you install Super User after rooting or before?

cuki3r3k83bln said:
Did you install Super User after rooting or before?
Click to expand...
Click to collapse
jaminmc said:
SuperUser needs to be installed for it to work.
Click to expand...
Click to collapse

Tried this as you did jaminmc and still fails, any other variable you might of done? Cheers

jaminmc said:
Here is the exact APK I used. I also had to have the app "Rotate screen orientation " lock all apps in landscape mode, as kingo wants to open in portrait.
Below should be all you need...
You will need a mouse, or I just used "RemoteMouse" with my iPhone.
The first time I ran it, I thought it froze, and I held the center, Play-pause buttons to reboot the Fire Stick, and on reboot, I ran it again, and it worked. While it was rebooting, the progress bar started moving. SuperUser needs to be installed for it to work.
Click to expand...
Click to collapse
I tried it on a 5.0.5.1 Fire TV Stick, replicating what you say, and also failed. I did not need a mouse btw since pressing the center button on the remote starts the rooting process.
If you're not just trolling us, the only thing I can think of is that there's some sweet spot during the rooting attempt that the device needs to be restarted which you hit, since you say "while it was rebooting, the progress bar started moving." Do you remember what percentage it was stuck at? It never goes past 90% for me and then eventually says root failed after about 2 minutes at 90%. When the bar started moving while it rebooted, did it go past 90%?
If there is some sweet spot to reboot at, my guess is it's from when it stops at 90% to 50 seconds later. Around 50 seconds after it stops at 90%, the app tries to mount the system partition as writable and fails.

Tried the same with running su before and after kingo root and restarted at several times while it was at 90 % but had no luck until now...

I finally got root succeeded, the way I did it was as per op instructions. When it gets to 90 percent I waited around 45 seconds then held home/play pause down. Restsrted then re launched Kingo ?

Tried it too with my second FTV Stick running 5.0.5.1 and it fails...

Michael Kors Access Bradshaw [MKT500X Series] [1st Gen Fossil]

This is my first foray into Wear OS. I seem to always end up with some locked down devices. It Always teaches me a thing or two though! Because all is not lost it seems. I've been trying to compile what I can see from the device into one spot. Information on this series of watches is spread out all over the place. Let me explain what I've found out about The MK Access Bradshaw, that makes me think there is a light at the end of the tunnel. If you have experience with these watches or the Fossil Q sister series, please share. Links to the Fossil Q firmware would be amazing at this point.
Code:
----------------------------------------------
Michael Kors Access Bradshaw Device Info
----------------------------------------------
MODEL: MKT5006
CHIPSET: SD Wear 2100
RAM: 512 MB
STORAGE: 4 GB
SCREEN: 1.4 inch
RESOLUTION: 320x290 pixels (309 ppi)
WEAR OS: 2.6
BUILD: fossil/gar/gar
8.0.0/OWD6.180205.022/53356216
user/release-keys
----------------------------------------------
1. FASTBOOT MODE
[adb reboot bootloader]
----------------------------------------------
PRODUCT_NAME - gar
VARIANT - PFW2
PHASE - SA
BOOTLOADER VERSION - GAR.EINSTEIN_0.083.00
BASEBAND VERSION - N/A
HW_CONFIG - 1
SERIAL NUMBER - XXXXXXXXX (9 Digits)
** A Direct Pin Connection is Needed
to utilize the Fastboot Protocol.
** Fastboot appears active and functional
and only missing a physical connection
** A Pin Connection can be made.
Now, when we finally make it into the recovery mode, we are presented with standard Android Oreo Recovery options. Including the Recovery Logs. It is in these logs I have found A LOT of Information. They have the Log Daemon configured to 'eng'. But I noticed that simply using the 'adb reboot recovery' command, would start recovery mode but never show the recovery menu before rebooting back to the system.
The recovery menu only ever appears for me when I boot into recovery mode from fastboot mode.
Code:
----------------------------------------------
2. RECOVERY MODE
[Boot to Recovery from Bootloader]
----------------------------------------------
* The Recovery Log displays the Recovery FSTAB
* Build.Prop Contents Can also been seen.
* ro.logd.kernel=eng
It is very verbose. But without actual access to the cache partition there is no way to copy & paste, or pull the logs from the watch. My "last_log" entry is from when I updated the device from WearOS 2.2 to version 2.6. In that log, so much of the nitty gritty partition details are revealed, here are a few I've wrote down so far:
Code:
/cache/recovery/last_log:
-----------------------------
0 /system ext4 /dev/block/platform/soc/7824900.sdhci/by-name/system 0
1 /cache ext4 /dev/block/platform/soc/7824900.sdhci/by-name/cache 0
2 /data ext4 /dev/block/platform/soc/7824900.sdhci/by-name/userdata -16384
3 /sdcard vfat /dev/block/mmcblk1p1 0
4 /boot emmc /dev/block/platform/soc/7824900.sdhci/by-name/boot 0
5 /recovery emmc /dev/block/platform/soc/7824900.sdhci/by-name/recovery 0
6 /misc emmc /dev/block/platform/soc/7824900.sdhci/by-name/misc 0
7 /oem ext4 /dev/block/platform/soc/7824900.sdhci/by-name/oem 0
8 /tmp ramdisk ramdisk 0
ro.sys.fw.use_trim_settings=true
ro.sys.fw.trim_enable_memory=1073741824
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.empty_app_percent=50
ro.sys.umsdirtyratio=20
ro.boot.hardware=gar
ro.boot.baseband=apq
ro.boot.console=null
ro.boot.ceibootmode=0
ro.boot.bootdevice=7824900.sdhci
ro.board.platform=msm8909
ro.build.host=abfarm648
ro.product.cpu.abi=armeabi-v7a
ro.boot.verifiedbootstate=green
ro.boot.authorized_kernel=true
ro.logd.kernel=eng
ro.bootimage.build.date=Thu Aug 9 00:39:05 UTC 2018
[11.364486]Verifying update package...
I:comment is 1476 bytes; signature is 1458 bytes from end.
I:signature (offset: 10127db, length: 5ac):
That log continues on with all of the signature, but on the watch screen it is quite a few pages long. But continues on during the whole verification process. And it really does say in so many words what it is doing and when. The log explains exactly what data it is putting where, and where the developers forgot to set expected values that the system must choose a default for.
What I need to do now is go through the log with an OCR App that can take pictures of the screen and extract the text. I believe the two most recent log files on my watch could explain just how to get at the bootloader & kernel. They definitely tell you where to go find the eFuse. Because even though it has Green Verified Boot Status, the boot log shows a few things for verified boot were never actually implemented. I'm working on getting these logs now.
Enable Developer Options:
Settings > System > About > Tap Build Number until it unlocks.
Connecting to ADB:
1.) Enable Developer Options
2.) Disable Bluetooth
3.) Connect Device to Wi-Fi
4.) Settings > Dev Options > ADB Debugging
5.) Settings > Dev Options > Debug Over Wi-Fi
6.) From a command line, start the adb server and then use this command with the watch's wifi ip address: "adb connect <ip_address>:5555"
7.) Run command "adb devices" and hit the yes button on the watch face to accept the connection.
Replacement 1st Gen Fossil Watch Chargers (2016-2017 Watches):
1.) 1st Party Marc Jacob's MJT0001/MKT0001
2.) 3rd Party Soarking Fossil Charger
Once I find a repair manual or schematic to this thing, I think I'm going to work on creating a cable to connect to the board for fastboot access.
MEMINFO
Code:
MemTotal: 455000 kB
MemFree: 8228 kB
MemAvailable: 179528 kB
Buffers: 2216 kB
Cached: 179400 kB
SwapCached: 7136 kB
Active: 153580 kB
Inactive: 154504 kB
Active(anon): 63348 kB
Inactive(anon): 64340 kB
Active(file): 90232 kB
Inactive(file): 90164 kB
Unevictable: 256 kB
Mlocked: 256 kB
SwapTotal: 338936 kB
SwapFree: 222520 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 125548 kB
Mapped: 78400 kB
Shmem: 1216 kB
Slab: 41732 kB
SReclaimable: 13440 kB
SUnreclaim: 28292 kB
KernelStack: 8544 kB
PageTables: 20392 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 566436 kB
Committed_AS: 26409868 kB
VmallocTotal: 499712 kB
VmallocUsed: 95544 kB
VmallocChunk: 291668 kB
MOUNTS
Code:
rootfs / rootfs ro,seclabel,size=205932k,nr_inodes=51483 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=221356k,nr_inodes=55339,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
none /config configfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/oem /oem ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
PARTITIONS
Code:
major - minor - #blocks name
-------------------------------------
254 - 0 - 262144 zram0
179 - 0 - 3817472 mmcblk0
179 - 1 - 65536 mmcblk0p1
179 - 2 - 512 mmcblk0p2
179 - 3 - 512 mmcblk0p3
179 - 4 - 512 mmcblk0p4
179 - 5 - 512 mmcblk0p5
179 - 6 - 768 mmcblk0p6
179 - 7 - 768 mmcblk0p7
179 - 8 - 1024 mmcblk0p8
179 - 9 - 1536 mmcblk0p9
179 - 10 - 1536 mmcblk0p10
179 - 11 - 1536 mmcblk0p11
179 - 12 - 1 mmcblk0p12
179 - 13 - 1024 mmcblk0p13
179 - 14 - 8 mmcblk0p14
179 - 15 - 10240 mmcblk0p15
179 - 16 - 32 mmcblk0p16
179 - 17 - 16 mmcblk0p17
179 - 18 - 32768 mmcblk0p18
179 - 19 - 32768 mmcblk0p19
179 - 20 - 512 mmcblk0p20
179 - 21 - 1024 mmcblk0p21
179 - 22 - 1024 mmcblk0p22
179 - 23 - 32768 mmcblk0p23
179 - 24 - 32768 mmcblk0p24
179 - 25 - 1024 mmcblk0p25
179 - 26 - 512 mmcblk0p26
179 - 27 - 512 mmcblk0p27
179 - 28 - 16384 mmcblk0p28
179 - 29 - 256 mmcblk0p29
179 - 30 - 256 mmcblk0p30
179 - 31 - 256 mmcblk0p31
259 - 0 - 256 mmcblk0p32
259 - 1 - 65536 mmcblk0p33
259 - 2 - 655360 mmcblk0p34
259 - 3 - 2310127 mmcblk0p35
179 - 32 - 4096 mmcblk0rpmb
DF Utility
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
---------------------------------------------------------------------------
rootfs 205932 3460 202472 2% /
tmpfs 221356 532 220824 1% /dev
tmpfs 221356 0 221356 0% /mnt
/dev/block/mmcblk0p34 645056 630224 0 100% /system
/dev/block/mmcblk0p33 60400 1632 57460 3% /cache
/dev/block/mmcblk0p1 65488 22240 43248 34% /firmware
/dev/block/mmcblk0p28 12016 64 11628 1% /oem
/dev/block/mmcblk0p35 2237680 690400 1530896 32% /data
/data/media 2237680 690400 1530896 32% /storage/emulated

Since making this thread, this update no longer seems to be available. I think I am also leaving XDA, my words here have caused me too much trouble.

Custom firmware on Axon 7s

Hello,
My Axon 7s (the dual cam one) (https://www.gsmarena.com/zte_axon_7s-8658.php) has an overheating issue. The battery melts dows super fast and the phone heats up alot even in standby with no sim card and wi-fi enabled. Factory reset did not helped at all. It is Android 7.1.1, ZTE2018V1.1.0B11. Is there any way to install custom firmware or update the stock one, ore anything else that will help prevent this issue?
Thanks!

no its not possible

It sounds like a bad battery more than a software issue. The Axon 7s does have some comments online saying it overheats frequently however.
If you're comfortable in doing so and your warranty has expired; I would try replacing the battery and maybe even the thermal paste inside.

After resetting the phone, the problem disappeared. It was cool for 2-3 hours. Then I logged in my google account, installed Viber and it started heating and draining the battery again. The Phone is 4 months old. Never played games on it. Only Facebook and Viber. I had another Axon 7 (without "s") before with the same problem. Changed the battery 2 times and nothing happened. Still discharges super fast...

Markovo said:
After resetting the phone, the problem disappeared. It was cool for 2-3 hours. Then I logged in my google account, installed Viber and it started heating and draining the battery again. The Phone is 4 months old. Never played games on it. Only Facebook and Viber. I had another Axon 7 (without "s") before with the same problem. Changed the battery 2 times and nothing happened. Still discharges super fast...
Click to expand...
Click to collapse
Had the same problem - in my case MediaServer locked up upon a corrupt MP4 file and utilitzed 1 core at 100% constantly. That caused my phone to overheat. Battery life was terrible.
Try to hook your phone up to your computer and open "ADB shell" and type "top -m 10" - you will see the top 10 processes that cause CPU utilization. If there is a process that hogs your CPU you know where to look closer. I found out that a corrupt MP4 video file was the culprit. After deleting it and a reboot my phone was fixed and felt lie new. Hope that helps...

I used ADB Shell too show the processes.
Here is the result:
Code:
Load: 3.33 / 3.59 / 3.64
CPU usage from 51297ms to 39789ms ago (2020-05-13 12:06:18.533 to 2020-05-13 12:06:30.042):
0.9% 2504/kworker/u8:10: 0% user + 0.9% kernel
0.6% 2599/system_server: 0.2% user + 0.4% kernel / faults: 58 minor
0.5% 53/ksmd: 0% user + 0.5% kernel
0.5% 7125/kworker/u8:11: 0% user + 0.5% kernel
0.5% 8893/kworker/u8:0: 0% user + 0.5% kernel
0.4% 16/ksoftirqd/2: 0% user + 0.4% kernel
0.2% 2426/gx_fpd: 0% user + 0.2% kernel
0.2% 3238/com.android.systemui: 0.2% user + 0% kernel / faults: 7 minor
0.1% 42/smem_native_rpm: 0% user + 0.1% kernel
0.1% 2963/thermal-engine: 0.1% user + 0% kernel
0.1% 6642/com.google.android.webview:s: 0.1% user + 0% kernel
0.1% 7323/kworker/0:2: 0% user + 0.1% kernel
0.1% 7703/kworker/2:5: 0% user + 0.1% kernel
0% 20/ksoftirqd/3: 0% user + 0% kernel
0% 34/kworker/0:1: 0% user + 0% kernel
0% 348/cfinteractive: 0% user + 0% kernel
0% 464/servicemanager: 0% user + 0% kernel / faults: 1 minor
0% 614/[email protected]: 0% user + 0% kernel
0% 635/healthd: 0% user + 0% kernel
0% 3390/com.android.phone: 0% user + 0% kernel / faults: 4 minor
0% 7695/kworker/3:4: 0% user + 0% kernel
0% 8940/kworker/2:1: 0% user + 0% kernel
1.3% TOTAL: 0.1% user + 0.8% kernel + 0% iowait + 0.3% irq + 0.1% softirq
Code:
Tasks: 580 total, 1 running, 573 sleeping, 0 stopped, 2 zombie
Mem: 3860956k total, 3633324k used, 227632k free, 117192k buffers
Swap: 1048572k total, 0k used, 1048572k free, 1886212k cached
400%cpu 2%user 1%nice 7%sys 390%idle 0%iow 0%irq 0%sirq 0%host
 PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS 
2551 system 18 -2 2.5G 284M 186M S 5.0 7.5 0:26.34 system_server
6370 shell 20 0 11M 3.0M 1.7M R 4.0 0.0 0:01.31 top -n 10
6068 root 20 0 0 0 0 S 0.6 0.0 0:00.21 [kworker/u8:12]
464 logd 30 10 24M 4.6M 1.4M S 0.6 0.1 0:03.44 logd
347 root RT 0 0 0 0 S 0.6 0.0 0:01.27 [cfinteractive]
895 root 20 0 0 0 0 S 0.3 0.0 0:01.05 [kworker/u8:10]
622 system RT 0 86M 3.3M 2.3M S 0.3 0.0 0:01.36 android.hardwar+
287 root 20 0 0 0 0 S 0.3 0.0 0:00.26 [kworker/u8:9]
54 root 25 5 0 0 0 S 0.3 0.0 0:00.40 [ksmd]
47 root RT 0 0 0 0 S 0.3 0.0 0:00.55 [irq/263-cpr3]
6354 shell 20 0 13M 1.0M 776K S 0.0 0.0 0:00.04 adbd --root_sec+
6194 system 20 0 2.1G 39M 19M S 0.0 1.0 0:00.06 com.zte.emode
6132 u0_a30 20 0 2.1G 59M 34M S 0.0 1.5 0:01.79 com.android.mms
6128 root RT 0 0 0 0 D 0.0 0.0 0:00.54 [mdss_fb0]
6120 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/3:5]
6104 system 20 0 2.1G 43M 23M S 0.0 1.1 0:00.11 zte.com.cn.alar+
6087 u0_a115 20 0 2.1G 38M 18M S 0.0 1.0 0:00.10 com.qualcomm.ti+
6077 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:16]
6076 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:15]
[?25h[?25h0.0 0.0 0:00.00 [kworker/u8:14]
Code:
Tasks: 577 total, 1 running, 570 sleeping, 0 stopped, 2 zombie
Mem: 3860956k total, 3630552k used, 230404k free, 117216k buffers
Swap: 1048572k total, 0k used, 1048572k free, 1886212k cached
400%cpu 1%user 0%nice 4%sys 395%idle 0%iow 0%irq 0%sirq 0%host
 PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS 
6385 shell 20 0 11M 3.0M 1.7M R 4.3 0.0 0:00.63 top -n 10
6354 shell 20 0 13M 0.9M 788K S 0.3 0.0 0:00.06 adbd --root_sec+
6068 root 20 0 0 0 0 S 0.3 0.0 0:00.60 [kworker/u8:12]
622 system RT 0 86M 3.2M 2.3M S 0.3 0.0 0:01.72 android.hardwar+
347 root RT 0 0 0 0 S 0.3 0.0 0:01.38 [cfinteractive]
54 root 25 5 0 0 0 S 0.3 0.0 0:00.67 [ksmd]
12 root 20 0 0 0 0 S 0.3 0.0 0:00.66 [ksoftirqd/1]
7 root 20 0 0 0 0 S 0.3 0.0 0:01.33 [rcu_preempt]
6194 system 20 0 2.1G 39M 19M S 0.0 1.0 0:00.06 com.zte.emode
6132 u0_a30 20 0 2.1G 59M 34M S 0.0 1.5 0:01.81 com.android.mms
6128 root RT 0 0 0 0 D 0.0 0.0 0:00.65 [mdss_fb0]
6120 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/3:5]
6104 system 20 0 2.1G 43M 23M S 0.0 1.1 0:00.11 zte.com.cn.alar+
6087 u0_a115 20 0 2.1G 38M 18M S 0.0 1.0 0:00.10 com.qualcomm.ti+
6077 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:16]
6076 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:15]
6075 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:14]
6069 root 20 0 0 0 0 S 0.0 0.0 0:00.16 [kworker/u8:13]
6066 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:11]
6045 root 20 0 0 0 0 S 0.0 0.0 0:00.02 [kworker/1:5]
It seems alright to me...