首页 > 忘记密码 > 为什么安卓7.0 不能装xp 框架无法激活xp 框架 安卓7.0 xp框架激活
2017
06-14

为什么安卓7.0 不能装xp 框架无法激活xp 框架 安卓7.0 xp框架激活

看上去越来越多的人对于Android 7.0版本的Xposed框架能否以及什么时候能够发布表示担忧,因此我(作者rovo89)觉得有必要说两句。
首先,为什么Android7.0的版本耗费了如此长的时间?因为每次的发布作者都要努力确保Xposed与新的ART版本能够完美适配,不是从Lollipop 到 Marshmallow这种级别的变化,这可以说是一种飞跃,甚至能够在某些方面能够让Xposed与Android系统结合的更完美,而Xposed则可以更加简洁,基于以上的种种,作者需要小心对待。

 如果你是安卓 6.0 一下可以直接联系qq765138898  远程就可以帮你激活xp 框架

总之是由于Android 7.0本身的一些变化加上作者的时间并不是很充沛造成了这个版本拖得如此之久,按照作者自己的比方假如每天倒腾24小时,可能一两周也就能搞定,但现在的情况是可能一个月也不见得有24小时能够用于Xposed的开发,所以对于Android 7.0 的xposed框架什么时候能够发布,作者也是不确定的,大家耐心等待吧。

It seems that more and more people get nervous about whether (and when) there will be Xposed for Nougat or not, so I felt I should say something.

Why does it take that long? Because with every release, I try to ensure that Xposed integrates nicely with the improvements in the new ART version. The step from Lollipop to Marshmallow wasn't huge. It was an evolution, some things even made it possible to integrate Xposed in a more elegant way. On the whole, it was mainly careful porting than rather innovating.

With Nougat, something fundamental has changed. If you're using Nougat already, you'll have noticed that installations are much faster now. That's because APKs aren't compiled immediately (AOT), but start in (slower) interpreting mode. Sounds bad, but they have enabled JIT, which will quickly compile those methods that are used very often. That will restore the well-known and constantly improving performance of native code. Besides that, ART keeps a list of these frequently used methods ("profiling"). When the device is idle, it finally does the AOT compilation, but based on the profiling data. After that, you get the great performance right after starting the app. JIT is still waiting in case the usage patterns change, and I think it will also adjust the profile and improve the AOT compilation.

That results in various different compilation states and more complexity. Besides that, there were many issues in the past caused by Xposed's need to recompile the whole ROM and all apps: It sometimes caused boot loops when the odex files were too heavily pre-optimized, it blocked quite some storage space to store the recompiled files, and I needed to disable some optimizations like inlining and direct pointer calls. I hope that I can make use of the JIT compiler to avoid that in Nougat. If Xposed knew from where a method is called, it could invalidate the callers' compiled code, so that they would temporarily use the interpreter. If they're important enough, JIT will recompile them.

I have already done a lot of research and experiments for this and I'm currently trying to implement this. But as you can imagine, all of that is much effort and can easily take hundreds of hours. That's net (working) time, not real time. If I worked on Xposed 24 hours a day, that might be done within a week or two. But, in the last year or so, my "time for Xposed stuff" was about 5 hours a week, sometimes more and sometimes less. You can do the math yourselves... There are just so many other (non-technical) things that I need or want to do. If you substract the time it took me to build the new installer version, move the repo to a new server and restore compatibility with the Nov 2016 security patches, that's even less time for new stuff.

So yes, I'm still working on Nougat support, whenever my free time allows it, but I don't have any idea when it will be done. Once it's done, you'll know.


 

本文》有 0 条评论

留下一个回复