yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] pixeltech.dev:
What do you mean by open notification in xhalo?
[Xposed Framework Modules] __Michael__:
Yep unchecked

Sometimes it dismissing , but most of the time it just clear the notification
[Xposed Framework Modules] txx3:
a great way to interact with notifactions, here check this video

https://youtu.be/n-DFPKg-RWk

there are notification apps that use this xposed Module and it's great!

notification comes in --> tap on it ---> window with full app opens (just like on windows) --->do your task ---->close it ..done! without leaving the app that u were running before!

!real Multitasking! [emoji7]

thx
[Xposed Framework Modules] pixeltech.dev:
Thanks for pointing this out, we'll learn more about it and see what we can do :)
[Xposed Framework Modules] pixeltech.dev:
Hi all,

version 1.8 is now ready for install from Google Play, Xposed repository or from the first post of this thread.

This version includes:

Fixed WhatsApp mark as read

Fixed Hangouts mark as read

Logs to better understand SystemUI crash for some users

Fixes and improvements

We are also working on a new version with support for Gmail, Inbox and Google messanger, we hope it will be ready soon.

If you like this module, we would very much appreciate if you take the time to click Thanks, rate this thread or rate the module on Google Play.

Also, we would very much appreciate any feedback, questions or new features suggestions.

Enjoy :)
[Xposed Framework Modules] liranco:
Hello.

What the leat version of whatsapp this mode is work. Because I use 2.16.4 and this mode dosen't work fine
[Xposed Framework Modules] Portgas D. Ace:
[MENTION=4454053]pixeltech.dev[/MENTION]

Thanks for the update. Unfortunately, "Mark as read" does still not work for Whatsapp v2.16.4 (downloaded from official Whatsapp webpage). Do you need a log file to solve this issue or is this a known issue?

EDIT: I see that the same issue has been reported before (see previous post).
[Xposed Framework Modules] D-m-x:
They said they are just supporting Official Versions from Google Play Store (Non Beta). Makes quite a lot if sense since Whatsapp is pushing Releases every other Day. It's understandable they can't support every new Beta.

Gesendet von meinem Nexus 6P mit Tapatalk
[Xposed Framework Modules] Portgas D. Ace:
Must have missed this part. Thanks for clarification.
[Xposed Framework Modules] piquadrat:
The main problem I have with this app (a deal breaker in my case) is that it is not working correctly when the multiple notifications events occurs and the notifications is being stacked. In such a case the rules engine misbehaves. I'm using it right now to assign a different sounds to different emails messages by "title".

The problem is: the first notification triggers appropriate sound correctly. But then if the user do not dismiss this notification the second identical one does not produce desired sound but the original sound (no rules matched) is being played. If you see the messages history it becomes pretty obvious why that happens. The second notification is being seen by the Xnotifications as having title "2 unread mails" not the original title. The body of this notification is also not related to notification number 2 body as it consists of the titles of two previous notifications.

That makes almost impossible to make a reliable notification systems as sometimes a "title" is a part of a "body" and adding additional rules with "body" filter generates false positives.

More... the same design flaw resulting in "body" filter permanent failure. Only the first notification body can be scanned for a keyword reliably.

The message from application should be intercepted before it it being stacked. Right now this renders the app unusable.
[Xposed Framework Modules] Hackills:
Works fine with version 2.12.556
[Xposed Framework Modules] Shawn2shine:
Being able to enable/disable heads up globally for notifications at my desire/automatically via tasker plugin would be a really cool feature although there doesn't seem to be much talk about it here.
[Xposed Framework Modules] pixeltech.dev:
Hi ,

You can create a rule for each scenario instead of trying to compose a "golden" rule. then, in any scenario the matching rule will be applied and the other ignored...
[Xposed Framework Modules] pixeltech.dev:
We're not so familiar with Tasker, we plan to learn it and see how we can add support for it
[Xposed Framework Modules] piquadrat:
No, I can't. If you have two messages A and B with titles respectively: Title_A, Title_B and identical bodies: Body_A=Body_B="Body" and you set a rule for message body and looking for keyword: "Body" your program match this rule only once. And there is no way to make it match more. Why? Because XNotification sees the second message as having title="2 new mails" or something similar depending on the app sending message (but not "Title_B" !) and having body="Title_A(enter)Title_B" not "Body"

So you can't get access to the second message body at all. How can you set any working rule for it? It is lost in the process.

I know that all this may look like some made-up problem but it isn't. Just make an experiment. Set a rule for body and then send two identical messages matching rule without dismissing/clearing first message. You see, only the first will trigger appropriate action (let it be sound). The second one (and all the following) won't.

And if you try cover this situation with a separate rule you quickly realize you can't.

And the same applies to titles. You can try to "catch this rabbit" with an additional rule looking for title in the body but that firstly: generates false positives secondly: there are apps like AquaMail for instance which does not put titles into messages body while stacking, well at least not in a way XNotification can decode properly. Aquamail is the worst case scenario. Even title rules won't work there.
[Xposed Framework Modules] pixeltech.dev:
You can create a rule that looks for both title and body matches, and in general if notification A differs from notification B, you can create a unique rule for each of them
[Xposed Framework Modules] lukakas:
Is there any ETA for this? I'm so hyped, sorry ^^.
[Xposed Framework Modules] pixeltech.dev:
Hopefully next version
[Xposed Framework Modules] piquadrat:
And these rules will work unless both notifications are being stacked. If you do not dismiss notification A before notification B arrives Android will contract/merge both notifications and form a notification with title "2 new messages" and body "notification_B_title (enter) notification_A_title" instead of notification B.

If you are not intercept notification before they are being stacked you are loosing notification B body as android replace it with new body built of titles of previous notifications.

Just make an experiment and you will see. Use for instance Aquamail or K9 based mail client. The goal is to change a sound of a new mail if the beginning of the mail contains arbitrary word let it be: success. If it doesn't contain "success" leave the default sound.

This is how XNotification sees the first mail notification:

The word success is visible as the content of notification. And below is how XNotification sees the second mail notification if the first one wasn't dismissed:

As you can see title has changed and Content does not contain word "success" even if both email had the same text inside (one word: success).

Tell me how to build a rule set to cover this example considering our goal which I made in bold above?

And the app will behave exactly the same for all cases not only this particular email client. Just test it and you will see. This is how android deals with multiple notifications going from the same app. You have to intercept notifications before they are being stacked.

Besides you see that XNotification does not intercept a content of a second notification properly. It should contain a second line: "rTorrent Rpi: Notification A" below "rTorrent Rpi: Notification B"
[Xposed Framework Modules] Fuzark:
How the module is behaving with the latest update on Google play of whatapp 2.16.13 play?
[Xposed Framework Modules] pixeltech.dev:
Basically we can create rules only based on notification parameters (you can leave some blank BTW). So of course, rules flexibility is dependent on notifying app. Anyways, we'll look into it and see if it can be supported.
[Xposed Framework Modules] pixeltech.dev:
We don't check it on beta versions as they are updated on a daily basis (sometimes hourly) and many times contain incomplete features. Is 2.16.3 beta or formal?
[Xposed Framework Modules] Fuzark:
Yeah! I always check xn topic, I read about it.. But it's formal. Update today on Google play. 2.16.13 v.

I'm asking, cuz I prefer xn way of things and ill wait to update whatsapp
[Xposed Framework Modules] pixeltech.dev:
This is the version we have, it works as should
[Xposed Framework Modules] d0nald01:
can you create a rule only to show the notification if content = "TEXT"? and hide everything else
[Xposed Framework Modules] pirasalbe:
Hi,

Could you add a feature that group notification from the same app in a unique notification???
[Xposed Framework Modules] GioKupreishvili:
Hello All, Can Anyone Tell Me Is There Xposed Mode Which Only Have "Mark As Read For Whatsapp" I Don't Want To Install XNotification. Or Is There Any Way To Bring "Whatsapp" Function From XNotificatio App? I Saw Other Module Which Was In Gravity Box And Someone Bring "Fullscreen Call Picture Function". Maybe It Is Also Possible To Do It For Whatsapp Mark As Read From XNotification. Sorry For Bad English.
[Xposed Framework Modules] pixeltech.dev:
If "TEXT" is contained then yes, if you want an exact match then not yet...
[Xposed Framework Modules] piquadrat:
I want to encourage you to do some testing with AquaMail as it is a very popular and I think the best free mail client for android. And just as I told before the problem is not the first notification but the second, third and so on if notifications were not being dismissed causing android to stack them.

In this situations you get something like this:

[IMG="Screen-Aquamail"]http://s27.postimg.org/4oislhh1f/S60407_221653.jpg[/IMG]

No useful information is being extracted in this case. Nothing about the mail which was received as a second in order. No mail subject, no sender, no body preview, only mail address of the inbox.

The thing is that programs like Flotify can reverse this message stacking mechanism and extract the info about the second mail received. So that should be doable.
[Xposed Framework Modules] aryayush:
Bug report: With XNotifications enabled, most of my WhatsApp notifications appear for a second or two and then get dismissed automatically. I’ve even disabled the preference that clears the notification when you swipe away the heads up display, but am still facing the same issue.

Feature request: When you tap on the Quick Reply button, the text field should be selected and the keyboard should come up automatically. Most of the time, I want to type in my reply, and having to bring your thumb up to the small text field takes time and you’re always in danger of hitting one of the predefined templates.

Thank you for making this fantastic module.
[Xposed Framework Modules] ChefChaudart:
Hello,

Can i prevent notifications to be displayed on lockscreen ?

Envoyé de mon ONE A2003
[Xposed Framework Modules] pixeltech.dev:
Hi all,

version 1.9 is now ready for install from Google Play, Xposed repository or from the first post of this thread.

This version includes:

Added mark as read for Google Messenger

Fixes and improvements

We are also working on a new version with support for Gmail and Inbox, we hope it will be ready soon.

If you like this module, we would very much appreciate if you take the time to click Thanks, rate this thread or rate the module on Google Play.

Also, we would very much appreciate any feedback, questions or new features suggestions.

Enjoy :)
[Xposed Framework Modules] piquadrat:
I would really appreciate "Mark as Read" feature for Gmail if you planning to support it.

And LED Notification control.

Two most important features IMO.
[Xposed Framework Modules] huladaddy:
Is it possible to use this module to disable "heads up" and instead have the older "ticker" style of notifications to be used instead on CyanogenMod 13 Marshmallow? If not, could I request that as a feature.
[Xposed Framework Modules] Reechings:
Thanks for this. Would you be able to add option for Mark as Read for AOSP/CM messenger/messaging? Thanks!
[Xposed Framework Modules] theoverseer:
I've downloaded the newest version from the play store (1.9), but cannot see the option for Messenger. I can only see WhatsApp and Hangouts...
[Xposed Framework Modules] SyCoREAPER:
[MENTION=4454053]pixeltech.dev[/MENTION]

Same here, was about to ask if there is anything we need to enable somewhere first
[Xposed Framework Modules] jolas:
In new message heads up, there is option to mark as read.
[Xposed Framework Modules] theoverseer:
I'm not seeing that.
[Xposed Framework Modules] SyCoREAPER:
Screenshot or it didn't happen. I find it hard to believe that it is there but only working for 1 out of 3 people.
[Xposed Framework Modules] jolas:
:p
[Xposed Framework Modules] SyCoREAPER:
Fantastic, lucky you :crying: . That is very strange. Do you have an option in XNotification Settings? Also what version of Messenger do you have?
[Xposed Framework Modules] jolas:
No there is no option regarding Messenger, in xnotification settings.

I'm running Messenger 1.8.035 (2737319-34.phone)
[Xposed Framework Modules] SyCoREAPER:
Hmm. Thanks

Wonder if its the version. Not sure what the -xx.phone is. Not sure if that is part of the version or if it defines the DPI similar to Play Services.

Mine is 1.8.035 (2737319-44.phone)
[Xposed Framework Modules] jolas:
You are right... look at the link below

http://www.apkmirror.com/apk/google-inc/messenger-google-inc/messenger-google-inc-1-8-035-release/
[Xposed Framework Modules] Xhatry:
The idea of the module is great, and it works perfect except for two things. I have a Moto G 3rd Generation (2015) and Android 6.0, and sometimes the module crashes the ui and I must unlock the device to continue working on what I was doing. Also, it is not compatible with the module XGPM, even if everything is disabled in the XNotifications settings. When I try to play a song with both modules activated, it says that Play Music has stopped working.
[Xposed Framework Modules] Reechings:
Both modules work fine together for me.
[Xposed Framework Modules] Xhatry:
Maybe there is something wrong using Android 6.0 and both modules... I have the latest version of both modules.
[Xposed Framework Modules] rdoane:
I have a quick feature request. Would it be possible to add an option to swap the "Reply" and "Mark as Read" buttons for Hangouts notifications? This would make the actions in line/similar with Inbox's. Thanks in advance!
[Xposed Framework Modules] aryayush:
Am I the only person whom this module doesn't work for? With it installed, WhatsApp notifications show up for a split second, if they happen to come in while I'm using the phone, and then disappear. Most of the time, since they show up while the screen is off, I miss them altogether. Sometimes, but not nearly often enough, they do show up like they're supposed to and I'm able to use the mark as read and quick reply features, which are awesome. I have the option to clear notifications when dismissing heads up disabled. Is there something I'm missing here? I'm using a Nexus 5X running the stock kernel and ROM.
[Xposed Framework Modules] raphTec:
I want to suggest some improvements:

First, I really would like to see an option to disable heads up display for notifications based on notification rules. Example: when the name of a special whatsapp or telegram group is in the the notification title, I do not want a heads up notification when a message from that group arrives.

When additional whatsapp messages arrives in a chat where already some messages are, the notification disappears and is created again with the new message included. Without the module activated, the notification is updated without getting cleared. While the clear and create animations take place, it is not possible to click the notification to open the chat.

When now a lot of messages arrive, the notification is cleared and created very often which makes it hard to open the chat.

It would be great if the module could update the notification text without clearing it.
[Xposed Framework Modules] theoverseer:
[MENTION=4454053]pixeltech.dev[/MENTION] could you look at this please?
[Xposed Framework Modules] Nitrooo84:
This!

Also, would be great if quick reply for WhatsApp would not pause the underlying activity.
[Xposed Framework Modules] FahrenGrade:
Latest PlayStore version of WhatsApp v 2.16.42 has new notification interactions that break the module.

Would the dev like a log?
[Xposed Framework Modules] SyCoREAPER:
[MENTION=4454053]pixeltech.dev[/MENTION]

Any update on this? Still running official version (non-beta)
[Xposed Framework Modules] Nitrooo84:
Just noticed that "All notifications clearable" option breaks GravityBox's progress bar in the statusbar. When on, you can't see the line in the statusbar, when turned off, the line is drawn again.

Nexus 6P, stock Marshmallow MHC19 rom, Elemental X 1.16
[Xposed Framework Modules] lokkiyo:
Have the same issue on my Redmi Note 3 Pro with MIUI.

I tought it was something related to the ROM, but should be a problem with the module itsel. :(
[Xposed Framework Modules] SyCoREAPER:
Have not heard from DEV in a while. Feeling a little abandoned, especially after having spend money for full features.
[Xposed Framework Modules] piquadrat:
+ 1
[Xposed Framework Modules] aryayush:
Well, fifteen days is not that long. Hopefully, they're just busy.
[Xposed Framework Modules] amandreamartino:
I'm very disappointed at this module. Almost every user request was replied with "we will take a look". Still no Telegram support.
[Xposed Framework Modules] latino147:
Floatify works with Telegram
[Xposed Framework Modules] pixeltech.dev:
Hi all,

sorry for not responding for a while... we had some technical issues that prevented us from responding.

Regarding WhatsApp interaction: As far as we are aware of our module works well with latest formal version of WhatsApp.

We refer to version 2.16.13 as this is the latest we have. If you have problems with other formal versions of WhatsApp please let us know.

Regarding Google Messenger: Assuming you are using latest version of our module, you should see a Mark Read button in the notification.

We forgot to add a setting for enabling / disabling this feature but it should be enabled by default. In any case - we'll release a version with the settings in the following days.

Regarding feature requests: Not all features can be implemented easily - some features are very hard to implement without causing bugs in the affected app, which obviously was not coded with those features in mind. We can only release features that are stable and maintainable. This means that for some apps a feature request will take long time to implement - assuming it is possible.

Regarding co-existing with other modules: This is how xPosed works, and if two modules target the same methods in the same apps, they are likely to affect each other.

If you have such specific issues please let us know and we'll see if we can work around it or add a setting for completely disable this specific feature in our module so that the affected module can work, leaving you with the decision of which module you prefer.

Regarding SystemUI crash: We added additional logs for this issue, but this is often caused in manufacturer-specific variations of SystemUI. if you encounter this crash, please make sure to contact us at taptigo.dev@gmail.com with the followings:

Debug log from our module

Logcat filter filtered by AndroidRuntime

Logcat filter filtered by SystemUI

Logcat filters can be taken using CatLog or MatLog.

For any other issues, questions or points we missed please contact us. If we seem not responsive - this is probably a technicality, so you can also contact us at taptigo.dev@gmail.com.

Thanks :)
[Xposed Framework Modules] Portgas D. Ace:
[MENTION=4454053]pixeltech.dev[/MENTION]

WhatsApp 2.16.57 is currently the latest formal version, at least in Germany. Downloaded it from Play Store. And your module does not work with it anymore as WhatsApp introduced Quick Reply functionality, I guess. Could you have a look?
[Xposed Framework Modules] pixeltech.dev:
Yes, as soon as we get it. What if you disable our "quick reply" feature in the module settings?
[Xposed Framework Modules] Portgas D. Ace:
Already disabled the quick reply setting, still the "mark as read" function does not work. Seems that the changes to make the native quick reply work has altered the code quite heavy.
[Xposed Framework Modules] aryayush:
The developer got back to me after communicating with them over email and resolved my issue. It was enabling the "ungroup notifications" setting, perhaps in conjunction with having a Mi Band paired with the phone, that was causing WhatsApp notifications to disappear immediately upon showing up. Disabling it fixed the issue. Cheers.
[Xposed Framework Modules] pixeltech.dev:
We should get the update today and then check it's effect and what should be aligned with it. You can contact us at taptigo.dev@gmail.com for the rest of this issue handling.
[Xposed Framework Modules] Teblakuda4o4:
Gonna try this module, it look very useful
[Xposed Framework Modules] paborges:
Just to Confirm, module not working after last whapp update here as well
[Xposed Framework Modules] pixeltech.dev:
Thanks, we got the update today - we can also confirm Mark as Read is not working in last update.

We are on it, fix will be released as soon as we can.
[Xposed Framework Modules] raphTec:
Can anyone confirm that there are issues with this module enabled in the xposed installer on ROMs that support the "quick pull down" of the notifications to access the quick settings with one swipe down of the status bar at the very left or right edge?

The issue is not affecting any functionality but it seems to introduce a lag in the pull down movement at the time the top notification is expanded or the stack of notifications is unfolded (I think so, as these are the only things related to this module that I can imagine) or as soon as the quick settings are loaded.

I can't reproduce this properly, although I did a lot of testing with different xposed modules activated. It seems than this module and xprivacy do both introduce a bit of lag and both together produce a bigger lag...

I would really like to know if other users also noticed a kind of lag like I described. Maybe it's only me at all.
[Xposed Framework Modules] pixeltech.dev:
Hi all,

We created a beta fix for Whatsapp version 2.16.57 (should also work on other versions - possibly betas also -but tested on this one). If you want to test it and give feedback, please install from here.

If this version is OK, we'll upload a formal version tomorrow.

Feedbacks will help us a lot, thanks :)
[Xposed Framework Modules] nachomagic:
No working for me, multiple groups to mark as read.

Oneplus one and CM13

Sorry for the lack of log but I'm with my ill baby

Enviado desde mi A0001 mediante Tapatalk

---------- Post added at 07:00 PM ---------- Previous post was at 06:17 PM ----------

Also don't work for a single chat

Enviado desde mi A0001 mediante Tapatalk
[Xposed Framework Modules] PatrickMac:
I can confirm that the beta fix does not work for me. Although I have to say that I am using the beta channel of Whatsapp and am currently running 2.16.67
[Xposed Framework Modules] raphTec:
Does also not work for me with whatsapp Version 2.16.57. Additional buttons in the notification introduced by the module do nothing. Also, group chats are not splitted correctly and create duplicate notifications, which lead to the same chat.

Also the whatsapp update broke support with the whatsappX xposed module, so they made quite big changes I think...