Related
Q&A for [MOD] Remove CarrierIQ
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD] Remove CarrierIQ. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Wonders_Never_Cease said:
Its one of your everyday apps,fresh flash,no new apps installed here...and of course it would stop,you stopped [email protected] system,even on test devices this is not an issue. Reflash,install app by app one at a time and youll find culprit....takes time but I can say with certainty ciq is NOT causing the issue your experiencing.
Click to expand...
Click to collapse
This might be a little late but I was searching Google for a solution, and stumbled onto this thread.
I think I have an answer to this. I just rooted my HTC One M8 (running 4.4.4 on AT&T), and started reinstalling apps. The stock 4.4.4 ROM might not have C IQ, but I think the HTC Service Pack (v. 1.1.853606) patches it onto devices. This is auto-installed inside of the Google Play store, I just saw it installing about a month ago and didn't realize it contained Carrier IQ.
The reason why I think this delivers it, is because around that date, I also noticed my "GPS signal" icon turning on, even when Wifi+4G+GPS were all turned off. I downloaded the Voodoo CarrierIQ Detector and confirmed that "Carrier IQ has been found and is active."
The app gives me these details:
detection score: 270
ROM binaries and daemons
/system/lib/libiq_client.so
/system/lib/libiq_service.so
Running processes
system 3815 1605............diagandroid.iqd
Suspicious classes
com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
So, somehow, in the few apps I've installed, Carrier IQ has definitely been added, and is definitely recording data.
EDIT: Actually, I'm starting to find some of the files. Using File Explorer (FX) on a rooted HTC One M8, I looked in (from the 'Home page' of the app):
Code:
System(root) > system > app
I see the "HtcResetNotify.apk" and .odex files. I'll attempt to delete and modify the files listed in the first post and confirm that I can manually remove them.
EDIT 1.5: I couldn't find three of the files the original post had listed for delete (all in the /system/framework folder):
frameworkEDIAG.jar
frameworkEDIAG.odex
framework-res.odex
EDIT 2: Deleting files went fine. I copied over the other files and...well....my phone immediately rebooted and it's now stuck on the 'htc one' splash page during boot. I'm praying that someone has the original files for the 3 "MODIFIED" files. Anyone?
EDIT 3: All is not lost! I forced a reboot (Power+Volume Up) and it came back on. I checked the folders where I deleted, and the libiq_client/_service files were back. Deleted those again. The other files I deleted seem to be back as well...not sure what happend.
EDIT 4: Ok, so in case anyone finds this. I have a rooted HTC One M8, and I want to keep it stock (except for the root). My solution was to get two apps:
1. "AutoStarts." This was a paid app ($1.60 USD I think?) but ended up not having Carrier IQ in the process list. I did end up using it to block other auto-starting applications, and it immensely sped up my boot time and kept the OS running smoothly for long stretches, no reboots required.
2. "MyAndroidTools." This was free (I think it has a paid version) and allowed me to find and disable the Carrier IQ process. Note that this app is made by the same developer as "Disable Services," less filter features in Disable Services but no ads as far as I can tell. Same exact processes show up though, and the disabled/enabled carries through between MAT and DS.
After setting MyAndroidTools up to disable Carrier IQ (found under "Service" type -> "System" tab -> "Android System" item), I used "Voodoo Carrier IQ" to check for the process. It found the files, but said it was inactive.
However, either after rebooting or a long enough period, it seems to be running again according to Voodoo. I have not seen it turn on GPS anymore, so MyAndroidTools may at least prevent it from re-hooking and turning on GPS. Maybe it's just on and logging local actions, I'm not sure. But I still have not seen in show in Autostarts; if it did, I would hope to step the process from re-hooking completely.
Hopefully someone getting here from Google will find some of this helpful.
Dondula,
You're not crazy. This IS an issue. There are several others experiencing the problem with the IQ Agent constantly turning on the GPS. It seems to happen anytime your service changes (no service -> 4G <-> 4GLTE). It is particularly bad for me as my office building gets poor LTE reception, so my phone is constantly going from 4G to LTE and wreaking havoc on my battery. I haven't found any solution yet.
Douglas_D said:
Dondula,
You're not crazy. This IS an issue. There are several others experiencing the problem with the IQ Agent constantly turning on the GPS. It seems to happen anytime your service changes (no service -> 4G <-> 4GLTE). It is particularly bad for me as my office building gets poor LTE reception, so my phone is constantly going from 4G to LTE and wreaking havoc on my battery. I haven't found any solution yet.
Click to expand...
Click to collapse
I was able to get rid of this issue by disabling the carrier IQ service. I did this using an application called Disable Service from the Google Play store.
Works like a charm, and has the added advantage of disabling the IQ service intrusion.
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.
Device: SM-N900P
Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).
The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:
-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).
-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.
-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.
The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.
I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .
After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://forum.xda-developers.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.
Then I installed this mod to pump sound out of both speakers: http://forum.xda-developers.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.
Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://forum.xda-developers.com/showthread.php?t=2752379 . Again, no problems.
I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.
I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://forum.xda-developers.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.
This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://forum.xda-developers.com/gal...camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://forum.xda-developers.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.
Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://forum.xda-developers.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .
I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.
I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.
These are all settings that monitor usage.... should that tell me anything? I have tried wiping cache and dalvik, but that only seems to fix battery usage and data usage very temporarily(like, for a minute or less). And it doesn't seem to have effect on Process Stats.
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
GAPO said:
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
Click to expand...
Click to collapse
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Will do. Thanks for your help!
Okay well I decided to re flash OC5 and start from scratch.
I took it back to stock and re rooted. Am now debloating....no isssues yet.
I have flashed everything except the Polish camera mod and the wallpapers. Having zero issues of any kind. I know it can take difficulties some time to manifest themselves, but I'm betting it is either the lock screen animations or the camera mod. Leaning towards the lock screen animations because it involves messing with system.ui...
Okay, made a new backup and flashed the camera mod. No issues. After every mod, I have been going back and checking for issues. This is all stil pretty new, but if everything is still fine after a couple of days, well, I will be convinced that it was the lock rings. Not surprising obviously that flashing stuff meant for foreign variants can wreck your sh*t, lol.
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
metalslug53 said:
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
Click to expand...
Click to collapse
You will need to modify your build.conf to prevent the update screen from prompting you.
Change the build number to something else....
/system/build.prop
Change the build to something like: ro.build.display.id=AKOT49HA
and do the same to the rest of them in the file.
Hi,
This is my first time specifically posting a question as a Q&A style thread so I hope I'm doing this right.
I have been using the Redmi Note 2 for about a month now. Overall, it's been a great phone (especially considering the price). However, I've been experiencing a couple of issues and I am hoping that some of you may be able to help.
I have rooted the phone but have not installed a ROM/kernel.
I have been using Wakelock Detector to track my battery life. Of most significance is com.baidu.map.location (NetworkLocation). I have attached the two screenshots showing the frequency of how often it wakes up my device. I tried to greenify it but it wouldn't allow me - it says "Sorry, "NetworkLocation" is ingreenifiable". Does anyone have any idea for me?
I have also been trying to use Amplify as another means to try and improve battery life. As mentioned, my phone is rooted, and the app prompted me to install the Xposed app which I did. However, after installing the app, it wants me to install the framework but it does not allow me to. I have attached the screenshot of this too.
Nova Launcher - Sometimes when I open the app drawer, the resolution of the app launcher appears funny. To fix it, I normally just press back and go back into the app drawer and it goes back to normal. I have attached a screenshot of what this roughly looks like. This is not a big deal but can be a little annoying. Has anyone experienced this?
SD Maid - I used to use this app on my old Galaxy S3 i9305 to clear out storage space taken up by unnecessary stuff. This app no longer works on this phone. I have attached a screenshot of the issue that I am having.
I have downloaded Auto Call Recorder from the app store with the intention of having it automatically record my phone conversations. It does not work but I am unable to figure out why. I have checked the settings and I cannot identify any obvious setting that is incorrectly configured.
Flynx - I have been trying to use Flynx as it appears to be an incredibly useful app, but it seems something is not working correctly. In the screenshot that I have attached, where it says "Tap on the bubble to open it!" I am assuming there is a bubble that is supposed to appear for me to tap, but it does not appear.
APUS Launcher/Clean Master - finally and maybe most worryingly, I sometimes get 2 or 3 apps "pushed" to my device prompting me to install it. I can only remember 2 at the moment; APUS Launcher and Clean Master. Fortunately, I am asked to give the app permission for installation but it worries me because it has occurred a few times and I did not download it at all. I do not have a screenshot of this at the moment, but I will do it next time it occurs.
I have been told that my provider (Vaya in Australia) sends out a SMS for "automatic update" purposes. I only spotted this because I have noticed that I was charged for 2 separate international SMS on 2 occasions when I did not send them (to a UK number, +44 7786209730). I am not sure whether this one is a phone problem or something else.
I appreciate any of your assistance in advance and I am sorry if I have not provided enough information. I am also not sure as to which issues may simply be app problems as opposed to a problem with MIUI software or Xiaomi.
Hope I will be able to get some assistance!
SD Maid - I used to use this app on my old Galaxy S3 i9305 to clear out storage space taken up by unnecessary stuff. This app no longer works on this phone. I have attached a screenshot of the issue that I am having.
Click to expand...
Click to collapse
Does the crash happen when the dialog opens, or when you click the orange entry?
Try giving your sdcard a name, possibly doing it from a desktop computer.
Hi, the crash happens when I click on "Overview" then click on "To start press [refresh icon]" and then you just press there - what normally happens is it will give a overall summary of the phone.
However, I have just tried it again. When that error message comes up, instead of tapping on the listed entry (as is instructed), I press "Done" and it is able to give me a summary!
So for some reason it appears as though it doesn't work (at least from the error message), and I just press done and it still works.
Thanks for your reply nevertheless! Would not have figured that out had you not replied hahaha.
If you just press "done", SD Maid won't have access to your external sdcard.
Did you try installing the Xiaomi EU rom, since it's supposed to be cleaned from chinese apps (Like the baidu one).
Hi all,
Sorry it seems like I never came back to expand what I have done to try and fix these problems.
I ended up changing to Hermes ROM here http://www.smiui.net/redminote2_hermes.php
Most of the issues above are now solved, but there are some that are still present such as #2 and #5. So Amplify still doesn't work, but I think this is a hardware limitation and Auto Call Recorder still doesn't work. As for why Auto Call Recorder doesn't work, I don't know why, but I am not greatly bothered by it so I have not attempted to do anything to resolve that problem.
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!!