yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Beefheart:
Can't speak for other Pixels as this is the first I've owned, but the 7 Pro is very easy to root. Received mine in the post yesterday around 1230, it was rooted by 1330. I have unrooted and relocked the bootloader now as I decided I'd rather have OTA updates working, but it's one of the easier phones I've rooted.
[Google Pixel 7 Pro] Pritster5:
Super easy. You need a PC, USB cable, and just follow the guide here: https://xdaforums.com/t/unlock-boot...gain-all-relevant-links.4502805/post-87540339
[Google Pixel 7 Pro] K1nsey6:
Coming from OnePlus, where I could root with my eyes closed, the process for rooting Pixel looks complicated as ****
[Google Pixel 7 Pro] cultofluna:
Rooting pixels is taking no more than 2 minutes
[LG V60 ThinQ Questions & Answers] Najam121:
I own LG G8, It does have Video in Portrait Mode at very early stage, Does LG V60 also have this? or did they drop that idea?
[LG V60 ThinQ Questions & Answers] FCORGI:
It does have this. Long pressing on the shutter button while in portrait mode will switch to video portrait mode. Additionally the tooltip blurb mentions both photo and video uses.
[LG V60 ThinQ Questions & Answers] Najam121:
Thanks,If you have LG V60 can you or someone else can share the result of portrait video? I didn't find any sample on youtube for V60
[Battlestations] Godless_Geek:
I do some gaming and a lot of programming, among other things. I'm definitely a multitasker.

Mobo: MSI MEG x399 Creation

CPU: AMD Threadripper 2920X

GPU: Zotac Gaming GeForce RTX2060 w/6 GB

Memory: G.Skill Ripjaws V DDR4-3200 CL14 (64 GB)

Power: SeaSonic Focus Plus Platinum 750W 80+ Platinum

Case: Phanteks Enthoo Pro ATX Full Tower

Monitors: BenQ Zowie 24" @ 144Hz, BenQ XL2420T 24" @ 120Hz

OS: MS Windows 10 Pro / Linux Mint 20.3
[Moto E7 Plus Questions & Answers] kalinx:
Hi! I want to unlock bootloader on my Moto E7 plus and i have a problem. I install official sdk tool from android website and add path to system variables etc. I open CMD in platform tools and connect my phone to pc, activate USB debugging and OEM unlock in developer tools options, in the next step i type commands in cmd console - adb reboot bootloader (works), checked again it was my device still connected - adb devices (still visible), but now i'm stuck af because if i type "fastboot oem get_unlock_data" console responds to me (remote: unknown command).

Did i lost this battle forever, guys? :poop:
[Moto E7 Plus Questions & Answers] caio61:
Try turning off your phone and entering fastboot by pressing power + volume down and then try again if you still get that error use "fastboot devices" to check if fastboot recnogizes the phone
[Google Pixel 7 Pro] rester555:
So in display fingerprint for in app authentication... Ugh that sucks
[Google Pixel 7 Pro] Morgrain:
This whole community feedback on Faceunlock sparks a curious eyebrow raising.

When the P4 XL came out, there were thousands of people that screamed for a Fingerprint unlock. They didn't like Faceunlock. They felt Soli was pure gimmick. They didn't like the P4 XL. When the P5 came out, those voices rose again, calling out the P4 XL for having "mega bezels and ****ty biometrics".

Back when I used my P4 XL, I loved faceunlock, except for two facts

a) Faceunlock was horrible to use when I had to wear masks in shops or other public places, due to Covic restrictions in 2020/2021 - any time I wanted to pay via phone or look something up, I had to write down my pin, which is a horrible security risk when you are surrounded by other people.

b) most apps did not support Faceunlock biometrics at all, even 1 1/2 years after launch, only a handful of apps supported the new biometric API. Meaning, for example, whenever I wanted to open my banking app, I had to write down all the details by hand. That was terrible. And since it was the fault of the developers, and Google didn't force them to comply, there were little ways as a user to mitigate that problem.

Those voices soon died out, however. The ones that "upgraded" from a P4 XL noticed a) the p5 was a downgrade in specs and b) Faceunlock offers a good amount of practicality, IF done right. Now, the P4 XL with Soli was near perfect: You only had to get close with your hand to your phone, it detected you and when you picked it up, the unlock was instant. Friends of mine with IPhones saw that and were stunned and marveled about it ("you don't have to swipe to unlock your phone? You just have to pick it up, and it's fully automatic? Woa, that's cool, my IPhone can't do that. It's annoying to always swipe to unlock, even after faceunlock").

I loved the experience of Soli powered Faceunlock. Soli was not a gimmick, Soli was the final piece in the puzzle that made Faceunlock a seamless experience. The hand waving thing was a gimmick, yes, but not the detection to unlock.

Now, in the recent year, I've read hundreds, if not thousands of people over at Reddit, on Twitter or here at XDA, wishing for faceunlock. Something that (back in the day) barely managed to create a sort of positive feedback.

People tend to take something for granted, until it is taken away.

And instead of a decent faceunlock, we now - sadly, because of the overwhelmingly bad feedback of the Community about faceunlock - have a weak, 2D version that will only be used for simple phone unlocking.

Google should have gone the Apple route, made a notch and then refined upon it, PLUS adding the FP scanner.

Well, let's see what the future holds.
[Google Pixel 7 Pro] rester555:
Absolutely agreed. I remember all the articles that said it was a gimmick. I agree that the hand gestures were a joke.

Saying that, I loved my Pixel 4 XL with the soli sensor. I was able to use the face unlock through a module on magisk with all apps that used the fingerprint sensor. So I had the best of both worlds.

I too remember when COVID made it difficult, but think the face unlock was still amazing. I second putting a pill back on the front display with the soli sensor to get a proper face unlock.

Currently on the pixel 6 pro, I am using the face unlock module from Moto baked in. It doesn't allow for you to use the face unlock on in-app though. That sucks. Here's to hoping you can use that API through some form of magisj module on all apps including unlocking the screen.
[Google Pixel 7 Pro] rester555:
On second thought, the Pixel 4 XL, IMHO, was the best pixel to me from a utility stand point.
[Google Pixel 7 Pro] Namelesswonder:
According to someone that checked a display model the modem is the 5300g. This contrasts to the leaks from Android Police that it would be the 5300b or from Twitter that it would be the 5300f.

I'm trying to find out what process node the G2 is on but I can't find any solid information. There are no references anywhere and I've seen guesses with 5LPE, 5LPP, 4LPX, 4LPE, 4LPP which hasn't even entered volume yet, and shout out again to Android Police with the non-existent "4PLP" which they've misconstrued from the process of fan-out panel level packaging.

It's probably going to be on 4LPE, my bigger question is whether the modem is going to internal this time. They cut back on the size of the GPU, so they might have enough space to make the modem internal now. If they don't then it's probably another year of bad efficiency. Will have to wait for TechInsights to do a teardown.
[Google Pixel 7 Pro] Namelesswonder:
Also the telephoto sensor should be the GM5 as it has 0.7 micrometer pixels, while the GM1 is 0.8 micrometer.
[Google Pixel 7 Pro] rester555:
Yes, here's to hoping the modem is internal.
[Google Pixel 7 Pro] Morgrain:
Changed those values. Thanks for the infos!
[Google Pixel 7 Pro] Solomon M:
"This thread will serve as a comprehensive overview about the technical data of the P7 Pro"

I'm game lets put together the info we all wish we had and do it right! hehehe

& the model numbers for replacement parts are what?

LOL Someone has completed a teardown but didn't list out all the "replacement parts list & locations guide" so users could repair what gets broken easily.....

💗Google💗 should make this avalible...

wait we don't live in a world where this : https://www.onearmy.earth//project/phonebloks is reality manfest.
[Google Pixel 7 Pro] benleonheart:
Do you have a source for the 120mm claim on the telephoto?

Thanks in advance!!!!
[Google Pixel 7 Pro] Morgrain:
Sure

Google Pixel 7 Pro - Full phone specifications

www.gsmarena.com

View attachment 5731337
[Google Pixel 7 Pro] wilbur-force:
Can anyone confirm what the DAC will be capable of? likely to manage lossless or will i need to go for an external DAC?
[Google Pixel 7 Pro] Namelesswonder:
You're going to have to get an external DAC because the only thing connected to the internal DAC are the speakers, there's no other way to get an analog audio signal out of the phone.
[Google Pixel 7 Pro] m3ath:
Why three years only update os
[Google Pixel 7 Pro] galaxys:
Not sure why, but should be more!📱
[Google Pixel 7 Pro] m3ath:
yes but Google has not yet announced that it will be 3 years, this number is not a source
[Google Pixel 7 Pro] Lughnasadh:
Yep, their support page which lists how long guaranteed Android version updates will be for doesn't list the Pixel 7 series yet. Haven't seen an official word elsewhere, but might have missed it.

The fine print in the Google Store say:

"Pixel security updates for at least 5 years from when the device first became available on the Google Store in the US. Updates may also include feature drops and other software updates. See g.co/pixel/updates for more information."

Having said that, I'm guessing it will still be 3 years of OS updates. If it were more I think they would have announced it during the Event to entice more people to buy it.
[Google Pixel 7 Pro] wilbur-force:
I thought most android phones had internal DACs for USB audio but that they normally didn't push high quality?
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, appears to be 4LPE as you surmised, that is if SamMobile is not a close sibling of Android Police 🙃

Google’s Tensor G2 chipset uses Samsung’s 4nm process, Exynos 5300 5G modem

The Pixel 7 and the Pixel 7 Pro, which were launched last week, use Samsung Foundry's 4nm fabrication process and ...

www.sammobile.com

EDIT: Of course, Android Authority says 5nm, quoting a Google spokesperson...

Google Tensor G2 is a 5nm chip, despite what the internet might say

Google has confirmed that the Tensor G2 processor powering the Pixel 7 and Pixel 7 Pro is built on a 5-nanometer manufacturing process.

www.androidauthority.com
[Google Pixel 7 Pro] Namelesswonder:
Internal DACs can't interface with USB audio because DACs output analog signals and USB audio is digital. Sound over USB audio is handled by the OS encoding the still digital audio stream into a format for USB audio.

USB digital audio | Android Open Source Project

source.android.com

What you're thinking of is the analog audio over USB-C mode. Most phones don't implement the analog audio over USB-C port today because some manufacturers jumped the gun back in the day and implemented it before the specification was finalized leading to differences between the passive dongles. This lead to some manufacturers not implementing this at all and just relying on USB audio dongles that would work on every device with an OS supporting USB audio.

Google has never released a device that implements analog audio over the USB-C port.

Audio quality over USB audio with regards to the host device is all on the source stream and what the OS does to the stream, and what USB Audio Class version is supported. USB Audio Class 1 supports 24bit 96KHz PCM, with USB Audio Class 2 the only limit is what the OS supports, the bandwidth of USB version being used, and audio device supports.

I believe Android 13 supports USB Audio Class 2, however the audio stack on Android is artificially limited for sample rate and in order to break past that you need a Magisk module or script.

GitHub - Magisk-Modules-Alt-Repo/usb-samplerate-unlocker: USB (HAL) Audio Class drivers on Android have a limiter of sample rates at 96kHz. This magisk module unlocks the limiter.

USB (HAL) Audio Class drivers on Android have a limiter of sample rates at 96kHz. This magisk module unlocks the limiter. - GitHub - Magisk-Modules-Alt-Repo/usb-samplerate-unlocker: USB (HAL) Audi...

github.com

GitHub - yzyhk904/USB_SampleRate_Changer: This script changes the sample rate of the USB audio class driver on Android devices on the fly like Bluetooth LDAC or Windows mixer

This script changes the sample rate of the USB audio class driver on Android devices on the fly like Bluetooth LDAC or Windows mixer - yzyhk904/USB_SampleRate_Changer

github.com
[Google Pixel 7 Pro] Namelesswonder:
Wouldn't make much sense for it to be anything other than 4LPE. 4LPE started risk production last year and is now in mass production.

4LPP is only starting up now so can't be used.

3GAE isn't possible with it just entering risk production and being too expensive for the size of Tensor.

5LPP doesn't exist because it was renamed to 4LPX, but ended up not carrying any improvements over 5LPE. Putting GS201 on 4LPX/5LPE would be laughable, and everyone already laughed at Qualcomm for doing it earlier in the year, but then again Google thought the 5123b would be a good modem.

SamMobile also doesn't have citations or sources, so they're just pulling it out of nowhere. They confidently published last month that Tensor G3 would be on 3nm. They actually attributed a source, however the source itself had no sources, was written non-authoritatively, and included the blogspam holy grail "some experts say..." without referencing the experts.
[Google Pixel 7 Pro] Batfink33:
Google themselves are saying it's 5nm https://www.androidauthority.com/tensor-g2-5nm-chip-3218342/

Also had on their website that the battery life was Less than the P6! Not sure why anyone would be surprised by this given the specs of the SOC.
[Google Pixel 7 Pro] Lughnasadh:
Yeah, that's why I said "for what it's worth". More inclined to believe Android Authority's quote of the Google spokesperson, but you never know.
[Google Pixel 7 Pro] Batfink33:
Literally says on the Google website the 7pro has *worse* battery life than the 6Pro 🤦
[Google Pixel 7 Pro] EtherealRemnant:
For what it's worth, DevCheck Pro is reporting A76, not A78.

https://twitter.com/i/web/status/1578808287201722368
[Google Pixel 7 Pro] EtherealRemnant:
Not directly comparable. Testing conducted in 2021 by a third party versus first party testing in 2022, both on pre-production hardware so neither is truly representative to begin with. I highly doubt that battery life will be worse on a 4nm chip. Early reports on Twitter suggest that battery may not be an issue this time around.
[Google Pixel 7 Pro] Batfink33:
Deleted.
[Google Pixel 7 Pro] EtherealRemnant:
I'm just saying that's what it's reporting.
[Google Pixel 7 Pro] Namelesswonder:
Won't find out until Google says something official or someone puts the processor under a microscope. Although it's starting to lean towards Google doing the laughable thing yet again.

Their silicon hardware division seems to be lost since Manu Gulati left to cofound NUVIA.

It looks like their testing methodology changed to a "median Pixel user". So we'll end up seeing how it actually performs in the coming weeks.

DevCheck uses a database for lookup, best case scenario is that it is looking at /proc/cpuinfo to get the implementer, variant, part, and revision to tell you what it is. We'll find out soon once someone posts the output from /proc/cpuinfo. If the middle cores are part 0xD41 then it's A78, I don't know how DevCheck does it, but the cpuinfo library does check for it.
[Google Pixel 7 Pro] m3ath:
I think the system will be updated for 5 years

Google Pixel 7 Pro Tech Specs - Google Store

See the full tech specs and discover how Pixel 7 Pro's camera helps you capture the moment beautifully from virtually any distance.

store.google.com
[Google Pixel 7 Pro] Ghisy:
Security updates are different from OS updates. Pixels are 3 years for the OS and 5 for the security patches. Your screenshot matches this. Unless Google have changed their mind.
[Google Pixel 7 Pro] Dayuser:
So Tensor 2.. Is it with 2xA76 or 2xA78??
[Google Pixel 7 Pro] EtherealRemnant:
2xA78
[Google Pixel 7 Pro] Namelesswonder:
Yep 4 A55, 2 A78, 2 X1.

cheetah:/ $ cat /proc/cpuinfo
processor : 0
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 1
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 2
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 3
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 4
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x1
CPU part : 0xd41
CPU revision : 1

processor : 5
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x1
CPU part : 0xd41
CPU revision : 1

processor : 6
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x1
CPU part : 0xd44
CPU revision : 0

processor : 7
BogoMIPS : 49.15
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x1
CPU part : 0xd44
CPU revision : 0
[Google Pixel 7 Pro] Namelesswonder:
@Morgrain

Pulled information on the storage, it appears on page 3 of their MWC 2021 trade show slides.

176 layer 4D NAND, 2GB/s sustained read, 1.3GB/s sustained write on the 128GB, 1.7GB/s sustained write on 256/512GB.

Apparently Google could've made a 1TB phone too.

I don't know if Google is only sourcing the flash from SK Hynix or if Micron and Kioxia are also supplying flash. Will need more people to pull their NAND model number from the bootloader with fastboot getvar all.
[Google Pixel 7 Pro] Namelesswonder:
USB speed is 10Gbps. Speedy transfers if your computer and cable can support it.

$ sudo lsusb -d 18d1:4ee7 -v
Bus 002 Device 025: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x18d1 Google Inc.
idProduct 0x4ee7 Nexus/Pixel Device (charging + debug)
bcdDevice 5.10
iManufacturer 1 Google
iProduct 2 Pixel 7 Pro
iSerial 3 <redacted>
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x002c
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 896mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 1
iInterface 4 ADB Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 4
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x002a
bNumDeviceCaps 3
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x0000010e
BESL Link Power Management (LPM) Supported
BESL value 256 us
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000f
Device can operate at Low Speed (1Mbps)
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 0 micro seconds
bU2DevExitLat 0 micro seconds
SuperSpeedPlus USB Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000001
Sublink Speed Attribute count 1
Sublink Speed ID count 0
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x000a4030
Speed Attribute ID: 0 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[1] 0x000a40b0
Speed Attribute ID: 0 10Gb/s Symmetric TX SuperSpeedPlus
Device Status: 0x0000
(Bus Powered)

Did a firmware flash in 60 seconds flat. I remember when it took almost 200 seconds back on the Nexus 6P. And more on a Pixel XL with it's fat firmware images if you weren't using a USB 3.0 5Gbps cable.
[Google Pixel 7 Pro] Morgrain:
Thanks for the info, added it to the main post. My p7 pro has still not been shipped (I ordered on release -.-) so it'll be some time until I will dive into all the finer details and add it myself.
[Google Pixel 7 Pro] Namelesswonder:
Bought a 256GB to return my 128GB, my 256GB is using Kioxia THGJFGT1E45BAIP.

112 layer vertically stacked 3D NAND TLC, 2.1-2.3GB/s sustained read, 1.45GB/s sustained write.

Wayback Machine

UFS 3.1 for Consumer & Industrial | KIOXIA - United States (English)

Designed to be the next-generation of higher performance embedded storage after e-MMC, KIOXIA’s Universal Flash Storage (UFS) brings ultra high-speed read/write performance, low power consumption and quick application launch times demanded by a wide range of digital consumer products. UFS has a...

americas.kioxia.com

Only question left is what model of Micron flashes are being used for the phones that have them. I have seen two dumps of getprop that reference Micron for storage, however that doesn't show the model number, only fastboot getvar all does.

Also I'm guessing that 512GB Kioxia is gonna be model THGJFGT2T85BAIU, will have to wait for people with 512GB to verify.

1.6GB/s sustained write.

Wayback Machine
[Galaxy S6 Q&A, Help & Troubleshooting] fovea1959:
Trying to get TWRP installed on an old S6 (with no SIM card), on the way to getting a newer Android on it.

Device is freshly factory reset, I do not believe that it has ever been rooted.

Per

, I have been using Odin to load twrp-3.3.1-0-zerofltespr.img.tar. Odin indicates success, but after that, if I try to get into recovery mode to use TWRP (volup+home+power), I get a blue "Installing system update" screen, then a "No Command" screen. It then drops into the stock Samsung recovery screen (zerofltespr7.0/NRD90M/G920PVPS4DRC2) instead of TWRP.

Did I miss a step? I saw something about the stock boot writing over TWRP, but the sequence of operations to avoid it did not make sense to me.
[Galaxy S6 Q&A, Help & Troubleshooting] fovea1959:
Found the missing step in

Needed to uncheck Autoreboot, then VOLUP+VOLDOWN+MENU+POWER.