Applocations Refuse To Boot

[VILLO1988]

Hi guys, as you know I love miui I think it's one of the best rom available but I have to open this thread since I'm using this rom from miui7 till miui8 in every single devs. As far as I know I have an huge problems maybe the only defect of the rom.
Some apps refuse to boot. No matter what you do, miui won't start them also, if you open them manually, miui savings battery will close them. A service will appear on miui running and closing your apps.
This not only won't let you receive notifications but also close running apps and consider them in background.
I honestly don't know why this happens, maybe because miui has to save battery, and to be honest not every single app acts the same. In my case for example whatsapp and FB messenger are working great, but telegram is acting differently. Miui kills the app, until you lock it on ram, still you also have to manually start the same telegram when you boot your phone.
I made this example since I don't know if it's miui fault or telegram fault, but anyway I'd like to discuss about it since it's a daily issue.

Inviato dal mio Redmi Note 2 utilizzando Tapatalk

 

[RaulC]

Hi guys, as you know I love miui I think it's one of the best rom available but I have to open this thread since I'm using this rom from miui7 till miui8 in every single devs. As far as I know I have an huge problems maybe the only defect of the rom.
Some apps refuse to boot. No matter what you do, miui won't start them also, if you open them manually, miui savings battery will close them. A service will appear on miui running and closing your apps.
This not only won't let you receive notifications but also close running apps and consider them in background.
I honestly don't know why this happens, maybe because miui has to save battery, and to be honest not every single app acts the same. In my case for example whatsapp and FB messenger are working great, but telegram is acting differently. Miui kills the app, until you lock it on ram, still you also have to manually start the same telegram when you boot your phone.
I made this example since I don't know if it's miui fault or telegram fault, but anyway I'd like to discuss about it since it's a daily issue.

Inviato dal mio Redmi Note 2 utilizzando Tapatalk

Hi,
In my case it only happens if i turn on battery saver in definitions. I use battery saver on schedule, from 00:30 to 07:30. From these time schedule app's wont boot and don't syncronize, so i don't receive any notification.

If i turn off battery saver, everything is ok!

 

[VILLO1988]

Have you enabled those Apps in Security>Permissions>Autostart ?

Yes of course! It's a long list but the service refuses to start.
Here's an example, I tried to boot also with differents programs but with no results, as you can see the receiver is locked for no reason and I can't do anything about it.

Inviato dal mio Redmi Note 2 utilizzando Tapatalk

 

[VILLO1988]

Hi,
In my case it only happens if i turn on battery saver in definitions. I use battery saver on schedule, from 00:30 to 07:30. From these time schedule app's wont boot and don't syncronize, so i don't receive any notification.

If i turn off battery saver, everything is ok!

Battery saver is now freeezed on my phone but still isn't booting.

Inviato dal mio Redmi Note 2 utilizzando Tapatalk

 

[Stefano131270]

Tomorrow i arrive Villo

 

[Stefano131270]

Villo, I can confirm that WhatsApp uses a lot of energy, for the rest I am not fans of social networks, anything will be solved

 

[VILLO1988]

I found a solution that might be helpful in any case. I installed my android tools. This programming can directly change any setup of applications so, you can control how the application is running.. Its very useful. Right now telegram is autobooting... Yay.

@Stefano: Google play services are too expensive too for battery. I found a guide that explains how to reduce impact of those services but still letting works the services. Try myandroidtools maybe you can start trying killing some parts and seeing if whatsapp is still working correctly

Inviato dal mio Redmi Note 2 utilizzando Tapatalk