Android OS Forum banner
1 - 3 of 3 Posts

·
Carbon-Based Robotic Tech Machine
Joined
·
2,243 Posts
Chris3D said:
From what I've read, while this will stop the OTA from installing, it does so by making the downloaded update fail the cert check. This can apparently lead to the OTA being repeatedly downloaded over and over. Download, fail check, download, fail check...

I believe the actual update process is com.smithmicro, which is contained in the DmClient.apk file. The process can be frozen with Titanium, or prevented from starting by renaming or deleting DmClient.apk in /system/app using Root Explorer. This will ensure the OTA is never even downloaded in the first place.
That is correct. I would also recommend the otacerts.zip renaming as well since that should prevent it from installing should it download anyway or is already downloaded.
 

·
Carbon-Based Robotic Tech Machine
Joined
·
2,243 Posts
linuxmotion said:
The correct fix is to have the build.prop the same as the latest ota. Hmm think about it. If the phone thinks its at the latest ota already why would it download the update. Think about it. This is the fix.

Renaming or removing the oatcerts will cause excessive battery use. Fix the build.prop

Sent from my Incredible using Tapatalk
Agreed that the build.prop mod should prevent the update as well, but editing the build.prop version info can cause market issues and is a lot more involved for beginners and is more dangerous. As for otacerts.zip causing battery issues, I agreed on that part. Renaming the otacerts.zip will not cause battery issues if you rename it IN ADDITION to renaming the smithmicro download manager because it won't be able to download the update anyway. The reason for renaming both is so it doesn't download and so if it has already downloaded, it will not install.
 

·
Carbon-Based Robotic Tech Machine
Joined
·
2,243 Posts
linuxmotion said:
Really this should not even be left to the user. The rom developer should resolve this issue. I think that this users should kindly ask the developer to fix that issue. As for smithmicro that is good to know.

Though i don't have an inc2 this was a problem for us as well on the inc1. I hope the OP got the problem resolved

Sent from my Incredible using Tapatalk
Agreed that the ROM devs should have fixed that before release, but I don't think that all the devs knew and/or know what the smith micro dm does. I don't hold it against them since we are not buying the roms. If they were for sale, I would expect it though. As for the dev making the build.prop correct, when it was released, it likely was correct. Many of these ROMs are not updated frequently, if at all, so if that is all they did to block it, then the next release would require it to be updated again. Without the DM there it won't matter what the current version is. +$.02
 
1 - 3 of 3 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top