我现在，然后使用在设备的每个启动时写入自动启动的应用程序。这很烦人，因为我不使用它。我怎么能阻止它？
我知道有一个"autorun manager" 应用程序，但它需要一个rooted手机。有没有办法在非生根设备上执行此操作？
I now and then use an app that is written to autostart on every boot of the device. This is pretty annoying since I don't use it that much. How can I stop it ?
I know there is an "Autorun Manager" app, but it requires a rooted phone. Is there a way to do this on a non-rooted device ?
如何建立如何建立它。虽然，如您所知，大多数非常好的解决方案都需要您的设备植根，即使没有root，也有一些方法工作：
autorun manager 您已经提到过 - 到我的经验，这是该领域最好的应用程序。此应用程序还提供了一种非根模式，您可能需要尝试。但与非根模式中的其他应用程序一样，它只能在他们开始后杀死应用程序 - 虽然在扎根模式下，它可以禁用相应的"侦听器" ，从而保持应用程序始终开始。即使远离杀死，那些应用程序中的许多应用程序即使再次重新启动（由ARM检测到），那么该应用程序然后单独避免杀戮启动终止循环）。此外，它们只能处理 boot_completed 事件 - 但有些应用程序（例如，例如谷歌地图）从这么多不同的场合开始（网络已更改，SDCard安装......） - 再次在哪里root-mode中的版本可以处理，但非根模式不能。
如果您有Android 4.0或更高版本，则可能存在另一个有用的"工作" - 至少如果它是一个很少使用的应用程序：转到设置→应用程序→管理应用滚动到所讨论的应用程序，点击一次，然后点击"禁用" 按钮。应用程序已经消失（已禁用），然后不再在App抽屉中显示 - 并且不再自动或手动启动，以及系统它是"不存在的" 。如果稍后再需要它，请转到同一个地方，滚动到列表的最终（啊！有禁用的应用程序已经去...），再次点击它，然后点击"启用" 按钮 - 返回它是！
因为这是一种相当复杂的方式，它可能对您每天需要的应用程序可能是不可行的。但如果它是一个应用程序，你不需要一个月，它可能值得努力。
一些相关问题进入细节，其中许多包括仅对植根设备相关的东西。但是，在这种情况下，它们可能值得读取，因此我在此处包含他们的链接：
There are several ways how you could establish that. Though, as you discovered, most really good solutions require your device to be rooted, there are some methods working even without root:
Autorun Manager you've already mentioned -- to my experience, this is the best app in this area. This app also offers a non-root mode you might want to give a try. But like other apps in non-root mode, it can only kill apps after they've started -- while in rooted mode, it can disable the corresponding "Listeners" and thus keeping the app from being started at all. Even if killed right away, many of those apps simply re-start again (which is detected by ARM, and that app then left alone to avoid a kill-start-kill cycle). Moreover, they can only handle the boot_completed event -- but some apps (like e.g. Google Maps) start on so many different occasions (network changed, sdcard mounted...) -- where again the Pro-Version in root-mode can deal with, but the non-root mode can't.
If you've got Android 4.0 or higher, there might be another useful "work-around" -- at least if it's a rarely used app: Go to Settingsxe2x86x92Appsxe2x86x92Manage Apps, scroll to the app in question, tap it once, and then tap the "Disable" button. App is gone (disabled) then, no longer shown in the app drawer -- and no longer started automatically or manually, as to the system it is "non existent". If you need it again later, go to the very same place, scroll to the very end of the list (Ah! there the disabled apps have gone to...), tap it again, and tap the "Enable" button -- back it is!
As this is a rather complicated way, it's probably not feasable for apps you need on a daily basis. But if it's an app you need no more often than once a month, it might be worth the effort.
Some related questions go deeper into details, many of them including stuff only relevant for rooted devices. However, they might be worth reading in this context, so I include their links with my answer here:
© 2022 it.wenda123.org All Rights Reserved. 问答之家 版权所有