Android 应用程序(Samsung Galaxy Tab,2.2)*有时*不会写入数据库
我们有一个在 Samsung Galaxy Tab 上运行 Android 2.2 的 Android 应用程序,该应用程序将数据写入 SQLite DB。
但是,我们发现某些平板电脑会出现以下间歇性问题。
- 数据被写入DB。 (没有抛出 SQLiteException;我们正在提交事务)。
- 但数据库实际上并不包含数据。
卸载并重新安装应用程序或清除应用程序的数据似乎根本没有任何区别。
然后,当我们将手机恢复出厂设置并重复相同的过程时,它就可以正常工作了。这个问题并不局限于给定的一块;我们开发团队中的所有人都间歇性地遇到过这种情况。
但是,我无法在任何 Android 手机(我在 HTC Desire、HTC Desire HD 和 Samsung Galaxy S 上尝试过,它们都运行 Android 2.2)或模拟器(运行 Galaxy tab add -在)。
我怀疑这可能与三星在入侵 Android 2.2 时引入的错误有关。我想知道其他人是否遇到过这个问题,如果是的话,你们知道有什么比恢复出厂设置更严厉的措施吗?
谢谢,
西杜
We have an Android application running on Android 2.2 on the Samsung Galaxy Tab that writes data into the SQLite DB.
However, we find the following intermittent problem arising on some tablets.
- The data is written into the DB. (No SQLiteExceptions being thrown; we are committing the transaction).
- But the DB does not actually contain the data.
Uninstalling and reinstalling the application or clearing the application's data does not appear to make any difference at all.
When we then factory reset the handset and repeat the same procedure, it works just fine. This problem is not restricted to a given piece; all of us in my dev team have come across this intermittently.
However, I have not been able to reproduce the problem on any Android handsets (I tried on the HTC Desire, the HTC Desire HD, and the Samsung Galaxy S, all running Android 2.2), or on the emulator (running the Galaxy tab add-on).
I have a suspicion this may have something to do with a bug introduced by Samsung when they hacked Android 2.2. I was wondering if anybody else had encountered this problem, and if so, do you guys know of any less drastic measure than factory resetting the tablet?
Thanks,
Siddhu
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
有报道称三星的设置行为不当(不保存它们)。请参阅此 Google 问题。设置也保存在数据库中。所以我猜你的问题是相关的,即使不完全相同。
谷歌搜索
以供更多点击。
我们在三星的应用程序中也遇到了类似的问题。找不到三星的官方声明,因此最终向用户记录了这种情况可能会发生在三星设备上。
There are reports out there about Samsung misbehaving with Settings (not saving them). See this Google issue. The settings are also saved in the database. So my guess your issue is related, if not exactly the same.
Google for
for more hits.
We faced similar issues with our app in Samsung. Couldn't find an official statement from Samsung, so in the end documented to the users that this could happen in Samsung devices.