Search results

Yes, the notification will stay. Turning the gesture off doesn't disable the service entirely, it simply removes the sensor listeners. It's meant to conserve battery, not kill the app entirely.

R210GLU0AQC6 seems to be the latest in February 2018, it's mentioned in a French blog post here: https://infos2technos.blogspot.com/2018/02/comment-brancher-la-samsung-gear-360-2017-street-view.html?m=0, whereas the blog post that gave me a lot of firmware info here...

The keyboard gate relies on the system and keyboard reporting events when it's in use. Android does not provide a way to know when the keyboard is open from a background service (and didn't even for a foreground app until last year either), this is the best it can do.

That seems to be something specific to Samsung's Android framework rejecting it. Nothing I can do, sorry.

Seems fine, similar to mine. Only thing I did potentially differently was to wipe when updating, seems pretty overkill to wipe just to have a change of fixing something like this though.

OneUI Home may be the QuickStep/Recents provider on Samsung phones so it'll be running for that even if you don't have it as your launcher

Strange because my daily is a 7T Pro on 11 and I've found it better on 11 than it was on 10. I always had issues with apps being killed on 10, high memory usage of Android System, SystemUI and the Galaxy Watch app mostly seemed to be to blame, but on 11 it's dropped massively and I don't have...

You shouldn't get app not installed unless the app is either not compatible (which I've never seen for accessory manager, it's compatible with non-Samsung devices) or if it's already installed but doesn't like the APK you're trying to install of it. Try installing one or all of the APKs over...

What version is already on your phone?

Not a lot I can do about Samsung's own apps not being compatible with their own phones. Did you get the APK from APKmirror?

Ah ok I can retract this now and change it slightly. There is no change that would make a difference if OEMs gave a damn. https://dontkillmyapp.com/samsung Read the bit at the top. That's why. **** you Samsung.

Something very low, like 0.00001

Use Tasker for that. It'll probably need root though, unless something has changed (apps haven't been able to toggle mobile data without root since Lollipop last I checked)

You can set a custom sensitivity in the advanced settings

Yes, there is no difference to how the services are used that would make it worse, it should only improve it.

New version (v3.2) in the first post with support for Android 11 and the ability to select which apps are marked as sensitive when the hide sensitive notification content option is enabled

New bug fix release in the first post & in-app update:

The update modding isn't designed to allow downgrading, I don't even know if downgrading will work or whether it'll cause a brick. The option to choose firmware from a list is to pick which one you want to upgrade to, if you are on a version older than that.

Do you have access to a PC for ADB logcat or the ability to dump the logs during the time it's searching for an update? It dumps the version info to the logs and I wonder if my guessed version (0.85) might actually be too low for the 2017 camera to see it as an update.

If you go into the mod settings you can set which firmware you want to download, which will force it to download R210GLU0ARB2

C200GLU0AQK1 is the latest version for the 2016 camera. Are you using a 2016 or 2017 model?

Yes, no idea the cause. I don't have a Samsung phone to debug on. Possible that one of the fixes suggested by someone on GitHub (to ask for the display over other apps permission and draw a 1x1 pixel outside of the screen bounds) may fix it on Samsung devices too as Samsung themselves use that...

You don't actually need the phone to capture images or view them on a PC. You can do all the capturing on the device and just put the microSD into a PC and use the ActionDirector software to stitch images (or other available software).

No, 0.91 would be 0.9.1 which would be a bug fix. Going from 0.9 to 0.10 (while in the past still having 0.1) is very common and standard in open source software.

Yes.

Sounds like a corrupted download, just download the APK again from GitHub

Pixel 3 I'm fairly sure has one as the original Columbus supports the 3 XL and they have the same CPU, it wouldn't have been supported otherwise (like the 2/2XL isn't) I've never managed to find a proper list of exactly which CPUs have them, or I'd have baked a check into the app.

New Release: 0.10 Beta Changelog: APK is available on GitHub or in the first post as usual. Hopefully this is the last major release before it can go to stable. I expect to have to fix some minor issues that I have not been able to find when testing the rewrite, so if you find a crash please...

The split screen command is handled by the system, I can't fix this unfortunately.

Works absolutely fine on my 7T Pro on 11 though. I have no idea what is causing the seemingly random problem for some.

Most likely because of how Android handles launching things, as the app is already open I'd have to declare all launches as a "new" task to fix this, but in doing so that would cause other apps to launch weirdly.

This is not the fault of the app, it is always the system killing, there is absolutely nothing I can do about OEM skins killing everything left right and center in the name of "battery optimisation". Make sure you have absolutely definitely followed all of this: https://dontkillmyapp.com/xiaomi...

No, it needs root. Shell does not have the required permissions to change sys properties.

First, check you don't have the display off gate enabled. Then, disable all the battery optimisations for the app.

Cheers. Known bug, fixed in next version. Caused by MIUI being MIUI and breaking stuff.

The setting you are looking for is Settings.Secure.doze_always_on. settings put secure doze_always_on 1 will turn it on settings put secure doze_always_on 0 will turn it off. Both of these still require the sys prop from the OP though of course. They also don't take effect immediately, you...

Reboot.

Yeah it's pretty terribly optimised. Not particularly surprising as it's unfinished (and it's OnePlus). It might be possible to repurpose the Tasker task I made a while back which did help when using an earlier version of OPAodMod before it was built into the module...

It will not work on Oxygen 11. The whole ambient display system has changed. Use the system AOD per the instructions two posts above yours.

It retains the settings. The flag only controls whether it shows in the settings and actually works, the saved settings would stay even if you disabled the script (it just wouldn't show)

Yes. It moves all around the screen, much more than the Pixel one

Custom sensitivity is already available in the advanced settings. Set the value as you please.

It turns off automatically when it's in your pocket, but for DnD you probably would need to find the setting that controls it and toggle that

Post the logcat, I can't do anything without that.

Agreed, maybe it'll come with the often-teased Xposed style injections one day

You can, but Magisk isn't really built for modules to do tiny things like this. One liners are what service.d scripts are for.

Contrary to what OnePlus have said, the code for the Always on Ambient Display is in the first beta of Oxygen OS 11. All you have to do is enable the feature, which is disabled in the "OPFeatures" framework. This is very simple, and can be done in two lines in a root terminal (ie. do "su"...

Not sure what to suggest with that tbh. It's clearly connected but something deep in the app isn't seeing the camera.

It does have the new AoD actually, if you enable it. Run this in a root terminal: setprop sys.aod.debug_support_always_on 1 pkill systemui Now the option to enable it will appear in the settings.

That's always been the case on more recent versions, it's something database related that I never figured out. If you download photos you can view them in Google Photos as an alternative.