Related
Hi guys,
I am currently using the latest CyanogenMod (have been for more 7 months). I have found that it takes about 1 full seconds (at times maybe more) to load the Dialer app when I press the "Call" button. I would like to find out how can I speed up this function, as for me, the phone dialer app is the MOST crucial function for a PDA phone.
I find that it is much faster for me to get to the "Home" app after I have enabled "Home App in Memory" using "Spare Parts". Is the reason why the dialer is slow due to it having to load up every single time? Can we run "Dialer" the same way as "Home App in Memory"? Going back to the Home screen takes less than a second from any app that I may be using, at any time. Can you guys help me to make the same happen for Dialer? Ideas?
Thanks! Hope I am not the only one with this minor quirk.
The problem is that Wysie's Contacts (which is used in most of the roms out there) takes so long to load it's ridiculous. The only permanent fix would be to extract the original contacts app from one of the stock roms and push it to your phone. Of course you may lose certain features in the process.
That is to the best of my knowledge, anyway.
Try clearing your call log.
r4d14n7 said:
The problem is that Wysie's Contacts (which is used in most of the roms out there) takes so long to load it's ridiculous. The only permanent fix would be to extract the original contacts app from one of the stock roms and push it to your phone. Of course you may lose certain features in the process.
That is to the best of my knowledge, anyway.
Click to expand...
Click to collapse
Ah, so it's Wysie's contacts app that is slow right? Hmmm... is there an .apk file for the original stock app? I think speed really is very important in this sense. I do not have to have all the fancy stuff if it slows down my ability to phone another person. Thanks for your suggestion.
Sleeepy2 said:
Try clearing your call log.
Click to expand...
Click to collapse
It works, but for a while only (when the log grows longer then the lag comes back again). Thanks, this would be a temporary 'fix'.
It has to do with the gruoping. I don't have root any more so I can't check. See if you can turn the grouping off or if there is a way to auto clear the log. There are a lot of great features in that contact apk that make it a must.
Damn, I wish I could get root so I could have it back.
Hello guys,
I'm looking for a decent app that monitors and prevents certain processes from automatically starting. I'm not looking for a "killer", which reacts after the processes has started. I'm looking for a way that can stop certain processes from starting by itself. The best example would be: my FM Radio would start by itself?! And I don't want that, because I rarely listen to it, yet I still need it there, only when I manually open it up and listen to the radio...
The information from my search are heavily mixed up and some are extremely old (dated back to 2009), yet the newer ones are mostly vague in terms of a verdict as to what the best solution is.
I would appreciate your input and insights, and click that Thanks button generously
an app that i can suggest you is rom toolbox pro. one of its many functions is disabling the programs' autostart. i have to tell you that i haven't used this function yet, because i'm a bit noob and i wouldn't like to reflash the rom. the app is a bit expensive, but there is also the trial version, so before buying it, you can see if it is what you are searching for.
Thanks for your reply!
If I understood correct, you couldn't use the "anti-autostart" function because you haven't rooted yet?
I agree, ROM Toolbox Pro is a fine tool, and does this.
Before I started messing with ROMs, I just used Autostart. It does only this. What it also does is allow you to turn off the 'listeners' each app has for certain events.
For installed apps, you can often just disable all listeners to stop them popping up when they like and chew into my battery. For system apps, be more careful (or leave them). Most event names will mean nothing, so use with care. I try them one at a time and make sure everything still works, typically.
I think that is more comprehensive that ROM Toolbox, although that does a lot more. I have bought both anyway, and both are available for free to try out.
I seriously recommend DroidWall as well. It gives you control over what app can use what method, or none, to access the internet. A Must-Have, IMO.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
cswithxda said:
Thanks for your reply!
If I understood correct, you couldn't use the "anti-autostart" function because you haven't rooted yet?
Click to expand...
Click to collapse
I think you can use the 'don't start' without Root. You cannot block the listeners until you have Root, so it is probably a waste of time. They'll just pop right up again whenever they wish.
Great, Jerome! ROM toolbox downloading
'Autostarts' works fine for me.
Using Autostarts here as will.
System tuner pro is also a very useful tool for app- and task-handling and many other things too.
Sent from my GT-N7000 using Tapatalk
^Thanks!
I encountered a problem in ROM Toolbox though:
In Auto Start Manager, when I either try to disable an event or application, it says "disabling connectivity changed...", and loads from there infinitely. (more than 10 minutes). I ended up force quit it every time. Open it up again, it does show the event/application chosen was disabled, but I don't know if I have to force quit it everytime... Does anybody have any experience like this?
Have your superuser works perfact?
Anybody have a delayed response on the ICS leak roms with autostart settings?
I.e. In gemini app manager and rom toolbox, when you toggle autostart, it takes like 10 seconds before you can carry on.
Like a delay in acquiring superuser rights.
I do suspect it has to do with the rather rushed root kernel by CF, but I can live with it ;-)
cswithxda said:
^Thanks!
I encountered a problem in ROM Toolbox though:
In Auto Start Manager, when I either try to disable an event or application, it says "disabling connectivity changed...", and loads from there infinitely. (more than 10 minutes). I ended up force quit it every time. Open it up again, it does show the event/application chosen was disabled, but I don't know if I have to force quit it everytime... Does anybody have any experience like this?
Click to expand...
Click to collapse
Do you get a popup from SuperUser requesting rights for Rom Toolbox when you start it the fist time? If so,m check the 'always' box and press 'OK'. You should get a message ('toast') saying access granted if you start the app again.
This assumes you have Root. If you do not, and you still get events disabled by ROM Toolbox, you have discovered a new 'exploit' that Rom Toolbox is using!
Best one I've ever used is App Manager. Doeing everything you said you need
Regards
Sent from my Galaxy Note with DarkyROM 3.3
dr.ketan said:
Have your superuser works perfact?
Click to expand...
Click to collapse
Yes, it is working fine. I checked su's log, and it shows the permission was granted.
Also, now that the toolbox has another issue. It won't save settings. For example, somehow my email initiator application was disabled (never set it that way), and when I press it to enable it, it says success. But after reboot, the email application is gone (in home screen and app drawer), and I open the toolbox to check it, it's still disabled. I temporarily solved this issue by deny the toolbox's permission in SU, but this is obviously not a permanent fix.
I emailed the author, but there's no response yet. So please help me
Many thanks!
hkgrob said:
Anybody have a delayed response on the ICS leak roms with autostart settings?
I.e. In gemini app manager and rom toolbox, when you toggle autostart, it takes like 10 seconds before you can carry on.
Like a delay in acquiring superuser rights.
I do suspect it has to do with the rather rushed root kernel by CF, but I can live with it ;-)
Click to expand...
Click to collapse
Delays in mine also, except that it never finishes. The longest I waited was 60 minutes, and it still says please wait...
jeromepearce said:
Do you get a popup from SuperUser requesting rights for Rom Toolbox when you start it the fist time? If so,m check the 'always' box and press 'OK'. You should get a message ('toast') saying access granted if you start the app again.
This assumes you have Root. If you do not, and you still get events disabled by ROM Toolbox, you have discovered a new 'exploit' that Rom Toolbox is using!
Click to expand...
Click to collapse
Sorry, I should've stated this clearly in the OP. I am rooted with ChainFire's kernel, I also have the toast notification poped up (already set it at the first time as "OK" and "always")
But it always says please wait...and never recovers. Pressing the "back" button has no response, pressing home button will let me go back to homescreen but the toolbox is still running in background, and if I open it up again, it's still at "please wait" status, which is why i always had to end it up in force quitting..
Also, in my last post, I described this new issue: it won't save settings on quit (or on system restart). I disable or enable certain events, after the restart, the event was still blocked, and the app icon was gone. I could only get my Email app (samsung stock) back by denying the toolbox's permission in SU.
Im using Android Assistant..
its free in the android market.. it takes 1 minute boot time for the app to load and you can manually shutdown/disable all running apps (that would load always everytime you boot up your phone)
cswithxda said:
Also, in my last post, I described this new issue: it won't save settings on quit (or on system restart). I disable or enable certain events, after the restart, the event was still blocked, and the app icon was gone. I could only get my Email app (samsung stock) back by denying the toolbox's permission in SU.
Click to expand...
Click to collapse
Sounds like a severe problem. I would try one of the others suggested, they appear just as good. Autostart always does what I want without issues too. I do not use ROM Toolbox for blocking listeners, just for ROM utilities.
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
letters_to_cleo said:
Im using Android Assistant..
its free in the android market.. it takes 1 minute boot time for the app to load and you can manually shutdown/disable all running apps (that would load always everytime you boot up your phone)
Click to expand...
Click to collapse
It is good and useful, but it does not block listeners. If you do not do that, the apps will just pop up again.
^ Thanks for all your help fellas!
Just an update: I've got a response from the author and he said it's a known issue, and will hopefully be fixed in next update or so, so let's hope for good
cswithxda said:
Hello guys,
I'm looking for a decent app that monitors and prevents certain processes from automatically starting.
Click to expand...
Click to collapse
Another alternative which disables receivers in Autorun Manager, the pro version works perfectly for me
YA PROCESS MANAGER
It's a process/autostart manager.
If you're like me you're bummed that we have no root and are missing the abilities of root. Namely having the ability to use Xposed to turn off the annoying high volume warning. The following information aims to restore that functionality without root but requires some work but when you're done it's "set it and forget it.". You will never have to do it again. (Unless you wipe your phone)
I have this running on my phone and it works perfectly. I've attached a screenshot showing that the high volume warning is disabled on my phone. Note there is no popup on my volume slider when it's at max, so it's working. This mod uses Tasker and AutoTools. If you're not familiar with them it's OK, the article I'm linking has a step by step process for creating events and tasks.
Once again this isn't my work. I'm just bringing the information to the masses.
All set? Click here to go to the article. Enjoy!
P.S. You will need to open AutoTools and activate the 30 day trial if you don't have the full version. Then grant it permission, If not this won't work. To get the full version just open AutoTools and clock "Get full version".
***********UPDATE 09/15***********
I have confirmed that you will have to manually "test" this procedure first before it survives a reboot.
To do this:
Open tasker.
Click on the Monitor Start event.
Click on the 30 second task.
Click the "play" button in the lower left corner.
The task will begin manually.
If all is well both of the actions will turn green.
If anything turns red something isn't configured correctly.
***********UPDATE 09/17***********
For those that either don't want to or are having difficulty setting up the profiles I have attached them to this post in XML form, Then all you have to do is give the apps permission in ADB as stated in the article and import the profiles.
To import them into Tasker:
Download the file called "Tasker Profiles.zip" from the link below.
Unzip it and save it anywhere on your internal storage. Open up Tasker and disable Beginner Mode in Preferences.
Then, go back to the main screen and long-press on the “Profile” tab up top. You should see a pop-up with one of the options being “Import.”
Tap on that and browse to where you saved the .prf.xml files and select that file to import.
Repeat for the second profile.
Screenshots for this are attached to this OP.
I have also attached a quick demo video to show that this process works perfectly. No popup.
Credit:
Mishaal Rahman
reboot and see if it still works.
I already tried this and after reboot it still prompts the first time.
I've rebooted several times. It works for me. There is a 30 second delay before the task is executed. That is by design.
Compusmurf said:
reboot and see if it still works.
I already tried this and after reboot it still prompts the first time.
Click to expand...
Click to collapse
Try this to see if everything is set up correctly:
Open tasker.
Click on the Monitor Start event.
Click on the 30 second task.
Click the "play" button in the lower left corner.
The task will begin manually.
If all is well both of the actions will turn green.
If anything turns red something isn't configured correctly.
I've attached screenshots of this procedure.
Also something to consider is that if you have any task killers installed or anything that kills tasks on startup you should add tasker to the ignore list of that app.
Hope this helps.
It's configured correctly. Here is the thing. If you pull the value before without using, then pull the value after clicking ok manually, it is NOT 2, it's 0. This was discussed on the s7 and s8 forums. Odd that yours works and dozens of other folks doesn't.
Sent from my SM-N950U using Tapatalk
I dont know what to tell you. It does work for me just fine as my screen shots show. Sorry it's not working for you.
Can you screenshot your configuration screen? Is the value your sending "int" for integer? It shouldn't matter but what Carrier are you using? I'm Sprint.
One other thing to check is under app permissions ensure that AutoTool has the ability to change system settings. Just running the adb shell pm command isn't enough.
Compusmurf said:
It's configured correctly. Here is the thing. If you pull the value before without using, then pull the value after clicking ok manually, it is NOT 2, it's 0. This was discussed on the s7 and s8 forums. Odd that yours works and dozens of other folks doesn't.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
According to the article 0 is 'not configured' 1 is 'disabled' which is what the value would be when you click ok. 2 is 'inactive'.(How this differs from 'not configured' or 'disabled' I do not know). and 3 is 'enabled'. All depending on your mobile country code. Perhaps changing it to 1 will work for you?
Specifically, we will be modifying the System.Global property audio_safe_volume_state both on boot and periodically so Android will always think you have consented to bypass the warning. This property is defined in AOSP, which we’re reproducing below. There are several states this property can take, ranging from 0-3. 30 seconds after boot or after every 20 hours of continuous music playback, the state is set to ‘0’ or ‘not configured.’ It is then set to ‘1’ for ‘disabled’ or ‘3’ for ‘enabled’ depending on your Mobile Country Code. If you live in the E.U., this property is set to ‘3’ by default but is changed to ‘2’ for ‘inactive’ whenever the user manually bypasses the volume warning. We will be changing the value of this property to the ‘inactive’ state (changing it to ‘disabled’ never worked for me, in case you’re wondering).
Click to expand...
Click to collapse
Hope this helps.
This is already built in...Vibration>Volume>3 dots menu in upper right hand corner> Media Volume Limiter> Turn it off.
Namuh said:
This is already built in...Vibration>Volume>3 dots menu in upper right hand corner> Media Volume Limiter> Turn it off.
Click to expand...
Click to collapse
Confirmed.
Going to Settings -> Sound and Vibration -> Volume -> hit the 3 dot menu -> Media Volume Limiter -> Off works.
I came from a Note 4 with Android 5.1.1 that didn't have this feature. I had no idea Samsung finally caved and added it.
Thank you.
Or not. I rebooted again and it does NOT work anymore. I'm really not trusting Samsung with this. The tasker method works every time. Every reboot. See attached screenshots showing it's turned on (and set to max) and still showing this message. I rebooted several times just in case I had a weird reboot. I'm still getting the popup even with it turned on and the max adjusted to the maximum or even with it turned off completely.
I only wish I was wrong. Thanks for the try though.
Yeah will reset after a boot
https://forum.xda-developers.com/showpost.php?p=73802232&postcount=4
marctronixx said:
https://forum.xda-developers.com/showpost.php?p=73802232&postcount=4
Click to expand...
Click to collapse
Yup...so with tasker I don't have to do any of that. I never have to touch it again. It never comes back.
Thanks again though.
I did learn something from this process. When I re-enabled the tasker even it didn't work when I rebooted. So I hit the "play" button that I mentioned earlier to retest the task and once everything turned green I rebooted and it now works again...after every reboot. So I'll add this to the OP that the task must be "tested" after it's set up in order to get it to work.
Even more interesting is who posted it. Compusmurf was the guy who stated in this thread that this did not work for him. Interesting.
I did get it to work finally. I had another tasker/app that was stepping on it.
Compusmurf said:
I did get it to work finally. I had another tasker/app that was stepping on it.
Click to expand...
Click to collapse
Well I also confirmed that when I disabled it and allowed the popup to come back by rebooting simply re-enabling the tasker even then rebooting did not make it work again. I had to "test" it with the play button to get it to work again. So I'm updating the OP to reflect this.
rawintellect said:
Yup...so with tasker I don't have to do any of that. I never have to touch it again. It never comes back.
Thanks again though.
Click to expand...
Click to collapse
Yeah my point of my post was to show the reason why the built in way doesn't work long term. The tasker way is preferred for those who find the nanny thing an annoyance. :good:
System ui tuněr app should be able to do it
Techvir said:
System ui tuněr app should be able to do it
Click to expand...
Click to collapse
I looked at every single screenshot of System UI Tuner in the play store. I saw no option to disable the high volume warning. Only an option to remove the volume icon which isn't the same thing.
Can you show me a screenshot of it working?
I know this process I linked is a long one and I would really love to be shown a better way but until I am this works for non rooted devices every time.
I realized that when I change some settings in ColorOS it magically changes back without telling you.
I installed Google Assistant from the app store. It required Google Assistance to be selected as the default Assistive App [default value : none]. After I changed that.. it changes back at some random amount of time.. I'm not able to work out how long it takes for it revert the setting.. but sure enough it will.
Another App is LastPass.. It requires me to Enable Autofill from accessbility Options.. Once again I turn it ON.. after some random amount of time it will revert it back to "Off"...
What can be done to stop this from happening?
Blah blah blah! said:
I realized that when I change some settings in ColorOS it magically changes back without telling you.
I installed Google Assistant from the app store. It required Google Assistance to be selected as the default Assistive App [default value : none]. After I changed that.. it changes back at some random amount of time.. I'm not able to work out how long it takes for it revert the setting.. but sure enough it will.
Another App is LastPass.. It requires me to Enable Autofill from accessbility Options.. Once again I turn it ON.. after some random amount of time it will revert it back to "Off"...
What can be done to stop this from happening?
Click to expand...
Click to collapse
Happens to some degree in the EU model too,noticed the lastpass app autofill stops amongst other things. Am thinkin maybe it's the Phone Manager app which I think kills battery intensive apps if you allow it
manus31 said:
Happens to some degree in the EU model too,noticed the lastpass app autofill stops amongst other things. Am thinkin maybe it's the Phone Manager app which I think kills battery intensive apps if you allow it
Click to expand...
Click to collapse
I'll give this a try.. I've gone into phone manager -> startup manager and allowed the two apps.. the two apps wasn't there even though I have allowed the app to run in the background.
We will see tomorrow.
Nope that didn't work.. anyone else have other suggestions? Anything to remove delete or hack?
Blah blah blah! said:
Nope that didn't work.. anyone else have other suggestions? Anything to remove delete or hack?
Click to expand...
Click to collapse
Man,I don't know what the issue is but read on the Realme community that the OS just reverts to defaults to ensure proper functioning of the phone,
ColorOS is certainly the biggest downside to this phone. Am missing OxygenOS on my 6T a lot though I'm Gona stick with the x2 pro for now,
Bought the phone for its flagship specs and storage and and to get away from the hassle of messing around with the phones setting's with tricks and mods.
Have decided to just accept colourOS for what it us.,though there is some battery drain,it's not awful and I'm still getting notifications.
Will just have to hope things improve with updates and the next big update should improve things a lot,mind you,it's a long way to April ?
Not notice anything revert on mine... This sounds like the same issue I had on the mi 9... I can't remember how I solved it but it was something to do with the auto security checks the phone manager app did... After a set amount of time the phone manager would perform certain checks and reset certain options throughout the operating system.
ngagephone said:
Not notice anything revert on mine... This sounds like the same issue I had on the mi 9... I can't remember how I solved it but it was something to do with the auto security checks the phone manager app did... After a set amount of time the phone manager would perform certain checks and reset certain options throughout the operating system.
Click to expand...
Click to collapse
Sounds about right,Have feeling the phone manager app has something to do with it.It does not like the developer options
Ok.. I found my work around for now.
I'm using tasker every 10 mins to change the accessibility options for all the apps that need it and set the google assistant to default.
Working ok so far for the last day.
Blah blah blah! said:
Ok.. I found my work around for now.
I'm using tasker every 10 mins to change the accessibility options for all the apps that need it and set the google assistant to default.
Working ok so far for the last day.
Click to expand...
Click to collapse
Seems like more trouble than its worth,the only settings I'm having trouble keeping are the animation ones, but honestly it's not bothering me anymore. Have animations setting set to fast in the stock launcher setting and it's not so bad.
Didn't think lastpass was working but it has been appearing to autofill login to sites in a chrome
Did anyone found a solution? Im having this issues too...
B0dYGu4rD said:
Did anyone found a solution? Im having this issues too...
Click to expand...
Click to collapse
you can simply turn off battery optimizing for the app and check... it works
Nice suggestion... Ill try this :good:
Apps will automatically close within 10-20 seconds after I leave the app through the home gesture. It drives me crazy that literally no app will stay open in my recents. I tried locking the apps in the recents, it did not help. (What's the sense of locking apps there then?!)
Anyone has a solution/workaround?
Just select to not optimize that app in battery settings....
I'm on OOS 13 Open Beta 2 build and haven't encountered this issue at all. Apps stay in background for hours honestly.
Maybe check Battery Optimization for each of those apps and permit Background Activity?
zopostyle said:
Just select to not optimize that app in battery settings....
Click to expand...
Click to collapse
I did that but it doesn't help. Apps stay in recent when I leave them but if I open it again seconds later, I'm greeted with the splash screen and for example Chrome reloads the website.
hackslash said:
I'm on OOS 13 Open Beta 2 build and haven't encountered this issue at all. Apps stay in background for hours honestly.
Maybe check Battery Optimization for each of those apps and permit Background Activity?
Click to expand...
Click to collapse
I tried disabling every possible battery optimisation but apps still close seconds after I leave them.
Here is few solutions. Don't know if they works or not.
Oneplus
Hey Android vendors, don’t kill my app!
dontkillmyapp.com
Dayuser said:
Here is few solutions. Don't know if they works or not.
Oneplus
Hey Android vendors, don’t kill my app!
dontkillmyapp.com
Click to expand...
Click to collapse
Tried everything described in there already, nothing helped sadly. Thanks though
memocatcher said:
Tried everything described in there already, nothing helped sadly. Thanks though
Click to expand...
Click to collapse
Final solution... Change phone
memocatcher said:
Apps will automatically close within 10-20 seconds after I leave the app through the home gesture. It drives me crazy that literally no app will stay open in my recents. I tried locking the apps in the recents, it did not help. (What's the sense of locking apps there then?!)
Anyone has a solution/workaround?
Click to expand...
Click to collapse
stop using cos. install oos.
g96818 said:
stop using cos. install oos.
Click to expand...
Click to collapse
I'm on OOS 12.1
I have this same issue. All this ram and apps still closing out right after you leave them.
This is definitely a tweak/edit/change you did somewhere on your end. Maybe developer options?
Tilde88 said:
This is definitely a tweak/edit/change you did somewhere on your end. Maybe developer options?
Click to expand...
Click to collapse
No, since its happening to.other people too as you can see. I tried everything
Yes It can be a "pita"! Looking for a solution as well...
memocatcher said:
Tried everything described in there already, nothing helped sadly. Thanks though
Click to expand...
Click to collapse
Developer options>standby apps, are all buckets showing as active? If not global power management is active.
Does it happen in safe mode ie 3rd party app causing it?
memocatcher said:
No, since its happening to.other people too as you can see. I tried everything
Click to expand...
Click to collapse
Weird doesn't happen to me at all. I just checked, and I am even in battery saver mode. Programs stay in RAM as expected, and load immediately in the state/position they are in. Android 12 A.15, rooted, tons of debloat via adb disable. I also even run Malwarebytes with realtime stuff and scanning enabled.
Double post. Please delete
Tilde88 said:
Weird doesn't happen to me at all. I just checked, and I am even in battery saver mode. Programs stay in RAM as expected, and load immediately in the state/position they are in. Android 12 A.15, rooted, tons of debloat via adb disable. I also even run Malwarebytes with realtime stuff and scanning enabled.
Click to expand...
Click to collapse
I'm sure it does, try opening one app, copy from one, switch to another and paste, continue doing that. Eventually it'll lose your position.
Apps remain in recents yes but the absolute state is not kept.
dladz said:
I'm sure it does, try opening one app, copy from one, switch to another and paste, continue doing that. Eventually it'll lose your position.
Apps remain in recents yes but the absolute state is not kept.
Click to expand...
Click to collapse
Um, yes, they absolutely stay in whatever position I left it in for as long as I leave it. Do I screen record for you?
Tilde88 said:
Um, yes, they absolutely stay in whatever position I left it in for as long as I leave it. Do I screen record for you?
Click to expand...
Click to collapse
Thats so weird because they won't stay open in the background for like most of us. 10 seconds after I minimize an app like Gmail, then reopen it, I will be greeted with the Spash Screen of Gmail which takes like 1-2 seconds.
Chrome is even more annoying, since the website I was on 10 seconds ago, will have to reload.
It's stupidly annoying and I tried everything to get it fixed. With this behavior of RAM, that Apps close withing literaly seconds, 2 GB RAM could have also made the deal