# Android 更新日志

## 4.0.0 

### new:

策略重构：所有事件优先入DB，减少事件丢失率。DB中的事件会在轮询中上报 完善多通道下的LogID统计，更准确的统计上报率 初始化方法、上报方法耗时优化等 更灵活的接口设计

## 3.2.0.4

### Fixed

* 修复多线程初始化SDK问题

## 3.2.0.1

### Fixed

* 修复UserAction中集合线程同步的问题

## 3.2.0

### Added

* 新增`setOmgId()` 方法，若业务方有接入Omgid可自行设置。
* 增强Android Q环境下Qimei稳定性

### Fixed

* 修改Qimei存储逻辑

## 3.1.2

### Added

* 支持多道通上报，具体请查看：[多道通上报](broken://pages/-LeVjWcfk-nd89nBhL6E)

### Fixed

* 优化了非实时事件上报。进一步降低丢失率
* 修复SDK自行生成Qimei的问题。

  * 在旧版本中，SDK还没获取到服务端返回的Qimei之前，会本地生成一个，这会导致与服务端生成的不一致。因此在新版中，我们移除了本地生成逻辑。
  * 调用getQimei()的时机建议放到onStrategyQuerySuccess里

  ```
  UserAction.initUserAction(this, isMainProcess(this), 0, new InitHandleListener() {
      @Override
      public void onInitEnd() {
          //sdk初始化完成
          Log.i("beacon", "on sdk initEnd");
      }

      @Override
      public void onStrategyQuerySuccess() {
          //sdk更新策略完成，在这里获取Qimei
          Log.i("beacon", "on sdk onStrategyQuerySuccess");
      }
  }, null);
  ```

  �

  * 即使如此，调用getQimei()接口仍可能返回空，请注意适配
  * 移除64位so
    * officail不再包含64位so（因为大部分产品只有32位进程，这样可以减少包体）
    * official64包含32位和64的so
    * 需要适合64位系统的请使用official64

## 3.0.0 

### Added

* 支持Gradle/Maven

### Fixed

* 修复多个crash以及上报问题


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://beacon-help.gitbook.io/beacon-help/sdk-wen-dang/sdkji-cheng-zhi-nan/android-geng-xin-ri-zhi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.