yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] mionica:
Oh, there's plenty of those. But SElinux is in permissive mode at that time, so I think it's more likely that between me getting the PID and actually calling flimit, the process actually exits. This seems to be supported by the fact that in the flimit log (v2.5; with v2.5a you can't see that anymore), I've never seen a PID being processed in both iteration #1 and iteration #2 - and if the flimit would have actually failed, the the same PID would have caught in every iteration (until flimit succeeded).

There's another possibility: a fuction that checks whether an operation is allowed, gets called, it says "no" hence the log entry, but the operation is attempted anyway, and it succeeds because SElinux is in permissive mode. But IMO, it's more likely that those were transitory processes - they either forked the intended children then went six feet under on purpose, or they kicked the bucket for some other reason.

Which makes me wonder: suppose zygote ("Z") forks a child ("A"), that child forks another child ("B"), then A exits. In this case, I'll never find out that I have to reset the limits for B as well, because the PID for A no longer exists is pgrep -p $ZPID? Feck I wish I knew more about how linux handled process groups :|

I think I'll try a mod tmr that'd go through all processess after the flimit_restore thing, and check if any of those would need a restore despite not being traceable back to zygote. I hope not, though - i.e. I hope Linux has the sense to change B's PPID to Z when A goes away; if that's not the case, it kinda means that version 2.0 was the most stable to date :D

And there's one more thing. We like to blame Xposed (or at least you seem to :) ), but we don't have a clue whether it's Xposed or Android itself. This just occured to me - they recently released 5.1.1, which reportedly fixed some memory leaks that have been in since 5.0.0 - I wonder if memory's all that 5.0.2's leaking... What about handles? What if Xposed LP only works on other platforms because the kernel devels of those devices had figured **** might hit the fan, so they increased the kernel limits to accomodate a leaky Android?... What if Sony's stock app_process does some crazy Sony-specific things to avoid said leaks, or clean up after them, which Xposed's doesn't?... That wouldn't break SU, which only hooks the file entry, but would break Xposed, which replaces app_process altogether...

Anyway, I'm tired, and I have logcats and dmesgs to look at tmr... :D

---------- Post added at 01:35 AM ---------- Previous post was at 01:25 AM ----------

...and yeah, that's obviously the thing to do. If we talk to the Xposed devs and say, "it doesn't work on our device", I think a "so what?" answer would be actually appropriate. That's why I haven't approached them do date; when I do, I mean to be able to say, "this is what seems to be wrong, this is my analysis, here are my logs; can I help you (help me :D) in any other way?" - there's nothing like a sensible audience to warm the heart of a dev :p and I know that from my own experience :D
[Sony Cross-Device General] infinitylook:
Did a clean install and installed xposed with all nodules i had before everything's smooth and not restarting. Apps restored (not all but mostly) using titanium. It seems everything is good. 2.3 is the version I flashed. Could it be that Xposed is not the root cause? Just wondering.

Maybe a contributing factor are google apps (or some any apps) that are doing memory leaks causing system instability. Xposed just adds to it but with Xposed itself it's manageable with these fixes. Anyway I still have to observe this if it's stable for a day. Would restore apps one by one using titanium to see if it would replicate the problem on v2.3 fix.
[Sony Cross-Device General] jbbandos:
:( flashed 2.5a, wiped dalvik+cache, rebooted, flashed xposed framework, wiped dalvik+cache again, rebooted, and bootloops continue. I have a Xperia z1 compact, running lollipop (of course), and twrp 2.8.5.0
[Sony Cross-Device General] mionica:
Well I'll be. I just wanted to check what happened if I removed the SD card. Bootloop; put the SD card back in, still bootloop. Niiiice :) Wiped dalvik/cache, booting all right.

Looks like there'll be a 2.6 soon - have to figure out exactly what does XZDR do when /storage/sdcard1 isn't available.
[Sony Cross-Device General] _mysiak_:
My guess would be that it ignores init.d scripts as it can't read XZDR.prop file. It should be safer to put the XZDR config file to /cache or internal SD.
[Sony Cross-Device General] mionica:
Ah feck it. Those scripts have to be the worst way to do this; I'll just write a daemon (in .c) then use a single init.d script to start it. C will be _so_ much better :)

Next version will be 3.0 + sources.
[Sony Cross-Device General] RJASSI21:
I'm still on 2.3v with no reboots so far I was on 1.1 and I had the error but now I don't will update if I see any reboots I have z2 .690 also my z2 tab is still on 1.1v same fw thanks for the fix though guys honestly its great so happy working xposed now :)
[Sony Cross-Device General] hasona:
Wonderful support you guys are giving, mine is working but it randomly reboots on random occasions(6 times since last night) but there definitely is progress compared to last week so keep up the good work!
[Sony Cross-Device General] infinitylook:
[MENTION=1103233]mionica[/MENTION] I experienced my first reboot. I was downloading on the playstore. Just want to ask. The only difference between 2.3 and 2.4 is only the ability to edit in the prop file for 2.4 right? While 2.3 has a fixed value?
[Sony Cross-Device General] McBane87:
About Memory-Leak in Lollipop on Xperia:

http://xdaforums.com/crossdevice-dev/sony/clarification-xperia-lollipop-fix-t3087240
[Sony Cross-Device General] pvnsai73:
Can I add this on prf creator
[Sony Cross-Device General] mionica:
Logging is good, FFS.

Here's some nice findings:

by the time we change the flimits of zygote, it had already spawned other processes (at the very least, Xposed's logcat service, xposed_service_system, and system_server). And those obviously inherited the default (1024 4096) limits of zygote, which spells trouble

it seems some of the processes we're attempting to revert the limits of have more open files at that time than we could care to count; in my case, system_server had 952 - which is fine on my system, but I'm pretty damn sure this will be > 1024 for those with cartloads of apps/modules

It looks like 3.0 isn't going to be written in C after all :D
[Sony Cross-Device General] TheQwertiest:
Sadly, that's not the only leak in 5.0.2, there are others, not as big as that one though =)
[Sony Cross-Device General] ondrejvaroscak:
Well, I could have expected that actually... sheet.
[Sony Cross-Device General] mionica:
Here's a teaser for you; package to follow shortly (be sure to scroll down :p):

[i] found flimit settings at /storage/sdcard1/XZDualRecovery/flimit.prop
[v]
[i] 01_flimit starting...
[i] =====================
[v]
[d] during.boot limits from .prop file: soft=[] hard=[]
[d] during.boot limits after normalization: [0 0]
[d] during.boot limits after sanity check: [0 0]
[d] during.boot limits after applying defaults: [4095 4095]
[d] during.boot limits after making parity fixup: [4095 4095]
[i] during boot, using softlimit 4095, hardlimit 4095
[i] byeSElinux is already loaded
[i] waiting for the zygote process to appear...
[i] found zygote process after 1900ms at PID 696
[i] initial zygote flimits: [1024 4096]
[i] new zygote flimits: [4095 4095]
[b][color=red][i] scanning processes that had already spawned from zygote...
[i] 4 processes to check
[i] target PIDs: [1042 1043 1045 1050]
[i] 4 additional processes were updated
[i] > [1042 1043 1045 1050][/color][/b]
[i] applying during.boot flimits - done
[v]
[i] 98_revert_flimit_after_boot starting...
[i] =======================================
[v]
[d] after.boot limits from .prop file: soft=[] hard=[]
[d] other .prop settings: keep.boot.limit=[]
[d] other .prop settings: save.boot.logcat=[yes]
[d] other .prop settings: save.boot.dmesg=[yes]
[d] after.boot limits after normalization: [0 0]
[d] other settings after normalization: keep.boot.limit=[false]
[d] other settings after normalization: save.boot.logcat=[true]
[d] other settings after normalization: save.boot.dmesg=[true]
[d] after.boot limits after sanity check: [0 0]
[d] after.boot limits after applying defaults: [1024 4096]
[i] during boot, used softlimit 4095, hardlimit 4095
[i] after boot, using softlimit 1024, hardlimit 4096
[i] waiting for boot to complete...
[i] boot completed after 33600ms
[i] byeSElinux is already loaded
[i] applying after.boot flimits - iteration #1
[i] 38 processes to check
[i] > target PIDs: [696 1042 1043 1045 1699 2898 2955 2970 3019 3086 3154 3169 3188 3208 3344 3360 3427 3452 3465 3477 3501 3508 3531 3552 3568 3589 3608 3615 3674 3742 3792 3957 3967 4007 4039 4149 4328 1050]
[i] 37 processes were updated to the init defaults
[i] > [696 1042 1043 1045 2898 2955 2970 3019 3086 3154 3169 3188 3208 3344 3360 3427 3452 3465 3477 3501 3508 3531 3552 3568 3589 3608 3615 3674 3742 3792 3957 3967 4007 4039 4149 4328 1050]
[b][color=red][i] 1 processes had to be updated to custom limits: [1699:{952}:1536][/color][/b]
[i] applying after.boot flimits - iteration #2
[i] 5 processes to check
[i] > target PIDs: [4530 4590 4683 4892 5030]
[i] 3 processes were updated to the init defaults
[i] > [4530 4590 4683]
[i] applying after.boot flimits - iteration #3
[i] 2 processes to check
[i] > target PIDs: [5292 5316]
[i] no processes were updated to the init defaults
[i] applying after.boot flimits - done

PS. Usually, "sheet" :D is actually pronounced "sheite" in Ireland, just like "fook" would be usually pronounced "feck" :) And in the pub culture, neither one seems to be offensive at all. I love that!
[Sony Cross-Device General] ondrejvaroscak:
Hmmm that log seems good :)

Newly will be testing it on 23.2.A.0.278 with ne kernel build 3.4.0-perf-g0f9f962 (date 2015-03-11)
[Sony Cross-Device General] joseangel.alv:
I don't know if you are speaking about this:

As it's said in "Defaults:" spoiler and "Error reporting:" chapters, if there is no external storage, XZDualRecovery searchs for XZDR.prop at '/cache/XZDualRecovery'

However, if '/storage/sdcard1/XZDualRecovery' exists, ''/cache/XZDualRecovery'' will not!

(So, If you remove the external SD card where the 'XZDR.prop' file is located, I suppose XZDualRecovery reverts its properties to their default values.)
[Sony Cross-Device General] --jenana--:
Thanks again!

** Maybe a stupI noticed there's a new version of Xposed Framework: xposed-sdk21-arm-20150426.zip in this thread.

** I flashed your 3.0 over former 2.5 and got a reboot immediately. You'll find the logs in attachement.
[Sony Cross-Device General] kris555777:
rollout exposed alpha 3

http://xdaforums.com/showthread.php?p=60366947#post60366947
[Sony Cross-Device General] hispanico957:
Thank... and now we see the feedback on this new release :fingers-crossed:

Hispa
[Sony Cross-Device General] mionica:
Ouch; those logs indicate that the 98_* file didn't get removed; wtf?

Anyway, while I investigate, remove it yourself from twrp (/system/etc/init.d/9*_revert_flimit) - be sure to mount /system before you try that :)

---------- Post added at 08:41 PM ---------- Previous post was at 08:16 PM ----------

Fixed, and 3.0a was attached to post #399 and post #123

Many, many thanks for the early and detailed report; you probably saved a lot of people here from a lot of grief ;)
[Sony Cross-Device General] --jenana--:
You're welcome! :)

I already flashed it again. Your latest fix with rovo's latest Xposed Framework. Everything worked fine, no reboots yet. Logs in attachment, if you can use them :)

At the moment I only have 01_flimit and 98_revert_flimit_after_boot in that directory.

Now I'll use 3.0a !
[Sony Cross-Device General] mionica:
You attached 2.5a logs :)

EDIT: never mind, I just saw the "Now I'll use 3.0a" part.
[Sony Cross-Device General] nurps:
Well I guess the interesting question is, will the new xposed work without that sonyfix?
[Sony Cross-Device General] norti:
There is not too much change in it (not Sony related at least), I don't think so.
[Sony Cross-Device General] hispanico957:
...mionica if we want try new relase of Xposed, you suggest to install it form recovery (already xposed-sonyfix 2.5 installed) or better after flash xposed reflash sonyfix to avoid the new xposed write something new in system ?

Thank

Hispa
[Sony Cross-Device General] --jenana--:
He, that first part is weird. It's absolutely possible that I didn't flash the version I intended to flash (I intented to flash the same 3.0 at that point), but I didn't ever download 2.5a;

Probably it doesn't matter anymore, but OR I did something without realizing what I did, OR the script didn't log the correct version-number? Oh well, latest Xposed + fix 3.0a -> everything working fine, no unexpected behaviour!
[Sony Cross-Device General] mionica:
what does post #123 say about xposed-sonyfix and xperia_arm? :p

---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------

Oh sorry. I said "2.5a", but I meant "something older than 3.0" :)

Here's how this works: since 3.0, you should only have flimit.log, dmesg.log.bz2, logcat0.log.bz2 and logcat1.log.bz2; and flimit.log should end with " 01_flimit done. " - if you have anything below that, either the 3.0a installer fecked up again by not removing 98*, or you're on something older than 3.0

You can tell the difference by looking for [d] during.boot limits from .prop file: a bit under 01_flimit starting...

Anyway, check if you have a 9*_revert_flimit* file in /system/etc/init.d, and remove it if so.
[Sony Cross-Device General] --jenana--:
Oh I know that one!

Xposed-sonyfix doesn't depend on Xposed-arm!

Which means something like: who cares! Our scripts doesn't do anything with Xposed, it only does some magic while we're in a boot, so Xposed can't **** it up :)

Which means something like: choose whatever Xposed-arm you 'ld like to choose.
[Sony Cross-Device General] hispanico957:
Yes... installed new release ox xposed, after upgrade sonyfix-3.0a and all run fine :good:

Hispanico
[Sony Cross-Device General] ogunja:
Off - Really all involved are committed to solve the problems presented in Xposed. I would like to thank everyone and XDA-Developers for providing this for us Android users. @mionica [MENTION=410007]Nut[/MENTION] [MENTION=6351145]ondrejvaroscak[/MENTION] @McBane87 [MENTION=4419114]rovo89[/MENTION] [MENTION=3989065]serajr[/MENTION] [MENTION=1897172]redincali[/MENTION] @Androplus @moly82 sorry if I forgot someone
[Sony Cross-Device General] ImADev:
You can ignore this post. I've fixed the problem.

This workaround works great for me. Hopefully we'll see it officially patched soon.
[Sony Cross-Device General] alinghi100:
Does the new alpha version 3.0 of xposed need this fix too or it solves the reboots? Thanks :)
[Sony Cross-Device General] mionica:
We'll know shortly. I nearly caught the ****er - now I understand exactly why the first boot after a /cache wipe works. WIll update you guys shortly.

EDIT: yes, sonyfix is required with alpha-3 too.
[Sony Cross-Device General] mionica:
completely new, and way better, fix

Guys, now that I understood exactly what was happening, I was able to put together a better fix than xposed-sonyfix :)

It's called xposed-leak_workaround.zip, and it's attached to the release post. You will most certainly still get random reboots with that - but it's been designed specifically to make those as rare as possible. Oh, and it's a lot simpler. And it isn't going to need updates, since it can't be done better than that (rofl)

The bad news is, it's still required; the good one is, I think I was spot-on with the analysis, so we sould see an Xposed that doesn't need any fix pretty soon :D
[Sony Cross-Device General] Depump:
i waiting xposed stable in LP

LP very sensitive when i use it without fix tool anymore

Bootloop so much so i back to KK temporary

and you can do it xposed back to stable again

You're Rock :good::good::good:
[Sony Cross-Device General] Vic.:
I advise you to post that on the GitHub bugtracker, as that thread is going to be filled by Samsung users.
[Sony Cross-Device General] sgiannouris:
Wow! Just - you definitely deserve a medal for all those efforts! Thanks!
[Sony Cross-Device General] xtremepredador:
Thanks friend your great efforts , I've been using since the first version and has always been stable, Not Reboot ! :D:D
[Sony Cross-Device General] Depump:
setup step as use following

http://xdaforums.com/showpost.php?p=60342525&postcount=331

or not ?
[Sony Cross-Device General] redincali:
You need a donation link mionica. I'll donate to it =) (next Friday on pay day)

~ via Xperia Z3, XDA App
[Sony Cross-Device General] hispanico957:
.. mionica also with new last release xposed-leak_workaround, if someone install it, first time on system with Busybox installed, it's prefer unistall the app and after install again Xdialrecovery prom pc and after install the leak_workaround ?

Thank

Hispa
[Sony Cross-Device General] vcdwelt:
Just for information...

[MENTION=4419114]rovo89[/MENTION] catched your infos and will have a look. Maybe he will release a Debug Version to nail down the issue.

Infos:

Source: https://github.com/rovo89/Xposed/issues/31
[Sony Cross-Device General] tenasama:
Sadly, my Z2 still meet bootloop on v3.0b,

but it goes well with the flimit_flashable_2048.zip from [MENTION=4712883]McBane87[/MENTION] .

here's my logcat, thx :p
[Sony Cross-Device General] pvnsai73:
Can I add this fix and xposed framework zip on prf creator as we dnt have dual recovery on lollipop firmware that we received recently

....plzz reply kindly frns

Thanks in advance
[Sony Cross-Device General] gioiellino:
THERE IS NEW ALPHA 3

http://xdaforums.com/showthread.php?t=3034811

---------- Post added at 09:40 AM ---------- Previous post was at 09:37 AM ----------

Changes:

- Fixed issues with replacing drawables

- Fixed NoSuchMethodError in handleInitPackageResources

- Possibly fixed some errors on ROMs that start in permissive SELinux mode and switch to enforcing mode later
[Sony Cross-Device General] mionica:
Well that was the point ;)

I know from my own experience (:p) that devs hate "it doesn't work" reports, but they love "here's what's wrong" reports - I know I do. So I did what I could to pinpoint the issue, with some success, I think :)
[Sony Cross-Device General] Wolfbreak:
Very good work mionica! Becouse of your effort we will soon have a fully bugfree working Xposed for Xperia Devices on LP.

I just saw serajr and greg2001 are soon done with the LP Version of their Xposed Modules so finally its looking good for Xposed on LP.
[Sony Cross-Device General] Jackos:
Superb job [MENTION=1103233]mionica[/MENTION]! Really glad we could cross paths again :)
[Sony Cross-Device General] baha76_s:
hahahah spoon-feeding you means ....

good job mionica, about 10 hours after installing your (xposed-leak_workaround) with the xposed framework alpha 3, without any crash or sudden reboot (only one reboot ;) after heavy using of phone - installing heavy apk and calling at the same time).

so you must consider yourself as one of the (Grate God) in the (World of Xposed - WoX) hahaha.

thanks
[Sony Cross-Device General] mionica:
Actually, I'm a sucker for [MENTION=3989065]serajr[/MENTION] 's work, which is the main reason why I put the effort into this. If I weren't the kind that drools over serajr's Xperia Xposed, I probably would have said, "ah, a bug; oh well, they'll fix it, let me check again in a while"; I'm using other Xposed modules too, but that's the one I can't live without :)

...said one of my heroes, the guru of TP2. Thank you kindly, Sir! :)

ummm. "alpha" means, typically, more issues than you can track, so like Tesco famously says, "every little bit helps" :D
[Sony Cross-Device General] new_world_2006:
Guys ,

flashing the xposed-leak_workaround and the arm is enough ?

should i do anything more ? like flash the two zip files also ?

---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------

[MENTION=1103233]mionica[/MENTION]!

Guys ,

flashing the xposed-leak_workaround and the arm is enough ?

should i do anything more ? like flash the two zip files also ?
[Sony Cross-Device General] ondrejvaroscak:
No, flash leak workaround zip the xposed.
[Sony Cross-Device General] new_world_2006:
i tried that but it bootloop once i installed the xposed installer apk

i used the latest version on xposed (alpha 3)

are you sure that i dont have to edit\script\flash anything else ?
[Sony Cross-Device General] ondrejvaroscak:
And did you try previous version? For example 3a
[Sony Cross-Device General] new_world_2006:
actually i didnot find it , could you please advise where i can download it ?

---------- Post added at 01:37 PM ---------- Previous post was at 01:27 PM ----------

or do you mean to install (sonyfix 3.0a zip then the workaround zip ?)
[Sony Cross-Device General] ondrejvaroscak:
No, only one of them. On post #123 are both zips. Flash leak workaround. If it still bootloops try version 3.0b instead.
[Sony Cross-Device General] new_world_2006:
i installed xposed-sdk21-arm-20150426\

then

xposed-leak_workaround

boot to the system successfully , then install the APK file , then restart the phone , the bootloop come again

i have LP 5.0.2
[Sony Cross-Device General] Bartekreaper:
Xposed workaround is just a newest version after sonyfix? I will try now to see if it work on my z1 compact [emoji14]

Wysłane z mojej Z1 compact przy użyciu Tapatalk
[Sony Cross-Device General] ondrejvaroscak:
Exactly
[Sony Cross-Device General] ondrejvaroscak:
So try version 3.0b instead.

After bootloop go to recovery Mount system, Advanced, File Manager and delete /system/etc/unit.d and flash version 3.0b
[Sony Cross-Device General] hispanico957:
Also can try to unistall xposed with tool of mionica. Reinstall from pc Xdualrecovery 2.8.14 reboot install xposed-leak_workaround reboot. At this point go to recoevry and install new release of xposed.

Hispa
[Sony Cross-Device General] Masoud.Ser:
thanks mionica

but please With the coming release or a new method

put Notify installing how?(op how?) Because it's really confusing and If an error occurs during installation problem :(

Thanks again
[Sony Cross-Device General] --jenana--:
Seriously, this is a forum for developpers and enthousiast about Xposed. The purpose of the scripts is explained in detail in post #123. The only requirements for this fix are:

- Have recovery.

- Read post #1 and post #123

The only thing you have to do, is flash the zip. It's ok if you don't know how to flash a motherf*ckin' zip, but in that case maybe it's not a good idea to install software-in-development at all. If you still want to know how to flash a motherf*ckin' zip, this isn't the right place to discuss it.
[Sony Cross-Device General] ondrejvaroscak:
Repetition is mother of wisdom...
[Sony Cross-Device General] Juventus1897:
Calm down lad
[Sony Cross-Device General] ondrejvaroscak:
Maybe he used some harsh language, but it is not inappropriate because if it is too complicated to read through simple instructions and realise what and how the script does then better stick to stock. Really. Or do you guys need a nice video tutorial?!