Pixel 4, running android 11, fully updated acording to the phone software.
I purchased a Pixel device because they are known to have access to the most up to date security patches and are one of a few brands that check the validity of carrier service messages. Despite all this, I'm still having serious issues with the device. I wanted to ask the experts here for their thoughts and advice on how to proceed; I've already reported this to google and to cyber crime officials, none of whom seemed to care.
Here's the story:
I use outlook for my emails. On installing the Outlook app, it requests authorisation as a device administrator. Usually deactivating the device administrator prevents the app from operating. However, my phone started crashing so I began to investigate and found I could deactivate outlook as an administrator and continue to send and receive emails as if nothing had happened. This concerned me enough to do a full factory data reset.
The factory reset was conducted without restoring or transferring my previous data.
I Immediately went to the security menu and updated the system security patch version to Nov 2020, but when google play security update ran, an “Unknown” versioned update installed with no option to cancel, and now it’s displaying “September 2020” stating no further updates are available.
I was fairly suprised to see my mother’s Huawei is on the Google Play Security patch "October 2020".
On previous Android phones following a factory reset, a text would arrive with settings that eventually automatically installed. That stopped when I got the Pixel (thanks to it's ability to validate such messages?); but now we have the “Unknown” play security update instead; which makes me think this could be a targeted attack.
Other observed effects:
1) Outlook device administrator once again has no effect on the apps usage.
2) At about 8:30 this morning, a request to view my screen arrived on my phone (like you get if you call google support), and I was not on a call to support at the time.
3) The structure and visabiltiy of settings changes from time to time; preventing access to certain things (see screenshots in link below - taken within an hour of each other).
4) I book train tickets through the Trainline App. I bought two sets of tickets. The first of which appeared in the apps history, the second set did not. Thankfully I was able to travel thanks to the email recepit.
5) I ordered shopping through amazon prime. I carefully checked the delivery address at the start of the process, and on order confirmation. The map displayed showed the correct information. On the day of delivery, the shopping went to a different address altogether.
6) After the update installed, reporting issues via the default browser became impossible. The menus won't display or form validation rules / captcha checks just refuse the submisison.
Link to screenshots: "https://photos.app.goo.gl/dKdVUkiEwLvEkv3u9"
I can only conclude that the device has been compromised, and that recent vulnerabilities have led to a situation where the system data used in a factory reset, or the network (cell or wifi) has been compromised to enable the delivery of a package to the device that is able to convince it that it is a critical update direct from google; and to install it no matter what.
Can anyone offer any advice on how to proceed?
at first read, my guess is that you have an issue with a/b partitions being out of sync. you should read up on a/b partitions. 2nd. i would recommend that you download the appropriate software images from google directly for your device and reflash them and then wipe everything and then flash again.
not sure what else to recommend without significantly more information.
Thank you - A/B
Hi
Thanks for the tip to look into A/B seamless system updates. I've been investigating and it seems to be involved in the issues I'm having.
More over, it's making the issue really tricky to research.
I got ADB back up and running on my PC to have a good look at the logfiles. I ran logcat -d and saved it to a file.
My Mum then called (always welcome) but one of the issues I'd been having with call quality kicked in. When we finished I reran logcat and saved to a new file. I also had a CMD prompt window open with one I'd not exported,.
A = First Export
B = Second export
C = CMD record
Date/Time marker chosen for spot comparison: 11-30 09:22:41.123
Test A=B=C = True (to ensure logging is reliable between runs and methods)
Results:
A=B=C A=B A=C B=C
FALSE TRUE TRUE TRUE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE FALSE FALSE
FALSE TRUE TRUE TRUE
Summary:
Whilst the log entries look the same to user, they are not
A always matches B - outputting to the same format was consistent for the sample
Format of export causes inconsistent matching
"
11-30 09:22:41.123 939 1047 I ASH : @ 1431.144: tmd3702v: Calibrating POFFSET
11-30 09:22:41.123 2873 11564 E AsyncOperation: operation=xlb opStatusCode=12009 [CONTEXT service_id=45 ]
11-30 09:22:41.123 2873 11564 E AsyncOperation: OperationException[Status{statusCode=unknown status code: 12009 resolution=null}]
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at aqyf.g[email protected]@20.42.17 (150400-342117392):1)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at aqyf.fP[email protected]@20.42.17 (150400-342117392):31)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at ywh.run[email protected]@20.42.17 (150400-342117392):9)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at bmxp.run[email protected]@20.42.17 (150400-342117392):2)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at rgn.c[email protected]@20.42.17 (150400-342117392):6)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at rgn.run[email protected]@20.42.17 (150400-342117392):8)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at rmi.run[email protected]@20.42.17 (150400-342117392):0)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at java.lang.Thread.run(Thread.java:923)"
11-30 09:22:41.123 939 1047 I CHRE : @ 1431.145: [gesture] dropping duplicate proximity!
11-30 09:22:41.123 939 1047 I chatty : uid=1000(system) [email protected] expire 9 lines
11-30 09:22:41.123 2873 11564 E AsyncOperation: operation=xlb opStatusCode=12009 [CONTEXT service_id=45 ]
11-30 09:22:41.123 2873 11564 E AsyncOperation: OperationException[Status{statusCode=unknown status code: 12009 resolution=null}]
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at aqyf.g[email protected]@20.42.17 (150400-342117392):1)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at aqyf.fP[email protected]@20.42.17 (150400-342117392):31)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at ywh.run[email protected]@20.42.17 (150400-342117392):9)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at bmxp.run[email protected]@20.42.17 (150400-342117392):2)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at rgn.c[email protected]@20.42.17 (150400-342117392):6)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at rgn.run[email protected]@20.42.17 (150400-342117392):8)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at rmi.run[email protected]@20.42.17 (150400-342117392):0)"
"11-30 09:22:41.123 2873 11564 E AsyncOperation: at java.lang.Thread.run(Thread.java:923)" "
Expecting to find an extra space or two, imagine my suprise when I found two things happening reported at the same time from the same device; only caught because I happened to leave a command prompt window open.
The fact that this could be different.... well it certainly can't be called tanmperproof beyond reasonable doubt; sadly.
Related
I'm assuming that, for the most part, the apps on the Market that are designed to "discover" CIQ or traces of it are going to look for any small thing that might be left over from the removals, regardless of whether or not it's actually still part of our ROMs. That said, for all our devs who've put out ROMs that claim to not have CIQ on board, how do we know for sure that it's been removed?
Case in point - I'm currently running ACS ICS v5, and every ACS release that I've been on has claimed to have CIQ removed - yet, I ran 4 different CIQ discovery apps on a whim this morning, and they all claimed to find Carrier IQ on board. Is it just hype, or have we been missing something all along?
/and by "we," I mean, all the devs who work way harder on this stuff than me
//is basically just a ROM slut
From what I've read, the CIQ code is still baked into the kernel. BUT because the guts of CIQ were removed, the code has nothing to talk to.
That may be the culprit being detected. If you are getting other "false positives" then post screen shots of your output.
I am running SRF 1.2 still and from the OP for that ROM states that it is completely removed, not disabled or partitially removed.
"What's the secret sauce? Carrier IQ, the infamous Sprint spyware package, has been completely removed! More details in the second post - you won't believe what we found! Themers and other mod developers take note, many modifications were made to the system in order to achieve this exclusive feature."
When I run Voodoo CIQ app it says.
Carrier IQ has been found and is active
Detection score: 370
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_client.so
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
found: system 9960 2376 213724 14076 ffffffff 00000000 S android.iqd
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Yeah, I guess Voodoo is the one I hadn't run yet - according to that, I'm in the clear:
Voodoo Carrier IQ Detector report:
Build fingerprint:
sprint/SPH-D700/SPH-D700:2.3.5/GINGERBREAD/EI22:user/release-keys
Carrier IQ elements found
− however it seems inactive
Detection score: 170
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, weight 50)
nothing found
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: I/ActivityManager( 285): No longer want android.iqd (pid 2073): hidden #16
Test for: Linux kernel drivers
(KERNEL_DRIVERS, weight 50)
nothing found
Test for: System services
(SERVICES, weight 70)
nothing found
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_service.so
found: /system/lib/libiq_client.so
Test for: ROM configs
(ETC_CONFIG, weight 0)
nothing found
Test for: Packages
(PACKAGES, weight 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
nothing found
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Linux kernel dmesg log
(DMESG, weight 100)
nothing found
Mine had a score of 170 and then re-ran it to show someone that mine is inactive and then the score jumped to 370 and said active. I'm thinking wtf...
when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.
The Root said:
when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.
Click to expand...
Click to collapse
/thread 10char
I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)
lancelane said:
I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)
Click to expand...
Click to collapse
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!
rekrdskratcher said:
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!
Click to expand...
Click to collapse
You must not have read the disclaimer on the app. It says it may report false positives still.
Hey all, first post here. Not a crazy power user but after my recent update my S5 has been dying way faster. According to gsam it's mostly Android system and kernel. Adding dumps
GSam Labs - Battery Monitor - Export Data
Android System
Aug 30, 2016 2:09:19 PM
Usage Details
CPU Usage:46m 30s
Bytes Sent:69.80 KB
Bytes Received:298.26 KB
App UID:1000
Wakelock Detail
Included Packages
System updates
IPsec Service
DiagMonAgent
Color adjustment
Voice Recorder
UcsPinpad
ClipboardSaveService
bootagent
RilNotifier
ClipboardUIService
SamsungDLPService
Fingerprints
Filter Installer
IMS Service
Fused Location
ANT HAL Service
SetDefaultLauncher
SmartFaceService
Camera test
Software update
TetheringAutomation
SecurityLogAgent
PopupuiReceiver
KnoxAppsUpdateAgent
Settings
Remote Controls
DumpCollector
com.android.wallpapercropper
BluetoothTest
USBSettings
Launcher
Assistant menu
Baby crying detector
SecurityManagerService
com.sec.android.app.wfdbroker
Samsung MirrorLink 1.1
SysScope
Input Devices
Samsung text-to-speech engine
Key Chain
KNOX
com.qualcomm.timeservice
withTV
Settings storage
WlanTest
Screen Mirroring
Setup Wizard
Service mode
GestureService
Enterprise Sim Pin Service
Perso
Factory Mode
EasyOneHand
Backup and Restore Manager
Mobile tracker
MTP application
Samsung keyboard
Private Mode Service
EmergencyManagerService
BBCAgent
DeviceTest
com.qualcomm.atfwd
KnoxFolderContainer
com.samsung.InputEventApp
SyncMLSvc
Phone
Easy settings
com.sec.bcservice
Interaction control
Application installer
Security policy updates
Kies Application BnR
Beaming Service
SilentLogging
Security storage
HwModuleTest
SyncmlPhoneDataService
Help
Android System
SecVideoEngineService
IOTHiddenMenu
DeviceKeystring
WallpaperPicker
KNOX SetupWizardClient
Included Processes
/system/bin/servicemanager
/system/bin/surfaceflinger
/system/bin/rfs_access
/system/bin/qseecomd
/system/bin/edmaudit
/system/bin/ddexe
/system/bin/smdexe
/system/bin/connfwexe
/system/bin/ss_conn_daemon
/system/bin/ss_kbservice_daemon
/system/bin/sensorhubservice
/system/bin/npsmobex
/system/bin/bintvoutservice
/system/bin/imsd
/system/bin/sdp_cryptod
/system/bin/gatekeeperd
/system/bin/ATFWD-daemon
/system/bin/time_daemon
/system/bin/audiod
/system/bin/vcsFPService
/system/bin/secure_storage_daemon
/system/bin/cs
system_server
/system/bin/mcDriverDaemon
/system/bin/tlc_server
/system/bin/otp_server
com.samsung.ucs.agent.boot
com.sec.imsservice
com.sec.sve
com.samsung.ucs.ucspinpad
com.sec.android.app.wfdbroker
com.sec.imsservice:ConfigService
com.ipsec.service
/system/bin/vpnclientd
com.samsung.android.fingerprint.service
com.qualcomm.telephony
com.sec.android.app.mt
com.android.settings
com.policydm
system:ui
android:ui
Thread-9134
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Aug 30, 2016 2:09:36 PM
Usage Details
CPU Usage:27m 27s
Bytes Sent:1.44 MB
Bytes Received:361.33 KB
App UID:0
Wakelock Detail
Included Packages
Included Processes
/init
kthreadd
ksoftirqd/0
kworker/u:0
kworker/u:0H
kworker/u:1H
sync_supers
bdi-default
kblockd
system
khubd
irq/305-max7780
kswapd0
fsnotify_mark
ecryptfs-kthrea
spi7
spi32765
file-storage
irq/627-cypress
irq/628-synapti
cfinteractive
irq/170-msm_sdc
irq/253-msm_sdc
irq/256-msm_sdc
irq/626-SSP_Int
ssp_sensorhub_t
mmcqd/0
mmcqd/0rpmb
irq/195-ngd_sli
ngd_rx_thread1
msm_thermal:fre
boost_sync/0
boost_sync/1
boost_sync/2
boost_sync/3
mmcqd/2
/sbin/ueventd
jbd2/mmcblk0p23
jbd2/mmcblk0p26
jbd2/mmcblk0p24
jbd2/mmcblk0p21
jbd2/mmcblk0p12
jbd2/mmcblk0p22
jbd2/mmcblk0p25
/system/bin/vold
msm_slim_qmi_cl
irq/288-wcd9xxx
/sbin/healthd
/system/bin/lmkd
/system/bin/netd
/system/bin/debuggerd
/system/bin/installd
/system/vendor/bin/thermal-engine
zygote
dhd_watchdog_th
dhd_dpc
dhd_rxf
flush-179:0
mdss_fb0
kworker/0:0H
pkgld
kworker/u:1
kworker/u:4
kauditd
irq/33-cpubw_hw
/system/bin/mpdecision
kworker/0:0
sdcard
loop0
kworker/0:1H
kworker/u:2
kworker/u:5
kworker/u:6
kworker/0:1
kworker/u:7
kworker/0:2H
ksoftirqd/2
kworker/0:3
wl_event_handle
kworker/0:2
kworker/u:3
flush-ecryptfs-
flush-179:64
ksoftirqd/3
kworker/u:8
kworker/3:0
kworker/3:0H
kworker/2:0H
kworker/2:1
kworker/1:0
ksoftirqd/1
kworker/2:1H
kworker/3:1H
Sent from my cell phone
Just a quick bump here and also if anyone needs more info to diagnose or has questions let me know
Sent from my cell phone
Hi. I'm having the same problem. It only occurs when connected to a certain wifi-network. I'm not rooted, but figuered out (thanks to cpu monitor) that IMS service is the main process that drains my battery, (while doing nothing). When I shut off wifi, this service disappears from the top list.
I hope to figure out how to close this service or to fix its behavior.
Just another bump here. Mine definitely drains while on WiFi, but it's doing it off of WiFi networks. It goes down like 10% an hour off of WiFi, with consistent signal, and with no real reason except that GSAM tells me it's almost entirely "Android System" and "Kernel (Android OS)"
I just upgraded from 9/1 to 9/9 and suffer from way more battery drain than normal.
I barely use my phone, and typically have ~70% left at bedtime. (this has been typical for years).
Since updating to the 9/9 build, I ran out of battery before lunch....
There have been an unusually high number of changes in the last 9 days:
https://www.cmxlog.com/13/klte
Same here...
It's little unbelievable but I have this battery after many tries ... With marshmallow, btu last version.
First of all,I bought a new battery. I did a full factory reset and install only Rom with a gsam, to find what drain the battery. I leave the phone , no "play" with it, and the results is over 6% drain per hour!
Close Google back up, auto brightness, weather app...and many apps, don't need as Polaris office.
Can anyone help me to find what drain the battery and fix it?
prntscr.com/ci7c65
prntscr.com/ci7ciy
prntscr.com/ci7cn2
SM-G935F
I'm running the latest eRobot rom using H-vitamin kernel, android MM on Exynos N910C.
Everything works smooth and fast, but when I start the YouTube app and then as soon as I press the playbutton it immediately drops out and reboots.
Here's what aLogrec catches of that moment;
Code:
10-14 23:45:52.745 4845 4845 D StatusBar.NetworkController: refreshNwBoosterIndicator - setNWBoosterIndicators(false)
10-14 23:45:52.750 4845 4845 D StatusBar.NetworkController: refreshNwBoosterIndicator - setNWBoosterIndicators(false)
10-14 23:45:53.735 4845 4845 D StatusBar.NetworkController: refreshViews connected={ wifi } level=1 combinedSignalIconId=0x7f02070d/com.android.systemui:drawable/stat_sys_wifi_signal_3 mobileLabel=Hi wifiLabel="Vlinderbos" emergencyOnly=false combinedLabel="Vlinderbos" mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x7f020610/com.android.systemui:drawable/stat_sys_signal_1_auto_rotate mQSPhoneSignalIconId=0x7f0201b6/com.android.systemui:drawable/ic_qs_signal_1 mDataDirectionIconId=0x0/(null) mDataSignalIconId=0x7f020610/com.android.systemui:drawable/stat_sys_signal_1_auto_rotate mDataTypeIconId=0x7f0204c1/com.android.systemui:drawable/stat_sys_data_connected_4g mQSDataTypeIconId=0x7f0201bc/com.android.systemui:drawable/ic_qs_signal_4g mNoSimIconId=0x0/(null) mWifiIconId=0x7f02070d/com.android.systemui:drawable/stat_sys_wifi_signal_3 mQSWifiIconId=0x7f0203ca/com.android.systemui:drawable/qs_tile_wifi_signal_3 mWifiActivityIconId=0x7f0206c3/com.android.systemui:drawable/stat_sys_signal_inout mBluetoothTetherIconId=0x7f0206ec/com.android.systemui:drawable/stat_sys_tether_bluetooth
10-14 23:45:53.735 4845 4845 D StatusBar.NetworkController: refreshNwBoosterIndicator - setNWBoosterIndicators(false)
10-14 23:45:53.740 4845 4845 D StatusBar.NetworkController: refreshNwBoosterInd--------- beginning of system
10-14 23:46:32.585 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{cf5961f 6440:com.samsung.android.coreapps/5011}
10-14 23:46:32.600 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{cf5961f 6440:com.samsung.android.coreapps/5011}
10-14 23:46:32.615 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{44e1034 6454:com.sec.android.app.mt/1000}
10-14 23:46:32.905 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{4b8968a 6514:com.sec.android.app.sbrowser/u0a98}
10-14 23:46:32.920 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{93254fb 6534:com.sec.modem.settings/1000}
10-14 23:46:32.945
And that's pretty much useless, because when I press play it also stops logging anything! I've looked at errors and stuff out of the ordinary when the YouTube app starts, but there's nothing there that doesn't look normal.
It looks as if video-starting tries to grab a part of memory or cache or GPU that's broken. Any ideas?
This was caused by the enhanced camera apk's version of media_profiles.xml offered by http://forum.xda-developers.com/note-4/themes-apps/galaxy-note-4-n910c-ultra-quality-t3356025 for erobot ROM.
Phone would reboot at every video playback app, not just YouTube.
I logged the events leading up to and after and this is what I see:
After the pause:
09-21 17:51:22.101 2109 2190 D vol.MediaSessions: onPlaybackStateChanged com.pandora.android STATE_PAUSED PlaybackState {state=2, position=154000, buffered position=0, speed=0.0, updated=286644238, actions=6, custom actions=[Action:mName='Thumb Down, mIcon=2130838088, mExtras=Bundle[mParcelledData.dataSize=144], Action:mName='Thumb Up, mIcon=2130838091, mExtras=Bundle[mParcelledData.dataSize=144], Action:mName='Skip Track, mIcon=2130838043, mExtras=Bundle[mParcelledData.dataSize=144], Action:mName='Bookmark, mIcon=2130837765, mExtras=Bundle[mParcelledData.dataSize=144]], active item id=-1, error=null}
Click to expand...
Click to collapse
and immediately before the pause:
09-21 17:51:22.069 1407 4449 D PowerManagerService: [api] release WakeLock SCREEN_BRIGHT_WAKE_LOCK 'p.ft.d' (uid=10201, pid=9027, ws=null) (uid=10201, pid=9027, ws=null, pkg=com.pandora.android, elapsedTime=1811656) (0x0) .09-21 17:51:22.092 1407 1407 D EdgeLightingManager: showForNotification : isInteractive=false, isHeadUp=false, color=0, sbn = StatusBarNotification(pkg=com.pandora.android user=UserHandle{0} id=1 tag=null key=0|com.pandora.android|1|null|10201: Notification(pri=0 contentView=com.pandora.android/0x7f0400c2 vibrate=null sound=null defaults=0x0 flags=0x62 color=0x00000000 category=transport vis=PUBLIC semFlags=0x0 semPriority=0))werManagerService: [api] release WakeLock SCREEN_BRIGHT_WAKE_LOCK 'p.ft.d' (uid=10201, pid=9027, ws=null) (uid=10201, pid=9027, ws=null, pkg=com.pandora.android, elapsedTime=1811656) (0x0)
Click to expand...
Click to collapse
09-21 17:51:22.097 1407 5688 D MediaSessionRecord: setPlaybackState oldState:3, newState:2, packageName:com.pandora.android
Click to expand...
Click to collapse
09-21 17:51:22.092 1407 1407 D EdgeLightingManager: showForNotification : isInteractive=false, isHeadUp=false, color=0, sbn = StatusBarNotification(pkg=com.pandora.android user=UserHandle{0} id=1 tag=null key=0|com.pandora.android|1|null|10201: Notification(pri=0 contentView=com.pandora.android/0x7f0400c2 vibrate=null sound=null defaults=0x0 flags=0x62 color=0x00000000 category=transport vis=PUBLIC semFlags=0x0 semPriority=0))
Click to expand...
Click to collapse
Any input would be appreciated.
Thanks
Dave
Did you protect the Pandora app from being suspended in standby by doze (see settings, apps, menu, special access, battery use)?
I believe so. There are two places to set pandora to not be monitored from what I can see.
themissionimpossible said:
Did you protect the Pandora app from being suspended in standby by doze (see settings, apps, menu, special access, battery use)?
Click to expand...
Click to collapse
I believe so. I have found 2 placed where I can change the battery monitoring for the app I think.
Dave
Yes, correct, Pandora is to be indicated there as a non battery optimized app.
It already is
Anyone have this occuring?
Does your phone also disable wifi when the screen is off (wifi in standby: off)?
Nope I turned that off. WiFi always on during sleep.
Dave
Seems it's not just pandora either. Any audio player stops.
Just saw the details on the new Mi Watch. As an OG Pebble purchaser (and owner of a Pebble Steel) I still like the rectangular form factor. So with a 3100, 1GB of RAM and a 570mAh battery, this thing looks like my perfect next watch. However it is only available In China, has a Chinese UI and no Google Play app store installed. Would any purchaser be able to side load the app store? Or use non-Xiaomi watch faces and apps? Any thoughts ?
I'm very interested in this watch, by the moment there are not much information
Maybe it's possible to install Wear OS apk's by adb
Enviado desde mi Pixel 3a mediante Tapatalk
I think it will be possible to install apps using abd because it based on Android wear so android wear apk is ment to work perfectly I guess
Sideloading apks should be possible. However it is running the chinese version of wear os and it has to be paired with the china android wear os app, too, which doesn't use google play services.
It's hard to say if stuff like gpay will function.
Apparently, the iOS version of wear os does not make this difference though.
Hopefully, sideloading the playstore would do the trick.
If the bootloader can be easily unlocked, we could flash roms or the global version.
with ram 1gb, processor snap wear 3100 + LTE and the price. I think it's great. Just waiting for how to install in global version rom on it
i have it here. tried to install a working music player for the last 4 hours. no luck.
erbsenmatsch said:
i have it here. tried to install a working music player for the last 4 hours. no luck.
Click to expand...
Click to collapse
Damn - sorry to hear that. I was super close to ordering one last week, but held off at the last minute until I could get a better sense for what was possible.
We're you able to get the play store installed, or were you trying to install the music players from apks? What happened when you tried to do the installs?
Hoping you have better luck moving forwards - would love to hear any updates.
1Markymark said:
Damn - sorry to hear that. I was super close to ordering one last week, but held off at the last minute until I could get a better sense for what was possible.
We're you able to get the play store installed, or were you trying to install the music players from apks? What happened when you tried to do the installs?
Hoping you have better luck moving forwards - would love to hear any updates.
Click to expand...
Click to collapse
You can easy install the play store with adb - but it won't work. Google apps witch need to sync your google account won't work too. The Watch want to sync the account with your phone .. but it will fail. All other apps seems to be fine (telegram etc.) . The biggest problem is that you can't use the Latin Gboard so you can only write Chinese :-/
Handwriting won't load other languages.
Another issue for me is, that I need to use my phone with English language .. if I set it to Germany , the watch will be completed in Chinese.
But I can say .. I love this watch
*Update*
Just found the "Wear Keyboard" apk from playstore .. it works, but you can only use "default keyboard language".
Also I managed to get Handwriting working (updated the apk).
Gerrett said:
You can easy install the play store with adb - but it won't work. Google apps witch need to sync your google account won't work too. The Watch want to sync the account with your phone .. but it will fail. All other apps seems to be fine (telegram etc.) . The biggest problem is that you can't use the Latin Gboard so you can only write Chinese :-/
Handwriting won't load other languages.
Another issue for me is, that I need to use my phone with English language .. if I set it to Germany , the watch will be completed in Chinese.
But I can say .. I love this watch
*Update*
Just found the "Wear Keyboard" apk from playstore .. it works, but you can only use "default keyboard language".
Also I managed to get Handwriting working (updated the apk).
Click to expand...
Click to collapse
Will get my hand on it very soon. Will try out things.
Update: got the watch, the chinese WearOS is really annoying, no Google app usable on watch: playstore, keep, google map and the most annoying is the Keyboard (I know imputing on watch is kind of stupid, but I want to do some quick responds if needed.) - English keyboard works partial (using the same wear keyboard above), no solution for other language.
Anyway, let hope there's global rom or some mod available, but I like the screen and the watch .
try bootloader oem unlock
but can't unlock bootloader
Yep, we need an unlocked bootloader !
installed com.android.vending_17.3.27 (Google Play Store) apk via adb
installed com.google.android.gms_19.6.29 (Google Play Services) apk via adb
but logcat still spits errors out, like something's missing or blocked:
Code:
11-30 22:52:51.827 1661 1675 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.os.UpdateLock.UPDATE_LOCK_CHANGED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
11-30 22:52:52.141 6106 6106 W Finsky : [2] dig.a(6): Null bundle, which breaks event chain!. Creating a new logging context.
11-30 22:52:52.203 6106 6114 W System : A resource failed to call end.
11-30 22:52:52.204 6106 6114 W System : A resource failed to call end.
11-30 22:52:52.223 6106 6106 E AndroidRuntime: FATAL EXCEPTION: main
11-30 22:52:52.223 6106 6106 E AndroidRuntime: Process: com.android.vending, PID: 6106
11-30 22:52:52.223 6106 6106 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.vending/com.google.android.finsky.wear.activities.MainActivity}: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.vending/cwc}; have you declared this activity in your AndroidManifest.xml?
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2914)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3049)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1809)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6680)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: Caused by: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.vending/cwc}; have you declared this activity in your AndroidManifest.xml?
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2005)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Instrumentation.execStartActivity(Instrumentation.java:1673)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:4587)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at eo.startActivityForResult(PG:4)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:4545)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at eo.startActivityForResult(PG:2)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivity(Activity.java:4906)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.startActivity(Activity.java:4874)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at ewx.b(PG:35)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at ewx.a(PG:19)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at com.google.android.finsky.wear.activities.MainActivity.a(PG:5)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at ewx.onCreate(PG:6)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7144)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7135)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2894)
11-30 22:52:52.223 6106 6106 E AndroidRuntime: ... 11 more
11-30 22:52:52.226 6106 6106 W Finsky.CrashDetector: Crash at version: 17.3.27-all [5] [PR] 278037957 cnt=4 ts=1575128953673 cause=RuntimeException fg=false".
11-30 22:52:52.238 1661 1944 W ActivityManager: Force finishing activity com.android.vending/com.google.android.finsky.wear.activities.MainActivity
11-30 22:52:52.342 1661 1675 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
11-30 22:52:52.343 1661 1675 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
11-30 22:52:52.545 1661 3363 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.scheduler.JobSchedulerEngine$PhoneskyJobSchedulerJobService in 1000ms
Actually, Google play services and google service framework all are pre-installed on the watch, our biggest problem is same as Tic watch run China wearOS- we can't sync Google service from our phone to watch (due to the wearOS app used to connect the watch is china wearOS app).
And... There's not a way to unlock bootloader of the watch.
---------- Post added at 10:59 ---------- Previous post was at 10:14 ----------
erbsenmatsch said:
i have it here. tried to install a working music player for the last 4 hours. no luck.
Click to expand...
Click to collapse
There's mi music app in mi watch app store, you also need the china mi music app on your phone, can control music app from there.
Spotify control also works.
I have no intention of playing music directly from the watch....
ted presley said:
Actually, Google play services and google service framework all are pre-installed on the watch, our biggest problem is same as Tic watch run China wearOS- we can't sync Google service from our phone to watch (due to the wearOS app used to connect the watch is china wearOS app).
And... There's not a way to unlock bootloader of the watch.
---------- Post added at 10:59 ---------- Previous post was at 10:14 ----------
There's mi music app in mi watch app store, you also need the china mi music app on your phone, can control music app from there.
Spotify control also works.
I have no intention of playing music directly from the watch....
Click to expand...
Click to collapse
It's sounds like on tic watch they also didn't find a way to get google sync working?
Gerrett said:
It's sounds like on tic watch they also didn't find a way to get google sync working?
Click to expand...
Click to collapse
Yep, same annoying Chinese wearOS .... But it's fun if we can find a workaround [emoji28][emoji28].
Sent from my MI 9 using Tapatalk
ted presley said:
Yep, same annoying Chinese wearOS .... But it's fun if we can find a workaround [emoji28][emoji28].
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
Yep, let's find one
Tried to update the Wearos.apk .. but it will failed . No Idea what else we can do with a locked bootloader.
Someone need to unlock it
It seem fastboot oem unlock worksss...
All we need a working TWRP and.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 9 using Tapatalk
soralis0123 said:
try bootloader oem unlock
but can't unlock bootloader
Click to expand...
Click to collapse
It wont do anything after you click unlock?
Because there's no TWRP or zip rom yet, I haven't clicked on unlock button (due to a unlock one may break the official firmware update)
ted presley said:
Yep, same annoying Chinese wearOS .... But it's fun if we can find a workaround [emoji28][emoji28].
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
ted presley said:
It seem fastboot oem unlock worksss...
All we need a working TWRP and.....View attachment 4891937
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
It's not working .. I run through the unlock process, but device is still locked
Has anyone the changelog from the system update today?
What a pity to hear. So any notice? The device still be formatted but it's still lock? Or it tell error in unlocking?
Sent from my MI 9 using Tapatalk