Why haven't you put in Repo? Having it only in forum makes me have to create an account just to download it.
Xposed - Legacy thread. Don't panic, Xposed is still here.
- Thread starter rovo89
- Start date
- Status
Memory leak ...
Thank you for a great new tool and idea!
I am using Xposed on an S3 and I might have seen something that looks like a very slow memory leak in some part of the system that does not appear visible in the normal end-user statistics - the leak was very slow and would become bad only after like 8+ hours when the remaining memory for apps would slowly become smaller and smaller and apps would start to be closing almost at random.
How should I further research any such slow memory leaks? For the moment I am trying a few days without Xposed and so far it appears some change took place but I can not say anything for certain without more extensive tests!
Thank you again for all the great work.
Thank you for a great new tool and idea!
I am using Xposed on an S3 and I might have seen something that looks like a very slow memory leak in some part of the system that does not appear visible in the normal end-user statistics - the leak was very slow and would become bad only after like 8+ hours when the remaining memory for apps would slowly become smaller and smaller and apps would start to be closing almost at random.
How should I further research any such slow memory leaks? For the moment I am trying a few days without Xposed and so far it appears some change took place but I can not say anything for certain without more extensive tests!
Thank you again for all the great work.
Last edited:
Re: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
how many apps do you enabled? i have enabled more then 10 apps include firefox, systemui, system etc. and uptime more then 100 hours, everything seems still fast and stable as normal
Send from my note2.
how many apps do you enabled? i have enabled more then 10 apps include firefox, systemui, system etc. and uptime more then 100 hours, everything seems still fast and stable as normal
Send from my note2.
AW: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
are you on 4.2.1?
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
are you on 4.2.1?
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
That's hard to say as you mentioned it's hardly visible. A further problem is that Xposed is integrated in every process. So you can't differentiate between the memory taken by Xposed and the memory needed for the apps themselves. You could compare how much memory certain processes take up usually, how much they take with Xposed enabled and how the usage evolves over time. But as there are many factors for memory usage, I'm not sure how much this will tell you. Also, unused processes will be killed after some time, so the process that was started 8 hours ago might not be the same as the one now.
The one thing that came to my mind when you mentioned apps are getting killed: Did you use the App Settings module and enabled the "resident" flag for some apps? That would keep them into memory as long as possible, thus taking memory away from the other apps.
YES, with Xposed for the moment I was actually ONLY using the resident flag (for exactly 3 programs - phone, contacts and TW; all on 4.1.2 XXEMA2 with Siyah 1.8.9) - but the thing that is stumping me is that the memory taken by those 3 is not increasing almost at all in time (maybe something like 1MB for each of them after 8+ hours), while the overall free memory actually decreases by a significant margin (100+ MB, and most notably no longer 'responds' after forcing to close apps in task manager, since all apps that could be removed from the cache have been already removed, and then apps running in the background have already been gradually stopped).
The next step I will try running ps from adb just after the reboot and then after the 8+ hours and see what differences can be seen. I am now even thinking if the leak could actually be somewhere inside the kernel, but that one seems like a very long shot (and for that one I don't yet have any idea on how I could test, maybe eventually just compare Siyah vs stock, but that way I will temporarily loose dual-boot
).Re: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
Ignoring the perceived memory leak for the moment, are you actually having issues that you can attribute to low memory?
Sent from my Nexus 4 using Tapatalk 2
YES, with Xposed for the moment I was actually ONLY using the resident flag (for exactly 3 programs - phone, contacts and TW; all on 4.1.2 XXEMA2 with Siyah 1.8.9) - but the thing that is stumping me is that the memory taken by those 3 is not increasing almost at all in time (maybe something like 1MB for each of them after 8+ hours), while the overall free memory actually decreases by a significant margin (100+ MB, and most notably no longer 'responds' after forcing to close apps in task manager, since all apps that could be removed from the cache have been already removed, and then apps running in the background have already been gradually stopped).
The next step I will try running ps from adb just after the reboot and then after the 8+ hours and see what differences can be seen. I am now even thinking if the leak could actually be somewhere inside the kernel, but that one seems like a very long shot (and for that one I don't yet have any idea on how I could test, maybe eventually just compare Siyah vs stock, but that way I will temporarily loose dual-boot
Ignoring the perceived memory leak for the moment, are you actually having issues that you can attribute to low memory?
Sent from my Nexus 4 using Tapatalk 2
Re: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
How do I go about doing that? I've changed system ui and I've changed the android system but the lettering in the status bar didn't change. I'm trying to achieve the phablet mode status bar but the notifications within stay at the phone ui.
Sent from the Great White Note
How do I go about doing that? I've changed system ui and I've changed the android system but the lettering in the status bar didn't change. I'm trying to achieve the phablet mode status bar but the notifications within stay at the phone ui.
Sent from the Great White Note
Attachments
Rovo ,
2.1.2 not working in ICJ 2.1 HOX. But 2.0.2 works. Can u please upload all the older versions as well.
Thanks
2.1.2 not working in ICJ 2.1 HOX. But 2.0.2 works. Can u please upload all the older versions as well.
Thanks
AW: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
It should work, but the only way to know is trying it. However, make sure you have a backup and know how to restore it, just in case the disabler.zip doesn't work for you either.
I will only upload older versions for testing whether it works without certain changes. But I won't support older versions, so I don't want people to stay on them. Instead, let me identify what the problem is.
What does "not working" mean? Bootloop? Then please provide a logcat, it should show the reason.
It should work, but the only way to know is trying it. However, make sure you have a backup and know how to restore it, just in case the disabler.zip doesn't work for you either.
I will only upload older versions for testing whether it works without certain changes. But I won't support older versions, so I don't want people to stay on them. Instead, let me identify what the problem is.
What does "not working" mean? Bootloop? Then please provide a logcat, it should show the reason.
Re: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
Hello after i did make changes for play store i just changed its dpi to 265 lots of my apps disappeared from my installed list. And then i erased all changes but they are still missing. Maybe it's not the Xposed app but i think so.
Sent from my GT-N7100 using xda app-developers app
Hello after i did make changes for play store i just changed its dpi to 265 lots of my apps disappeared from my installed list. And then i erased all changes but they are still missing. Maybe it's not the Xposed app but i think so.
Sent from my GT-N7100 using xda app-developers app
Re: [FRAMEWORK] Xposed - ROM modding without modifying APKs/flashing (2.1.2)(05.02.20
Follow the link to villainrom in the first post and try if the module you'll find the fixes it.
Follow the link to villainrom in the first post and try if the module you'll find the fixes it.
No. No bootloop.
After install/update. I press reboot on same xposed app screen.
Then phone reboots to the white htc quietly brilliant screen.
Then full black.
Only my nandroid backup saved me.
If you need logcat.
At what point should i use adb logcat.
After black screen go to recovery and use adb logcat?
Else my nandroid will replace logs. No?
Edit : 2.0.2 works fine on same ROM (icecoldjelly 2.1) according to nimrodity.
---------- Post added at 06:21 PM ---------- Previous post was at 05:56 PM ----------
The play store wont recognise apps since you changed dpi.
Search multi dpi playstore in google. Install it and problem solved
Ok, so the phone doesn't boot anymore after installing Xposed. Can you please do the following?
1. Execute "adb logcat -c" (clears the log, so I don't need to skip over 1000s of old lines)
2. Execute "adb logcat > logcat.txt". You won't see any output as it goes to the file.
3. Click the soft reboot button. It will restart only the Java stack and thus keep the adb connection alive.
4. When you see the black screen, wait a minute to be sure that everything maybe running in the background is done.
5. Press Ctrl+C.
6. Attach the file or it to me via PM.
Logcat is reset at boot time, so yes, if you execute it in recovery mode, it doesn't help.
some features wont work on my phone
I have an htc evo 3d running king cobra gsm i can change the dpi but not the screen size and some other things, is this because my phone was originally ginger-bread or because my phones gsm but i have cheeked my installation a few times so i dont think ive dont anything wrong. if i cant use this app is there another one i can use to change dpi and screen size for specific apps? sorry forgot to say that im having trouble with xposed app settings
I have an htc evo 3d running king cobra gsm i can change the dpi but not the screen size and some other things, is this because my phone was originally ginger-bread or because my phones gsm but i have cheeked my installation a few times so i dont think ive dont anything wrong. if i cant use this app is there another one i can use to change dpi and screen size for specific apps? sorry forgot to say that im having trouble with xposed app settings
Last edited:
Work on galaxy s3 mini i8190 ? I press ''Install/Update'' But open this error;
''[: not found
[: not found
mounting/system writable
[: not found
Created backup of
app_process executable at /
system/bin/app_process.orig
copying app_process...
[: not found
copying XposedBridge.jar...
cp:cant create '/data/xposed/XposedBridge.jar.newversion':
Path does not exist
------------------------------------------------------------
Versions: activate bundled
app_process 31 31
XposedBridge.jar --- 2.1.2
''[: not found
[: not found
mounting/system writable
[: not found
Created backup of
app_process executable at /
system/bin/app_process.orig
copying app_process...
[: not found
copying XposedBridge.jar...
cp:cant create '/data/xposed/XposedBridge.jar.newversion':
Path does not exist
------------------------------------------------------------
Versions: activate bundled
app_process 31 31
XposedBridge.jar --- 2.1.2
- Status
Similar threads
- Locked
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
638Xposed 2.4 beta1/beta2
This is Xposed version 2.4 beta1. The main new features and fixes in this version are:
- Support for Android 4.4 (KitKat)
- Significant performance improvements of the framework
- Viewer for the debug.log in the installer
- Check in the installer whether Xposed is actually active and working
First of all, I would like to thank the 45 people who donated to get me a Nexus 5, from a little "thanks" to huge amounts of money. I was really impressed and hope you like this update.
In detail:
Xposed should now fully support KitKat. As mentioned, that wouldn't have been possible at this time without your support.
Modules should continue to work if they don't rely on AOSP internals that have changed in KitKat. One example: It seems that the battery icon is no longer an (animated) image, but a Java implementation. Obviously, any modules that try to replace the battery image will no longer work. The Xposed framework can't do anything here, the module needs to be rewritten. Therefore, if some of your modules don't work, please get in contact with the module author first. You will probably see an error in the new debug.log viewer in this case.
Xposed isn't compatible with ART, I can't say yet whether it will be in the future (will require a major rewrite if possible at all). As you would get into a bootloop if you try to combine Xposed+ART, Xposed automatically resets the choice to "Dalvik". If you want to test ART, you must uninstall the framework.
The performance improvements apply to the very core of Xposed, the method hooks, in all Android versions. In a test app developed by @exidler, the overhead per call used to be ~71 μs (= 0.071 ms) per call to a hooked method (with one empty callback handler) on my Galaxy S2. Now it's ~13 μs (= 0.013 ms). That's a relative improvement of factor ~5.5x. Thanks to @exidler for the research and several suggestions! I have sent a pre-beta to @kamso, who had reported lags with older versions. Now everything works fine for him. Anyway, I wouldn't say that Xposed had bad performance before. Keep in mind that we are talking about significantly less than a millisecond here.
The debug.log viewer should give a quick impression whether Xposed and modules could be loaded fine. It also includes options to save the log to SD card (so it's easier to transfer it to a PC etc.) and send it via mail.
The Xposed Installer now checks whether the latest version of the framework is active. If not (e.g. because it's not installed yet, you forgot to reboot or something in Xposed doesn't work), you will see a warning in the welcome screen and at the top of the module list.
Finally, there were some other minor improvements and fixes and new/updated translations.
Developers:
As a reminder, please keep the debug.log clean. It's only helpful if it's not as spammed as logcat. You should only use XposedBridge.log() for error messages and other unexpected situations. If everything runs fine, it shouldn't write anything to the log. If you really need to keep some logging in published builds, please use either logcat or make it an opt-in options (i.e. disabled by default and the user enables it if he runs into problems).
Apart from that, there was a little API change: https://github.com/rovo89/XposedBridge/commit/3c18f6f6bd4e0ec57898b3b3a79b5584d0396054
I assume that very few modules use the "extra" field to transfer information between beforeHookedMethod() and afterHookedMethod(). If you do, simply replace it by getExtra().
Layout inflation hooks now also work if the layout has been included in other layouts. That's actually a pretty tricky use-case for the "extra" parameter mentioned about (and other tricky technologies).
If for some reason you need to determine the active XposedBridge version in your module, you can use XposedBridge.XPOSED_BRIDGE_VERSION.
findMethodBestMatch() now also looks for protected and package-private methods in superclasses. That's mainly useful if you use the callMethod() or callStaticMethod() helper.
UPDATE: (beta2)
The new beta should fix the "read-only filesystem" errors. If you used to experience them, please try this version. Otherwise, there is no need (and no advantage) to update.
UPDATE:
The final version is out, please use it instead (see first post / in-app installer).479The 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!317General information on Xposed has been moved to this thread: http://xdaforums.com/xposed/xposed-installer-versions-changelog-t2714053
The FAQ has been moved to this thread: http://xdaforums.com/xposed/-t2735540
Questions, suggestions, bug reports and so on can be posted in the Xposed General forum (for the installer/framework/development only) and in the Xposed Framework modules forum (for anything module-related).222Xposed Framework Installer (Flashable Zip)
Announcement: Xposed Framework v2.5+ comes with an option to flash its own install zip via recovery, making my package obsolete. I'll leave them up for posterity; could be useful should the need arise for downgrading on some devices. Cheers all! 10000 downloads is pretty cool.
Xposed Framework v2.2+ has fixed JB4.3 installation and v2.4+ has added support for KK4.4, but for those that still want it, or cannot install via the APK due to /system write protection like HTC's S-ON, here is an updated zip frontend method for installing the framework; now for Xposed Framework v2.4.1.
You MUST have the Xposed Installer APK installed FIRST. The zip will detect if you do not and stop.
Flash this in recovery and my frontend script (the update-binary) will detect the correct architecture and SDK version to use the appropriate Xposed app_process and busybox builds (x86, armv5, v6 and v7 & sdk 15 and 16+ supported), and should detect the uid of the Xposed Installer APK on-the-fly and set up the required files with it.
It leaves a log behind in /data/local/tmp/xposed-log.txt either way with more details about how it went.
It also unpacks Xposed-Disabler-Recovery.zip to /sdcard/ (or /sdcard/0/ if it exists) to be as close to the APK install method as possible. For those wanting another method to reactivate after a ROM update or toggle Xposed disabled/enabled, @amishxda has also created a cool "Xposed toggler" zip here.
Note: Xposed Framework files and the install.sh used are the work of @rovo89 and @Tungstwenty; I have only created a recovery flashable zip to function as an alternative frontend for the framework installation process. I take no credit for their fantastic work.
P.S. If you found this handy then please check out my Odds and Ends thread for more flashable goodness.
5351 downloads of v2.1.4 when removed. 1049 downloads of v2.2 when removed.193Xposed 2.5 final
This is Xposed version 2.5 (final). The main new features and fixes in this version are:
- Rewritten framework installation/uninstallation
- Uses interactive su (via libsuperuser) to provide improved compatibility with different Superuser apps
- Better feedback when root access fails (doesn't freeze the app anymore)
- Offers installation via custom recovery (CWM/TWRP), either flashing the file automatically or manually
- Safemode to disable Xposed with hardware keys to get out of (most) bootloops
- Compatibility with Sony/LG ROMs (4.3 and 4.4), Meizu ROMs (4.4)
- Debug setting to disable resource hooking as a temporary workaround for incompatibilities with some theming engines (not all modules can be used in this mode)
In case you get a message "Segmentation fault" during installation, you can now download an additional app which provides statically compiled versions of BusyBox (a lot bigger, but should work with every ROM). It's not needed otherwise.
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.
New posts
-
[GSI][14] LineageOS 21 TrebleDroid-based
- Latest: ildar_prophet
-
