[ROM][UNOFFICIAL][SUNFISH][A11] LineageOS 18.1

Search This thread

icantlogin

Senior Member
Aug 23, 2017
73
55
@andrepd So I understand there are various options for enabling signature spoofing on any ROM. There's NanoDroid patcher, there's an option with Xposed or whatever its current reincarnation is, and there are the Needle/Tingle/Haystack scripts. Five years ago I ran microG and used Tingle to patch my ROM, which worked fine for me. Can you explain to me the advantage of having signature spoofing pre-enabled in the ROM?

@BWRainbow I have no experience with custom kernels. I've looked at some custom kernel threads in the past but it has always remained vague to me what the advantage of them would be. I would be interested in reducing power usage during standby, is that something a custom kernel could do? My current battery life is 2-3 days on average, with most of the time spent in standby.
 
  • Like
Reactions: BWRainbow

icantlogin

Senior Member
Aug 23, 2017
73
55
This month's build includes a patch for a vulnerability where anyone with physical access to your phone can bypass the lock screen within 1 minute by plugging in a SIM-card, entering the wrong PIN for that SIM three times and then entering the PUK-code for that SIM and setting a new PIN. Try it before updating if you like...

Yesterday I happened to stumble upon this article by one of the people who reported this bug to Google earlier this year. Seeing him easily bypass the lock screen in the included video was kind of terrifying. It really drove home to me why we update. Imagine how long this has been possible... at least since Android 10 (older versions aren't supported by Google), which also received the patch.

Makes you wonder what kind of vendor patches we are missing out on by not upgrading to Android 12/13 and now being more than a year behind 😭
 

BWRainbow

Member
Jun 8, 2021
32
4
I was going to talk about that vulnerability some days ago but didn't want to pressure you (as, in my case also, it's very hard for that to happen to me).
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Thanks for making this! I'm trying to follow this step:

  • Optionally flash Gapps or anything else:
    • Advanced > Reboot to recovery
    • Run adb sideload with your zip
  • Reboot system now

However, when I try to do this from the Apply from ADB menu, or alternatively flashing in fastboot, I get failures. For the ADB approach, it seems to start, but ends up at E:Error in /sideload package.zip (status 255). For the fastboot approach,

unknown partition '.\open_gapps-arm64-11.0-aroma-20220215.zip'
fastboot: error: cannot determine image filename for '.\open_gapps-arm64-11.0-aroma-20220215.zip'

Is there some other way I can flash GAPPS?

Thanks again.
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Update: Aroma gave me those errors, Stock gave me space errors, but Pico worked fine. Seems like a LineageOS recovery issue (TWRP has always worked fine before with the others, albeit on my old XZ1 Compact).
 

mxbndr

Senior Member
Sep 29, 2010
52
5
I have a new issue where I can't sign into any Samsung apps. My other Pixel 4a running Stock 13 has no issue. 3 apps display the issue differently: Galaxy Wearable goes to a white screen, Samsung Health gets a permanent spinning wheel, and Smartthings freezes. I am able to sign in via browsers, and Samsung Internet comes with Android Account integration, and that works. The other 3 have to go via a browser, but the apps fail to redirect. I have tried with Chrome, Samsung Internet, and Lynket.

I'm assuming something is trying to connect to Samsung and can't and so it doesn't proceed. I tried uninstalling Adaway and that didn't help. I also hid the Magisk app and that changed nothing.

Is there a log I can access somewhere to see what might be hanging/blocking?

My XZ1 Compact had the same set up (18.1, Magisk, etc) and I could sign in.
 

icantlogin

Senior Member
Aug 23, 2017
73
55
You can run logcat in an adb shell to see informational, warning and error messages i.e. see what's going on behind the scenes. There are arguments you can use to filter the output.
I'm assuming something is trying to connect to Samsung and can't and so it doesn't proceed.
Are you using a VPN provider by any chance? If so, have you tried turning it off before signing in?
 
  • Like
Reactions: mxbndr

mxbndr

Senior Member
Sep 29, 2010
52
5
You can run logcat in an adb shell to see informational, warning and error messages i.e. see what's going on behind the scenes. There are arguments you can use to filter the output.

Are you using a VPN provider by any chance? If so, have you tried turning it off before signing in?

Sorry for the long delay, didn't realize I didn't have email notifications on for forums.

I am not using a VPN, just Adaway updating host files. I've tried uninstalling Adaway, as well as allowing any DNS requests logged by Adaway when trying to sign into these apps. Sadly, that did not change anything.

Here is the log output (there's a lot more than this, but I think this is the start and end of the attempt to sign in). This is with the Galaxy Wear app:

Code:
12-03 10:25:57.461 21933 21933 I SamsungAccount(W): [SamsungAccountUiUtils] performClickActionForNonSamsungDevices: for GW sign in
12-03 10:25:57.462  1481  4924 I ActivityTaskManager: START u0 {cmp=com.samsung.android.waterplugin/com.samsung.android.companionapps.samsungaccount.view.webview.SaWebViewRelayActivity} from uid 10076
12-03 10:25:57.469 21933 21933 D  [BackupRestore] [BackupRestoreMainFragment]: <<--onPause-->>
12-03 10:25:57.470  1481  4921 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (58368807)
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [SaWebViewRelayActivity] onCreate()
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [SaWebViewRelayActivity] init()
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [SaWebViewRelayActivity] handleRequestMode()
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [AuthInfo] isAccessTokenValid(): false, Empty
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [AuthInfo] isRefreshTokenValid(): false, Empty
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [SaWebViewRelayActivity] startSignIn()
12-03 10:25:57.482 10818 10818 I SamsungAccount(W): [DeviceSecurityCodeUtil] getDeviceSecurityCode
12-03 10:25:57.482 10818 10818 I SA_SDK-1.5.21: [Util] == isNetworkConnected == true
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [BrowserUtil] resolveInfoList has com.android.chrome
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [BrowserUtil] isPackageDisabled ? false
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [BrowserUtil] Usable Browsers(Size) : 1
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [Util] SA doesn't exist
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [Util] isIotSaAppInstalled ? false
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [Util] canUseIotSaApp ? false
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [Util] Stand alone client package is not installed
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [Util] getSupportStandAloneFromMetaData : false
12-03 10:25:57.484 10818 10818 I SA_SDK-1.5.21: [Util] isStandAloneSaAppInstalled ? false
12-03 10:25:57.485 10818 10818 I SA_SDK-1.5.21: [Util] Stand alone client package is not installed
12-03 10:25:57.485 10818 10818 I SA_SDK-1.5.21: [Util] getSupportStandAloneFromMetaData : false
12-03 10:25:57.485 10818 10818 I SA_SDK-1.5.21: [Util] isStandAloneSaAppInstalled ? false
12-03 10:25:57.490 10818 22561 I SA_SDK-1.5.21: [BrowserUtil] com.sec.android.app.sbrowser exist.
12-03 10:25:57.492 10818 10818 I SamsungAccount(W): [SaWebViewRelayActivity] onResume
12-03 10:25:57.492 10818 22561 I SA_SDK-1.5.21: [BrowserUtil] isAvailableBrowserInstalledAndEnabled ? true
12-03 10:25:57.493 10818 22561 I SA_SDK-1.5.21: [BrowserUtil] com.android.chrome exist.
12-03 10:25:57.493 10818 22561 I SA_SDK-1.5.21: [BrowserUtil] isAvailableBrowserInstalledAndEnabled ? true
12-03 10:25:57.495 10818 22561 I SA_SDK-1.5.21: [BrowserUtil] createBrowser - isCustomTabNotAvailable ? false, isChinaManufacturer ? false
12-03 10:25:57.499 10818 22561 I SA_SDK-1.5.21: [CustomTabBrowser] findPriorityCustomTabBrowser resolveInfo : arun.com.chromer
12-03 10:25:57.499 10818 22561 I SA_SDK-1.5.21: [CustomTabBrowser] targetPackageName : arun.com.chromer
12-03 10:25:57.500 10818 22561 I SA_SDK-1.5.21: [Util] getUiModeForWebView ? N
12-03 10:25:57.513  1481  4924 W ActivityManager: Unable to start service Intent { act=android.support.customtabs.action.CustomTabsService pkg=arun.com.chromer } U=0: not found
12-03 10:25:57.538  1481  1567 I ActivityTaskManager: Displayed com.samsung.android.waterplugin/com.samsung.android.companionapps.samsungaccount.view.webview.SaWebViewRelayActivity: +69ms
12-03 10:25:57.549  3636  3636 E FullInputEventModel: onStartInput event aborted: vf.z: could not obtain extracted text (class vf.z)
12-03 10:25:57.959 21933 21933 I Water:MainInfoActivity: onTrimMemory() - level : 20
12-03 10:25:57.962 10818 11349 I Water:CompanionService4Water: GA:GoogleAccountSyncManager.unregisterWatchSettingsContentObserver() starts..
12-03 10:25:57.963 21933 21933 D  [BackupRestore] [BackupRestoreMainFragment]: <<--onStop-->>
12-03 10:25:58.675  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:25:58.766  1481  2151 D ConnectivityService: NetReassign [no changes]
12-03 10:25:58.139 21607 21607 I         : [K][PM] power PM Statistic start (12-03 10:25:58)
12-03 10:25:58.139 21607 21607 I [K] wakeup_source: 'a600000.ssusb'
12-03 10:25:58.139 21607 21607 I rpmh_master_stat: APSS(1151807,sleep:81000s) MPSS(207130,sleep:115858s) ADSP(6781631,sleep:116557s) ADSP_ISLAND(122563,sleep:110793s) CDSP(255,sleep:124842s)
12-03 10:25:58.139 21607 21607 I msm_rpmstats_stats_dump: (aosd,2549051,sleep:67237s) (cxsd,1209344,sleep:71741s) (ddr ,1266954,sleep:73506s)
12-03 10:25:58.139 21607 21607 I         : [K][PM] power PM Statistic done
12-03 10:25:58.447  2216  2216 I [cds_ol][2397551258190][10:25:59.119985] wlan: [2216:I:QDF] qdf_dp_display_proto_pkt_always: 1890:  DPT: 1437:255 DHCP: [0] [REQ] SA: 3c:5c:f1:22:15:ed  <--  DA: ff:ff:ff:ff:ff:ff
12-03 10:25:58.656 21607 21607 I google_charger: usbchg=USB typec=C usbv=4953 usbc=143 usbMv=5000 usbMc=3000
12-03 10:25:58.656 21607 21607 I sm7150_bms: MSC_PCS chg_state=fa601030001 [0x1:1:3:4006:0] chg=
12-03 10:25:58.656 21607 21607 I google_battery: MSC_DIN chg_state=fa601030001 f=0x1 chg_s=Not Charging chg_t=None vchg=4006 icl=0
12-03 10:25:58.657 21607 21607 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=4006602 ibatt=189819 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:25:58.657 21607 21607 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:25:58.657 21607 21607 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:25:58.657 21607 21607 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)
12-03 10:26:00.660 21607 21607 I google_charger: usbchg=USB typec=C usbv=4951 usbc=134 usbMv=5000 usbMc=3000
12-03 10:26:00.660 21607 21607 I sm7150_bms: MSC_PCS chg_state=fb501030001 [0x1:1:3:4021:0] chg=
12-03 10:26:00.660 21607 21607 I google_battery: MSC_DIN chg_state=fb501030001 f=0x1 chg_s=Not Charging chg_t=None vchg=4021 icl=0
12-03 10:26:00.661 21607 21607 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=4021589 ibatt=144958 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:26:00.662 21607 21607 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:26:00.662 21607 21607 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:26:00.662 21607 21607 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)

This is with the Samsung Health app:


Code:
12-03 10:33:40.295 20927 20927 E SHEALTH#AppStateManager: Current stateManager: [email protected], state: NEEDED
12-03 10:33:40.299 20927 20927 D SHEALTH#AppStateManager: doAction(), Current stateManager: [email protected]
12-03 10:33:40.305 20927 20927 I SHEALTH#OOBEManager: doAction: cc: US, lc id:en_US
12-03 10:33:40.310  1481  2709 I ActivityTaskManager: START u0 {act=com.samsung.android.app.shealth.intent.action.START_OOBE flg=0x10010000 cmp=com.sec.android.app.shealth/com.samsung.android.app.shealth.home.oobe2.view.HomeOobeActivity} from uid 10321
12-03 10:33:40.315 20927 20927 D SHEALTH#HomeMainActivity: [PERF] onCreate - end
12-03 10:33:40.326  1481  4922 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (58963438)
12-03 10:33:40.383 20927 20927 W SeslBaseReflector: Fail to get class = com.samsung.android.widget.SemHoverPopupWindow
12-03 10:33:40.384 20927 20927 W SeslBaseReflector: Reflector did not find method = hidden_semSetHoverPopupType
12-03 10:33:40.386 20927 20927 D FragmentManager: [email protected] put NavHostFragment{755cf25} (ada408ed-814d-4685-ab21-e3c3c5d635cf id=0x7f0a0eeb) to Active Fragments, mActive size: 1
12-03 10:33:40.401 20927 20927 D SamsungAnalytics605030: user do not agree
12-03 10:33:40.401 20927 20927 D FragmentManager: [email protected] put HomeIntroFragment{aafac49} (51bf6a28-abc5-4240-8fa0-0cb2479a5699 id=0x7f0a0eeb) to Active Fragments, mActive size: 1
12-03 10:33:40.531 20927 20927 I SHEALTH#HomeConsentBaseFragment: initViewDependencies : initDPModules called
12-03 10:33:40.532 20927 20927 I SHEALTH#HealthDataStoreManager: Activate health data framework
12-03 10:33:40.537 20959 23078 I Health.data.TncComplete: Now, health data framework is activated
12-03 10:33:40.539 20927 20927 I SHEALTH#VerifyPhoneViewModel: PhoneNumber null
12-03 10:33:40.539 20927 20927 I SHEALTH#HomeConsentBaseFragment: initViewDependencies : PhoneNumber not set
12-03 10:33:40.541 20927 20927 I SHEALTH#HomeConsentBaseFragment: onConnected :: mIsKnoxAvailable false true false
12-03 10:33:39.867 15864 15864 I google_charger: usbchg=USB typec=C usbv=4950 usbc=120 usbMv=5000 usbMc=3000
12-03 10:33:39.867 15864 15864 I sm7150_bms: MSC_PCS chg_state=f3a01030001 [0x1:1:3:3898:0] chg=
12-03 10:33:39.867 15864 15864 I google_battery: MSC_DIN chg_state=f3a01030001 f=0x1 chg_s=Not Charging chg_t=None vchg=3898 icl=0
12-03 10:33:39.868 15864 15864 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=3898189 ibatt=744934 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:33:39.868 15864 15864 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:33:39.868 15864 15864 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:33:39.868 15864 15864 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)
12-03 10:33:40.563 20927 20927 D SHEALTH#SocialAppLifecycleChecker: onActivityResumed() 0
12-03 10:33:40.571  1481  4896 I ActivityTaskManager: START u0 {act=com.samsung.android.app.shealth.intent.action.SA_MANDATORY_GUIDE flg=0x4010000 cmp=com.sec.android.app.shealth/com.samsung.android.app.shealth.home.oobe2.view.HomeSaSignInActivity} from uid 10321
12-03 10:33:40.576 20927 20927 D HealthConsole: Service for HealthDataConsole is connected
12-03 10:33:40.579 20927 20927 D HealthConsole: Service for HealthDataConsole is connected
12-03 10:33:40.580 20927 20927 D SHEALTH#SocialAppLifecycleChecker: onActivityPaused() 0
12-03 10:33:40.581  1481  2709 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (58963536)
12-03 10:33:40.628 20927 20927 D SamsungAnalytics605030: user do not agree
12-03 10:33:40.629 20927 20927 D SHEALTH#SocialAppLifecycleChecker: onActivityResumed() 0
12-03 10:33:40.675 20927 20927 I NestedScrollView: GTT HSC not support : under Platform Version : 30
12-03 10:33:40.682 20927 20927 I NestedScrollView: GTT HSC not support : under Platform Version : 30
12-03 10:33:40.693  1481  1567 I ActivityTaskManager: Displayed com.sec.android.app.shealth/com.samsung.android.app.shealth.home.oobe2.view.HomeSaSignInActivity: +488ms
12-03 10:33:40.693 20927 20927 D SHEALTH#HomeMainActivity: onDestroy()
12-03 10:33:40.693 20927 20927 D SHEALTH#SocialAppLifecycleChecker: onActivityDestroyed() 0
12-03 10:33:40.701  3636  3636 E FullInputEventModel: onStartInput event aborted: vf.z: could not obtain extracted text (class vf.z)
12-03 10:33:40.706  3726  5568 I AssistantForeground: (REDACTED) Get launcher package: %s
12-03 10:33:40.796  1481  2151 D ConnectivityService: NetReassign [no changes]
12-03 10:33:41.870 15864 15864 I google_charger: usbchg=USB typec=C usbv=4946 usbc=134 usbMv=5000 usbMc=3000
12-03 10:33:41.870 15864 15864 I sm7150_bms: MSC_PCS chg_state=fac01030001 [0x1:1:3:4012:0] chg=
12-03 10:33:41.870 15864 15864 I google_battery: MSC_DIN chg_state=fac01030001 f=0x1 chg_s=Not Charging chg_t=None vchg=4012 icl=0
12-03 10:33:41.871 15864 15864 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=4012831 ibatt=185547 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:33:41.871 15864 15864 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:33:41.871 15864 15864 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:33:41.871 15864 15864 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)
12-03 10:33:42.669  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:33:42.671  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:33:42.739 26790 26790 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.cast.firstparty.START dat=chimera-action: cmp=com.google.android.gms/.chimera.CastPersistentBoundBrokerService }
12-03 10:33:42.754 26827 23088 I Authzen : [DeviceStateSyncManager] The server is in sync with current state. Nothing to do
12-03 10:33:42.785 26827 26827 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.auth.cryptauth.cryptauthservice.START dat=chimera-action: cmp=com.google.android.gms/.chimera.GmsBoundBrokerService }
12-03 10:33:43.170   890   974 D CHRE    : @ 125336.510: [ActivityPlatform] type 4, confidence 95
12-03 10:33:43.161   573   573 D logd    : logdr: UID=2000 GID=2000 PID=23090 b tail=0 logMask=99 pid=0 start=0ns timeout=0ns
12-03 10:33:43.878 15864 15864 I google_charger: usbchg=USB typec=C usbv=4951 usbc=147 usbMv=5000 usbMc=3000
12-03 10:33:43.878 15864 15864 I sm7150_bms: MSC_PCS chg_state=fb601030001 [0x1:1:3:4022:0] chg=
12-03 10:33:43.878 15864 15864 I google_battery: MSC_DIN chg_state=fb601030001 f=0x1 chg_s=Not Charging chg_t=None vchg=4022 icl=0
12-03 10:33:43.879 15864 15864 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=4022173 ibatt=104065 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:33:43.879 15864 15864 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:33:43.879 15864 15864 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:33:43.879 15864 15864 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)
12-03 10:33:44.059 15864 15864 I         : [K][PM] power PM Statistic start (12-03 10:33:44)
12-03 10:33:44.059 15864 15864 I [K] wakeup_source: 'a600000.ssusb'
12-03 10:33:44.059 15864 15864 I rpmh_master_stat: APSS(1167548,sleep:81198s) MPSS(208390,sleep:116284s) ADSP(6846375,sleep:116958s) ADSP_ISLAND(124751,sleep:111147s) CDSP(255,sleep:125307s)
12-03 10:33:44.059 15864 15864 I msm_rpmstats_stats_dump: (aosd,2549051,sleep:67237s) (cxsd,1209344,sleep:71741s) (ddr ,1266954,sleep:73506s)
12-03 10:33:44.059 15864 15864 I         : [K][PM] power PM Statistic done
12-03 10:33:46.327   890   974 D CHRE    : @ 125339.668: [ActivityPlatform] type 4, confidence 95
12-03 10:33:45.881 15864 15864 I google_charger: usbchg=USB typec=C usbv=4948 usbc=133 usbMv=5000 usbMc=3000
12-03 10:33:45.881 15864 15864 I sm7150_bms: MSC_PCS chg_state=fb901030001 [0x1:1:3:4025:0] chg=
12-03 10:33:45.881 15864 15864 I google_battery: MSC_DIN chg_state=fb901030001 f=0x1 chg_s=Not Charging chg_t=None vchg=4025 icl=0
12-03 10:33:45.883 15864 15864 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=4025287 ibatt=109558 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:33:45.883 15864 15864 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:33:45.883 15864 15864 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:33:45.883 15864 15864 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)
12-03 10:33:46.703 12825 12849 D BugleConnectivity: onSignalStrengthsChanged: SIGNAL_STRENGTH_GOOD to SIGNAL_STRENGTH_GREAT
12-03 10:33:46.739  5154  5154 I Tycho.VoiceLibrary: ImsRegistrationNetworkSelector.OnCellStateChanged for subId: 1
12-03 10:33:46.741  5154  5154 I Tycho.VoiceLibrary: Unsupported CellInfo type! Returning null CellularNetworkInfo object
12-03 10:33:47.088  2493  2493 D GRIL-S  : [0333]> UPDATE_DEVICE_STATE DeviceState: Usb:1, Wifi: 1, Wifi AP: 0, Earpiece: 0, Bluetooth: 1, Wireless charging: 0, Screen: 1, Camera: 0, 0, -, -, Motion: 0, Bluetooth tethering: 0, Voice: 0, Wifi 2.4G: 0, Radio: 1, Bluetooth connected: 0, Bluetooth media: 0
12-03 10:33:43.831  1481  2151 I chatty  : uid=1000(system) ConnectivitySer identical 1 line
12-03 10:33:46.869  1481  2151 D ConnectivityService: NetReassign [no changes]
12-03 10:33:47.094   910   910 I [email protected]: Wifi: Reseting SAR Scenario to default
12-03 10:33:47.099   875   875 I [email protected]: BluetoothSar:setBluetoothTxPowerCap: 64
12-03 10:33:47.099   875   875 D [email protected]: buildBTSarVSCommand:
12-03 10:33:47.099   875   875 D [email protected]_queue: BT HCI command queue: sendDataToController:
12-03 10:33:47.099   875   875 D [email protected]_queue: BT HCI command queue: sendDataToController: sending VS cmd, starting timer
12-03 10:33:47.099   875   875 D [email protected]_queue: BT HCI command queue: timerStart: is_timer_created=1
12-03 10:33:47.099   875   875 D [email protected]_handler: SendBTDataWithCallback
12-03 10:33:47.099   875   875 D [email protected]_handler: isProtocolInitialized:
12-03 10:33:47.099   875   875 I [email protected]_handler: isProtocolInitialized: status:1
12-03 10:33:47.099  3457  3491 W GooglePlayServicesUtil: com.google.android.apps.scone requires the Google Play Store, but it is missing.
12-03 10:33:47.099  2493  3490 D GRIL-S  : [0333]< UPDATE_DEVICE_STATE
12-03 10:33:47.100  3457  3491 W GoogleApiManager: The service for bie is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
12-03 10:33:47.101  3457  3491 W GooglePlayServicesUtil: com.google.android.apps.scone requires the Google Play Store, but it is missing.
12-03 10:33:47.102  3457  3491 W GoogleApiManager: The service for bie is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
12-03 10:33:47.102   875   875 D [email protected]_queue: BT HCI command queue: sendDataToController: Command is sent
12-03 10:33:47.103   875  2863 D [email protected]_queue: BT HCI command queue: HCI event received
12-03 10:33:47.103   875  2863 D [email protected]_queue: BT HCI command queue: timerStop: is_timer_created= 1
12-03 10:33:47.103   875  2863 D [email protected]_queue: BT HCI command queue: cmd_queue size:1
12-03 10:33:46.436  2215  2215 I [schedu][2406536650827][10:33:47.109230] wlan: [2215:I:WMI] SAR2 result: WMI_SAR2_SUCCESS
12-03 10:33:47.523 12825 12859 D BugleConnectivity: onSignalStrengthsChanged: SIGNAL_STRENGTH_GREAT to SIGNAL_STRENGTH_GOOD
12-03 10:33:47.543  5154  5154 I Tycho.VoiceLibrary: ImsRegistrationNetworkSelector.OnCellStateChanged for subId: 1
12-03 10:33:47.544  5154  5154 I Tycho.VoiceLibrary: Unsupported CellInfo type! Returning null CellularNetworkInfo object
12-03 10:33:47.710  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:33:47.712  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:33:47.746  1481  1752 E LightsService: Light requested not available on this device. 2
12-03 10:33:47.889 15864 15864 I google_charger: usbchg=USB typec=C usbv=4951 usbc=983 usbMv=5000 usbMc=3000
12-03 10:33:47.889 15864 15864 I sm7150_bms: MSC_PCS chg_state=fb901030001 [0x1:1:3:4025:0] chg=
12-03 10:33:47.889 15864 15864 I google_battery: MSC_DIN chg_state=fb901030001 f=0x1 chg_s=Not Charging chg_t=None vchg=4025 icl=0
12-03 10:33:47.890 15864 15864 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=4025482 ibatt=139465 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:33:47.890 15864 15864 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:1->1, vbatt_idx:0->0, fv=4200000->4200000, cc_max=1540000
12-03 10:33:47.890 15864 15864 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=1540000 update_interval=30000
12-03 10:33:47.890 15864 15864 I google_charger: MSC_CHG fv_uv=4200000, cc_max=1540000, rerun in 2000 ms (0)
12-03 10:33:49.029  1481  2107 E LightsService: Light requested not available on this device. 2
12-03 10:33:49.113  1481  4896 I ActivityTaskManager: START u0 {cmp=com.sec.android.app.shealth/com.samsung.android.app.shealth.accounts.AuthenticatorActivity (has extras)} from uid 10321
12-03 10:33:49.123 20927 20927 D SHEALTH#SocialAppLifecycleChecker: onActivityPaused() 0
12-03 10:33:49.124  1481  4896 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (58963792)
12-03 10:33:49.158 20927 20927 I SA_SDK-1.5.22: [Util] == isNetworkConnected == true
12-03 10:33:49.160 20927 20927 I SA_SDK-1.5.22: [BrowserUtil] resolveInfoList has com.android.chrome
12-03 10:33:49.160 20927 20927 I SA_SDK-1.5.22: [BrowserUtil] isPackageDisabled ? false
12-03 10:33:49.160 20927 20927 I SA_SDK-1.5.22: [BrowserUtil] Usable Browsers(Size) : 1
12-03 10:33:49.160 20927 20927 I SA_SDK-1.5.22: [Util] SA doesn't exist
12-03 10:33:49.160 20927 20927 I SA_SDK-1.5.22: [Util] isIotSaAppInstalled ? false
12-03 10:33:49.160 20927 20927 I SA_SDK-1.5.22: [Util] canUseIotSaApp ? false
12-03 10:33:49.161 20927 20927 I SA_SDK-1.5.22: [Util] Stand alone client package is not installed
12-03 10:33:49.161 20927 20927 I SA_SDK-1.5.22: [Util] getSupportStandAloneFromMetaData : false
12-03 10:33:49.161 20927 20927 I SA_SDK-1.5.22: [Util] isStandAloneSaAppInstalled ? false
12-03 10:33:49.161 20927 20927 I SA_SDK-1.5.22: [Util] Stand alone client package is not installed
12-03 10:33:49.161 20927 20927 I SA_SDK-1.5.22: [Util] getSupportStandAloneFromMetaData : false
12-03 10:33:49.161 20927 20927 I SA_SDK-1.5.22: [Util] isStandAloneSaAppInstalled ? false
12-03 10:33:49.162 20927 23096 I SA_SDK-1.5.22: [BrowserUtil] com.sec.android.app.sbrowser exist.
12-03 10:33:49.163 20927 23096 I SA_SDK-1.5.22: [BrowserUtil] isAvailableBrowserInstalledAndEnabled ? true
12-03 10:33:49.165 20927 23096 I SA_SDK-1.5.22: [BrowserUtil] com.android.chrome exist.
12-03 10:33:49.165 20927 20927 D SamsungAnalytics605030: user do not agree
12-03 10:33:49.165 20927 23096 I SA_SDK-1.5.22: [BrowserUtil] isAvailableBrowserInstalledAndEnabled ? true
12-03 10:33:49.165 20927 23096 I SA_SDK-1.5.22: [BrowserUtil] createBrowser - isCustomTabNotAvailable ? false, isChinaManufacturer ? false
12-03 10:33:49.165 20927 20927 D SHEALTH#SocialAppLifecycleChecker: onActivityResumed() 0
12-03 10:33:49.174 20927 23096 I SA_SDK-1.5.22: [CustomTabBrowser] findPriorityCustomTabBrowser resolveInfo : arun.com.chromer
12-03 10:33:49.175 20927 23096 I SA_SDK-1.5.22: [CustomTabBrowser] targetPackageName : arun.com.chromer
12-03 10:33:49.175 20927 23096 I SA_SDK-1.5.22: [Util] getUiModeForWebView ? N
12-03 10:33:49.182  1481  4246 W ActivityManager: Unable to start service Intent { act=android.support.customtabs.action.CustomTabsService pkg=arun.com.chromer } U=0: not found
12-03 10:33:49.184 20927 20927 I NestedScrollView: GTT HSC not support : under Platform Version : 30
12-03 10:33:49.185 20927 20927 I NestedScrollView: GTT HSC not support : under Platform Version : 30
12-03 10:33:49.186  1481  1567 I ActivityTaskManager: Displayed com.sec.android.app.shealth/com.samsung.android.app.shealth.accounts.AuthenticatorActivity: +72ms
12-03 10:33:49.217  3636  3636 E FullInputEventModel: onStartInput event aborted: vf.z: could not obtain extracted text (class vf.z)
12-03 10:33:49.522   890   974 D CHRE    : @ 125342.863: [ActivityPlatform] type 4, confidence 95

This is with Smartthings:

Code:
12-03 10:38:30.824 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][Presenter].doSignIn - Do Sign in
12-03 10:38:30.834 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][Account].launchSignIn - StartAccountActivity. LOGIN
12-03 10:38:30.835 22144 22144 W [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][Account].transitState - SIGN_OUT_DONE -> SIGN_IN_PROGRESS
12-03 10:38:30.835 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][Presenter].subscribeForSignState - onNext. state=SIGN_IN_PROGRESS
12-03 10:38:29.640  1481  2151 D ConnectivityService: NetReassign [no changes]
12-03 10:38:30.837  1481  3757 I ActivityTaskManager: START u0 {flg=0x24800000 cmp=com.samsung.android.oneconnect/.ui.account.SCAccountActivity (has extras)} from uid 10319
12-03 10:38:30.849 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [email protected] -
12-03 10:38:30.849 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][SCMainActivity].onPause - ************** PAUSE **************
12-03 10:38:30.850 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [CardView][ViewModelHelper].stopCards - requestStop. card count=3
12-03 10:38:30.851 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [Favorites][Fragment].onPause - ====== PAUSE(8ef10e9) ======
12-03 10:38:30.851 22144 23582 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [email protected] - true
12-03 10:38:30.851 22144 23644 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [CardView][ViewModelHelper].stopCards - card count=3
12-03 10:38:30.851 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][Model].pause - this=6f0c271
12-03 10:38:30.852  1481  2151 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=1521, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10319 AdministratorUids: [] RequestorUid: 10319 RequestorPackageName: com.samsung.android.oneconnect] ] (release request)
12-03 10:38:30.852 22010 22031 I [-8]oneconnect[1.7.91.24_01][CORE]: DiscoveryPublisherImpl.notifyDiscoveryStop - 83456510 GUIScanTypeMap.size = 0
12-03 10:38:30.853  1481  4902 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (59243550)
12-03 10:38:30.855 22010 22125 I [-8]oneconnect[1.7.91.24_01][CORE]: MdnsHelper.stopDiscovery - mDiscoveryStarted is false. ignore stopDiscovery
12-03 10:38:30.856 22010 22128 D BluetoothAdapter: isLeEnabled(): ON
12-03 10:38:30.868 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][AccountActivity].onCreate - create SCAccountActivity
12-03 10:38:30.884 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][AccountActivity].doLogIn - Log-In. isSignedIn=false
12-03 10:38:30.884  1481  5116 I ActivityTaskManager: START u0 {flg=0x24800000 cmp=com.samsung.android.oneconnect/.auth.ui.account.LoginActivity} from uid 10319
12-03 10:38:30.892 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][AccountActivity].onResume - resume SCAccountActivity
12-03 10:38:30.920 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: [SCMain][AccountActivity].onPause - pause SCAccountActivity
12-03 10:38:30.922  1481  5116 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (59254065)
12-03 10:38:30.934 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: LoginActivity.onCreate -
12-03 10:38:30.939 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: FeatureUtil.isTablet - Config. smallest screen width=392
12-03 10:38:30.941   890   974 I ASH     : @ 125624.282: tcs3701: PROX sample: FAR (0052), POFFSET: 0048, ORE: -1
12-03 10:38:30.942 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: LoginActivity.startSignIn -
12-03 10:38:30.942 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: AccountActivityHelper.startGedSigninActivity - LoginActivity
12-03 10:38:30.942 22144 22144 I [-8]oneconnect[1.7.91.24_01][MAIN_UI]: AccountActivityHelper.startGedSigninActivity - state = upA4zJVg3Zfb3avAUXje
12-03 10:38:30.943 22144 22144 I SA_SDK-1.5.22: [Util] == isNetworkConnected == true
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] resolveInfoList has com.android.chrome
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] isPackageDisabled ? false
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] Usable Browsers(Size) : 1
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [Util] SA doesn't exist
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [Util] isIotSaAppInstalled ? false
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [Util] canUseIotSaApp ? false
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [Util] Stand alone client package is not installed
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [Util] getSupportStandAloneFromMetaData : false
12-03 10:38:30.945 22144 22144 I SA_SDK-1.5.22: [Util] isStandAloneSaAppInstalled ? false
12-03 10:38:30.946 22144 22144 I SA_SDK-1.5.22: [Util] Stand alone client package is not installed
12-03 10:38:30.946 22144 22144 I SA_SDK-1.5.22: [Util] getSupportStandAloneFromMetaData : false
12-03 10:38:30.946 22144 22144 I SA_SDK-1.5.22: [Util] isStandAloneSaAppInstalled ? false
12-03 10:38:30.980  1481  1567 I ActivityTaskManager: Displayed com.samsung.android.oneconnect/.auth.ui.account.LoginActivity: +138ms
12-03 10:38:31.007  3636  3636 E FullInputEventModel: onStartInput event aborted: vf.z: could not obtain extracted text (class vf.z)
12-03 10:38:31.132 22144 23648 I SA_SDK-1.5.22: [HttpRequestClient] Request CheckDomain
12-03 10:38:31.132 22144 23648 I SA_SDK-1.5.22: [HttpRequestClient] Security=[true]
12-03 10:38:31.136 22144 23649 D OkHttp  : --> GET https://auth2.samsungosp.com/v2/license/open/whoareyou
12-03 10:38:30.778 15864 15864 I         : [K][PM] power PM Statistic start (12-03 10:38:31)
12-03 10:38:30.779 15864 15864 I [K] wakeup_source: 'fts_tp''a600000.ssusb''88c000.qcom,qup_uart'
12-03 10:38:30.779 15864 15864 I rpmh_master_stat: APSS(1172632,sleep:81263s) MPSS(209210,sleep:116542s) ADSP(6897527,sleep:117194s) ADSP_ISLAND(128315,sleep:111346s) CDSP(255,sleep:125594s)
12-03 10:38:30.779 15864 15864 I msm_rpmstats_stats_dump: (aosd,2549051,sleep:67237s) (cxsd,1209344,sleep:71741s) (ddr ,1266954,sleep:73506s)
12-03 10:38:30.779 15864 15864 I         : [K][PM] power PM Statistic done
12-03 10:38:31.986 22144 23649 D OkHttp  : <-- 200 https://auth2.samsungosp.com/v2/license/open/whoareyou (849ms, 130-byte body)
12-03 10:38:31.988 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ==================== RESPONSE ====================
12-03 10:38:31.988 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ResponseCode = [200]
12-03 10:38:31.988 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ResponseMessage = []
12-03 10:38:31.988 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ==================================================
12-03 10:38:31.988 22144 22144 I SA_SDK-1.5.22: [MetaManager] setDomainResponseData
12-03 10:38:31.988 22144 22144 I SA_SDK-1.5.22: [DomainResponseData (Full)] setupSpecificDomainUrlIfNeeded
12-03 10:38:31.992 22144 22144 I SA_SDK-1.5.22: [Util] countryCode : us
12-03 10:38:31.993 22144 22144 I SA_SDK-1.5.22: [CommonAPIThread] checkDomain Response - Bundle[{idm_server_url=us.account.samsung.com, api_server_url=us-auth2.samsungosp.com, auth_server_url=us-auth2.samsungosp.com}]
12-03 10:38:31.993 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] Request getEntryPointOfIdm
12-03 10:38:31.996 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] Security=[true]
12-03 10:38:32.010 22144 23655 D OkHttp  : --> GET https://us.account.samsung.com/accounts/ANDROIDSDK/getEntryPoint?countryCode=us
12-03 10:38:31.466 22669 22669 I google_charger: usbchg=USB typec=C usbv=4948 usbc=144 usbMv=5000 usbMc=3000
12-03 10:38:31.466 22669 22669 I sm7150_bms: MSC_PCS chg_state=f9801030001 [0x1:1:3:3992:0] chg=
12-03 10:38:31.466 22669 22669 I google_battery: MSC_DIN chg_state=f9801030001 f=0x1 chg_s=Not Charging chg_t=None vchg=3992 icl=0
12-03 10:38:31.468 22669 22669 I google_battery: MSC_DSG vbatt_idx:0->0 vbatt=3992199 ibatt=235595 fv_uv=4200000 cv_cnt=3 ov_cnt=0
12-03 10:38:31.468 22669 22669 I google_battery: MSC_LOGIC cv_cnt=3 ov_cnt=0 temp_idx:2->2, vbatt_idx:0->0, fv=4200000->4200000, cc_max=3080000
12-03 10:38:31.468 22669 22669 I google_battery: MSC_VOTE fv_uv=4200000 cc_max=3080000 update_interval=30000
12-03 10:38:31.468 22669 22669 I google_charger: MSC_CHG fv_uv=4200000, cc_max=3080000, rerun in 2000 ms (0)
12-03 10:38:32.356 22144 23655 D OkHttp  : <-- 200 OK https://us.account.samsung.com/accounts/ANDROIDSDK/getEntryPoint?countryCode=us (346ms, unknown-length body)
12-03 10:38:32.359 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ==================== RESPONSE ====================
12-03 10:38:32.359 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ResponseCode = [200]
12-03 10:38:32.359 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ResponseMessage = [OK]
12-03 10:38:32.359 22144 22144 I SA_SDK-1.5.22: [HttpRequestClient] ==================================================
12-03 10:38:32.359 22144 22144 I SA_SDK-1.5.22: [MetaManager] setEntryPointResponseData
12-03 10:38:32.360 22144 22144 I SA_SDK-1.5.22: [CommonAPIThread] getEntryPointOfIdm Response - Bundle[{confirmPasswordURI=https://us.account.samsung.com/accounts/ANDROIDSDK/confirmPasswordGate, pkiPublicKey=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCylnSE8ANPUNPmgYJGnApUrUPQiBmTY44Lw+fQbFOOslZZnuUasDFJuPU4287/LBQEpTtgPWLmjGftG/b2sj8eTH46mvhDtE8ijgZsMnGPMmhu/AljEvNOqU6nDZDtgGmL/pAdEBtsJ/VzClv8G9bV1kvczuZtg0gt3JTH+pagEwIDAQAB, signOutURI=https://us.account.samsung.com/accounts/ANDROIDSDK/signOutGate, pbeKySpcIters=200, signInURI=https://us.account.samsung.com/accounts/ANDROIDSDK/signInGate, signUpURI=https://us.account.samsung.com/accounts/ANDROIDSDK/signUpGate, chkDoNum=1}]
12-03 10:38:32.362 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] com.sec.android.app.sbrowser exist.
12-03 10:38:32.362 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] isAvailableBrowserInstalledAndEnabled ? true
12-03 10:38:32.364 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] com.android.chrome exist.
12-03 10:38:32.364 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] isAvailableBrowserInstalledAndEnabled ? true
12-03 10:38:32.364 22144 22144 I SA_SDK-1.5.22: [BrowserUtil] createBrowser - isCustomTabNotAvailable ? false, isChinaManufacturer ? false
12-03 10:38:32.368 22144 22144 I SA_SDK-1.5.22: [CustomTabBrowser] findPriorityCustomTabBrowser resolveInfo : arun.com.chromer
12-03 10:38:32.368 22144 22144 I SA_SDK-1.5.22: [CustomTabBrowser] targetPackageName : arun.com.chromer
12-03 10:38:32.370 22144 22144 I SA_SDK-1.5.22: [Util] getUiModeForWebView ? N
12-03 10:38:32.373 22144 22144 I SA_SDK-1.5.22: [Util] LangCodeBefore : en_US
12-03 10:38:32.373 22144 22144 I SA_SDK-1.5.22: [Util] LangCodeAfter : en_US
12-03 10:38:32.393  1481  5116 W ActivityManager: Unable to start service Intent { act=android.support.customtabs.action.CustomTabsService pkg=arun.com.chromer } U=0: not found
12-03 10:38:32.471  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:38:32.671  1481  2151 D ConnectivityService: NetReassign [no changes]
12-03 10:38:32.474  3457  3487 D DeviceStateHelper: Audo mode: 0
12-03 10:38:32.690 22010 23610 D ASF_JAVA[1.2.2]: MulticastServer.read - Multicast received.
12-03 10:38:32.691 22010 23619 D ASF_JAVA[1.2.2]: CallbackHandler.invokeUpperLayerUDPRequestListener - No listeners that could handle received UDP packet. 'mStartLine = [M-SEARCH * HTTP/1.1] mUri = [*] mStatusCode = 0] mHeaderMap = [] mContent = [] mClientIpAddr = [192.168.4.31] mMyIpAddr = [192.168.4.105] mPort = 63897'

It's odd to me that arun.com.chromer keeps getting called. That's probably the browser app Lynket (formerly Chromer), which Samsung identifies as an unapproved browser for login. However, this was the case on my other phone, too, and the solution was always to just temporarily set a different default browser like Chrome or Samsung Internet, which is what I've done here, too. I might try uninstalling it and seeing what changes.
 

mxbndr

Senior Member
Sep 29, 2010
52
5
OK, so I was able to sign into Samsung Health! Here's what I changed, based on those logs:

  1. I uninstalled Lynket. I don't think this mattered, but it was easy to do. I'll try installing it again and see if that changes anything.
  2. I stopped the service for an app called Advanced Charging Controller App (AccA), which is not an app that existed on my old phone. The clue for this was all the random calls to battery in the logs, which made me think maybe it was interrupting Samsung.
I think it's the 2nd one, though the first is browser-related and given Samsung's hardcoded method for whitelisting only certain browsers (Lynket should work because it's just Chrome via Chrome Custom Tabs, but Samsung blocks it), it might just be Lynket.
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Can confirm that Smartthings and Galaxy Wearable are both working, too. I haven't tested which app is the issue (I'm afraid to irreparably break it again) but will follow up here if it reoccurs. It's definitely one or the other!
 

icantlogin

Senior Member
Aug 23, 2017
73
55
Maybe Lynket was still set as the default WebView implementation in Developer Options before you uninstalled it. Next time try changing that option to Chrome or Android System WebView. Anyway, glad you solved it. And that you learned to use logcat; it's really useful to get a clue in these kinds of situations!
 
  • Like
Reactions: mxbndr

mxbndr

Senior Member
Sep 29, 2010
52
5
Maybe Lynket was still set as the default WebView implementation in Developer Options before you uninstalled it. Next time try changing that option to Chrome or Android System WebView. Anyway, glad you solved it. And that you learned to use logcat; it's really useful to get a clue in these kinds of situations!

Interesting. I didn't realize you could change that. I did check just now and only Android System WebView is an option, but maybe Lynket was there before I uninstalled and reinstalled it?
 

icantlogin

Senior Member
Aug 23, 2017
73
55
I recently ran into an artificial limitation built into AOSP. The default maximum lockscreen password length is set to 16 characters, which is ‘kind of arbitrary’, as the accompanying comment in the source code says:

Code:
/**
 * Maximum supported password length. Kind-of arbitrary.
 * @hide
 */
public static final int MAX_PASSWORD_LENGTH = 16;

From what I understand, this value is simply checked when setting a lock screen password, and if the new password is longer it is rejected. Organizations can set a different value for their managed devices through Android Device Policy, but regular users are stuck with it.

From now on, I will change this to 64 in my builds, which should accomodate any sane password or passphrase length, and about covers the maximum static password length supported by hardware tokens like the YubiKey and OnlyKey. GrapheneOS does this too by the way.

It's probably not a concern of many and I'm adding this tweak for my personal benefit, but if you ever wanted to secure your phone with a decent passphrase or long random string of characters stored on a hardware token, now you can.

Happy New Year everyone!
 

AkumDX

Senior Member
Aug 18, 2012
353
120
...
Loving the rom👍
Thanks for keeping it updated 🙂 @icantlogin
 

Attachments

  • Screenshot_20230126-113506_Settings.png
    Screenshot_20230126-113506_Settings.png
    140.8 KB · Views: 14
  • Screenshot_20230126-113455_Settings.png
    Screenshot_20230126-113455_Settings.png
    92.4 KB · Views: 14

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I recently ran into an artificial limitation built into AOSP. The default maximum lockscreen password length is set to 16 characters, which is ‘kind of arbitrary’, as the accompanying comment in the source code says:

    Code:
    /**
     * Maximum supported password length. Kind-of arbitrary.
     * @hide
     */
    public static final int MAX_PASSWORD_LENGTH = 16;

    From what I understand, this value is simply checked when setting a lock screen password, and if the new password is longer it is rejected. Organizations can set a different value for their managed devices through Android Device Policy, but regular users are stuck with it.

    From now on, I will change this to 64 in my builds, which should accomodate any sane password or passphrase length, and about covers the maximum static password length supported by hardware tokens like the YubiKey and OnlyKey. GrapheneOS does this too by the way.

    It's probably not a concern of many and I'm adding this tweak for my personal benefit, but if you ever wanted to secure your phone with a decent passphrase or long random string of characters stored on a hardware token, now you can.

    Happy New Year everyone!
    1
    Just d/led the Jan build, runs great. Thanks for continuing to work on this into the new year.
  • 8
    I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.

    As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.

    You can download the builds here:

    I intend to publish updates at least once every three months. Depending on my life, it may be more frequent, but never less frequent. There may be exceptions of course, like a zombie apocalypse happening or a new deadly virus spreading over the internet, forcing us all offline...

    Additional tweaks​

    • Default maximum lockscreen password length of 64 characters (instead of 16) [more info]

    Firmware​

    It's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).

    Clean install​

    • Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
    • Boot to bootloader a.k.a. fastboot
    • Flash the boot image with this command (replace filename with actual filename):
      fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
    • Boot to recovery
    • Factory reset > Format data/factory reset > confirm (your data will be erased)
    • Apply update > Apply from ADB
    • Sideload the ROM with this command (replace filename with actual filename):
      adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
      (If it asks "Signature verification failed. Install anyway?" answer Yes)
    • Optionally flash Gapps or anything else:
      • Advanced > Reboot to recovery
      • Run adb sideload with your zip
    • Reboot system now

    Updating​

    Updates are delivered through the built-in updater (Settings > System > Updater).

    If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.

    Migrating from last official LineageOS 18.1 build​

    So it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).

    The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).

    You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.

    When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...

    Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.

    If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!

    Acknowledgements​

    Thanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!

    Source code​

    5
    I recently ran into an artificial limitation built into AOSP. The default maximum lockscreen password length is set to 16 characters, which is ‘kind of arbitrary’, as the accompanying comment in the source code says:

    Code:
    /**
     * Maximum supported password length. Kind-of arbitrary.
     * @hide
     */
    public static final int MAX_PASSWORD_LENGTH = 16;

    From what I understand, this value is simply checked when setting a lock screen password, and if the new password is longer it is rejected. Organizations can set a different value for their managed devices through Android Device Policy, but regular users are stuck with it.

    From now on, I will change this to 64 in my builds, which should accomodate any sane password or passphrase length, and about covers the maximum static password length supported by hardware tokens like the YubiKey and OnlyKey. GrapheneOS does this too by the way.

    It's probably not a concern of many and I'm adding this tweak for my personal benefit, but if you ever wanted to secure your phone with a decent passphrase or long random string of characters stored on a hardware token, now you can.

    Happy New Year everyone!
    5
    The October update is live!

    A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.

    Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.

    What can I say, the geek in me is very happy :)
    3

    Gcam​

    (Not included.) The camera app from the factory ROM works mostly fine (I moved it over to LineageOS through a backup, I think I read installing it from the Play Store doesn't work as well?). There are a few bugs:
    • In photo mode, slide up to record video doesn't work
    • Motion Photos doesn't work
    • It doesn't scan QR codes without Google Lens

    App versions without Material You​

    If, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
    • Calculator 7.8
    • Calendar 2021.35.3
    • Camera 8.2.400
    • Clock 6.4.1
    • Contacts 3.49.2
    • Gboard 10.8.05
    • Maps 10.80.1
    • Phone 68.0.3
    • Photos 5.58.0
    • Translate 6.24.0.02
    Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.
    3
    This month's build includes a patch for a vulnerability where anyone with physical access to your phone can bypass the lock screen within 1 minute by plugging in a SIM-card, entering the wrong PIN for that SIM three times and then entering the PUK-code for that SIM and setting a new PIN. Try it before updating if you like...

    Yesterday I happened to stumble upon this article by one of the people who reported this bug to Google earlier this year. Seeing him easily bypass the lock screen in the included video was kind of terrifying. It really drove home to me why we update. Imagine how long this has been possible... at least since Android 10 (older versions aren't supported by Google), which also received the patch.

    Makes you wonder what kind of vendor patches we are missing out on by not upgrading to Android 12/13 and now being more than a year behind 😭