> For the complete documentation index, see [llms.txt](https://portal-integracao.intelbras.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portal-integracao.intelbras.com.br/linha-android/proxyserver/lamydevicesinfo.md).

# LamyDevicesInfo

LamyDevicesInfo fornece informações como número de série do dispositivo, modelo do dispositivo e versão

```java
/**
*Obtain device model
*
*@ return string null is returned after failed acquisition
*/
public String getDeviceModel();
/**
* Get the software version number of the device.
*
*@ return string null is returned after failed acquisition
*/
public String getDeviceSWVersion();
/**
* Obtain the Device Serial Number
*
*@ return string null is returned after failed acquisition
*/
public String getDeviceSerial();
/**
*Obtain Android version number
*
**@ return Android version number, returned null if acquisition failed
*/
public String getAndroidVersion();
/**
* Obtain system version compilation time
*
*@ return utc time, returned 0 if acquisition failed
*/
public long getBuildTime();
/**
*Obtain internal software version number
*
* @return returned null if acquisition failed
*/
public String getDeviceInternalModel();
/**
*Returnthe system IMEI string
*@ return string null is returned after failed acquisition
*/
public String getDeviceIMEI();

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://portal-integracao.intelbras.com.br/linha-android/proxyserver/lamydevicesinfo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.