Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Thread Closed

Xposed - Legacy thread. Don't panic, Xposed is still here.

OP rovo89

2nd February 2014, 11:40 AM   |  #8421  
Junior Member
Thanks Meter: 3
 
27 posts
Join Date:Joined: Jun 2005
Muy case is almost the same... Mtk6592... Zopo zp990+ octa corte... Same specs as zp998 bit screen size... After installing with no modules activated... Boot loop!!!!

Sent from my GT-I9300 using XDA Premium 4 mobile app
2nd February 2014, 12:42 PM   |  #8422  
.rootCoder.'s Avatar
Senior Member
xda ;)
Thanks Meter: 154
 
217 posts
Join Date:Joined: Nov 2013
Donate to Me
Thanks a lot sir for you your project !
it's helping me making my smartphone faster and secure !
Thanks Agin
The Following 5 Users Say Thank You to .rootCoder. For This Useful Post: [ View ]
2nd February 2014, 01:05 PM   |  #8423  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 15,016
 
2,383 posts
Join Date:Joined: Jan 2012
More
Quote:
Originally Posted by ryebread761

When a method wants an int for my drawable, what should I give it? I tried

Code:
modRes.fwd(R.drawable.my_drawable).getId()
but it didn't seem to work.

It isn't enough to give the ID of your drawable to the app because it wouldn't know how to resolve it properly. Use the XResources.addResource() method instead. Xposed will give you a new resource ID that you can use and will automatically set up a redirect from that ID to your resource.

Quote:
Originally Posted by scar200

Hi!
Firstly, I'd like to say this awesome work.

However, I have a problem on my Huawei U9508, after installing the framework, just the framework, it breaks my EMUI theming, all the custom icons revert back to the original icons and no amount of changing themes and restarting will help.

Unfortunately, this means I have to remove the framework and can't use all the fantastic modules that are available.

Any clue if this can or will be fixed?

Thanks in advanced, and a Happy Lunar New Year to all those that celebrate it. =)

Yeah, theming engines become more and more of a problem. There are so many of them and basically Xposed is one of them as well, which is the reason for these conflicts. Sometimes it's possible to work around these conflicts, but often it requires much time (which I don't have), especially if it doesn't appear on my own device and I have to give step by step instructions for remote debugging.
Maybe I'll add a "disable resource replacement" setting in the future so you can get at least some modules working.

Quote:
Originally Posted by Rohit99

Sir I've installed latest version of xposed frame work
it seems like its not working check out the screen shot

Yes, the smaller version of Busybox conflicts with some ROMs. I can compile Busybox differently, but that will make it much larger, which I don't want to put on 99.9% who don't have this issue and also not on my hosting account traffic. I'm currently testing an approach where the bigger Busybox executable can be installed as a separate package, which seems to be working nicely.

Quote:
Originally Posted by n3ptun3

So, I had Xposed working just fine with my Moto X 4.4, today I received an OTA update to 4.4.2, and kept my root.
Installation goes ok, but if I do a hard reboot, it won't work, doesn't detect as installed on the main screen, but inside installation screen it shows as installed. If I install again and do a soft reboot, it works. If I hard reboot later, it doesn't work, I have to do a install/soft reboot afterwards.
Same goes for updating and installing modules.
Would a boot logcat + soft reboot logcat help?

No, that's basically like HTC's S-On, which resets /system on reboot. You have to flash the Xposed files. Next version will have that function builtin, for now check the first post for a link.

Quote:
Originally Posted by dams161

hello
I made 2 of bootloop logcat
if someone can help me thank you @rovo89

The second log at least includes some lines with "Xposed". It also shows several lines which look like a theming engine. So maybe this is another conflict here. Not much I can do at the moment. In case I add the setting mentioned above in the future, you can try again.

Quote:
Originally Posted by dams161

i can probably find the sdk is not the correct version

D/Xposed ( 283): Starting Xposed binary version 46, compiled for SDK 16

D/Xposed ( 283): Phone: BS472 (TCT), Android version 4.2.2 (SDK 17)

No, that's fine. The binary is compiled for SDK 16, but it works on SDK 17 and SDK 18 as well.

Quote:
Originally Posted by BotsOne

I'm having an issue trying to hook a method. I can't seem to get it to work no matter what I do. I'm probably doing something stupid but I can't figure it out!

First off I used apktool and looked at the smali code to find some names of methods that sound like a good hook point. Found the perfect one. My code is as follows:
...
can anybody help with this?

Quote:
Originally Posted by GermainZ

Keep it as an object, then call isRecording using callMethod and cast that to a boolean. I think that should work.

Code:
Object recorder = XposedHelpers.callStaticMethod(recorderClass, "getInstance");
boolean isRecording = XposedHelpers.callMethod(recorder,"isRecording");
if (!isRecording)
    XposedHelpers.callMethod(recorder,"start");

I think you need to cast the result of the second callMethod() to Boolean before, but in general, that should be the answer. You have a direct reference to the VoiceRecorderHelper class in your own class. So Android tries to resolve it with the classloader of your class and can't find it.

Quote:
Originally Posted by Ramis

Hey rovo,

Since I am having issues reading the settings file from my hooks I was thinking of copying the preferences file to a folder on the sdcard and then reading the preferences from there. Of course my first instinct was to extends the XSharedPreferences class but its final. So I was wondering if I just make my own class which is a exact copy of your XSharedPreferences, (except with a change in location) would it work?

(Also I of course tried it before asking and I am not able to import the XmlUtils class. It can't seem to find it. Could you point me to the library you used?)

The easiest way would be to use the constructor takes a File as parameter, then you can use your own location.
I linked the framework against a JAR which includes the hidden methods of AOSP as well.
The Following 11 Users Say Thank You to rovo89 For This Useful Post: [ View ]
2nd February 2014, 01:47 PM   |  #8424  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 15,016
 
2,383 posts
Join Date:Joined: Jan 2012
More
The ART of patience
Regarding ART possibly becoming the default runtime engine: I think that's good news because it means that we will get a stable version of ART then. I'm reluctant to work further on ART support at the moment for mainly three reasons:

1. Time. I used to spend every evening and every weekend for Xposed, either to give support here (often answering the same questions again and again), writing code or researching about bugs or new ideas. As you may have noticed, there are now days or even weeks where I don't even log on to XDA, and I'm actually glad about this.

2. Experimental software is bound to contain bugs, even severe ones. There is a reason why Google didn't make this choice available for the typical user (and keep in mind, we are not typical users). I neither want people to blame Xposed if their phone starts acting up nor do I want to hunt bugs which are caused by a runtime engine that is explicitely labelled as not finished yet.

3. As long as ART is experimental, it's much easier to make big changes to the code. Once a final version is out and used by the masses, quality engineers we be much more careful not to break things. That means that Xposed for ART on 4.5 (or whatever it will be called) might need to be completely different than for ART on 4.4. More variants means more time for maintenance. And I don't feel like pushing something out now just to drop support again in a later version. There is not enough benefit of using ART at the moment to justify that.

You know, I had already worked on ART support and spent several dozens of hours reading the code, looking for ways to hijack it, implementing my ideas, doing trial and error and starting again from the beginning. I finally had my Nexus 5 boot with Xposed in early December and quickly tested the App Settings module. I'm happy about that, but I also know that this was just a very experimental version, less ready than ART itself. It is totally hacked together and only tested with the stock ROM. ART is quite complex and has several different modes. It's not worth giving the current development to someone else before I have tested these things on my phone, where I can debug much better than instructing someone else to do it. It also requires rewriting app_process to be a light executable again, which loads either the Dalvik or ART Xposed library, depending on your settings. That would require changes in the installer as well, etc. etc.

So you see, there is still lots of work to do. At the moment, I'm not actively working on it, but trying to get some other things fixed (e.g. LG ROMs) or improved (installation via recovery, better installation feedback in case root access failed, static Busybox package). And as I said, I do have other things in my life as well. It's not about money, that's what I have my full-time job for. I work on Xposed for fun (and maybe a bit for the reputation ), so the best way to ensure that I keep on working on it is not taking away the fun part of it. Don't pressure me like it was my duty to implement something ASAP (!!!), be patient even if it takes a bit longer until I answer and join the volunteers who help answering basic questions here so I don't have to. Thanks!
The Following 442 Users Say Thank You to rovo89 For This Useful Post: [ View ]
2nd February 2014, 02:01 PM   |  #8425  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 15,016
 
2,383 posts
Join Date:Joined: Jan 2012
More
Forgot to mention one more thing. It's unlikely that Xposed will work for ART on the day the next Android version is released. The very important "start from scratch" research is done, but as I said, I need to see how the final version works. It seems that Dalvik will still be available, for those who claim that they can't live without Xposed. Whatever may happen, remember my words about patience and fun.
The Following 119 Users Say Thank You to rovo89 For This Useful Post: [ View ]
2nd February 2014, 02:03 PM   |  #8426  
dams161's Avatar
Senior Member
Thanks Meter: 110
 
915 posts
Join Date:Joined: Apr 2012
@rovo89
and if I chanche my launcher
what do you call an engine theme
Last edited by dams161; 2nd February 2014 at 02:13 PM.
codmaster
2nd February 2014, 02:22 PM   |  #8427  
Guest
Thanks Meter: 0
 
n/a posts
Quote:
Originally Posted by rovo89

Regarding ART possibly becoming the default runtime engine:

I think that's good news because it means that we will get a stable version of ART then. I'm reluctant to work further on ART support at the moment for mainly three reasons:
1. Time. I used to spend every evening and every weekend for Xposed, either to give support here (often answering the same questions again and again), writing code or researching about bugs or new ideas. As you may have noticed, there are now days or even weeks where I don't even log on to XDA, and I'm actually glad about this.

2. Experimental software is bound to contain bugs, even severe ones. There is a reason why Google didn't make this choice available for the typical user (and keep in mind, we are not typical users). I neither want people to blame Xposed if their phone starts acting up nor do I want to hunt bugs which are caused by a runtime engine that is explicitely labelled as not finished yet.

3. As long as ART is experimental, it's much easier to make big changes to the code. Once a final version is out and used by the masses, quality engineers we be much more careful not to break things. That means that Xposed for ART on 4.5 (or whatever it will be called) might need to be completely different than for ART on 4.4. More variants means more time for maintenance. And I don't feel like pushing something out now just to drop support again in a later version. There is not enough benefit of using ART at the moment to justify that.

You know, I had already worked on ART support and spent several dozens of hours reading the code, looking for ways to hijack it, implementing my ideas, doing trial and error and starting again from the beginning. I finally had my Nexus 5 boot with Xposed in early December and quickly tested the App Settings module. I'm happy about that, but I also know that this was just a very experimental version, less ready than ART itself. It is totally hacked together and only tested with the stock ROM. ART is quite complex and has several different modes. It's not worth giving the current development to someone else before I have tested these things on my phone, where I can debug much better than instructing someone else to do it. It also requires rewriting app_process to be a light executable again, which loads either the Dalvik or ART Xposed library, depending on your settings. That would require changes in the installer as well, etc. etc.

So you see, there is still lots of work to do. At the moment, I'm not actively working on it, but trying to get some other things fixed (e.g. LG ROMs) or improved (installation via recovery, better installation feedback in case root access failed, static Busybox package). And as I said, I do have other things in my life as well. It's not about money, that's what I have my full-time job for. I work on Xposed for fun (and maybe a bit for the reputation ), so the best way to ensure that I keep on working on it is not taking away the fun part of it. Don't pressure me like it was my duty to implement something ASAP (!!!), be patient even if it takes a bit longer until I answer and join the volunteers who help answering basic questions here so I don't have to. Thanks!

Thanks for all your work. You are amazing, man!
2nd February 2014, 02:25 PM   |  #8428  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 15,016
 
2,383 posts
Join Date:Joined: Jan 2012
More
Quote:
Originally Posted by dams161

@rovo89
and if I chanche my launcher
what do you call an engine theme

A theming engine provides extension points for apps or the ROM itself to change the resources (like images, colors etc.) at runtime. It's a part of the ROM, not of the launcher, so it won't make a difference if you change your launcher.
The Following User Says Thank You to rovo89 For This Useful Post: [ View ]
2nd February 2014, 02:42 PM   |  #8429  
dams161's Avatar
Senior Member
Thanks Meter: 110
 
915 posts
Join Date:Joined: Apr 2012
Quote:
Originally Posted by rovo89

A theming engine provides extension points for apps or the ROM itself to change the resources (like images, colors etc.) at runtime. It's a part of the ROM, not of the launcher, so it won't make a difference if you change your launcher.

ok thanks
Xposed but walking on Hungarian phone
2nd February 2014, 03:02 PM   |  #8430  
Falseclock's Avatar
Senior Member
Flag Almaty
Thanks Meter: 317
 
517 posts
Join Date:Joined: Jun 2012
Donate to Me
More
Quote:
Originally Posted by GermainZ

Keep it as an object, then call isRecording using callMethod and cast that to a boolean. I think that should work.

thanks you!!! now getting understand how it works )))

Thread Closed Subscribe to Thread

Tags
don't ask questions about modules here!!!, framework, xposed
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes