我正在开发一个应用程序,当我卸载了手机那种半重新启动。
这是我以前的帖子:
我有一个奇怪的问题,我的电话。我使用三星GALAXY 5 (GT-I5500)采用Android 2.2就可以了(不是植根)。
我是一个Android开发人员,我一直在做pretty的先进的应用程序。 但是,有时,当我测试和安装应用程序 手机重新启动。
我开始它槽的Eclipse,但我不知道究竟是什么 导致重新启动手机。
这是不热是肯定的,因为我把我的手机足够凉。
这是不是从应用程序源本身的电话,而我使用的应用程序不会重新启动,但是,安装时间
这是不存储的我觉得,因为我有26 MB的内部和1GB外部存储器的分类和应用程序不超过2 MB。
所以我的问题是什么可能导致手机重启?
在这方面,我定义重启的手机显示初始三星屏,像正常启动,但没有提示输入密码。这就是为什么我断定它是像半重启或我并不确切地知道。
解决方案在经历了同样的问题,我发现,删除的Dalvik缓存和格式缓存分区帮助 - 我无法分辨这两者之一的伎俩,但现在我可以高兴地再次卸载应用程序,无需设备重启自发。 这两种操作我能够在恢复模式下进行,使用ClockWorkMod救援体系,他们都是非破坏性的。没有实际的数据或应用程序丢失,只有下次重新启动需要更长的时间,因为Dalvik的缓存被重建。
今天,近一个月后,这个问题再次表明了,所以我能测试,其中这两个行动修复它。原来它删除缓存。 Dalvik的缓存被单独留在家中,删除了可能沿袭不过。
![android手机强制重启](https://p.xsw88.cn/allimgs/daicuo/20230906/2131.png)
I am developing an app and when I uninstall the phone kind of semi-reboots.
This is my old post:
I have a strange problem with my phone. I am using SAMSUNG GALAXY 5 (GT-I5500) with Android 2.2 on it (not rooted).
I am an android developer and I have been doing pretty advanced apps. However, sometimes when I am testing and installing an application the phone reboots.
I'm starting it trough Eclipse but I do not know what exactly what causes the phone to reboot.
It is not heat for sure, as I keep my phone cool enough.
It is not from the app source itself as the phone doesn't reboot while I am using the application but on installing time
It is not storage I think, because I have 26 MB internal and 1GB external memory free and the app is no more than 2 MB.
So my question is what could cause the phone to reboot?
In this context I define "reboot" as the phone showing the initial SAMSUNG screen, like normal booting but without the prompt for PIN. This is why I conclude it is something like semi-reboot or I do not exactly know.
解决方案
Having experienced the same problem, I found that deleting dalvik cache and formatting cache partition helped - I can't tell which one of those two did the trick, but I can now happily uninstall apps again, without the device spontaneously rebooting. Both operations I was able to perform in recovery mode, using ClockWorkMod rescue system, and they are non-destructive. No actual data or apps are lost, only next reboot takes longer, due to dalvik cache being rebuilt.
Today, close to a month later, that problem showed again, so I was able to test which of those two action fixes it. Turns out it was erasing the cache. Dalvik cache was left alone, deletion was possible afterwars nevertheless.
相关推荐
最新文章