SystemUI Color enhancements #2
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SystemUI Color enhancements Changing Colors in Framework to match the AOSP Colors
AsuraNico
referenced
this pull request
Jan 3, 2017
Change-Id: I3d6d8473f46e4e1071f4db96b45aca159ce8c5f3
Contributor
|
Hi there; This is an automated reply, to let you know LineageOS doesn't merge pull You can submit your change requests through our public review system, That review system is an installation of Google's Gerrit code review. Thanks! |
Rashed97
pushed a commit
to Rashed97/android_frameworks_base
that referenced
this pull request
Dec 24, 2017
AKA the pixel navbar This is a combination of 8 commits. This is the 1st commit message: Pixel Navbar, reverse engineered from smali. Notes: - This is forcing the Pixel Home button on people, and it looks ugly with the other nav buttons being hollow - There MAY still be a few fixes yet to be found in this code because it WAS a big file to RE from smali. I have yet to find any, but time is the best tester. - Shoutout to @bigrushdog for providing a decompiled form used to verify the smali and as a guideline for the more obsure smali sections. It was a big help. - Tagging myself here to see adoption rate. @USA-RedDragon PureNexus Edits: By: @BeansTown106 *squashed with the landscape fix *cleaned up some of the if statements and removed the unused constants *removed the renamed icons, this was unnecessary as we will vectorize pixel icons Change-Id: Ia45fc89e4f1518fcabc379c4790d1955a026daee This is the commit message LineageOS#2: Vectorize all navbar icons (pixel theme) fix landscape bug *the only thing navbar related that is not vectorized is the lightsout/carmode/menu icons This is the commit message LineageOS#3: Pixel navbar: allow disabling based on config Create new config_allowOpaLayout bool to allow themers to disable the Pixel Navbar Fixes the dreaded "yellow" home button Change-Id: I69ad9a0d87317c9d9732b08b33ceabd096afee77 This is the commit message LineageOS#4: Pixel Navbar animation toggle [1/2] *made to work with the exposure for themers to disable navbar animation Change-Id: Icb057edaf0c49933d6a882df3af627a076a14561 This is the commit message LineageOS#5: Pixel navbar: remove this. and OpaLayout references, cleanup Since it's all on the same file, I don't think they are needed (?) Replace some hardcoded int values with meaningful variables, like MotionEvent Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba This is the commit message LineageOS#6: Pixel navbar: Fix Home button FC Change-Id: I7c463999a76ee02f1f5af615ddcff3c05ca4e4f2 This is the commit message LineageOS#7: Reload Pixel Home Animation without reboot Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba
Rashed97
pushed a commit
to Rashed97/android_frameworks_base
that referenced
this pull request
Jan 5, 2018
AKA the pixel navbar This is a combination of 8 commits. This is the 1st commit message: Pixel Navbar, reverse engineered from smali. Notes: - This is forcing the Pixel Home button on people, and it looks ugly with the other nav buttons being hollow - There MAY still be a few fixes yet to be found in this code because it WAS a big file to RE from smali. I have yet to find any, but time is the best tester. - Shoutout to @bigrushdog for providing a decompiled form used to verify the smali and as a guideline for the more obsure smali sections. It was a big help. - Tagging myself here to see adoption rate. @USA-RedDragon PureNexus Edits: By: @BeansTown106 *squashed with the landscape fix *cleaned up some of the if statements and removed the unused constants *removed the renamed icons, this was unnecessary as we will vectorize pixel icons Change-Id: Ia45fc89e4f1518fcabc379c4790d1955a026daee This is the commit message LineageOS#2: Vectorize all navbar icons (pixel theme) fix landscape bug *the only thing navbar related that is not vectorized is the lightsout/carmode/menu icons This is the commit message LineageOS#3: Pixel navbar: allow disabling based on config Create new config_allowOpaLayout bool to allow themers to disable the Pixel Navbar Fixes the dreaded "yellow" home button Change-Id: I69ad9a0d87317c9d9732b08b33ceabd096afee77 This is the commit message LineageOS#4: Pixel Navbar animation toggle [1/2] *made to work with the exposure for themers to disable navbar animation Change-Id: Icb057edaf0c49933d6a882df3af627a076a14561 This is the commit message LineageOS#5: Pixel navbar: remove this. and OpaLayout references, cleanup Since it's all on the same file, I don't think they are needed (?) Replace some hardcoded int values with meaningful variables, like MotionEvent Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba This is the commit message LineageOS#6: Pixel navbar: Fix Home button FC Change-Id: I7c463999a76ee02f1f5af615ddcff3c05ca4e4f2 This is the commit message LineageOS#7: Reload Pixel Home Animation without reboot Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba
Rashed97
pushed a commit
to Rashed97/android_frameworks_base
that referenced
this pull request
Mar 30, 2018
AKA the pixel navbar This is a combination of 8 commits. This is the 1st commit message: Pixel Navbar, reverse engineered from smali. Notes: - This is forcing the Pixel Home button on people, and it looks ugly with the other nav buttons being hollow - There MAY still be a few fixes yet to be found in this code because it WAS a big file to RE from smali. I have yet to find any, but time is the best tester. - Shoutout to @bigrushdog for providing a decompiled form used to verify the smali and as a guideline for the more obsure smali sections. It was a big help. - Tagging myself here to see adoption rate. @USA-RedDragon PureNexus Edits: By: @BeansTown106 *squashed with the landscape fix *cleaned up some of the if statements and removed the unused constants *removed the renamed icons, this was unnecessary as we will vectorize pixel icons Change-Id: Ia45fc89e4f1518fcabc379c4790d1955a026daee This is the commit message LineageOS#2: Vectorize all navbar icons (pixel theme) fix landscape bug *the only thing navbar related that is not vectorized is the lightsout/carmode/menu icons This is the commit message LineageOS#3: Pixel navbar: allow disabling based on config Create new config_allowOpaLayout bool to allow themers to disable the Pixel Navbar Fixes the dreaded "yellow" home button Change-Id: I69ad9a0d87317c9d9732b08b33ceabd096afee77 This is the commit message LineageOS#4: Pixel Navbar animation toggle [1/2] *made to work with the exposure for themers to disable navbar animation Change-Id: Icb057edaf0c49933d6a882df3af627a076a14561 This is the commit message LineageOS#5: Pixel navbar: remove this. and OpaLayout references, cleanup Since it's all on the same file, I don't think they are needed (?) Replace some hardcoded int values with meaningful variables, like MotionEvent Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba This is the commit message LineageOS#6: Pixel navbar: Fix Home button FC Change-Id: I7c463999a76ee02f1f5af615ddcff3c05ca4e4f2 This is the commit message LineageOS#7: Reload Pixel Home Animation without reboot Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba
Koloses
pushed a commit
to GalaxyFork/android_frameworks_base
that referenced
this pull request
May 29, 2018
If mSurface has already been released in another thread, this would result in a null-pointer dereference in SurfaceSession contructor i.e. in nativeCreateScoped(). 7757 7757 F DEBUG : pid: 1402, tid: 1583, name: android.anim >>> system_server <<< 7757 7757 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xd0 7757 7757 F DEBUG : Cause: null pointer dereference ... <trimmed> 7757 7757 F DEBUG : backtrace: 7757 7757 F DEBUG : #00 pc 000000000007fe58 /system/lib64/libgui.so (android::Surface::getIGraphicBufferProducer() const) 7757 7757 F DEBUG : LineageOS#1 pc 00000000000ff000 /system/lib64/libandroid_runtime.so (android::nativeCreateScoped(_JNIEnv*, _jclass*, long)+52) 7757 7757 F DEBUG : LineageOS#2 pc 0000000000ac8968 /system/framework/arm64/boot-framework.oat (offset 0x614000) (android.content.res.XmlBlock.nativeCreateParseState [DEDUPED]+152) 7757 7757 F DEBUG : LineageOS#3 pc 0000000001327d24 /system/framework/arm64/boot-framework.oat (offset 0x614000) (android.view.SurfaceSession.<init>+52) 7757 7757 F DEBUG : LineageOS#4 pc 00000000014b7320 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.drawSizeMismatchSnapshot+128) 7757 7757 F DEBUG : LineageOS#5 pc 00000000014b784c /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.drawSnapshot+188) 7757 7757 F DEBUG : LineageOS#6 pc 00000000014b6f2c /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.create+2684) 7757 7757 F DEBUG : LineageOS#7 pc 00000000014b0158 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotController.createStartingSurface+72) 7757 7757 F DEBUG : LineageOS#8 pc 00000000014a5ca0 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.SnapshotStartingData.createStartingSurface+96) 7757 7757 F DEBUG : LineageOS#9 pc 000000000144b030 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.AppWindowContainerController.lambda$-com_android_server_wm_AppWindowContainerController_4735+496) ... <trimmed> Change-Id: I41268c7680d3885c85fc3b682d0eba7415674062 Signed-off-by: Adesh15 <[email protected]>
i81u812
pushed a commit
to i81u812/android_frameworks_base
that referenced
this pull request
Jul 30, 2018
If mSurface has already been released in another thread, this would result in a null-pointer dereference in SurfaceSession contructor i.e. in nativeCreateScoped(). 7757 7757 F DEBUG : pid: 1402, tid: 1583, name: android.anim >>> system_server <<< 7757 7757 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xd0 7757 7757 F DEBUG : Cause: null pointer dereference ... <trimmed> 7757 7757 F DEBUG : backtrace: 7757 7757 F DEBUG : #00 pc 000000000007fe58 /system/lib64/libgui.so (android::Surface::getIGraphicBufferProducer() const) 7757 7757 F DEBUG : LineageOS#1 pc 00000000000ff000 /system/lib64/libandroid_runtime.so (android::nativeCreateScoped(_JNIEnv*, _jclass*, long)+52) 7757 7757 F DEBUG : LineageOS#2 pc 0000000000ac8968 /system/framework/arm64/boot-framework.oat (offset 0x614000) (android.content.res.XmlBlock.nativeCreateParseState [DEDUPED]+152) 7757 7757 F DEBUG : LineageOS#3 pc 0000000001327d24 /system/framework/arm64/boot-framework.oat (offset 0x614000) (android.view.SurfaceSession.<init>+52) 7757 7757 F DEBUG : LineageOS#4 pc 00000000014b7320 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.drawSizeMismatchSnapshot+128) 7757 7757 F DEBUG : LineageOS#5 pc 00000000014b784c /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.drawSnapshot+188) 7757 7757 F DEBUG : LineageOS#6 pc 00000000014b6f2c /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.create+2684) 7757 7757 F DEBUG : LineageOS#7 pc 00000000014b0158 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotController.createStartingSurface+72) 7757 7757 F DEBUG : LineageOS#8 pc 00000000014a5ca0 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.SnapshotStartingData.createStartingSurface+96) 7757 7757 F DEBUG : LineageOS#9 pc 000000000144b030 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.AppWindowContainerController.lambda$-com_android_server_wm_AppWindowContainerController_4735+496) ... <trimmed> Change-Id: I41268c7680d3885c85fc3b682d0eba7415674062 Signed-off-by: Pranav Vashi <[email protected]>
i81u812
pushed a commit
to i81u812/android_frameworks_base
that referenced
this pull request
Jul 30, 2018
AKA the pixel navbar This is a combination of 8 commits. This is the 1st commit message: Pixel Navbar, reverse engineered from smali. Notes: - This is forcing the Pixel Home button on people, and it looks ugly with the other nav buttons being hollow - There MAY still be a few fixes yet to be found in this code because it WAS a big file to RE from smali. I have yet to find any, but time is the best tester. - Shoutout to @bigrushdog for providing a decompiled form used to verify the smali and as a guideline for the more obsure smali sections. It was a big help. - Tagging myself here to see adoption rate. @USA-RedDragon PureNexus Edits: By: @BeansTown106 *squashed with the landscape fix *cleaned up some of the if statements and removed the unused constants *removed the renamed icons, this was unnecessary as we will vectorize pixel icons Change-Id: Ia45fc89e4f1518fcabc379c4790d1955a026daee This is the commit message LineageOS#2: Vectorize all navbar icons (pixel theme) fix landscape bug *the only thing navbar related that is not vectorized is the lightsout/carmode/menu icons This is the commit message LineageOS#3: Pixel navbar: allow disabling based on config Create new config_allowOpaLayout bool to allow themers to disable the Pixel Navbar Fixes the dreaded "yellow" home button Change-Id: I69ad9a0d87317c9d9732b08b33ceabd096afee77 This is the commit message LineageOS#4: Pixel Navbar animation toggle [1/2] *made to work with the exposure for themers to disable navbar animation Change-Id: Icb057edaf0c49933d6a882df3af627a076a14561 This is the commit message LineageOS#5: Pixel navbar: remove this. and OpaLayout references, cleanup Since it's all on the same file, I don't think they are needed (?) Replace some hardcoded int values with meaningful variables, like MotionEvent Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba This is the commit message LineageOS#6: Pixel navbar: Fix Home button FC Change-Id: I7c463999a76ee02f1f5af615ddcff3c05ca4e4f2 This is the commit message LineageOS#7: Reload Pixel Home Animation without reboot Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba Signed-off-by: Erfan Abdi <[email protected]>
Rashed97
pushed a commit
to Rashed97/android_frameworks_base
that referenced
this pull request
Aug 4, 2018
AKA the pixel navbar This is a combination of 8 commits. This is the 1st commit message: Pixel Navbar, reverse engineered from smali. Notes: - This is forcing the Pixel Home button on people, and it looks ugly with the other nav buttons being hollow - There MAY still be a few fixes yet to be found in this code because it WAS a big file to RE from smali. I have yet to find any, but time is the best tester. - Shoutout to @bigrushdog for providing a decompiled form used to verify the smali and as a guideline for the more obsure smali sections. It was a big help. - Tagging myself here to see adoption rate. @USA-RedDragon PureNexus Edits: By: @BeansTown106 *squashed with the landscape fix *cleaned up some of the if statements and removed the unused constants *removed the renamed icons, this was unnecessary as we will vectorize pixel icons Change-Id: Ia45fc89e4f1518fcabc379c4790d1955a026daee This is the commit message LineageOS#2: Vectorize all navbar icons (pixel theme) fix landscape bug *the only thing navbar related that is not vectorized is the lightsout/carmode/menu icons This is the commit message LineageOS#3: Pixel navbar: allow disabling based on config Create new config_allowOpaLayout bool to allow themers to disable the Pixel Navbar Fixes the dreaded "yellow" home button Change-Id: I69ad9a0d87317c9d9732b08b33ceabd096afee77 This is the commit message LineageOS#4: Pixel Navbar animation toggle [1/2] *made to work with the exposure for themers to disable navbar animation Change-Id: Icb057edaf0c49933d6a882df3af627a076a14561 This is the commit message LineageOS#5: Pixel navbar: remove this. and OpaLayout references, cleanup Since it's all on the same file, I don't think they are needed (?) Replace some hardcoded int values with meaningful variables, like MotionEvent Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba This is the commit message LineageOS#6: Pixel navbar: Fix Home button FC Change-Id: I7c463999a76ee02f1f5af615ddcff3c05ca4e4f2 This is the commit message LineageOS#7: Reload Pixel Home Animation without reboot Change-Id: I4d7b2fe57d3e1bf2fa034bf81efb11d37a5ebfba
ChronoMonochrome
pushed a commit
to CustomROMs/android_frameworks_base
that referenced
this pull request
Sep 13, 2018
If mSurface has already been released in another thread, this would result in a null-pointer dereference in SurfaceSession contructor i.e. in nativeCreateScoped(). 7757 7757 F DEBUG : pid: 1402, tid: 1583, name: android.anim >>> system_server <<< 7757 7757 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xd0 7757 7757 F DEBUG : Cause: null pointer dereference ... <trimmed> 7757 7757 F DEBUG : backtrace: 7757 7757 F DEBUG : #00 pc 000000000007fe58 /system/lib64/libgui.so (android::Surface::getIGraphicBufferProducer() const) 7757 7757 F DEBUG : LineageOS#1 pc 00000000000ff000 /system/lib64/libandroid_runtime.so (android::nativeCreateScoped(_JNIEnv*, _jclass*, long)+52) 7757 7757 F DEBUG : LineageOS#2 pc 0000000000ac8968 /system/framework/arm64/boot-framework.oat (offset 0x614000) (android.content.res.XmlBlock.nativeCreateParseState [DEDUPED]+152) 7757 7757 F DEBUG : LineageOS#3 pc 0000000001327d24 /system/framework/arm64/boot-framework.oat (offset 0x614000) (android.view.SurfaceSession.<init>+52) 7757 7757 F DEBUG : LineageOS#4 pc 00000000014b7320 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.drawSizeMismatchSnapshot+128) 7757 7757 F DEBUG : LineageOS#5 pc 00000000014b784c /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.drawSnapshot+188) 7757 7757 F DEBUG : LineageOS#6 pc 00000000014b6f2c /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotSurface.create+2684) 7757 7757 F DEBUG : LineageOS#7 pc 00000000014b0158 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.TaskSnapshotController.createStartingSurface+72) 7757 7757 F DEBUG : LineageOS#8 pc 00000000014a5ca0 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.SnapshotStartingData.createStartingSurface+96) 7757 7757 F DEBUG : LineageOS#9 pc 000000000144b030 /system/framework/oat/arm64/services.odex (offset 0x5be000) (com.android.server.wm.AppWindowContainerController.lambda$-com_android_server_wm_AppWindowContainerController_4735+496) ... <trimmed> Bug: 74129970 Change-Id: I41268c7680d3885c85fc3b682d0eba7415674062
villarleg
pushed a commit
to villarleg/android_frameworks_base
that referenced
this pull request
Dec 18, 2018
11-13 20:00:00.527 10645 10645 I crash_dump64: performing dump of process 1467 (target tid = 10124) 11-13 20:00:00.538 10645 10645 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-13 20:00:00.539 10645 10645 F DEBUG : Build fingerprint: 'HONOR/BKL-L09/HWBKL:8.0.0/HUAWEIBKL-L09S/172(C432):user/release-keys' 11-13 20:00:00.539 10645 10645 F DEBUG : Revision: '0' 11-13 20:00:00.539 10645 10645 F DEBUG : ABI: 'arm64' 11-13 20:00:00.539 10645 10645 F DEBUG : pid: 1467, tid: 10124, name: Visualizer >>> com.android.systemui <<< 11-13 20:00:00.539 10645 10645 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 11-13 20:00:00.539 10645 10645 F DEBUG : Abort message: 'FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x7c633df0f4)' 11-13 20:00:00.539 10645 10645 F DEBUG : x0 0000000000000000 x1 000000000000278c x2 0000000000000006 x3 0000000000000008 11-13 20:00:00.539 10645 10645 F DEBUG : x4 0000000000008080 x5 0000000000008080 x6 0000000000008080 x7 0000000000000038 11-13 20:00:00.539 10645 10645 F DEBUG : x8 0000000000000083 x9 40ef6d32d31c854a x10 0000000000000000 x11 fffffffc7ffffbdf 11-13 20:00:00.539 10645 10645 F DEBUG : x12 0000000000000001 x13 000000005beb1f30 x14 0005a1f49bc3a000 x15 0000112f9e154a12 11-13 20:00:00.539 10645 10645 F DEBUG : x16 0000007cffb6f2c8 x17 0000007cffaad0d0 x18 00000000fffbfffe x19 00000000000005bb 11-13 20:00:00.539 10645 10645 F DEBUG : x20 000000000000278c x21 0000007d000d96d0 x22 0000000000000001 x23 0000000000000035 11-13 20:00:00.539 10645 10645 F DEBUG : x24 0000007d000c6fc8 x25 0000007d000c7680 x26 0000007c52a14588 x27 0000000000000000 11-13 20:00:00.539 10645 10645 F DEBUG : x28 0000000000000005 x29 0000007c52a141a0 11-13 20:00:00.539 10645 10645 F DEBUG : sp 0000007c52a14160 lr 0000007cffaa1bfc pc 0000007cffaa1c24 11-13 20:00:00.564 10645 10645 F DEBUG : 11-13 20:00:00.564 10645 10645 F DEBUG : backtrace: 11-13 20:00:00.564 10645 10645 F DEBUG : #00 pc 0000000000021c24 /system/lib64/libc.so (abort+116) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#1 pc 0000000000082f04 /system/lib64/libc.so (__fortify_fatal(char const*, ...)+120) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#2 pc 0000000000082600 /system/lib64/libc.so (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#3 pc 00000000000824b4 /system/lib64/libc.so (pthread_mutex_lock+228) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#4 pc 00000000000a8c54 /system/lib64/libmedia.so (android::Visualizer::periodicCapture()+56) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#5 pc 00000000000a8aac /system/lib64/libmedia.so (android::Visualizer::CaptureThread::threadLoop()+88) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#6 pc 000000000000f9d8 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#7 pc 00000000000b4980 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#8 pc 0000000000081938 /system/lib64/libc.so (__pthread_start(void*)+36) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#9 pc 0000000000023478 /system/lib64/libc.so (__start_thread+68) Change-Id: Ic7f9788df8a38084c3b150eaa22d67f869085ca2 Signed-off-by: Pranav Vashi <[email protected]>
lineageos-gerrit
pushed a commit
that referenced
this pull request
Feb 6, 2019
*1 -- not truncate(2) but "PRAGMA wal_checkpoint(TRUNCATE)" Otherwise, depending on how an app operate on a DB, SQLite may not have a chance to "shrink" the WAL file. Fixes: 112777941 Bug: 111939259 Test: atest /android/master/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCompatibilityWalFlagsTest.java Test: Manual test with google dailer: 1. With normalized_spam.db-wal > 100MB and receive a phone call -> WAL file gets truncated to 0 bytes. 2. Restart the dialer process and receive a phone call again -> WAL file is already 0 bytes; won't be truncated. 3. Restart with the WAL file deleted Same as #2. WAL file will be created before the added logic, but is 0 bytes, so it won't be truncated. 4. Test with settings put global sqlite_compatibility_wal_flags truncate_size=1024 -> make sure the threshold is overridden Merged-in: I2b193603e5dfa493ccccb8123db592f0e9c0e7ae Change-Id: I2b193603e5dfa493ccccb8123db592f0e9c0e7ae (cherry picked from commit 96e0600)
partcyborg
pushed a commit
to partcyborg/android_frameworks_base-lineage
that referenced
this pull request
Jul 31, 2019
11-13 20:00:00.527 10645 10645 I crash_dump64: performing dump of process 1467 (target tid = 10124) 11-13 20:00:00.538 10645 10645 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-13 20:00:00.539 10645 10645 F DEBUG : Build fingerprint: 'HONOR/BKL-L09/HWBKL:8.0.0/HUAWEIBKL-L09S/172(C432):user/release-keys' 11-13 20:00:00.539 10645 10645 F DEBUG : Revision: '0' 11-13 20:00:00.539 10645 10645 F DEBUG : ABI: 'arm64' 11-13 20:00:00.539 10645 10645 F DEBUG : pid: 1467, tid: 10124, name: Visualizer >>> com.android.systemui <<< 11-13 20:00:00.539 10645 10645 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 11-13 20:00:00.539 10645 10645 F DEBUG : Abort message: 'FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x7c633df0f4)' 11-13 20:00:00.539 10645 10645 F DEBUG : x0 0000000000000000 x1 000000000000278c x2 0000000000000006 x3 0000000000000008 11-13 20:00:00.539 10645 10645 F DEBUG : x4 0000000000008080 x5 0000000000008080 x6 0000000000008080 x7 0000000000000038 11-13 20:00:00.539 10645 10645 F DEBUG : x8 0000000000000083 x9 40ef6d32d31c854a x10 0000000000000000 x11 fffffffc7ffffbdf 11-13 20:00:00.539 10645 10645 F DEBUG : x12 0000000000000001 x13 000000005beb1f30 x14 0005a1f49bc3a000 x15 0000112f9e154a12 11-13 20:00:00.539 10645 10645 F DEBUG : x16 0000007cffb6f2c8 x17 0000007cffaad0d0 x18 00000000fffbfffe x19 00000000000005bb 11-13 20:00:00.539 10645 10645 F DEBUG : x20 000000000000278c x21 0000007d000d96d0 x22 0000000000000001 x23 0000000000000035 11-13 20:00:00.539 10645 10645 F DEBUG : x24 0000007d000c6fc8 x25 0000007d000c7680 x26 0000007c52a14588 x27 0000000000000000 11-13 20:00:00.539 10645 10645 F DEBUG : x28 0000000000000005 x29 0000007c52a141a0 11-13 20:00:00.539 10645 10645 F DEBUG : sp 0000007c52a14160 lr 0000007cffaa1bfc pc 0000007cffaa1c24 11-13 20:00:00.564 10645 10645 F DEBUG : 11-13 20:00:00.564 10645 10645 F DEBUG : backtrace: 11-13 20:00:00.564 10645 10645 F DEBUG : #00 pc 0000000000021c24 /system/lib64/libc.so (abort+116) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#1 pc 0000000000082f04 /system/lib64/libc.so (__fortify_fatal(char const*, ...)+120) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#2 pc 0000000000082600 /system/lib64/libc.so (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#3 pc 00000000000824b4 /system/lib64/libc.so (pthread_mutex_lock+228) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#4 pc 00000000000a8c54 /system/lib64/libmedia.so (android::Visualizer::periodicCapture()+56) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#5 pc 00000000000a8aac /system/lib64/libmedia.so (android::Visualizer::CaptureThread::threadLoop()+88) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#6 pc 000000000000f9d8 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#7 pc 00000000000b4980 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#8 pc 0000000000081938 /system/lib64/libc.so (__pthread_start(void*)+36) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#9 pc 0000000000023478 /system/lib64/libc.so (__start_thread+68) Change-Id: Ic7f9788df8a38084c3b150eaa22d67f869085ca2
pengus77
pushed a commit
to pengus77/frameworks_base
that referenced
this pull request
Sep 30, 2019
11-13 20:00:00.527 10645 10645 I crash_dump64: performing dump of process 1467 (target tid = 10124) 11-13 20:00:00.538 10645 10645 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 11-13 20:00:00.539 10645 10645 F DEBUG : Build fingerprint: 'HONOR/BKL-L09/HWBKL:8.0.0/HUAWEIBKL-L09S/172(C432):user/release-keys' 11-13 20:00:00.539 10645 10645 F DEBUG : Revision: '0' 11-13 20:00:00.539 10645 10645 F DEBUG : ABI: 'arm64' 11-13 20:00:00.539 10645 10645 F DEBUG : pid: 1467, tid: 10124, name: Visualizer >>> com.android.systemui <<< 11-13 20:00:00.539 10645 10645 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 11-13 20:00:00.539 10645 10645 F DEBUG : Abort message: 'FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x7c633df0f4)' 11-13 20:00:00.539 10645 10645 F DEBUG : x0 0000000000000000 x1 000000000000278c x2 0000000000000006 x3 0000000000000008 11-13 20:00:00.539 10645 10645 F DEBUG : x4 0000000000008080 x5 0000000000008080 x6 0000000000008080 x7 0000000000000038 11-13 20:00:00.539 10645 10645 F DEBUG : x8 0000000000000083 x9 40ef6d32d31c854a x10 0000000000000000 x11 fffffffc7ffffbdf 11-13 20:00:00.539 10645 10645 F DEBUG : x12 0000000000000001 x13 000000005beb1f30 x14 0005a1f49bc3a000 x15 0000112f9e154a12 11-13 20:00:00.539 10645 10645 F DEBUG : x16 0000007cffb6f2c8 x17 0000007cffaad0d0 x18 00000000fffbfffe x19 00000000000005bb 11-13 20:00:00.539 10645 10645 F DEBUG : x20 000000000000278c x21 0000007d000d96d0 x22 0000000000000001 x23 0000000000000035 11-13 20:00:00.539 10645 10645 F DEBUG : x24 0000007d000c6fc8 x25 0000007d000c7680 x26 0000007c52a14588 x27 0000000000000000 11-13 20:00:00.539 10645 10645 F DEBUG : x28 0000000000000005 x29 0000007c52a141a0 11-13 20:00:00.539 10645 10645 F DEBUG : sp 0000007c52a14160 lr 0000007cffaa1bfc pc 0000007cffaa1c24 11-13 20:00:00.564 10645 10645 F DEBUG : 11-13 20:00:00.564 10645 10645 F DEBUG : backtrace: 11-13 20:00:00.564 10645 10645 F DEBUG : #00 pc 0000000000021c24 /system/lib64/libc.so (abort+116) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#1 pc 0000000000082f04 /system/lib64/libc.so (__fortify_fatal(char const*, ...)+120) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#2 pc 0000000000082600 /system/lib64/libc.so (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#3 pc 00000000000824b4 /system/lib64/libc.so (pthread_mutex_lock+228) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#4 pc 00000000000a8c54 /system/lib64/libmedia.so (android::Visualizer::periodicCapture()+56) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#5 pc 00000000000a8aac /system/lib64/libmedia.so (android::Visualizer::CaptureThread::threadLoop()+88) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#6 pc 000000000000f9d8 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#7 pc 00000000000b4980 /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#8 pc 0000000000081938 /system/lib64/libc.so (__pthread_start(void*)+36) 11-13 20:00:00.564 10645 10645 F DEBUG : LineageOS#9 pc 0000000000023478 /system/lib64/libc.so (__start_thread+68) Change-Id: Ic7f9788df8a38084c3b150eaa22d67f869085ca2
SagarMakhar
pushed a commit
to SagarMakhar/android_frameworks_base-1
that referenced
this pull request
Feb 9, 2020
For security reasons, the system UID can't make URI permission as itself; it always needs to do so on behalf of a specific app. To handle this, we grant notification Uri permissions as the UID that sent a given notification. To give meaningful debug messages to developers, check to see if the caller has permissions to grant Uri access when they're enqueuing a notification. If they're targeting P, throw any security issues back at the caller; if older SDK, log and ignore that Uri. Since multiple notifications can grant access to the same content, we need unique UriPermissionOwner per active notification. For example, consider these two notifications: 1. sound=content://sound, image=content://image1 2. sound=content://sound, image=content://image2 When LineageOS#1 is cancelled, we still need to keep the content://sound grant active until LineageOS#2 is also cancelled. Using unique owners means that ActivityManagerService tracks reference counting on our behalf. Optimizations to avoid allocations in hot code paths. Test: atest frameworks/base/services/tests/uiservicestests/src/com/android/server/notification Bug: 9069730 Change-Id: I69601793538adcbf06c4986a2fb1ea2dd9d876eb
SagarMakhar
pushed a commit
to SagarMakhar/android_frameworks_base-1
that referenced
this pull request
Feb 9, 2020
b/77862560 detected that when converting an apk to binary using aapt2, all resource ids of attributes that have been replaced with resource identifiers become set to the identifier of the first attribute. This is because the attribute names are all empty because the names are not necessary since the resource ids are present. The empty attribute names all map to the same string pool reference and cause all the ids to be the first empty string into the string pool. The ag/3897499 approach to fix the specified bug was extremely inefficient and caused hour long builds. This change takes advantage of the multimap data structure to do lookups efficiently. Bug: 77862560 Test: Converted apk in listed bug from proto to binary and observed correct resource ids and correct badging. Also built the Android tree to check for regressions in build time. Change-Id: I27a9ee4ffbed8b9ff6f238ad315cdf87b588947c
SagarMakhar
pushed a commit
to SagarMakhar/android_frameworks_base-1
that referenced
this pull request
Feb 9, 2020
SagarMakhar
pushed a commit
to SagarMakhar/android_frameworks_base-1
that referenced
this pull request
Feb 9, 2020
…nto pi-dev am: b2182c4 Change-Id: Ib7829b0203134eecdfd59a3dcd1e78b8fbdd39b4
SagarMakhar
pushed a commit
to SagarMakhar/android_frameworks_base-1
that referenced
this pull request
Feb 9, 2020
krasCGQ
pushed a commit
to kud-workspace/android_frameworks_base
that referenced
this pull request
Aug 20, 2020
Pull webview patches from aospa
FaN11X
added a commit
to FaN11X/android_frameworks_base
that referenced
this pull request
May 12, 2021
merge latest upstream
althafvly
pushed a commit
to LOS-M8916/android_frameworks_base
that referenced
this pull request
Jun 26, 2021
Add Battery Styles
sn-00-x
pushed a commit
to sn-00-x/android_frameworks_base
that referenced
this pull request
Sep 22, 2021
The chooser and resolver activities run as a special system UI process belonging to the core "android" package, separate from both system_server and com.android.systemui. This process, named "android:ui", runs separately under each user with the special app ID 1000 (SYSTEM_UID). Check the app ID instead of the UID to fix detection of SYSTEM_UID processes in secondary users. This fixes the following crash: FATAL EXCEPTION: AsyncTask LineageOS#2 Process: system:ui, PID: 8982 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: java.lang.RuntimeException: No data directory found for package android at android.app.ContextImpl.getDataDir(ContextImpl.java:2560) at com.android.internal.gmscompat.dynamite.client.DynamiteContext.<init>(DynamiteContext.java:58) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.getClientContext(GmsDynamiteHooks.java:64) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.loadAssetsFromPath(GmsDynamiteHooks.java:93) at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:143) at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:374) at android.app.ResourcesManager.access$000(ResourcesManager.java:67) at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:146) at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:833) at android.app.ResourcesManager.getResources(ResourcesManager.java:937) at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:2226) at android.app.ApplicationPackageManager.getResourcesForApplication(ApplicationPackageManager.java:1682) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIconBitmap(ResolverListAdapter.java:920) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIconBitmap(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIcon(ResolverListAdapter.java:908) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIcon(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter.loadIconForResolveInfo(ResolverListAdapter.java:599) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:782) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:769) at android.os.AsyncTask$3.call(AsyncTask.java:394) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 4 more Change-Id: I928db502d2cc24e50ed2798575e0e8a37475cd97
sn-00-x
pushed a commit
to sn-00-x/android_frameworks_base
that referenced
this pull request
Sep 22, 2021
Not all packages have data directories: FATAL EXCEPTION: AsyncTask LineageOS#2 Process: system:ui, PID: 8982 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: java.lang.RuntimeException: No data directory found for package android at android.app.ContextImpl.getDataDir(ContextImpl.java:2560) at com.android.internal.gmscompat.dynamite.client.DynamiteContext.<init>(DynamiteContext.java:58) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.getClientContext(GmsDynamiteHooks.java:64) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.loadAssetsFromPath(GmsDynamiteHooks.java:93) at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:143) at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:374) at android.app.ResourcesManager.access$000(ResourcesManager.java:67) at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:146) at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:833) at android.app.ResourcesManager.getResources(ResourcesManager.java:937) at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:2226) at android.app.ApplicationPackageManager.getResourcesForApplication(ApplicationPackageManager.java:1682) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIconBitmap(ResolverListAdapter.java:920) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIconBitmap(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIcon(ResolverListAdapter.java:908) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIcon(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter.loadIconForResolveInfo(ResolverListAdapter.java:599) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:782) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:769) at android.os.AsyncTask$3.call(AsyncTask.java:394) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 4 more Use the underlying Environment methods instead to construct a device-protected data path for GMs without relying on error-prone Context methods. Change-Id: I180cfe464f80a55ac534e150199ba1708841d13d
sn-00-x
pushed a commit
to sn-00-x/android_frameworks_base
that referenced
this pull request
Sep 22, 2021
The chooser and resolver activities run as a special system UI process belonging to the core "android" package, separate from both system_server and com.android.systemui. This process, named "android:ui", runs separately under each user with the special app ID 1000 (SYSTEM_UID). Check the app ID instead of the UID to fix detection of SYSTEM_UID processes in secondary users. This fixes the following crash: FATAL EXCEPTION: AsyncTask LineageOS#2 Process: system:ui, PID: 8982 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: java.lang.RuntimeException: No data directory found for package android at android.app.ContextImpl.getDataDir(ContextImpl.java:2560) at com.android.internal.gmscompat.dynamite.client.DynamiteContext.<init>(DynamiteContext.java:58) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.getClientContext(GmsDynamiteHooks.java:64) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.loadAssetsFromPath(GmsDynamiteHooks.java:93) at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:143) at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:374) at android.app.ResourcesManager.access$000(ResourcesManager.java:67) at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:146) at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:833) at android.app.ResourcesManager.getResources(ResourcesManager.java:937) at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:2226) at android.app.ApplicationPackageManager.getResourcesForApplication(ApplicationPackageManager.java:1682) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIconBitmap(ResolverListAdapter.java:920) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIconBitmap(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIcon(ResolverListAdapter.java:908) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIcon(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter.loadIconForResolveInfo(ResolverListAdapter.java:599) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:782) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:769) at android.os.AsyncTask$3.call(AsyncTask.java:394) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 4 more Change-Id: I928db502d2cc24e50ed2798575e0e8a37475cd97
sn-00-x
pushed a commit
to sn-00-x/android_frameworks_base
that referenced
this pull request
Sep 22, 2021
Not all packages have data directories: FATAL EXCEPTION: AsyncTask LineageOS#2 Process: system:ui, PID: 8982 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: java.lang.RuntimeException: No data directory found for package android at android.app.ContextImpl.getDataDir(ContextImpl.java:2560) at com.android.internal.gmscompat.dynamite.client.DynamiteContext.<init>(DynamiteContext.java:58) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.getClientContext(GmsDynamiteHooks.java:64) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.loadAssetsFromPath(GmsDynamiteHooks.java:93) at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:143) at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:374) at android.app.ResourcesManager.access$000(ResourcesManager.java:67) at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:146) at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:833) at android.app.ResourcesManager.getResources(ResourcesManager.java:937) at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:2226) at android.app.ApplicationPackageManager.getResourcesForApplication(ApplicationPackageManager.java:1682) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIconBitmap(ResolverListAdapter.java:920) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIconBitmap(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIcon(ResolverListAdapter.java:908) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIcon(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter.loadIconForResolveInfo(ResolverListAdapter.java:599) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:782) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:769) at android.os.AsyncTask$3.call(AsyncTask.java:394) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 4 more Use the underlying Environment methods instead to construct a device-protected data path for GMs without relying on error-prone Context methods. Change-Id: I180cfe464f80a55ac534e150199ba1708841d13d
krasCGQ
pushed a commit
to kud-workspace/android_frameworks_base
that referenced
this pull request
Oct 6, 2021
The chooser and resolver activities run as a special system UI process belonging to the core "android" package, separate from both system_server and com.android.systemui. This process, named "android:ui", runs separately under each user with the special app ID 1000 (SYSTEM_UID). Check the app ID instead of the UID to fix detection of SYSTEM_UID processes in secondary users. This fixes the following crash: FATAL EXCEPTION: AsyncTask LineageOS#2 Process: system:ui, PID: 8982 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: java.lang.RuntimeException: No data directory found for package android at android.app.ContextImpl.getDataDir(ContextImpl.java:2560) at com.android.internal.gmscompat.dynamite.client.DynamiteContext.<init>(DynamiteContext.java:58) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.getClientContext(GmsDynamiteHooks.java:64) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.loadAssetsFromPath(GmsDynamiteHooks.java:93) at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:143) at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:374) at android.app.ResourcesManager.access$000(ResourcesManager.java:67) at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:146) at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:833) at android.app.ResourcesManager.getResources(ResourcesManager.java:937) at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:2226) at android.app.ApplicationPackageManager.getResourcesForApplication(ApplicationPackageManager.java:1682) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIconBitmap(ResolverListAdapter.java:920) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIconBitmap(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIcon(ResolverListAdapter.java:908) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIcon(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter.loadIconForResolveInfo(ResolverListAdapter.java:599) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:782) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:769) at android.os.AsyncTask$3.call(AsyncTask.java:394) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 4 more Change-Id: I928db502d2cc24e50ed2798575e0e8a37475cd97 Signed-off-by: Albert I <[email protected]>
krasCGQ
pushed a commit
to kud-workspace/android_frameworks_base
that referenced
this pull request
Oct 6, 2021
Not all packages have data directories: FATAL EXCEPTION: AsyncTask LineageOS#2 Process: system:ui, PID: 8982 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$4.done(AsyncTask.java:415) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383) at java.util.concurrent.FutureTask.setException(FutureTask.java:252) at java.util.concurrent.FutureTask.run(FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: java.lang.RuntimeException: No data directory found for package android at android.app.ContextImpl.getDataDir(ContextImpl.java:2560) at com.android.internal.gmscompat.dynamite.client.DynamiteContext.<init>(DynamiteContext.java:58) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.getClientContext(GmsDynamiteHooks.java:64) at com.android.internal.gmscompat.dynamite.GmsDynamiteHooks.loadAssetsFromPath(GmsDynamiteHooks.java:93) at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:143) at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:374) at android.app.ResourcesManager.access$000(ResourcesManager.java:67) at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:146) at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:833) at android.app.ResourcesManager.getResources(ResourcesManager.java:937) at android.app.ActivityThread.getTopLevelResources(ActivityThread.java:2226) at android.app.ApplicationPackageManager.getResourcesForApplication(ApplicationPackageManager.java:1682) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIconBitmap(ResolverListAdapter.java:920) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIconBitmap(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter$TargetPresentationGetter.getIcon(ResolverListAdapter.java:908) at com.android.internal.app.ResolverListAdapter$ActivityInfoPresentationGetter.getIcon(ResolverListAdapter.java:843) at com.android.internal.app.ResolverListAdapter.loadIconForResolveInfo(ResolverListAdapter.java:599) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:782) at com.android.internal.app.ResolverListAdapter$LoadIconTask.doInBackground(ResolverListAdapter.java:769) at android.os.AsyncTask$3.call(AsyncTask.java:394) at java.util.concurrent.FutureTask.run(FutureTask.java:266) ... 4 more Use the underlying Environment methods instead to construct a device-protected data path for GMs without relying on error-prone Context methods. Change-Id: I180cfe464f80a55ac534e150199ba1708841d13d Signed-off-by: Albert I <[email protected]>
SuperAviation001
pushed a commit
to ExtinctOS/android_frameworks_base
that referenced
this pull request
Aug 10, 2025
@ idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 [ghostrider-reborn]: keep default behaviour in power manager Change-Id: Idebd1f0922b0db5a5349f551ca0ba9e0afc15678 Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Adithya R <[email protected]> Co-Authored-By: jhonboy121 <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Aug 11, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_los
that referenced
this pull request
Aug 12, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Aug 15, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Aug 15, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_los
that referenced
this pull request
Aug 16, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Aug 16, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Aug 24, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 1, 2025
Currently the full user (e.g. userId 0) is required to enter device credential (e.g. device PIN/pattern/password) to unlock the device in certain cases as specified by StrongAuthFlags (e.g. the user has triggered lockdown). After successfully verify the device credential, StrongAuthFlags for the full user will be set back to STRONG_AUTH_NOT_REQUIRED. This may or may not clear StrongAuthFlags for a profile of the user, depending on whether the profile has a separate or unified lock. Case LineageOS#1: the profile has a seprate lock. In this case, the user will need to enter the device credential on lockscreen to unlock the device, and then enter the different profile lock to unlock the profile. StrongAuthFlags for the profile will only be cleared after successfully verifying the profile lock. Case LineageOS#2: the profile has a unified lock. Currently in this case, StrongAuthFlags for the profile doesn't get cleared properly after the user verifies the device credential on lockscreen and unpauses the profile. For example, if the user triggers lockdown and later enters the device credential to unlock the device, StrongAuthFlags for the full user gets cleared (so the full user exits lockdown) while StrongAuthFlags for the profile doesn't get cleared (so the profile remains in lockdown), and thus notifications for the profile won't be shown properly. This CL fixes the issue above for the case LineageOS#2. The user will only need to enter the device credential on lockscreen once to unlock the device. If the profile is already unpaused, at this point StrongAuthFlags should already be cleared; otherwise, StrongAuthFlags will be cleared after the user unpauses the profile (but without having to enter any lock again since the profile uses a unified lock). Test: (1) Set up a profile (e.g. a managed profile) with a unified lock. (2) Trigger the lockdown mode on lockscreen, and verify that StrongAuthFlags for the full user and the profile are both set properly, via "adb shell dumpsys lock_settings". (3) Enter the device credential on lockscreen for the full user, and verify that StrongAuthFlags for the full user is unset. StrongAuthFlags for the profile should also be cleared at this point if the profile was unpaused already before lockdown; otherwise (4) Unpause the profile and verify that StrongAuthFlags for the profile is cleared. Fix: 176924824 Bug: 173721373 (cherry picked from commit ea925cf) (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a3e155e8060b3652baac209e4e48fa988e255206) Merged-In: Ic466fc22a5be9047d39194ad42c56dc4a2acb4dc Change-Id: Ic466fc22a5be9047d39194ad42c56dc4a2acb4dc
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 1, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 1, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
ralf979
pushed a commit
to Black-Iron-Project/frameworks_base
that referenced
this pull request
Sep 2, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Sep 3, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 4, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 4, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 5, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 5, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
toukashishigaya
pushed a commit
to youkai-b/los_fwb
that referenced
this pull request
Sep 7, 2025
Fix NULL deref
```
Cmdline: com.android.systemui
pid: 2530, tid: 2589, name: RenderThread >>> com.android.systemui <<<
uid: 10293
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000010
Cause: null pointer dereference
x0 b400007cbe7b8ff0 x1 0000007bf78fb9f0 x2 b400007c8c184898 x3 0000000000000001
x4 0000007bf78faf80 x5 00000000007f5687 x6 000000001991ade0 x7 0000000000000010
x8 0000000000000000 x9 43490de4ff9b0700 x10 b400007cbe7b8c00 x11 0000000000000002
x12 0000000000000000 x13 000000003f800000 x14 000000003f800000 x15 0000000000000000
x16 0000007d71724720 x17 0000007d57ccdb00 x18 0000007bf7568000 x19 b400007cbe7b8ff0
x20 b400007cbe7b9018 x21 b400007cbe7b8ff0 x22 b400007cbe280010 x23 b400007cbe280000
x24 7ffffffffffffff8 x25 1fffffffffffffff x26 00000000ffffffff x27 b400007c7e1b0da8
x28 0000007bf78fc000 x29 0000007bf78fb7a0
lr 0000007d67aaf330 sp 0000007bf78fb7a0 pc 0000007d67ab1590 pst 0000000020001000
backtrace:
#00 pc 0000000000253590 /system/lib64/libhwui.so (android::uirenderer::AnimatorManager::pushStaging()+112)
LineageOS#1 pc 000000000025132c /system/lib64/libhwui.so (android::uirenderer::AnimationContext::runRemainingAnimations(android::uirenderer::TreeInfo&)+44)
LineageOS#2 pc 0000000000267664 /system/lib64/libhwui.so (android::uirenderer::AnimationContextBridge::runRemainingAnimations(android::uirenderer::TreeInfo&)+36)
LineageOS#3 pc 0000000000292720 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::prepareTree(android::uirenderer::TreeInfo&, long*, long, android::uirenderer::RenderNode*)+352)
LineageOS#4 pc 00000000002959c8 /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.c1671e787f244890c877724752face20)+360)
LineageOS#5 pc 0000000000282ce4 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+1108)
LineageOS#6 pc 00000000002a808c /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+556)
LineageOS#7 pc 0000000000013a14 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+436)
LineageOS#8 pc 00000000000d07ac /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204)
LineageOS#9 pc 00000000000567f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
```
Signed-off-by: Pranav Vashi <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Sep 8, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
AndyCGYan
pushed a commit
to LOS21-pre-QPR2/android_frameworks_base
that referenced
this pull request
Sep 11, 2025
This is a combination of 2 commits. This is the 1st commit message: Revert "Check sound Uri permission when creating a notification channel" This reverts commit 4a5ab5249a74a49ef6e76c3c88e9766ccec01713. Reason for revert: b/337775777 (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:55273fb3059a1e92f933306ece8d8647b0593568) Merged-In: I4b1035742846dc3a39a8b1bb23be18fe9c54f4fa Change-Id: I4b1035742846dc3a39a8b1bb23be18fe9c54f4fa This is the commit message LineageOS#2: Check sound Uri permission when creating a notification channel Verify that the calling app has the right permissions to read/grant the sound Uri for a channel it creates. Fallback to default notification sound if permission check fails. Previously, Uri permissions would only be checked by NotificationRecord when a notification was posted. Flag: EXEMPT security fix Test: atest PreferencesHelperTest Test: atest NotificationManagerServiceTest Bug: 337775777 (cherry picked from commit f9cbae0) (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:ad8b9ff6cce542f1aed21442fa5b1a1de98aeba8) Merged-In: I7977a8b6eea4b75873787e0ab75de7b4e788f2df Change-Id: I7977a8b6eea4b75873787e0ab75de7b4e788f2df
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_los
that referenced
this pull request
Sep 16, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
ralf979
pushed a commit
to Black-Iron-Project/frameworks_base
that referenced
this pull request
Sep 22, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_los
that referenced
this pull request
Oct 1, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
keosh1
pushed a commit
to Project-NovaLine/android_frameworks_base
that referenced
this pull request
Oct 21, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Project-Mist-OS/frameworks_base_los
that referenced
this pull request
Nov 3, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_new
that referenced
this pull request
Nov 5, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
momenabdulrazek
referenced
this pull request
in ProjectSakura/frameworks_base
Nov 16, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message #2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yehonatan5785
pushed a commit
to Lineage-OS-Special-Project/android_frameworks_base
that referenced
this pull request
Dec 8, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_new
that referenced
this pull request
Dec 20, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
yusufnoor786
pushed a commit
to Mist-OS-Staging/frameworks_base_new
that referenced
this pull request
Dec 24, 2025
@idoybh edits: Adapted to A11's settings backup [jhonboy121]: adapt to A12 changes in DozeParameters. Also in the og commit DOZE_ALWAYS_ON was being read from System namespace instead of Secure, fixed it here. Make use of SettingsProxy utlity classes for settings / getting values Change-Id: I831583fde68de15788e3d7ecab55d864726d140f Commit message LineageOS#2: base: check whether device is charging when alwaysOnChargingEnabled is called * Using settings for this is quite redundant. And if you toggle aod on charge after plugging in then aod won't turn on unless you unplug and plug again (since DOZE_ON_CHARGE_NOW is set only if aod on charge is enabled and device is plugged in" Signed-off-by: jhonboy121 <[email protected]> Commit message LineageOS#3: base: fix deadlock between activity manager and power manager * Using the battery manager intent to query plugged in status was the root cause of deadlock, so inside power manager, user mIsPowered and setting value instead of using the intent based power status Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: adapted to A13 Co-authored-by: jhonboy121 <[email protected]> Signed-off-by: jhonboy121 <[email protected]> Signed-off-by: Pranav Vashi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changing Colors in Framework to match the AOSP Colors