Related
I have a BlueAnt Endure headset connected to my XPZ. Randomly my phone will dial someone from my phone book. I have just realised that it is because I keep the headset in my pocket (when not in use) and if I accidentally lean on it and subsequently press the command button twice within a few seconds it will enable the 'Voice Dialer'. It will then interpret any noise or voice into random numbers or sometimes a phonebook name.
I have called BlueAnt and they tell me that I cannot disable the 'Voice Dialer' command within the unit.
Is there a way to disable this action on the phone? Is this a SONY or an Android thing?
Do I need to install a custom ROM to disable this function?
If you are rooted then the best thing I can think of is to freeze the voice dialer app with titanium backup. (or remove it from /system/app)
Lgrootnoob said:
If you are rooted then the best thing I can think of is to freeze the voice dialer app with titanium backup. (or remove it from /system/app)
Click to expand...
Click to collapse
Unfortunately not rooted, As I understand it, rooting and ROM'ing would void my warranty?
I tried disabling it with Startup Manager and Starup Cleaner 2.0. Rebooted and still comes up.
What's the best thing to do if it is not rooted?
Hagar76 said:
Unfortunately not rooted, As I understand it, rooting and ROM'ing would void my warranty?
I tried disabling it with Startup Manager and Starup Cleaner 2.0. Rebooted and still comes up.
What's the best thing to do if it is not rooted?
Click to expand...
Click to collapse
There is truly no such thing as a warranty when it comes to software.
Think about it.
The software can almost always be put back to stock like nothing ever happened.
Even if you do manage to brick your phone beyond repair, (very unlikely but can happen) you would still be able to come up with some crap lie to get a replacement because it would be almost impossible to figure out have messed with it; you will have a backup of all of your data,(linux skills maybe required)
Go ahead and root only if you feel up to it.(warranty is for software only.)
Think about it.
(p.s. a little bit of advice: dont use any task killers or startup managers. I can provide you with solutions to these problems.)
A legitimate alternative is to use a program called autostarts.
It disables applications from autostarting based on their intents.
Android uses intents. Example: there is an intent for headphones plugged in.
So an application can sign its self up to use that intent.
So now when the headphones get plugged in the application can start up or play music etcetera.
Lgrootnoob said:
There is truly no such thing as a warranty when it comes to software.
Think about it.
The software can almost always be put back to stock like nothing ever happened.
Even if you do manage to brick your phone beyond repair, (very unlikely but can happen) you would still be able to come up with some crap lie to get a replacement because it would be almost impossible to figure out have messed with it; you will have a backup of all of your data,(linux skills maybe required)
Go ahead and root only if you feel up to it.(warranty is for software only.)
Think about it.
(p.s. a little bit of advice: dont use any task killers or startup managers. I can provide you with solutions to these problems.)
A legitimate alternative is to use a program called autostarts.
It disables applications from autostarting based on their intents.
Android uses intents. Example: there is an intent for headphones plugged in.
So an application can sign its self up to use that intent.
So now when the headphones get plugged in the application can start up or play music etcetera.
Click to expand...
Click to collapse
I have rooted, and ROMd my SGT7 several times and my SGS2 recently with neatROM (looking for a better one. Didn't like CM10.2)
I'll certainly give your points some thought. Very interested in the autostarts, so yes, I'd be greatful for your help.
Lgrootnoob said:
There is truly no such thing as a warranty when it comes to software.
Think about it.
The software can almost always be put back to stock like nothing ever happened.
Even if you do manage to brick your phone beyond repair, (very unlikely but can happen) you would still be able to come up with some crap lie to get a replacement because it would be almost impossible to figure out have messed with it; you will have a backup of all of your data,(linux skills maybe required)
Go ahead and root only if you feel up to it.(warranty is for software only.)
Think about it.
(p.s. a little bit of advice: dont use any task killers or startup managers. I can provide you with solutions to these problems.)
A legitimate alternative is to use a program called autostarts.
It disables applications from autostarting based on their intents.
Android uses intents. Example: there is an intent for headphones plugged in.
So an application can sign its self up to use that intent.
So now when the headphones get plugged in the application can start up or play music etcetera.
Click to expand...
Click to collapse
I have rooted, and ROMd my SGT7 several times and my SGS2 recently with neatROM (looking for a better one. Didn't like CM10.2)
I'll certainly give your points some thought. Very interested in the autostarts, so yes, I'd be greatful for your help.
Hagar76 said:
I have rooted, and ROMd my SGT7 several times and my SGS2 recently with neatROM (looking for a better one. Didn't like CM10.2)
I'll certainly give your points some thought. Very interested in the autostarts, so yes, I'd be greatful for your help.
Click to expand...
Click to collapse
I don't like cm either.
Rescan Media Root is also a good one for speed.(by disabling android native intents)
It can disable the media scanner on startup if you want a little speed boost.
(root only though)
Autostarts will cost money and should be used to stop apps from running on boot.(an alternative is xposed framework module "bootmanager" or something like that)
Titanium backup is what you should use to freeze the voice dialer.(<preferred method)
I wonder why upgrade to Android 4.3 installs dialer on tablet
which is a data -only device.
After had upgraded to Android 4.3 we noticed a new app installed which was not the case before the upgrade.
4.3 installs voice dialer.
We wonder why, one can not use tablet to setup classic voice calls.
VoIP merely are possible. However, as for the voice dialer automatically installed by Android 4.3 we
do not see any possibility to say which is our VoIP app.
What is the sense of voice dialer on data-only device? Any ideas?
I know this has probably been discussed in one form or another in the past, but I want something more up-to-date.
I'd prefer not to use an app that will replace Google notifications with its own, but am willing to root. I do not want to downgrade in any way or form the OS by flashing some old custom ROM.
What are my options for increasing the intensity (and maybe duration) of the vibration? I can barely feel it, especially with a Pebble on my other wrist (two mobile devices).
Currently it is paired with a Nexus 5 running Android 6.0.1
P.S. Does this work?: https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
*Oh yeah, my vibration from Facebook is way better than from Messenger by Google (separate SMS yet again...). Therefore, I could change texting app (and my other messengers are on my iPod Touch 6), but email and other notifications (mainly reminders) need better vibrations as well. Plus, I'd like to unlock the 3 other cores, so going to root and try invisiblek's kernel soon.
This tutorial didn't work as shown in page 2: http://forum.xda-developers.com/g-watch/development/tutorial-root-android-wear-6-0-1-t3320215
Heck, it even lists the wrong command for rebooting into fastboot: "adb reboot fastboot" instead of "adb reboot bootloader". And I've overwritten my recovery partition, thanks a lot! Must be getting rusty...
*Step 4 should be "fastboot boot twrp300modif.img" if Xmaster24's posts were heeded properly (and if the tutorial actually works for others).
Great, a bricked watch until someone sends me stock images... (forgot to backup)
*Maybe I'm wrong about step 4, but anyhow just read this: http://forum.xda-developers.com/showpost.php?p=65661084&postcount=21
OK, I finally resolved my root problems and installed "Advanced Settings for Watch". I increased the vibration from 80 to 100, but it's still not enough for texts (though notable increase for other vibrations).
I have a feeling it has everything to do with the "Messenger by Google" app, so will be exploring some other options soon.
So, I updated my Moto to Oreo yesterday using fastboot method. Quick and painless process.
But after initial setup and check "what's new" I've noticed first bug. Then I thought : maybe we could make a list with all the bugs we spotted ?
Just in case, so maybe we could also keep track when (or if) they will be eliminated ?
So, put your findings there - but I propose that it should be done only by those who already tried factory reset on their phones or complete wipe during flashing. Just to avoid the bugs which come from previous setup leftovers on the phone.
So, my entry to the list is :
- when setting up ringtones - notifications, when I play the selected sound it's most often played back very quietly for the first time, the second time I click the same sound it's played back with normal volume.
By the way, the audio equalizer is working properly now - for me this was the most important change
Found a few.
- Sound glitch is still here, can be unnoticed, but I found a funny thing now. When playing music, with Spotify, YT or similar; you can get a weird glitch in where the sounds goes up and down fast. You need to stop the audio source, and wait few seconds to keep playing.
- Nav Bar, moves a lot so you can really notice when the icons are slightly up or down. I understand why; to avoid damaged pixels, but is funny.
- Nav Bar again. It can be unresponsive, needing to press it twice to allow usage. Solve for this was to start the Moto App, enable the fingeprint sensor and just disable again. It makes the nav bar Works normally then.
- EQ finally Works. But you need to get into a move few options unless is gonna be bass oriented even after you open the EQ settings, you would see a flat config, but the sound match a bass oriented way. Solve is just to mess aroung a Little until is working correctly.
- Moto App Launcher still stops working along with Google. Easy workaround is just Forcing Quit, and go back home. Other workaround for me was being in the Beta testing for the Google. alongside better performance and less problems with Moto App Launcher you can use the Pixel at Glance widget.
So far what I got
Hey there, I've got a few bugs to report to the INDIAN unit of MOTO Z2 PLAY 64GB 4G
1. I've MOTO Z PLAY too and i compared both the devices after the oreo update, in Z i can change the icon shape to round, circle square etc. But it's missing in the MOTO Z2 PLAY
2. I cannot make or receive calls using JIO 4G sim even though i can use this sim on another android mobile MOTO Z and can easily make and recieve calls from there, although the internet is working fine with. MOTO Z2 PLAY
Theae are the major 2 bugs I've found till now..
My Battery life is lower.
ive never seen Batterysaver orange until I updated. Now I have to dust off my TP mod.
Hey guys i need help, i have stock oreo on my Z2. After upgrading it was giving up some issue while on lockscreen and even delay in showing up moto display. then i format my phone and it all well, then i installed greenify and gave it access via adb commands, and the passing of lockscreen again start giving issues, i revoked the greenify commands and still it is giving the same lag on passing lockscreen and drlay in moto display to appear. Can i do something other than full format and without loosing my data.
Mine's performance and battery life have actually improved. I get 6+ hours battery life throughout the day, something I never got in nougat.
The only thing I've noticed is that the screen sometimes doesn't wake up when I pick up the phone, but it's very rare and it also happened to me in Nougat.
So far so good.
victorhbm15 said:
Mine's performance and battery life have actually improved. I get 6+ hours battery life throughout the day, something I never got in nougat.
The only thing I've noticed is that the screen sometimes doesn't wake up when I pick up the phone, but it's very rare and it also happened to me in Nougat.
So far so good.
Click to expand...
Click to collapse
Yeah, the battery is now amazing. First day i got 9h SOT and 20h total. With less usage I get 40 hours with 5,5h SOT! On Nougat it was like 24 hours and 6h SOT.
The only issue I have is that Moto Key force closes sometimes.
Is it normal, that gmail syncs like every 10 min. and that on Oreo this is shown in the Statusbar?
I've found the Nav Bar unresponsive, too.
q.snake said:
I've found the Nav Bar unresponsive, too.
Click to expand...
Click to collapse
Same here, went back to FP navigation, and that's a pain with Screen protector installed....
P2P feature
P2P feature not working for YouTube or Google map or any app
I also have this issue, PiP is not working for me, there is no option in settings for this but the specific for every app, and for all of them it is active. What I have noticed is that the camera image seems to be more "dusty" like with a higher ISO this did not happened with Nougat, I have not verified image results after photographs. I also have a very impressive battery life.
I don't think this counts as a bug, but it is something that is making me crazy since I upgraded to Oreo:
-"Ok Google" detection now only works when the screen is on (if "trusted voice" is on, it will work in the lockscreen, but never when the screen is off).
The option related to "Ok Google" detection changed from "anytime" to something that indicates that the screen has to be on. I had a Moto X (2013) some time ago, and something that I loved about that device was how I could ask google to do some things even if the screen was off. I loved that about my Moto Z2 Play running Nougat, and I didn't expect it to stop working like that with the upgrade.
Does anyone know if it is possible to make it work with the screen off like before? Thanks in advance!
Thank you so much for posting this, you saved me man! I was just about to tap update before i saw this post. The only reason i bought a Moto Z2 Play in the first place is because it was one of the few phones that allowed OK Google detection while the screen is OFF. Very sad to learn they removed this feature in Oreo, though now i think i understand why everyone is reporting better battery life. In Nougat a microphone was always listening for "OK Google" and thus constantly consuming a certain amount of power. According to your post this is seems to no longer be the case.
I doubt that this will ever be addressed so i won't be upgrading to Oreo, having to approach your phone for Google Assistant to acknowledge voice commands is unacceptable, and the fact that only some flagship phones allow it is an embarrassment.
ClowReedd said:
I don't think this counts as a bug, but it is something that is making me crazy since I upgraded to Oreo:
-"Ok Google" detection now only works when the screen is on (if "trusted voice" is on, it will work in the lockscreen, but never when the screen is off).
The option related to "Ok Google" detection changed from "anytime" to something that indicates that the screen has to be on. I had a Moto X (2013) some time ago, and something that I loved about that device was how I could ask google to do some things even if the screen was off. I loved that about my Moto Z2 Play running Nougat, and I didn't expect it to stop working like that with the upgrade.
Does anyone know if it is possible to make it work with the screen off like before? Thanks in advance!
Click to expand...
Click to collapse
Clear data of the Google App.
I'm on Oreo on the Z² Play and Ok Google works just fine with the screen off.
ClowReedd said:
I don't think this counts as a bug, but it is something that is making me crazy since I upgraded to Oreo:
-"Ok Google" detection now only works when the screen is on (if "trusted voice" is on, it will work in the lockscreen, but never when the screen is off).
The option related to "Ok Google" detection changed from "anytime" to something that indicates that the screen has to be on. I had a Moto X (2013) some time ago, and something that I loved about that device was how I could ask google to do some things even if the screen was off. I loved that about my Moto Z2 Play running Nougat, and I didn't expect it to stop working like that with the upgrade.
Does anyone know if it is possible to make it work with the screen off like before? Thanks in advance!
Click to expand...
Click to collapse
Also turn it on as a "Trust Agent" in settings-->security, if you have a screenlock.
You'll also find Moto Voice's Screen unLock activation there. if you use it.
I am scared of upgrading to Oreo since i have no sure way of knowing if i my phone will lose the ability to recognize "OK Google" when the screen is off. If i suffer the same fate as ClowReedd there would be no way for me to roll back and i would lose the functionality i bought this phone for in the first place. Motorola support is incapable of understanding the difference between a phone that can be unlocked with "OK Google" when the screen is completely off and a phone that can achieve the same only when you manually push the power button so you can see the lock screen. But to be fair there is no company in the world whose support is capable of understanding this, i had an extremely difficult time selecting a phone to purchase because of this. Multiple Samsung employees for example would either claim a certain Samsung model that i know has this capability doesn't have it, or claim that a phone that i know doesn't does. Google is also of no help, i have tried to find a list of phones with this capability and got nowhere. Most flagships have it( though some do not), but most midrange phones do not. Which is the only reason i bought a Moto Z2 Play.
Hopefully ClowReedd will respond whether or not clearing the Google app data fixes the issue, since if it doesn't nothing can be done. Google provides absolutely no support for it's assistant other than copy pasted responses online from what i have to assume are bots.
XDANooby said:
I am scared of upgrading to Oreo since i have no sure way of knowing if i my phone will lose the ability to recognize "OK Google" when the screen is off. If i suffer the same fate as ClowReedd there would be no way for me to roll back and i would lose the functionality i bought this phone for in the first place. Motorola support is incapable of understanding the difference between a phone that can be unlocked with "OK Google" when the screen is completely off and a phone that can achieve the same only when you manually push the power button so you can see the lock screen. But to be fair there is no company in the world whose support is capable of understanding this, i had an extremely difficult time selecting a phone to purchase because of this. Multiple Samsung employees for example would either claim a certain Samsung model that i know has this capability doesn't have it, or claim that a phone that i know doesn't does. Google is also of no help, i have tried to find a list of phones with this capability and got nowhere. Most flagships have it( though some do not), but most midrange phones do not. Which is the only reason i bought a Moto Z2 Play.
Hopefully ClowReedd will respond whether or not clearing the Google app data fixes the issue, since if it doesn't nothing can be done. Google provides absolutely no support for it's assistant other than copy pasted responses online from what i have to assume are bots.
Click to expand...
Click to collapse
Exactly how many people have reported such an issue? If it was common, Motorola would probably know exactly what you are talking about. Have you searched the MZ²P forums? how many posts have you found?
'Special'...
The ability for Google Now, to unlock phone and carry out tasks/commands. Is the User Agent, as I posted above.
kewlzter said:
Exactly how many people have reported such an issue? If it was common, Motorola would probably know exactly what you are talking about. Have you searched the MZ²P forums? how many posts have you found?
'Special'...
The ability for Google Now, to unlock phone and carry out tasks/commands. Is the User Agent, as I posted above.
Click to expand...
Click to collapse
Well we already have 1 report in this thread, and it is not hard to imagine that a detail like this would go unreported since i am not even sure if it is a bug. Also a lot of people including yourself don't even know the difference between Google Assistant(i am guessing that is what you mean by Google Now) being able to unlock the phone and being able to wake and then unlock the phone when the screen is completely off.
Most people do not care one way or the other which is why this change could easily go unreported, assuming it is indeed a bug and not just an intentional change to conserve battery life.
XDANooby said:
Well we already have 1 report in this thread, and it is not hard to imagine that a detail like this would go unreported since i am not even sure if it is a bug. Also a lot of people including yourself don't even know the difference between Google Assistant(i am guessing that is what you mean by Google Now) being able to unlock the phone and being able to wake and then unlock the phone when the screen is completely off.
Most people do not care one way or the other which is why this change could easily go unreported, assuming it is indeed a bug and not just an intentional change to conserve battery life.
Click to expand...
Click to collapse
if you look hard enough, you'll find ONE person who's phone exploded.
These forums are for solving problems, not to alleviate your FEARS.
Many things MIGHT happen, there is no point clogging up the threads listing all of them.
If you have a problem, let's solve it,. If you are worried your phone will attract lightning ?, there's no helping you.
Handsfree is important to me, since the 2013 Moto X, (I've had many Moto phones since), It's an invaluable function when phone is lost in the couch cushions.
You are thinking too hard, and making assumptions, I know exactly what you are talking about. Waking the phone and unlocking it are lumped together, what good is a feature that wakes the phone but doesn't unlock it (it can be optionally restricted), likewise what good is handsfree activation, if it can't wake the phone? it seems redundant to spell that out!
Google Now, was the original name for the Google Assistant, phased out last year, let's not nitpick.
BTW: it's fairly easy to go back to Nougat, should you desire it.
Regarding Picture in Picture mode, particularly for Youtube - this is a limitation that Google has put in place that only USA users can access, unless you purchase Youtube Premium. Can confirm PIP works with VLC media player. Netflix only has PIP with 8.1
Hello, just straight forward, ever since android 6.0 come and introduce doze, i always keep getting problem with notifications...
Kinda random actually, sometimes it arrives on time, sometimes its delayed 5-10 mins, sometimes its 1 hour+, or sometiems i didnt receive it at all... the most common occurence is when i unlock my phone suddenly notifications (mainly from gmail) flooded but actually it have been received some times ago...
if im playing with my phone i rarely get this problem...
i have tried several brands like lenovo, asus, and xiaomi and at some point i experienced notification problems on ALL of those phones..
i even root and flashed custom roms but to no luck, the problem still persist. i also tried an app by boeffla "doze control" but still no luck also...
im sure this is because of the "Doze" feature... because when i am using android phone thats still android lollipop im 100% sure i never ran into this kind of problems, before marshmallow i always get 100% notification correctly...
and yes, i have disabled battery optimization on every single application on my phone...
sometimes i didnt get email or importnat chat so i have to refresh those apps like everytime to make sure i dont miss notification...
Anyway my question is does anybody know what android phone today has the feature to COMPLETELY disable doze ?... i dont care about battery life.. whats the point of longer battery if my phone is non-functional...
If anyone know it please let me know, thanks before
Doze Mode
HI,
Did you ever get the delayed notification issue resolved?
I am having the same problem.
I am trying everything humanly possible to sort this out, otherwise I'll have to switch to iphone as notifications are instant with it. I wont be happy at all if I have to do that as Apple just doesn't nearly have the apps that android has but getting instant notifications is most important.
Just curious if you found something out.
Thanks
It's due to the devises you are getting. All 5he ones you listed are mid tier devices that have crap hardware. So they have to make changes to the software to make the battery last. The only way to stop it is to make a custom rom yourself for the device.
zelendel said:
It's due to the devises you are getting. All 5he ones you listed are mid tier devices that have crap hardware. So they have to make changes to the software to make the battery last. The only way to stop it is to make a custom rom yourself for the device.
Click to expand...
Click to collapse
Thanks for the idea, but I'm using the Bullhead(Nexus5X), which is one of _Google_ devices and it does exactly the same. Meaning: higher version of Android, better the Doze is working and it is harder to an application to push notifications thru. On AOSPExtended (9/Pie) I've got a "record" 43 minutes before a GMail notification was shown... While on 4.4 (well before 6.0 when Doze was implemented) it is always < 3min.
Where you could help is to mention of where in Android ROM the Doze actually located? Kernel, vendor, System ?
ppav1776 said:
Thanks for the idea, but I'm using the Bullhead(Nexus5X), which is one of _Google_ devices and it does exactly the same. Meaning: higher version of Android, better the Doze is working and it is harder to an application to push notifications thru. On AOSPExtended (9/Pie) I've got a "record" 43 minutes before a GMail notification was shown... While on 4.4 (well before 6.0 when Doze was implemented) it is always < 3min.
Where you could help is to mention of where in Android ROM the Doze actually located? Kernel, vendor, System ?
Click to expand...
Click to collapse
That is the rom devs doing that and the nexus 5x is a very old nexus and hasn't been officially supported for a few years. So the devs ha e to make hacks to make it work.
Doze is terrible. I personally disable it
zelendel said:
Doze is terrible. I personally disable it
Click to expand...
Click to collapse
Good idea, indeed. Which of the ways you used, pls?
ppav1776 said:
Good idea, indeed. Which of the ways you used, pls?
Click to expand...
Click to collapse
If you have an unlocked bootloader then I do it in the OS. If kot then go into apps and (this will take a while) but then make sure each app is not using battery optimization. This will disable doze for the most part.
As you said you had a 5x then I would build your own this way you know the rom dev is not over writing your selections.
zelendel said:
go into apps and (this will take a while) but then make sure each app is not using battery optimization. This will disable doze for the most part..
Click to expand...
Click to collapse
In stock (8.1) and especially AOSPExtended (9) changing Battery Optimisation on app' level does not solve the issue, at least to my long testing experience.
Both tested GMail and WhatsApp are delaying notifications. WhatsApp IM notifications are a bit better, but WA missed calls are terrible - I've got them delayed for hours during day time (till next time unlock the phone).
GM new emails notifications are as bad as WA missed calls one.
Last couple of days testing disabling Doze completely ("dumpsys deviceidle disable"). It works, indeed, giving 5-8 min delay and without a noticeable battery time decline (<20%). But this requires 'root', which I was avoiding for last 2 years (due to security reasons). So searching for a better non-root way.
Are any ROMs have script scheduling plug-ins, which would allow to run init.d scripts without a need to have 'root' mode active all the time? The best would be, of course, to enable Doze over night and disable it during day ...
For android 6.0+ to get notification instantly try disabling doze mode by this command:
adb shell dumpsys deviceidle disable
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!!