Hi all,
I am trying to track down the slowness problem on my sgs.
I think that the problem is the io system.
Can someone tell me his thoughts about this iostat output ?
Code:
CPU: 13.1% usr 2.7% sys 0.0% nic 0.0% idle 82.4% io 0.0% irq 1.5% sirq
Load average: 3.46 2.08 1.50 2/542 4702
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
2353 90 10115 S 176m 48.2 0 11.5 {d.process.acore} android.process.
690 90 system S 277m 75.7 0 1.7 system_server
62 2 root DW 0 0.0 0 1.5 [mmcqd]
5 2 root RW 0 0.0 0 1.0 [events/0]
809 90 system S 160m 43.8 0 0.3 {ndroid.systemui} com.android.syst
2148 2141 root R 2260 0.6 0 0.3 /system/xbin/busybox /sbin/top
15 2 root SW 0 0.0 0 0.3 [kondemand/0]
822 90 radio S 172m 46.9 0 0.1 {m.android.phone} com.android.phon
2561 90 10093 S 138m 37.8 0 0.1 org.dayup.gtask
100 1 compass S 2880 0.7 0 0.1 /system/bin/orientationd
861 90 10044 S 226m 61.8 0 0.0 {e.process.gapps} com.google.proce
31608 1 10175 S 186m 50.8 0 0.0 {udsandsheepfree} com.hg.cloudsand
2681 90 10061 S 174m 47.6 0 0.0 {ogle.android.gm} com.google.andro
2711 90 10054 S 169m 46.0 0 0.0 {LocationService} com.google.andro
2626 90 10054 S 166m 45.5 0 0.0 {droid.apps.maps} com.google.andro
2318 90 10104 S 151m 41.3 0 0.0 {droid.apps.plus} com.google.andro
1668 90 10084 S 151m 41.1 0 0.0 {nputmethod.axt9} com.sec.android.
2733 90 10054 S 150m 41.1 0 0.0 {onFriendService} com.google.andro
2726 90 10054 S 144m 39.4 0 0.0 {s:FriendService} com.google.a
Related
Why do i get this output when testing? What the heck am i doing wrong.
I want some compcache with backing swap love too!!!!!!!!!
=== CompCache status ===
CompCache version 0.6+
Compcache enabled
CompCache: MemLimit 16384(system) 8192(user)
CompCache: BackingSwap /dev/block/mmcblk0p3(system) /dev/block/mmcblk0p3(user)
!!! Unable to set compcache cc_swappiness to user specific "60"
Current system value is "28"
=== CompCache status output ===
BackingSwap: /dev/block/mmcblk0p3
DiskSize: 100564 kB
MemLimit: 16384 kB
NumReads: 1
NumWrites: 0
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 0
PagesDiscard: 0
ZeroPages: 0
GoodCompress: 0 %
NoCompress: 0 %
PagesStored: 0
PagesUsed: 0
OrigDataSize: 0 kB
ComprDataSize: 0 kB
MemUsedTotal: 0 kB
BDevNumReads: 0
BDevNumWrites: 0
find: /system/app/*.odex: No such file or directory
find: /data/app/*.odex: No such file or directory
#
anybody????????????
I think xROM is ignoring my userinit.sh and user.conf, because when I type "free" in to the terminal it shows the size of my swap partition under swap, rather than my compcache size :-S What command are you using to retrieve those values?
Hi all,
I'm still working trying to work my openvpn:
Link related to thread:
http://forum.xda-developers.com/showpost.php?p=8347800&postcount=3
http://code.google.com/p/android-openvpn-installer/issues/detail?id=2
Now, some info about my config:
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Check load of tun.ko
#lsmod
tun 11088 0 - Live 0xbf203000
Path to busybox:
# which busybox
/system/xbin/busybox
Path to Openvpn:
# which openvpn
/system/xbin/openvpn
Links for openvpn due harcode
# busybox ls -la /system/xbin/bb
total 8
drwxrwxrwx 1 0 0 0 Oct 20 03:17 .
drwxr-xr-x 1 0 2000 0 Oct 20 03:18 ..
lrwsrwsrwt 1 0 0 60 Oct 20 03:14 ifconfig -> /system/xbin/ifconfig
lrwsrwsrwt 1 0 0 56 Oct 20 03:17 route -> /system/xbin/route
# busybox ls -la /system/xbin/ifconfig
busybox ls -la /system/xbin/ifconfig
lrwsrwsrwt 1 0 0 60 Oct 20 07:19 ←[1;36m/system/xbin/ifconfig←[0m -> ←[1;32m/system/xbin/busybo←[0m
# busybox ls -la /system/xbin/route
busybox ls -la /system/xbin/route
lrwsrwsrwt 1 0 0 60 Oct 20 07:19 ←[1;36m/system/xbin/route←[0m -> ←[1;32m/system/xbin/busybox←[0m
Path to tun.ko module
# busybox ls -la /system/lib/modules
busybox ls -la /system/lib/modules
total 152
drwxrwxrwx 1 0 0 0 Oct 20 07:19 ←[1;34m.←[0m
drwxr-xr-x 1 0 0 0 Oct 20 02:19 ←[1;34m..←[0m
-rwxrwxrwx 1 0 0 154447 Oct 20 12:19 ←[1;32mtun.ko←[0m
Busybox Version:
# busybox
busybox
BusyBox v1.17.1 (2010-08-12 23:44:34 CDT) multi-call binary.
Openvpn Version based on first link
# openvpn
openvpn
OpenVPN 2.1_rc15 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] built on Jan 21 2010
Now, my openvpn connect, but cant get ip address , i mean, on GUI interface of openvpn after connect, still like "connected to mydomain.com as"..
if a try to launch via terminal (adb shell) after write "openvpn --config <path to my *.ovpn config file>, freeze the screen and nothins happens...
This is the final phase for each connection, looking on my logfile:
Wed Oct 20 09:13:40 2010 TLS: Initial packet from XXX.XXX.XXX.XXX:YYY, sid=caddb5cd 96066b25
Wed Oct 20 09:13:43 2010 VERIFY OK: depth=1, /C=CO/ST=CU/L=Bogota/O=Favernet/CN=NASVPN/[email protected]
Wed Oct 20 09:13:43 2010 VERIFY OK: depth=0, /C=CO/ST=CU/O=Favernet/CN=FavernetVPN/[email protected]
Wed Oct 20 09:13:56 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 20 09:13:56 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 20 09:13:56 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Oct 20 09:13:56 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Oct 20 09:13:56 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Oct 20 09:13:56 2010 [FavernetVPN] Peer Connection Initiated with XXX.XXX.XXX.XXX:YYY
Wed Oct 20 09:13:57 2010 Initialization Sequence Completed
I'm not good with this, but i don't know what else need verification..any suggestions?
http://forum.xda-developers.com/showthread.php?t=729531 >> This is a DEVELOPMENT section, not GENERAL. Do NOT post questions here!
try here: http://forum.xda-developers.com/forumdisplay.php?f=748
Moved to Q&A as not development
I am trying to upgrade from GC100ZSALJ6 rom but failed when flashing the modem.bin. I have tried odin and heimdallv1.3.1.
The output of the heimdall is,
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading RADIO
0%File Part #0... Response: 0 0 0 0 0 0 0 0
1%
File Part #1... Response: 0 0 0 0 1 0 0 0
2%
File Part #2... Response: 0 0 0 0 2 0 0 0
3%
File Part #3... Response: 0 0 0 0 3 0 0 0
4%
File Part #4... Response: 0 0 0 0 4 0 0 0
5%
File Part #5... Response: 0 0 0 0 5 0 0 0
6%
File Part #6... Response: 0 0 0 0 6 0 0 0
7%
File Part #7... Response: 0 0 0 0 7 0 0 0
8%
File Part #8... Response: 0 0 0 0 8 0 0 0
9%
File Part #9... Response: 0 0 0 0 9 0 0 0
10%
File Part #10... Response: 0 0 0 0 A 0 0 0
11%
File Part #11... Response: 0 0 0 0 B 0 0 0
12%
File Part #12... Response: 0 0 0 0 C 0 0 0
13%
File Part #13... Response: 0 0 0 0 D 0 0 0
14%
File Part #14... Response: 0 0 0 0 E 0 0 0
15%
File Part #15... Response: 0 0 0 0 F 0 0 0
16%
File Part #16... Response: 0 0 0 0 10 0 0 0
17%
File Part #17... Response: 0 0 0 0 11 0 0 0
18%
File Part #18... Response: 0 0 0 0 12 0 0 0
19%
File Part #19... Response: 0 0 0 0 13 0 0 0
20%
File Part #20... Response: 0 0 0 0 14 0 0 0
21%
File Part #21... Response: 0 0 0 0 15 0 0 0
22%
File Part #22... Response: 0 0 0 0 16 0 0 0
23%
File Part #23... Response: 0 0 0 0 17 0 0 0
24%
File Part #24... Response: 0 0 0 0 18 0 0 0
26%
File Part #25... Response: 0 0 0 0 19 0 0 0
27%
File Part #26... Response: 0 0 0 0 1A 0 0 0
28%
File Part #27... Response: 0 0 0 0 1B 0 0 0
29%
File Part #28... Response: 0 0 0 0 1C 0 0 0
30%
File Part #29... Response: 0 0 0 0 1D 0 0 0
31%
File Part #30... Response: 0 0 0 0 1E 0 0 0
32%
File Part #31... Response: 0 0 0 0 1F 0 0 0
33%
File Part #32... Response: 0 0 0 0 20 0 0 0
34%
File Part #33... Response: 0 0 0 0 21 0 0 0
35%
File Part #34... Response: 0 0 0 0 22 0 0 0
36%
File Part #35... Response: 0 0 0 0 23 0 0 0
37%
File Part #36... Response: 0 0 0 0 24 0 0 0
38%
File Part #37... Response: 0 0 0 0 25 0 0 0
39%
File Part #38... Response: 0 0 0 0 26 0 0 0
40%
File Part #39... Response: 0 0 0 0 27 0 0 0
41%
File Part #40... Response: 0 0 0 0 28 0 0 0
42%
File Part #41... Response: 0 0 0 0 29 0 0 0
43%
File Part #42... Response: 0 0 0 0 2A 0 0 0
44%
File Part #43... Response: 0 0 0 0 2B 0 0 0
45%
File Part #44... Response: 0 0 0 0 2C 0 0 0
46%
File Part #45... Response: 0 0 0 0 2D 0 0 0
47%
File Part #46... Response: 0 0 0 0 2E 0 0 0
48%
File Part #47... Response: 0 0 0 0 2F 0 0 0
49%
File Part #48... Response: 0 0 0 0 30 0 0 0
51%
File Part #49... Response: 0 0 0 0 31 0 0 0
52%
File Part #50... Response: 0 0 0 0 32 0 0 0
53%
File Part #51... Response: 0 0 0 0 33 0 0 0
54%
File Part #52... Response: 0 0 0 0 34 0 0 0
55%
File Part #53... Response: 0 0 0 0 35 0 0 0
56%
File Part #54... Response: 0 0 0 0 36 0 0 0
57%
File Part #55... Response: 0 0 0 0 37 0 0 0
58%
File Part #56... Response: 0 0 0 0 38 0 0 0
59%
File Part #57... Response: 0 0 0 0 39 0 0 0
60%
File Part #58... Response: 0 0 0 0 3A 0 0 0
61%
File Part #59... Response: 0 0 0 0 3B 0 0 0
62%
File Part #60... Response: 0 0 0 0 3C 0 0 0
63%
File Part #61... Response: 0 0 0 0 3D 0 0 0
64%
File Part #62... Response: 0 0 0 0 3E 0 0 0
65%
File Part #63... Response: 0 0 0 0 3F 0 0 0
66%
File Part #64... Response: 0 0 0 0 40 0 0 0
67%
File Part #65... Response: 0 0 0 0 41 0 0 0
68%
File Part #66... Response: 0 0 0 0 42 0 0 0
69%
File Part #67... Response: 0 0 0 0 43 0 0 0
70%
File Part #68... Response: 0 0 0 0 44 0 0 0
71%
File Part #69... Response: 0 0 0 0 45 0 0 0
72%
File Part #70... Response: 0 0 0 0 46 0 0 0
73%
File Part #71... Response: 0 0 0 0 47 0 0 0
74%
File Part #72... Response: 0 0 0 0 48 0 0 0
76%
File Part #73... Response: 0 0 0 0 49 0 0 0
77%
File Part #74... Response: 0 0 0 0 4A 0 0 0
78%
File Part #75... Response: 0 0 0 0 4B 0 0 0
79%
File Part #76... Response: 0 0 0 0 4C 0 0 0
80%
File Part #77... Response: 0 0 0 0 4D 0 0 0
81%
File Part #78... Response: 0 0 0 0 4E 0 0 0
82%
File Part #79... Response: 0 0 0 0 4F 0 0 0
83%
File Part #80... Response: 0 0 0 0 50 0 0 0
84%
File Part #81... Response: 0 0 0 0 51 0 0 0
85%
File Part #82... Response: 0 0 0 0 52 0 0 0
86%
File Part #83... Response: 0 0 0 0 53 0 0 0
87%
File Part #84... Response: 0 0 0 0 54 0 0 0
88%
File Part #85... Response: 0 0 0 0 55 0 0 0
89%
File Part #86... Response: 0 0 0 0 56 0 0 0
90%
File Part #87... Response: 0 0 0 0 57 0 0 0
91%
File Part #88... Response: 0 0 0 0 58 0 0 0
92%
File Part #89... Response: 0 0 0 0 59 0 0 0
93%
File Part #90... Response: 0 0 0 0 5A 0 0 0
94%
File Part #91... Response: 0 0 0 0 5B 0 0 0
95%
File Part #92... Response: 0 0 0 0 5C 0 0 0
96%
File Part #93... Response: 0 0 0 0 5D 0 0 0
97%
File Part #94... Response: 0 0 0 0 5E 0 0 0
98%
File Part #95... Response: 0 0 0 0 5F 0 0 0
99%
File Part #96... Response: 0 0 0 0 60 0 0 0
100%
RADIO upload failed!
Ending session...
ERROR: Failed to confirm end of file transfer sequence!
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Are there anyone has done this type of work successfully?
Is it related to the flash tools hasn't support this device yet?
not sure if it makes a diff.. but have you rooted your device ?
pileiba said:
not sure if it makes a diff.. but have you rooted your device ?
Click to expand...
Click to collapse
Thanks for your reply.
Yes I have rooted the device. But as this procedure is in the download mode, is it related to rooted/non-rooted?
I just want to try another rom.
I have tried another way without modem.bin included and seems all the file could be uploaded to the device now.
But I still not sure about why the modem.bin couldn't been flashed
some other solutions I came across where here.. https://github.com/Benjamin-Dobell/Heimdall/issues/43 i.e. to try different versions of heimdell, try a 32bit operating system as opposed to 64 bit, and reinstall the samsung drivers. There is apparently a Heimdell 1.4 . http://www.glassechidna.com.au/2012/devblogs/heimdall-1-4-release-candidate-1/ . Lastly you could try a different usb cable and a different usb port. I think powered hubs sometimes work better.
I've seen a few different things that stated our watches have an 800 MHz processor. I was looking for a reason to tinker, so heres what I came up with via root and Busybox:
total used free shared buffers
Mem: 420 392 27 0 13
-/+ buffers: 379 40
Swap: 0 0 0
[email protected]:/ #
Processor : ARMv7 Processor rev 8 (v7l)
processor : 0
BogoMIPS : 1592.52
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 8
Chip name : EXYNOS4212
Hardware : SMDK4x12
Revision : 0005
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 210.1M 76.0K 210.0M 0% /dev
tmpfs 210.1M 0 210.1M 0% /mnt/secure
tmpfs 210.1M 0 210.1M 0% /mnt/asec
tmpfs 210.1M 0 210.1M 0% /mnt/obb
/dev/block/mmcblk0p20
787.4M 388.0M 399.4M 49% /system
/dev/block/mmcblk0p3 19.7M 4.2M 15.5M 21% /efs
/dev/block/mmcblk0p19
315.0M 5.5M 309.5M 2% /cache
/dev/block/mmcblk0p21
2.4G 119.2M 2.3G 5% /data
/data/media 2.4G 119.2M 2.2G 5% /mnt/shell/emulated
I was surprised at the processor, doesn't seem too shabby!
Also, if anyone screws up their build.prop and needs the stock, or wants to tinker, its attached.
How did you root it?
Sent from my SM-N900V now Free
http://forum.xda-developers.com/showpost.php?p=46340266&postcount=21
Hi,
I am running stock N960FXXS3CSG1 AP firmware on a freshly factory reset Exynos-based Note 9 device and I observed that when either face or iris is enabled as screen lock type, SystemUI is continuously generating warning logs as long as the screen is on. This can be seen by connecting the phone to a PC and running 'adb logcat' after enabling USB debugging. The warning logs are generated even if the phone is unlocked using the fingerprint sensor, without even showing the lock screen. Restarting the phone does not help.
The lines that are continuously written to the log by the SystemUI process are:
Code:
07-20 11:24:58.157 5439 5439 W View : requestLayout() improperly called by com.android.keyguard.biometric.KeyguardBiometricSmallIconView{c777788 V.E...... ......ID 0,84-1440,217 #7f0a0273 app:id/keyguard_iris_text_preview} during layout: running second layout pass
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayout is already in process
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayoutDuringLayout is already in process
07-20 11:24:58.157 5439 5439 I [email protected][StatusBar]: requestLayoutDuringLayout is already in process
07-20 11:24:58.159 5439 5439 W View : requestLayout() improperly called by com.android.systemui.statusbar.phone.NotificationPanelView{5a9da25 V.E...... ........ 0,0-1440,2960 #7f0a0387 app:id/notification_panel} during second layout pass: posting in next frame
07-20 11:24:58.159 5439 5439 W View : requestLayout() improperly called by com.android.keyguard.biometric.KeyguardBiometricSmallIconView{c777788 V.E...... ........ 0,84-1440,217 #7f0a0273 app:id/keyguard_iris_text_preview} during second layout pass: posting in next frame
This behavior causes high CPU usage and battery drain when either iris or face unlock is enabled.
Here is a snapshot of top running after the phone was unlocked, with face unlock enabled:
Code:
800%cpu 80%user 7%nice 104%sys 608%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
5439 u0_a8 20 0 4.9G 380M 300M S 74.3 6.7 8:16.99 com.android.systemui
4388 system 12 -8 3.0G 45M 37M S 31.6 0.7 5:07.57 surfaceflinger
4261 logd 30 10 21M 4.7M 2.7M S 18.3 0.0 4:04.49 logd
4366 system 20 0 166M 5.0M 4.3M S 16.0 0.0 2:03.32 [email protected]
2259 root RT 0 0 0 0 S 11.0 0.0 2:49.27 [decon0]
20277 root 20 0 0 0 0 S 7.0 0.0 0:06.64 [kworker/0:0]
20228 root 0 -20 0 0 0 S 6.6 0.0 0:02.47 [kworker/u17:1]
15695 root 0 -20 0 0 0 S 6.0 0.0 0:19.06 [kworker/u17:4]
4931 system 18 -2 5.4G 429M 318M S 5.6 7.6 32:10.51 system_server
21346 shell 20 0 12M 5.1M 3.9M R 3.6 0.0 0:00.35 top
This is how it looks when face and iris unlock are disabled (phone was restarted so different pids):
Code:
800%cpu 10%user 2%nice 9%sys 778%idle 0%iow 0%irq 0%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
4927 system 18 -2 5.2G 502M 400M S 11.0 8.9 5:07.68 system_server
17742 shell 20 0 12M 5.0M 3.8M R 3.3 0.0 0:00.33 top
17650 root 20 0 0 0 0 S 1.6 0.0 0:01.89 [kworker/0:2]
4569 wifi 20 0 19M 5.8M 5.5M S 1.6 0.1 0:08.97 wificond
6128 u0_a15 20 0 3.7G 138M 120M S 1.0 2.4 0:12.86 android.process.acore
6414 system 20 0 3.7G 132M 118M S 0.6 2.3 0:26.58 com.sec.android.sdhms
4532 system 20 0 11M 3.3M 3.2M S 0.6 0.0 0:10.69 argosd
7 root 20 0 0 0 0 S 0.6 0.0 0:09.04 [rcu_preempt]
5406 u0_a8 20 0 4.5G 358M 286M S 0.3 6.3 0:42.20 com.android.systemui
Here is the logcat output for pid/tid 5439 (com.android.systemui), starting from when the power button was pressed, with face unlock enabled:
https://pastebin.com/zX77zHW8
The messages at the end keep repeating until the screen is turned off.
Here is the logcat output with face unlock disabled:
https://pastebin.com/1An2X6TJ
Can anyone else run 'adb shell top' with face or iris unlock enabled and confirm whether this is a firmware issue or it's just something on my end?
Thanks!
Did you manage to figure it out? I'm getting the same exact issue.
artoria5 said:
Did you manage to figure it out? I'm getting the same exact issue.
Click to expand...
Click to collapse
Unfortunately, no. I was hoping to get more input on this. Samsung Community hasn't been much help either.