Related
I am running android L on my Nexus 7 but i just wanted to know when will Xposed support the android version??
Or will it ever support android L
Android L is a preview version. So you shouldn't wait Xposed for this version. Maybe in few weeks or months we will have Android 4.5 or Android 5.0 with Xposed support :good:
Yeah.. I'm currently playing around with it a bit, trying to get adb working in root mode and stuff which makes it easier to develop.
It's indeed still a preview release, and it's a moving target (there are very strong signs that Google will update the preview before the final release). Root apps and even some normal apps don't work well at the moment. It's good that I can try what is necessary to get Xposed running, but I haven't decided yet whether I will work on a Xposed preview release for this preview ROM. I'll share some more thoughts once I had the chance to look deeper into it.
rovo89 said:
Yeah.. I'm currently playing around with it a bit, trying to get adb working in root mode and stuff which makes it easier to develop.
It's indeed still a preview release, and it's a moving target (there are very strong signs that Google will update the preview before the final release). Root apps and even some normal apps don't work well at the moment. It's good that I can try what is necessary to get Xposed running, but I haven't decided yet whether I will work on a Xposed preview release for this preview ROM. I'll share some more thoughts once I had the chance to look deeper into it.
Click to expand...
Click to collapse
if you can get xposed running in android L developer preview it will make xposed available to kitkat with art ?
PedroM.CostaAndrade said:
if you can get xposed running in android L developer preview it will make xposed available to kitkat with art ?
Click to expand...
Click to collapse
How about you just let him work on it and see how it's goes.
There's literally no reason at all to bother him with questions, when he has something new to share he will, when he doesn't those questions will be just annoying to him. Not yours personally, but the sheer amount of people bombarding him with all kinds of art related questions just add up.
PedroM.CostaAndrade said:
if you can get xposed running in android L developer preview it will make xposed available to kitkat with art ?
Click to expand...
Click to collapse
"Getting it running" is one thing, whether it's good to publish it is another question. I've had a prototype of Xposed for the ART preview in December already. Barely tested, needed manual installation, probably failing here and there, but generally it did what it should. But already back then, I've seen that Google is still working actively on improving ART. They have made huge internal changes since then. Last weekend, I made my prototype compile against the master branch of AOSP and I had to introduce lots of conditionals. That's without knowing whether it will actually work, I just changed declarations, calls etc. to avoid compile time errors.
The ART preview in KitKat and the ART almost-final in the Android L preview are different pieces of software. Maintaining support for both of them means basically twice the work, especially for testing. That, and the fact that ART in KitKat was just an optional preview (with potential bugs that may be incorrectly blamed on Xposed), makes it less likely that I will publish Xposed for the KitKat variant of ART. That's not a final decision, it depends on how ART development continues and how well I can support Android L. It's important that Xposed works fine on upcoming Android versions where ART is the only runtime. KitKat support would be a bonus if it's not too much effort to maintain in parallel.
Oh, and for everyone who thinks that posting "pleeeeease" or "you have to support it" will increase the chances of publishing something: It won't. It will just annoy me and make it less likely.
tonyp said:
How about you just let him work on it and see how it's goes.
There's literally no reason at all to bother him with questions, when he has something new to share he will, when he doesn't those questions will be just annoying to him. Not yours personally, but the sheer amount of people bombarding him with all kinds of art related questions just add up.
Click to expand...
Click to collapse
Indeed. I have received lots of hints "hey, Android L is out now" - yes, I know. So for now, I have disabled PMs...
By the way, I have just read the "How to Report Bugs Effectively" essay by the PuTTY developer. It's so true!
I just wanted to say how incredibly awesome it is that you're already working on Xposed with this early preview version of Android L. I for one am very happy with my current 4.4.4+Xposed setup, and would rather stick with that than use a newer Android release without Xposed. It's a truly great piece of software that I have come to depend on. Keep up the good work and ignore those who would try to pressure you. We can wait!
rovo89 said:
"Getting it running" is one thing, whether it's good to publish it is another question. I've had a prototype of Xposed for the ART preview in December already. Barely tested, needed manual installation, probably failing here and there, but generally it did what it should. But already back then, I've seen that Google is still working actively on improving ART. They have made huge internal changes since then. Last weekend, I made my prototype compile against the master branch of AOSP and I had to introduce lots of conditionals. That's without knowing whether it will actually work, I just changed declarations, calls etc. to avoid compile time errors.
The ART preview in KitKat and the ART almost-final in the Android L preview are different pieces of software. Maintaining support for both of them means basically twice the work, especially for testing. That, and the fact that ART in KitKat was just an optional preview (with potential bugs that may be incorrectly blamed on Xposed), makes it less likely that I will publish Xposed for the KitKat variant of ART. That's not a final decision, it depends on how ART development continues and how well I can support Android L. It's important that Xposed works fine on upcoming Android versions where ART is the only runtime. KitKat support would be a bonus if it's not too much effort to maintain in parallel.
Oh, and for everyone who thinks that posting "pleeeeease" or "you have to support it" will increase the chances of publishing something: It won't. It will just annoy me and make it less likely.
Indeed. I have received lots of hints "hey, Android L is out now" - yes, I know. So for now, I have disabled PMs...
By the way, I have just read the "How to Report Bugs Effectively" essay by the PuTTY developer. It's so true!
Click to expand...
Click to collapse
Thanks for the answer it's what imagined and I understand, I just wanted to make sure that i was right xD
You have done a really great job, and you and all of the good developers of XDA are our heroes!!! Take a beer you deserve it! [emoji106]
Any chance of a sticky and close on this thread? I was fortunate to find it quickly enough on the second page but I was checking the General and FAQ threads first for this exact info. I'm sure a lot of people are coming to see it.
Thanks for the hint. I have extended the FAQ item about ART with a link to this thread.
I use Xposed on stock GPE 4.4.4. Its great, and for my use actually better than some of the more customised ROM's. I find i dont actually want a lot of customisation, just a few things that Xposed with a couple of modules does well.
From what i am reading at the moment, ART wont be a really viable alternative until the release of Android L. Hopefully the GPE ROMs will be early releases.
So, i would think that if you choose to continue Xposed releases (if you dont the sobbing from XDA will keep you awake nights!!) then developing for Android L which NEEDS to be ART compatible, and forgetting a version for KK which can use Dalvik anyway is the way to go.
Many thanks for all you efforts.
Hi @rovo89 I have a quick petition for you. Please release your art KitKat "alpha" of xposed so somebody interested can complete it. I think that is pretty fair and it shouldn't take you too much time. Please consider it.
resadent said:
Hi @rovo89 I have a quick petition for you. Please release your art KitKat "alpha" of xposed so somebody interested can complete it. I think that is pretty fair and it shouldn't take you too much time. Please consider it.
Click to expand...
Click to collapse
You mean the source code, so interested developers can compile it themselves? I'm indeed thinking about publishing some work-in-progress code because I'm getting more and more frustrated with L (currently uninstalled it again, I need my phone). Not yet though, I would at least like to get L booting with it (if necessary with permissive SELinux). *If* I ever support ART on KitKat, then I wouldn't want to maintain two totally different codebases.
rovo89 said:
You mean the source code, so interested developers can compile it themselves? I'm indeed thinking about publishing some work-in-progress code because I'm getting more and more frustrated with L (currently uninstalled it again, I need my phone). Not yet though, I would at least like to get L booting with it (if necessary with permissive SELinux). *If* I ever support ART on KitKat, then I wouldn't want to maintain two totally different codebases.
Click to expand...
Click to collapse
Thanks for your answher, that's mostly what I meant. I read in the last page you had a prototype running in kitkat+art, so I thought you could publish that work in order for other devs to have the possibility to keep working on it if you don't want to for whatever the reason or even help you with the code. Also, it would be good for any user who wants to use it even if he knows it may fail here or there as you say.
resadent said:
Thanks for your answher, that's mostly what I meant. I read in the last page you had a prototype running in kitkat+art, so I thought you could publish that work in order for other devs to have the possibility to keep working on it if you don't want to for whatever the reason or even help you with the code. Also, it would be good for any user who wants to use it even if he knows it may fail here or there as you say.
Click to expand...
Click to collapse
Never underesimate the stupidity of the users
They will install it, run into all kinds of issues and then come complaining and whining at xda.
This will just cause issues, so I don't think it should be released in any way to endusers.
But I do think the release of the source code is a good idea when it comes with the request kindly not to share any compiled versions.
Each developer who could seriously help working in that complex field (which aren't too many I suppose) won't have a problem compiling it, so it might help in speeding up the development or producing new ideas.
tonyp said:
Never underesimate the stupidity of the users
They will install it, run into all kinds of issues and then come complaining and whining at xda.
This will just cause issues, so I don't think it should be released in any way to endusers.
But I do think the release of the source code is a good idea when it comes with the request kindly not to share any compiled versions.
Each developer who could seriously help working in that complex field (which aren't too many I suppose) won't have a problem compiling it, so it might help in speeding up the development or producing new ideas.
Click to expand...
Click to collapse
May be the stupidity is on your side! I don't have a problem to flash 98% done xposed on my KitKat and give feedbacks to the developer.
I am sure that there are many users like me who will agree to do it, don't forget that hundreds of users still using Dalvik because of xposed!
Some module won't work or other small bug isn't a reason not to use it.
So, if you think you are so smart-you are wrong!
yanleites said:
May be the stupidity is on your side! I don't have a problem to flash 98% done xposed on my KitKat and give feedbacks to the developer.
I am sure that there are many users like me who will agree to do it, don't forget that hundreds of users still using Dalvik because of xposed!
Some module won't work or other small bug isn't a reason not to use it.
So, if you think you are so smart-you are wrong!
Click to expand...
Click to collapse
Don't get me wrong, as soon as it's in a functional beta state I'm with you there, but what rovo had wasn't even close to an alpha stage afaik. At that point users feedback is hardly ever useful for developers as it's quite obvious what's working and what isn't. Here you need useful logs and no general feedback (and usually you're testing a new version every other minute, so it doesn't really make sense to make testing releases and wait for feedback).
Please don't read my post as offense, the fact that you're actually reading here means you're not in the scope of "users" I was referring to.
It's sad, but unfortunately xda(-developers) usually isn't the best place to do and discuss actual development. There are loads of people who fail to read instructions, the OP or a couple pages back before posting, which results in lots of redundant bug reports of well known problems.
The situation has improved in the last years and the staff is doing a great job at keeping it within boundaries, but still loads of development threads (see e.g. the N5 section) are getting spammed with stupid and redundant posts.
tonyp said:
Don't get me wrong, as soon as it's in a functional beta state I'm with you there, but what rovo had wasn't even close to an alpha stage afaik. At that point users feedback is hardly ever useful for developers as it's quite obvious what's working and what isn't. Here you need useful logs and no general feedback (and usually you're testing a new version every other minute, so it doesn't really make sense to make testing releases and wait for feedback).
Please don't read my post as offense, the fact that you're actually reading here means you're not in the scope of "users" I was referring to.
It's sad, but unfortunately xda(-developers) usually isn't the best place to do and discuss actual development. There are loads of people who fail to read instructions, the OP or a couple pages back before posting, which results in lots of redundant bug reports of well known problems.
The situation has improved in the last years and the staff is doing a great job at keeping it within boundaries, but still loads of development threads (see e.g. the N5 section) are getting spammed with stupid and redundant posts.
Click to expand...
Click to collapse
Ok, First of all there are always be "stupid and redundant posts", because when I see "franco kernel" thread for N4 - it's thouthends of pages, not many people will search inside to find simple answer to question like "how to flash", it's much easier to ask again and get an answer in 5 minutes.
About Rovo, I think if it works on his phone, there is no reason not to let other users WHO WANT to use the new Xposed version, again, few modules less didn't kill anyone, so f I use 5 instead of 10 modules - it's OK by me.
I tried to change to ART (ofcourse disabled Xposed), but I had to install 6 other apps instead to make phone look/work as with Xposed, I think it's not worth it, but ART working better... After 1 day I changed to Dalvik and Xposed.
In coclusion, I prefer almost ready Xposed + ART then Dalvik with 100% working Xposed.
yanleites said:
Ok, First of all there are always be "stupid and redundant posts", because when I see "franco kernel" thread for N4 - it's thouthends of pages, not many people will search inside to find simple answer to question like "how to flash", it's much easier to ask again and get an answer in 5 minutes.
About Rovo, I think if it works on his phone, there is no reason not to let other users WHO WANT to use the new Xposed version, again, few modules less didn't kill anyone, so f I use 5 instead of 10 modules - it's OK by me.
I tried to change to ART (ofcourse disabled Xposed), but I had to install 6 other apps instead to make phone look/work as with Xposed, I think it's not worth it, but ART working better... After 1 day I changed to Dalvik and Xposed.
In coclusion, I prefer almost ready Xposed + ART then Dalvik with 100% working Xposed.
Click to expand...
Click to collapse
LOL. Translated - "Give it me now! It's not fair that rovo is keeping it to himself!" No offence, but that is how your posts are coming across. There's also no need to be insulting to someone that has contributed many things to the users of this site.
The reasons for not releasing the experimental version in a precompiled easily installable state were explained clearly by tonyp. The Xposed framework is a hugely complicated project to begin with and the fact that rovo has a test version does not mean that it's anywhere near ready for end users to install on their devices. If it didn't work properly, there would be many, many people with unusable devices flooding this section complaining that rovo broke their phone. Even if the experimental framework itself worked perfectly on the multitude of devices people have, it may break some modules, which would cause complaints and headaches for the module developers, because most people wouldn't mention they were using the test version.
As for it only being released to people that agree that it may not work. What normally happens here is that people that just want the latest version apply, then disappear without ever providing any feedback apart from complaints that "It doesn't work", with no useful logs etc provided.
The source being made available is the correct way to go here. It ensures, in the most part, that only people that have knowledge and understanding of the risks involved and are able to collaborate properly with development are able to install the experimental version. Not impatient people that just can't wait to make their phone cool and don't read or search threads before modifying their expensive device.
Sent from my C6603 using Tapatalk
rovo89 said:
You mean the source code, so interested developers can compile it themselves? I'm indeed thinking about publishing some work-in-progress code because I'm getting more and more frustrated with L (currently uninstalled it again, I need my phone). Not yet though, I would at least like to get L booting with it (if necessary with permissive SELinux). *If* I ever support ART on KitKat, then I wouldn't want to maintain two totally different codebases.
Click to expand...
Click to collapse
Why don't you keep L as a secondary rom(with MultiROM)? By doing so you can test xposed on L, and then switch to kitkat when you need your phone.
So I look through the built in repo and I install a lot of things on my old phone to play with. However on the primary I only use FOSS. If a module doesn't have a git page then I don't install it.
I was thinking it would be neat if someone maintained a separate F-Droid repo specifically for xposed modules which are open source. Since xposed itself is open source you could have that on there as well.
It'd be nicer if there was a filter option in the program itself but I'm sure the devs are busy and the above would just be easier.
Maybe it is possible to add "Open source modules" in Sort mode (in Xposed Installer -> Download). It will simply check if Source link for module is not empty.
Who can take this idea and contribute this feature to Xposed?
Waking up this thread. I would also really like to have a structured list of modules which are open source for security reasons. Is this available anywhere yet?
E--Man said:
Waking up this thread. I would also really like to have a structured list of modules which are open source for security reasons. Is this available anywhere yet?
Click to expand...
Click to collapse
Maybe we can get "repo db" and look for source code field. But "in app implementation" is prefered. @rovo89
pyler said:
Maybe we can get "repo db" and look for source code field. But "in app implementation" is prefered. @rovo89
Click to expand...
Click to collapse
Where could we obtain the DB with those fields? I would never install any closed-source modules on my devices. Doing so is absolutely ludicrous in my opinion.
Also, is there a list of verified and trusted (by @rovo89 or someone alike) Xposed modules anywhere?
This is a very important topic...
Thanks,
E.
See https://github.com/rovo89/XposedInstaller/issues/249
The information about the source code URL is available in the repository XML file already and could easily be read be the installer. The issue is up for grabbing. I would appreciate a quick outline if the intended implementation though, so I can intervent regarding architectural decisions before someone writes a lot of code.
I can't give any "trust" recommendations for any but my own modules. It would mean that I would have to analyse the complete source code, verify that the APK actually matches that source code and repeat these steps for every new versions.
Well, if module is open source, anybody can check code so I think there is almost zero chance for malwares or so...
Closed sourced and obfuscated modules are the worst ones. Avoid them. They can do basically everything in background and user knows nothing.
So any skilled dev who is able to create new filter in Xposed Installer for open source modules here? It could be good addition.
pyler said:
Well, if module is open source, anybody can check code so I think there is almost zero chance for malwares or so...
Closed sourced and obfuscated modules are the worst ones. Avoid them. They can do basically everything in background and user knows nothing.
So any skilled dev who is able to create new filter in Xposed Installer for open source modules here? It could be good addition.
Click to expand...
Click to collapse
Really?..
Anybody can check sources, but who will?..
And can you trust their results?..
FOSS can be riddled with exploits like Heartbleed for years, and no one will notice anything. There are even competitions on hiding malicious code inside innocent one...
Only a small number of experienced and skilled developers will be able to find such malware, and believe me - 99% of them don't waste their time on reading, understanding and checking for exploits the sources of all software they use...
@rovo89, thanks for responding to this thread.
I am just wondering if anyone has any updates on the development of an Open Source repository.
Also, I feel that it would also be helpful if we had some sort of a "Developer Trust Rating" as well as a "Code Reviewer" status to ensure that the code of a particular module (or even revision if someone volunteers to take it that far) is both safe and/or that the code has been inspected.
Without this, installing modules on devices means we could be installing software that can be as malicious as it can get.
Lastly, where can I download the XML file that lists XPosed modules along with the "source code URL", and how can I validate that the source code in the URL matches that of the XPosed module itself?
Thanks.
E--Man said:
Also, I feel that it would also be helpful if we had some sort of a "Developer Trust Rating" as well as a "Code Reviewer" status to ensure that the code of a particular module (or even revision if someone volunteers to take it that far) is both safe and/or that the code has been inspected.
Click to expand...
Click to collapse
That's a nice vision, but I doubt that you will find enough people to actually do this who you trust and who would be willing to take the responsibility.
E--Man said:
Lastly, where can I download the XML file that lists XPosed modules along with the "source code URL", and how can I validate that the source code in the URL matches that of the XPosed module itself.
Click to expand...
Click to collapse
Check the source code of the installer for the URL, I don't remember it. But there is no way you can check an APK and find out whether it's built from a certain source. That would only be possible if the developer gave the source code to a trusted party, who would compile it and sign it with their keys. If you trust that third party AND inspect the source code, then you can be sure that it's not malicous. That's F-Droid's model, as far as I know.
YaDr said:
Really?..
Anybody can check sources, but who will?..
And can you trust their results?..
FOSS can be riddled with exploits like Heartbleed for years, and no one will notice anything. There are even competitions on hiding malicious code inside innocent one...
Only a small number of experienced and skilled developers will be able to find such malware, and believe me - 99% of them don't waste their time on reading, understanding and checking for exploits the sources of all software they use...
Click to expand...
Click to collapse
Hello there my Russian friend. I will respectfully disagree with you on this point and I will explain why. Right here on XDA, we have many highly-skilled developers who are the authors of countless lines of code translating into ROMs, modules, enhancements, etc. Much (if not all) of these projects are free to distribute and created as a contribution to the community. In other words, to ask "who will check sources" is the same thing as asking "who will create custom ROMs for people?" or "who will create invaluable/indispensable modules such as XPosed?" or even the general question of "why would someone do this for free?".
It is evident that all of these exist already and that people do indeed contribute, so coupled with the fact that the XDA community is over 5 million members in size, I think there will be developers who may be interested.
The only reason I can see someone not supporting this is if they have an interest not to do so, such as being the author of a closed-source (or open-source) malicious module.
"FOSS can be riddled with exploits like Heartbleed for years, and no one will notice anything"
Yeah but if it was closed source there is a chance it would have never been found.
Also saying that "no one would bother to check the code" is a horrible argument. At least give people the option to inspect it if they want to.
Bump, has anyone taken this to the next step? I am still interested!
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Bump, has anyone taken this to the next step? I am still interested! <br />
<br />
Please use the QUOTE feature when replying to me to get my attention. Thanks!<br/>
Please use the QUOTE feature when replying to me to get my attention. Thanks!
I think more filters in general would be a good thing. There are a lot of Asian based apps that I have no interest in, nor do I play Pokemon/Ingress.
Categories for what country you're in or if an app is for gaming/banking/etc... would be nice. Maybe have the API levels it will work with too, and then just not show anything outside of that range.
I suppose someone could just make an F-Droid repo specifically for xposed/magisk apps too, though I would prefer it if it were officially maintained/sanctioned.
Xposed has become an iconic platform for customizing Android OS starting from vanilla to OEM customized versions. @rovo89 has been actively contributing the community. I have discussed my idea in the past but I was left out. For modders but who doesn't have much programming knowledge, Xposed is heaven. So, it should be there as long as there is Android.
It's beyond any gracious comment that Rovo89 deserves. Xposed has changed how we (at least me) look at Android. So, to keep it continuous, we need some enterprise effort. I don't mind if there is a company named Rovo89 and I have to buy a pro version of Xposed that promises to update with future Android versions in a professional way. Like more developers can work on this.
I Rovo89's efforts to in the app is awesome already. I don't know what he is planning for the future Xposed versions but I believe it is an undeniable addition to android and living in android without it will not be the same.
izephyr said:
Xposed has become an iconic platform for customizing Android OS starting from vanilla to OEM customized versions. @rovo89 has been actively contributing the community. I have discussed my idea in the past but I was left out. For modders but who doesn't have much programming knowledge, Xposed is heaven. So, it should be there as long as there is Android.
It's beyond any gracious comment that Rovo89 deserves. Xposed has changed how we (at least me) look at Android. So, to keep it continuous, we need some enterprise effort. I don't mind if there is a company named Rovo89 and I have to buy a pro version of Xposed that promises to update with future Android versions in a professional way. Like more developers can work on this.
I Rovo89's efforts to in the app is awesome already. I don't know what he is planning for the future Xposed versions but I believe it is an undeniable addition to android and living in android without it will not be the same.
Click to expand...
Click to collapse
No business will want to be associate with "Android Hacking" that google is working hard to put a stop. Even if it's a positive one as Xposed.
The source code is there, but no one has a company to "take it over" nor will want to work on someone else idea instead of they're own.
In other words Xposed is Rovo and we should either sit tight and wait for his timing... or move on from Xposed (MM work great for me and i wont move on... but i know that he is only one man with job, life and family besides Xposed... so i accept it may take too long).
Google just is lame to release a new android every year just to change the code enough to make Xposed and other "hacks" harder to be in...
All in all what i want to say is... ppl love to give ideas but they don't understand how things work...
Sit tight... wait... or move on..
Pupet_Master said:
Google just is lame to release a new android every year just to change the code enough to make Xposed and other "hacks" harder to be in...
Click to expand...
Click to collapse
They keep working on making Android more secure. What's strange (or "lame") about that? And face it... Xposed, root access and other "hacks" are security issues.
Didgeridoohan said:
They keep working on making Android more secure. What's strange (or "lame") about that? And face it... Xposed, root access and other "hacks" are security issues.
Click to expand...
Click to collapse
Have admin rights isn't a security issue. I never use a system without it (even windows has it). If the user don't know how to use admin rights with safety.. just don't use it.. Use the limited user account..
Also, make security updates... great... but change the code just to do so and break the tools that we, experienced users depend is lame.
Android never come rooted, who root it know what they are doing and all the risks.
It isn't a security issue.
As no real detail has been given behind the "development" of these new release, please read the below and inform yourself before installing this on your devices.
https://github.com/rovo89/Xposed/issues/230#issuecomment-315959127
This should be stickied for greater visibility.
It's progress even if it is incomplete. I know Rovo prefers to work alone, but it'd be nice to see a small team of Xposed developers working together and sharing the load. I can only imagine how many hundreds of hours have been put into Xposed so far.
Thanks for sharing. Indeed insightful and should be stickied.
Please allow me to quote a post of me:
I'm definitely praying for Xposed eventually coming to Nougat in order to enable me especially to use XPrivacy again for further enhancement of my privacy. I know that most of us have found our individual and custom ways how to "live" without Xposed.
It seems to me there's currently a hype on XDA regarding some ("unofficial") Xposed modules for Nougat 7.1.2 being around. Being curious, I tried one of them myself a few days ago I immediately reverted to my Xposed-free backup. Besides many cries for help, requests for spoon-feeding etc. I quickly realised that many people entered this boat who aren't really familiar with their devices. I really doubt that it was a wise idea by XDA to actively propagate these projects and to create an attraction that they might not deserve yet.
Lots of discussions and comments are already available in the different respective threads but they are already hard to find among all that spam.
I'd rather stay with that what I can read and follow here. For me, these are the details you need to know about possible upcoming times of Xposed for Nougat, where it currently stands, in which way it might walk, the processes, and occasionally what's the views on the mentioned "unofficial" modules are.
But most important for me is to see that Rovo89 himself is in deed working on Xposed for Nougat and that wanam obviously joined the bridge of the Xposed fleet flagship. Both are THE masters of Xposed in my personal opinion - and they both seem to be in hot.:good:
EDIT: Please allow me to quote my highly esteemed friend @Davey126. I always benefit from his clear, rational insight and actually wisdom as well as I'm enjoying his British language and humour (written with "ou"!):
"The nature of Xposed framework produces a shotgun-on-a-marry-go-round set of impacts where a huge community is forced into a respond when untested change is introduced. You already see criticism mounting due to perceived issues with Magisk; no doubt that will quickly expand to module developers who will be accused of dodging their implicit volunteer responsibilities (huh?) by not supporting the handful of Franken-Frameworks that emerge from this effort. To be clear I am NOT against public alpha releases or going out on a limb to help ferret out issues. However, that is not the way the initial roll out has been handled, at least to date. Unbridled turmoil does not always lead to better outcomes.
Time to step away from this discussion and OT posts to this thread. There are no winners/losers; just various islands of thought that different people choose to inhabit (and defend)."
His original post is available here.
Click to expand...
Click to collapse
[EDIT (2017-08-01):] Anyhow, Xposed on Nougat is now working for me. If interested please refer to this post.
noc.jfcbs said:
Please allow me to quote a post of me:
Click to expand...
Click to collapse
You're so wrong there. No one is forcing anyone to try an unstable version (and it is said EVERYWHERE that this is a very unstable WIP). Anyone going in knows the consequences or should had read before.
And it is great to see a ton of people on this now. Both xposed for N and modules are being tested on N even if this is an unofficial half-assed hack. And this will get a ton of modules ready updated for N.. for if official N ever appears (which probably won't).
RusherDude said:
You're so wrong there. No one is forcing anyone to try an unstable version (and it is said EVERYWHERE that this is a very unstable WIP). Anyone going in knows the consequences or should had read before.
And it is great to see a ton of people on this now. Both xposed for N and modules are being tested on N even if this is an unofficial half-assed hack. And this will get a ton of modules ready updated for N.. for if official N ever appears (which probably won't).
Click to expand...
Click to collapse
Yea, i may understand Rovo post... but he really missed the point of those forks too.
It is a good thing to have those new ideas and something that seen impossible now look managable.
Ppl want Xposed for N, this is the best we have so far.
So far it seems development has ended on this project. After so long of happy modding not able to be done otherwise unless you get a custom ROM, or depending on what you need nothing else can do, anyone (like myself) who is on or upgraded to pie gets no official Xposed support.
Sure, there's EdXposed but it's closed source, and therefore suspect with what it can do to my system and I've heard of issues with it on some devices. If something is making or capable of making such change to my device, I better be able to inspect the source myself and it better have the public eye on it
And there's Tai Chi, but it's mostly in Chinese, which I don't happen to speak. Also not quite as capable
So is there any planned support for Android version beyond 8.1? I mean, Q/10.0 is already in beta. If there isn't, then has development stopped and if so why?
If needed, @rovo89, myself and I'm sure the community would be more then happy to pitch in. I and many others are grateful to what you did, and would be happy to help or carry on your hard work. I personally hold you in high regard, and I mean that seriously. I'm not sure who is more important in the Android modding community: @rovo89 or @topjohnwu
Because development is not necessary to the developers at all.
Please read this:
https://forum.xda-developers.com/showpost.php?p=79162792&postcount=5
EdXposed is IMHO as official as Xposed is and is not a clone and is not and has never been closed source.
clcombs262 said:
Sure, there's EdXposed but it's closed source, and therefore suspect with what it can do to my system and I've heard of issues with it on some devices. If something is making or capable of making such change to my device, I better be able to inspect the source myself and it better have the public eye on it
Click to expand...
Click to collapse
https://github.com/ElderDrivers/EdXposed
Happy inspecting
In fact, sources of "official" Xposed haven't been released for Oreo so far.
C3C076 said:
https://github.com/ElderDrivers/EdXposed
Happy inspecting
In fact, sources of "official" Xposed haven't been released for Oreo so far.
Click to expand...
Click to collapse
Flat style colored keyboard module works with edxposed on pie?
clcombs262 said:
Sure, there's EdXposed but it's closed source, and therefore suspect with what it can do to my system and I've heard of issues with it on some devices. If something is making or capable of making such change to my device, I better be able to inspect the source myself and it better have the public eye on it
Click to expand...
Click to collapse
search and read properly.
Since when EdXposed is closed source?
Thread Closed as per Op's request.
Thanks
SacredDeviL666.