yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] mionica:
I can't think of any problem. You'll be left with one extra flimit file in /system/bin (I store mine in /system/xbin), and I think with a leftover .prop file somewhere, but that's it. No problems whatsoever.
[Sony Cross-Device General] TheQwertiest:
Hm... I encountered a strange problem after installing the .zip with fix (the flashable zip with 2047 limit, not the one in OP): while it fixed the bootloop with xposed, it broke FolderMount app (this app links one folder to the other)... Though it might be caused by SELinux disabling...
[Sony Cross-Device General] hispanico957:
Ok but sorry.... i dont understand if new flash write file and command in different position of file respect old workround of McBane87 ? I see in my device and i have flimit file in /system/bin...

And i see xposed-uninstall ...this unistall all file installed from xposed and not like flimit_undo_full_flashable.zip that unistall only the procedure of workround !?

Thank

Hispa
[Sony Cross-Device General] mionica:
Well, I personally think that extra bin files should stay in /system/xbin, so that's where I put the thing. After you flash my package, you can safely delete the one in /system/bin. The important file, the one in /system/etc/init.d/, gets replaced by my package.

True. Uninstalling my package only requires deleting /system/etc/init.d and /system/xbin/flimit - and potentially editing XZDR.prop; it isn't worth the effort to make an update package for that IMO. Now, with the overall Xposed that's a different story, there's a lot of console work to remove, so it deserves an uninstaller; that's why I provided one.
[Sony Cross-Device General] hispanico957:
...thanks all clear now, but compared to the previous flimit (4096), your file is more suitable and / ormay Sharpening system stability ??

Thank again for your work

Hispa
[Sony Cross-Device General] mionica:
Huh? What SElinux disabling? What my scripts do is, they check if byeSElinux was loaded; if it was, they just do the flimit thing, and if not, byeSElinux is loaded, the flimit thing is done, and byeSElinux is unloaded. The idea was, I wanted the state of SElinux to be exactly the same after my script finishes, as it was before it was run - that's because I might want to run them from terminal (with su) if debugging them :)

Sorry about the FolderMount issue; can you confirm it's from my package? (see my previous post on how to uninstall it - the uninstaller zip removes Xposed, not my fix).

---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------

Read the description: what it does it 1) allows boot to work without having to clear /cache, and 2) once boot completes, it restores the state of zygote to what would have been if the fix hadn't been applied at all. Not sure how safe it is, but what I can tell you is, I couldn't possibly make it any safer. And it's certainly safer than permanent 2048 4096 configurations. I won't even mention 4096 4096 ones, since we already know apps crash on that (the Operas, for one).
[Sony Cross-Device General] TheQwertiest:
My bad, I edited byeselinux manually and thought that your script will disable it %)

I'll try again with restored SELinux and check if the problem persists.

[EDIT] Nope, problem persists with enabled SELinux... Will try to remove the fix and check once again...
[Sony Cross-Device General] mionica:
Btw, if you have su and a terminal, insmod /system/lib/modules/byeselinux.so disables SE enforcing, and rmmod byeselinux re-enables it. That should make things easier - no reboots or anything. To find out if SElinux is bypassed, do lsmod|grep byeselinux; if that returns a line saying something with byeselinux, SElinux is disabled; if it returns nothing, SElinux is enabled (and enforced).

Btw, the lsmod thing is the only reliable method to tell whether SElinux is actually working or not on an Xperia, AFAIK.

And btw, my install script enables byeselinux in XZDR.prop (i.e. disables SElinux enforcing) only once, when the zip is installed; if you mess later with it, my init.d scripts will not interfere (they'll just load byeselinux to do their job, and then honor the XZDR.prop settings, i.e. unload byeselinux thus re-enabling enforcing SElinux in the kernel once they're done).

Finally, there's a 2 seconds window at the end of boot, when SElinux is disabled altogether, regardless of your XZDR.prop setting - while I restore the flimit's on the processes I modded in order to prevent the bootloop. So if something that relied on SElinux being enabled ran exactly then, yup, that might be an issue - but frankly I can't imagine any app refusing to work becase SElinux is off.
[Sony Cross-Device General] ondrejvaroscak:
I didnt check the zip yet, but from what you wrote I dont like the way you check the zygote childs by giving them rather non-standard limits. I must admit it is pretty clever, however from my perspective not clean approach toward the problem. But its purely personal view, nothing to do with functionality of the script or desired result.

My opinion is taken back based on explanation:

]I leave any process that sets its own custom flimits alone, because of the way I detect those I need to restore (if a process changes its own flimits, I won't flag it for restoration)

I consider this hack super efficient, ridiculously simple and way genius. Thank you [MENTION=1103233]mionica[/MENTION] ....
[Sony Cross-Device General] mionica:
Agreed - if my solution is clean, then I'm Santa Claus. But given that I want the limits exactly where they were, I can't think of a better hack; this should be in Xposed after all :D I'm simply attempting to provide the least intrusive solution for as long as one is needed - may that time short! ;)

However, I expect my solution is as low-risk as possible. That's because:

those limits are transitory, and go away as soon as boot completes;

the file limits only matter if you're actually trying to go over them (for an app opening 100 files, it's irrelevant whether the limit is 1000 or 4000);

memory is allocated in pages, and I'm pretty damn sure 4095 entries will take exactly as many 4K pages as 4096 ones; that way, when realloc() happens while resetting the flimits, the reallocation will happen in-place;

I leave any process that sets its own custom flimits alone, because of the way I detect those I need to restore (if a process changes its own flimits, I won't flag it for restoration)

for pid in $(ps|awk '{print $1}')
do
/system/xbin/flimit $pid | grep 'soft=2047; hard=4095' 2>&1 > /dev/null \
&& /system/xbin/flimit $pid 1024 4096 2>&1 > /dev/null
done

finally, the 3-stage flimits restoration procedure makes it extremely unlikely that I'd miss any process I shouldn't miss - 2 steps should've been enough, actually

I rest my case :)

PS. There's one thing I'm not happy about - having left 1s between the stages of flimit restoration. 1s is perfect for waiting for boot to complete, but after that, I think 0.1s would have been more appropriate :D But I won't mod the .zip just for that.
[Sony Cross-Device General] ondrejvaroscak:
I knew I am missing something ... that´s genius way ... actually given the limited possibilities in busybox, it can not be detected better way.

I am taking back my objection. Its not systematic clean, but its GLORIOUS hack.
[Sony Cross-Device General] mionica:
PPS. Here's some homework for somebody who feels so inclined: modify my system/etc/init.d/99_revert_flimit_after_boot script (or replace it) such that the limits are only checked for PIDs of zygote descendants. That way, only descendants of zygote which didn't touch their flimits would be restored.

That'd be cleaner; but I'm not considering doing it myself, unless I'm satisfied that there's any need for it (in my understanding, there's none).

---------- Post added at 04:42 PM ---------- Previous post was at 04:36 PM ----------

Well, you're to blame :D If I hadn't seen your post about some zygote descendants being 8192/8192, I wouldn't have bothered. But if you flagged it, how could I refuse what I can't refute?

;)
[Sony Cross-Device General] ondrejvaroscak:
Update OP

Hi guys, I am updating OP for this thread. I didn't have much time today for follow ups and own development, but [MENTION=1103233]mionica[/MENTION] cooked nice ZIPs that address most of the concerns. http://xdaforums.com/showpost.php?p=60298690&postcount=123?

For the time being I consider his workaround as most suitable for working with/flashing.
[Sony Cross-Device General] TheQwertiest:
[MENTION=1103233]mionica[/MENTION]: Not so clean it seems :D

There is a little bug in fix_xzdr.sh:

echo [B]echo[/B] "dr.keep.byeselinux=true" >> $file

Extra echo is unneeded here ;)

It doesn't fix my problem with FolderMount though... I tried removing your fix and restoring Enforce SELinux, but no avail... It might be caused by updated XZDR that I flashed before flashing the fix though... Need to try downgrading to previous version.

[EDIT] Oh, and I'm not sure about extra grep here as well:

if test "z$?" != "z0" || cat $file | grep [B]grep [/B]"dr.initd.active=false" > /dev/null

Seriously Copy-Paste coding is bad :P
[Sony Cross-Device General] ondrejvaroscak:
I am posting here modified 99_revert_flimit_after_boot. Edits in red. Modifications is it waits less for boot and it only checks zygote childs for changed values (just processes whole thing faster as not every pid needs checking.). Flashable in att.:

#!/system/bin/sh
#
#zygote filelimits reverting, after boot completed
#Created by mionica
#Based on work by Ondrej Varoscak (ondrejvaroscak @ xda-developers)
#Copyleft
#
#flimit executable source code from http://lzone.de/cheat-sheet/ulimit
#no copyright statement - reused and redistributed in good faith
#
#edited by ondrejvaroscak to shorten waiting for boot completed signal
#and checking only processes that are child of zygote using $(pgrep -P $(pidof zygote))
#

# wait for boot to complete
echo -n "Waiting for boot to complete... "
STATE=$(getprop sys.boot_completed)
while test \( -z "$STATE" \) -o \( "$STATE" = "0" \)
do
[COLOR="Red"]sleep 0.1[/COLOR]
echo -n "."
STATE=$(getprop sys.boot_completed)
done
echo "ok"

# load byeSElinux, if it wasn't already loaded
BYESELINUX=0
echo -n "Checking if byeSElinux is loaded... "
if lsmod | grep byeselinux > /dev/null
then
BYESELINUX=1
echo "yes"
else
echo "no"
echo -n "Loading byeSElinux... "
if test ! -e /system/lib/modules/byeselinux.ko
then
echo "NOT FOUND!"
return -1
fi
insmod /system/lib/modules/byeselinux.ko
if lsmod | grep byeselinux > /dev/null
then
echo "ok"
else
echo "FAILED"
return -2
fi
fi

# do the patch
# - run this 3 times at 1s intervals, just in case a process is spawning right
# while we're attempting to change the limits of its parent
echo "Reverting file limits... "
for n in 1 2 3
do
echo -n "$n "
[COLOR="Red"]for pid in $(pgrep -P $(pidof zygote))[/COLOR]
do
/system/xbin/flimit $pid | grep 'soft=2047; hard=4095' 2>&1 > /dev/null \
&& /system/xbin/flimit $pid 1024 4096 2>&1 > /dev/null
done
test "$n" != "3" && sleep 1
done
echo "done"

# unload byeSElinux if we loaded it
#(leave it alone if it was already loaded, i.e. if XZDR wants it kept)
if test "$BYESELINUX" = "0"
then
echo -n "Removing byeSElinux... "
rmmod byeselinux \
&& echo "ok" \
|| echo "FAILED"
fi

return 0
[Sony Cross-Device General] mionica:
Brilliant finds, thanks. Fixed, v2 added to post #123

Thanks!

---------- Post added at 05:40 PM ---------- Previous post was at 05:29 PM ----------

Brilliant, except there's a little bug :) You're only checking for descendants of zygote, but skipping zygote itself ;) here's my version:

for pid in [color=red]$(pidof zygote)[/color] $(pgrep -P $(pidof zygote))
do
/system/xbin/flimit $pid | grep 'soft=2047; hard=4095' 2>&1 > /dev/null \
&& /system/xbin/flimit $pid 1024 4096 2>&1 > /dev/null
done
test "$n" != "3" && sleep 0.1

I'll release version 2.1 in 5mins on post #123 - please mirror it to 1st post (I've also merged the 100ms waiting step when waiting for boot completion).

EDIT: version 2.1 is tested, up, and ready for mirroring.
[Sony Cross-Device General] jawzf:
Any work around for boot loops in Samsung Stock ROMs?? It would be awesome to get Xposed on my phone... cause my rooted Lollipop phone feels powerless!!! :(
[Sony Cross-Device General] McBane87:
I recreated my undo-flashables.

Now they will also remove mionica's Version of the Workaround

http://xdaforums.com/showpost.php?p=60276913&postcount=36
[Sony Cross-Device General] mionica:
See the Xposed discussion thread, first posts. Short answer is no (not yet), but it's caused by Samsung using a custom ART; this thread isn't going to help you, it deals with a Sony-specific issue.
[Sony Cross-Device General] TheQwertiest:
[MENTION=1103233]mionica[/MENTION]:

Actually not per [NUT]:

I.e. if you have dr.keep.byeselinux=true, then you'll have Permissive SELinux. AFAIK=)
[Sony Cross-Device General] mionica:
You're probably right, but frankly I have no idea what XZDR would assume as default once the dr.keep.byeselinux property was gone altogether (having been replaced with a property named "echo dr.keep.byeselinux" :D); so whether byeselinux would be unloaded or not would have depended on how NuT chose to write his script. Anyway, It was an excellent, and early, find.

PS. those weren't copy-paste errors; they were leftovers from version 0, which I based off another package which used a /tmp/busybox (extracted from the.zip itself :p), so all commands looked like /tmp/busybox cat ... | /tmp/busybox grep ... etc; I was careless when getting rid of the busybox refs, no copy-pasting involved.
[Sony Cross-Device General] _mysiak_:
Does anyone know why XZDR uses only /cache directory for setting/reading properties? I tried to re-install XZDR several times, created manually folder on SD card, copied files from cache to SD and removed cache, but files on SD are always somehow ignored. Any idea what did I miss? :)
[Sony Cross-Device General] faded_giant:
You are an effing lifesaver. Thank you so much. Seriously.
[Sony Cross-Device General] [NUT]:
I can tell you I designed it so that it needs to be true in order for byeselinux to remain loaded. That means xzdualrecovery will unload the module when set to false or when it's not set or not even available at all.

---------- Post added at 11:03 PM ---------- Previous post was at 11:01 PM ----------

That's actually a question you should ask me in the devdb thread... ;)

There can be multiple reasons, but I will only be able to tell you why if/when you provide me with the logs from the xzdualrecovery folder...

---------- Post added at 11:08 PM ---------- Previous post was at 11:03 PM ----------

You're right in that.

[MENTION=1103233]mionica[/MENTION], grab the dr- set and get prop functions from the dualrecovery.sh, use them to get and set the variable the correct way. Because if you start echoing stuff in like that you will most likely add multiple lines of the same var in the xzdr.prop file. Using my drsetprop function you will instead replace the value or if it really does not exist, it will add it.

You will need them both because drsetprop will use drgetprop to check if the value exists or not.
[Sony Cross-Device General] mionica:
Good to know.

Aye Sir! ;)

Actually, it didn't occur to me to do that at all; and since I was busy adding support for a flimit.prop under /storage/sdcard1/XZDualRecovery, I already got at the

NSOFT=$(cat $dir/flimit.prop 2> /dev/null | grep -E "^fl.limit.soft=" | tail -1 | cut -c 15- )

stage :D

So, right. Thank you very much; I'll switch shortly, particularly since I'll obviously have uses for them ;)
[Sony Cross-Device General] [NUT]:
You're welcome :)

If you change the filename in the functions to $1 and renumber the other variables you will be able to set a specific properties file, that way you can use them for multiple files :)
[Sony Cross-Device General] Masoud.Ser:
hi thanks for mionica xposed-sonyfix

I'm a little confused about the work process (hard op)

What is the work process?

In this way

1. flash xposed-arm and wipe cache wipe dalvik

2. flash it (XZDR_Inid-Enabler by McBane87)

3. flash it (flimit_flashable_2048 by McBane87) and reboot?

or

1. flash xposed-arm and wipe cache wipe dal..

2. flash it (XZDR_Inid-Enabler by McBane87)

3. flash it (flimit_flashable_2048 by McBane87)

4- flash (mionica xposed-sonyfix) and reboot?

or

1. flash xposed-arm and wipe cache wipe dal..

2- flash (mionica xposed-sonyfix) and reboot?

please explaine more clearly. Thank you very much
[Sony Cross-Device General] CazeW:
No need to wipe anything. The best method for now is:

1. Flash xposed-arm

2. Flash xposed-sonyfix

3. Reboot
[Sony Cross-Device General] mionica:
deleted - somebody answered before I hit "submit reply"

EDIT: be sure to use the xposed-sonyfix-v2.1 from post #123, until the OP updates the attachment to the first thread.
[Sony Cross-Device General] Masoud.Ser:
thanks for reply

Does not require any wipes?(wipe cache-dalvik)

mionica@ The steps right?

1. Flash xposed-arm

2.no wipe anything

3. Flash xposed-sonyfix2.1

4. Reboot

5.install xposed.apk and mods

my nutxdrecovery:v2.8.14
[Sony Cross-Device General] mionica:
You can wipe /cache to your heart's content; but you don't have to, since the apps will all be recompiled when Android figures out the binaries for ART have changed.
[Xiaomi Mi 4] brunneis:
Today I bring to you some new wallpapers in QHD (2560p). They are all inspired by Xiaomi (Mi) and their presentation poster of the inminent event at New Delhi. (But completly new and exclusive).

View attachment 3275253

So... I packed them in a new app, like I did with the LG G4 Wallpapers (here: http://xdaforums.com/lg-g2/themes-apps/lg-g4-lg-ux-4-0-wallpaper-t3075077). There are 9 free wallpapers + 5 exclusive for PRO users (PRO is like a donation, if you like my work. You will remove all ads too).

Hope you like them! :o

Download: Mi5 Material Wallpapers (on Play Store)

View attachment 3275256

Some screenshots:

View attachment 3275261
[LG Optimus L9 P760, P765, P768, P769] cheppiroma:
Dear friends,

I had this problem for a long time. I always facing network problem everytime i flash custom rom from kitkat to lolipop. The notwork is disabling everytime i change wifi to mobile data, and change from airplane mode. Some friends in XDA thread says it because my P765 baseband (v20b) is out of date, and should be updated to v20p. I already try this method but it did not suceed. I wonder is there an easy way to update the baseband? Realy need the feed back, thanks before friends..

Regards,

Koldan
[LG Optimus L9 P760, P765, P768, P769] BajoPrimate:
Hi [MENTION=5205592]cheppiroma[/MENTION],

you could try the artas182x way in his site:

http://artas182x.tk/how-to-flash-baseband-without-flashing-kdz/

Cheers. Good luck.

Sent from my LG P76020p-EUR-XX unlocked and rooted
[LG Optimus L9 P760, P765, P768, P769] cheppiroma:
Thank's friend, it solved. And yes like you said, I should read carefully of what Artas tell in the post. Maybe I just don't read too well though ;)
[LG Optimus L9 P760, P765, P768, P769] BajoPrimate:
Hi cheppiroma, you're welcome, I'm glad with your success. Cheers. Good luck.
[Galaxy S III Original Android Development] perseolorenzo:
​

​

PERSEO MASTERGOLD DISCOVERY V4s. AROMA

Galaxy S3 GT-I9300 with operating system -( 4.3 - 4.4.2 - 4-4-4 )

Do not install on other devices

NOT compatible : With Kernel-based ANYKERNEL

FOR THE SAFETY OF YOUR PHONE

Please read this thread clearly and carefully before attempting installation

VERY IMPORTANT - Please take a NANDROID backup of your device before installing this MOD

The new versions also cleans uninstall old Mastergold​

WHAT IS THIS MOD :

Features: - Less RAM usage through Zipalign - Graphics Enhancement

best overall performance - Less delays through LMK Tweak Various VM and Tweaks

Faster SDCARD read / write speed - CWM / TWRP flashable - Increases sensitivity touchscreen

screenplay system cleaner for regular cleaning of the system - better battery performance

Ad block - script optimization GPS - build.prop tweaks - tweaks Kernal - SQLite optimization etc ........

WHAT YOU NEED TO INSTALL THIS MOD MOD :

Superior to Android 2.3 - Kernel with init.d support - Root access - CWM / TWRP

Free space Depending on your choices in Aroma

( At the end of the installation in Aroma you carefully read the list of the features that you have installed. )

How to install the MOD

1. Download the flash can zip.

2. Reboot into recovery mode.

3. Install the ZIP file

4. Have a little patience That loads the good system.

5 a when the system is loaded, wait about 5 minutes and restart the device.

You're done, you now have installed on your phone:

MASTERGOLD DISCOVERY

Thank you very much :

All credits goes to these people

Franciscofranco

Ryuinferno

ImbaWind

Jeeko

Zeppelinrox

Pikachu01

Nitzz

Micro Monster

DroidFolks

Slaid480

Slim80

Zoot1

Fivefour

matyas69

ZeroInfinity

Ricky310711

SkywalkerZ

Chainfire

Lord Boeffla

arter97

javilonas

​

​

​

​

XDA:DevDB Information

Perseo Mastergold Discovery Mod, Device Specific App for the Samsung Galaxy S III I9300

Contributors

perseolorenzo

Version Information

Status: Stable

Current Stable Version: V4s.

Stable Release Date: 2015-04-22

Beta Release Date: 2015-04-22

Created 2015-04-22

Last Updated 2015-04-21
[Galaxy S III Original Android Development] perseolorenzo:
Reserved

DOWNLOAD​

Do not install on other devices​

4.4.4

Mastergold Discovery V4s. Samsung Galaxy S3 GT-I9300

Download Megahttps://mega.co.nz/#!WBMzlBbT!Hb36m9GsCStbZdKmjqEkId5YsPXU3soqGRdykWrPgBQ

Download Drivehttps://drive.google.com/file/d/0BwTKfuhna4Y2R19EZTFXcUFKSzA/view?usp=sharing

Uninstall Downloadhttps://mega.co.nz/#!qccyBIzC!p3J5S2HAY-VHVp_pU-6mbgxXQelk9m5LHOmUVZEvDjA

=========================================================

4.4.2

Mastergold Discovery V4s. Samsung Galaxy S3 GT-I9300

Download Megahttps://mega.co.nz/#!2VMzCRYD!pe7tXGnSCbASevWPjH3OdLUgzjn5YuRd3BOwi4UUXwo

Download Drivehttps://drive.google.com/file/d/0BwTKfuhna4Y2RzZBVDZhSHV5ems/view?usp=sharing

Uninstall Downloadhttps://mega.co.nz/#!3JkUiLrS!ewJHBVW0zuwyzQKfvlCs4rUN_16oNivX9-xtEzUOdhI

=========================================================

4.3

Mastergold Discovery V4s. Samsung Galaxy S3 GT-I9300

Download Megahttps://mega.nz/#F!xVlUUQKI!iihDe08ylX2Ea7WqttUFBQ

Download Drivehttps://drive.google.com/file/d/0BwTKfuhna4Y2OUpTX0IwY2FqbmM/view?usp=sharing

Uninstall Downloadhttps://mega.co.nz/#!KQ0TRZRb!W007lvrsPt07gGmo50jx5KfH5hhFnE8J_Ei5LoHCg-U
[Galaxy S III Original Android Development] perseolorenzo:
Reserved
[Galaxy S III Original Android Development] vinodr5371@xdaroms.co.in:
Where is download link??
[Galaxy S III Original Android Development] perseolorenzo:
Mod Perseo

I hope to upload it today
[Galaxy S III Original Android Development] dead4ngel:
cant wait to try this. been on md4 rom for a while now (4.4.4 tw) and installed boeffla kernel. its been laggy lately so hopefully this mod will help.
[Galaxy S III Original Android Development] perseolorenzo:
Mod Perseo

4.3

Mastergold Discovery V4s. Samsung Galaxy S3 GT-I9300

Download Megahttps://mega.co.nz/#!DF9WQQbb!jwKpepUgnkUPEto6cRtF7GlH5s8NEsU-uOZUzYuFsM0

Download Drivehttps://drive.google.com/file/d/0BwTKfuhna4Y2Tk5kMUEzcnlKWGM/view?usp=sharing

Uninstall Downloadhttps://mega.co.nz/#!KVlA2KQI!j381cwi_DtVycngj3DrgKb1uBO-LMcGKQiI9yO8lwq8
[Galaxy S III Original Android Development] arvins03:
Gooooooo Thanks Perseo
[Galaxy S III Original Android Development] Drakkal:
I9300

When you can download 4.4.4? Thank
[Galaxy S III Original Android Development] dead4ngel:
thank you. will be installing right now. is it fine to install with boeffla kernel installed?
[Galaxy S III Original Android Development] perseolorenzo:
Mod Perseo

Soon 4.4.2, you can install with boeffla.
[Galaxy S III Original Android Development] dead4ngel:
well i just installed 4.3 and all went well. i will let it settle and will report back later if it has made a difference or not. also i installed it with boeffla kernel already installed. all i did before hand was set the profile to default.
[Galaxy S III Original Android Development] perseolorenzo:
Mod Perseo

Ok let me know how it runs.