endoflife.date icon indicating copy to clipboard operation
endoflife.date copied to clipboard

Published 20 hours ago • verified publisher icon endoflife-date

Add device model code for Samsung devices

Open PGRITS opened this issue 2 years ago • 4 comments

I would like to have one more field on Samsung devices that contains the device model code for the device. Sadly there are sometimes more than one code for a device model like for the S10. https://techbeasts.com/list-of-samsung-galaxy-s10-model-numbers-and-differences/

It would be useful to have this information because for example Intune collects hardware information on devices and creates an inventory. Sadly in the informations only this device model code is included. So when we are trying to get information about the support status of a device we have to resolve the device model code to a model name and then use that name to search for the support status.

PGRITS avatar Mar 09 '22 10:03 PGRITS

Thanks for opening your first issue here! Be sure to follow the issue template!

welcome[bot] avatar Mar 09 '22 10:03 welcome[bot]

Is there actually a difference in the support cycle depending on the code?

I could see carriers supporting their carrier branded devices for shorter amounts, but to keep track of this would be a nightmare. Maybe more appropriately we can add a disclaimer at the bottom about this?

Evernow avatar Mar 18 '22 03:03 Evernow

I'm facing the same issue in the iPhone page, where some iPhone models have different model codes. iPhone 13 Pro Max is A2484 A2641 A2644 A2645 A2643 for eg.

I wanted to use the model codes for the API, but unsure how to keep it accessible. In my case, there's no difference in support cycle, but it would allow some interesting use-cases via the API (get model code, validate over API).

captn3m0 avatar Mar 20 '22 05:03 captn3m0

Is there actually a difference in the support cycle depending on the code?

I could see carriers supporting their carrier branded devices for shorter amounts, but to keep track of this would be a nightmare. Maybe more appropriately we can add a disclaimer at the bottom about this?

I do not think there is a difference in this. It just would be pleasant to be able to use the code from a data source like EMM system and query this against the database. This way not only the base models would be resolved.

It is not about anything just about to be able to resolve the code via API to device and corresponding support status.

PGRITS avatar Mar 21 '22 13:03 PGRITS