Develop Bugs

[GENERAL HELP] Post Your Questions Here Instead of Making a New Thread

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nextbit Robin ​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
... @abhishekr700 @daavm
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request to me through PM
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link(Not yet made , PM me to add it once someone makes it.)
Index for Device Thread Link(Not yet made , PM me to add it once someone makes it.)
Please look for a similar [HELP THREAD] when visiting another device forum.
Dont forget to press the Thanks button for me !!! :good:
​

I think Robin is what Nexus 5X should've been. Having said that though, I am a T-Mobile subscriber and I wonder about T-Mobile's unusual network compatibility. Nexus 5X is fully compatible with T-Mobile: Wi-Fi Calling, Band 12 with VoLTE and E911, and even band aggregation between LTE bands: 2+4, 2+12, and 4+12. Is Robing going to have this level of compatibility with T-Mobile? That is pretty much the thing that is keeping me from ordering it and still considering Nexus 5X. Any information is appreciated.

Robin or Nexus 6P
I was the first group of backer. So hopefully I would receive the phone at the mid Feb. But I am having some question here. 1. I am having an 1+ 2(which is very disappointed, purchased on ebay, after 2months screen defected hardware problem, warranty not cover since no order number or buyer info ebay seller couldnt provide to me, and this is not im planning for). Then I would want to cash out robin and 1+ for a 6p. because of 1+ i couldnt trust new company anymore..... what a shame. So I am wondering which would you guys suggest robin is worry a try or just go for 6p.

arrickx said:
I was the first group of backer. So hopefully I would receive the phone at the mid Feb. But I am having some question here. 1. I am having an 1+ 2(which is very disappointed, purchased on ebay, after 2months screen defected hardware problem, warranty not cover since no order number or buyer info ebay seller couldnt provide to me, and this is not im planning for). Then I would want to cash out robin and 1+ for a 6p. because of 1+ i couldnt trust new company anymore..... what a shame. So I am wondering which would you guys suggest robin is worry a try or just go for 6p.
Click to expand...
Click to collapse
Wait for the Robin! It will be well worth the wait!

marsupial99 said:
I think Robin is what Nexus 5X should've been. Having said that though, I am a T-Mobile subscriber and I wonder about T-Mobile's unusual network compatibility. Nexus 5X is fully compatible with T-Mobile: Wi-Fi Calling, Band 12 with VoLTE and E911, and even band aggregation between LTE bands: 2+4, 2+12, and 4+12. Is Robing going to have this level of compatibility with T-Mobile? That is pretty much the thing that is keeping me from ordering it and still considering Nexus 5X. Any information is appreciated.
Click to expand...
Click to collapse
They've said on their Reddit forum that they expect to have Band 12 functionality approved and running soon:
https://www.reddit.com/r/Nextbit/comments/45gnna/band_12_checkin/
Sent from my Nexus 5 using Tapatalk

Can someone please tell me what font is used on the Nexbit Robin?
Thanks
Sent from my XT1575 using Tapatalk

Need ROOT! anyone?

Hi I wanted to know if the robin works on UK 4g/LTE although it says GSM buy seller

adamo86 said:
Hi I wanted to know if the robin works on UK 4g/LTE although it says GSM buy seller
Click to expand...
Click to collapse
Working perfectly fine here. Live in Scotland near Glasgow.

varun.gid said:
Need ROOT! anyone?
Click to expand...
Click to collapse
Someone has posted instructions in the general section. Root working fine here.

hi can anyone tell me how to get rid of the google bar on top on the home screen?
and also how can you show the FB msg on the screen? i hate going to the messenger and clicking the msg.
thanks

(Pixel XL + Project FI) vs. (Note 7 + prepaid USC)

(Pixel XL + Project FI) vs. (Note 7 + prepaid USC)
What is your hypothetical choice?
I'm a low data user, usually not more than 500MB per month...
So, what would YOU choose?
1) Note 7, banned, not any other phone even compares in terms of features, and $35 per month on USC
vs.
2) Pixel XL, you know the score, but $25-30 per month on Project FI.
I already have the two phones, I can cancel/port number, either one. The question is which do I keep?
Considerations:
a) In terms of features, prestige, looks, coolness factor, not even a contest - Note 7 blows ANY current phone out of the water. Add to that Samsung Pay, which works everywhere unlike Android Pay or Apple Pay or any other paypay, and you have a winner. But the phone is dead - no updates, no new features, possible disable of IMEI in the future... The future is very bleak, but today is glorious!
b) Pixel Xl is fast- FAST, Project FI is cheap for a low data user, and there are new updates a coming! But that's about it - the phone is kinda ugly, Project Fi is buggy, and it's just, well, uninspiring. It's a solid phone, but it's ...just that.
I'll have to make a choice in the near future - logic dictates to keep awesome Note 7 until Galaxy S8 arrives, then return for a full refund. But what if they ban Note 7 imei in the US like they did in New Zealand and Australia? Or stop full refunds?
Opinions?
P.S. BTW, before any fire hazard discussion starts - Note 7 safety is not a concern here. Zero concern.

@nabbed,
For starters, I'll state that I have a Pixel XL running on Fi.
My comments:
Note 7: Prestige? Maybe in your mind. But since the battery debacle, not in a lot of others.
Project Fi: Buggy? Really? I've been on Fi since it's launch. It has been rock solid for me.
In any event, my personal criteria is to never let my device drive my carrier choice. For me, the 1st criteria is to choose the carrier that best fits my needs and offers the best value. Then the device follows...

cam30era said:
@nabbed,
For starters, I'll state that I have a Pixel XL running on Fi.
My comments:
Note 7: Prestige? Maybe in your mind. But since the battery debacle, not in a lot of others.
Project Fi: Buggy? Really? I've been on Fi since it's launch. It has been rock solid for me.
In any event, my personal criteria is to never let my device drive my carrier choice. For me, the 1st criteria is to choose the carrier that best fits my needs and offers the best value. Then the device follows...
Click to expand...
Click to collapse
Hey, I also have a Pixel XL, running on FI! But it's buggy as hell! I spent over a literal hour on my other phone with an agent to sort it out. And it wouldn't make calls even though data was working, and then it was working again, making calls. And then it stopped calling again. And then it started again. There was no reason for it though, seemed like a bug in software.
And just so it doesn't seem like I'm blowing smoke up your huhu, here's a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nabbed said:
Hey, I also have a Pixel XL, running on FI! But it's buggy as hell! I spent over a literal hour on my other phone with an agent to sort it out. And it wouldn't make calls even though data was working, and then it was working again, making calls. And then it stopped calling again. And then it started again. There was no reason for it though, seemed like a bug in software.
And just so it doesn't seem like I'm blowing smoke up your huhu, here's a screenshot:
Click to expand...
Click to collapse
I understand that it is buggy, now, for you. I have no doubt. But this isn't the norm. Plenty of Project Fi users with the Pixel XL.
I don't know if the problem is your device. And I'm sorry that I can't offer any tangible tips for troubleshooting. But I can assure you that something isn't right. And if you can get it sorted out, the combination of XL plus Fi works just fine.

cam30era said:
I understand that it is buggy, now, for you. I have no doubt. But this isn't the norm. Plenty of Project Fi users with the Pixel XL.
I don't know if the problem is your device. And I'm sorry that I can't offer any tangible tips for troubleshooting. But I can assure you that something isn't right. And if you can get it sorted out, the combination of XL plus Fi works just fine.
Click to expand...
Click to collapse
Do you really believe that the combination of XL plus FI works just fine, that is, for everyone?
Or is it buggy Google software?
I guess I answered my own question here.

Aside from the risk of fire, it's now a federal crime you bring a Note 7 onboard an aircraft. Even considering the features, that would be enough to strike the Note 7 as an option.
My experience with Pixel XL on Project Fi has been flawless. For low data users, Fi offers excellent value, especially with the coverage overseas.

I have Fi since day one and it's been buggy since day one as well. I probably have over 50 support calls lol. If not for recent T-Mobile price hike and Fi somewhat buggy but fast international roaming, I would be on T-Mobile instead

Fi and the Pixel XL have been amazing for me so far in the few weeks I've had it. I've had a few call issues, but I quickly fixed by forcing to Sprint or vice versa.

You posted this in the pixel sub-forum, responses should be obvious.
Also, Samsung wouldn't take billions in losses and non-reversible brand damage in recalling a phone that isn't a threat to YOU.

Stupid question honestly.
And I've had FI for almost a year now, Pixel XL a couple weeks after it was released. Never had any problems with Fi.

g00s3y said:
Stupid question honestly.
And I've had FI for almost a year now, Pixel XL a couple weeks after it was released. Never had any problems with Fi.
Click to expand...
Click to collapse
You really think it was a stupid question? Note 7 vs. Pixel XL?

custom ROMs

Why have i not seen any custom Roms yet for this wonderful phone?

Lol, I believe it's due to the Pixel being kinda expensive maybe when the price drops we'll see more developers joining the Pixel wagon. All the development is currently over on the OnePlus side of the fence

Because we're all waiting for you to release some

My guess is because TWRP is still getting stablized and because of the pain in the ass associated with a/b partitions on the device.

bajasur said:
My guess is because TWRP is still getting stablized and because of the pain in the ass associated with a/b partitions on the device.
Click to expand...
Click to collapse
Why does it have two slots unlike the nexus devices...?
Sent from my OnePlus3 using XDA Labs

Prattham said:
Why does it have two slots unlike the nexus devices...?
Click to expand...
Click to collapse
Because Google wanted to implement better OTAs so they created dual partitions.

mackentosh said:
Lol, I believe it's due to the Pixel being kinda expensive maybe when the price drops we'll see more developers joining the Pixel wagon. All the development is currently over on the OnePlus side of the fence
Click to expand...
Click to collapse
I don't think this is correct. Pixel XL has nearly zero rom choices... Purenexus and a few others but it's not there. I think Rom development is dead.. 6P was the last great development phone at least for rootable on Verizon.

plisskenn said:
I don't think this is correct. Pixel XL has nearly zero rom choices... Purenexus and a few others but it's not there. I think Rom development is dead.. 6P was the last great development phone at least for rootable on Verizon.
Click to expand...
Click to collapse
The one plus devices have great support. I do believe it's because of the pricepoint

Rom's suck no matter what something doesn't work right and with this phone getting updates for 3 years I wouldn't even consider a rom at this point. The only time I use a rom is to get latest Android on a phone that doesn't get anymore updates.

plisskenn said:
I don't think this is correct. Pixel XL has nearly zero rom choices... Purenexus and a few others but it's not there. I think Rom development is dead.. 6P was the last great development phone at least for rootable on Verizon.
Click to expand...
Click to collapse
Rom developement isn't dead or else there wouldn't be one plus activity or 6p maintenance. Pxl2 is new and TWRP isn't even stable. It's still in early beta.
If anyone is pissed off that there device does something stupid or if they want center clock or AdAway, there will be rom development. I know AdAway is a root app, but it's an option that there is a demand for. They're will be ROMs as long as they're bootloader unlockable and manufacturers lack the options we need

And as far as custom roms "sucking", must not be running the right roms cause of had great experiences with a half dozen different ones.

dontbeweakvato said:
Rom developement isn't dead or else there wouldn't be one plus activity or 6p maintenance. Pxl2 is new and TWRP isn't even stable. It's still in early beta.
If anyone is pissed off that there device does something stupid or if they want center clock or AdAway, there will be rom development. I know AdAway is a root app, but it's an option that there is a demand for. They're will be ROMs as long as they're bootloader unlockable and manufacturers lack the options we need
Click to expand...
Click to collapse
Rom development is mostly dead on google phones since the first pixel, and it has nothing to do with the price point. People still buy these phones and they still want things associated with custom roms. My guess is that it may be due to the partition thing.
I remember it being a huge pain in the butt to install a rom on my first pixel. They make it harder i guess.
But I'm still hopeful.

bigv5150 said:
Rom's suck no matter what something doesn't work right and with this phone getting updates for 3 years I wouldn't even consider a rom at this point. The only time I use a rom is to get latest Android on a phone that doesn't get anymore updates.
Click to expand...
Click to collapse
Really? And that's why these forums are filled with them?

I can build ASOP rom with Gapps built in but I can't get the gapps to work when I boot the phone... I get a null error when I try to setup the phone and if I skip it I cant get any gapps to load. I think that has something to do with it.

Development is not dead, just take a look at the OnePlus 5 forum it's loaded with development and the 5t will follow suit soon

mackentosh said:
Development is not dead, just take a look at the OnePlus 5 forum it's loaded with development and the 5t will follow suit soon
Click to expand...
Click to collapse
It's only (almost) dead on pixel phones.....

deeproot said:
I can build ASOP rom with Gapps built in but I can't get the gapps to work when I boot the phone... I get a null error when I try to setup the phone and if I skip it I cant get any gapps to load. I think that has something to do with it.
Click to expand...
Click to collapse
I'm rooting for you to come up with something buddy! May the force be with you.

Pixel ROMs ain't dead... Maybe trickier,but not dead.
Ps. A true Mastermind can't resist the urge to mess with something that they can't or are told they can't mess with.

I just went and looked at the pixel XL forum. They have Pure Nexus, RR and EX kernel so if that is any indication of where this might go in more than happy with those choices...

We'll definitely have some cool ROMs for our device
https://plus.google.com/+CarbonROM/posts/ebgR9wonCAt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nitin

Google Pixel 2 XL DVT Models

Hey, So I got my hands on some Google Pixel 2 XL devices (actually 8) which were shipped here on 29th of August 2017 (Pixel 2 XL released on first week of Oct 2017)These devices are up for auctions by the Customs department here and I'am thinking to buy them however I have some doubts regarding the DVT sticker and "Not for Sale" marking on back-panel. I have some pics from inspection. It would be really great if you could help me out in buying decision.
My main doubts are:
1. Can build no. be changed after a normal update ? (i guess yes, but still looking for a sure answer)
2. Will it be a good deal to get them at 40% of the present retail price ? (I mean will people would like to own a Pixel 2 XL @ 40 to 50% discounted rate, 'cause "Not for Sale" is mentioned on back-panel)
Looking forward that community members will help.

The "Not For Sale" item on the back is a red flag. It tells me these are engineering samples. The software in an engineering sample is rarely finished and of beta quality. Worse, the bootloader may be locked, something Verizon owners are all too familiar with. The engineering sample bootloader however isn't a Verizon device and ignores any and all attempts to unlock it.
Google may have changed its development practices and these could be something else, but I would be wary regardless.

Strephon Alkhalikoi said:
The "Not For Sale" item on the back is a red flag. It tells me these are engineering samples. The software in an engineering sample is rarely finished and of beta quality. Worse, the bootloader may be locked, something Verizon owners are all too familiar with. The engineering sample bootloader however isn't a Verizon device and ignores any and all attempts to unlock it.
Google may have changed its development practices and these could be something else, but I would be wary regardless.
Click to expand...
Click to collapse
Thanks for your reply . Initially I too had same doubts and after checking about word "DVT" I found it stands for "Design Validation Testing" and it's one step before Mass Production for consumers. And also noticing the date of shipment which is 29th Aug 2017 (almost 35 days before official launch) I don't think there would be any hardware differences.
however one thing I would really like to know is Build No. I mean can we change that through a normal update ?
Here are the links/images of back-panel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and About me section in settings

Your image links are screwed up. Let's try that again.
Back Panel
About Me - Settings
Now, in answer to your question, probably not. The software here is a pre-release version of Android 8.0, as noted by the build number. From past experience with people who have come across these devices thinking they got a good deal, what usually happens is they attempt to update the device and it fails. Where these devices are intended for testing the software, Google locks down the device so that only testing images can be loaded. Unlocking the bootloader will not be possible, and Verizon owners know all about that, but this will be worse. The option to allow OEM Unlocking will most likely be grayed out.
Unless you don't care about unlocking the device and never seeing an update of any kind, this is not a good deal. Not when you can go to Swappa and purchase a production model that has potentially been used even less than these units.

https://drive.google.com/file/d/1G6G_YgwFOL0ktOSEw3G-wv33b5c6w7oZ/view?usp=drivesdk
https://drive.google.com/file/d/1h2ZdbqIyqtTpqFinYzRP1Lx29CYVK0cD/view?usp=drivesdkSo here are updated image links.
Build No. is taimen-userdebug 8.0.0 OPD1.170816.007

rasi_rana said:
Thanks for your reply . Initially I too had same doubts and after checking about word "DVT" I found it stands for "Design Validation Testing" and it's one step before Mass Production for consumers. And also noticing the date of shipment which is 29th Aug 2017 (almost 35 days before official launch) I don't think there would be any hardware differences.
however one thing I would really like to know is Build No. I mean can we change that through a normal update ?
Here are the links/images of back-panel
and About me section in settings
Click to expand...
Click to collapse
I do something similar for the Dept of Defense as far as testing weapons systems, software, etc. and if these units are indeed test validation units, they have been stressed in super heated, super cold, harsh environmental conditions, attempts to overcharge the battery, leave it plugged in during heavy use, overheating the CPUs, and a ton of other tests that validate it's consumer usability.
Basically, these units, if test validation pieces, have been abused both physically and software to represent the worst use the average consumer would put them through.
With some of our software testing, earlier versions are unable to be overwritten, or updated via conventional methods because it is still under testing. IF these units are similar, they might be stuck on whatever OS is currently on them.
If they are being sold AS IS, or you can verify they are actually TEST units, I'd put my money somewhere else.
Just my .02.
Good luck!
If it were me, I wouldn't risk ANY funding I wasn't willing to lose on these. With some

Az Biker said:
With some of our software testing, earlier versions are unable to be overwritten, or updated via conventional methods because it is still under testing. IF these units are similar, they might be stuck on whatever OS is currently on them.
If they are being sold AS IS, or you can verify they are actually TEST units, I'd put my money somewhere else.
Just my .02.
Good luck!
If it were me, I wouldn't risk ANY funding I wasn't willing to lose on these. With some
Click to expand...
Click to collapse
thanks for stopping by and putting forward your views.
How about investing 1/4th of the retail price on a single device ? and btw Build No. is "taimen-userdebug 8.0.0 OPD1.170816.007" (in case you could offer some more help)

rasi_rana said:
thanks for stopping by and putting forward your views.
How about investing 1/4th of the retail price on a single device ? and btw Build No. is "taimen-userdebug 8.0.0 OPD1.170816.007" (in case you could offer some more help)
Click to expand...
Click to collapse
If it were me, I would stop at Verification Test Device.
Only you can determine whether you're willing to risk how ever much 25% would total.
Especially if you don't know that you can sell these as upgradable, unlockable, or if they even have all the final release apps and features installed.
Since you asked, my advice is: walk away save your $ for another venture that has more reliable resale and profit tied to it. Way too many IFs and unknowns with these devices in my opinion.

General Pixel 6 pro - Face unlock

I don't think there's any thread regarding this, but I still think that the pixel 6 pro is still getting face unlock.
On the latest beta, you can get open the face unlock settings main page using this command in adb shell:
am start -n com.android.settings/com.android.settings.biometrics.face.FaceEnrollIntroduction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only issue is the "can't add more faces" text above. which blocks us from setting up any face unlock.
So far there's no way to bypass this, but I think that face unlock is definitely coming in the december feature drop, although it's one year late.

For what it's worth...
Google reportedly says face unlock won't be coming to Pixel 6 Pro
Google Germany reportedly told a publication that face unlock won't be rolling out to older Pixel phones, including the Pixel 6 Pro.
www.androidauthority.com

Lughnasadh said:
For what it's worth...
Google reportedly says face unlock won't be coming to Pixel 6 Pro
Google Germany reportedly told a publication that face unlock won't be rolling out to older Pixel phones, including the Pixel 6 Pro.
www.androidauthority.com
Click to expand...
Click to collapse
I doubt that. they more like denied to answer as they said "we don't know about any such thing currently". Hopefully Google will be generous with its older pixel users.

mohamed.sakhiri said:
I don't think there's any thread regarding this, but I still think that the pixel 6 pro is still getting face unlock.
On the latest beta, you can get open the face unlock settings main page using this command in adb shell:
am start -n com.android.settings/com.android.settings.biometrics.face.FaceEnrollIntroduction
View attachment 5746067
The only issue is the "can't add more faces" text above. which blocks us from setting up any face unlock.
So far there's no way to bypass this, but I think that face unlock is definitely coming in the december feature drop, although it's one year late.
Click to expand...
Click to collapse
On the pixel 4a5g I used face unlock. I think Google doesn't want to do it on Pixel 6 pro only.

Trungxuan said:
On the pixel 4a5g I used face unlock. I think Google doesn't want to do it on Pixel 6 pro only.
Click to expand...
Click to collapse
Can you elaborate more? how did you use it?

Home - PixelExperience
Home - PixelExperience
download.pixelexperience.org
I use the above romcook. Are google developers not as good as that development team? I use the above romcook. Are google developers not as good as that development team?

Trungxuan said:
Home - PixelExperience
Home - PixelExperience
download.pixelexperience.org
I use the above romcook. Are google developers not as good as that development team? I use the above romcook. Are google developers not as good as that development team?
Click to expand...
Click to collapse
Pixel experience is a custom rom. This thread is about face unlock in the stock official rom.

Trungxuan said:
Home - PixelExperience
Home - PixelExperience
download.pixelexperience.org
I use the above romcook. Are google developers not as good as that development team? I use the above romcook. Are google developers not as good as that development team?
Click to expand...
Click to collapse
Totally different. Comparing apples and oranges. Yes, it's possible and yes it has been added into custom builds, but that doesn't mean it meets a number of other criteria needed to be included in a stable release from Google. I am sure number one is security. Due to the technology of the pixel 6 and 6p, face unlock is far from being a "reliable security measure".

scott.hart.bti said:
Totally different. Comparing apples and oranges. Yes, it's possible and yes it has been added into custom builds, but that doesn't mean it meets a number of other criteria needed to be included in a stable release from Google. I am sure number one is security. Due to the technology of the pixel 6 and 6p, face unlock is far from being a "reliable security measure".
Click to expand...
Click to collapse
6 pro has a dpaf front camera, which has all the capabilities of the one used on the 7 series.

scott.hart.bti said:
but that doesn't mean it meets a number of other criteria needed to be included in a stable release from Google.
Click to expand...
Click to collapse
You mean like adding a feature to an old phone doesn't help them sell new ones?