yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Ex_FallenSkyTear:
can you add tasker integration or compatibility?
[Xposed Framework Modules] Stoutpuppy GFX:
Update 1.5.6-4 working perfect for me

Applied the latest update last night and so far 100%

It even fixed the issue of transparency I was having

Running G3 D855 RR 5.8.5 nougat, xposed framework, & SU

Keep up the great work!
[Xposed Framework Modules] Artieza:
> Wrong symbol displayed in the silent mode toggle.

Give it another try, because it isn't fixed. :confused: Still have icon of enabled silent while it isn't.
[Xposed Framework Modules] DrAcHe981:
If I purchase the tasker app to test it, then sure I can try what I can do, but it's a lower priority on my to-do list than some other bugs that I found

Interesting that this fixed itself without me doing anything

That was addressed to it displaying the symbol for silent mode active when it wasn't active, but on another device I just noticed its using default graphics while the graphics for the sound mode toggle are changed (It seems to want the symbols being set twice in the graphics screen, which isn't how it's meant to be)
[Xposed Framework Modules] Artieza:
Lol, okay, why did you not fix active/inactive shuffle with second issue? :confused: It's a minor fix.
[Xposed Framework Modules] Ex_FallenSkyTear:
yes, i understand it, but tasker have by default option to run a task by app's shortcut...

so, you can just ad this option...

this is only an advice, just for information.
[Xposed Framework Modules] DrAcHe981:
The problem is, displaying shortcuts is limited to launchers, my app can't access them, or at least I have no idea how to get them (already tried it multiple times)
[Xposed Framework Modules] Ex_FallenSkyTear:
this is strange, gravitybox use this way, and isn't a default launcher, but tasker, and others apps, shortcut work greatly...
[Xposed Framework Modules] Artieza:
Tasker doesn't have it. Use AutoShortcut plugin from Joao Dias.
[Xposed Framework Modules] DrAcHe981:
Gravitybox can use shortcuts? Never noticed that, most probably because I never used gravitybox to modify button actions or similar

I guess then I could take a look into the gravitybox source and check out how they do it
[Xposed Framework Modules] NGOwner:
Never mind ... move along.

[NG]Owner
[Xposed Framework Modules] Ex_FallenSkyTear:
i use it, without plugins...

---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------

it can, and i was used it, in a clock shortcut...
[Xposed Framework Modules] Ex_FallenSkyTear:
this is a launcher, but it can be used from gravitybox, for example.
[Xposed Framework Modules] DrAcHe981:
Worked all night for this... But stay tuned, I'm gonna fix some bugs and test a bit (maybe also try to get my translators up X.x)

Probably will be released before the next week begins!

The bottom row in the second screenshot are all shortcuts

And now I need sleep...
[Xposed Framework Modules] Ex_FallenSkyTear:
uh, really thanks...

you can sleep, just for now...
[Xposed Framework Modules] Artieza:
Ups, I thought you want to trigger any action of Neo from Tasker. But you want to push Tasker's commands from Neo. :eek:

It isn't "Tasker integration". It's just shortcuts support.
[Xposed Framework Modules] Ex_FallenSkyTear:
yep, tasker integration is better, but if it's difficult to create, and isn't a priority of developer, shortcut is an accettable solution.
[Xposed Framework Modules] halimsing828@gmail.com:
Thanks for your help
[Xposed Framework Modules] Stoutpuppy GFX:
transparency issue

ok it seems that the last update didn't fix the transparency issue

after installing update I must have selected blur in advanced settings

if I un-select it blur - I lose transparency for background for menus

also adjusting blur radius has no effect.

Not a big deal - as I'm just happy to have transparency - just a heads up

LG G3 D855 nougat RR 5.8.5, SU + xposed framework/sdk25/arm

logs attachedhttps://drive.google.com/open?id=0BwlZBdUIdTcNakwzWXl2Z0RSaTg
[Xposed Framework Modules] DrAcHe981:
Luckily I have a ton of text editors on my laptop, because my favorite one wasn't able to open that log file properly, see attachment xD

Anyways, according to another editor the first line has tons of unix new line chars, and then only an error from the the swipeback module which tried to hook a method in the xposed installer itself, but the method wasn't found

I'm gonna try a bit why it isn't working, I might have some ideas tho, but that's just ideas as usual :T

And the blur radius, on my test device (Sony xperia Z1 with resurrection remix android 7.1.2) its working properly

Please take a normal logcat with the tag filter set to "NPM", my module should log such problems there! ( Stuff that's not related to an xposed hook itself isn't logged in the xposed log)
[Xposed Framework Modules] Stoutpuppy GFX:
how to set filter to NPM

Please take a normal logcat with the tag filter set to "NPM", my module should log such problems there! ( Stuff that's not related to an xposed hook itself isn't logged in the xposed log)[/QUOTE]

What do I type: adb logcat ?????
[Xposed Framework Modules] DrAcHe981:
Normally i use an app for it, but i think it's 'adb logcat -s "TAGNAME"' to filter for tags
[Xposed Framework Modules] Stoutpuppy GFX:
new logs

Here are the new logs
[Xposed Framework Modules] DrAcHe981:
Please give this apk file a shot, little spoiler, it also contains all changes that are meant for the next official release ;D (Some might be buggy tho, so its basically a test release)

If it didn't changed , then give me a log with deep logging enabled and the command 'adb logcat -s "NPM"', start the app, execute whats not working and then give the entire log

I changed a lot of my debugging lines to give me more information on that main tag instead of splitting it more into multiple ones (before it was for example "NPM:blurTask" or "NPM:xposedDialog", but adb cant handle such tags which contain a ":")
[Xposed Framework Modules] Stoutpuppy GFX:
logs attached

ok still same problem - disable blur or set blur radius to zero and transparency disappears logs attached

I know from your end you want to zero in on these bugs - but it's working as I need it to

but I'm happy to help test for you to sort this out for other users who may be facing similar problems
[Xposed Framework Modules] Ibuprophen:
I had just opened the following, new issue, within Github [MENTION=6342037]DrAcHe981[/MENTION]...

https://github.com/DrAcHe981/NeoPowerMenu/issues/21

This issue isn't that complicated to explain...

Basically, no matter what position I set for the power menu, it always reflects the same results on being placed on the top of the screen.

I had uploaded 4 example screenshots in support of what I'm explaining.

Thank you very much for your time, development and understanding!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Xposed Framework Modules] DrAcHe981:
As answered on github:

It looks to me like you have the full screen theme activated, that theme doesn't supports dialog position changes as it's covering the entire screen with the list view.

If that's not the case then I need an logcat with the tag filter set to "NPM", calculation problems should appear there.
[Xposed Framework Modules] BeachNYC:
Error Logs

Hi:

I've attached the xposed error report, and the url for the bugreport is:

https://drive.google.com/file/d/1a-kO26xEZJo9zoGqWLdurH-wsPRj10yf/view?usp=sharing .

Note that I had enabled deep logging in NeoPower, but it does not seem to have done so.

Thanks again for your app, and for your help.
[Xposed Framework Modules] DrAcHe981:
Deep logging not being able to be activated is a known problem with the preferences not being readable by xposed during boot on marshmallow and higher roms, is fixed in next release...

According to the log the hook is working fine... (errors are logged no matter if deep logging is enabled or not)

And because of that preferences bug it also didn't even enabled the experimental hook in the first try

Please check out this answer from me https://xdaforums.com/showpost.php?p=74417685&postcount=966 and install that version, in that version the preferences bug is fixed.

Unfortunately it seems like either the rom on the oneplus 3 replaces it itself, or isn't even using the stock showDialog from android, in that case i would need to find another way to directly hook the power button, i think that'll remove the ability to set other actions on that button tho (like if the phone or another module adds a double press action or similar)
[Xposed Framework Modules] ninestarkoko:
Or simply use Automagic wich supports shortcuts and other features that are provided by plugins on tasker...

I agree on shortcuts being the easiest way to support custom actions/triggers from apps and automation apps in NeoPowerMenu.

Really nice to see developement is still on and strong!

Not sure if it's been already reported but i see a kind of "flickering"/ menu misalignement in the latest version, probably due to the new position feature.

Here's the video:

https://ufile.io/j9hdy

The Confirmation dialog immediately changes position after appearing so giving a flikering effect.

I don't know any other english word to describe this phenomenon, sorry.
[Xposed Framework Modules] Alexey71:
Hi. Can your add support miui please?
[Xposed Framework Modules] DrAcHe981:
Yeah, that's most probably caused by the new position system, it uses a different approach compared to previous releases, using a padding value that updates whenever the size of the container changes, since I added the new positioning I'm working on fixing that, but so far it's just a little cosmetics problem, not as big as some other bugs on my list...

Try enabling the experimental hook found in the advanced settings, it might work, if not then it's like with the OnePlus devices that they changed how the power menu is activated, but still have the android original functions without ever calling them. (And that's why my module isn't throwing errors)

Still trying to find a solution for this which isn't causing even more problems
[Xposed Framework Modules] Artieza:
java.lang.RuntimeException: Unable to start activity ComponentInfo{de.NeonSoft.neopowermenu/de.NeonSoft.neopowermenu.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.SharedPreferences android.content.Context.getSharedPreferences(java.lang.String, int)' on a null object reference

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2331)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2393)

at android.app.ActivityThread.access$800(ActivityThread.java:151)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1309)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:135)

at android.app.ActivityThread.main(ActivityThread.java:5356)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:908)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:703)

at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:107)

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.SharedPreferences android.content.Context.getSharedPreferences(java.lang.String, int)' on a null object reference

at de.NeonSoft.neopowermenu.helpers.WorldReadablePrefs.<init>(WorldReadablePrefs.java:52)

at de.NeonSoft.neopowermenu.helpers.SettingsManager.<init>(SettingsManager.java:76)

at de.NeonSoft.neopowermenu.helpers.SettingsManager.getInstance(SettingsManager.java:88)

at de.NeonSoft.neopowermenu.MainActivity.onCreate(MainActivity.java:109)

at android.app.Activity.performCreate(Activity.java:6021)

at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2284)

... 11 more
[Xposed Framework Modules] DrAcHe981:
Punch me please... I did one of my typical dumb mistakes again, the "WorldReadablePrefs" is a new class I took to fix the settings not being readable on nougat and above, but I forgot while writing to make cases for pre nougat devices, and since both my testing devices are nougat, I didn't noticed it...

Now it's crashing because the "Device Protected Context" is never created (at least that's my guess now)

Would you be so kind to test the attached version?
[Xposed Framework Modules] Artieza:
java.lang.NoSuchMethodError: No virtual method getDataDir()Ljava/io/File; in class Landroid/content/Context; or its super classes (declaration of 'android.content.Context' appears in /system/framework/framework.jar)

at de.NeonSoft.neopowermenu.helpers.SettingsManager.registerFileObserver(SettingsManager.java:185)

at de.NeonSoft.neopowermenu.helpers.SettingsManager.<init>(SettingsManager.java:80)

at de.NeonSoft.neopowermenu.helpers.SettingsManager.getInstance(SettingsManager.java:88)

at de.NeonSoft.neopowermenu.MainActivity.onCreate(MainActivity.java:109)

at android.app.Activity.performCreate(Activity.java:6021)

at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2284)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2393)

at android.app.ActivityThread.access$800(ActivityThread.java:151)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1309)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:135)

at android.app.ActivityThread.main(ActivityThread.java:5356)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:908)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:703)

at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:107)
[Xposed Framework Modules] DrAcHe981:
I wish my previous device with android L would still work, it'll make this much easier -.-"

Anyways, another shot here I come, let's see if it hates me once again (android studio didn't said anything this time about the function being sdk 24+, so I blame android studio for it)
[Xposed Framework Modules] DrAcHe981:
I take this as a "It's working"? xD

Then I'm gonna upload a new new version to the repo now...
[Xposed Framework Modules] Artieza:
Problem: you forbid shutting down to the system. I have LG device so I can call original power menu. Nothing happens when I press shut down.

It leads to more deep and dangerous problem when energy is low and system tries to shut down itself, it goes to the loop with shut down calls.
[Xposed Framework Modules] DrAcHe981:
Before we start this reply, sorry if the reply is a bit too long, I kinda have the habit to always explain what exactly my stuff is doing xD

- - - - -

That's weird, especially since I'm not touching the android default shutdown at all, and that's what's triggered when battery is low, or when you press stuff in the original menu (and also I still don't get why lg seems to not use the normal function to show the power menu)

My module is hooking into the "showDialog" of the GlobalActionsDialog class, which is the stock power menu, the actual stock reboot process tho is in the ShutdownThread class, I was trying stuff with that class, but absolutely none of my test stuff is in the public releases, so I don't think my module is really the cause of this...

And since you're able to bring up the stock menu, my other hooks into the GlobalActionsDialog class are also ignored, and I also didn't changed them in that update (LG seems to somehow have it's complete own class for the dialog )

But anyways, I would need a logcat to look into it if it's containing something about what's happening :T

Also I can't reproduce it on my phone as my phones never doing the low battery shutdown because of broken battery, and I also can't show the stock menu on it
[Xposed Framework Modules] Artieza:
Many words, totally wrong. ? You rape com.android.server.power.ShutdownThread. Rebuild the function to stop displaying the default shutdown loading dialog.

11-24 20:11:45.962 I/Xposed ( 1675): [NeoPowerMenu] Loading Power Menu...

11-24 20:11:45.962 I/Xposed ( 1675): [NeoPowerMenu] Detected 5.0.2(21), injecting to:

11-24 20:11:45.962 I/Xposed ( 1675): [NeoPowerMenu] com.android.internal.policy.impl.GlobalActions

11-24 20:11:45.962 I/Xposed ( 1675): [NeoPowerMenu] com.android.internal.policy.impl.PhoneWindowManager

11-24 20:11:45.962 I/Xposed ( 1675): [NeoPowerMenu] com.android.server.power.ShutdownThread

11-24 20:11:45.962 I/Xposed ( 1675): [NeoPowerMenu] com.android.server.pm.PackageManagerService

11-24 20:11:45.968 I/Xposed ( 1675): [NeoPowerMenu] Getting permissions, using method for lollipop and above...

11-24 20:11:45.974 I/Xposed ( 1675): [NeoPowerMenu] Permission request hooked.

11-24 20:11:45.974 I/Xposed ( 1675): [NeoPowerMenu] Hooking (replace) com.android.internal.policy.impl.GlobalActions Constructor...

11-24 20:11:45.975 I/Xposed ( 1675): [NeoPowerMenu] Registering Broadcast Receiver and setting other values...

11-24 20:11:45.976 I/Xposed ( 1675): [NeoPowerMenu] Hooking (replace) com.android.internal.policy.impl.GlobalActions#showDialog...

11-24 20:11:45.978 I/Xposed ( 1675): [NeoPowerMenu] Replaced with showDialog(), just executing startActivity() to start my own dialog.

11-24 20:11:45.979 I/Xposed ( 1675): [NeoPowerMenu] Hooking (replace) com.android.internal.policy.impl.GlobalActions#createDialog...

11-24 20:11:45.982 I/Xposed ( 1675): [NeoPowerMenu] Replaced with empty method to prevent crashes.

11-24 20:11:45.983 I/Xposed ( 1675): [NeoPowerMenu] Hooking (replace) com.android.internal.policy.impl.GlobalActions#onAirplaneModeChanged...

11-24 20:11:45.985 I/Xposed ( 1675): [NeoPowerMenu] Replaced with empty method to prevent crashes.

11-24 20:11:45.985 I/Xposed ( 1675): [NeoPowerMenu] Hooking (after) com.android.server.power.ShutdownThread constructor...

11-24 20:11:45.986 I/Xposed ( 1675): [NeoPowerMenu] Getting needed values...

11-24 20:11:45.986 I/Xposed ( 1675): [NeoPowerMenu] Hooking (after) com.android.server.power.ShutdownThread#beginShutdownSequence...

11-24 20:11:45.987 I/Xposed ( 1675): [NeoPowerMenu] Rebuild the function to stop displaying the default shutdown loading dialog...

11-24 20:11:45.987 I/Xposed ( 1675): [NeoPowerMenu] Loading complete, all hooks executed.
[Xposed Framework Modules] DrAcHe981:
Okay... That's more than weird?!

The hook on the shutdown thread is in an if statement, but the conditions for it should never be true, it's hard coded to false during start-up of the script!

But as I know me I most probably simply missed one small and hidden debug line -.-"

There will most probably come an update just for that then soon (and some other bugs would be fixed there too)

(ps... I should sleep more, that could prevent such situations -.-)
[Xposed Framework Modules] Xspeed:
You can solve the problem in two ways:

1. Inject your Activity/Dialog code and resources into the system process

2. Send a broadcast when user selects something on the dialog, make the system process catch it and take actions there

If you need help, feel free to send me a PM ;)
[Xposed Framework Modules] DrAcHe981:
Samsung seems to have some changes in the global actions dialog that are not in my xperia z1, I will try to solve them in a next version
[Xposed Framework Modules] xdapowerapps:
Gave you a :good:. Can't wait for this to work on my phone, this is the best power menu I've seen in a LONG time. :highfive:
[Xposed Framework Modules] Rakuu:
That's odd, module works fine on my s5 aside from some very slight lag between holding the power button and the menu opening.
[Xposed Framework Modules] DrAcHe981:
I have gathered some new infos, the problem is not in the Samsung files, the problem Is in the used rom (Radium) it seems they have edited the Global Actions dialog code
[Xposed Framework Modules] xdapowerapps:
Thank you. I will try a different ROM and see if the ROM is the actual issue (which it maybe). Thank you for taking the time to look into this. I will keep you posted. :highfive:
[Xposed Framework Modules] DrAcHe981:
Also you could try this one: https://www.dropbox.com/s/u1094yml754a5a3/NeoPowerMenu v1.4-1.apk?dl=0

(It's fast coded so I only replace the function that makes problems on your rom)
[Xposed Framework Modules] xdapowerapps:
Just tried it and crashed as well. :(

--------- beginning of main
D/lights ( 639): set_light_leds: type=0, color=0x00ff00ff00, fM=0, fOnMS=0, fOffMs=0.
D/lights ( 639): write_leds: color=0x0000ff00, delay_on=0, delay_off=0, blink="0x0000ff00 0 0".
D/lights ( 639): set_light_leds: type=0, color=0x00ff00ff00, fM=0, fOnMS=0, fOffMs=0.
D/lights ( 639): write_leds: color=0x0000ff00, delay_on=0, delay_off=0, blink="0x0000ff00 0 0".
I/art ( 785): Background partial concurrent mark sweep GC freed 71369(3MB) AllocSpace objects, 39(1132KB) LOS objects, 32% free, 32MB/48MB, paused 1.586ms total 129.089ms
I/ClearcutLoggerApiImpl( 1957): disconnect managed GoogleApiClient
I/art ( 639): Background sticky concurrent mark sweep GC freed 210408(12MB) AllocSpace objects, 72(1737KB) LOS objects, 18% free, 35MB/43MB, paused 2.441ms total 115.875ms
E/AndroidRuntime( 639): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui
E/AndroidRuntime( 639): java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.GlobalActions.createDialog(GlobalActions.java:306)
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.GlobalActions.showDialog(GlobalActions.java:205)
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.PhoneWindowManager.showGlobalActionsInternal(PhoneWindowManager.java:1532)
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.PhoneWindowManager.showGlobalActionsInternal(PhoneWindowManager.java:1523)
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.PhoneWindowManager.powerLongPress(PhoneWindowManager.java:1363)
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.PhoneWindowManager.access$800(PhoneWindowManager.java:153)
E/AndroidRuntime( 639):	at com.android.internal.policy.impl.PhoneWindowManager$PolicyHandler.handleMessage(PhoneWindowManager.java:778)
E/AndroidRuntime( 639):	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 639):	at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 639):	at android.os.HandlerThread.run(HandlerThread.java:61)
E/AndroidRuntime( 639):	at com.android.server.ServiceThread.run(ServiceThread.java:46)
I/Process ( 639): Sending signal. PID: 639 SIG: 9
I/ServiceManager( 215): service 'gfxinfo' died
I/ServiceManager( 215): service 'cpuinfo' died
. . .
[Xposed Framework Modules] xdapowerapps:
[MENTION=6342037]DrAcHe981[/MENTION] I flashed Pacman ROM and your menu works beautifully! This is the best menu ever. Thank you so much for your support. :)
[Xposed Framework Modules] Lord. Tech:
Ummm, idgi... How am i supposed to take a screenshot now with this power menu? I only have option for reboots etc, nothing else
[Xposed Framework Modules] DrAcHe981:
Screenshot and other items are on the planned list, I'm currently working on it!
[Xposed Framework Modules] GreyCelt:
So, confirmed working for the HTC Desire 816 a5_chl for VirginMobile USA on unofficial CM13.

The only problem is that it does take a loooooooooooong time to perform the chosen task, i.e. Power Off, Reboot, etc.

Other than that, it works great! Colors look awesome and are easily changable.

Thank you for your beautiful work!

I'm patiently waiting for the Screenshot option. ?
[Xposed Framework Modules] CodingEthos:
Confirmed working on M8 Harmon Kardon Edition Sprint, CM13 official latest nightly, performance is quick (ish) and animations are mostly smooth.

Just needs some polishing, other than that the functionality is all there. Waiting for more options such as flashlight, screenshot, etc.

Good work.