Database Users

[MOD/DEV] Charging Battery Animation with Dock Connected ** Help needed! **

OK this thread is dedicated to developing a WORKING charging battery icon animation. The main problem is this: ASUS' code only allows for still images to be drawn when the battery is charging (specifically when the dock is connected). Applying existing techniques to allow for animation results in the following exception:
Code:
W/dalvikvm( 149): threadid=8: thread exiting with uncaught exception (group=0x401ab760)
E/AndroidRuntime( 149): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 149): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) } in [email protected]
E/AndroidRuntime( 149): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:725)
E/AndroidRuntime( 149): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 149): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 149): at android.os.Looper.loop(Looper.java:132)
E/AndroidRuntime( 149): at com.android.server.ServerThread.run(SystemServer.java:608)
E/AndroidRuntime( 149): Caused by: java.lang.ClassCastException: android.graphics.drawable.AnimationDrawable cannot be cast to android.graphics.drawable.BitmapDrawable
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.adjustStatusBarDockLocked(DockManagerService.java:371)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.updateLocked(DockManagerService.java:317)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.updateDockBatteryState(DockManagerService.java:309)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.access$300(DockManagerService.java:55)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService$3.onReceive(DockManagerService.java:229)
E/AndroidRuntime( 149): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:716)
E/AndroidRuntime( 149): ... 4 more
The line in question is the following: "Caused by: java.lang.ClassCastException: android.graphics.drawable.AnimationDrawable cannot be cast to android.graphics.drawable.BitmapDrawable", which is pretty much self-explanatory.
Anyways, I have dug into it more and traced the issue back to the source where I believe it is triggered from. First off, let me explain what I did:
Extracted 'classes.dex' from 'services.jar'
Decompiled 'classes.dex' using dex2jar
Was only able to view the source code with JD-GUI (don't know how to make edits)
Traced the issue to the file \com\android\server\asus\DockManagerService.class
In the 'DockManagerService.class', there are references to BitmapDrawable which I think need to be AnimatedDrawable, since that is what the logcat debug message says above (in the OP). I have no idea what to change it to exactly (let alone recompile it), but I believe this is where we need to look ('...' is edited-out code):
Code:
private void adjustStatusBarDockLocked()
...
...
localImageView.setImageResource(n);
int i1 = this.mDockBatteryLevel;
localImageView.setImageLevel(i1);
Bitmap localBitmap = ((BitmapDrawable)localImageView.getDrawable().getCurrent()).getBitmap();
localRemoteViews.setImageViewBitmap(16908985, localBitmap);
}
Also, near the top of 'DockManagerService.class', there is the following:
Code:
import android.graphics.Bitmap;
import android.graphics.drawable.BitmapDrawable;
import android.graphics.drawable.Drawable;
...not sure if we'd need to add something like 'android.graphics.drawable.AnimationDrawable;' in order to get animations supported?
Anyways, that's about as far as I can get with my current knowledge. If any other experienced dev is out there, it would be super great if they could give their thoughts, suggestions, ANYTHING!
Hopefully after we get to the bottom of this, we'll be able to have animated charging icons which support the ASUS dock.
OH, and forgot to mention that users of the OC kernel by Clemsyn (which is currently NOT built from source, since the 3.1 official ASUS source has not yet been released) do not suffer from this problem, since that OC kernel has broken support for the dock battery level/charging status. It currently only becomes an issue with the Stock 3.1 kernel which is able to correctly read the Dock Status.
Thanks in advance!

This may (or may not) help - but -
Can you locate the source for "BatteryService" and see if anything in there helps?
Also - did the Asus "limited release" for the Dock issues not contain a working Dock Status? If it did, someone may have the files kicking around from that which could have the parts you need in?

I use a widget called "bat stat" that uses animation, but it does not handle the dock (of course). It is small, has great animation and graphics, and is not well know yet it is in the market.
Was thinking to do my own tf version, will let you know if succeeds.
Hope this helps.
=======
UPDATE:
I finished the *graphics* to represent various tablet & dock and charging or discharging states.
I will look at some widget *codes* next.

[Q] Straight Answer on CIQ

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.

(request) team venom viperRom beta testers

Team venom will soon be supporting the desire z with the assistance of lms24
ViperZ is based on the other wvga viperRoms on the dhd, vivo, and vivow
We are looking for 5-10 beta testers who can run the rom for a few days prior to release to make sure there are no huge bugs that would prevent a release
Testers should meet following requirements:
Proficient with adb and logcats
Have run sense4 roms on this phone for at least a little while before
Are active forum members (ie didn't join a month ago and have very few posts-
Ethical (won't share beta links with anyone)
Please post here if interested !
Beta should be out this week

Let's do it
Sent from my HTC Vision using xda premium

I can participate too.

I'd be willing to try but I don't have much time in my hands. This is full sense, correct? Also would you prefer us not to use things such as PMR or ROM Cleaner?

I'm willing to participate. i have a spare desire z at home and i used the rom on dhd so i can compare if needer

crestofawave said:
I'd be willing to try but I don't have much time in my hands. This is full sense, correct? Also would you prefer us not to use things such as PMR or ROM Cleaner?
Click to expand...
Click to collapse
yes, please run the rom as close to stock as possible :fingers-crossed:
ok, guys check your inboxes....just run the rom for a day or two, and let me know if there are any serious bugs (bootlooping)
G2 users, you need to be on a Z Hboot

Have fun while you're testing the Rom, guys. Let's hope this runs as great on your phones as on my DZ.
Sent from my HTC Desire Z using xda app-developers app

Smooth installation with aroma. No errors. No bootloops. Also no reboots yet.
Lowmemorykiller works great, even tho there is 50-60 mb free ram, no stutters in games. Actually better gaming then aosp roms.
I went ahead and changed the phone ID from s710e to HTC Desire Z since it bothers me and i do it with every rom before installation. I hope its okay.
All in all great job with the rom.

Don't have time to flash it now will do so later tonight. Looks promising already loved it on dhd
Sent from my HTC Vision using Tapatalk 2

OC settings in venom tweaks not working. or i cant seem to save the new frequencies. they just go back to default when i close the app.

btrst said:
OC settings in venom tweaks not working. or i cant seem to save the new frequencies. they just go back to default when i close the app.
Click to expand...
Click to collapse
ah, i guess torxx didnt remove them before the latest update (i did in viperINC)
good catch, thanks

Something strange,
I tried to enable swap with swap_enabler script but it said swap was already enabled. So i checked with terminal and it shows 122 mb swap space enabled without me enabling it. Strange thing is, my sdcard partitioned for 256 mb swap space. I checked the init.d scripts and none of them has any lines indicating automatic swap enabling. Im really confused here.

Yo, OP send beta towards this way if you don't mind?
I'm off all week and have spare G2 and Always On my phone atleast 18hours of the day literally.
-thanks
Sent from my HTC Vision using xda premium

The PDF Reader app is FC'ing for me. Other than that and what btrst mentioned I haven't had any other issues. The only thing I did was disable CPU Rendering and use CPU Tuner for CPU freq management.
The ROM is between smooth and choppy for me, and has fairly decent performance, things to be expected as we're talking about Sense 4. Quite impressive as far as I'm concerned. I also like the very extensive customizations, especially the Sweep to Unlock.
I can imagine that getting rid of all redundant stuff using ROM Cleaner will increase the ROM's Performance. Thanks for the share

crestofawave said:
The PDF Reader app is FC'ing for me. Other than that and what btrst mentioned I haven't had any other issues. The only thing I did was disable CPU Rendering and use CPU Tuner for CPU freq management.
The ROM is between smooth and choppy for me, and has fairly decent performance, things to be expected as we're talking about Sense 4. Quite impressive as far as I'm concerned. I also like the very extensive customizations, especially the Sweep to Unlock.
I can imagine that getting rid of all redundant stuff using ROM Cleaner will increase the ROM's Performance. Thanks for the share
Click to expand...
Click to collapse
can you logcat the pdf reader fc?

Here you go. (Longer logcat here). I launched the app several times. The longer log is fudged up as I'm running adb from cmd. I managed to salvage a few lines that had to do with the app and make them easier to read. Hope it helps.
Code:
I/Adreno200-EGLSUB( 101): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 101): <GetImageAttributes:1158>: RGBX_8888
I/ActivityManager( 184): Start proc com.htc.pdfviewer for activity com.htc.pdfviewer/.ActPDFReader: pid=9821 uid=10013 gids={2001, 3003, 1015, 1006, 5001}
W/ResourceType( 184): Skipping entry 0x7f04000c in package table 0 because it is not complex!
D/dalvikvm( 102): GC_EXPLICIT freed 38K, 27% free 2802K/3807K, paused 2ms+9ms
D/ConnectivityService( 184): onUidRulesChanged(uid=10013, uidRules=0)
D/dalvikvm( 102): GC_EXPLICIT freed <1K, 27% free 2802K/3807K, paused 3ms+2ms
D/dalvikvm( 102): GC_EXPLICIT freed <1K, 27% free 2802K/3807K, paused 2ms+2ms
I/ActivityThread( 9821): Pub com.htc.provider.pdfviewer: com.htc.pdfviewer.provider.PdfProvider
D/com.htc.pdfviewer.provider.PdfProvider( 9821): onCreate
D/com.htc.pdfviewer.provider.PdfProvider( 9821): AvailableDataDirectorySize 797159424
D/SqliteDatabaseCpp( 9821): Registering sqlite logging func: /data/data/com.htc.pdfviewer/databases/book.db
D/SqliteDatabaseCpp( 9821): DB info: open db, path = /data/data/com.htc.pdfviewer/databases , key = fkko, flag = 6, file size = 5120
D/SqliteDatabaseCpp( 9821): DB info: path = /data/data/com.htc.pdfviewer/databases , key = fkko, handle: 0x1fda9b0, type: w, r/w: (0,1), mode: truncate, disk free size: 760 M
I/ActivityThread( 9821): Pub com.htc.pdfviewer.PdfSuggestionProvider: com.htc.pdfviewer.PdfSuggestionProvider
W/dalvikvm( 9821): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/htc/pdfviewer/JNIHost;
D/AndroidRuntime( 9821): Shutting down VM
W/dalvikvm( 9821): threadid=1: thread exiting with uncaught exception (group=0x40aaf228)
E/EmbeddedLogger( 184): App crashed! Process: com.htc.pdfviewer
E/EmbeddedLogger( 184): App crashed! Package: com.htc.pdfviewer v400371055 (4.0.2215132855.371055.304684)
E/EmbeddedLogger( 184): Application Label: PDF Viewer
E/AndroidRuntime( 9821): FATAL EXCEPTION: main
E/AndroidRuntime( 9821): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 9821): at com.htc.pdfviewer.ActPDFReader.<init>(ActPDFReader.java:577)
E/AndroidRuntime( 9821): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 9821): at java.lang.Class.newInstance(Class.java)
E/AndroidRuntime( 9821): at android.app.Instrumentation.newActivity(Instrumentation.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.access$600(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
E/AndroidRuntime( 9821): at android.os.Handler.dispatchMessage(Handler.java)
E/AndroidRuntime( 9821): at android.os.Looper.loop(Looper.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.main(ActivityThread.java)
E/AndroidRuntime( 9821): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 9821): at java.lang.reflect.Method.invoke(Method.java)
E/AndroidRuntime( 9821): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
E/AndroidRuntime( 9821): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
E/AndroidRuntime( 9821): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9821): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load pdfviewer: findLibrary returned null
E/AndroidRuntime( 9821): at java.lang.Runtime.loadLibrary(Runtime.java)
E/AndroidRuntime( 9821): at java.lang.System.loadLibrary(System.java)
E/AndroidRuntime( 9821): at com.htc.pdfviewer.JNIHost.<clinit>(JNIHost.java:768)
E/AndroidRuntime( 9821): ... 16 more
W/ActivityManager( 184): Force finishing activity com.htc.pdfviewer/.ActPDFReader
D/ViewRootImpl( 184): @@@- disable SystemServer HW acceleration
D/OpenGLRenderer( 587): Flushing caches (mode 1)
D/OpenGLRenderer( 587): Flushing caches (mode 0)
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x58dd8000 size:15052800 offset:13516800
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x56fbb000 size:4608000 offset:3072000
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x5a545000 size:6144000 offset:4608000
I/Adreno200-EGLSUB( 101): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 101): <GetImageAttributes:1102>: RGBA_8888
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{40daba60 com.htc.pdfviewer/.ActPDFReader}

thanks, seems to be missing the proper lib
im just gonna remove it from the rom, adobe reader is better (imo)

Just saw the new release for DZ, Thank you guys. I'm finishing downloading and i will share my experience with this rom after installation

desperately waiting for this rom keep up the good work thanks..

ahmedrzvi said:
desperately waiting for this rom keep up the good work thanks..
Click to expand...
Click to collapse
wait no longer! ITS BEEN OUT FOR TWO DAYS!
great for a full sense 4 ROM.
If you really want sense and all its features plus more, this is near perfect

[Q] At pressing play on YouTube (app) video device reboots

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.

Potentially major android security flaw - advice sought

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.