yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Bejda:
I'm not used to the way apks are stored for now,a little lost :)

I only caught some mechanisms at first like if we tick the global "Share primary apps with current rom" option it push two files under this current rom /data partition:

/data/patcher.share-app

And for paid apps:

/data/patcher.share-app-asec

At each boot on this current rom the patched boot.img init.multiboot.mounting.sh (remember? ;) ) check if files exists and then binds or not some /raw-data(primary/let's say real,usual or main /data partition, don't really now how to say it lol) folders to current rom /data partition.

If we use individuals apps sharing from the little i see it's different and push a syncdaemon.json file but this time only to our /raw-data/ partition (if you're running primary rom you'll find under /data but if you're on secondary/multislot you'll only see it under /raw-data/ )

[[see that "sharedata": false tag on this file?.. :) I tried to change it to "true" already lol but it didn't shared app's data,searched on patched boot.img side also if there was a check for this "false" or "true" value but found nothing]].

Btw just noticed that renaming rom trough patcher also create a rominfo.json to that same /(raw-)data location

But yeah I'm pretty lost for now with the way apks are stored,for instance i thought that if i delete the syncdaemon.json file and reboot I could redo my individuals apps sharing process from scratch but apks were still shared.

I stopped a little to try to understand the whole thing for now (even with Chen's scheme I'm still confused lol),rather waiting for a sudden light that will make me get it in a flash :D

Things are still under tests also,not sure but yours and others reports might shows that something maybe doesn't work as intended on the apk storage side,dunno..
[Galaxy S 4 i9505 Original Android Development] Technical:
Right now, two AOSP Roms and I'm having a lot of issues:

1. Lauchers FC at secondary. Even deleting their data, they FC.

2. Some apps do not upgrade at all: Go Launcher, Google Apps Device, Google Play Music, LeanDroid, Moovit... Is it only me?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It's good for me, even when I made the update, I saw a popup with "DualBoot was authorized root privileges".
[Galaxy S 4 i9505 Original Android Development] RK:
I am using the jeboo kernel from this post:

http://xdaforums.com/showthread.php?p=46151563
[Galaxy S 4 i9505 Original Android Development] remorema:
Is there a chance to use a touchwiz rom in mslot1? Wich one would you suggest? Im looking for one that has s5 style and apps as slim as possible and preferably bug free. Any suggestions?

Tapatalked from I9505 Primary Slot XXUGNF1 With Adam Kernel
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Well, I managed to get miui official which is based on tw onto multi slot 2 - I tried with shostock but couldn't get it too boot so I'm guessing not enough space left in system to accommodate, I was running 3 other ROMs at the same time though one of which tw in slot 1.

I use twrp, although did have a little mess about with philz which actual tells you if your system has run out of space after flashing.

Best thing to do is try and see what happens ;)
[Galaxy S 4 i9505 Original Android Development] remorema:
I'll try to patch phoenix v9 and see what happens. I never used multislot so it should fit if I choose wisely during the aroma installer. I'm downloading it now and will post results later ;)

edit: its a no go. not enough space on cache partition. i have to use it as primary.

Tapatalked from I9505 Primary Slot XXUGNF1 With Adam Kernel
[Galaxy S 4 i9505 Original Android Development] gaww:
When you uninstall from secondary, does it also delete it from primary? It did for me, but I may have forgotten to first untick it as shared.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
I wanted to use latest Wanamlite as secondary.

I patched it using the WIndows Application.

For some reason it screwed up my complete /system partition.

When it first didn´t booted (stuck @ samsung bootlogo) I thought okay too less space is the problem.

I tried go back to primary using the Recovery Zip. No go. Still samsung logo appeared...

I formated /system, installed patched Rom and checked with Aromafm. The rom installs into /system AND /system/dual/

So strange...

Formatted system again and used another patched Rom and checked with AromaFM again. This one just installs into dual and boots fine.

Not sure why this happened. Oh well, my primary is semi gone now... need re install some stuff
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Strange things -

I rebooted to my primary and discovered adaway had disappeared. Went into both dual and multi 1 and unchecked and rechecked the app sharing options and then wiped cache/dalvik and rebooted primary but no adaway - just reinstalled it as apk and it's working fine.

Also, in my multi 2 I just tried to install Opera and got an insufficient memory error, cleared out sone system bloat but still the same, however back in primary downloaded and installed no problem.

Hope this feed back is useful, and of course this kind of thing is to be expected as really we are just beta testing atm :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] gaww:
Primary and secondary go into the system partition, Multies go into cache - have you any other Multi's installed. When I was finally able to flash a stripped down TW as Multi 3, I had to delete the other two I had been running first. There is only about 2 GB available for the Multi ROMs.

PS - I have had a few initially shared apps disappear also after either deleting them in the sharing ROM or after unchecking them only.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
That's different to how Chen described earlier although it would make sense except I just installed a 44mb game in multi 1?

Also, definitely haven't unchecked adaway or uninstalled, it's the one app I always have installed.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Anyone with a TW Rom not as primary?

When I have a TW Rom not as primary, burst Mode doesn´t work and also Youtube (server error). Anyone else noticed that?
[Galaxy S 4 i9505 Original Android Development] Technical:
No issues here with Goldeneye as secondary.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, this should be fixed in the latest development version (7.0.0.r128.g6a0b6a0) and will make it into the upcoming 8.0.0 release.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Noticed a couple of small glitches, I have lost SuperSU twice today on multi 1, had to reflash and then download SuperSU app from play.

Also, on primary I seem to have lost access to r/w even though I have Xposed module to allow access to ext SD.

I definitely have plenty of room left in cache partition though as just installed a ROM in multi 3 which is working fine.
[Galaxy S 4 i9505 Original Android Development] Technical:
Stop at bootanimation...

Installed Goldeneye (TW) as secondary (and KT as kernel). Booted, worked like a charm.

Try to share app, next boot, trapped...

Tested twice, using DualBoot Utilities in between to wipe all the secondary ROM.

Installation and 1st run, ok.

Sharing app, trapped into bootanimation...
[Galaxy S 4 i9505 Original Android Development] zetazeta2:
Using stock firmware (few apps debloated) and CM11 as secondary. Everything is working fine, thanks!
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Okay, I changed now and got TW as Primary and a GE as secondary.

Someone else get fails for some root apps on secondary?

SManager can´t delete a file in /system (failed) but another App (Root Browser) can.

On Primary SManager always worked fine.

Someone knows what my mistake is?
[Galaxy S 4 i9505 Original Android Development] Bejda:
Bootanimation has too be longer once apps are shared but yes it seems to also happens to me to be stuck on never ending bootanim (no log for now,sorry).

For now i just force reboot by long pressing power button and it always finally booted fine.
[Galaxy S 4 i9505 Original Android Development] Technical:
More than 30 minutes is not normal even when sharing apps.

I've tested a forced boot also and it fails, i.e., the boot is in loop again.
[Galaxy S 4 i9505 Original Android Development] gaww:
You have room in the cache (use the tool to see what is available in system and cache at any point in time), so you could install something there, but apparently not enough for that Echoe ROM (full version or slim). It depends on its unzipped size vs the size available in the cache for them - which ROM did you finally get to work In Multi ?

I had problems with SuperSU also, and could not get the Play Store version to install binary - it took the latest direct download patched with latest patcher version to get it working. Problems with AdAway also, but t titanium restore got it working again.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
No, I think you misunderstood - I was trying to install an app (30mob max) in ROM multi slot 2 and was getting the not enough memory error, after that I went back to primary and installed the app I wanted then shared it back with multi 2, after that I installed another aosp in multi 3 no problems so lots of space in cache left clearly.

What tool do you use to see how much space is actually in cache?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Also had a long time on the bootanim when I shared a lot of my apps. But phone has finally started after this interminable moment.
[Galaxy S 4 i9505 Original Android Development] gaww:
It is from the OP - DuelBootUtilities 3.1. Besides seeing the usage fn system, cache, etc. on flashing it, it then lets you wipe specific partitions for each ROM and also switch ROMs
[Galaxy S 4 i9505 Original Android Development] Technical:
I have managed to run AOSP ROMs on multislot sharing all apps.

No SuperSu issues.

But, sooner or later, Launchers start to FC (Apex, Goolge and Trebuchet).

Is there any way to have a "shareall apps" except Launchers?

I couldn't understand what I'm doing at the interface when sharing specific apps. Checking and unchecking is not intuitive, i.e., am I sharing or not when check one app at one ROM?

The message also says that will keep a copy of the app for each ROM and then this will SAVE space. Won't be the opposite?
[Galaxy S 4 i9505 Original Android Development] Bejda:
As Gaww said DualBootUtilities zip gently shows us our space left when we flash it but reboot to recovery and flash a zip just to check this..

A root file manager would be the faster and easier way,Root Explorer (but paid app) is pretty handy for that,it always shows partitions used and free space on top of screen wherever we are:

Here i wasn't on primary rom so it's /raw-cache/ that i had to check (would have been usual /cache partition if i was running primary rom).

There should be others root file manager that should give space left though,sometimes by long pressing desired partition then tick "details" or "properties" things like that.

There's also some dedicated apps like DiskUsage and many others that may help:

Another easy and fast way is Terminal Emulator,you just type "df" and then "enter" on your keyboard and it gives you this:

/raw-cache/ for reasons mentioned above here also.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Is it possible not only share the App but also it´s App data? I think about something like Foldermount

E.g. I have Whatsapp installed on my primary and secondary and my Whatsapp Database gets synced between each roms.

Is this possible?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
I like the df command, nice and simple, so I can now see I have 46mb cache free which should be ample seeing as I'm already loaded with 5 roms and individual data plus shared apks, and I know I still have a load of bloat to remove from a couple of those roms.

Happy to say everything seems to be running sweet now, I think I'm staying to get my head around how it all works. Deleting individual apps from roms seems to be working now without removing them on the others.
[Galaxy S 4 i9505 Original Android Development] gaww:
Ditto here - thanks. Just ran it and it showed 40 mb free on system (same as I saw on the tool), and 1 GB free on cache (only have 2 AOSP Multi ROMs and GAPPs on it currently).
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
Primary Slim Rom (aosp based) and Phoenix Rom as secondary (tw based).

Tried sharing several applications, everything seems to be working 100% (actually I can't make any calls through secondary Rom but it's 90% my fault and not patcher's).

Great release, great project!
[Galaxy S 4 i9505 Original Android Development] Technical:
I've used this configuration AOSP (Slim) + TW (Goldeney) and the phone or FC or was unusable (frozen).

All other things work...
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Interesting, I'm running 5 ROMs all sharing the same apks and switching between them often, everything is running as expected.

I have tried many ROMs in my tests and ask work just as well as I would expect if they were run as stand alone.

Maybe try formatting your SD so it's nice and clean and try again?
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
Oh, same thing then. Frozen whenever I was trying to make or receive a call.

Will make a clean installation(flash it as primary - in case it has to do with my modem/old bl even tho I do have signal), if the issue persists it's my settings/Rom issue and not the patch, if not then something is going on.

Thanks for the report.
[Galaxy S 4 i9505 Original Android Development] Technical:
I've installed from scratch (full wipe) a lot of times. I couldn't keep TW as secondary because I lose my phone as a phone :(

But I didn't mess anything with modem and bootloader (and I won't do that, knock wood :cyclops:).
[Galaxy S 4 i9505 Original Android Development] v00d007:
As already told some times here from different users when using a TWz rom it is highly recommended to install it as PRIMARY. Otherwise problems are upcoming pretty sure ...
[Galaxy S 4 i9505 Original Android Development] parkhaus:
Sorry, but i just can't get this to work. I have flashed Phoenix Rom v9 as primary, boots fine. then installed the apk and set the primary kernel to Phoenix ROM. then I use the patch function to patch a CM11 nightly ROM. I then boot into recovery and flash this patched CM11 ROM (not installed as primary, it says, just as it should). Then I reboot, and it boots into CM11. When I then try to switch back to Phoenix ROM, it just does not boot anymore (blue led blinks). I also tried it with other ROMs. also tried switching using Dual Boot utilies - all to no avail :eek:
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Strange, can you try another tw ROM in primary just to see what happens, in fact try my setup just as a little test ;)

Make sure to wipe primary and secondary with dual boot utilities script first though.
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
Sorry for asking the obvious but.. after flashing Cm as secondary and installing Dual boot app, do you set secondary kernel to Cm?

Cause you know you have to set kernels through the app for all the Roms you're using.

I've got a question btw.. is there an easy way to keep the secondary Rom after updating primary? Or I have to flash secondary as well every time..

Thank you in advance.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
May you forgot to set kernel?

1. Install Primary

2. Set Kernel in Dualboot App for primary rom

3. Install secondary

4. Set Kernel for in Dualboot App for secondary rom

Edit:

There is something written in the 1st post.

I am not sure but maybe you could just backup /system/dual to sdcard for example, install Primary Rom and copy folder back? lol did not try it myself so far
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Well Chen gives us a way to do it in the op but I've never been able to work out exactly which files to edit and how. For me, the easy way is to use ROM that doesn't need updating to often then flash back other ROM (s) or even back up other ROMs using the backup utilities aroma script and then restore them after, about as broad as it's long really.

There is no need to set kernels for dual/multi slot ROMs anymore as Chen fixed that, I confirm 5 ROMs and only set primary kernel and ask works fine, in fact I think I did set kernel for secondary after the fix and it messed up, maybe coincidence or maybe this is causing problems for some of you?
[Galaxy S 4 i9505 Original Android Development] parkhaus:
I just gave it one more try (I have already tried with jamal2367 Google ROM for i9505, CM11 nightly and PhoenixRom v9 in every possible dual combination). This time, I did not touch the kernel setting, just change the ROM to boot from.

Outcome: the same. After the secondary ROM (CM11 in this case) has started up, I install the DualBoot apk and set the ROM to be booted back to primary. Reboot - then bootloop with blinking blue led.

Instructions on first page are probably also not up-to-date, as Slot 1-3 options are already available in the apk (but written as "soon available" in the 1st post).

This time for patching I tried slot 1 instead of dual boot. also tried 2 recoveries total: PhilZ advanced CWM and latest TWRP. same outcome.

Sorry, but I give up. Already spent too many hours on that!
[Galaxy S 4 i9505 Original Android Development] Technical:
The new patcher create a situation that solves the situation of Google Play registered account and PC downloads.

Now, the Google account could be used in more than one ROM and in any of them you're logged, you can download apps from web in your PC.

Before, only the latest ROM (the last registered Google Account) receive remote installations. You need to remove your Google Account in the 1st ROM and add it again to be the latest installed account and so, be able to receive updates.
[Galaxy S 4 i9505 Original Android Development] olarf:
Hello, I try this tool the first time and have a question about the following Problem:

I run CM11 as first Rom. I install the patcher apk 7.0 there and set the cm11 kernel as first one. Then i rebooted into cwm and flashed a dualpatched aosp Rom. Then I rebooted and it Boot into the aosp Rom fine. But there Im not able to install any APP (i think the apk Bad to be patched also but how can i do this now). So i find no way to Boot into Rom 1 to patch the patcher apk. Any way to solve this? Is there a patched apk availiable AS download?
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Check OP.

There is a ZIP file you can run via recovery.

It allows you to switch from/kernel
[Galaxy S 4 i9505 Original Android Development] olarf:
Many thanks, it helps me to switch back easy. Now I just have to find the trick to install the APP on second Rom for comfortable switching.

Gesendet von meinem GT-I9295 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] gaww:
I have not ever had problems with Google Play registered account between the multi ROMs.

I think it is because when I wipe and start a new ROM, on boot up - I go straight to titanium. It gives notice that the device ID has changed and asks if you want to keep it or revert. If you keep the new one, your Google Account is toast. If you revert, it works fine. I can update on any other ROM with no problem.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Using DualBootPatcherAndroid-7.0.0.r131.geb3f241-snapshot

Everything seems to be working as expected other than unsharing apks (although uninstalling them from the ROM you no longer want them in manually works fine), also, when sharing to new ROM it is necessary to install dual boot utilities then wipe cache/dalvik for that ROM - I remember in earlier snapshot wipe was done automatically for the individual apks when they were shared. Chen - it would be handy if this could be reinstated ;)
[Galaxy S 4 i9505 Original Android Development] xk0niR:
You could try to push the apk to /system/dual/app (check permissions)
[Galaxy S 4 i9505 Original Android Development] Bejda:
What happens when you try to install apps on this secondary rom?

Apk's doesn't need to be patched,normally you still have the patcher apk on your sd>you click on it and,if unknown sources are ticked under your rom settings>security section, it gets installed without problems.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Anyone else having problem of wrong time @ secondary?

It´s not the 1970 bug and it´s random after every reboot.

Only Googy Kernel hadn´t this problem (GE)

TW = Googy and GE = Googy | no time problem

TW = Googy and GE = Alucard | time problem @ secondary

I will try both Alu
[Galaxy S 4 i9505 Original Android Development] remorema:
Disable auto time on second rom. Set correct time and config date to 2013. Reboot. Config date to 2014. Reboot.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
I am just at flashing both roms again.

Do get you right:

- Disable auto time at second rom

- Set correct time at second rom

- set config date to 2013? Whats that

- Again config date to 2014? Whats that

Thanks a lot!
[Galaxy S 4 i9505 Original Android Development] remorema:
config the clock with the correct time and the date to 2013. Reboot. And correct the date to 2014.
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Thanks it worked! :good:

Can I enable Auto Network time again?

Or better use Apps like clocksync?
[Galaxy S 4 i9505 Original Android Development] remorema:
leave it off. Otherwise you'll ran into the same issues. Why use clock sync if it shows the correct time already?

if it ain't broken don't fix it ;)
[Galaxy S 4 i9505 Original Android Development] xk0niR:
Haha yes you´re right.

There is correct and there is accurate :laugh: Well the german in me... wants all perfect always :p
[Galaxy S 4 i9505 Original Android Development] remorema:
if you want to have atomic time just buy yourself a Tag Heuer :p
[Galaxy S 4 i9505 Original Android Development] gaww:
Half German American, but the other half Irish - we like work-arounds.

Note - definition of Irish engineering - in most cases, if you can't fix it with duct tape or by kicking it - probably not worth fixing.....
[Galaxy S 4 i9505 Original Android Development] Technical:
No? Well, or you haven't used the same Google Account in both ROMs or you haven't try to download app, search for the device when you're connected to the main (1st) account.

I think it is because when I wipe and start a new ROM, on boot up - I go straight to titanium. It gives notice that the device ID has changed and asks if you want to keep it or revert. If you keep the new one, your Google Account is toast. If you revert, it works fine. I can update on any other ROM with no problem.[/QUOTE]

Well, this did not work for me.

chenxiaolong also acknowledged this problem: http://xdaforums.com/showpost.php?p=53586010&postcount=3000
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
G play works perfect for me across all ROMs, never had an issue with it, nor tab wanting to update device ID.

For reference: every time I flash a new ROM I flash new gapps including of course g play and services. I use these, also, tb is always shared, not sure if this makes the difference but it would for me
[Galaxy S 4 i9505 Original Android Development] olarf:
It tell me that the apk is not available even I downloaded it a second before and see it as download. Unkown sources was allowed, that was also my first idea. Spegelius is thinking about and maybe provide in his next build an file explorer. That should make it possible then to try to install apk's from sdcard for example. Actually I had no file explorer and can't install one and so I could just switch back to ROM one via cwm and the great aroma tool.

However, this dualboot kit is amazing! I guess my issue is ROM related or a result of my configuration and once the next build is out I will try it again and see what is the reason. Many thanks for all help so far!

Gesendet von meinem GT-I9295 mit Tapatalk