[ROM] Paranoid Android Quartz 5 - Pocophone F1

Retrial

Recognized Contributor
Jun 10, 2015
957
1,425
133
Athens
Looks like google has rolled out the update for hardware assisted safety net. CTS profile match is failing for Quartz 5 build
@mickaelmendes50

View attachment 5185933
Yeh, and unfortunately I can't do nothing about that for an old build. But it will be fixed on Ruby, I already pushed the fix to PA sources.
You could try SafetyNet Fix from my ⚡POCO F1 Ultimade Collection & Guides⚡ and check if it works. Available for A10 and A11. (Let me know if it's working)
No root required, flash it in Recovery, Delete TWRP folder in Internal Storage if you still have problem.
 

Vinnom

Senior Member
Jun 21, 2012
1,704
1,142
143
Campinas
hmmm I'm facing a weird issue.

Everytime I try to make a call, the dialer starts the inCall screen and then finishes the call immediately. I've grabbed some logs to understand the issue and it seems real weird.

Below is some relevant log lines:

starting the dialer
Code:
01-12 18:01:00.700 I/ActivityTaskManager(1416): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.dialer/.extensions.GoogleDialtactsActivity bnds=[11,1828][364,2114]} from uid 10220
01-12 18:01:00.713 I/wm_set_resumed_activity(1416): [0,com.google.android.dialer/.extensions.GoogleDialtactsActivity,bringingFoundTaskToFront]
01-12 18:01:00.713 I/wm_new_intent(1416): [0,164464861,1748,com.google.android.dialer/.extensions.GoogleDialtactsActivity,android.intent.action.MAIN,NULL,NULL,270532608]
01-12 18:01:00.731 I/wm_set_resumed_activity(1416): [0,com.google.android.dialer/.extensions.GoogleDialtactsActivity,resumeTopActivityInnerLocked]
01-12 18:01:00.732 I/wm_resume_activity(1416): [0,164464861,1748,com.google.android.dialer/.extensions.GoogleDialtactsActivity]
permission related logs:
Code:
01-12 18:01:00.751 I/DialerPermissionsUtil(20003): com.android.dialer.permissions.PermissionsUtil.registerPermissionReceiver:234 Permission: android.permission.READ_CONTACTS
01-12 18:01:02.756 I/DialerPermissionsUtil(20003): com.android.dialer.permissions.PermissionsUtil.unregisterPermissionReceiver:240 unregisterPermissionReceiver
01-12 18:01:04.613 I/DialerPermissionsUtil(20003): com.android.dialer.permissions.PermissionsUtil.registerPermissionReceiver:234 Permission: android.permission.READ_CONTACTS
01-12 18:01:06.155 I/DialerPermissionsUtil(20003): com.android.dialer.permissions.PermissionsUtil.unregisterPermissionReceiver:240 unregisterPermissionReceiver
selecting the contact and calling:
Code:
01-12 18:01:02.385 I/DialerInCallPresenter(20003): com.android.incallui.InCallPresenter.isActivityStarted:1411 inCallActivity is started
01-12 18:01:02.431 I/DialerInCallFragment(20003): com.android.incallui.incall.impl.InCallFragment.setPrimary:676 primaryInfo: PrimaryInfo, number: *****-****, name: Redacted-10-chars, photo: null, photoType: 0
01-12 18:01:02.445 I/DialerInCallFragment(20003): com.android.incallui.incall.impl.InCallFragment.setCallState:727 primaryCallState: PrimaryCallState, state: CONNECTING
01-12 18:01:02.448 I/DialerCallButtonPresenter(20003): com.android.incallui.CallButtonPresenter.updateUi:1078 state: PENDING_OUTGOING
01-12 18:01:02.448 I/DialerCallButtonPresenter(20003):     call: null
01-12 18:01:02.448 I/DialerCallButtonPresenter(20003): com.android.incallui.CallButtonPresenter.updateButtonsState:1098 call: null
and after repeating this pending outgoing -> null thing for a while:
Code:
01-12 18:01:04.482 I/DialerInCallPresenter(20003): com.android.incallui.InCallPresenter.dontAddToThisMethodOrYoullBeSorry:999 Phone switching state: INCALL -> INCALL
01-12 18:01:04.487 I/DialerCallCardPresenter(20003): com.android.incallui.CallCardPresenter.handleInCallStateChange:336 oldState: INCALL, newState: INCALL
01-12 18:01:04.489 I/DialerInCallFragment(20003): com.android.incallui.incall.impl.InCallFragment.setCallState:727 primaryCallState: PrimaryCallState, state: DISCONNECTED
01-12 18:01:04.568 I/DialerInCallPresenter(20003): com.android.incallui.InCallPresenter.isActivityStarted:1411 inCallActivity is started
01-12 18:01:04.574 I/wm_finish_activity(1416): [0,268421563,1754,com.google.android.dialer/com.android.incallui.InCallActivity,finish-activity]
01-12 18:01:04.573 I/DialerInCallActivityPeer(20003): com.android.incallui.InCallActivityPeer.shouldCloseActivityOnFinish:1013 activity is visible and has no locks, allowing activity to close
01-12 18:01:04.583 I/wm_pause_activity(1416): [0,268421563,com.google.android.dialer/com.android.incallui.InCallActivity,userLeaving=false]
01-12 18:01:04.584 I/DialerCallList(20003): com.android.incallui.call.CallList.lambda$updateCallInMap$7:852 Timeout expired, finish the disconnected call
01-12 18:01:04.588 I/DialerInCallPresenter(20003): com.android.incallui.InCallPresenter.dontAddToThisMethodOrYoullBeSorry:999 Phone switching state: INCALL -> NO_CALLS
01-12 18:01:04.589 I/DialerCallCardPresenter(20003): com.android.incallui.CallCardPresenter.handleInCallStateChange:336 oldState: INCALL, newState: NO_CALLS
01-12 18:01:04.589 I/DialerCallScopesImpl(20003): com.android.dialer.incall.core.callscope.CallScopesImpl.setLegacyPrimaryCallScope:272 Legacy primary call set as empty
01-12 18:01:04.589 I/DialerInCallFragment(20003): com.android.incallui.incall.impl.InCallFragment.setCallState:727 primaryCallState: PrimaryCallState, state: IDLE
after that, a lot of logs related to NO_CALLS going to NO_CALLS. Anyone faced anything like this? I've just tried Google Dialer.
 

Vinnom

Senior Member
Jun 21, 2012
1,704
1,142
143
Campinas
I was playing songs on Bluetooth, got a call so disconnected Bluetooth. When call got finished music started to play from speaker. 😐
Isn't resuming the expected behavior? As you disconnected the BT, it went through the route available, which was the speaker, if I understood you correctly. Had you not disconnected the BT, it would resume to it. At least, this is the kind of thing that happens here
 
  • Like
Reactions: SAGY the MEGATRON

Forever Alone

Senior Member
Jun 22, 2012
811
1,068
123
Isn't resuming the expected behavior? As you disconnected the BT, it went through the route available, which was the speaker, if I understood you correctly. Had you not disconnected the BT, it would resume to it. At least, this is the kind of thing that happens here
Yes u understood it right, but it's little embarrassing. I was listening songs in car, when I got out the song was blasting through my phone lol. Any way to fix this?
 

Vinnom

Senior Member
Jun 21, 2012
1,704
1,142
143
Campinas
Yes u understood it right, but it's little embarrassing. I was listening songs in car, when I got out the song was blasting through my phone lol. Any way to fix this?
If it's not an issue, it can't be fixed. Android was designed to do just that.
I think if, during the call, you force close the music app (via Settings > Apps) then it won't resume, but I'm not sure if the intent will restart the app. Another possible way (I think) would be to use tasker to route the call to phone speaker when a call is received and then route the sound to bluetooth when the call ends.
 

McDanknalds

New member
Apr 23, 2019
2
0
1
You could try SafetyNet Fix from my ⚡POCO F1 Ultimade Collection & Guides⚡ and check if it works. Available for A10 and A11. (Let me know if it's working)
No root required, flash it in Recovery, Delete TWRP folder in Internal Storage if you still have problem.
Your Safetynet fix works.

That said, I'll come back to this ROM once Ruby has been released. It had served me well for 6 months but its time to move on. Keep up the good work devs!