auto boot delay - General Questions and Answers

Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?

m0d hippĀ„ said:
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
Click to expand...
Click to collapse
After your OS finishes booting and loads the full OS stack, a system-wide message called Broadcast Intent will be sent to all apps, notifying them that your device has completed booting (this intent is called BOOT_COMPLETED). Then it's up to the individual app to use that broadcasted intent to pre-load in memory whatever they want (or simply not react at all).
The thing is you want to delay auto boot for that specific application, so there are 2 options for that:
you turn off auto boot in the App itself (if it provides such an option).
you block the app from receiving the intent broadcasted.
The second option is also achieved either by using a task killer to force kill the app (which defeats your point IMO) or it manipulate the app from receiving the intent entirely. Both of these options require root access.
If you have root I suggest The App: SD maid (pro version). Under app control you can modify which system Broadcasts that Keymapper recieves (among them could be boot_completed). See attached screenshot from my device for example.
Hope I helped somehow

Thank you for your response. That was super helpful! The device I am playing around with is a Mekotronics R58x, and it had some sort of modified root that was conflicting with Magisk. I read somewhere on these forums that someone suggested renaming the su file if it exists in /system/xbin/su; which it did. I renamed it and rebooted and after that everything worked wonderfully. Keymapper was still autobooting like previously, but this time all the services loaded right up and I didn't have to restart the app it just worked.
Basically I think the issue was this custom su file that was conflicting with Magisk and causing a headache with the keymapper. I'm glad I stumbled across the fix, but either way your post was also very helpful! Thank you!

Related

Idea for a dev sandbox for apps

I had this idea about an app on the phone that could assist debugging an app or troubleshooting the app.
Essentially my idea is an app gets installed on the phone, this app acts as a sandbox. So the app gets opened and it displays a list of installed apps on your phone, and you choose a second app. The second app opens inside the sandbox application and functions just as it would normally.
What the sandbox does is log all the I/O procedures of the app. As an example if you open up a sound board and press a button it logs the coding used for the button press (onClick) as well as the function calls and where it looks for the file.
While you use the app normally it logs all the I/O and essentially creates a logcat but of the more technical functions of the app.
If this is possible it could be a great way to step through an app and replicate an issue. Such as a FC that happens by pressing the back button. This could pinpoint the why and how.
Is something like this possible within the Android OS ?

[Q] [Android] Can I prevent app from being (easily) killed/stopped by user?

First some backstory (skip it if not interested)
Thing is, I made an alarm clock app that forces user to do some stuff before turning off alarm - classic.
But for some time now, I have been receiving mails from users asking me to add feature that won't let them (quickly) turn off alarm while it is playing, that including force stop or uninstalling with Applications Manager, or turning phone off with power off button.
For some time I got off asking how would I stop them from just taking battery out, but some stated it is not about completely blocking option to stop app, but to make it so time consuming or complicated, that doing it will wake them up anyway (some turn phone off without opening eyes).
Quick ways of stopping application that I have found and that I need to block, are:
- power off phone
- go to Applications Manager and use Force Stop
- other, ROM added ways - as for example, one user wrote, that his ROM lets him quickly stop running apps by long pressing back button
From what I know, blocking any of above is officially impossible. But is it possible with root access?
After doing some research, I didn't found any way to just block application from being stopped/uninstalled, so I have to ask
(ACTUAL QUESTION)
Is it possible (with root access or not) to block user from stopping app in any way? Or at least making it really timeconsuming?
Any help appreciated!
Kogerro said:
First some backstory (skip it if not interested)
Thing is, I made an alarm clock app that forces user to do some stuff before turning off alarm - classic.
But for some time now, I have been receiving mails from users asking me to add feature that won't let them (quickly) turn off alarm while it is playing, that including force stop or uninstalling with Applications Manager, or turning phone off with power off button.
For some time I got off asking how would I stop them from just taking battery out, but some stated it is not about completely blocking option to stop app, but to make it so time consuming or complicated, that doing it will wake them up anyway (some turn phone off without opening eyes).
Quick ways of stopping application that I have found and that I need to block, are:
- power off phone
- go to Applications Manager and use Force Stop
- other, ROM added ways - as for example, one user wrote, that his ROM lets him quickly stop running apps by long pressing back button
From what I know, blocking any of above is officially impossible. But is it possible with root access?
After doing some research, I didn't found any way to just block application from being stopped/uninstalled, so I have to ask
(ACTUAL QUESTION)
Is it possible (with root access or not) to block user from stopping app in any way? Or at least making it really timeconsuming?
Any help appreciated!
Click to expand...
Click to collapse
With root most things are possible but I would think it would be something that could easily be done..otherwise every malicious app out there would use it to make it hard for the user to stop it from doing what have malicious thing its doing
zacthespack said:
With root most things are possible but I would think it would be something that could easily be done..otherwise every malicious app out there would use it to make it hard for the user to stop it from doing what have malicious thing its doing
Click to expand...
Click to collapse
I guess that you meant "I would think it wouldn't be something that could easily be done"
I don't really know much about possibilities of rooted devices etc., but isn't it that every app has to get some kind of "root persmissions" to perform such tasks? So first any malicious app would need to receive that permission from user.
I am currently having hard time trying to find a way to copy behaviour of (default) Maps application - when it gets Force Stopped (in All tab of Applications Manager) with also stopping all of its services (in Running), it will start running after some time anyway. Anybody knows how thats possible?
Anyway - my real question is - is there some place (like wiki or faq) that one could read about possibilities opened by device rooting? What services, config files etc. can be used or is it that everyone trying to do some knew just have to try everything on his own?
I have been looking around for the exact same thing for a few hours now but unsuccessful. I know its possible to do it without root because an app in the play store called "App Lock" is able to do it. I'm not 100 percent sure but I believe its some sort of broadcast they are filtering. I just dont know which
in app juice defender ultimate you can choose applications which you won't kill
I would try to move the app to /system/app folder and set the permissions to rw-r--r-- using an app like ES File Explorer. Or use Titanium backup and long press and scroll down to 'convert to system app', and make sure to clear data afterwards.
any update on this, i have managed to kill my alarm several times this week. and being late for work is never popular.

Popup dialogs not responsive to taps

I just got this phone last week and I love it...except for this one annoying issue:
It appears for certain apps, when there's a popup window/dialog, I have trouble making the dialog responding to my taps.
For example, I have privateinternetaccess app, when I hit connect, a popup comes up asking if I trust this app, and I cannot tap to check "I trust this application" checkbox.
Another example: when sideloading an apk, the screen shows a list of permissions the app requires and asks me to accept it, but I cannot tap "Install"...
A third example: SuperSU prompt me when an app requests for root, and I cannot make the popup respond to any taps. However, today I discovered that in SuperSU there's a setting to disable tapjacking prevention and when I checked it, it worked! I'm wondering if the other two issues are related.
Anyone else experience this issue? I did search the forum first and so far only http://forum.xda-developers.com/showthread.php?t=1189703 thread sounds like something that's remotely related to my issue and it got 0 replies...
kevinjqiu said:
I just got this phone last week and I love it...except for this one annoying issue:
It appears for certain apps, when there's a popup window/dialog, I have trouble making the dialog responding to my taps.
For example, I have privateinternetaccess app, when I hit connect, a popup comes up asking if I trust this app, and I cannot tap to check "I trust this application" checkbox.
Another example: when sideloading an apk, the screen shows a list of permissions the app requires and asks me to accept it, but I cannot tap "Install"...
A third example: SuperSU prompt me when an app requests for root, and I cannot make the popup respond to any taps. However, today I discovered that in SuperSU there's a setting to disable tapjacking prevention and when I checked it, it worked! I'm wondering if the other two issues are related.
Anyone else experience this issue? I did search the forum first and so far only http://forum.xda-developers.com/showthread.php?t=1189703 thread sounds like something that's remotely related to my issue and it got 0 replies...
Click to expand...
Click to collapse
Are you using lux? There is a known issue with that and the tap jacking feature in su
My God....this was driving me crazy. I installed a different ROM/kernel combo trying to figure it out! In my case, I was only experiencing the issue with the SuperSU popup dialogue. I flashed back to stock and it seems to have fixed it for now. I am using Lux BTW.
I play with my food
zelendel said:
Are you using lux? There is a known issue with that and the tap jacking feature in su
Click to expand...
Click to collapse
That's it! I'm not using lux but I use a similar app twilight. I stopped it and popups are responsive again! It's a pity - I like that app.

Android Permissions - Not able to switch off

Hi all,
Just out of curiosity. I have a 3rd party app on my phone (not available on the Google Play Store, obviously)
I am currently running Android 7.0. When accessing the settings - - > apps--> theApp--> permissions where one can adjust the permissions on demand, I noted that the "Telephone" permission for this specific app cannot be switched off.
When selecting to switch it off there is the usual prompt that the app won't work as intended and I "continue anyway". The slider goes into the off position. Then when clicking back and then opening the permissions, the Telephone permissions switch is back into the on position.
What do you make of this? I have suspected that the app is "spying" somehow for quite some time. Reverse engineering on the apk itself had some very strange permissions logged in the Android Manifest file.
I would really like to hear your opinion....
41 views and zero replies....

Question Trun off additional step after facial recognition?

When I use facial recognition to unlock and app, after my face is recognized, before I can go into the app, I get a screen that is showing a message: "Verified. Tap confirm to continue". I am trying to get rid of that message and avoid the unnecessary extra step to press the confirm button before I can access the app. I am told by an app manufactured that it is a setting on my Samsung S22 Ultra with Android 12. But I am coming from an old Pixel phone and cannot find this setting on my new 22Ultra. Can someone direct me to the setting to turn off that extra step after facial recognition works? Thanks!
Sounds like you've installed some 3rd party app that does this. The default S22 behaviour doesn't show this message.
I can see you asked on other fourms, and they suggested things I was going to say. But it seems like some third party app is either doing this, or enforcing it.
the_scotsman said:
Sounds like you've installed some 3rd party app that does this. The default S22 behaviour doesn't show this message.
I can see you asked on other fourms, and they suggested things I was going to say. But it seems like some third party app is either doing this, or enforcing it.
Click to expand...
Click to collapse
Yes I posted on another forum but no solution there yet, just a few good suggestions that don't work. I don't have any other apps that enforce this behavior though. And I pressed support at RoboForm pretty hard about it and they insist it is not something in their app even though RoboForm is an app that it happens in. I am thinking it is when certain 3rd party apps are opened using face recognition, the Android system does not acknowledge those apps for some reason and pops up the message to do a 2nd confirmation before it will allow the apps to open. Thanks for the reply.
Have you tried unistalling Roboform to test if that fixes it?
I have found a few other apps that call up the exact same message so it is not just Roboform. I did uninstall and reinstall Roboform today for another reason and called up a health record app that does the same thing. It happened in the health app even with Roboform uninstalled.
I think we have determined that it is a system message. An app may call it up or trigger it when using face recognition but it is not generated by the app itself. If we knew what it was called then it would be easier to track it down. within Android or the Samsung settings. if it is even in the settings somewhere.
Yea, it's likely going to be a system message, that is called by certain apps in certain circumstances. But the only way you'll find it is to remove apps a few at a time until it stops appearing.
I get the same message and have looked everywhere for a setting. It doesn't exist. Pretty stupid behavior for sure.
Is there a solution? I have the same thing with Microsoft apps. So stupid..
Try: Settings, Biometrics and Security, Face Recognition, And untick: Stay on lockscreen until swipe.
For me, double tapping the screen or using the power button to wake the phone, triggers the face unlock which then quickly unlocks the phone with no other input.
Is this just one app, or all apps?

Categories

Resources