Looks like google has rolled out the update for hardware assisted safety net. CTS profile match is failing for Quartz 5 build
@mickaelmendes50
@mickaelmendes50
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.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
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
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)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.
Thanks, I really don't want to flash magisk or tinker around the rom.I like it the way it is minimal, that's why I am sticking to this rom.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.
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]
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
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
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
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 hereI was playing songs on Bluetooth, got a call so disconnected Bluetooth. When call got finished music started to play from speaker.
"Soon" since November
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?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
If it's not an issue, it can't be fixed. Android was designed to do just that.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?
Your Safetynet fix works.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.
I would like to be releasing it since January, but unfortunately it doesn't depend only of me. Andrey and Yume don't want to release for Mi845 devices yet, so I'm waiting for them...@mickaelmendes50 when can we expect paranoid android ruby stable build for poco f1?
I'm here for helping the communityJuly 20 was the scheduled date( weekend) so expect the build tomorrow if all went well. PA team is like Apple of Android while developing a rom. They simply polish basic features so well in their roms and implement it perfectly. Probably that's why everyone gets hype with every PA release.
Plus, the PA devs ( specially our device developer) respond to all queries politely and take feedback too. That's the best part about PA team.