I get the pin and unpin options showing up, but they don't seem to do anything. If I pin a notification and then open it, it still gets removed.
I'm running c-rom 6.6.
I'm running c-rom 6.6.
The goal is to keep you from accidentally removing them, not keeping them forever.I get the pin and unpin options showing up, but they don't seem to do anything. If I pin a notification and then open it, it still gets removed.
I'm running c-rom 6.6.
I/Xposed ( 658): java.lang.NullPointerException
I/Xposed ( 658): at com.germainz.pinnotif.XposedMod$2.beforeHookedMethod(XposedMod.java:164)
I/Xposed ( 658): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)
I/Xposed ( 658): at com.android.server.NotificationManagerService.enqueueNotificationWithTag(Native Method)
I/Xposed ( 658): at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:101)
I/Xposed ( 658): at android.os.Binder.execTransact(Binder.java:351)
I/Xposed ( 658): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
I/Xposed ( 658): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
I/Xposed ( 658): at android.os.Binder.execTransact(Native Method)
I/Xposed ( 658): at dalvik.system.NativeStart.run(Native Method)
Does it happen for a specific notification? Are you using another Xposed module that alters the long press menu (XHaloFloatingWindows or ViewInPlay)? Does the Xposed log show anything?It s randomly stopping working. Sometimes I get the pin option and sometimes I don't. I'm aware that persistent notifications won't get the pin option. But cleanable notifications too don't get the pin options sometimes.
I'm running stock 4.4.3 on a Nexus 5.
Does it happen for a specific notification? Are you using another Xposed module that alters the long press menu (XHaloFloatingWindows or ViewInPlay)? Does the Xposed log show anything?
Use Play Store link in App info 1.0 from qwerty12 instead of ViewInPlay 1.0.8.Yea, possbly ViewInPlay was the issue. Disabled notification shade option in that and Pin returned. I wish both could work together.
Use Play Store link in App info 1.0 from qwerty12 instead of ViewInPlay 1.0.8.
Me too, but I returned to it from ViewInPlay, because Play Store link in App info works without any problem and it has much smaller footprint than ViewInPlay.That's the one I was using previously. That gives the play store link only in the app info page.
I use Play Store link in App info and have App Info link in both places too.ViewInPlay creates a link in Notification shade and recent apps screen too.
Added:Simply outstanding work! This is the fourth GermainZ Xposed module that has earned a permanent place on my phone (out of only 11 total that have earned such distinction).
SUGGESTION: Revise the OP to state something like:
“This will not prevent notifications from being cleared by the application when you click on them. It simply prevents them from being cleared when you click 'clear all'."
WHY DO I SUGGEST THAT:
The average non-sophisticated user (like me), relates the word “pinned” to things like pinning an app to status bar in windows or pinning a post to the top of a forum....or even in the old days pinning a paper note on a corkboard. In all those cases, it stays pinned there until you deliberately unpin it. You have explained several times in the thread already why that’s not the case for notifications, but I’ll bet you’ll be answering that same question again and again if you don’t put it in the op. I read where you said "to prevent accidentally clearing", but that didn't tell the whole story for a simple minded person like me who expected it to remain pinned until deliberately unpinned.
Thanks again for all your great modules.
This will not prevent notifications from being cleared by the application when you open them, and the application can still control the notification at any time (including clearing it). It simply prevents them from being cleared when you tap the "clear all" button or when you try to swipe them away.
No, I don't see any other method that doesn't make it overly complicated.@GermainZ
Can you change adding method?
Because I like Pinned Notifications, but I more like ROMs features....
1.3:
1.1:
- Compatibility fixes for 4.1.x and LG devices.
1.0:
- Compatibility fixes for pre-4.3 devices.
- Don't fail when the notification contains large data (e.g. large icon.)
- Other crash fixes.
- Initial release.
I need your SystemUI.apk as well, please. It's usually in /system/app/ or /system/priv-app/.Unfortunately, System UI has stopped. - Still doesn't work on SGNII 4.1.2 if I select App Info instead Pin/Unpin.
Pin/Unpin works.
Is it enough?
Alright, try the attached build and let me know if it works. If not, I need a log as before.
I'll look into it once the compatibility bugs are fixed.It might be cm specific. I'm on beanstalk but I know it isn't on the new slim (or wasn't a while back).
I'd just like to let the dev know that I spent the last 2.5 hours attempting to recover my device which was stuck in a loop of "Unfortunately, system UI has stopped" messages every 2 seconds.
I was about to perform a factory reset and repeatable flash my entire ROM, but thankfully I doubt a way to disable this module from TWRP. Even so, I had to go through a series of file deletes and a couple dozen reboot cycles to determine that this module was the one causing problems.
This message is also for anyone that happens to stumble upon it before enabling this module to spare them stress. I am on a rooted OnePlus One with TWRP on COS 13.1 based on Android M and Xposed Framework v85.
If the dev could please write a note in the module description warning about boot loops on Android M, I think that would be great. Thanks.