Could that feature be ported to Note 9 or is it a Pixel only thing? I know the camera from the Pixel has been ported to the Note 9. I would really like the call screen.
https://phandroid.com/2016/10/11/pixel-dialer-apk-download/
https://android.gadgethacks.com/how-to/get-googles-new-pixel-dialer-other-android-devices-0174211/
Not sure if it works, but I think this is what you're after right?
I want the ability for assistant to answer my calls on the note 9! That would be an awesome port!
Probably detects if your phone is a pixel via build.prop or something, like they do for other features.
jdmsohc22 said:
https://phandroid.com/2016/10/11/pixel-dialer-apk-download/
https://android.gadgethacks.com/how-to/get-googles-new-pixel-dialer-other-android-devices-0174211/
Not sure if it works, but I think this is what you're after right?
Click to expand...
Click to collapse
This is what I am after...
https://www.theverge.com/2018/10/9/17955274/google-pixel-3-spam-calls-assistant-screen-filter
There are some flags you can change in the dialer_phenotype_flags.xml file to partially enable it, the call gets screened, but I cant hear the assistant.
Yes this would be awesome. Someone please port it!
Have you got any solution?.
Anyone figured out a way yet?
Sent from my SM-N960U using Tapatalk
I want this!!
a coworker just showed me this feature on his pixel. I know I have been under a rock:cyclops:, but is this possible on the Note 9 yet?
Mike
This is a Pixel exclusive and it's not likely Google well allow it to come to Note 9.
Sent from my Pixel 3 XL
Hi, I recently installed Pixel, and I'm loving it, the only thing it's bothering me is that the device model shows up as "Google Pixel 2 Xl, and every time I login using my phone, it says to check my "Pixel 2 Xl".
In the about phone, all the info is correct.
Is there anyway to fix it? Thanks.
Young Hipster said:
Hi, I recently installed Pixel, and I'm loving it, the only thing it's bothering me is that the device model shows up as "Google Pixel 2 Xl, and every time I login using my phone, it says to check my "Pixel 2 Xl".
In the about phone, all the info is correct.
Is there anyway to fix it? Thanks.
Click to expand...
Click to collapse
You can change it inside the build.prop.. But honestly it just a name on the rom and it will not affect your phone or your life.. Your phone is still Mi A2 ?
Aziziamran said:
You can change it inside the build.prop.. But honestly it just a name on the rom and it will not affect your phone or your life.. Your phone is still Mi A2 ?
Click to expand...
Click to collapse
That was my first thought, I used Root Browser Classic to edit build.prop but when I opened it, all the info that I could see was already correct. Did I miss something or is this truly a mystery?
Ok. That's weird now.. Before this I'm using PE around December until early January, I had same issue, when I open build.prop, model name is Pixel 2 XL and the brand is Google. I just change the model name to Mi A2.. Then I'm jump in to Havoc os until now, so I don't know about latest build from PE
Well, @Aziziamran, thanks for the assistance. I hope they fix it in the future builds of Pixel Experience.
What's everyone's view of rooting the pixel unlocked version? What features won't work? I know knox for samsung trips when unlocking. Is it the same concept with Pixels? My last device similar was a nexus 6 so yeah..
jobhax said:
What's everyone's view of rooting the pixel unlocked version? What features won't work?
Click to expand...
Click to collapse
Any feature that relies on Safetynet won't work and there is simply no way around that.
With Samsung, KNOX is a "fuse" that gets tripped so after you unlock the bootloader there's no going back. It'll forever know the bootloader has been unlocked at some point which messes with certain features (depending on make/model). With the Pixel phones you can flash the stock software and then re-lock the bootloader if you want. Once re-locked the OS sees the factory state and everything works as usual. Just make sure you've got the stock software flashed before you re-lock the bootloader or you risk bricking the device.
As a side note, with biometric security, make sure you've properly logged out of your Google account and removed all stored fingerprints or faces BEFORE you unlock. The unlocking process will wipe the device but your biometrics are still stored. If that happens you have to go through the setup process without biometrics and then perform a "proper" factory reset within the Android OS in order to get biometrics working again.
Of course the Pixel 5 is a new phone, so I'm giving this info based on currently released devices. There are always risks when you alter the factory state so be warned. There's a phrase my old boss used to use: "Pioneers take the arrows, settlers take the land." Not very PC but the underlying concept is sound.
I'll root asap. These days, I use it mainly for effective Adblock. The occasional app goes wonky, but it's a game of cat and mouse with safety-net.
YMMV etc
kboya said:
I'll root asap. These days, I use it mainly for effective Adblock. The occasional app goes wonky, but it's a game of cat and mouse with safety-net.
YMMV etc
Click to expand...
Click to collapse
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
SteveYoungs said:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
Click to expand...
Click to collapse
What's the best adblocker for a non-rooted phone right now?
Guys, since Android 9 you don't have to root in order to adblock. Just use the private DNS option together with something like nextdns.io . It's also battery efficient, since it's not a VPN.
SteveYoungs said:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
Click to expand...
Click to collapse
We'll see what happens because, as you make clear when you include experiences, MAV (Mileage Always Varies).
---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------
Nightwish1976 said:
Guys, since Android 9 you don't have to root in order to adblock. Just use the private DNS option together with something like nextdns.io . It's also battery efficient, since it's not a VPN.
Click to expand...
Click to collapse
True, but when I tried that after 9's release it wasn't particularly effective or at least not as effective as Adaway w Magisk's systemless solution. Maybe I'll give it another go on the P5.
likepeas said:
What's the best adblocker for a non-rooted phone right now?
Click to expand...
Click to collapse
Blockada, but download the App from the developer Website (play store Version doesnt get Updates Quick)
Pixel 5 will be the first device i dont plan to unlock+root, most benefits of rooting are gone in the last years because they got baked into Android. For adblocking there is Blockada which is as good as rooted adblock. I dont need a custom rom with stock clean Android and monthly Updates anymore. For debloating you dont need root, just a PC so i am going to deactivate most Google Apps.
Adblock so has a non-root version now.
kboya said:
We'll see what happens because, as you make clear when you include experiences, MAV (Mileage Always Varies).
Click to expand...
Click to collapse
Prediction: I'll eventually die of old age and you still won't be passing Safetynet. ☺
SteveYoungs said:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
Click to expand...
Click to collapse
If you know what you are doing there is no issues with Android 11, Magisk and safety net.
I can still use Google Pay and my banking apps without modules and nonsense coding. Just use Magisk and that is it. Oh of course you will need to hide a few apps in the Magisk settings.
Sent from my Pixel 3a XL using Tapatalk
One thing to keep in mind is warranty and insurance (if you have insurance) claims.
If you have to use the warranty or insurance and you are unable to revert to factory default then warranty and insurance claims will be a huge pain.
vandyman said:
If you know what you are doing there is no issues with Android 11, Magisk and safety net.
I can still use Google Pay and my banking apps without modules and nonsense coding. Just use Magisk and that is it. Oh of course you will need to hide a few apps in the Magisk settings.
Click to expand...
Click to collapse
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
SteveYoungs said:
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
Click to expand...
Click to collapse
Anything is possible, we go through this year after year with new updates to the software.
Google has always aloud its devices to have an unlocked boot loader and to be developed.
I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.
Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
Sent from my Pixel 3a XL using Tapatalk
vandyman said:
Anything is possible, we go through this year after year with new updates to the software.
Google has always aloud its devices to have an unlocked boot loader and to be developed.
I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.
Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
The Verizon versions of the Google Pixel 3Xl were locked down. I wouldn't say Giggle always allowed phones to be rooted. However, the ones sold by Google were rootable.
Sent from my Pixel 3 XL
Eudeferrer said:
The Verizon versions of the Google Pixel 3Xl were locked down. I wouldn't say Giggle always allowed phones to be rooted. However, the ones sold by Google were rootable.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
You are right. Verizon versions of Google devices will always be locked down.
If I remember correctly the last and only time that version allowed a Google unlocked device was a Samsung/Google Galaxy Nexus.
Sent from my Pixel 3a XL using Tapatalk
SteveYoungs said:
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
Click to expand...
Click to collapse
You said your not rooted right? You can still force basic key attestation (only needed for some devices), change device fingerprint, etc. Lots of things to do to pass safety net at the moment. Has worked fine for me ever since topjohnwu releaased that news.
vandyman said:
Anything is possible, we go through this year after year with new updates to the software.
Google has always aloud its devices to have an unlocked boot loader and to be developed.
I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.
Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
Click to expand...
Click to collapse
Hardware attestation does not prevent you from unlocking your boot loader, and it does not prevent you from rooting. What it does do is make passing Safetynet impossible if you are rooted, unlocked boot loader.
This is not something that will one day be worked around. The days of passing Safetynet on a rooted device are behind us.
SteveYoungs said:
Hardware attestation does not prevent you from unlocking your boot loader, and it does not prevent you from rooting. What it does do is make passing Safetynet impossible if you are rooted, unlocked boot loader.
This is not something that will one day be worked around. The days of passing Safetynet on a rooted device are behind us.
Click to expand...
Click to collapse
Nothing has changed yet! I still can use Gpay with Magisk and without any add on.
Sent from my Pixel 3a XL using Tapatalk
So right now I have the pixel 3 and want to upgrade to the pixel 5. What issues do I need to know about going into this. My pixel 3 has the terrible constant auto focus when using the camera and the power button is activates when not pressed bringing up the camera and rebooting itself. Does the pixel 5 have issues like this that google doesn't want to acknowledge or patch?
daswahnsinn said:
So right now I have the pixel 3 and want to upgrade to the pixel 5. What issues do I need to know about going into this. My pixel 3 has the terrible constant auto focus when using the camera and the power button is activates when not pressed bringing up the camera and rebooting itself. Does the pixel 5 have issues like this that google doesn't want to acknowledge or patch?
Click to expand...
Click to collapse
I've had mine since late November and haven't had any issues at all with it.
xunholyx said:
I've had mine since late November and haven't had any issues at all with it.
Click to expand...
Click to collapse
Thanks for the reply. I love my pixel 3 and want to keep the physical layout, I like having the rear mounted finger print scanner. The pixel 6 looks good but sadly I'm wanting the rmfps. Have you had any issues with ROMs or kernels?
daswahnsinn said:
Thanks for the reply. I love my pixel 3 and want to keep the physical layout, I like having the rear mounted finger print scanner. The pixel 6 looks good but sadly I'm wanting the rmfps. Have you had any issues with ROMs or kernels?
Click to expand...
Click to collapse
I haven't flashed any ROMs on it, but I did use ElementalX up until I went to Android 12 on the first Developers Preview. @flar2 hasn't updated for that yet afaik, but it worked great on 11. Last I checked he made a blind build that did cause issues on 12. It might be updated now. I should check.