Pixel device cluster topology error
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 409
- PR merge metrics
- No merged PRs in 30d
Description
cpuinfo detects all cores as ARM Cortex-A520
SoC name: Unknown
Microarchitectures:
8x Cortex-A520
Cores:
0: 1 processor (0), ARM Cortex-A520
1: 1 processor (1), ARM Cortex-A520
2: 1 processor (2), ARM Cortex-A520
3: 1 processor (3), ARM Cortex-A520
4: 1 processor (4), ARM Cortex-A520
5: 1 processor (5), ARM Cortex-A520
6: 1 processor (6), ARM Cortex-A520
7: 1 processor (7), ARM Cortex-A520
Clusters:
0: 8 processors (0-7), 0: 8 cores (0-7), ARM Cortex-A520
Logical processors (System ID):
0 (0)
1 (1)
2 (2)
3 (3)
4 (4)
5 (5)
6 (6)
7 (7)
Specs from gsmarena:
Pixel 9
Android 14, upgradable to Android 15
Google Tensor G4 (4 nm)
Octa-core (1x3.1 GHz Cortex-X4 & 3x2.6 GHz Cortex-A720 & 4x1.92 GHz Cortex-A520)
Pixel 10
Android 15
Google Tensor G5 (4 nm)
Octa-core (1x3.1 GHz Cortex-X4 & 3x2.6 GHz Cortex-A720 & 4x1.92 GHz Cortex-A520)
The issue was introduced in Dec 2024 Android 15 update, affecting all Pixel devices that run Android 15
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the cpuinfo output on an affected Pixel device running Android 15 and trace the ARM CPU topology detection entry point. Compare the reported clusters and microarchitectures with the Pixel specifications in the issue; done means the affected devices no longer report all cores as Cortex-A520.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100