Possible hacky solution to apps being aggressively killed - Nokia 1 Questions & Answers

I say possible because the possible solution is basically disabling a system app, but this was after disabling other system apps and mucking around with settings, so it might be a combination of apps being disabled, but i dont think so
By the way, i can confirm that twrp from the here https://forum.xda-developers.com/nokia-1/development/unlocking-rooting-nokia-1-stock-rom-t3832230 works, and so does the latest magisk 17.
Twrp
Ive succesfully used the backup/install feature but havent had the courage yet to test the wipe and restore (data,system) feature, although following that ^ guide ^, looks like restore recovery/boot image works, so thats hopefully a good sign
Magisk
Following that guide, use twrp to flash, no major issues with installation.
Note, if you follow that guide and you come to the bit where the stock recovery only shows "no commands", hold press power button + up volume for a sec or two, or at least thats what i read somewhere, read somewhere else to just press these buttons continually on and off, which i did randomly, and eventually the stock recovery options appeared, dont know why this is this way
Anyways, the culprit, assuming im right barring the above reasons was........a system app called EMM or emmupdate (literately the apps name changed on my phone, i remembered it was emmupdate and now, after checking, its changed to emm, thats weird)
I used a root based logcat app
https://f-droid.org/en/packages/com.dp.logcatapp/
to try and see if there was anything to see, using a particular app i could reliably duplicate the issue with (swiping away from recents app would turn off this apps service removing its notification a couple seconds after being cleared from recents, this app being https://play.google.com/store/apps/...ite&pcampaignid=APPU_1_LUahW_D4DonSgAajx4y4Aw
Paused the logcat searched for the app, and saw a reference with this app, showing the emm app and references to "killing"
Solution
My particular solution was this app,(requires root)
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootservicedisabler
(i dont think you can disable this emm app normally like some system apps, check, i could be wrong)
-in my brief researching this area, i saw discussions that you may be able to do this with adb(i dont know for sure, but might be worth looking into it yourselves, if you dont want to root, no guarantees)
The service disabler app lets you disable, well, services, and this emm app had one service attached to it called "MemoryManagerService", so maybe thats what did it, and not the disabling of the app, so i suggest that if you use this app, also disable the service as i did, for the emm app if disabling the app only, did nothing
IMPORTANT- Reboot the phone after, as thats when the change took affect for me
Ive rebooted, slept, and cleared recents and so far, multiple background apps that were continually being killed before, have NOT been killed
Hope this helps, hope it works.........silly that we have to do this

---

Well i did the same thing by analyazing the logcat through adb. What i found was that any app was killed after this so called emmservice in emmapp was run. After this the activity manager simple killed that app.
To check i choose emm app and turned d switch off under background apps in developer options. Also fc emm.apk. but still problem was there.
Ill check your workaround. It sounds more promising.

---

coolboyforeva said:
Well i did the same thing by analyazing the logcat through adb. What i found was that any app was killed after this so called emmservice in emmapp was run. After this the activity manager simple killed that app.
To check i choose emm app and turned d switch off under background apps in developer options. Also fc emm.apk. but still problem was there.
Ill check your workaround. It sounds more promising.
Click to expand...
Click to collapse
If you get the time, let us know if it works, that way anyone else with the same issue who comes across this thread at least has a way to make the phone multitask
An open source alternative to the disable services app, is an app called oandbackup on the fdroid store(like titanium backup), has a feature that lets you disable apps(requires root), aswell as backup/restore apps and their data, its very good
I just tried looking for a non root solution, but it seems that adb solution i briefly saw earlier also needs root
Besides that, like i said in my first post, it could have been the disabling of emmupdate/s service in the disable service app, so if disabling alone doesnt do it, try disabling the service aswell...........i kinda wanna know the least amount of steps to get it fixed, so if disabling did it alone, that would be worth knowing
Gd luck
Spoke to soon, seems like there might be a way to use adb without root to disable system apps https://www.androidpit.com/uninstall-system-apps-without-root, whether it works on oreo i dont know.
The article solution implies the this will uninstall the apps, but apparently, according to a commenter in that article, it deletes a part of the app in a certain place in android that essentially just disables it, if you did a factory reset, the app would return
If it works, at least users wont have to go through the trouble or risk of mistake in flashing twrp/root or any other modifications to fix it, assuming just disabling emm....... works.

---

banderos101 said:
If you get the time, let us know if it works, that way anyone else with the same issue who comes across this thread at least has a way to make the phone multitask
An open source alternative to the disable services app, is an app called oandbackup on the fdroid store(like titanium backup), has a feature that lets you disable apps(requires root), aswell as backup/restore apps and their data, its very good
I just tried looking for a non root solution, but it seems that adb solution i briefly saw earlier also needs root
Besides that, like i said in my first post, it could have been the disabling of emmupdate/s service in the disable service app, so if disabling alone doesnt do it, try disabling the service aswell...........i kinda wanna know the least amount of steps to get it fixed, so if disabling did it alone, that would be worth knowing
Gd luck
Spoke to soon, seems like there might be a way to use adb without root to disable system apps https://www.androidpit.com/uninstall-system-apps-without-root, whether it works on oreo i dont know.
The article solution implies the this will uninstall the apps, but apparently, according to a commenter in that article, it deletes a part of the app in a certain place in android that essentially just disables it, if you did a factory reset, the app would return
If it works, at least users wont have to go through the trouble or risk of mistake in flashing twrp/root or any other modifications to fix it, assuming just disabling emm....... works.
Click to expand...
Click to collapse
I tried. I can confirm the root method works. However, i also did the adb method. The adb too works. Apps are not killed by android now. No need to unlock bootloader, root or twrp. It just executing 2 commands
Code:
adb shell pm clear com.evenwell.emm
adb shell pm uninstall -k --user 0 com.evenwell.emm
And then reboot.
This clears the app data and disables the app for current user.
And, moreover it survives ota updates too. !!
Only thing to keep in mind is that if you factory reset, you have to re execute above 2 adb commands.
So now all sorted. Just a matter of executing 2 commands.

---

coolboyforeva said:
I tried. I can confirm the root method works. However, i also did the adb method. The adb too works. Apps are not killed by android now. No need to unlock bootloader, root or twrp. It just executing 2 commands
Code:
adb shell pm clear com.evenwell.emm
adb shell pm uninstall -k --user 0 com.evenwell.emm
And then reboot.
This clears the app data and disables the app for current user.
And, moreover it survives ota updates too. !!
Only thing to keep in mind is that if you factory reset, you have to re execute above 2 adb commands.
So now all sorted. Just a matter of executing 2 commands.
Click to expand...
Click to collapse
Very nice, now we know a solution
There you go folks, thanks to coolboyforeva's info, work, testing, and confirmation, anyone who comes across this annoying issue now has a non root solution to fix it, two adb commands.............not to bad, not to bad at all
Cheers CBF, for finding the specific adb commands, and the helpful info, hope it was'nt to much of a bother...........doing gods work pal

---

can confirm that the adb method works and can easily multitask now... thanks guys... no force closures of app now.....

---

Any you guys noticing a delay after reboot for your user apps to start, or just me.
Edit: even during operation(comes and goes), example app = Tasker
Edit2: mmmm, i have a suspicion it might be something to do with gaining root from magisk. Magisk has a few settings that changes how this works, so i might mess around with that first and see what happens. Might also just be tasker/oreo incompatibilities, or perhaps conflicting tasks
Probably gonna look into it, ill post here if i find anything, unless someone beats me to the punch, suspect its one of the manufactor's sytem "optimizing" apps..........
Was hoping we'd be swimming in custom roms, seing as our device SEEMS to be treble compatible and so cheap, a nice bloat free working lineage as daily driver..........guess ill have to stream line stock as much as possible until that day hopefully comes

---

banderos101 said:
Any you guys noticing a delay after reboot for your user apps to start, or just me.
Edit: even during operation(comes and goes), example app = Tasker
Edit2: mmmm, i have a suspicion it might be something to do with gaining root from magisk. Magisk has a few settings that changes how this works, so i might mess around with that first and see what happens. Might also just be tasker/oreo incompatibilities, or perhaps conflicting tasks
Probably gonna look into it, ill post here if i find anything, unless someone beats me to the punch, suspect its one of the manufactor's sytem "optimizing" apps..........
Was hoping we'd be swimming in custom roms, seing as our device SEEMS to be treble compatible and so cheap, a nice bloat free working lineage as daily driver..........guess ill have to stream line stock as much as possible until that day hopefully comes
Click to expand...
Click to collapse
Yes there is delay. Bt i think it would be there. Initially when apps were killed u had enough ram to quickly process any app. But now since apps reside, android ram management has to manage. And that delay in app starting maybe coz be hardware. Its a low grade mediatek chipset. I dont expect it to be quick. (Atleast it auto start apps after delay). But yes if you could find some clue to optimize , that would be good.
Meanwhile i am looking for a pie rom. treble rom works on our nokia 1. I flashed phh treble pie gsi. It boots normal. Only thing is you dont get notified of incoming calls, no rings. Outgoing calls work normal though. So it cant be used.
Link for rom : https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
If this issue is resolved we could have a ready pie rom too.

---

coolboyforeva said:
Yes there is delay. Bt i think it would be there. Initially when apps were killed u had enough ram to quickly process any app. But now since apps reside, android ram management has to manage. And that delay in app starting maybe coz be hardware. Its a low grade mediatek chipset. I dont expect it to be quick. (Atleast it auto start apps after delay). But yes if you could find some clue to optimize , that would be good.
Meanwhile i am looking for a pie rom. treble rom works on our nokia 1. I flashed phh treble pie gsi. It boots normal. Only thing is you dont get notified of incoming calls, no rings. Outgoing calls work normal though. So it cant be used.
Link for rom : https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
If this issue is resolved we could have a ready pie rom too.
Click to expand...
Click to collapse
Cheers buddy, nice to know these things, good to know that theres already an initial treble rom.
Gonna wait for incoming call ring support, might give it a couple of months actually, before trying out any rom that might come along, let the bugs get settled if any, assuming were lucky enough to get a maintainer
Edit
Commenting about the slow response time of user apps, normally i'd agree with you on the outdated hardware, but either the rom is very streamlined or the hardware is not so bad, as the phone is surprisingly snappy when its not stalling, which leads me to believe its a system app/service........ive had slow devices, and usually, everything is slow all the time, either because outdated hardware or heavy rom, so hopefully its a system app

---

Adb method works well here, tanks a lot. No UB, no root.

---

I'll be trying the ADB method when have enough charge as had to take Nokia 2.1 back and for that device having a Snapdragon I can confirm that this Nokia 1 is quicker by a mile

---

I done the adb method and it's worked!!!

---

thank you guys for this hack. multi-tasking is finally working and alot of overlays and apps are now working without closing.
I'll share with you something i found to make this phone really fast: in developer mode disable animations from x1 to OFF. Then turn ON gpu for 2d drawings. And reboot.
Now it will be buttery smooth!!