[ROM] Paranoid Android Quartz 5 - Pocophone F1

Search This thread

vihangkale

Senior Member
Sep 27, 2012
68
16
Xiaomi Poco F1
Looks like google has rolled out the update for hardware assisted safety net. CTS profile match is failing for Quartz 5 build
@mickaelmendes50

Screenshot_20210113-173358.jpg
 
  • Like
Reactions: Retrial

Retrial

Recognized Contributor & Translator
Jun 10, 2015
4,098
11,981
Athens
Samsung Galaxy S4
Sony Xperia L
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,705
1,143
Campinas
Xiaomi Poco F1
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,705
1,143
Campinas
Xiaomi Poco F1
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
816
1,083
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,705
1,143
Campinas
Xiaomi Poco F1
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
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!
 
@mickaelmendes50 when can we expect paranoid android ruby stable build for poco f1?
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...

You can find unofficial builds at t.me/aospa_mi845
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 75
    photo_2020-12-02_20-17-13.jpg


    We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.

    On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.

    Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.

    Notice

    As we are growing on our list of supported devices in each release, we require of a stronger build environment so we can speed up the compilation process for releases. Based on the actual Quartz 4 list, we support over 30 devices, which takes between 2 and 3 days for all the builds to be completed without counting possible compilation issues or rebuild needs, based on our current specs.

    We kindly ask all of you that are in position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.

    You can donate on the button below:
    Donate

    Device-specific issues

    You tell me.

    Note: Custom kernels are NOT supported!

    Requirements

    Make sure you've latest Stable firmware flashed before flashing the ROM.

    Download

    Get the latest Pocophone F1 build Download

    Changelogs

    Keep an eye on our Twitter account, @paranoidaospa , as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them.

    Paranoid Android Quartz released

    Instructions

    • Reboot to Recovery.
    • Performe full Wipe.
    • Install PA zip package.
    • Reboot


    Important / Useful links
    Paranoid Android Twitter
    Paranoid Android Channel (Telegram)
    Paranoid Android Community (Telegram)
    Paranoid Android Community for Mi845 (Telegram)

    Help us improve PA by submitting detailed bug reports with logs. Learn how to take logs here.

    Cheers and #StayParanoid!

    XDA:DevDB Information
    AOSPA, ROM for the Xiaomi Poco F1

    Contributors
    mickaelmendes50, herna
    Source Code: https://github.com/AOSPA/android_kernel_xiaomi_sdm845

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    Based On: CAF

    Version Information
    Status:
    Stable
    Current Stable Version: Quartz 4
    Stable Release Date: 2020-07-18

    Created 2020-06-25
    Last Updated 2020-07-22
    20
    Here's my first review after using Paranoid Android after 2 days usage.

    Pros:
    - Battery SoT almost hit 12 hours.
    - Stability because it is CAF based Android.
    - Smooth because it is CAF based Android.
    - Mobile Data, Wifi, Bluetooth, GPS, Hotspot, Dark Theme everything is working.
    - Devices not Overheating, Fast charging support.
    - No random reboot.

    Cons:
    - Performances, why? When I test the CPU it doesn't have a stable performances. It will always go up and down like 15%-30% (I test it on CPU Thorttling for 5 mins)
    - Lacks of features/customization, I hope they will add more.
    - Not for "Hardcore" Gamer that want to play PUBG on EXTREME SETTINGS with 60FPS no Drop and want the devices cool AF.

    So would I recommend this ROM for daily usage? Yes.
    For social media? Yes, it has a good battery backup. I almost hit 12 hours SoT.
    For gaming? No. Why? Because you will not get the performances you wanted.

    Is there any solution you will get the best performances for Gaming? Yes, use Custom Kernel but the devs not support it.
    You will have to play in higher temperatures in cost not even a single FPS drop and performances is a beast.

    I wish I can upload the CPU thorttling w/ or w/o the Custom Kernel.
    To make it clear, if you want to use this ROM to get the best performances and play PUBG, use Custom Kernel.

    Sorry devs! Can't provide any screenshot for more detailed.
    But I do like PA Quartz 3 and still counting on this ROM!

    Cheers!
    19
    July 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.
    I'm here for helping the community ;)
    Thank you so much.