yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Deodexed and odexed gapps could potentially affect the size of the dex cache on /system too. I specifically tested "aokp_jflte_kitkat_nightly_2014-05-24.zip" and "aokp-full_gapps-kk-20140528.zip" and when my /system partition only had 250MB free, I ran into similar issues you encountered. I still wonder why PA gapps would work without issues though.

Regarding f2fs, the method you suggested should work just fine with version 7.0.0 of the patcher (it will be released in a few minutes). Just patch AOKP, the gapps, and KT-SGS4. I haven't tested f2fs yet because my partitions are all ext4, but the worst case is that AOKP would simply not boot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks a lot :D
[Galaxy S 4 i9505 Original Android Development] remorema:
You know you can just hit the thanks button. Lololol. Just kidding! never mind my sense of humour. ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
But, but, but...I did :laugh:
[Galaxy S 4 i9505 Original Android Development] remorema:
Finally a skilled dev with good sense of humour. Lol

Back to topic. To start I'm no dev. So feel free to correct me if I'm wrong.

I've read something about camera not working even without dual boot in stock ROM with custom kernel's. The work around mentioned was to run the camera at first launch with the original kernel to let it apply camera firmware update, and only after that apply the custom firmware.

I don't know if it's related or not but it's worth to check out (IMO).

Edit: yey! First one to download the apk :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the suggestion! In this case though, the camera fails before the camera app even has a chance to check what firmware version is on the camera.
[Galaxy S 4 i9505 Original Android Development] remorema:
Edit: Other thing is. Why does it happen only when running TW 4.4 as secondary? It has something to do with the patch process? Running it as primary with v6 I had no issues at all.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, it's the strangest thing I've seen on TouchWiz by far :confused: I forgot to mention it in my previous post, but if you try to change the permissions while the mm-qcamera-daemon is running, a kernel panic happens and the whole device reboots.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I have to use a custom AOSP init (modified to add the TouchWiz 'vibe' vibration group) because the TouchWiz init binary can't mount the dual boot partitions for whatever reason. I'm guessing they have something in their init binary that avoids this problem.
[Galaxy S 4 i9505 Original Android Development] remorema:
I wouldn't go trough all the hassle just to boot TW as secondary. because anyway it makes more sense to keep it as primary. But that's just me ;) I had that issue if you can remember and solve it that way. Never had any more issues since I placed TW as primary.
[Galaxy S 4 i9505 Original Android Development] AoEKiller:
There you go my friend:

http://xdaforums.com/attachment.php?attachmentid=2470765&d=1387825856
[Galaxy S 4 i9505 Original Android Development] Technical:
Some time ago I've downloaded 5 zip files to share user apps among ROMs. Now I can't find them anymore.

As they were

not

developed by me, I can't give more support, only my personal user experience.

They allow sharing the user apps only, i.e., not system ones and not the user data either.

Also, TW apps (for instance, Samsung ones) does not work on AOSP ROMs and could crash.

But they allow saving space and also it makes a mirror of all installed apps among ROMs. Install in one, install in all of them.

Paid apps will require the same Google account to register.

The files are available here:

AppShare_dualboot.zip 149 Kb MD5: 1C16EC2C0A436E4E95046E9CCD22C321

AppShare_multislot1.zip 150 Kb MD5: 77532ED75F2345E6732152E862C1579A

AppShare_multislot2.zip 150 Kb MD5: 12076790E7D209AD6D8B62E5301FEAF0

AppShare_multislot3.zip 150 Kb MD5: DEECADE6DE5E1A8C4EAB80D91C3C40F3
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
I tried to install it to multi slot 1 and I got an error. I will attach the recovery log. I saw that your script mounts everything as ext4, even though my data and cache are f2fs. I was using ktoonsez his molded them with f2fs. I tried it with the 'force f2fs' option in the settings on and also why off. I also installed omnirom to dual, but couldn't get past the setup wizard. I think it is a problem with f2fs. I don't mind if you won't support f2fs (will probably switch to ext4 soon anyways) but if you are interested here is the log: I cut everything out except the rom install and the error:

https://www.dropbox.com/s/ub89ct3mm7tt03l/aokpinstall.log

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] remorema:
Hi mate,

Just to let you know this script works flawless. and both roms detect the apps, either if they're installed in one or another.

I need a little help to another script if you have the time.

In my primary TW rom I use folder mount to read obb files from extSdCard, but in secondary wich is CM11 latest Snapshot

that apps fails to read the folders I need to mount so, I need a little script to mount external/Obb as internal/Android/obb.

I would look something like this

#!/sbin/busybox-static sh
/sbin/busybox-static mount -o bind /storage/sdcard1/Obbs /storage/emulated/0/Android/obb

Will it work without messing up anything ?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
So could I use these zips for roms that are already present (up and running) or do I need to start from fresh installs?
[Galaxy S 4 i9505 Original Android Development] kunal.bodke:
I need help!

I want to make MIUI v5 4.6.13 to be my primary ROM on my GT - I9500 and CM 11 4.4.2 KitKat as secondary rom, I tried the patcher app it shows "Failed to write kernel"

I am attaching the screenshot for the details about kernel and baseband version.

Should I flash another kernel ? :confused:
[Galaxy S 4 i9505 Original Android Development] Bejda:
It won't work on i9500 anyway, sorry.
[Galaxy S 4 i9505 Original Android Development] Technical:
I'll start the dual and multiboots again.

You can use Dual Boot Utilities (see OP) and wipe data from that installations.

After that, return to recovery and flash the zips.

Reboot into the other ROMs. First boot will be "very" long (10-15 minutes) if you have so many installed apps.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Sorry for the million questions - do you mean wipe data from all roms or all but the primary?

Also, if we want to put another new rom in after we have done the app share will this work or have to start the process all over?
[Galaxy S 4 i9505 Original Android Development] kunal.bodke:
The thread says All S4 variants..?? it doesn't support? [emoji19]
[Galaxy S 4 i9505 Original Android Development] Technical:
Don't worry, this is a help forum :)

Better ask to do something "wrong".

I mean wipe the data from all roms except the primary.

You can also do a backup of the primary with Titanium and restore the USER apps and data among ROMs. Some (exceptional) apps could fail. Do NOT restore system apps and any system settings among different ROMs.

It will work, you don't have to share the other (previous) ROMs again, i.e., you don't have to start the process all over again.

I flash the AppShare zip each time I flash a ROM.
[Galaxy S 4 i9505 Original Android Development] Bejda:
The point is to save some space under /data (under our internal storage then), it would be useless to keep your secondary rom /data/app/ folder full while your secondary rom actually uses primary's /data/app/ i think.

I never used these scripts but i guess what you could do to avoid a simple wipe data on secondary rom and then keep your secondary rom apps and system settings could be to just delete secondary rom /data/app folder content (/data/app-lib/ also).

What i would do is (if I only wanted to share primary data/app with secondary rom):

Switch to primary first.

Go to /data/dual/app/ and delete content (/data/dual/app-lib/ also).

Put the init.d script under /system/dual/etc/init.d/ (+set needed perms on this file).

And then switch to secondary.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Thank you, and flash the zip in recovery or did bejda say something about putting zip in init.d? Confused
[Galaxy S 4 i9505 Original Android Development] Bejda:
As you wish :) Flash the zip that will push the file under init.d or put the file manually is about the same.

As for "methods" mine is untested and only "useful" if a wipe data on secondary rom (btw you only have primary and secondary rom yeah? That's what I supposed) would be a big pain for you lol.

Edit:But let's do it simple, I guess i bring again confusion here lol. Better follow what Technical says ;)

---------- Post added at 06:23 PM ---------- Previous post was at 06:07 PM ----------

[MENTION=1634956]remorema[/MENTION]

By using the script you'll be sharing same FolderMount apk but not its settings.

Even if using share-apps script i guess you can just configure FolderMount differently for it works on secondary or multi-slot roms.

http://xdaforums.com/showpost.php?p=52310718&postcount=2638
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Yeah, I'm planning on restoring a back up of slim to dual slot
[Galaxy S 4 i9505 Original Android Development] remorema:
Either I wasnt clear or you misread my post. I dont want to share any settings. All I want is to have OBB folder in external card and mount it in both primary and secondary even if I have to use diferent methods.

The thing is none of my methods are working.

On primary TW folder mount says my sdcard module is not OK.

And in secondary Im still looking for a method that works :(

Edit: I kanged the sdcard module from wanamlite rom and now I'm able to mount externa obb to primary rom using folder mount.

Still looking for a solution to secondary rom ;)
[Galaxy S 4 i9505 Original Android Development] Bejda:
Maybe something changed with FolderMount i didn't used it very recently but when the app says something about Module i used to let it "fix" it + reboot and it always worked fine.

On secondary or multislots rom it also always worked but again:

http://xdaforums.com/showpost.php?p=45560831&postcount=1952

Still doesn't work for you if you show /raw-data/media/0 as source path?

Edit: Doesn't seems to work for me either but used to work before,something's changed maybe dunno..
[Galaxy S 4 i9505 Original Android Development] royredman:
Has anyone tried patching their titanium backup update zip file? If it works, I would love to do it with my dualboot roms!! :D

OR better yet, are we able to share the apps from one rom to the other so we only have one set of apps installed and the second rom can grab the apks (this would save a bunch of space)
[Galaxy S 4 i9505 Original Android Development] Bejda:
Should work fine with Custom preset/AutoPatcher/boot.img untick.

On my side i sometimes use ZipMe app:

https://play.google.com/store/apps/details?id=zip.me

Which allows me to make a cwm zip of Titanium Backup paid version + settings and i patch it with same settings (custom,autopatch,no boot.img).

About sharing apps possibility we were just talking about it on last pages,check ;)
[Galaxy S 4 i9505 Original Android Development] remorema:
the folder mount fixed only worked after I kanged the file from wanamlite.

with my original TW rom file it wasnt working.

for the secondary somehow folder mount cant read /storage/emulated/0/Android folder.

I was trying to fix that by using some kind of bot script and forget about folder mount but the script

I posted earlier its not working.
[Galaxy S 4 i9505 Original Android Development] Bejda:
That is normal as,when we're on secondary or multislot rom,the real/physical path to sdcard is /raw-data/media/0/ and not /data/media/0/ anymore.

I,and others,always had FolderMount working fine on secondary and multislot roms by showing /raw-data/media/0/Android/obb/*** as source path but it doesn't seem to work anymore,don't know why :(
[Galaxy S 4 i9505 Original Android Development] remorema:
Tks for the info. I tried to use folder mount in secondary and mount it as /raw-data/media/0/Android/obb/***

And its working. Actually folder mount is able to mount that folder and when I browse to it I can actually see the mounted content.

Edit: found it. Hehehe

We have to folder mount to /raw-data/media/obb instead :)

Eureka :D

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
A little bit more help please - I have wiped all apps from secondary, I go to recovery. flash app share dual boot zip then boot straight beck into secondary but it boots very quick and no apps are mirrored there. What am I doing wrong??
[Galaxy S 4 i9505 Original Android Development] RK:
Does your secondary ROM support init.d?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Slimkat - yes, certainly, and the script is there with permissions set correctly 755
[Galaxy S 4 i9505 Original Android Development] allan1313:
Forgive my ignorance. I flashed this for dual boot but it didn't work. Is there a certain way to do it??
[Galaxy S 4 i9505 Original Android Development] remorema:
Any solution to keep whatsapp active on both primary and secondary?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Still trying to work it out - I have put clean install of slim in secondary now but still not seeing apps from primary. Hopefully [MENTION=1011179]Technical[/MENTION] will be able to advise us exactly the steps he has taken to get it working :)

Information: wanamlite with talexop kernel in primary and SlimSaberKat with Alucard in secondary.
[Galaxy S 4 i9505 Original Android Development] Bejda:
I never really paid attention to sharing apps possibilities, we have about 9gb of internal storage ,mine is almost always full of 5 roms data's lol but well we have microsd slot and FolderMount ;) , it could be worse.

Actually the(one of the) way to do it is available from the start,as far as i remember when on secondary or multislot rom we always had this /init.multiboot.mounting.sh under root that says near the end:

# Eventually, maybe share /data/app
#/sbin/busybox-static mkdir -p /raw-data/app /data/app
#/sbin/busybox-static chmod 0771 /data/app
#/sbin/busybox-static chmod system:system /data/app
#/sbin/busybox-static mount -o bind /raw-data/app /data/app

if [ -f /init.additional.sh ]; then
/sbin/busybox-static sh /init.additional.sh
fi

Same scripts that Chenxiaolong advised to use a few pages back yep (never used one but others similar init.d scripts are also known to work it seems)

The file belongs to patched sec-multislots kernels,if someone's interested (mainly for the fun of it I'd say lol) i used this tool yesterday on my phone and it went perfect:

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

Unpacked my already patched multislot 1 kernel,edit the init.multiboot.mounting.sh in the ramdisk (removed the # on the mentioned lines) and repack.

I wanted to push the edited boot.img in my multislot-1 rom zip and flash it again after a multislot-1 wipe data but i can't manipulate patched zips on my phone as i would wish (see: http://xdaforums.com/showpost.php?p=53191679&postcount=2853 ) so what I've done is:

_Wipe data on multislot-1 with DualBootUtilities (i didn't took time to try to only manually delete /raw-data/multislot-1/app to try to keep multislot-1 rom and apps settings as i told to Jimsilver73 yesterday).

_On device put my edited boot.img under /sdcard/MultiKernels/ renamed as multi-slot-1.img.

Switch to multislot 1 rom and it worked as expected,my multislot-1 rom now uses primary /data/app folder.

Users can make their own share apps ready kernels that way.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Hey Bejda, I successfully installed the tool, moved the boot.img into the aik, now have the split Ramdisk but stuck as to where to find the

init.multiboot.mounting.sh - please could you tell us exactly where to find it and brake down in simple steps what to do next, I'm only a beginner but keen to learn :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
In the ramdisk folder but only if you unpacked an already patched boot.img. File won't exists otherwise.

You remove the # (Comment? Uncomment? Comment out? Should be Uncomment out maybe lol, I never remember the exact term with these # lines :laugh: ) here:

#/sbin/busybox-static mkdir -p /raw-data/app /data/app

#/sbin/busybox-static chmod 0771 /data/app

#/sbin/busybox-static chmod system:system /data/app

#/sbin/busybox-static mount -o bind /raw-data/app /data/app

But the init.d script you tried should have worked, i have no idea why it didn't for you as many others used this without issues before.

Maybe you could try to edit the init.d script you have now installed under secondary rom /system/etc/init.d/ , replace existing lines by these ones here (second code part of Chenxiaolong's post, same lines again yep):

http://xdaforums.com/showpost.php?p=53337612&postcount=2892&nocache=1&z=4137220163829624
[Galaxy S 4 i9505 Original Android Development] Technical:
How did you wipe the apps in dualboot ROM? Did you use wiping feature of Dual Boot Utilities? Or, on contrary, did you wipe data at recovery?

In fact, it always worked for me, if I use the Dual Boot Utilities to wipe data and flash the AppShare.zip for the dualboot ROM it will remap all the apps of the primary.

Which are your primary and dualboot ROMs?

Which is your recovery?

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

Which is your primary and dualboot ROMs?

Which is your recovery?

Which flash order are you following? ROM (dualboot) > Kernel > AppsShare > Reboot?

---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------

Mine works in both ROMs... :o
[Galaxy S 4 i9505 Original Android Development] allan1313:
My primary is hyperdrive.

Secondary is liquid smooth.

Twrp is my recovery.

I flashed ROM, kernel, appshare. Do I need to flash appshare on both Roms because I did after patching it.
[Galaxy S 4 i9505 Original Android Development] Technical:
No. It just need to be flashed after you flash the dualboot (secondary).

I've tested a lot of times and for me it never failed... I've flashed 2 minutes ago and will post in a minute...

Edited: worked as a charm. Android is updated (451 apps being optimized = Dalvik being built) when I reboot on second ROM. All the apps I've installed yesterday are now in the second (dualboot) ROM.

As I've said previously, all apps are shared for me. I'll try to double check if the actual file I'm flashing is that one I've posted.

For me it works not only in the first boot, but if I install an app on ROM 1, it "appears" on ROM 2 (without any setting/data). And vice-versa.
[Galaxy S 4 i9505 Original Android Development] :
Dont you have to re-register each time you switch rom?

In my case I always have to re-register and receive a new code via SMS every time I switch roms :(
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Hey technical - I'm pulling my hair out with this now :mad::mad::mad::mad::mad::mad:

Please - is it the same file you use? I don't know what else to do, feel like I've tried everything, honestly this is the most exhaustive thing I have ever tried to do! Please help before I drown in the mire of android despair!!
[Galaxy S 4 i9505 Original Android Development] Bejda:
I guess the problem with sharing apps scripts has something to do with Android 4.4.3

I'm also unable to get it working through init.d script.

I tested both many times, the commonly used that [MENTION=1011179]Technical[/MENTION] repacked for us and the one we see here that works for [MENTION=1634956]remorema[/MENTION].

The scripts themselves are readable and executed it's not the problem,if i add to them a "echo something somewhere" or any way to debug i can see that init file is read and executed but it just can't do what it's meant to do and even produce unexpected stuffs with data/apps (install manually an .apk > apk uninstalled at next boot and such..)

According to their signatures Technical and Remorema use 4.4.2 roms as secondary (as rom that use primary /data/app partition,you confirm guys? :) )

I didn't took time to test again with a 4.4.2 rom but i'm pretty sure that's the problem.

I can confirm the ramdisk edit i talked about earlier works on 4.4.3 but personally i still don't feel a real need to share stuffs between roms if it's only apk's. Plus despite apps aren't shared this dual/multiboot solution is already very storage-space-friendly,especially on S4.

I guess i'll keep a multislot-1 rom dedicated to testing these stuffs now that i felt into it lol but even when it work (through ramdisk for me on 4.4.3 then) it's more a pain than a help.

I keep preferring having a different sets of apps for every rom despite some storage space loss and do my little TitaniumBackup gymnastic :)
[Galaxy S 4 i9505 Original Android Development] allan1313:
Tried it again. Its working now. Thanks a bunch.
[Galaxy S 4 i9505 Original Android Development] Bejda:
On which rom please? Which Android version especially?

edit:Ah sorry,LiquidSmooth then as you said before?
[Galaxy S 4 i9505 Original Android Development] allan1313:
Yup.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Thanks,and it's a 4.4.2 from what i see..

Well your issue was different then but for others the problem is indeed 4.4.3 i guess, i flashed latest CM11 Snapshot which is still 4.4.2 as multislot-1 and there it simply works with Technical's zip.
[Galaxy S 4 i9505 Original Android Development] Technical:
No need for that. The file is absolutely correct.

---------- Post added at 07:25 PM ---------- Previous post was at 07:18 PM ----------

I'm using Slim 4.4.3 (5.8 weekly) and Goldeneye 34 (which is still 4.4.2). Are you saying the problem will be when the secondary becomes 4.4.3?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Sorry technical - the mad faces weren't meant at you, but at myself - grrrrrrrrr lol. Thank you for all your help, I think I see where the problem lies now as points out by Bejda, I have 4.4.2 primary and 4.4.3 secondary - simple as that!

Going to try editing the ramdisk some more now bejda's way - I like having all the same apps, for me I am out of space with 3 roms, no space for the fourth and fifth and I NEED these to feed the beast lol.

Maybe I'll get a bigger ext sd so I can start running user apps from that, hmm, there's an idea :cyclops:
[Galaxy S 4 i9505 Original Android Development] Technical:
No, for me they're working. But, I have restored into the 2nd ROM the data from the primary (and it carried all the settings...).
[Galaxy S 4 i9505 Original Android Development] Bejda:
From my tests the sharing apps init.d scripts doesn't work anymore on 4.4.3 (if the rom that uses the init script is 4.4.3)
[Galaxy S 4 i9505 Original Android Development] Technical:
It won't work as simple as that. If you move an app from the phone to sdcard, it disappears from the other ROMs and can't be relinked.

Probably you need a script to do that or make a 2nd partition in your sdcard where you move the apps. I was not brave enough to create this 2nd partition as I've lost a 1 month sdcard (Made in China) messing with partitions. Now I want to keep mine intact. :cyclops:

---------- Post added at 07:34 PM ---------- Previous post was at 07:33 PM ----------

Any way to get it working again by editing it?

Can any dev help us on this?

---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------

For me, besides the space, I think is very convenient to have 2 ROMs "identical".

Other users will have space issues, specially it any of the ROMs is TW. It will be almost impossible to have 3 ROMs and, at the same time, many installed apps.