Android phone code names

Android Phone Codenames

The objective of this project is to vet the best officially supported LineageOS phones by using the most popular phones currently used according to the LineageOS Stats.

I had a lot of trouble finding a relation between code names and phone brand and model. After trawling the web for a bit, I found Google has a supported_devices.csv file for their Google Play support which contains the data I want. This data doesn’t completely fit the LineageOS data so I had to correct some of it by researching and adding my own corrections.

After collecting that data, I then hit the fonoapi to expand each phone’s fields which gave me an additional 60 records. Some data is incomplete but still very useful. Going forward, I need to also collect cost for each phone to find budget phones. I’d also like to do a 3D bubble graph of a phone’s price (z) vs specs score (y) vs release date (x).

Google Play supported devices
LineageOS Stats
Fono API
Manual research

Update google api supported devices, convert to utf8, and remove BOM

The file missing_devices.csv was built manually and the rest are automatic.

Follow the steps in this tutorial and you should have your own sheet with permission set to the email in your client_secret.json

Get fono api key and place it in a .envrc file to load the env variable using direnv or export FONO_API manually

Create pip environment and install dependencies

Remove old data (optional)

You should now see data in your Google Spreadsheet

DONE — scrape lineageos stats
DONE — find and scrape trove of code names from google data
DONE — find and scape trove of code names from lineage data
DONE — insert all device info into devices table
DONE — hit fono api
DONE — combine lineageos stats with google data
DONE — combine new data with fono data
DONE — upsert a google spreadsheet
DONE — move cached data to data/ directory
DONE — get devices that don’t have any data
Add a new missing_devices_fono.csv for devices like the Xiaomi Pocophone F1 that do not exist in the fono API but info does exist publicly
- This is where we can add manual data from gsmarena or another source
Scrape lineageos download page to get versions
- [. document.querySelectorAll(‘table.striped.bordered tr td:nth-child(2)’)].map((val) => val.innerText)
- also get if this version is officially supported or not. might be able to tell if it’s missing from search.json .
- include links to supported devices
- include links for unsupported devices
Scrape ifixit for fixit scores
Create separate Python SDK similar to jaredrummler/AndroidDeviceNames
Get average or min/max cost metrics per phone. If new is unavailable, find used.
- Amazon, Craigslist, FB Marketplace, Ebay

DONE — get the top 100 lineageos phones instead of only 10
- FIXED — getting 429 quota exceeded for quota group ‘WriteGroup’. Now writes to google sheets in a single batched command.
redownload files if last scrape is more than 7 days ago
- save all files with a timestamp
find a way to improve match rates. Roughly 50 to 70% right now.
- once improved, go from top 100 to top 200 and keep iterating
audit matches to see if they are correct

strip out android_x86 as it may be an android virtual machine
save data to database file instead of memory
- why? what does a db even buy us?
- create better db schema
  - devices table
  - stats table
  - fono api table
  - create_at timestamp from when data was retrieved
prefix comma delimited sources of data

About

Map of phone code names to actual names combined with lineageos data

Источник

nitrocode / phone-code-names Go PK Goto Github PK

Map of phone code names to actual names combined with lineageos data

phone-code-names’s Introduction

Android Phone Codenames

The objective of this project is to vet the best officially supported LineageOS phones by using the most popular phones currently used according to the LineageOS Stats.

Google Play supported devices
LineageOS Stats
Fono API
Manual research

Update google api supported devices, convert to utf8, and remove BOM

The file missing_devices.csv was built manually and the rest are automatic.

Follow the steps in this tutorial and you should have your own sheet with permission set to the email in your client_secret.json

Get fono api key and place it in a .envrc file to load the env variable using direnv or export FONO_API manually

Create pip environment and install dependencies

Remove old data (optional)

You should now see data in your Google Spreadsheet

DONE — scrape lineageos stats
DONE — find and scrape trove of code names from google data
DONE — find and scape trove of code names from lineage data
DONE — insert all device info into devices table
DONE — hit fono api
DONE — combine lineageos stats with google data
DONE — combine new data with fono data
DONE — upsert a google spreadsheet
DONE — move cached data to data/ directory
DONE — get devices that don’t have any data
Add a new missing_devices_fono.csv for devices like the Xiaomi Pocophone F1 that do not exist in the fono API but info does exist publicly
- This is where we can add manual data from gsmarena or another source
Scrape lineageos download page to get versions
- [. document.querySelectorAll(‘table.striped.bordered tr td:nth-child(2)’)].map((val) => val.innerText)
- also get if this version is officially supported or not. might be able to tell if it’s missing from search.json .
- include links to supported devices
- include links for unsupported devices
Scrape ifixit for fixit scores
Create separate Python SDK similar to jaredrummler/AndroidDeviceNames
Get average or min/max cost metrics per phone. If new is unavailable, find used.
- Amazon, Craigslist, FB Marketplace, Ebay

DONE — get the top 100 lineageos phones instead of only 10
- FIXED — getting 429 quota exceeded for quota group ‘WriteGroup’. Now writes to google sheets in a single batched command.
redownload files if last scrape is more than 7 days ago
- save all files with a timestamp
find a way to improve match rates. Roughly 50 to 70% right now.
- once improved, go from top 100 to top 200 and keep iterating
audit matches to see if they are correct

strip out android_x86 as it may be an android virtual machine
save data to database file instead of memory
- why? what does a db even buy us?
- create better db schema
  - devices table
  - stats table
  - fono api table
  - create_at timestamp from when data was retrieved
prefix comma delimited sources of data

Источник

Android Hidden Codes: All the custom Dialer Codes and What they do!

The Android operating system is well known for its hidden features and easter eggs. One such area is using custom dialer codes to access various hidden apps and settings. Some of these codes are universal, which means you’ll get the desired output on any Android device, irrespective of them being a great flagship or a cheap budget phone. However, custom OEM skins (e.g. One UI by Samsung and MIUI by Xiaomi) and carrier-customized models often come with their own set of hidden codes.

Below you can find a bunch of generic as well as device-specific Android hidden codes. Give them a try and discover some of the handiest secret functionalities of your phone. If you donвЂ™t see your device listed or you want to submit a new code, send a message to Skanda Hazarika (SkandaH on the forums) with all the relevant details.

Table of Contents:

Structure of the Android hidden codes

The so-called hidden codes are basically part of the Man Machine Interface (MMI) schema. These are a bit different from the Unstructured Supplementary Service Data (USSD) codes, although both of them start with an asterisk (*) followed by digits that comprise of commands or data. Groups of digits may be separated by additional asterisks. The message is terminated with a hash symbol (#), but custom MMI codes may end with an asterisk as well.

While USSD codes are used to communicate with the mobile network operator’s servers for menu-based information services, mobile-money services, and location-based content services, the MMI Supplementary Service codes work completely offline.

Just like USSD, you have to dial the “hidden” codes on the stock dialer app to invoke the corresponding action.

Generic hidden codes

*#07#
Displays the Specific Absorption Rate (SAR) value of the device.

*#*#225#*#*
Displays calendar storage information.

*#*#426#*#*
Displays the Firebase Cloud Messaging (FCM) diagnostics page or information related to Google Play Services.

*#*#759#*#*
Displays the RLZ Debug UI with Unique Device ID and other data related to application installation. It’s also possible to turn on (and off) OEM mode through this interface.

*#*#4636#*#*
Displays information about the phone, battery, and various network statistics.

Special hidden codes for popular Android brands

The generic codes should work on every Android device out there. In case you’re looking for OEM-specific codes, take a look at the following index.

*#07#
Displays the regulatory labels.
.12345+= (must be entered in the stock calculator app)
Opens the engineering mode.

Google

Google Pixel devices run an enhanced version of vanilla Android, which means you’re limited to the generic codes mentioned above.

Motorola

*#*#2486#*#*
Opens up the engineering mode. You may need to boot through the “BP Tools” section in the fastboot interface at least once before trying this code.
*#07#
Displays the regulatory information.

Nokia

*#*#372733#*#*
Opens up the service mode (also known as the FQC menu).

OnePlus

1+= (must be entered in the stock calculator app)
Displays the company’s motto – “Never Settle” – on the calculator app.

*#66#
Displays the IMEI and MEID in an encrypted format

*#888#
Displays the PCB version of the motherboard of the phone.

*#1234#
Displays the software version.

*#*#2947322243#*#*
Wipes out the internal memory (use with caution!).

Realme

*#800#
Opens up the factory mode/feedback menu.

*#888#
Displays the PCB version of the motherboard of the phone.

*#6776#
Displays the software version and additional details.

Samsung

*#0*#
Opens up the hardware diagnostic menu.

*#011#
Displays network connection and serving cell related information.
*#0228#
Displays battery status.

*#0283#
Opens up the packet loopback settings.

*#1234#
Displays the software version and additional details.

*#2663#
Displays advanced firmware version menu.

*#7353#
Displays the quick test menu.
*#9090#
Displays advanced debugging tools.

*#9900#
Opens up system dump mode.

*#2683662#
Displays advanced service mode.

*#34971539#
Displays advanced camera firmware information.

*#*#73788423#*#*
Displays the service menu.
*#07#
Displays certifications details.

Xiaomi

*#*#64663#*#*
Displays the hardware diagnostic menu (also known as the QC test menu).

We hope this guide will get you in and out of hidden menus within Android. WeвЂ™ll be updating this guide with more such codes for specific phones, so check back again in the future.

XDA В» Tutorials В» Android Hidden Codes: All the custom Dialer Codes and What they do!

Источник