[ROM][Pixel 3][10.0.0_r41] PixelDust CAF Android 10 for blueline [7 Aug 2020]

jewnersey

Senior Member
Jul 25, 2010
1,715
596
0
Thanks. Seems to be running quite smooth.
I am a big fan of the 2-button nav bar (swiping between apps feels intuitive) but is there any way to remap the home button (short and long press)?
 

luckana

Senior Member
Apr 30, 2012
741
177
73
Burgas
I had an issue with the Play Store not being certified, and Netflix would not function, which is a deal breaker. Suggestions?
You have to change your device's fingerprint with a certified one, you can do that for example with the MagiskHide Props Config magisk module

What not being certified means is that the device doesn't pass the SafetyNet api check
 
Last edited:

BNTofu

New member
Jul 27, 2016
1
0
0
Pardon my ignorance, but is a full wipe from PD just clearing usercache or flashing latest factory stock then following OP's install direction?

Again wanting to go from PD to PDCAF.
 

big in japan

Member
Nov 27, 2010
14
0
0
Can someone confirm that this is the correct order of operations to install Magisk (for G Pay, Netflix, etc.)? And does it need to be redone every time there's a PixelDust ROM update?

1) On phone: Install Magisk Manager
2) On desktop: Download Magisk patched boot image (https://sourceforge.net/projects/pixeldustproject/files/ota/blueline/magisk_patched.img/download)
3) Boot into Fastboot mode and flash magisk_patched.img - "fastboot flash boot magisk_patched.img"
4) Reboot phone

Many thanks, want to be sure I avoid a bricking!
 
Last edited:

nyolsson2

Member
Apr 25, 2020
8
4
3
Can someone confirm that this is the correct order of operations to install Magisk (for G Pay, Netflix, etc.)? And does it need to be redone every time there's a PixelDust ROM update?

1) On phone: Install Magisk Manager
2) On desktop: Download Magisk patched boot image (https://sourceforge.net/projects/pixeldustproject/files/ota/blueline/magisk_patched.img/download)
3) Boot into Fastboot mode and flash magisk_patched.img - "fastboot flash boot magisk_patched.img"
4) Reboot phone

Many thanks, want to be sure I avoid a bricking!
correct
 
  • Like
Reactions: big in japan

nyolsson2

Member
Apr 25, 2020
8
4
3
Thank you! This worked perfectly. "CTSfailed" in Magisk which I fixed by following these instructions (which led here for details).

One last question: Does updating PD CAF usually kill Magisk? Or does it generally survive the update process?
anytime you flash a new rom, even if just a dirty flash of an updated version of rom, you will need to repeat steps for magisk/root
 
  • Like
Reactions: big in japan

big in japan

Member
Nov 27, 2010
14
0
0
New problem! TLDR: Google Fi won't download the eSIM because it thinks my Pixel 3 is locked.

It's not, it's originally an unlocked Google Fi device, bought from fi.google.com when the P3 came out; the bootloader says that the device is unlocked. The error code it coughs up is E0x30003. I have Magisk installed and running to allow Google Pay tap-to-pay, and that seems to be fine. (Haven't been able to test it on a reader, but I'm able to access cards, etc.)

The only thing I noticed that was a bit unusual is that in Bootloader mode, the Boot Slot is B - probably because of the Magisk patched_boot.img?

Do I need to switch it to slot A and run the default boot image boot_caf_2020_2.img, set up Fi, and then run the Magisk patched_boot.img again?
 
Last edited:

nyolsson2

Member
Apr 25, 2020
8
4
3
New problem! TLDR: Google Fi won't download the eSIM because it thinks my Pixel 3 is locked.

It's not, it's originally an unlocked Google Fi device, bought from fi.google.com when the P3 came out; the bootloader says that the device is unlocked. The error code it coughs up is E0x30003. I have Magisk installed and running to allow Google Pay tap-to-pay, and that seems to be fine. (Haven't been able to test it on a reader, but I'm able to access cards, etc.)

The only thing I noticed that was a bit unusual is that in Bootloader mode, the Boot Slot is B - probably because of the Magisk patched_boot.img?

Do I need to switch it to slot A and run the default boot image boot_caf_2020_2.img, set up Fi, and then run the Magisk patched_boot.img again?
I don't know anything about google fi sry
 

redsmith

Senior Member
Apr 11, 2011
676
359
63
Hi, just flashed latest version. Does anybody else have trouble with system gestures?? The "back" gesture is borked. The little arrow appears and everything, but it only works about 40% of the time. What gives?

Clean-flashed, no 3rd party kernel or anything, not even rooted.

EDIT: Solved. "Accidental gestures" was toggled on. Everything works fine now. That Telegram support group is awesome!
 
Last edited:
  • Like
Reactions: spezi77 and kkjb

glehel

Senior Member
Jun 9, 2013
305
55
58
awesome ROM, very fast and stable, currently it will be the daily driver. Thanks to the developer! I hope there will be an update for it!
 

swordphsh

Senior Member
Jul 21, 2010
61
6
8
Does anyone else have trouble with Android Auto? I clean installed this yesterday. AA goes through the setup process, when the car says loading, it quickly switches to "no phone connected" (different from the 'no device' screen). Phone thinks it's connected but nothing come up on the car screen.