Moto E2 SMS latency Solution

E2 has been used for two months. Since January August, there has been a serious SMS delay on my mobile phone. Generally, the latency is 4 ~ In about five hours, the more serious case is that delayed text messages will be repeatedly received many times. The delay has been a headache. It is so annoying to receive the delayed text message again!

I have studied the solutions of experts online, and I have gained some practical results.

The text message delay has nothing to do with the version or the original version. The reason may be that you have used too many custom scripts, fonts, themes, boot diagrams, boot animations, and boot ringtones, the loading of the text message file fails. Many people do not feel the text message delay because the text message has been sent after the startup or has not been shut down for a long time. The text message file has been running normally. If you have not received the text message after the reboot, you will find the text message delay.

The method to determine whether your E2 will have a delay is: re-boot, wait about 20 seconds, enter the text message, if you can enter once, there will be no text message delay, if one cannot enter, if you try again, there will be SMS latency. However, as long as you have entered the SMS operation interface, there will be no latency before shutdown, because the SMS file has been loaded.

Practice has found that my mobile phone does have this phenomenon, and the delay should also be reasonable. The solution is as follows:

Asmotoe2 has released several versions of scripts to solve text message latency. The third version of the script seems to be quite good.

First version:

#! /Bin/bash
If PS-Ef | grep messaging
Then
Kill $ (pidof messaging)
Echo "already">/MMC/mmca1/messaging.txt
Sleep 5S
Kill $ (pidof messaging)
Else
Echo "Starting MSG...">/MMC/mmca1/messaging.txt
./Home/native/. Profile
/Usr/sysqtapp/messaging &
Fi

With this script, the boot speed will be slowed down by 5 seconds.

Of course, this is the echo "already">/MMC/mmca1/messaging.txt that can be modified.
Sleep 5S 5s stands for 5 seconds! However, we have not tested any other products! If you are interested, test it on your own! At least 2 seconds are recommended!

If you do not want debugging information
Delete the echo row.

The debugging information only shows the information service enabled in which way.
If it is already running, messaging will be killed.
The system automatically calls the message again, which means that messaging is restarted twice.

But two retries will cause a problem at 13th times!

Because twice, when 13th reboots, you cannot enter the text message again!

Therefore, if you are afraid of two unreliable start times, if you are afraid of two unreliable start times,
You can add more
Sleep 5S
Kill $ (pidof messaging)

Version 2:

#! /Bin/bash
If PS-Ef | grep messaging
Then
Kill $ (pidof messaging)
# Echo "already">/MMC/mmca1/messaging.txt
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Else
Echo "Starting MSG...">/MMC/mmca1/messaging.txt
./Home/native/. Profile
/Usr/sysqtapp/messaging &
Fi

Third Edition:

#! /Bin/bash
If PS-Ef | grep messaging
Then
Kill $ (pidof messaging)
# Echo "already">/MMC/mmca1/messaging.txt
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof brwdaemon)
/Usr/sysqtapp/Opera/brwdaemon &
Else
Echo "Starting MSG...">/MMC/mmca1/messaging.txt
./Home/native/. Profile
#/Usr/sysqtapp/messaging &
/Usr/sysqtapp/Opera/brwdaemon-WebAccess &
Fi

Version 4:

#! /Bin/bash
If PS-Ef | grep messaging
Then
Kill $ (pidof messaging)
# Echo "already">/MMC/mmca1/messaging.txt
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof messaging)
Sleep 2 S
Kill $ (pidof brwdaemon)
/Usr/sysqtapp/Opera/brwdaemon-wap-Push &
Else
Echo "Starting MSG...">/MMC/mmca1/messaging.txt
./Home/native/. Profile
#/Usr/sysqtapp/messaging &
/Usr/sysqtapp/Opera/brwdaemon-WebAccess &
Fi

Usage:Use ultraedit and other editing software to create a TXT file (such as startup.txt), copy and paste the version field to be used into the TXT file, and save it, upload the file to the "unrecognized file" folder on the mobile phone.

Previously, I used the 3D 46p anti-delay patch (the mobile phone version is 3D 48p-2nd), and the USB interface was unavailable (I could not connect to the computer or charge, !). First, delete the startup.txt file, then shut down, and unplug the SD file without a memory card to start the mobile phone. Everything is normal, then shut down, insert the SD card, and start the mobile phone. Everything is normal, and the text message delay also disappears. Somehow, haha

Reprinted from: http://hi.baidu.com/6light Thank you author...