I'm not a dev so plz understand my clumsyness
It seems all of xposed modules run at the same time now.
This make the messy result sometimes when using the modules which hooks same things.
For example, I'm changing the size and format of clock on the statusbar with module A and I'm using module B also to theme my rom and this contains the function changing the size of clock on the statusbar also.
As you see, it seems that A and B have same function. But their way to make it in technical are not same.
This makes the size of clock every boot different, and users and devs can't set the module which hooks something LAST.
I asked @rovo89 before about the 'priority' of modules before and he answered xposed framework doesn't.
But I recognized my question was wrong recently.
I had to ask the 'batch' of modules
I think making a batch could solve the concurrent hooks
Possible?
It sounds like you want to be able to specify the order in which modules get loaded. Though your use of the word ``batch'' makes no sense to me, please elaborate.
Related
Hello,
I want to force some applications to have floating windows using the (awesome ^^ ) Xposed framework.
So far, I managed to hook on the "onAttachedToWindow()" method (as explained here goo.gl/ZFb8iQ ) to set the floating layout (as explained in goo.gl/GyCXac ), which seems to work pretty well (I can't embed a screenshot due to the forum's restrictions to new members).
However, in order to set a transparent background (outside the resized app, in order to allow the manipulation of other apps in the background), the only method that I'm aware of is adding the following line in the app theme (e.g. styles.xml)
Code:
<item name="android:windowIsTranslucent">true</item>
My question is: how can I do that using Xposed ?
Thanks in advance for your help.
windowIsTranslucent can't be set programmatically AFAIK. You could try seeing where windowIsTranslucent is parsed and set (in the AOSP source code), and hook that method to enable it for your package.
GermainZ said:
windowIsTranslucent can't be set programmatically AFAIK. You could try seeing where windowIsTranslucent is parsed and set (in the AOSP source code), and hook that method to enable it for your package.
Click to expand...
Click to collapse
I see. It's a shame the Android framework doesn't allow such a thing...
Is there any other technique for forcing activities to display a floating window (programmatically) ?
Also, would it be possible, with the help of Xposed, to create a translucent floating window then "insert" a hooked activity into it ?
Or, how could I use Xposed to make an app use a custom theme ?
WARNING: This might seem like a really noob question. It probably is.
The other day, when I was optimizing a chinese phone (it's system was the messiest thing I've ever seen), I ran into an issue.
For the sake of example, imagine you have a module that lets you choose your statusbar color and a module with loads of useful features but alas, one of them is coloring the statusbar red (can't be disabled except by disabling the module).
I'm guessing there's some sort of thing as module priority, be it load/hook order or something else (I'm not a module developer). Is there any way (modding apks of the modules?) I can adjust these priorities myself?
And to provoke module developers, is it possible for a module to achieve this?
hajdulak said:
WARNING: This might seem like a really noob question. It probably is.
The other day, when I was optimizing a chinese phone (it's system was the messiest thing I've ever seen), I ran into an issue.
For the sake of example, imagine you have a module that lets you choose your statusbar color and a module with loads of useful features but alas, one of them is coloring the statusbar red (can't be disabled except by disabling the module).
I'm guessing there's some sort of thing as module priority, be it load/hook order or something else (I'm not a module developer). Is there any way (modding apks of the modules?) I can adjust these priorities myself?
And to provoke module developers, is it possible for a module to achieve this?
Click to expand...
Click to collapse
Rovo has said that there is no way to prioritize one module over another...
The way to deal with that is to ask module developers to put in switches to turn off portions of the module...
hajdulak said:
For the sake of example, imagine you have a module that lets you choose your statusbar color and a module with loads of useful features but alas, one of them is coloring the statusbar red (can't be disabled except by disabling the module).
Click to expand...
Click to collapse
This is exactly my example to explain why module priorities are not needed. The problem is that what you mentioned last - the module isn't flexible enough to let you disable its features seperately. The solution would be to ask the module developer to implement such a setting, where the module wouldn't touch the statusbar color at all (not even setting it to the assume standard black). There are different ways to change the statusbar color, and only in some cases, the module which is executed last will win. If the modules use different ways to change it, there's a good chance that one of them will win no matter whether it can do its changes first or last.
I remember only one use-case where higher priority is the only way to achieve the goal, and that was a module hooking other modules/Xposed itself. Apart from that, I have only heard about cases like you described, where priority handling is only a workaround that works only sometimes. I don't want to encourage such behavior by offering a feature that only experts would understand.
rovo89 said:
The solution would be to ask the module developer to implement such a setting
Click to expand...
Click to collapse
At the moment, I am using something like this...
afterHookedMethod
if (isEnabled) changeSomething()
Is this scheme OK?
or should I hook something only if it is enabled:
if (isEnabled) findAndHookMethod...
?
rovo89 said:
This is exactly my example to explain why module priorities are not needed. The problem is that what you mentioned last - the module isn't flexible enough to let you disable its features seperately. The solution would be to ask the module developer to implement such a setting, where the module wouldn't touch the statusbar color at all (not even setting it to the assume standard black). There are different ways to change the statusbar color, and only in some cases, the module which is executed last will win. If the modules use different ways to change it, there's a good chance that one of them will win no matter whether it can do its changes first or last.
I remember only one use-case where higher priority is the only way to achieve the goal, and that was a module hooking other modules/Xposed itself. Apart from that, I have only heard about cases like you described, where priority handling is only a workaround that works only sometimes. I don't want to encourage such behavior by offering a feature that only experts would understand.
Click to expand...
Click to collapse
Amen.
the Xposed module that would give you're notification panel a blurred effect. seems to have disappeared earlier last year. Just wondering if there are any alternatives you guys may know of. I have a rooted Note 5, 5.1.1 btw.
edit: suggest of any system tweaking mods would help
It's still in there as an exposed module. I tried it yesterday but it doesn't play ball with the toggle tiles.
Yeah an update needs to be released for this phone. It's not 100% working yet. I'm having trouble finding modules that actually would work.
I have a Note 3 which I'm looking to make into my backup phone/dedicated GPS. It's currently on 4.4.2 and I would like to believe that, in the intervening major versions, many of the missing (obvious) OS features which made Xposed so necessary are now available as stock system options. Being familiar with the awful, pervasive anti-customization/pro-simplicity/for-dummies mobile development philosophy that now threatens even PC software, I'm afraid I'm probably wrong.
Ideally, of course, I'd want Xposed on my yet-to-be-determined 7.x phone, but if that isn't going to happen, I'd like to know if there are built-in options now to partially replace great Xposed modules like:
NotifyClean - In Android N, can I set rules to totally block specific notifications?
NeverSleep - Set certain applications to disable sleep mode when active?
Wanam Xposed - Theming options (assuming I go with a Samsung phone)?
Xposed LED Control - Different LED colors per notification type?
DoubleTapToSleep - Sleep without using a hard button?
BootManager
Network Speed Indicator
If someone familiar with Android N could comment on the list above, I'd be very grateful. I'd rather buy a 'new' older phone than get an S8 or similar and find (assuming there's even a root exploit) that my phone is crippled versus my nearly 4 years old Note 3.
Notifiyclean can be substituted by power notification controls, which I don't know if it comes with stock rom, but I know it's there for the rom I'm using.
Neversleep can be substituted by the caffeine toggle, if your rom has it. I believe you can also find it on the play store to use if it's not built-in.
Wanam Xposed, I haven't used in ages. Can't even remember what it does...
LED Control should be built-in, if not custom roms.
DoubleTapToSleep should be your kernel.
Bootmanager, I'm unsure... Maybe alternatives with root?
Network Speed Indicator can be done with apps or built-in from custom roms.
http://cloud.tapatalk.com/s/58fb86661071a/Screenshot_20170422-120817.png?
http://cloud.tapatalk.com/s/58fb867bf37d6/Screenshot_20170422-122512.png?
http://cloud.tapatalk.com/s/58fb868630b93/Screenshot_20170422-122601.png?
Sent from my Nexus 6P using Tapatalk
Thanks... It sounds like I should be able to get by without Xposed, though I don't know if I'll ever be able to install a custom ROM considering I will probably end up with an AT&T phone. I guess first I need to find a rootable phone.
Is there an alternative to App Settings module, to allow for per-app dpi settings without Xposed, because android n?
thktanuki said:
Is there an alternative to App Settings module, to allow for per-app dpi settings without Xposed, because android n?
Click to expand...
Click to collapse
My first idea was Tasker, but I am not sure if you can modify the dpi value with Tasker itself. I guess with the help of an appropriate plugin, you should be able to set the dpi on a per-app base.
outdated
go to here
Gravitybox for nougat
removed the "gravitybox framework not responding" error on api 24 and 25
also re-branded the app as gravitybox for nougat
tested working:
battery (kind of)
center clock + day of the week
data transmission Monitor
power setting menu
skip tracks with volume buttons
clock settings
you tell me...
Not working:
Stock battery with percentage
Quick Settings
Lock screen shortcuts
Setting of the optional button
deactivate network type indicator in status bar
Navigation bar tweaks (BRICK WARNING!)
you tell me...
sources for helpers
download links for sdk 24 and 25 are the same
Code:
uninstall the old one, otherwise it'll give "Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.ceco.nougat.gravitybox attempting to redeclare permission gravitybox.permission.UNLOCK already owned by com.ceco.marshmallow.gravitybox]" error
Since I won't have a lot of time to port everything (btw, I'm already late for one thing right now) so I expect the community to help.
That's why I posted the source at github, this way anyone can collaborate to the code.
Anyone that helps me will get credit too, just claim it someway I can see it
brick fix by @photoguy29
To fix this: Reboot to TWRP recovery and navigate to: Advanced>File Manager>data>data>com.ceco.nougat.gravitybox
Once you are in the com.ceco.nougat.gravitybox folder, in the bottom right corner is a folder Icon. Tap that icon>delete
This will delete all the changes you made in Gravitybox, and upon reboot, the System UI functions properly. The gravitybox apk will also still be installed, so you can go and re-activate your tweaks that WERE working.
credits to @C3C076 creator of gravitybox
For me works:
battery
center clock + day of the week
data transmission Monitor
power setting menu
Not works:
Lock screen shortcuts
Setting of the optional button
Why that rush?
I have already migrated like 90% of the module to Nougat after working for almost 2 weeks on it non-stop. Currently QS management is undergoing redesign and there's still quite a lot of work left. It's still a work in progress - not suitable to be made available to the masses and also, I am still not convinced whether to release something as there is no official Xposed Framework. I'll see.
@ C3CO76
Because I like it a lot your gravity box [emoji41] [emoji39]
Wysłane z mojego Moto G (4) przy użyciu Tapatalka
I'm glad you like it. But then it doesn't make any sense to release a version that is far from working when you could keep it for personal use.
Feel me?
@C3C076 i guess people love GB so much
This ported xposed for N situation is confusing but people are desperate to have xposed and their beloved modules even if its partially working
Can't live without gb's pie control
C3C076 said:
Why that rush?
I have already migrated like 90% of the module to Nougat after working for almost 2 weeks on it non-stop. Currently QS management is undergoing redesign and there's still quite a lot of work left. It's still a work in progress - not suitable to be made available to the masses and also, I am still not convinced whether to release something as there is no official Xposed Framework. I'll see.
Click to expand...
Click to collapse
sorry, I didn't knew it, I looked into the git and thought that no one would do it anymore (because nougat had been here for a long time)
but still a lot of people are just crazy like me that wants it even if sacrifices need to be made, just like people wants an unstable xposed rather then nothing, they want the gravitybox
and no one uses every tweak available like me, I just use one or two and both works
I'm glad to see you haven't abandoned the project, I wouldn't be able to do it like you
and please release it, for people like us, there are 66422 downloads on the xposed for nougat thread (counting the xposed installer app because it's the same for both api levels and only one version) not counting people like me that downloaded it from the alternate link.
sort of 66422 persons waiting for gravitybox to be released even if it breaks something
and not everyone knows how to release a version that is far from working when you could keep it for personal use, I learned how to use xposed 3 years before learning something that would allow me to do this port (and it still sucks)
Yes, I understand. Hard to tell what comes next at this time. I will be taking decisions after I am happy enough with the migration results and the results of internal testing on various device/OS combinations I have at hand.
not working : deactivate network type indicator in status bar
Is lockscreen transparency and blur working
Not working: Navigation bar tweaks
Activating the master switch will cause the System UI to crash upon reboot.
To fix this: Reboot to TWRP recovery and navigate to: Advanced>File Manager>data>data>com.ceco.nougat.gravitybox
Once you are in the com.ceco.nougat.gravitybox folder, in the bottom right corner is a folder Icon. Tap that icon>delete
This will delete all the changes you made in Gravitybox, and upon reboot, the System UI functions properly. The gravitybox apk will also still be installed, so you can go and re-activate your tweaks that WERE working.
I hope this helps
Stock battery with percentage not working for me.
I believe what this guy is doing, is a good thing, if people get into installing Xposed modules that are unofficial they should know that it's unstable, and in most cases can brick your device. CT, I do see where you're coming from, but it's along the lines of "People don't kill people, guns do." No, that's not how the world works, and everyone on the Internet should be able to share what they want.
Thanks for the mod, working battery percentage (buggy), skip tracks with volume buttons, clock settings, advances power menu. Moto G5+ stock rom sdk 24 Xposed systemless (magisk)
Patience is a virtue...
LexignisOfficial said:
I believe what this guy is doing, is a good thing, if people get into installing Xposed modules that are unofficial they should know that it's unstable, and in most cases can brick your device. CT, I do see where you're coming from, but it's along the lines of "People don't kill people, guns do." No, that's not how the world works, and everyone on the Internet should be able to share what they want.
Click to expand...
Click to collapse
yes, that's what I meant
if you use any xposed version with any module, custom roms, root, any mods you shouldn't care about stability (people do but they shoudn't)
by the way, I looked on the Gravitybox git and I saw no nougat branch
so I did this because I thought that either the creator wouldn't make any more releases or he hadn't started (and if he wanted to use my as base because of the mm to n naming changes could save him like 5 minutes and I wanted to help and this is all the only help I can give)
and I had this mod for myself because Center clock and round battery works and I only use thoose
but I thought on the people at the same situation that coudn't do It by themselves
but thanks again for C3C076 for being patient with my impatience
I'm happy it won't be my job to port the rest of it because it'd be baaad
gkillershots said:
yes, that's what I meant
if you use any xposed version with any module, custom roms, root, any mods you shouldn't care about stability (people do but they shoudn't)
by the way, I looked on the Gravitybox git and I saw no nougat branch
so I did this because I thought that either the creator wouldn't make any more releases or he hadn't started (and if he wanted to use my as base because of the mm to n naming changes could save him like 5 minutes and I wanted to help and this is all the only help I can give)
and I had this mod for myself because Center clock and round battery works and I only use thoose
but I thought on the people at the same situation that coudn't do It by themselves
but thanks again for C3C076 for being patient with my impatience
I'm happy it won't be my job to port the rest of it because it'd be baaad
Click to expand...
Click to collapse
not working
Force LTR direction
forrces LTR layout direction RTL locales
(requires rebbot )
masrysat said:
not working
Force LTR direction
forrces LTR layout direction RTL locales
(requires rebbot )
Click to expand...
Click to collapse
an official port has been released here
nexus 6 on slimroms (Slim-shamu-7.1.2.build.1.13),
"am/pm" option does NOT work.