Fix to Get Rid of the MMS Notification in your Call Logs
Apologies about the brief post earlier today, was at work and a bit of a hurry. Here is a more detailed method.
This was created from the JS5, i9000 source, but has been confirmed to also work on JS7 and KB1.
This will not remove exisiting notifications, but will stop new ones from popping up.
I do not take credit for the original fix, my source is listed below.
Clockwork Flashable zip file below to apply this fix, the steps are listed because I was asked for the process, but if you just want the mod, just flash the file at the bottom of this post.
This assumes you have knowledge of apkmanager or apktool to decompile the apk's, and notepad++ or another way to compare and edit the smali's. Those are lessons for another thread.
I happened upon this thread this morning over in Vibrant Q&A: http://xdaforums.com/showthread.php?t=988929
Which led me here: http://xdaforums.com/showthread.php?t=853177 (Go Hit mammon88's thanks button)
-Grab the LogsProvider.apk from the Epic thread, second one linked, and decompiled using apkmanager.
-Move that file somewhere else, maybe even rename the folder, you won't need it again, and it will be the example folder/files.
-Take the LogsProvider.apk from your rom, and decompile with apkmanager or similar program.
-Inside the decompiled apk, using the one in the apkmanager folder here, not the Example Folder, browse to \smali\com\sec\android\provider\logsprovider, and open the LogsProvider.smali with notepad++ (that what I recommend using)
-Now from you Example Folder, drag the corresponding smali file to notepad++, and it will be in a new tab.
-In notepad++, hit Plugins->Compare->Compare, and the differences in the files are highlighted.
-Recreate the edits in the example to your main file, and save.
-Recompile the apk being sure to delete the classes.dex in the process.
These steps may/will work for comparing and editing other files, but be cautious. I didn't go in blindly and say "Eureka" on the first differences I saw. I compared every smali and xml, being cautious in editing, and got lucky on my first shot. Thankfully this apk only has a handful of smali files, first one I've ever decompiled that had less than 40. If you follow my steps, don't hold me responsible if it doesn't work, especially if you failed to make a backup.
The zip below is flashable via Clockwork Recovery. Backup as always, cause hey, it happens.
Apologies about the brief post earlier today, was at work and a bit of a hurry. Here is a more detailed method.
This was created from the JS5, i9000 source, but has been confirmed to also work on JS7 and KB1.
This will not remove exisiting notifications, but will stop new ones from popping up.
I do not take credit for the original fix, my source is listed below.
Clockwork Flashable zip file below to apply this fix, the steps are listed because I was asked for the process, but if you just want the mod, just flash the file at the bottom of this post.
This assumes you have knowledge of apkmanager or apktool to decompile the apk's, and notepad++ or another way to compare and edit the smali's. Those are lessons for another thread.
I happened upon this thread this morning over in Vibrant Q&A: http://xdaforums.com/showthread.php?t=988929
Which led me here: http://xdaforums.com/showthread.php?t=853177 (Go Hit mammon88's thanks button)
-Grab the LogsProvider.apk from the Epic thread, second one linked, and decompiled using apkmanager.
-Move that file somewhere else, maybe even rename the folder, you won't need it again, and it will be the example folder/files.
-Take the LogsProvider.apk from your rom, and decompile with apkmanager or similar program.
-Inside the decompiled apk, using the one in the apkmanager folder here, not the Example Folder, browse to \smali\com\sec\android\provider\logsprovider, and open the LogsProvider.smali with notepad++ (that what I recommend using)
-Now from you Example Folder, drag the corresponding smali file to notepad++, and it will be in a new tab.
-In notepad++, hit Plugins->Compare->Compare, and the differences in the files are highlighted.
-Recreate the edits in the example to your main file, and save.
-Recompile the apk being sure to delete the classes.dex in the process.
These steps may/will work for comparing and editing other files, but be cautious. I didn't go in blindly and say "Eureka" on the first differences I saw. I compared every smali and xml, being cautious in editing, and got lucky on my first shot. Thankfully this apk only has a handful of smali files, first one I've ever decompiled that had less than 40. If you follow my steps, don't hold me responsible if it doesn't work, especially if you failed to make a backup.
The zip below is flashable via Clockwork Recovery. Backup as always, cause hey, it happens.
Last edited:
