Database Info

Notifications mess with active app when using Pebble, Troubleshooting advice needed

Hi everyone,
Nexus 5 on different recent CM11 nightlies, and Pebble V3R1 on firmwares from 2.4 to 2.6, fwiw.
So I'm using a "Notification Center" app to get notifications to my Pebble smartwatch. The app uses NotificationListener, then filters through custom settings (like "no notifications for app xyz"), then sends the message to the Pebble (or not).
Now whenever I'm having the phone on and an app running, taking WhatsApp with the keyboard up as an example now, and I get a new notification that wasn't previously there (like the first Hangouts message since I last dismissed Hangouts notifications), and the message is not filtered out but actually forwarded to the watch, WhatsApp will behave like when you hit the home button and open it again right away, which means the keyboard will minimize in that case, which is annoying, to say the least. It also happens when I dismiss the notification on the phone from the watch.
I also found out over time that this issue exists for four different apps (had to buy every single one :victory: ) from independent developers. I contacted two of them personally and none of them has a clue what to do or is able to reproduce the issue. Also no one else seems to have reported this one.
There are options to work around the problem like disabling notifications being sent to the watch while the phone screen is on, but that's not convenient, because I enjoy having those notifications on the watch while using a fullscreen app, for example. But I'm really out of ideas as to where to look or who to talk to to get a step further with this weird issue.
Also I can not reproduce it using other NotificationListener apps, like tasker + relevant plugin to execute some stuff.
If anyone had really any input, like how would I go about finding out "who" actually messes with the active app, or anything really, I'd be grateful.
Thanks, Silkey
Edit: And just minutes after posting I find another one: whenever opening or closing the main menu on the pebble the exact same thing happens. I guess I'll have to take this one over to the pebble developers. I'll leave this here though if I may, maybe someday someone will experience this too and stumble upon this thread.
Edit2: With the first edit and some help on IRC we were now able to be 100% sure it's an pebble issue. Sorry for this one, I guess.

[HELP NEEDED] Some apps not installing, can't click "Next"!??

Friends, Android user of 10 years. Never seen this issue, EVER. Came over from an Axon 7 yesterday. Here's the situation.
Mate 9 US Version B138
Not Rooted or altered AT ALL
Unknown sources is checked in Security
Developer Options enabled
No screen dimmer apps
Blue Eye filter disabled and enabled when this happened
Basically, when trying to install some apps via a File Manager, not the Play Store, some apps are installing like any other would, while others are not letting me click the "Next" button during the installation process. No errors, no other indicators of why? "Cancel" button works fine. While some other APKs even the "Next" button works and everything installs fine.
Like I said... I have never ever seen this weird issue before. The closest was when I had a non root blue light filter app on and the "Install" button wouldn't work, no errors, no other indicators.
Can someone please help? Have you seen this issue before?
Thanks!

Anyone? Thanks guys!

ProFragger said:
Anyone? Thanks guys!
Click to expand...
Click to collapse
Touch screen sensitivity issue? It happens sometimes, sometimes I think my device is frozen because my tap is not registered several times in a row...

goranimo said:
Touch screen sensitivity issue? It happens sometimes, sometimes I think my device is frozen because my tap is not registered several times in a row...
Click to expand...
Click to collapse
Thanks brother, but that wasn't it...

[SOLVED]
For anyone else who may face this issue, here's the solution:
It's similar to the screen dimmer/blue light filter issue. Basically, I was using a custom theme that was skinning the Package Installer. Somehow, the system must have seen this as "drawing" over the application and therefore disabled any app installations. That still does not explain why some APKs were installing, but this is good enough. The fix is to revert to stock theme and install your APK then.
Thanks to anyone that tried to help!

I had the same problem with a theme yesterday - went back to stock because of it. Kind of annoying

jayb082 said:
I had the same problem with a theme yesterday - went back to stock because of it. Kind of annoying
Click to expand...
Click to collapse
I hear ya bud! Even scarier, this issue is not documented anywhere, hope this post helps others! Have you seen this issue with EVERY theme?
Thanks for your input!

I have been having trouble finding themes I like - I like dark themes but then they look terrible in the email app (everything dark except the email body is colored or white which looks bad). Finally found the BWM black & white theme I liked and that had the installer problem. For now, back to stock.

Is it possible that those failed apps needed much more free space on your mobile?

This issue actually occurs if you have any screen filter apps installed in your device. Some apps that are known to cause the apk file installation problem include Twilight, Screen Adjuster, Easy Eye, Darker and Blue Light Filter.
In addition, any persistant overlay may prevent usage of the "install" or "next" button when installing an app from the SD card. Chat heads, floating battery stats, etc are all possible culprits.
This is a safety built into android to prevent an app from popping up an overlay over the required permissions list and showing a "safe" list of required permissions on top of the real list of persmissions that allow it to read your texts, pick your wallet, and root around in your underwear drawer.

goranimo said:
Touch screen sensitivity issue? It happens sometimes, sometimes I think my device is frozen because my tap is not registered several times in a row...
Click to expand...
Click to collapse
James_Watson said:
Is it possible that those failed apps needed much more free space on your mobile?
Click to expand...
Click to collapse
James_Watson said:
This issue actually occurs if you have any screen filter apps installed in your device. Some apps that are known to cause the apk file installation problem include Twilight, Screen Adjuster, Easy Eye, Darker and Blue Light Filter.
In addition, any persistant overlay may prevent usage of the "install" or "next" button when installing an app from the SD card. Chat heads, floating battery stats, etc are all possible culprits.
This is a safety built into android to prevent an app from popping up an overlay over the required permissions list and showing a "safe" list of required permissions on top of the real list of persmissions that allow it to read your texts, pick your wallet, and root around in your underwear drawer.
Click to expand...
Click to collapse
Hey James, thanks for your thoughtful responses. No I definitely have a lot of space, and to your point, this problem is famously known with other phones and with the "Install" button. But two things make it unique:
1. Huawei calls their install button "Next" so this is hard to find a Google solution to.
2. I don't have any of those apps you mentioned, otherwise I would have solved that issue right away. The culprit here was a theme an .hwt file... So that's why I was struggling to find an answer...
Thanks again!

ProFragger said:
Hey James, thanks for your thoughtful responses. No I definitely have a lot of space, and to your point, this problem is famously known with other phones and with the "Install" button. But two things make it unique:
1. Huawei calls their install button "Next" so this is hard to find a Google solution to.
2. I don't have any of those apps you mentioned, otherwise I would have solved that issue right away. The culprit here was a theme an .hwt file... So that's why I was struggling to find an answer...
Thanks again!
Click to expand...
Click to collapse
Another clue for your reference.
As I know, Huawei mate 8 has a feature which is some like those "Bluelight Filter for Eye Care" apps.
Settings - Display - SCREEN - Eye confort.
So, is there this stock blue light filter feature on your phone? If yes, is it possible that the issue resulted from this feature enabling?

James_Watson said:
Another clue for your reference.
As I know, Huawei mate 8 has a feature which is some like those "Bluelight Filter for Eye Care" apps.
Settings - Display - SCREEN - Eye confort.
So, is there this stock blue light filter feature on your phone? If yes, is it possible that the issue resulted from this feature enabling?
Click to expand...
Click to collapse
Yes it exists in the Mate 9 James, and of course I disabled or turned it off... The problem was still there... It's the themes, some of them fool the system into thinking a screen drawing is enabled to it doesn't allow for installation. Strangely, my current custom theme is allowing for installation... :-\

I'm having similar issues. The apps I can't get to install are; Anything from Amazon App store underground app. mSecure app, and various others.
2nd: Phone will NOT pair with external Camera that I have...HTC Re-Cam, or LG 360 Camera.
Sent from my MHA-L29 using Tapatalk

I think I solved the issue today.
Using stock theme app, apply the stock EMUI theme. Reboot phone, than try to install applications.
My thoughts:... any non-stock theme being used/applied creates an overlay. So when the "next" button isn't responding (when the next button is at the top of install screen), it's cause the real button is located on the bottom right.
Sent from my MHA-L29 using Tapatalk

Push notifications

The phone stopped getting push notifications until after the app is opened (groupme). Any way to fix that?

No one else had experienced this? It's really bad. No notifications from group messaging apps

yebbey2 said:
The phone stopped getting push notifications until after the app is opened (groupme). Any way to fix that?
Click to expand...
Click to collapse
Go to settings, battery, battery optimization and ensure your concerned app is showing you "don't optimize".
Try this and lemme know

I did that already. I searched and saw that that was supposed to be the solution.....but not working for me

In the same settings there is an advanced optimise (top right ... Button)
Make sure that's not ON

harigavara said:
Go to settings, battery, battery optimization and ensure your concerned app is showing you "don't optimize".
Try this and lemme know
Click to expand...
Click to collapse
Thanks. I have this problem too with some apps. I will try this solution

DaveHTC200 said:
In the same settings there is an advanced optimise (top right ... Button)
Make sure that's not ON
Click to expand...
Click to collapse
Did that too....it's a mystery.

Getting delayed notifications too. Particularly with WhatsApp. Can't work it out.

hallo dare said:
Getting delayed notifications too. Particularly with WhatsApp. Can't work it out.
Click to expand...
Click to collapse
this device faces network drops, often not recognized if an app wouldn't show an alert like FB messenger.
these drops are mostly responsible for missed pus messages because the device is not ready at the moment the push happens and it will not be repeated every few seconds (delay)
even worse if one is using several devices, of which one is i.e. at home and the other on the road. while a the working device will receive the push notification the OP6 would not ( you can check for network drops where it shows the IP number, it happens on wifi as well as data and both wifi frequencies BTW.)
so in the last case the message will never arrive because it's delivered, (to the working device at home) and hence no more push attempt will happen until next message arrives.
i and others posted this in OP support, as mentioned above, open you network settings and watch the IP number, it will disappar and re-appear.
also you can use FB messenger where you will frequently see an orange bar saying "connectin" intermittently with a green bar saying "connected"
of course i dunno if that happens on EVERY device but at least it happens on MANY including mine.
since i'm always having 2 phones on man i'm receiving all mails and messages on at least on of the two which also illustrates quite well how often a push will reach one of my various other devices but miss the OP6.
Go to OP support and report the issue if you face it, that way they get aware of the full scale of the issue.

Yep, notifications are patchy for me. Sometimes they arrive on time, other times they arrive but silently without triggering the alert sound. Other times they only arrive after waking the phone up.
And yes, I've set to not optimise these apps and turned off advanced optimisation. It's a bug I reckon, hopefully fixed in 5.1.6

Well, somehow it's working...for now. I did a few things. I updated the Groupme app. I think I changed the notifications from urgent to high. Something worked

yebbey2 said:
Well, somehow it's working...for now. I did a few things. I updated the Groupme app. I think I changed the notifications from urgent to high. Something worked
Click to expand...
Click to collapse
Yeah I've mine set to urgent also, but no real difference. Simple things at this stage for a company like Oneplus, that should not be an issue

I've been having the same issue. Some apps work fine and some don't give me notifications until I actually open the app and refresh it. One is Power Facebook and the other is my visual voicemail app. It's highly annoying as I use the phone for business too. Disabling then in battery optimizations does nothing.

If you have advanced optimization turned on in Battery settings, it will prevent a lot of apps that need to do things in the background from working. It will definitely affect push notifications. I have it on but I've exempted a bunch of apps I want running.
Oops, n/m, see this was discussed already.

I'm not sure if it was switching the notification from urgent to high that did it but it was the last thing I did before it started working....it did go back to urgent by itself afterwards though...notifications still working now

..guys any other facing this issue? Even after update to pie stable recently.. I get this problem, notifications arrive to every other device except op6. When i unlock the phone only then notification arrives...all battery optimizations are off..
any solutions?

I got the same issue with Threema. None of the mentioned settings worked for me.
Any ideas?

Same problem for me. Super annoying. Is this an oxygen os or android problem? Would installing a custom ROM help?

It's the DOZE feature in android that is causing the delay in receiving notifications. Setting an app to "Don't Optimize" does not help; this used to work on nougat when I was using HTC U11 but this does not work in Oneplus 6 PIE.
Run the command below in ADB to completely disable DOZE.
adb shell dumpsys deviceidle disable
The down side is that it will reset to "enable" after reboot so you will need to run the command, again, after rebooting. To get around this, I use Automagic to execute command "dumpsys deviceidle disable" after reboot. You can use Tasker for this, too.
After disabling DOZE, push notifications are received almost immediately. I often see notification for the same message on both my PC and phone.

ausaras said:
It's the DOZE feature in android that is causing the delay in receiving notifications. Setting an app to "Don't Optimize" does not help; this used to work on nougat when I was using HTC U11 but this does not work in Oneplus 6 PIE.
Run the command below in ADB to completely disable DOZE.
adb shell dumpsys deviceidle disable
The down side is that it will reset to "enable" after reboot so you will need to run the command, again, after rebooting. To get around this, I use Automagic to execute command "dumpsys deviceidle disable" after reboot. You can use Tasker for this, too.
After disabling DOZE, push notifications are received almost immediately. I often see notification for the same message on both my PC and phone.
Click to expand...
Click to collapse
Even using this i still do not get notifications i disabled every battery saving function.. I think it is time for a factory reset

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?

auto boot delay

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!